| Next revision | Previous revision |
| fxdemo:02-part:16-logical-requirements:16-4-logical-communication-requirements:start [2026/07/03 14:29] – created owen | fxdemo:02-part:16-logical-requirements:16-4-logical-communication-requirements:start [2026/07/11 12:57] (current) – ↷ Links adapted because of a move operation nick_dido |
|---|
| ====== 16.4 Logical Communication Requirements ====== | ====== 16.4 Logical Communication Requirements ====== |
| [[fxdemo:02-part:start | Go To Top ]] | [[fxdemo:02-part:16-logical-requirements:start | Go To Logical Requirements ]] |
| |
| - The Logical Architecture / PIM SHALL define [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:l:logical_communication_endpoint|Logical Communication Endpoint]] and [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:c:communication_role|Communication Role]]. | This section identifies the normative requirements established for the Logical Communication Model. The canonical requirement statements are maintained in [[dido:99_annexes:annex-d-requirements:part-02:start|Annex C: Requirements, Part 2, Section 16.4]]. |
| - The Logical Architecture / PIM SHALL define communication roles for [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:p:publisher_role|Publisher Role]], [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:s:subscriber_role|Subscriber Role]], [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:r:requester_role|Requester Role]], [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:r:responder_role|Responder Role]], [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:c:command_producer_role|Command Producer Role]], [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:c:command_consumer_role|Command Consumer Role]], [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:e:event_producer_role|Event Producer Role]], and [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:e:event_consumer_role|Event Consumer Role]]. | |
| - A [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:l:logical_communication_endpoint|Logical Communication Endpoint]] SHALL identify a platform-independent point of information exchange among [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:l:logical_node|Logical Nodes]]. | <WRAP table-caption> |
| - A [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:c:communication_role|Communication Role]] SHALL identify how a [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:l:logical_node|Logical Node]] participates in a [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:l:logical_communication_endpoint|Logical Communication Endpoint]]. | **Table 16-3:** Logical Communication requirements. |
| - The Logical Architecture / PIM SHALL define logical communication through explicit [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:l:logical_communication_endpoint|Logical Communication Endpoints]] rather than hidden coupling, undocumented dependencies, or implicit control paths. | </WRAP> |
| - The Logical Architecture / PIM SHALL distinguish [[fxdemo:99_part_annexes:annex-b-terms-and-definitions:l:logical_communication_endpoint|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. | |
| - The Logical Architecture / PIM SHALL NOT prescribe one communication technology or interaction style. | ^ Requirement ID ^ Statement ^ |
| - The Logical Architecture / PIM SHALL support communication pattern independence by distinguishing logical communication relationships from the implementation mechanisms that realise them. | | [[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-4-001|P2-REQ-16-4-001]] | {{section>dido:99_annexes:annex-d-requirements:part-02:p2-req-16-4-001#statement&noheader&nofooter}} | |
| | | [[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-4-002|P2-REQ-16-4-002]] | {{section>dido:99_annexes:annex-d-requirements:part-02:p2-req-16-4-002#statement&noheader&nofooter}} | |
| | | [[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-4-003|P2-REQ-16-4-003]] | {{section>dido:99_annexes:annex-d-requirements:part-02:p2-req-16-4-003#statement&noheader&nofooter}} | |
| | | [[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-4-004|P2-REQ-16-4-004]] | {{section>dido:99_annexes:annex-d-requirements:part-02:p2-req-16-4-004#statement&noheader&nofooter}} | |
| | | [[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-4-005|P2-REQ-16-4-005]] | {{section>dido:99_annexes:annex-d-requirements:part-02:p2-req-16-4-005#statement&noheader&nofooter}} | |
| | | [[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-4-006|P2-REQ-16-4-006]] | {{section>dido:99_annexes:annex-d-requirements:part-02:p2-req-16-4-006#statement&noheader&nofooter}} | |
| | | [[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-4-007|P2-REQ-16-4-007]] | {{section>dido:99_annexes:annex-d-requirements:part-02:p2-req-16-4-007#statement&noheader&nofooter}} | |
| | | [[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-4-008|P2-REQ-16-4-008]] | {{section>dido:99_annexes:annex-d-requirements:part-02:p2-req-16-4-008#statement&noheader&nofooter}} | |
| |
| ---- | ---- |