====== 18.10 Implementation Traceability Summary ====== [[fxdemo:04-part:18-phase-0-implementation-traceability-model:start | Go To Phase 0 Implementation Traceability Model ]] The Phase 0 Implementation [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] Model preserves the connection between FX logical architecture and Phase 0 implementation artifacts. **Table 18-3: Summary of Phase 0 implementation traceability relationships** ^ Traceability relationship ^ Connects ^ Supports ^ | Part 3 FX logical element to Part 4 implementation artifact | FX logical elements to implementation artifacts | Forward review from logical design to implementation realization | | Implementation artifact to Part 3 FX logical element | Implementation artifacts to FX logical sources or implementation concerns | Backward review from implementation artifact to architectural justification | | [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Node]] implementation traceability | FX logical Nodes and Node Roles to implementation participants and modules | Responsibility review and implementation mapping | | Topic implementation traceability | FX logical Communication Endpoints to DDS Topics | Communication mapping and endpoint review | | IDL and generated type traceability | FX logical information structures to IDL structures and generated types | Data representation review and generation repeatability | | Runtime Plane implementation traceability | FX Runtime Planes to DDS topic families, QoS profiles, logging categories, and implementation conventions | Runtime Plane discipline and separation of concerns | | Script and repository traceability | Scripts and repository locations to implementation concerns | Workflow review, automation control, and repository governance | | Developer Handbook traceability | Handbook rules to implementation concerns and Part 4 requirements | Developer discipline, review consistency, and baseline control | The implementation traceability relationships in Table 18-3 prepare Part 5 to deploy, test, observe, operate, and evidence the Phase 0 implementation artifacts while preserving traceability back to Parts 1, 2, and 3. ---- © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.