P4-REQ-21-15-005 [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-15-005 ======

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

===== Statement =====

The Part 5 handoff SHALL identify QoS profile mappings.

===== Source =====

Part 4, Section 21.15: Part 5 Handoff Requirements.

===== Rationale =====

Part 5 requires the selected Phase 0 communication behavior when deploying and exercising DDS participants.

Including QoS profile mappings ensures that Part 5 uses the governed reliability, durability, history, ordering, liveliness, and compatibility expectations defined by Part 4.

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

This requirement applies to:

  * QoS profiles;
  * DDS Topic mappings;
  * publishers and subscribers;
  * Runtime Plane mappings; and
  * QoS configuration artifacts.

===== Verification =====

Verification SHALL confirm that the Part 5 handoff identifies applicable QoS profile mappings.

Verification activities should include review checks confirming that:

  * applicable profiles are identified;
  * associated DDS Topics are identifiable;
  * publisher and subscriber compatibility expectations are available; and
  * configuration sources are identifiable.

===== Traceability =====

This requirement carries the Part 4 QoS Profile Model into the Part 5 execution and deployment context.

Related requirement identifiers:

  * [[dido:99_annexes:annex-d-requirements:part-04:p4-req-21-9-001]]
  * [[dido:99_annexes:annex-d-requirements:part-04:p4-req-21-9-012]]
  * [[dido:99_annexes:annex-d-requirements:part-04:p4-req-21-15-006]]

Related source section:

  * [[fxdemo:04-part:21-phase-0-implementation-requirements:21-15-part-5-handoff-requirements:start]]

===== Status =====

Draft

----

<WRAP centeralign>

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

</WRAP>