Software Configuration Management (SCM) can be define as a process of defining and implementing a standard configuration. which results in easier setup and maintenance and more efficient and reliable backups and also maximizes productivity. SCM uses to track and manage the emerging product and its versions. SCM ensures that all people involved in the software process know what is being designed, developed, bunt, tested, and delivered. Through SCM, the design requirements can be trace to the final software product.
Objectives of software configuration management:
1. Remote System Administration
2. Reduced user downtime
3. Reliable data backups
4. Easy workstation setup
5. Multi-user support
Objectives of software configuration management:
1. Remote System Administration
i. The configuration standard should include necessary software and/ or privileges for remote system administration tools.
ii. These remote tools can be use to check the version of virus protection, check machine configuration, or offer remote help-desk functionality.
2. Reduced user downtime
i. A great advantage of using a standard configuration is that system becomes completely interchangeable resulting in reduced user downtime.
3. Reliable data backups
i. Using a standard directory for user data allows backup systems to selectively backup a small portion of a machine, thus, greatly reducing the network traffic and tape usage for backup systems.
ii. Also, should be a catastrophic failure occurs, the data directory could be restored to a new machine with little time and effort.
4. Easy workstation setup
i. Any sort of standardized configuration streamlines the process of setting up the system and ensures that vital components are available.
ii. if multiple machines are being set up according to a standard setup, most of the setup and configuration can be automated.
5. Multi-user support
i. It is common for users to share a workstation, the system configuration is designed to allow multiple users to use the same workstation without interfering with each other’s work.
SCM activities
1. Identification of configuration components
i. This process requires us to freeze the baseline product.
ii. The product baseline further can be view and split into requirement driver design (RDD) baseline, design baseline, and document baseline.
iii. The baseline product needs to be broken down into smaller components.
iv. These identified components are the basic units for modification and control; hence, they are numbered and tagged for identification, access, and control.
2. Change management control (CMC) process:
i. CMC is trigger through a change requirement from -user, customer, or the developer.
ii. The configuration management group has to _describe its utility and other technical and commercial implications and then make the decision of accepting the CR for implementation.
iii. All accepted CRs are then prioritizing and schedule for effecting the change in a planned manner.
3. Product status accounting and management
i. The baseline product and baseline components undergo a change and assume new status.
ii. The role of product status accounting is to ensure that the product in its latest status is functional in all respects and all concern are informing.
Read more about the Feasibility study
