P3-REQ-17-5-007

Return to Requirements

The FX Demo Logical Profile SHALL NOT prescribe one communication technology or interaction style.

Part 3, Section 17.5: FX Logical Communication Requirements.

The FX Demo Logical Profile defines a platform-independent logical architecture and therefore must not mandate a specific communication technology or interaction style. Different deployments may realize the same logical Communication Endpoint using technologies such as DDS, REST, RPC, messaging systems, event streaming platforms, or future communication mechanisms while preserving the same architectural meaning.

Avoiding technology prescription maintains portability, implementation flexibility, interoperability, and long-term architectural sustainability.

This requirement applies to the FX Demo Logical Profile and to every FX logical Communication Endpoint defined within the profile.

It applies specifically to:

• logical communication architecture;
• Implementation Profile development;
• technology selection;
• deployment architecture; and
• architectural governance.

Verification SHALL confirm that the FX Demo Logical Profile does not require or mandate any specific communication technology or interaction style.

Verification activities should include review checks confirming that:

• no communication technology is prescribed;
• no interaction style is mandated;
• logical Communication Endpoints remain implementation independent; and
• multiple Implementation Profiles could realize the logical communication architecture without violating the specification.

This requirement preserves the platform-independent principles established by Parts 1 and 2 while enabling multiple technology-specific Implementation Profiles to realize the same logical communication architecture.

Related requirement identifiers:

• P3-REQ-17-5-001
• P3-REQ-17-5-005
• P3-REQ-17-5-006

Related source section:

• 17.5 FX Logical Communication Requirements

Draft