2018KiltHub RepositoryOpen access

A History of the Capability Maturity Model for Software

Mark C. Paulk

Open full text 111 citations

Abstract

The Software Engineering Institute developed a five-level Capability Maturity Model for Software that described how software organizations transform their capability for building software by focusing on software process improvement. The model was initially published in 1987 as a software process maturity framework that briefly described five maturity levels. The model was formalized as the Software CMM® with a detailed description of recommended software engineering and management practices when published in 1991. Version 1.1 of the model was published in 1993, and work on Software CMM v2 was nearing completion when it was halted in 1997 in favor of the CMM Integration™ (CMMI) effort, which integrated systems engineering, software engineering, and integrated process and product development into a single model. The success of the Software CMM inspired a variety of maturity models and other standards. This article describes the history of the model and some of the major decisions made in its evolution.

About this research paper

What this paper is about

The Software Engineering Institute developed a five-level Capability Maturity Model for Software that described how software organizations transform their capability for building software by focusing on software process improvement. The model was initially published in 1987 as a software process maturity framework that briefly described five maturity levels. The model was formalized as the Software CMM® with a detailed description of recommended software engineering and management practices when published in 1991. Version 1.1 of the model was published in 1993, and work on Software CMM v2 was nearing completion when it was halted in 1997 in favor of the CMM Integration™ (CMMI) effort, which integrated systems engineering, software engineering, and integrated process and product development into a single model. The success of the Software CMM inspired a variety of maturity models and other standards. This article describes the history of the model and some of the major decisions made in its evolution.

Why it matters

OpenAlex reports 111 citations for this work. Citation counts describe recorded attention and do not establish research quality.

Key contribution

A contribution statement is not available in the OpenAlex record.

Method / approach

Method details are not available in the OpenAlex metadata.

Main findings

Findings are not separately available in the OpenAlex metadata.

Limitations

Limitations are not available in the OpenAlex metadata.

Applications

Application details are not available in the OpenAlex metadata.

Available abstract

The Software Engineering Institute developed a five-level Capability Maturity Model for Software that described how software organizations transform their capability for building software by focusing on software process improvement. The model was initially published in 1987 as a software process maturity framework that briefly described five maturity levels. The model was formalized as the Software CMM® with a detailed description of recommended software engineering and management practices when published in 1991. Version 1.1 of the model was published in 1993, and work on Software CMM v2 was nearing completion when it was halted in 1997 in favor of the CMM Integration™ (CMMI) effort, which integrated systems engineering, software engineering, and integrated process and product development into a single model. The success of the Software CMM inspired a variety of maturity models and other standards. This article describes the history of the model and some of the major decisions made in its evolution.

Key concepts: LeanCMMI, Capability Maturity Model, Verification and validation, Software engineering, Software quality, Software sizing, Software construction, Software development

Related papers

Back to paper searchBrowse research topicsOriginal source
A History of the Capability Maturity Model for Software — Research Paper | ScholarLens