P2-REQ-16-4-006

Return to Requirements

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.

Part 2, Section 16.4: Logical Communication Requirements.

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.

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 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.

This requirement supports traceability between Logical Communication Endpoints and the implementation artifacts that realize them.

Related requirement identifiers:

• P2-REQ-16-4-005
• P2-REQ-16-4-007
• p2-req-16-10-007

Related source section:

• 16.4 Logical Communication Requirements

Draft