The FX Demo Logical Profile SHALL distinguish FX 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.
Part 3, Section 17.5: FX Logical Communication Requirements.
FX logical Communication Endpoints are logical architectural constructs that describe communication responsibilities independently of implementation technologies. Technologies such as DDS Topics, REST resources, RPC methods, Protocol Buffers services, message queues, event streams, and deployment artefacts are implementation mechanisms that may realize a logical Communication Endpoint but do not define its architectural meaning.
Maintaining this distinction preserves platform independence and allows multiple Implementation Profiles to realize the same logical communication architecture using different technologies.
This requirement applies to every FX logical Communication Endpoint defined within the FX Demo Logical Profile.
It applies specifically to:
Verification SHALL confirm that logical Communication Endpoints are defined independently of implementation technologies.
Verification activities should include review checks confirming that:
This requirement preserves the separation between conceptual communication architecture, logical communication architecture, and implementation-specific communication mechanisms established throughout the layered architecture.
Related requirement identifiers:
Related source section:
Draft
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.