2.1 CMM Version 1.1

Capability Maturity Model (CMM) version 1.1 is the most widely used maturity model. It was developed and is still supported by the Software Engineering Institute, at Carnegie Mellon University. Version 1.0 was released in 1991, following an initiative from the Department of Defense, which had identified a need for an assessment method of their software suppliers. Version 1.1 was released in 1993. Work has been conducted on version 2.0, but this version seems to have been overtaken by CMMI. Version 2 is therefore not discussed here. CMMI is described later in the chapter.

CMM Maturity Levels

The CMM version 1.1 model is stagedeach maturity level has a number of associated key process areas, as shown in Figure 2-1.

Figure 2-1. CMM Version 1.1 Maturity Levels

graphics/02fig01.gif

Configuration management is a key process area at maturity level 2. To get to maturity level 2, a company has to achieve the goals within all the key process areas at maturity level 2, including configuration management. The goals for configuration management in CMM version 1.1 are

Goal 1: Software configuration management activities are planned.

Goal 2: Selected software work products are identified, controlled, and made available.

Goal 3: Changes to identified software work products are controlled.

Goal 4: Affected groups and individuals are informed of the status and content of software baselines.

Definition

CMM version 1.1 defines configuration management like this:

The purpose of Software Configuration Management is to establish and maintain the integrity of the products of the software project throughout the project's software life cycle. Software Configuration Management is an integral part of most software engineering and management processes.

Activities

A detailed discussion of the CMM version 1.1 expectations concerning configuration management would be out of scope here. Further details are available in the sources listed in the bibliography. It is, however, instructive to take a look at the activities to be performed, as they provide a good idea of what is expected to achieve the key process area goals. The activities defined by CMM version 1.1 are shown in Table 2-1, along with mapping to this book. (In the list of activities, SCM stands for software configuration management.)

Table 2-1. Mapping from CMM Version # 1.1 Activities

CCM Version 1.1 Activity

Mapping to This Book

Activity 1: A SCM plan is prepared for each software project according to a documented procedure.

Chapter 23Planning Configuration Managementup to Capability Level 2

Activity 2: A documented and approved SCM plan is used as the basis for performing the SCM activities.

Chapter 23Planning Configuration Managementup to Capability Level 2

Activity 3: A configuration management library system is established as a repository for the software baselines.

Chapter 1Storage

Activity 4: The software work products to be placed under configuration management are identified.

Chapter 1Identification

Chapter 7What One Needs to Know about a Configuration Item

Activity 5: Change requests and problem reports for all configuration items/units are initiated, recorded, reviewed, approved, and tracked according to a documented procedure.

Chapter 1Change Control

Chapter 8Event Registration

Chapter 8Change Request

Chapter 17Configuration Management

Activity 6: Changes to baselines are controlled according to a documented procedure.

Chapter 1Change Control

Chapter 8Event Registration

Chapter 8Change Request

Activity 7: Products from the software baseline library are created and their release is controlled according to a documented procedure.

Chapter 1Storage

Chapter 8Item Approval

Chapter 8Release Request

Activity 8: The status of configuration items/units is recorded according to a documented procedure.

Chapter 1Identification

Chapter 1Change Control

Activity 9: Standard reports documenting the SCM activities and the contents of the software baseline are developed and made available to affected groups and individuals.

Chapter 1Status Reporting

Chapter 9What Information Is Available for Configuration Items

Activity 10: Software baseline audits are conducted according to a documented procedure.

Not handledsee Chapter 1, Auditing

CMM version 1.1 also includes expectations concerning verifying implementation, commitment to perform, and the ability to perform for configuration management (and for all other key process areas).



Configuration Management Principles and Practice
Configuration Management Principles and Practice
ISBN: 0321117662
EAN: 2147483647
Year: 2002
Pages: 181

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net