17.9 Implementation Governance Summary [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.9 Implementation Governance Summary ======

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

The Phase 0 Implementation Governance Model controls how implementation artifacts become part of the Phase 0 implementation baseline and remain [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|traceable]] to the FX Demo Logical Profile.

**Table 17-1: Summary of Phase 0 implementation governance concerns**

^ Governance concern ^ Primary purpose ^
| Implementation ownership | Identifies responsibility for governed Phase 0 implementation artifacts. |
| Implementation versioning | Identifies versions of implementation artifacts, generated artifacts, configuration, mappings, scripts, and handbook rules. |
| Implementation compatibility | Confirms that implementation artifacts work together without loss of meaning, traceability, communication compatibility, generated-type compatibility, QoS compatibility, or reviewability. |
| Implementation change control | Governs changes to implementation artifacts, mappings, configuration, scripts, repository structure, generated artifacts, and handbook rules. |
| Generated artifact governance | Controls generation, regeneration, review, traceability, and manual-editing rules for generated artifacts. |
| Repository governance | Controls baseline artifact locations, non-baseline material, workflow, cleanup, and review. |
| Developer Handbook governance | Controls approval, change, application, and review of handbook rules. |

Implementation governance keeps Phase 0 from becoming uncontrolled prototype code. It supports disciplined implementation while preserving traceability to Parts 1, 2, and 3.

----

<WRAP centeralign>

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

</WRAP>