7.9 Technology Selection Boundaries [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.

====== 7.9 Technology Selection Boundaries ======

[[fxdemo:04-part:07-phase-0-technology-selection-and-implementation-context:start | Go To Phase 0 Technology Selection and Implementation Context ]]

The Phase 0 technology selections apply only to the Phase 0 implementation baseline.

[[dido:99_annexes:annex-b-terms-and-definitions:d:dds|DDS]], [[dido:99_annexes:annex-b-terms-and-definitions:i:idl|IDL]], Quality of Service (QoS) profiles, generated types, Python, scripts, and the repository structure provide the selected Phase 0 implementation context. They do not define the permanent implementation architecture for all subsequent phases, nor do they redefine the conceptual, logical, or FX Demo Logical Profile layers.

A later development phase may extend, refine, supersede, or replace one or more Phase 0 technology selections. Any later profile must preserve [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|traceability]] to the applicable conceptual, logical, FX logical, implementation, and Developer Handbook artifacts.

Phase 0 technology selections also remain separate from deployment and [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|evidence]]. Part 4 identifies the implementation artifacts and mappings. Part 5 defines the deployment, testability, operation, observation, and evidence approach for those artifacts.

----

<WRAP centeralign>

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

</WRAP>