====== P4-REQ-21-9-003 ======

[[dido:99_annexes:annex-d-requirements:part-04:start| Return to Requirements]]

===== Statement =====

Each QoS profile mapping SHALL identify the DDS Topic or Topic family that uses the profile.

===== Source =====

Part 4, Section 21.9: QoS Profile Requirements.

===== Rationale =====

A QoS profile must identify the DDS communication exchanges to which its behavior applies.

Connecting profiles to DDS Topics or Topic families makes communication configuration explicit and allows publishers, subscribers, and reviewers to determine which behavior governs each exchange.

===== Applies To =====

This requirement applies to:

  * QoS profile mappings;
  * DDS Topics and Topic families;
  * publishers;
  * subscribers; and
  * communication configuration.

===== Verification =====

Verification SHALL confirm that each QoS profile mapping identifies the DDS Topic or Topic family that uses the profile.

Verification activities should include review checks confirming that:

  * applicable Topics are identified;
  * Topic families are identified where profiles are shared;
  * publishers and subscribers use the intended profile; and
  * unused or ambiguous profile mappings are not part of the baseline.

===== Traceability =====

This requirement connects the Phase 0 QoS Profile Model to the applicable DDS Topic mappings.

Related requirement identifiers:

  * [[dido:99_annexes:annex-d-requirements:part-04:p4-req-21-9-002]]
  * [[dido:99_annexes:annex-d-requirements:part-04:p4-req-21-9-004]]
  * [[dido:99_annexes:annex-d-requirements:part-04:p4-req-21-5-008]]

Related source section:

  * [[fxdemo:04-part:21-phase-0-implementation-requirements:21-9-qos-profile-requirements:start]]

===== Status =====

Draft

----

<WRAP centeralign>

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

</WRAP>