18.3 Implementation Artifact to Part 3 FX Logical Element [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.3 Implementation Artifact to Part 3 FX Logical Element ======

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

Implementation artifact to Part 3 FX logical element [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|traceability]] connects a Phase 0 implementation artifact back to the FX logical element or implementation concern that justifies it.

This relationship supports backward review. A reviewer can start with an implementation file, IDL structure, generated type, DDS Topic, QoS profile, configuration file, script, repository location, or handbook rule and identify the FX logical element, implementation mapping, or implementation concern it realizes or supports.

**Table 18-2: Backward traceability from Part 4 implementation artifacts to Part 3 FX logical elements**

^ Part 4 implementation artifact ^ Part 3 FX logical source or implementation concern ^
| Implementation [[dido:99_annexes:annex-b-terms-and-definitions:n:node|node]] module | FX logical Node or FX logical Node Role |
| Process entry point | FX logical Node, FX logical Node Role, or execution concern |
| Supporting module | FX logical Node Role, Runtime Plane concern, logging concern, exception-handling concern, traceability concern, or shared implementation concern |
| DDS Topic | FX logical Communication Endpoint |
| IDL structure | FX logical information structure |
| Generated type | IDL structure and FX logical information structure |
| QoS profile | FX Runtime Plane and FX logical Communication Endpoint |
| Configuration file | Implementation participant, DDS Topic, QoS profile, Runtime Plane, or repository concern |
| Script | Build, generation, execution, startup, shutdown, cleanup, or workflow concern |
| Repository directory | Artifact category, implementation mapping, generation concern, documentation concern, or traceability concern |
| File header | Artifact identity, purpose, logical source, implementation concern, modification rule, and review context |
| Generated-file header | Source definition, generator, generation context, regeneration rule, manual-editing rule, and FX logical information structure |
| Developer Handbook rule | Implementation discipline concern governed by Part 4 |
| Review checklist | Acceptance, conformance, traceability, and baseline governance concern |

----

<WRAP centeralign>

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

</WRAP>