Capability Maturity Model¶

A staged process-improvement model that assesses organizational software practice from ad hoc execution through defined, measured and continuously optimizing control.

Version: v2 · 2026-09-19 · History
Domain-specific #: 3586
Domain group: Applied Sciences & Engineering
Origin domain: Computer Science & Software Engineering
Subdomain: Software Process Management → Computer Science & Software Engineering
Aliases: CMM, SW-CMM

Core Idea¶

The original SW-CMM is historically specific and largely superseded by CMMI, maturity levels summarize institutionalized process capability rather than product quality, and an organization cannot infer a level from isolated best practices. Process areas supply goals and institutionalization practices; evidence is assessed across them, gaps guide improvement and staged achievement moves the organization from repeatable control toward quantitative management and optimization. The abstraction is therefore identified by a declared carrier, a transformation or constraint over that carrier, and an invariant that tells an analyst whether the named structure is genuinely present.

How would you explain it like I'm…

The Getting-Organized Ladder

Think of a team that builds computer programs. The Capability Maturity Model is like a set of five steps that shows how well the team's way of working is set up, from messy to very organized and always improving. Being on a high step means the team works in a steady, checked way, not that every program it makes is perfect.

Levels of Good Work Habits

The Capability Maturity Model is a way to rate how organized a software organization's working habits are. It has five levels, in order, from working in a messy, unpredictable way up to measuring everything and always improving. To reach a level, the organization has to show proof that it really follows certain practices across its work, not just in one lucky project. Checkers look for gaps, and those gaps tell the organization what to fix to climb to the next level. A high level describes how well the process is run, not how good each product turns out.

Software Process Maturity Levels

The Capability Maturity Model rates a software organization on five ordered maturity levels. A level summarizes how institutionalized its process capability is, meaning how consistently practices are defined, followed, and supported across the organization, rather than measuring the quality of its products. The model is organized into process areas, each with goals and practices, and an appraisal gathers evidence across them to decide what level has been reached. Gaps found in the appraisal guide the next round of improvement, moving the organization from repeatable control toward quantitative management and, eventually, continuous optimization. You cannot infer a level from a few isolated best practices. The original SW-CMM is historically specific and largely superseded by CMMI.

The Capability Maturity Model (originally SW-CMM) is a staged model for assessing and improving an organization's software process capability. It defines five ordered maturity levels; each is characterized by key process areas with goals plus institutionalization practices that make the processes stick organization-wide. An appraisal method gathers evidence across those process areas within a declared organizational and assessment scope, establishing the current level; comparing it with a target level identifies gaps and drives improvement actions, with measurement feedback closing the loop. Staged achievement moves the organization from repeatable control toward quantitative management and optimization. Two cautions are central. First, maturity describes institutionalized process capability, not product quality or output performance, so a high level is not a quality certificate. Second, a level cannot be inferred from isolated best practices; the evidence and institutionalization criteria must be met. The SW-CMM is historically specific and has been largely superseded by CMMI, and any claim should state which model it is using.

Scope of Application¶

Capability Maturity Model belongs to software process management and is useful where the analyst can specify the typed software process management carrier, including objects, relations, parameters, conventions, evidence, boundaries, and comparison targets, then evaluate the organization and assessment scope, five maturity levels and their ordering, key process areas or goals, institutionalization and evidence criteria, appraisal method, current and target level, improvement actions, measurement feedback, distinction between process maturity and output performance and relationship to CMMI are explicit.

Clarity¶

The abstraction clarifies a crowded vocabulary by making the organization and assessment scope, five maturity levels and their ordering, key process areas or goals, institutionalization and evidence criteria, appraisal method, current and target level, improvement actions, measurement feedback, distinction between process maturity and output performance and relationship to CMMI are explicit the center of the account. A claim should name the carrier, the governing operation or relation, the applicable assumptions, and the recognition test.

Manages Complexity¶

Without the abstraction, an analyst must reason directly over many local details: the carrier roles, admissibility assumptions, competing conventions, derived invariants, boundary cases, and proof or validation obligations specific to Capability Maturity Model. Capability Maturity Model compresses them into the roles in the structural signature. That compression permits comparison across instances without erasing the variables that determine validity. It also exposes which details may be varied safely and which are constitutive.

Abstract Reasoning¶

Identify the carrier. State what the elements, states, objects, or observations are: the typed software process management carrier, including objects, relations, parameters, conventions, evidence, boundaries, and comparison targets. Reject examples whose alleged carrier belongs to a different problem.
Lock the constitutive rule. Express the organization and assessment scope, five maturity levels and their ordering, key process areas or goals, institutionalization and evidence criteria, appraisal method, current and target level, improvement actions, measurement feedback, distinction between process maturity and output performance and relationship to CMMI are explicit independently of one notation or implementation.

Knowledge Transfer¶

Knowledge transfers strongly among subfields of software process management because they reuse the typed software process management carrier, including objects, relations, parameters, conventions, evidence, boundaries, and comparison targets, Process areas supply goals and institutionalization practices; evidence is assessed across them, gaps guide improvement and staged achievement moves the organization from repeatable control toward quantitative management and optimization., and type the carrier, state every parameter and convention in the definition, test that the organization and assessment scope, five maturity levels and their ordering, key process areas or goals, institutionalization and evidence criteria, appraisal method, current and target level, improvement actions, measurement feedback, distinction between process maturity and output performance and relationship to CMMI are explicit, compare the nearest accepted identity, and report counterexamples, uncertainty, and limiting cases.

Relationships to Other Abstractions¶

Current abstraction Capability Maturity Model Domain-specific

Parents (1) — outgoing typed relations

Capability Maturity Model is a kind of Evaluation Prime

It remains its own entry because its identity is fixed by the organization and assessment scope, five maturity levels and their ordering, key process areas or goals, institutionalization and evidence criteria, appraisal method, current and target level, improvement actions, measurement feedback, distinction between process maturity and output performance and relationship to CMMI.

Hierarchy path (1) — routes to 1 parentless root

Capability Maturity Model → is a kind of Evaluation → presupposes Comparison

Neighborhood in Abstraction Space¶

Capability Maturity Model sits in a crowded region of the domain-specific corpus (30^th percentile for distinctiveness): several abstractions share nearly its structure, so a description that fits it tends to fit its neighbors too.

Family — Statistical Process Control & Quality Management (15 abstractions)

Nearest neighbors

Computed from structural-signature embeddings · 2026-10-25