Differences

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

--- fxdemo:01-part:13-conceptual-requirements:13-10-profile-and-layering-requirements [2026/06/29 14:31] – ↷ Page moved from fxdemo:01-part:13-10-profile-and-layering-requirements to fxdemo:01-part:13-conceptual-requirements:13-10-profile-and-layering-requirements owen
+++ fxdemo:01-part:13-conceptual-requirements:13-10-profile-and-layering-requirements [2026/07/11 12:57] (current) – ↷ Links adapted because of a move operation nick_dido
@@ Line 1: / Line 1: @@
 ====== 13.10 Profile and Layering Requirements ======
-[[fxdemo:01-part:start | Go to Top ]]
+[[fxdemo:01-part:13-conceptual-requirements:start | Go to Conceptual Requirements]]
-  - A Domain Profile SHALL preserve the conceptual definitions inherited from this part.
+This section identifies the normative requirements for profile and layering 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]].
-  - An Implementation Profile / PSM SHALL preserve the conceptual definitions inherited from this part.
-  - A Deployment, Testability, and Evidence Plan SHALL preserve the conceptual definitions inherited from this part.
-  - A later part SHALL NOT use a technology selection to redefine a conceptual element.
-  - A later part SHALL NOT use a deployment decision to redefine a conceptual element.
-  - A later part that introduces a new term SHALL identify whether the term is conceptual, logical, implementation-specific, deployment-specific, or evidence-specific.
-  - A later part that introduces a new conceptual term SHALL identify its relationship to the conceptual architecture defined in this part.
-  - A later part that specialises, realises, deploys, tests, or evidences a conceptual element SHALL preserve traceability to that conceptual element.
+<WRAP table-caption>
+**Table 13.10-1:** Part 1 profile and layering requirements.
+</WRAP>
+^ Requirement ID ^ Statement ^
+| [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-10-001:start|P1-REQ-13-10-001]] | {{section>dido:99_annexes:annex-d-requirements:part-01:p1-req-13-10-001:start#statement&noheader&nofooter}} |
+| [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-10-002:start|P1-REQ-13-10-002]] | {{section>dido:99_annexes:annex-d-requirements:part-01:p1-req-13-10-002:start#statement&noheader&nofooter}} |
+| [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-10-003:start|P1-REQ-13-10-003]] | {{section>dido:99_annexes:annex-d-requirements:part-01:p1-req-13-10-003:start#statement&noheader&nofooter}} |
+| [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-10-004:start|P1-REQ-13-10-004]] | {{section>dido:99_annexes:annex-d-requirements:part-01:p1-req-13-10-004:start#statement&noheader&nofooter}} |
+| [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-10-005:start|P1-REQ-13-10-005]] | {{section>dido:99_annexes:annex-d-requirements:part-01:p1-req-13-10-005:start#statement&noheader&nofooter}} |
+| [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-10-006:start|P1-REQ-13-10-006]] | {{section>dido:99_annexes:annex-d-requirements:part-01:p1-req-13-10-006:start#statement&noheader&nofooter}} |
+| [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-10-007:start|P1-REQ-13-10-007]] | {{section>dido:99_annexes:annex-d-requirements:part-01:p1-req-13-10-007:start#statement&noheader&nofooter}} |
+| [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-10-008:start|P1-REQ-13-10-008]] | {{section>dido:99_annexes:annex-d-requirements:part-01:p1-req-13-10-008:start#statement&noheader&nofooter}} |
+----
+<WRAP centeralign>
+© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
+</WRAP>