P4-REQ-21-5-007
Statement
Each DDS Topic mapping SHALL identify the Runtime Plane or Runtime Planes associated with the exchange.
Source
Part 4, Section 21.5: Communication Endpoint Mapping Requirements.
Rationale
Runtime Plane classification preserves separation of concerns in Phase 0 communication mappings.
Recording the applicable Runtime Plane allows communication behavior, QoS, logging, exception handling, and later observation to remain aligned with the logical purpose of the exchange.
Applies To
This requirement applies to:
-
DDS Topic mappings;
-
Runtime Plane mappings;
-
QoS profiles;
-
implementation participants; and
-
applicable communication conventions.
Verification
Verification SHALL confirm that each DDS Topic mapping identifies the Runtime Plane or Runtime Planes associated with the exchange.
Verification activities should include review checks confirming that:
-
applicable Runtime Planes are explicitly identified;
-
mappings agree with Part 3 Runtime Plane classifications;
-
multi-plane associations are recorded where applicable; and
-
communication implementation does not collapse distinct Runtime Plane concerns.
Traceability
This requirement connects each DDS Topic mapping to the Runtime Plane classification of its corresponding FX logical exchange.
Related requirement identifiers:
Related source section:
Status
Draft
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.