| Both sides previous revision Previous revision Next revision | Previous revision |
| fxdemo:01-part:10-conceptual-traceability-model:10-8-traceability-boundaries [2026/06/30 17:11] – owen | fxdemo:01-part:10-conceptual-traceability-model:10-8-traceability-boundaries [2026/07/18 12:33] (current) – external edit 127.0.0.1 |
|---|
| [[fxdemo:01-part:start | Go to Top ]] | [[fxdemo:01-part:start | Go to Top ]] |
| |
| [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] has boundaries. The document set can preserve meaningful relationships without creating unnecessary administrative burden. | [[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 [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] relationship can exist when it supports architecture review, implementation mapping, deployment verification, [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] collection, conformance assessment, audit, [[fxdemo:99_part_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 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 [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] relationship can identify enough information to support review, including: | A [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] relationship can identify enough information to support review, including: |
| |
| * Source element | * Source element |
| * Target element | * Target element |
| * Relationship type | * Relationship type |
| * Part, profile, or artefact containing the relationship | * Part, profile, or artifact containing the relationship |
| * Purpose of the relationship | * Purpose of the relationship |
| * [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] or review mechanism, where applicable | * [[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> |
| |
| [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] cannot imply that all details belong in the conceptual architecture. Part 1 defines the conceptual [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] model. Later sections provide detailed [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] matrices, mappings, deployment references, and [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] records appropriate to their respective layers. | |