Configuration management is a process for controlling cordinating and tracking all the project related documents.(requriemnts code documents tesplans testcases etc)
Configuration management (CM) is the processes of controlling coordinate and tracking the Standards and procedures for managing changes in an evolving software product.
Configuration Testing is the process of checking the operation of the software being tested on various types of hardware
The process Configuration Management falls in the 2nd level (Repeatable) in CMM.
Basic purpose is to keep the central repository and maintain the historic data. Added features like are text file (code) comparison labeling file locking etc.
VSS StarTeam PVCS CVS ClearCase ....etc are the widely used Configuration Management tools.
Configuration management covers the processes used to control coordinate and track: code requirements documentation problems change requests designs tools/compilers/libraries/patches changes made to them and who makes the changes.
Configuration management is a critical process responsible for identifying controlling and tracking all versions of hardware software documentation processes procedures and all other inanimate components of the information technology (IT) organization. The goal of configuration management is to ensure that only authorized components referred to as configuration items (CIs) are used in the IT environment and that all changes to CIs are recorded and tracked throughout the component’s life cycle. Vista VSS CVS ClearCase ....etc are the widely used Configuration Management tools.
It is a process in which they mainly perform 2 tasks. Change control Version control
Change control: It is a process of updating the selected documents whenever some changes made to the application inorder to the application & related documents in the same level with each other.
Version control: It is process of maintaining the naming conventions and version numbers.
