P4-REQ-21-5-008 [Dido Solutions, Inc Wiki]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== P4-REQ-21-5-008 ======

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

===== Statement =====

Each DDS Topic mapping SHALL identify the QoS profile or QoS profile family used for the topic.

===== Source =====

Part 4, Section 21.5: Communication Endpoint Mapping Requirements.

===== Rationale =====

QoS profiles define the selected Phase 0 communication behavior associated with DDS Topic exchange.

Identifying the applicable profile makes reliability, durability, history, ordering, liveliness, and compatibility expectations explicit and reviewable.

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

This requirement applies to:

  * DDS Topic mappings;
  * QoS profiles;
  * publishers;
  * subscribers; and
  * communication configuration.

===== Verification =====

Verification SHALL confirm that each DDS Topic mapping identifies its applicable QoS profile or profile family.

Verification activities should include review checks confirming that:

  * the applicable QoS profile is identified;
  * publishers and subscribers use compatible profiles;
  * profile selection agrees with the applicable Runtime Plane; and
  * QoS configuration is governed by the Phase 0 baseline.

===== Traceability =====

This requirement connects DDS Topic mappings to the Phase 0 QoS Profile Model and applicable Runtime Plane concerns.

Related requirement identifiers:

  * [[dido:99_annexes:annex-d-requirements:part-04:p4-req-21-5-004]]
  * [[dido:99_annexes:annex-d-requirements:part-04:p4-req-21-5-007]]
  * [[dido:99_annexes:annex-d-requirements:part-04:p4-req-21-3-004]]

Related source section:

  * [[fxdemo:04-part:21-phase-0-implementation-requirements:21-5-communication-endpoint-mapping-requirements:start]]

===== Status =====

Draft

----

<WRAP centeralign>

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

</WRAP>