17.5 Implementation Change Control

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:

1. Artifact being changed
2. Reason for the change
3. Affected FX logical element or implementation concern
4. Affected DDS Topic, IDL structure, generated type, QoS profile, script, or configuration artifact
5. Compatibility impact
6. Traceability impact
7. Developer Handbook impact
8. Part 5 deployment, testability, operation, observation, or evidence impact where applicable
9. 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.