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

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-006 [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-006 [2026/07/18 12:33] (current) – external edit 127.0.0.1
Line 1: Line 1:
 +====== P2-REQ-16-4-006 ======
 +
 +[[dido:99_annexes:annex-d-requirements:part-02:start| Return to Requirements]]
 +
 +===== Statement =====
 +
 +The Logical Architecture / PIM SHALL distinguish [[dido:99_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 artifacts.
 +
 +===== Source =====
 +
 +Part 2, Section 16.4: Logical Communication Requirements.
 +
 +===== Rationale =====
 +
 +Logical Communication Endpoints are architectural concepts that describe platform-independent information exchange. They must remain distinct from technology-specific communication mechanisms to preserve architectural meaning, implementation flexibility, and traceability across multiple Implementation Profiles.
 +
 +===== Applies To =====
 +
 +This requirement applies to the Logical Communication Model, Implementation Profiles, and Deployment Profiles.
 +
 +It applies specifically to:
 +
 +  * Logical Communication Endpoints;
 +  * Communication technology mappings;
 +  * Implementation artifacts; and
 +  * Deployment artifacts.
 +
 +===== Verification =====
 +
 +Verification SHALL confirm that Logical Communication Endpoints remain distinct from technology-specific communication mechanisms.
 +
 +Verification activities should include review checks confirming that:
 +
 +  * Logical Communication Endpoints are not defined as implementation technologies;
 +  * communication technology selections are deferred to Implementation Profiles;
 +  * implementation mappings preserve the meaning of Logical Communication Endpoints; and
 +  * deployment artifacts do not redefine Logical Communication Endpoints.
 +
 +===== Traceability =====
 +
 +This requirement supports traceability between Logical Communication Endpoints and the implementation artifacts that realize them.
 +
 +Related requirement identifiers:
 +
 +  * [[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-4-005]]
 +  * [[dido:99_annexes:annex-d-requirements:part-02:p2-req-16-4-007]]
 +  * [[fxdemo:dido_99_annexes:annex-c-requirements:part-02:p2-req-16-10-007]]
 +
 +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>