Configuration Management

Configuration Management (CM):

To understand configuration management, we will first look at the bookish meaning of Configuration.
What is configuration?
Configuration means the way a system is arranged. The arrangement of parts or elements in a particular form or combination.
Once configuration is clear, we can try to know what the management of the configuration is. In very simple words the purpose of CM is to maintain software integrity throughout the software development lifecycle and can also be defined as the best solution to handling changes in software projects.
Configuration management includes 4 procedures:
1.       Configuration Identification
2.       Configuration control
3.       Configuration status accounting
4.       Configuration audits
We will now see each of the procedures.
Configuration identification: In this process we identify the attributes that define every aspect of a configuration item. The attributes are then recorded in the configuration documentation and baselined. These ate later tracked  through design, development , testing and final delivery.
What is configuration item?
A product that has end user purpose can be termed as configuration item. The product can be any hardware or software.
Configuration control: This is the process of controlling changes to the system’s design, hardware, firmware, software and documentation. It also includes the approval stages of the change and re-baseline them
Configuration status accounting: This is the process of recording and reporting  configuration item descriptions from the baseline and if any problems found the approved modifications can be quickly determined.
Configuration audits: The audit ensures that functional and performance attributes of a configuration item are achieved.
The benefits of a SCM are being able to perform functions like
1. Root cause analysis
2. Impact analysis
3. Change management and

4. Current state assessment for the future state strategy development.

No comments:

Post a Comment