Capability Maturity Model

What is CMM?
CMM:

Capability Maturity Model Developed by the Software Engineering Institute of the Carnegie Mellon University Framework that des ribes the key elements of an effe tive software pro ess!

What is CMM?

Des ribes an evolutionary improvement path for software organi"ations from an ad ho # immature pro ess to a mature# dis iplined one! $rovides guidan e on how to gain ontrol of pro esses for developing and maintaining software and how to evolve toward a ulture of software engineering and management e% ellen e!

Process Maturity Concepts

Software $ro ess

set of a tivities# methods# pra ti es# and transformations that people use to develop and maintain software and the asso iated produ ts &e!g!# pro'e t plans# design do uments# ode# test ases# user manuals( des ribes the range of e%pe ted results that an be a hieved by following a software pro ess means of predi ting the most likely out omes to be e%pe ted from the ne%t software pro'e t the organi"ation undertakes

Software $ro ess Capability

Process Maturity Concepts

Software $ro ess $erforman e

a tual results a hieved by following a software pro ess e%tent to whi h a spe ifi pro ess is e%pli itly defined# managed# measured# ontrolled and effe tive implies potential growth in apability indi ates ri hness of pro ess and onsisten y with whi h it is applied in pro'e ts throughout the organi"ation

Software $ro ess Maturity

What are the CMM Levels?

(The five levels of software process maturity) Maturity level indi ates level of pro ess apability: Initial )epeatable Defined Managed *ptimi"ing

Level 1 !nitial

Initial : +he software pro ess is hara teri"ed as ad ho # and o asionally even haoti ! Few pro esses are defined# and su ess depends on individual effort!

,t this level# fre-uently have diffi ulty making ommitments that the staff an meet with an orderly pro ess $rodu ts developed are often over budget and s hedule .ide variations in ost# s hedule# fun tionality and -uality targets Capability is a hara teristi of the individuals# not of the organi"ation

Level " #epeatable

/asi pro ess management pro esses are established to tra k ost# s hedule# and fun tionality! +he ne essary pro ess dis ipline is in pla e to repeat earlier su esses on pro'e ts with similar appli ations!

)ealisti pro'e t ommitments based on results observed on previous pro'e ts Software pro'e t standards are defined and faithfully followed $ro esses may differ between pro'e ts $ro ess is dis iplined earlier su esses an be repeated

Level $ %efined
+he

software pro ess for both management and engineering a tivities is do umented# standardi"ed# and integrated into a standard software pro ess for the organi"ation! ,ll pro'e ts use an approved# tailored version of the organi"ation0s standard software pro ess for developing an maintaining software!

Level & Mana'ed

Detailed measures of the software pro ess and produ t -uality are olle ted! /oth the software pro ess and produ ts are -uantitatively understood and ontrolled!

1arrowing the variation in pro ess performan e to fall within a eptable -uantitative bounds .hen known limits are e% eeded# orre tive a tion an be taken 2uantifiable and predi table
predi t trends in pro ess and produ t -uality

Level ( )ptimi*in'

Continuous pro ess improvement is enabled by -uantitative feedba k from the pro ess and from piloting innovative ideas and te hnologies! 3oal is to prevent the o urren e of defe ts

Causal analysis

Data on pro ess effe tiveness used for ost benefit analysis of new te hnologies and proposed pro ess hanges

!nternal +tructure to Maturity Levels

E% ept for level 4# ea h level is de omposed into key pro ess areas &5$,( Ea h 5$, identifies a luster of related a tivities that# when performed olle tively# a hieve a set of goals onsidered important for enhan ing software apability!

ommitment ability a tivity measurement verifi ation

Level " ,P-s

)e-uirements Management

Establish ommon understanding of ustomer re-uirements between the ustomer and the software pro'e t )e-uirements is basis for planning and managing the software pro'e t 1ot working ba kwards from a given release date6 Establish reasonable plans for performing the software engineering a tivities and for managing the software pro'e t

Software $ro'e t $lanning

Level " ,P-s

Software $ro'e t +ra king and *versight

