Differences

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

--- fxdemo:01-part:13-conceptual-requirements:13-2-conceptual-separation-requirements [2026/07/02 09:18] – ↷ Page moved and renamed from fxdemo:01-part:13-conceptual-requirements:13-2-conceptual-separation-requirements:start to fxdemo:01-part:13-conceptual-requirements:13-2-conceptual-separation-requirements nick_dido
+++ fxdemo:01-part:13-conceptual-requirements:13-2-conceptual-separation-requirements [2026/07/11 12:57] (current) – ↷ Links adapted because of a move operation nick_dido
@@ Line 1: / Line 1: @@
 ====== 13.2 Conceptual Separation Requirements ======
-[[fxdemo:01-part:start | Go to Top ]]
+[[fxdemo:01-part:13-conceptual-requirements:start | Go to Conceptual Requirements]]
-  - The Conceptual Architecture SHALL preserve separation between conceptual meaning, logical [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:s:structure|Structure]], implementation mapping, deployment mechanics, testability, and [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]].
+This section identifies the normative requirements for conceptual separation 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 conceptual elements from logical elements, implementation artefacts, deployment artefacts, and [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]].
-  - The Conceptual Architecture SHALL NOT allow implementation technologies to redefine conceptual elements.
+<WRAP table-caption>
-  - The Conceptual Architecture SHALL NOT allow deployment artefacts to redefine conceptual elements.
+**Table 13.2-1:** Part 1 conceptual separation requirements.
-  - The Conceptual Architecture SHALL NOT treat runtime identifiers as substitutes for conceptual elements.
+</WRAP>
+^ Requirement ID ^ Statement ^
+| [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-2-001:start|P1-REQ-13-2-001]] | {{section>dido:99_annexes:annex-d-requirements:part-01:p1-req-13-2-001:start#statement&noheader&nofooter}} |
+| [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-2-002:start|P1-REQ-13-2-002]] | {{section>dido:99_annexes:annex-d-requirements:part-01:p1-req-13-2-002:start#statement&noheader&nofooter}} |
+| [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-2-003:start|P1-REQ-13-2-003]] | {{section>dido:99_annexes:annex-d-requirements:part-01:p1-req-13-2-003:start#statement&noheader&nofooter}} |
+| [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-2-004:start|P1-REQ-13-2-004]] | {{section>dido:99_annexes:annex-d-requirements:part-01:p1-req-13-2-004:start#statement&noheader&nofooter}} |
+| [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-2-005:start|P1-REQ-13-2-005]] | {{section>dido:99_annexes:annex-d-requirements:part-01:p1-req-13-2-005:start#statement&noheader&nofooter}} |
+----
+<WRAP centeralign>
+© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
+</WRAP>