====== P4-REQ-21-9-004 ======

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

===== Statement =====

Each QoS profile mapping SHALL identify the communication purpose of the profile.

===== Source =====

Part 4, Section 21.9: QoS Profile Requirements.

===== Rationale =====

The communication purpose explains why a QoS profile exists and which implementation concern its behavior supports.

Explicit purpose helps reviewers determine whether reliability, durability, ordering, history, liveliness, and other settings are appropriate for the intended exchange.

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

This requirement applies to:

  * QoS profile mappings;
  * DDS Topic mappings;
  * Runtime Plane mappings; and
  * communication configuration.

===== Verification =====

Verification SHALL confirm that each QoS profile mapping identifies its communication purpose.

Verification activities should include review checks confirming that:

  * the intended communication purpose is stated;
  * the purpose agrees with the applicable Runtime Plane;
  * the purpose agrees with the DDS Topic mapping; and
  * selected QoS behavior supports the stated purpose.

===== Traceability =====

This requirement connects each Phase 0 QoS profile to the communication concern it is intended to support.

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-003]]
  * [[dido:99_annexes:annex-d-requirements:part-04:p4-req-21-9-005]]

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>