Configuration management (CM) is the detailed http://www.onestoptesting.com/configuration-management/what-is-cm.asp - recording and updating of information that describes an enterprise's computer systems and networks, including all hardware and http://www.onestoptesting.com/configuration-management/what-is-cm.asp - software components. Such information typically includes the versions and updates that have been applied to installed software packages and the locations and network addresses of hardware devices. Special configuration management software is available.

When a system needs hardware or software upgrade, a computer technician can accesses the configuration management program and database to see what is currently installed. The technician can then make a more informed decision about the upgrade needed.

An advantage of a configuration management application is that the entire collection of systems can be reviewed to make sure any changes made to one system do not adversely affect any of the other systems.

Configuration management is also used in software development, where it is called Unified Configuration Management (UCM). Using UCM, developers can keep track of the source code, documentation, problems, changes requested, and changes made.

Software CM is a discipline for controlling the evolution of software systems.

1. Identification: an identification scheme is needed to reflect the structure of the product. This involves identifying the structure and kinds of components, making them unique and accessible in some form by giving each component a name, version identification, and configuration identification.
2. Control: controlling the release of a product and changes to it throughout the lifecycle by having controls in place that ensure consistent software via the creation of a baseline product.
3. Status Accounting: http://www.onestoptesting.com/configuration-management/meaning.asp - recording and reporting the status of components and change requests, and gathering vital statistics about components in the product.
4. Audit and review: validating the completeness of a product and maintaining consistency among the components by ensuring that components are in an appropriate state throughout the entire project life cycle and that the product is a well-defined collection of components.