3.6 Traceability to Phase 0 Implementation Source Material [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.
====== 3.6 Traceability to Phase 0 Implementation Source Material ======

[[fxdemo:04-part:03-traceability-to-parent-and-source-architectures:start | Go To Traceability to Parent and Source Architectures ]]

Phase 0 implementation source material provides the selected implementation context for this part. That source material includes prior FX Demo implementation planning, [[dido:99_annexes:annex-b-terms-and-definitions:d:dds|DDS]] and [[dido:99_annexes:annex-b-terms-and-definitions:i:idl|IDL]] mapping decisions, Quality of Service (QoS) profile decisions, generated-type expectations, Node skeleton planning, script planning, repository layout planning, and implementation conventions.

This part normalizes that source material into an implementation profile. It separates architecture-level implementation mappings from developer instructions, deployment procedures, runtime evidence, and operational test results.

<WRAP table-caption>
**Table 3-6:** Phase 0 implementation source material normalized into Part 4.
</WRAP>

^ Phase 0 source material ^ Part 4 treatment ^
| DDS communication decisions | Normalized into communication technology selection and endpoint-to-topic mapping. |
| IDL structure decisions | Normalized into information-structure-to-IDL mapping. |
| QoS profile decisions | Normalized into the Phase 0 QoS Profile Model. |
| Generated type decisions | Normalized into generated artifact mapping and generation conventions. |
| Node skeleton planning | Normalized into implementation Node and implementation participant mapping. |
| Script planning | Normalized into the script and execution model. |
| Repository layout planning | Normalized into the Phase 0 Repository and Build Artifact Model. |
| Logging and exception-handling concerns | Normalized into implementation conventions and Developer Handbook requirements. |
| Coding style concerns | Defers to the Phase 0 Developer Handbook, with architectural requirements identified in this part. |
| Deployment and evidence concerns | Deferred to Part 5. |

----

<WRAP centeralign>

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

</WRAP>