Establish ade-uate visibility into a tual progress +ake effe tive a tions when pro'e t0s performan e deviates signifi antly from planned Manage pro'e ts outsour ed to sub ontra tors $rovide management with appropriate visibility into
pro ess being used by the software pro'e ts work produ ts

Software Sub ontra t Management

Software 2uality ,ssuran e

Level " ,P-s

Software Configuration Management

Establish

and maintain the integrity of work

produ ts $rodu t baseline /aseline authority

Level $ ,P-s

*rgani"ation $ro ess Fo us

Establish organi"ational responsibility for software pro ess a tivities that improve the organi"ation0s overall software pro ess apability Develop and maintain a usable set of software pro ess assets
stable foundation that an be institutionali"ed basis for defining meaningful data for -uantitative pro ess management

*rgani"ation $ro ess Definition

Level $ ,P-s

+raining $rogram

Develop skills and knowledge so that individual an perform their roles effe tively and effi iently *rgani"ational responsibility 1eeds identified by pro'e t Integrated engineering and management a tivities Engineering and management pro esses are tailored from the organi"ational standard pro esses +ailoring based on business environment and pro'e t needs

Integrated Software Management

Level $ ,P-s

Software $rodu t Engineering

te hni al a tivities of the pro'e t are well defined &SD7C( orre t# onsistent work produ ts Software engineering groups parti ipate a tively with other groups early defe t dete tion and removal better understanding of the produ ts implemented with inspe tions# walkthroughs# et

Intergroup Coordination

$eer )eviews

Level & ,P-s

2uantitative $ro ess Management

ontrol pro ess performan e -uantitatively a tual results from following a software pro ess fo us on identifying and orre ting spe ial auses of variation with respe t to a baseline pro ess -uantitative understanding of software -uality
produ ts pro ess

Software 2uality Management

Level ( ,P-s

$ro ess Change Management

ontinuous pro ess improvement to improve -uality# in rease produ tivity# de rease y le time identify and transfer benefi ial new te hnologies
tools methods pro esses

+e hnology Change Management

Defe t $revention

ausal analysis of defe ts to prevent re urren e

What are the benefits ?

8elps forge a shared vision of what software pro ess improvement means for the organi"ation Defines set of priorities for addressing software problems Supports measurement of pro ess by providing framework for performing reliable and onsistent appraisals $rovides framework for onsisten y of pro esses and produ t

Why measure software and software process?

*btain data that helps us to better ontrol s hedule ost -uality of software produ ts

Consistent measurement provide data for

2uantitatively e%pressing re-uirements# goals# and a eptan e riteria Monitoring progress and anti ipating problems 2uantifying tradeoffs used in allo ating resour es $redi ting s hedule# ost and -uality

Measurements

8istori al $lan , tual $ro'e tions

+.! Core Measures

Unit of Measure $hysi al sour e lines of ode 7ogi al sour e lines of ode Staff hours Calendar dates for pro ess milestones Calendar dates for deliverables $roblems and defe ts Characteristics Addressed Si"e# reuse# rework Effort# ost# resour e allo ations S hedule# progress 2uality# improvement trends# rework# readiness for delivery

./amples of measurements for si*e of wor0 products

Estimated number of re-uirements , tual number of re-uirements Estimated sour e lines of ode &S7*C( , tual S7*C Estimated number of test ases , tual number of test ases

./ample of measurements of effort

Estimated man9hours to design: ode a given module , tual man9hours e%pended for designing: oding the module Estimated number of hours to run builds for a given release , tual number of hours spent running builds for the release

./amples of measurements of 1uality of the wor0 product

1umber of issues raised at re-uirements inspe tion 1umber of re-uirements issues open 1umber of re-uirements issues losed 1umber of issues raised during ode inspe tion 1umber of defe ts opened during unit testing

./amples of measurements of 1uality of the wor0 product

1umber of defe ts opened during system testing 1umber of defe ts opened during U,+ 1umber of defe ts still open 1umber of defe ts losed Defe t age

./amples of measurements of 1uality of the wor0 product

+otal number of build failures +otal number of defe ts fi%ed for a given release +otal number of defe ts verified and a epted +otal number of defe ts verified and re'e ted