配置管理的本质就是对配置的控制。这是建立控制规程的最初前提，后来在DoD-D-5010.19（1969）中正式化为一项声明，该声明将控制定义为:“正式建立配置标识后，对配置项的配置进行系统评估、协调、批准或不批准，并实施所有批准的变更。”这个定义没有说明配置更改控制任务的范围和规模，或者配置更改的理由。 本公告旨在描述结构化编程环境中的软件变更控制过程。本公告描述了:控制过程固有的或与之相关的问题、控制过程、由软件生命周期定义的控制环境、与每个生命周期阶段相关的工具、表格和程序，以及为实现通信自由流动而制定的方法、配置控制委员会的作用，最后，从开发阶段完成到运行和维护阶段的过渡过程。

The very nature of configuration management is the control of the configuration. This was the initial premise under which the control discipline was established and, later, formalized in DoD-D-5010.19 (1969) into a statement which defined control as: "The systematic evaluation, coordination, approval or disapproval, and implementation of all approved changes in the configuration of a configuration item after formal establishment of its configuration identification."What this definition does not impart is the scope and magnitude of the configuration change control task, or the rationale for configuration changes. The purpose of this bulletin is to describe the software change control process in the context of a structured programming environment. The bulletin provides a description of:Problems inherent in or to the control process,The control processThe control environment as defined by the software life cycle,The tools, forms, and procedures associated with each life cycle phase and the methodology instituted to attain a free flow of communication,The role of the Configuration Control Board, andFinally, the transition process from completion of the development phases to the Operational and Maintenance phase.