Differences

This shows you the differences between two versions of the page.

--- fxdemo:01-part:10-conceptual-traceability-model:10-8-traceability-boundaries [2026/06/29 14:38] – ↷ Page moved from fxdemo:01-part:11-conceptual-rules-and-constraints:10-8-traceability-boundaries to fxdemo:01-part:10-conceptual-traceability-model:10-8-traceability-boundaries owen
+++ fxdemo:01-part:10-conceptual-traceability-model:10-8-traceability-boundaries [2026/07/18 12:33] (current) – external edit 127.0.0.1
@@ Line 2: / Line 2: @@
 [[fxdemo:01-part:start | Go to Top ]]
-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 traceability relationship can exist when it supports architecture review, implementation mapping, deployment verification, evidence collection, conformance assessment, audit, governance, 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 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
   * Target element
   * Relationship type
-  * Part, profile, or artefact containing the relationship
+  * Part, profile, or artifact containing the relationship
   * Purpose of the relationship
-  * 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>
-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.