4.1 Separation of Concerns [Dido Solutions, Inc Wiki]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.

====== 4.1 Separation of Concerns ======
[[fxdemo:01-part:start | Go to Top ]]

The architecture separates conceptual meaning, logical [[dido:99_annexes:annex-b-terms-and-definitions:s:structure|Structure]], domain specialization, implementation mapping, deployment mechanics, testability, and [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]].

This separation allows each layer to evolve without redefining the layers inside it. For example, a later implementation profile may realize a [[dido:99_annexes:annex-b-terms-and-definitions:c:communication_endpoint|Communication Endpoint]] as a DDS Topic, but that mapping does not change the conceptual meaning of [[dido:99_annexes:annex-b-terms-and-definitions:c:communication_endpoint|Communication Endpoint]].

Section 9 defines the Separation of Concerns Model used to apply this principle.

----

<WRAP centeralign>

© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.

</WRAP>