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/07/01 14:41] – 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 [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:l:logical_model|Logical Architecture]] / [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:p:platform_independent_model|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 [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:l:logical_model|Logical Architecture]] / [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:p:platform_independent_model|PIM]] SHALL preserve the definitions of conceptual elements defined in this part.
-  - The [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:l:logical_model|Logical Architecture]] / [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:p:platform_independent_model|PIM]] SHALL NOT redefine [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:n:node|Node]], [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:n:node_identity|Node Identity]], [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:n:node_role|Node Role]], [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:r:runtime_plane|Runtime Plane]], [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:c:communication_endpoint|Communication Endpoint]], [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:d:data_structure_definition|Data Structure Definition]], [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:d:data_structure_instance|Data Structure Instance]], [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]], [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]], [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:e:ecosphere|Ecosphere]], [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:e:ecosystem|Ecosystem]], [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:d:domain|Domain]], or [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:c:classification_path|Classification Path]].
+<WRAP table-caption>
-  - The [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:l:logical_model|Logical Architecture]] / [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:p:platform_independent_model|PIM]] SHALL remain platform independent.
+**Table 13.9-1:** Part 1 relationship to Logical Architecture / PIM requirements.
-  - The [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:l:logical_model|Logical Architecture]] / [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:p:platform_independent_model|PIM]] SHALL NOT bind logical elements to DDS, IDL, Python, Kubernetes, K3s, Docker, RTI Connext DDS, Crucible, or other implementation-specific mechanisms.
+</WRAP>
-  - The [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:l:logical_model|Logical Architecture]] / [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:p:platform_independent_model|PIM]] SHALL provide [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] from logical elements to the conceptual elements they specialise, refine, constrain, or relate.
+^ 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>