18.7 Runtime Plane Implementation Traceability [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.

====== 18.7 Runtime Plane Implementation Traceability ======

[[fxdemo:04-part:18-phase-0-implementation-traceability-model:start | Go To Phase 0 Implementation Traceability Model ]]

[[dido:99_annexes:annex-b-terms-and-definitions:r:runtime_plane|Runtime Plane]] implementation [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|traceability]] relates FX Runtime Plane classifications to Phase 0 implementation artifacts and conventions.

A Runtime Plane implementation trace must identify:

  - FX Runtime Plane being realized
  - DDS Topic family or naming convention used for that plane
  - QoS profile family used for that plane
  - Implementation participants supporting that plane
  - IDL structures and generated types exchanged through that plane
  - Logging categories or fields associated with that plane
  - Exception-handling behavior associated with that plane
  - Audit/provenance expectations associated with that plane
  - 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.

----

<WRAP centeralign>

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

</WRAP>