Configuration Management (CM) is about uniquely identifying, controlling storage, controlling changes, and reporting status of software products, product components and selected intermediate work products during the system’s life cycle.
CM encompasses the everyday tasks within a software organization, whether development or maintenance, to establish and maintain the integrity of work products in a project throughout the project life cycle. CM involves identifying the configuration of developed work products, hence assuring the reliability of products delivered to customers by systematically controlling changes to the identified work products.
This chapter is to define a method for SMEs to use in providing configuration management of software system and/or software development projects.
Admins
Configuration Rep
Team leads
Practitioners
Developers
Testers
UX
QA team
PO Team
01-Establishing CM Environment Procedure
The purpose of this procedure is to establish the configuration management system including the storage media, system, and the tools for accessing the configuration system. The procedure will produces the required infrastructure for the overall development project.
02-Planning Procedure
The objective of the CM planning procedure is to develop the required guidance for the deployment of the configuration management procedures. This procedure involves the identification of the project configuration controller, developing the CM plan and ensuring its integration with the overall project plan
03-Baselining Procedure
The purpose of this procedure is to produce baselines from the identified CIs. The procedure, when performed, ensures the existence and existence’s announcement of the baselines that will be considered as a starting point for further development phases in the product development life cycle. The quality of the baseline is completely dependent on the functional and physical audits done before the baselining.
The following are a sub procedures under baselining procedures.
04-Change Control Procedure
The purpose of this procedure is to guide the performing of save changes to any stable work product. The change control procedure starts by raising a change request, then be being evaluated, implemented and verified. The impact of these changes should be estimated and then evaluated at the end of the project at the project closure phase.
05-Maintaining CM Environment Procedure
The purpose of this procedure is to maintain the configuration management system includes the storage media, system, and the tools for accessing the configuration system. The procedure will produces the required infrastructure for the overall development project.
TFS
Enterprise Architect