dido:99_annexes:annex-d-requirements:part-02:p2-req-16-4-001

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
dido:99_annexes:annex-d-requirements:part-02:p2-req-16-4-001 [2026/07/11 12:57] – removed - external edit (Unknown date) 127.0.0.1dido:99_annexes:annex-d-requirements:part-02:p2-req-16-4-001 [2026/07/18 12:33] (current) – external edit 127.0.0.1
Line 1: Line 1:
 +====== P2-REQ-16-4-001 ======
  
 +[[dido:99_annexes:annex-d-requirements:part-02:start| Return to Requirements]]
 +
 +===== Statement =====
 +
 +The Logical Architecture / PIM SHALL define [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_communication_endpoint|Logical Communication Endpoint]] and [[dido:99_annexes:annex-b-terms-and-definitions:c:communication_role|Communication Role]].
 +
 +===== Source =====
 +
 +Part 2, Section 16.4: Logical Communication Requirements.
 +
 +===== Rationale =====
 +
 +The Logical Communication Model establishes the platform-independent means by which Logical Nodes exchange information. Defining both Logical Communication Endpoints and Communication Roles provides a consistent foundation for modeling interactions while remaining independent of communication technologies, implementation mechanisms, and deployment environments.
 +
 +Without these concepts, logical communication would become dependent on implementation-specific interfaces, reducing interoperability, architectural consistency, and traceability.
 +
 +===== Applies To =====
 +
 +This requirement applies to the definition, review, maintenance, interpretation, and specialization of the Logical Communication Model.
 +
 +It applies specifically to:
 +
 +  * Logical Communication Endpoints;
 +  * Communication Roles;
 +  * Logical interaction modeling; and
 +  * Domain Logical Profiles.
 +
 +===== Verification =====
 +
 +Verification SHALL confirm that the Logical Architecture / PIM defines both Logical Communication Endpoints and Communication Roles.
 +
 +Verification activities should include review checks confirming that:
 +
 +  * Logical Communication Endpoints are explicitly defined;
 +  * Communication Roles are explicitly defined;
 +  * both concepts remain platform independent; and
 +  * the definitions support logical communication throughout the architecture.
 +
 +===== Traceability =====
 +
 +This requirement supports traceability from Logical Nodes to the Logical Communication Model and its interaction patterns.
 +
 +Related requirement identifiers:
 +
 +  * [[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-3-007]]
 +  * [[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-4-002]]
 +  * [[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]]
 +
 +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>