7.12 Communication Direction and Coupling [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.

====== 7.12 Communication Direction and Coupling ======
[[fxdemo:02-part:start | Go To Top ]]

Communication Direction specifies the logical flow of information between [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_node|Logical Nodes]] and [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_communication_endpoint|Logical Communication Endpoints]].

The Logical Architecture supports one-way exchange, two-way exchange, request/response exchange, command/acknowledgement exchange, event production and consumption, and other directed exchange patterns. Communication Direction describes the logical flow of information, not the physical network route or protocol behavior.

Logical coupling describes the degree to which a [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_node|Logical Node]] depends on another [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_node|Logical Node]], endpoint, information structure, timing expectation, or response expectation. The Logical Communication Model favours explicit coupling over hidden coupling. A logical interaction identifies the dependency so reviewers can assess governance, [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]], resilience, [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_compatibility|Compatibility]], and [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] expectations.

----

<WRAP centeralign>
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
</WRAP>