CAPABILITY MATURITY MODEL

for Software (CMM) Version 1.1

Maturity Level – 4 (Managed Level)Maturity Level – 4 (Managed Level)

Characteristics of a Level Characteristics of a Level 4 Organization4 Organization

• At level 3, measurements have been defined and collected systematically

• At level 4, decisions are made based on data collected

• The ORGANISATION sets quantitative goals for both software products and processes.

• The process performance of a project is controlled quantitatively.

Key Process Areas Key Process Areas

• Quantitative process management• Software quality management

Quantitative Process Quantitative Process Management Management

• Purpose is to control the process performance of the software project quantitatively

• Involves– Establishing goals for process performance– Measuring the performance of the project– Analyzing these measurements making

adjustments to maintain process performance within acceptable limits

QPM - Common FeaturesQPM - Common Features

• Commitment– Written organizational policy for measuring and

quantitatively controlling the performance of the project’s defined software process

QPM - Common FeaturesQPM - Common Features

• Ability– Group that is responsible for coordinating the

quantitative process management activities should exist.

– Adequate resources and funding– Support for collecting, recording and analyzing data– Training on quantitative process management for

personnel performing these activities– Orientation to software engineering group on the

goals and value of quantitative process management• Measurement

– To determine the status of the quantitative process management activities.

QPM - ActivitiesQPM - Activities• The quantitative process management activities are

planned.– The software project's plan for quantitative process

management is developed according to a documented procedure.

– The software project's quantitative process management activities are performed in accordance with the project's quantitative process management plan.

– The strategy for the data collection and the quantitative analyses to be performed are determined based on the project's defined software process.

QPM - ActivitiesQPM - Activities

• The process performance of the project’s defined software process is controlled quantitatively.– The software project's quantitative process

management activities are performed in accordance with the project's quantitative process management plan.

QPM - ActivitiesQPM - Activities

• The process performance of the project’s defined software process is controlled quantitatively.– The measurement data used to control the project's

defined software process quantitatively are collected according to a documented procedure.

– The project's defined software process is analyzed and brought under quantitative control according to a documented procedure.

– Reports documenting the results of the software project's quantitative process management activities are prepared and distributed.

Software Quality Software Quality Management Management

• Purpose– Is to develop a quantitative understanding of the

quality of the project’s software products and achieve specific quality goals

• Involves– Defining quality goals for the software products– Establishing plans to achieve these goals– Monitoring and adjusting software plans, software

work products, activities and quality goals to satisfy the needs and desires of customer and end-user

SQM - Common FeaturesSQM - Common Features

• Commitment– Written organizational policy for managing software

quality.• Ability

– Adequate resources and funding– Training to individuals to perform quality

management activities• Measurement

– To determine the status of software quality management activities.

SQM - ActivitiesSQM - Activities• The project’s software quality management activities are

planned.– The project's software quality plan is developed and

maintained according to a documented procedure.– The project's software quality plan is the basis for the

project's activities for software quality management. • Measurable goals for software product quality and their

priorities are defined.– The project's quantitative quality goals for the software

products are defined, monitored, and revised throughout the software life cycle.

– The software project's quantitative quality goals for the products are allocated appropriately to the subcontractors delivering software products to the project.

SQM - ActivitiesSQM - Activities

• Actual progress toward achieving the quality goals for the software products is quantified and managed.– The project's software quality plan is the basis for

the project's activities for software quality management

– The quality of the project's software products is measured, analyzed, and compared to the products' quantitative quality goals on an event-driven basis.

End of Managed Level (L4) KPAsEnd of Managed Level (L4) KPAs