====== P2-REQ-16-4-005 ======

[[dido:99_annexes:annex-d-requirements:part-02:start| Return to Requirements]]

===== Statement =====

The Logical Architecture / PIM SHALL define logical communication through explicit [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_communication_endpoint|Logical Communication Endpoints]] rather than hidden coupling, undocumented dependencies, or implicit control paths.

===== Source =====

Part 2, Section 16.4: Logical Communication Requirements.

===== Rationale =====

Explicit Logical Communication Endpoints make communication relationships visible, reviewable, and traceable. Avoiding hidden coupling and undocumented dependencies preserves architectural clarity and enables consistent governance, interoperability, and implementation mapping.

===== Applies To =====

This requirement applies to the Logical Communication Model and all Logical Interaction Patterns.

It applies specifically to:

  * Logical Communication Endpoints;
  * Logical Nodes;
  * Logical Interactions; and
  * Domain Logical Profiles.

===== Verification =====

Verification SHALL confirm that logical communication is defined through explicit Logical Communication Endpoints.

Verification activities should include review checks confirming that:

  * communication paths are explicitly identified;
  * undocumented dependencies are absent;
  * hidden coupling is avoided; and
  * logical interactions occur through defined Logical Communication Endpoints.

===== Traceability =====

This requirement supports traceability between Logical Communication Endpoints, Logical Nodes, and Logical Interaction Patterns.

Related requirement identifiers:

  * [[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-4-003]]
  * [[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-4-004]]
  * [[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-7-001]]

Related source section:

  * [[fxdemo:02-part:16-logical-requirements:16-4-logical-communication-requirements:start]]

===== Status =====

Draft

----

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