fxdemo:01-part:05-conceptual-architecture-principles:05-1-separation-of-concerns

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:05-conceptual-architecture-principles:05-1-separation-of-concerns [2026/06/25 14:39] – removed - external edit (Unknown date) 127.0.0.1fxdemo:01-part:05-conceptual-architecture-principles:05-1-separation-of-concerns [2026/07/18 12:33] (current) – external edit 127.0.0.1
Line 1: Line 1:
 +====== 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>
 +