10.1 Overview

Go to Top

The Conceptual Traceability Model defines how the Financial Systems Archetype preserves relationships among conceptual elements, logical elements, implementation artifacts, deployment artifacts, and Evidence.

Traceability allows authors, reviewers, implementers, testers, operators, and auditors to understand how a concern moves through the document set. It also supports impact analysis when a concept, logical element, implementation artifact, deployment artifact, or Evidence requirement changes.

Figure 10.1-1 summarises the traceability chain used by the Financial Systems Archetype.

Conceptual Element
└── Logical Element / PIM
    └── Implementation Artifact / PSM
        └── Deployment Artifact
            └── Evidence

Figure 10.1-1: Traceability chain from conceptual element to evidence

The Traceability chain does not require one-to-one mapping at every layer. One conceptual element may influence multiple logical elements. One logical element may map to multiple implementation artifacts. One Evidence item may support multiple claims. The architecture requires explicit relationships, not artificial one-to-one correspondence.