Differences

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

--- fxdemo:01-part:13-conceptual-requirements:13-9-relationship-to-logical-architecture-pim-requirements [2026/06/29 14:31] – ↷ Page moved from fxdemo:01-part:13-9-relationship-to-logical-architecture-pim-requirements to fxdemo:01-part:13-conceptual-requirements:13-9-relationship-to-logical-architecture-pim-requirements owen
+++ fxdemo:01-part:13-conceptual-requirements:13-9-relationship-to-logical-architecture-pim-requirements [2026/07/11 12:57] (current) – ↷ Links adapted because of a move operation nick_dido
@@ Line 1: / Line 1: @@
 ====== 13.9 Relationship to Logical Architecture / PIM Requirements ======
-[[fxdemo:01-part:start | Go to Top ]]
+[[fxdemo:01-part:13-conceptual-requirements:start | Go to Conceptual Requirements]]
-  - The Logical Architecture / PIM SHALL use the conceptual elements defined in this part.
+This section identifies the normative requirements for the relationship between the Conceptual Architecture and the Logical Architecture / PIM 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 Logical Architecture / PIM SHALL preserve the definitions of conceptual elements defined in this part.
-  - The Logical Architecture / PIM SHALL NOT redefine Node, Node Identity, Node Role, Runtime Plane, Communication Endpoint, Data Structure Definition, Data Structure Instance, Evidence, Traceability, Ecosphere, Ecosystem, Domain, or Classification Path.
-  - The Logical Architecture / PIM SHALL remain platform independent.
-  - The Logical Architecture / PIM SHALL NOT bind logical elements to DDS, IDL, Python, Kubernetes, K3s, Docker, RTI Connext DDS, Crucible, or other implementation-specific mechanisms.
-  - The Logical Architecture / PIM SHALL provide traceability from logical elements to the conceptual elements they specialise, refine, constrain, or relate.
+<WRAP table-caption>
+**Table 13.9-1:** Part 1 relationship to Logical Architecture / PIM requirements.
+</WRAP>
+^ Requirement ID ^ Statement ^
+| [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-9-001:start|P1-REQ-13-9-001]] | {{section>dido:99_annexes:annex-d-requirements:part-01:p1-req-13-9-001:start#statement&noheader&nofooter}} |
+| [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-9-002:start|P1-REQ-13-9-002]] | {{section>dido:99_annexes:annex-d-requirements:part-01:p1-req-13-9-002:start#statement&noheader&nofooter}} |
+| [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-9-003:start|P1-REQ-13-9-003]] | {{section>dido:99_annexes:annex-d-requirements:part-01:p1-req-13-9-003:start#statement&noheader&nofooter}} |
+| [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-9-004:start|P1-REQ-13-9-004]] | {{section>dido:99_annexes:annex-d-requirements:part-01:p1-req-13-9-004:start#statement&noheader&nofooter}} |
+| [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-9-005:start|P1-REQ-13-9-005]] | {{section>dido:99_annexes:annex-d-requirements:part-01:p1-req-13-9-005:start#statement&noheader&nofooter}} |
+| [[dido:99_annexes:annex-d-requirements:part-01:p1-req-13-9-006:start|P1-REQ-13-9-006]] | {{section>dido:99_annexes:annex-d-requirements:part-01:p1-req-13-9-006:start#statement&noheader&nofooter}} |
+----
+<WRAP centeralign>
+© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
+</WRAP>