Page 54 -

CHAPTER 2 THE PROCESS 25

Level 3: Defined. The software process for both management and engi-
neering activities is documented, standardized, and integrated into an organi-
zationwide software process. All projects use a documented and approved
version of the organization's process for developing and supporting software.
WebRef
This level includes all characteristics defined for level 2.
The SEI offers a wide
array of process-related Level 4: Managed. Detailed measures of the software process and product
information at quality are collected. Both the software process and products are quantitatively
www.sei.cmu.edu
understood and controlled using detailed measures. This level includes all char-
acteristics defined for level 3.
Level 5: Optimizing. Continuous process improvement is enabled by quan-
titative feedback from the process and from testing innovative ideas and tech-
nologies. This level includes all characteristics defined for level 4.

The five levels defined by the SEI were derived as a consequence of evaluating
responses to the SEI assessment questionnaire that is based on the CMM. The results
of the questionnaire are distilled to a single numerical grade that provides an indi-
cation of an organization's process maturity.
The SEI has associated key process areas (KPAs) with each of the maturity levels.
The KPAs describe those software engineering functions (e.g., software project plan-
Every organization ning, requirements management) that must be present to satisfy good practice at a
should strive to particular level. Each KPA is described by identifying the following characteristics:
achieve the intent of
the SEI CMM. • Goals—the overall objectives that the KPA must achieve.
However, • Commitments—requirements (imposed on the organization) that must be met
implementing every
aspect of the model to achieve the goals or provide proof of intent to comply with the goals.
may be overkill in your • Abilities—those things that must be in place (organizationally and technically)
situation.
to enable the organization to meet the commitments.
• Activities—the specific tasks required to achieve the KPA function.

• Methods for monitoring implementation—the manner in which the activities
are monitored as they are put into place.
• Methods for verifying implementation—the manner in which proper practice
for the KPA can be verified.
Eighteen KPAs (each described using these characteristics) are defined across the
maturity model and mapped into different levels of process maturity. The following
KPAs should be achieved at each process maturity level: 3
Process maturity level 2
• Software configuration management
• Software quality assurance

3 Note that the KPAs are additive. For example, process maturity level 4 contains all level 3 KPAs
plus those noted for level 2.