P4-REQ-21-9-012

Each QoS profile mapping SHALL preserve traceability to the applicable FX logical Communication Endpoint and Runtime Plane.

Part 4, Section 21.9: QoS Profile Requirements.

QoS profiles implement communication behavior for logical exchanges and must remain connected to both the Communication Endpoint and Runtime Plane purpose that justify their selection.

Preserving these relationships allows reviewers to determine why a profile exists and whether its communication behavior remains consistent with the FX Demo Logical Profile.

This requirement applies to:

  • QoS profile mappings;
  • FX logical Communication Endpoints;
  • Runtime Plane mappings;
  • DDS Topic mappings; and
  • configuration artifacts.

Verification SHALL confirm that each QoS profile mapping preserves traceability to the applicable FX logical Communication Endpoint and Runtime Plane.

Verification activities should include review checks confirming that:

  • the applicable Communication Endpoint is identifiable;
  • the applicable Runtime Plane is identifiable;
  • QoS behavior is consistent with both relationships; and
  • mapping changes preserve or explicitly update traceability.

This requirement establishes backward traceability from Phase 0 QoS profiles to their applicable Part 3 Communication Endpoint and Runtime Plane sources.

Related requirement identifiers:

Related source section:

Draft


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

  • dido/99_annexes/annex-d-requirements/part-04/p4-req-21-9-012.txt
  • Last modified: 2026/08/07 14:01
  • by owen