Differences

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

--- fxdemo:01-part:13-conceptual-requirements:13-7-traceability-requirements [2026/06/29 14:31] – ↷ Page moved from fxdemo:01-part:13-7-traceability-requirements to fxdemo:01-part:13-conceptual-requirements:13-7-traceability-requirements owen
+++ fxdemo:01-part:13-conceptual-requirements:13-7-traceability-requirements [2026/07/11 12:57] (current) – ↷ Links adapted because of a move operation nick_dido
@@ Line 1: / Line 1: @@
 ====== 13.7 Traceability Requirements ======
-[[fxdemo:01-part:start | Go to Top ]]
+[[fxdemo:01-part:13-conceptual-requirements:start | Go to Conceptual Requirements]]
-  - The Conceptual Architecture SHALL define traceability across conceptual elements, logical elements, implementation artefacts, deployment artefacts, and evidence.
+This section identifies the normative requirements for traceability established by Part 1. The canonical requirement statements are maintained in [[dido:99_annexes:annex-d-requirements:part-01:start|Annex C: Requirements, Part 1]].
-  - A Logical Architecture / PIM element SHALL trace to the conceptual element it specialises, refines, constrains, or relates.
-  - An Implementation Profile / PSM artefact SHALL trace to the logical element it realises.
-  - A Deployment Artefact SHALL trace to the implementation artefact it deploys, configures, executes, or exposes.
-  - Evidence SHALL trace to the claim, behaviour, artefact, configuration, execution condition, review conclusion, or governance decision it supports.
-  - Traceability SHALL support forward review from conceptual concern to evidence.
-  - Traceability SHALL support backward review from evidence to conceptual concern.
-  - Traceability SHALL support impact analysis across conceptual, logical, implementation, deployment, and evidence layers.
-  - Traceability SHALL NOT require artificial one-to-one correspondence where one-to-many or many-to-one relationships better represent the architecture.
+<WRAP table-caption>
+**Table 13.7-1:** Part 1 traceability requirements.
+</WRAP>
+^ Requirement ID ^ Statement ^
+| [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-7-001:start|P1-REQ-13-7-001]] | {{section>dido:99_annexes:annex-d-requirements:part-01:p1-req-13-7-001:start#statement&noheader&nofooter}} |
+| [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-7-002:start|P1-REQ-13-7-002]] | {{section>dido:99_annexes:annex-d-requirements:part-01:p1-req-13-7-002:start#statement&noheader&nofooter}} |
+| [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-7-003:start|P1-REQ-13-7-003]] | {{section>dido:99_annexes:annex-d-requirements:part-01:p1-req-13-7-003:start#statement&noheader&nofooter}} |
+| [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-7-004:start|P1-REQ-13-7-004]] | {{section>dido:99_annexes:annex-d-requirements:part-01:p1-req-13-7-004:start#statement&noheader&nofooter}} |
+| [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-7-005:start|P1-REQ-13-7-005]] | {{section>dido:99_annexes:annex-d-requirements:part-01:p1-req-13-7-005:start#statement&noheader&nofooter}} |
+| [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-7-006:start|P1-REQ-13-7-006]] | {{section>dido:99_annexes:annex-d-requirements:part-01:p1-req-13-7-006:start#statement&noheader&nofooter}} |
+| [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-7-007:start|P1-REQ-13-7-007]] | {{section>dido:99_annexes:annex-d-requirements:part-01:p1-req-13-7-007:start#statement&noheader&nofooter}} |
+| [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-7-008:start|P1-REQ-13-7-008]] | {{section>dido:99_annexes:annex-d-requirements:part-01:p1-req-13-7-008:start#statement&noheader&nofooter}} |
+| [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-7-009:start|P1-REQ-13-7-009]] | {{section>dido:99_annexes:annex-d-requirements:part-01:p1-req-13-7-009:start#statement&noheader&nofooter}} |
+----
+<WRAP centeralign>
+© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
+</WRAP>