====== 10.8 Traceability Boundaries ======
[[fxdemo:01-part:start | Go to Top ]]

[[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] has boundaries. The document set can preserve meaningful relationships without creating unnecessary administrative burden.

A [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] relationship can exist when it supports architecture review, implementation mapping, deployment verification, [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] collection, conformance assessment, audit, [[dido:99_annexes:annex-b-terms-and-definitions:g:governance_and_authority|Governance and Authority]], or impact analysis.

A [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|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
  * [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] or review mechanism, where applicable

[[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] cannot imply that all details belong in the conceptual architecture. Part 1 defines the conceptual [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] model. Later sections provide detailed [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] matrices, mappings, deployment references, and [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] records appropriate to their respective layers.


----

<WRAP centeralign>

© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.

</WRAP>