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 and Authority, or impact analysis.

A Traceability relationship can identify enough information to support review, including:

• Source element
• Target element
• Relationship type
• Part, profile, or artifact 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.