Differences

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

--- fxdemo:01-part:05-conceptual-architecture-principles:05-1-separation-of-concerns [2026/07/11 11:15] – ↷ Links adapted because of a move operation nick_dido
+++ fxdemo:01-part:05-conceptual-architecture-principles:05-1-separation-of-concerns [2026/07/18 12:33] (current) – external edit 127.0.0.1
@@ Line 2: / Line 2: @@
 [[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 specialisation, implementation mapping, deployment mechanics, testability, and [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]].
+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 realise 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]].
+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.