P2-REQ-16-4-006

Return to Requirements

Statement

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.

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 artefacts; andDeployment artefacts.

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; anddeployment artefacts do not redefine Logical Communication Endpoints.

Traceability

This requirement supports traceability between Logical Communication Endpoints and the implementation artefacts that realise them.

Related requirement identifiers:

Related source section:

Status

Draft

© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.