P4-REQ-21-9-013

Return to Requirements

QoS profiles SHALL NOT redefine Runtime Planes, FX logical Communication Endpoints, FX logical information structures, or FX logical interaction patterns.

Part 4, Section 21.9: QoS Profile Requirements.

QoS profiles control implementation communication behavior. They do not define the architectural meaning of Runtime Planes, Communication Endpoints, information structures, or interaction patterns.

This constraint preserves separation between the Part 3 FX Demo Logical Profile and the communication behavior selected for the Phase 0 DDS implementation.

This requirement applies to:

• Phase 0 QoS profiles;
• DDS Topic mappings;
• Runtime Plane mappings;
• FX logical Communication Endpoints;
• FX logical information structures; and
• FX logical interaction patterns.

Verification SHALL confirm that QoS profiles do not redefine Part 3 logical architectural elements.

Verification activities should include review checks confirming that:

• Runtime Plane definitions remain governed by Part 3;
• Communication Endpoint definitions remain governed by Part 3;
• logical information structures remain governed by Part 3;
• logical interaction patterns remain governed by Part 3; and
• QoS choices remain identifiable as implementation communication behavior.

This requirement preserves the separation between Part 3 logical architectural meaning and the Phase 0 QoS implementation model.

Related requirement identifiers:

• P4-REQ-21-9-001
• P4-REQ-21-9-012
• P4-REQ-21-7-008
• P4-REQ-21-5-011

Related source section:

• 21.9 QoS Profile Requirements

Draft