16.4 Logical Communication Requirements

Go To Top

1. The Logical Architecture / PIM SHALL define Logical Communication Endpoint and Communication Role.
2. 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.
3. A Logical Communication Endpoint SHALL identify a platform-independent point of information exchange among Logical Nodes.
4. A Communication Role SHALL identify how a Logical Node participates in a Logical Communication Endpoint.
5. The Logical Architecture / PIM SHALL define logical communication through explicit Logical Communication Endpoints rather than hidden coupling, undocumented dependencies, or implicit control paths.
6. 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 artefacts.
7. The Logical Architecture / PIM SHALL NOT prescribe one communication technology or interaction style.
8. The Logical Architecture / PIM SHALL support communication pattern independence by distinguishing logical communication relationships from the implementation mechanisms that realise them.