1997Unpublished venueOpen access

Responsibilities under the Capability Maturity Model

Colin Myers, Tracy Hall, Dave Pitt

Open full text 1 citations

Abstract

Software Engineering teams in organizations of all types and sizes are facing increasing pressure to deliver high-quality, complex products in highly competitive, complex and global environments. Concurrent with the increased mission-critical status of software and the reduced time to market inherent in many software development environments is the drive for higher quality which is increasingly being measured by process assessments. The Software Capability Maturity Model (CMM) developed by the Software Engineering Institute (SEI) at Carnegie Mellon University addresses key process areas (KPAs) for progressively higher (or more mature) levels of software development. Incumbent within these different levels of software development maturity are clear indicators of appropriate professional responsibilities for software engineers. The CMM is focused on process, however, and does not directly address people or teams and the issues arising from changing professional responsibilities. This chapter examines these responsibilities, many of which have new or renewed importance for software development professionals, in the context of the software maturity levels defined by the SEI CMM. These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.

Open-access reader

About this research paper

What this paper is about

Software Engineering teams in organizations of all types and sizes are facing increasing pressure to deliver high-quality, complex products in highly competitive, complex and global environments. Concurrent with the increased mission-critical status of software and the reduced time to market inherent in many software development environments is the drive for higher quality which is increasingly being measured by process assessments. The Software Capability Maturity Model (CMM) developed by the Software Engineering Institute (SEI) at Carnegie Mellon University addresses key process areas (KPAs) for progressively higher (or more mature) levels of software development. Incumbent within these different levels of software development maturity are clear indicators of appropriate professional responsibilities for software engineers. The CMM is focused on process, however, and does not directly address people or teams and the issues arising from changing professional responsibilities. This chapter examines these responsibilities, many of which have new or renewed importance for software development professionals, in the context of the software maturity levels defined by the SEI CMM. These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.

Why it matters

OpenAlex reports 1 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

Software Engineering teams in organizations of all types and sizes are facing increasing pressure to deliver high-quality, complex products in highly competitive, complex and global environments. Concurrent with the increased mission-critical status of software and the reduced time to market inherent in many software development environments is the drive for higher quality which is increasingly being measured by process assessments. The Software Capability Maturity Model (CMM) developed by the Software Engineering Institute (SEI) at Carnegie Mellon University addresses key process areas (KPAs) for progressively higher (or more mature) levels of software development. Incumbent within these different levels of software development maturity are clear indicators of appropriate professional responsibilities for software engineers. The CMM is focused on process, however, and does not directly address people or teams and the issues arising from changing professional responsibilities. This chapter examines these responsibilities, many of which have new or renewed importance for software development professionals, in the context of the software maturity levels defined by the SEI CMM. These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.

Key concepts: Capability Maturity Model, Software development, Personal software process, Software Engineering Process Group, Maturity (psychological), Team software process, Context (archaeology), Software development process

Related papers

Back to paper searchBrowse research topicsOriginal source
Responsibilities under the Capability Maturity Model — Research Paper | ScholarLens