12.5 Data Plane QoS Expectations

Go To Top

Return to Data Plane Topics

Data Plane Topics should use DDS QoS settings that match the meaning and expected behavior of the data they carry. Phase 0 may use simple QoS profiles, but the team should still document the assumptions that affect delivery, ordering, durability, history, liveliness, and replay.

The team should document Data Plane QoS expectations in the Topic Catalogue and DDS Configuration files. When a QoS setting matters to the demonstration, the implementation should not rely on undocumented DDS defaults.

For Data Plane Topics, the team should consider:

1. Reliability.
2. Durability.
3. History depth.
4. Ordering.
5. Liveliness.
6. Lifespan.
7. Deadline.
8. Ownership.
9. Resource limits.
10. Partitioning or domain separation, where applicable.

Phase 0 should keep QoS choices understandable. The team should not introduce complex QoS behavior unless the demonstration requires it. If a QoS choice affects acceptance Evidence, publisher/subscriber compatibility, or cross-vendor DDS behavior, the team should record the expectation and validation result.