16.4 Logical Communication Requirements

Go To Logical Requirements

This section identifies the normative requirements established for the Logical Communication Model. The canonical requirement statements are maintained in Annex C: Requirements, Part 2, Section 16.4.

Table 16-3: Logical Communication requirements.

Requirement ID	Statement
P2-REQ-16-4-001	The Logical Architecture / PIM SHALL define Logical Communication Endpoint and Communication Role.
P2-REQ-16-4-002	The Logical Architecture / PIM SHALL define communication roles for Publisher Role, Subscriber Role, Requester Role, Responder Role, Command Producer Role, Command Consumer Role, Event Producer Role, and Event Consumer Role.
P2-REQ-16-4-003	A Logical Communication Endpoint SHALL identify a platform-independent point of information exchange among Logical Nodes.
P2-REQ-16-4-004	A Communication Role SHALL identify how a Logical Node participates in a Logical Communication Endpoint.
P2-REQ-16-4-005	The Logical Architecture / PIM SHALL define logical communication through explicit Logical Communication Endpoints rather than hidden coupling, undocumented dependencies, or implicit control paths.
P2-REQ-16-4-006	The Logical Architecture / PIM SHALL distinguish Logical Communication Endpoints from DDS Topics, REST resources, RPC methods, Protocol Buffers services, message queues, event streams, files, database handoffs, shared-memory locations, network routes, and deployment artifacts.
P2-REQ-16-4-007	The Logical Architecture / PIM SHALL NOT prescribe one communication technology or interaction style.
P2-REQ-16-4-008	The Logical Architecture / PIM SHALL support communication pattern independence by distinguishing logical communication relationships from the implementation mechanisms that realize them.

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