Configuration management (CM) is concerned with the policies, processes and tools for managing changing software systems. It is useful as software systems are constantly changing during development and use, it is used as it is easy to lose track of what changes and component versions have been incorporated into each system version. CM is essential for team projects to control changes made by different developers.
There are multiple activities in CM:
Version management
Version management: keeping track of multiple versions of system components and ensuring that changes made to components by different developers do not interfere with each other.
Link to originalSystem building
System building: process of assembling program components, data and libraries, then compiling these to create an executable system.
Link to originalChange management
Change management: keeping track of requests for changes to the software from customers and developers, working out the costs and impact of changes, and deciding the changes that should be implemented.
Link to originalRelease management
Release management: preparing software for external release and keeping track of the system versions that have been released for customer use.
Link to original