Differences

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

--- fxdemo:01-part:13-conceptual-requirements:13-6-separation-of-concerns-requirements [2026/06/29 14:31] – ↷ Page moved from fxdemo:01-part:13-6-separation-of-concerns-requirements to fxdemo:01-part:13-conceptual-requirements:13-6-separation-of-concerns-requirements owen
+++ fxdemo:01-part:13-conceptual-requirements:13-6-separation-of-concerns-requirements [2026/07/11 12:57] (current) – ↷ Links adapted because of a move operation nick_dido
@@ Line 1: / Line 1: @@
 ====== 13.6 Separation of Concerns Requirements ======
-[[fxdemo:01-part:start | Go to Top ]]
+[[fxdemo:01-part:13-conceptual-requirements:start | Go to Conceptual Requirements]]
-  - The Conceptual Architecture SHALL distinguish Data, Structure, Semantics, Interpretation, Governance and Authority, and Traceability and Evidence as structured-information processing concerns.
+This section identifies the normative requirements for separation of concerns 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]].
-  - The Conceptual Architecture SHALL distinguish Data from Structure.
-  - The Conceptual Architecture SHALL distinguish Structure from Semantics.
-  - The Conceptual Architecture SHALL distinguish Semantics from Interpretation.
-  - The Conceptual Architecture SHALL distinguish Governance and Authority from the technical mechanisms that support governance.
-  - The Conceptual Architecture SHALL distinguish Traceability from Evidence.
-  - Cross-concern relationships SHALL preserve the distinction between the concerns involved.
-  - Cross-concern relationships SHALL be traceable when they affect meaning, interpretation, governance, authority, auditability, or evidence.
-  - The Conceptual Architecture SHALL distinguish full transaction detail from transaction metadata and aggregate information products.
-  - The Conceptual Architecture SHALL distinguish data sovereignty from data residency.
-  - The Conceptual Architecture SHALL distinguish data-at-rest concerns from data-in-motion concerns.
-  - Cross-concern relationships involving policy-governed release SHALL preserve the distinction between governance, authority, traceability, evidence, data, and interpretation.
+<WRAP table-caption>
+**Table 13.6-1:** Part 1 separation of concerns requirements.
+</WRAP>
+^ Requirement ID ^ Statement ^
+| [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-6-001:start|P1-REQ-13-6-001]] | {{section>dido:99_annexes:annex-d-requirements:part-01:p1-req-13-6-001:start#statement&noheader&nofooter}} |
+| [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-6-002:start|P1-REQ-13-6-002]] | {{section>dido:99_annexes:annex-d-requirements:part-01:p1-req-13-6-002:start#statement&noheader&nofooter}} |
+| [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-6-003:start|P1-REQ-13-6-003]] | {{section>dido:99_annexes:annex-d-requirements:part-01:p1-req-13-6-003:start#statement&noheader&nofooter}} |
+| [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-6-004:start|P1-REQ-13-6-004]] | {{section>dido:99_annexes:annex-d-requirements:part-01:p1-req-13-6-004:start#statement&noheader&nofooter}} |
+| [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-6-005:start|P1-REQ-13-6-005]] | {{section>dido:99_annexes:annex-d-requirements:part-01:p1-req-13-6-005:start#statement&noheader&nofooter}} |
+| [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-6-006:start|P1-REQ-13-6-006]] | {{section>dido:99_annexes:annex-d-requirements:part-01:p1-req-13-6-006:start#statement&noheader&nofooter}} |
+| [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-6-007:start|P1-REQ-13-6-007]] | {{section>dido:99_annexes:annex-d-requirements:part-01:p1-req-13-6-007:start#statement&noheader&nofooter}} |
+| [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-6-008:start|P1-REQ-13-6-008]] | {{section>dido:99_annexes:annex-d-requirements:part-01:p1-req-13-6-008:start#statement&noheader&nofooter}} |
+| [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-6-009:start|P1-REQ-13-6-009]] | {{section>dido:99_annexes:annex-d-requirements:part-01:p1-req-13-6-009:start#statement&noheader&nofooter}} |
+| [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-6-010:start|P1-REQ-13-6-010]] | {{section>dido:99_annexes:annex-d-requirements:part-01:p1-req-13-6-010:start#statement&noheader&nofooter}} |
+| [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-6-011:start|P1-REQ-13-6-011]] | {{section>dido:99_annexes:annex-d-requirements:part-01:p1-req-13-6-011:start#statement&noheader&nofooter}} |
+| [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-6-012:start|P1-REQ-13-6-012]] | {{section>dido:99_annexes:annex-d-requirements:part-01:p1-req-13-6-012:start#statement&noheader&nofooter}} |
+----
+<WRAP centeralign>
+© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
+</WRAP>