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, DDS and 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.
Table 3-6: Phase 0 implementation source material normalized into Part 4.
| 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. |
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.