10.8 Traceability Boundaries

Go to Top

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 elementTarget elementRelationship typePart, profile, or artefact containing the relationshipPurpose of the relationshipEvidence or review mechanism, where applicableTraceability 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.