National Consensus Standard for Configuration Management

The configuration change management function includes control of both changes and variances to a product using a systematic, measurable change process regardless of the type of product or phase of its life cycle.. The configuration change management process includes:
identifying the need for a change;
defining the change;
documenting change impact;
evaluating and coordinating the proposed change (including approval/disapproval);
incorporating the approved change in the product and its related product configuration information;
verifying change incorporation and continued consistency with the product configuration information; and
identifying, documenting, approving, and implementing variances from baselined product requirements.
Configuration change management is the function for the control of changes and variances to a product using a systematic, measurable change process.
The purposes of configuration change management are to ensure that:
configuration baselines are maintained and controlled;
product and product configuration information are kept consistent;
change information is communicated in an orderly manner;
cost, savings, and alternative change trade-offs are evaluated;
change decisions are based on knowledge of complete change impact;
changes are limited to those which are necessary or offer significant benefit;
ustomer interests are considered;
product interfaces are controlled;
variances are documented and controlled; and
products continue to be supportable after change.
The configuration change management process model shown in Figure 4 is valid for either enterprise configuration change management or management of changes to products under customer control. The configuration change management process addresses permanent changes (proposed in the Request For Change) to provide a new, approved product...