| Both sides previous revision Previous revision | |
| fxdemo:01-part:12-relationship-to-the-logical-architecture-pim:12-1-overview [2026/07/11 11:15] – ↷ Links adapted because of a move operation nick_dido | fxdemo:01-part:12-relationship-to-the-logical-architecture-pim:12-1-overview [2026/07/18 12:33] (current) – external edit 127.0.0.1 |
|---|
| The [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_model|Logical Architecture]] / [[dido:99_annexes:annex-b-terms-and-definitions:p:platform_independent_model|PIM]] uses the concepts defined in Part 1 to describe platform-independent relationships, responsibilities, constraints, information flows, and interaction patterns. It does not introduce implementation technologies, deployment mechanisms, product choices, runtime scripts, or [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] procedures. | The [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_model|Logical Architecture]] / [[dido:99_annexes:annex-b-terms-and-definitions:p:platform_independent_model|PIM]] uses the concepts defined in Part 1 to describe platform-independent relationships, responsibilities, constraints, information flows, and interaction patterns. It does not introduce implementation technologies, deployment mechanisms, product choices, runtime scripts, or [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] procedures. |
| |
| Part 2, therefore, acts as the next layer outward from the conceptual architecture. It specialises the conceptual elements without binding them to DDS, IDL, Python, Kubernetes, K3s, Docker, RTI Connext DDS, Crucible, or other implementation-specific mechanisms. | Part 2, therefore, acts as the next layer outward from the conceptual architecture. It specializes the conceptual elements without binding them to DDS, IDL, Python, Kubernetes, K3s, Docker, RTI Connext DDS, Crucible, or other implementation-specific mechanisms. |
| |
| ---- | ---- |