This is an old revision of the document!
10.8 Traceability Boundaries
Traceability has boundaries. The document set can preserve meaningful relationships without creating unnecessary administrative burden.
A traceability relationship can exist when it supports architecture review, implementation mapping, deployment verification, evidence collection, conformance assessment, audit, governance, or impact analysis.
A traceability relationship can identify enough information to support review, including:
-
Source element
-
Target element
-
Relationship type
-
Part, profile, or artefact containing the relationship
-
Purpose of the relationship
-
Evidence or review mechanism, where applicable
Traceability cannot imply that all details belong in the conceptual architecture. Part 1 defines the conceptual traceability model. Later sections provide detailed traceability matrices, mappings, deployment references, and evidence records appropriate to their respective layers.