This is an old revision of the document!
10.1 Overview
The Conceptual Traceability Model defines how the Financial Systems Archetype preserves relationships among conceptual elements, logical elements, implementation artefacts, deployment artefacts, 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 artefact, deployment artefact, or evidence requirement changes.
Figure 10.1-1 summarises the traceability chain used by the Financial Systems Archetype.
Conceptual Element
└── Logical Element / PIM
└── Implementation Artefact / PSM
└── Deployment Artefact
└── 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 artefacts. One evidence item may support multiple claims. The architecture requires explicit relationships, not artificial one-to-one correspondence.