fxdemo:01-part:12-relationship-to-the-logical-architecture-pim:12-4-logical-architecture-remains-platform-independent

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
fxdemo:01-part:12-relationship-to-the-logical-architecture-pim:12-4-logical-architecture-remains-platform-independent [2026/06/29 14:31] – removed - external edit (Unknown date) 127.0.0.1fxdemo:01-part:12-relationship-to-the-logical-architecture-pim:12-4-logical-architecture-remains-platform-independent [2026/07/11 11:15] (current) – ↷ Links adapted because of a move operation nick_dido
Line 1: Line 1:
 +====== 12.4 Logical Architecture Remains Platform Independent ======
 +[[fxdemo:01-part:start | Go to Top ]]
 +
 +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]] remains independent of implementation technologies.
 +
 +Part 2 may identify logical interactions, message flows, roles, responsibilities, state relationships, validation responsibilities, policy interactions, audit relationships, and [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] relationships. It does not bind those logical elements to DDS Topics, IDL structures, QoS profiles, Python processes, container images, Kubernetes objects, Crucible scenarios, or [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] bundles.
 +
 +Those mappings belong to later parts.
 +----
 +
 +<WRAP centeralign>
 +
 +© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 +
 +</WRAP>