The cm activity is called for in all process models. But each model attaches a different value to cm and gives more or less detailed guidelines.
CMMI
CMMI is the most popular process model in the software industry. In CMMI configuration management is demanded to obtain level 2 for the software development process. That means that configuration management is considered fundamental for controlled operation and achieving higher maturity levels.
According to CMMI cm essentially serves to assure the integrity of working results within the software life cycle.
Guidelines for roles and proceedings are given in a profoundly abstract manner.
Also, individual activities such as defining baselines, managing and tracking changes, and conducting audits are described in a very abstract way.
CMII
The process model CMII considers configuration management and its basic activities identification and storage as pivotal. CMII defines roles, boards, their tasks and a closed change process in a complete and very detailed mann.
SPICE – ISO 15504
SPICE (Software Prozess Improvement and Capability dEtermination) is a widely used international standard that is very similar to CMMI. By means of a reference model, SPICE can be used to assess and improve enterprise processes.
In the SPICE reference model, the concept of a support lifecycle is replaced by CM (SUP.08), the function of which is very similar to that of the CMMI model.
In addition to the concepts defined in CMMI, the SPICE reference model introduces outcomes, base practices, and work products for the CM process.
SPICE also differentiates between configuration management and change management - again a useful extension to the CMMI model.
CMII enhances the focus of classical configuration management and promotes a unique process for requirement, change, and problem management. Particularly the active designing of configurations is given priority.
RUP
The Rational Unified Process mirrors the knowledge of a vast number of software development experts, being practice-oriented and used as a concrete process guideline in many software houses.
Within RUP, configuration and change management workflows are defined as “core workflow”, which has to be established for any project. Roles and committees as well as their tasks within the workflow and the essential elements of a cm plan are specified within the entire software development process.
V Model XT
The process model of the government in Germany pools configuration management in a mandatory proceeding module, which is obligatory for all project types of the V Model (orderer, consignee, and introductory project).
According to V Model XT, configuration management aims at documenting the current and past product configuration and the state of compliance of its physical and functional requirements and constituting full transparency of the above-mentioned during the entire system life cycle. Activities within configuration management, contents of the cm plan, roles, committees (cm administrator, person responsible, steering committee) and their tasks are specified in a very abstract way.
XP / agile software development
These models require a well-functioning version, change, build, and test management due to their propagated dynamic and flexible proceedings, particularly short release cycles and the near absence of documentation.
In these models the requirements for configuration management are not defined. It is advised to follow well-known and proven practices in this case.
However, with increasing project complexity the principles underlying XP become problematic and additional formal proceedings should be adopted.
