18.7 Runtime Plane Implementation Traceability

Go To Phase 0 Implementation Traceability Model

Runtime Plane implementation traceability relates FX Runtime Plane classifications to Phase 0 implementation artifacts and conventions.

A Runtime Plane implementation trace must identify:

1. FX Runtime Plane being realized
2. DDS Topic family or naming convention used for that plane
3. QoS profile family used for that plane
4. Implementation participants supporting that plane
5. IDL structures and generated types exchanged through that plane
6. Logging categories or fields associated with that plane
7. Exception-handling behavior associated with that plane
8. Audit/provenance expectations associated with that plane
9. Part 5 deployment, observation, or evidence planning concerns supported by that plane

Runtime Plane implementation traceability preserves separation of concerns in implementation form. It prevents a shared DDS mechanism, logging mechanism, or repository grouping from collapsing Control, Data, Health and Observability, Policy and Release, and Audit and Provenance concerns into one undifferentiated implementation layer.