17.5 Implementation Change Control [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.

====== 17.5 Implementation Change Control ======

[[fxdemo:04-part:17-phase-0-implementation-governance:start | Go To Phase 0 Implementation Governance ]]

Phase 0 implementation change control governs changes to implementation artifacts, generated artifacts, configuration artifacts, mappings, scripts, repository structure, and Developer Handbook rules.

A change must identify:

  - Artifact being changed
  - Reason for the change
  - Affected FX logical element or implementation concern
  - Affected DDS Topic, IDL structure, generated type, QoS profile, script, or configuration artifact
  - Compatibility impact
  - [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] impact
  - Developer Handbook impact
  - Part 5 deployment, testability, operation, observation, or evidence impact where applicable
  - Review outcome

Implementation change control prevents local implementation changes from silently altering the Phase 0 baseline. It also supports later phase profiles by preserving a history of implementation decisions.

----

<WRAP centeralign>

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

</WRAP>