compatibilty maturity model

8/13/2019 Compatibilty Maturity Model

1/33

Capability Maturity Model


2/33

What is CMM?

CMM: Capability Maturity Model

Developed by the Software Engineering

Institute of the Carnegie Mellon

University

Framework that desribes the key

elements of an effetive softwareproess!


3/33

Desribes an evolutionary improvement

path for software organi"ations from an

ad ho# immature proess to a mature#

disiplined one! $rovides guidane on how to gain

ontrol of proesses for developing and

maintaining software and how to evolvetoward a ulture of software

engineering and management

e%ellene!

What is CMM?


4/33

Process Maturity Concepts

Software $roess set of ativities# methods# praties# and

transformations that people use to develop andmaintain software and the assoiated produts&e!g!# pro'et plans# design douments# ode# testases# user manuals(

Software $roess Capability

desribes the range of e%peted results that anbe ahieved by following a software proess

means of prediting the most likely outomes to bee%peted from the ne%t software pro'et theorgani"ation undertakes


5/33

Process Maturity Concepts

Software $roess $erformane atual results ahieved by following a software

proess

Software $roess Maturity e%tent to whih a speifi proess is e%pliitly

defined# managed# measured# ontrolled andeffetive

implies potential growth in apability indiates rihness of proess and onsisteny with

whih it is applied in pro'ets throughout theorgani"ation


6/33

What are the CMM Levels?

(The five levels of software process maturity)

Maturity level indiates level of proess

apability:

Initial

)epeatable

Defined

Managed

*ptimi"ing


7/33


8/33

Level 1 !nitial

Initial : +he software proess is harateri"edas ad ho# and oasionally even haoti! Fewproesses are defined# and suess depends

on individual effort!,t this level# fre-uently have diffiulty makingommitments that the staff an meet with an orderlyproess

$roduts developed are often over budget and

shedule .ide variations in ost# shedule# funtionality and

-uality targets Capability is a harateristi of the individuals# not

of the organi"ation


9/33

Level " #epeatable

/asi proess management proesses areestablished to trak ost# shedule# andfuntionality! +he neessary proessdisipline is in plae to repeat earliersuesses on pro'ets with similarappliations! )ealisti pro'et ommitments based on results

observed on previous pro'ets Software pro'et standards are defined and

faithfully followed $roesses may differ between pro'ets $roess is disiplined

earlier suesses an be repeated


10/33

Level $ %efined

+he software proess for both

management and engineering ativities

is doumented# standardi"ed# andintegrated into a standard software

proess for the organi"ation! ,ll

pro'ets use an approved# tailoredversion of the organi"ation0s standard

software proess for developing an

maintaining software!


11/33

Level & Mana'ed

Detailed measures of the software proess

and produt -uality are olleted! /oth the

software proess and produts are-uantitatively understood and ontrolled! 1arrowing the variation in proess performane to

fall within aeptable -uantitative bounds

.hen known limits are e%eeded# orretiveation an be taken

2uantifiable and preditable

predit trends in proess and produt -uality


12/33

Level ptimi*in'

Continuous proess improvement is enabledby -uantitative feedbak from the proessand from piloting innovative ideas andtehnologies!

3oal is to prevent the ourrene of defets Causal analysis

Data on proess effetiveness used for ostbenefit analysis of new tehnologies andproposed proess hanges


13/33

!nternal +tructure to Maturity

Levels E%ept for level 4# eah level is deomposed

into key proess areas &5$,(

Eah 5$, identifies a luster of relatedativities that# when performed olletively#ahieve a set of goals onsidered importantfor enhaning software apability! ommitment ability ativity measurement

verifiation


14/33


15/33


16/33

Level " ,P-s

)e-uirements Management Establish ommon understanding of ustomer

re-uirements between the ustomer and thesoftware pro'et

)e-uirements is basis for planning and managingthe software pro'et

1ot working bakwards from a given release date6

Software $ro'et $lanning Establish reasonable plans for performing the

software engineering ativities and for managingthe software pro'et


17/33

Level " ,P-s

Software $ro'et +raking and *versight Establish ade-uate visibility into atual progress +ake effetive ations when pro'et0s performane

deviates signifiantly from planned

Software Subontrat Management Manage pro'ets outsoured to subontrators

Software 2uality ,ssurane $rovide management with appropriate visibility

intoproess being used by the software pro'ets

work produts


18/33

Level " ,P-s

Software Configuration ManagementEstablish and maintain the integrity of work

produts $rodut baseline

/aseline authority


19/33

Level $ ,P-s

*rgani"ation $roess Fous Establish organi"ational responsibility for software

proess ativities that improve the organi"ation0soverall software proess apability

*rgani"ation $roess Definition Develop and maintain a usable set of software

proess assets stable foundation that an be institutionali"ed

basis for defining meaningful data for -uantitative

proess management


20/33

Level $ ,P-s

+raining $rogram Develop skills and knowledge so that individual

an perform their roles effetively and effiiently

*rgani"ational responsibility 1eeds identified by pro'et

Integrated Software Management Integrated engineering and management ativities

Engineering and management proesses aretailored from the organi"ational standardproesses

+ailoring based on business environment andpro'et needs


21/33

Level $ ,P-s

Software $rodut Engineering tehnial ativities of the pro'et are well defined

&SD7C( orret# onsistent work produts

Intergroup Coordination Software engineering groups partiipate atively

with other groups

$eer )eviews early defet detetion and removal better understanding of the produts implemented with inspetions# walkthroughs# et


22/33

Level & ,P-s

2uantitative $roess Management ontrol proess performane -uantitatively

atual results from following a software proess fous on identifying and orreting speial auses

of variation with respet to a baseline proess

Software 2uality Management -uantitative understanding of software -uality

produts

proess


23/33

Level ,P-s

$roess Change Management ontinuous proess improvement to improve

-uality# inrease produtivity# derease yle time

+ehnology Change Management identify and transfer benefiial new tehnologies

tools

methods

proesses

Defet $revention ausal analysis of defets to prevent reurrene


24/33

What are the benefits ?

8elps forge a shared vision of what softwareproess improvement means for theorgani"ation

Defines set of priorities for addressingsoftware problems

Supports measurement of proess by

providing framework for performing reliableand onsistent appraisals $rovides framework for onsisteny of

proesses and produt


25/33

Why measure software and

software process?*btain data that helps us to better ontrol

shedule

ost

-uality of software produts


26/33

Consistent measurement provide

data for 2uantitatively e%pressing re-uirements#

goals# and aeptane riteria

Monitoring progress and antiipatingproblems

2uantifying tradeoffs used in alloating

resoures $rediting shedule# ost and -uality


27/33

Measurements

8istorial

$lan

,tual

$ro'etions


28/33

+.! Core Measures

Unit of Measure Characteristics Addressed

$hysial soure lines of ode7ogial soure lines of ode

Si"e# reuse# rework

Staff hours Effort# ost# resoure alloations

Calendar dates for proessmilestonesCalendar dates for deliverables

Shedule# progress

$roblems and defets 2uality# improvement trends#rework# readiness for delivery


29/33

./amples of measurements for

si*e of wor0 products Estimated number of re-uirements

,tual number of re-uirements

Estimated soure lines of ode &S7*C(

,tual S7*C

Estimated number of test ases ,tual number of test ases


30/33

./ample of measurements of

effort Estimated man9hours to designode a

given module

,tual man9hours e%pended fordesigningoding the module

Estimated number of hours to run buildsfor a given release

,tual number of hours spent runningbuilds for the release


31/33

./amples of measurements of

uality of the wor0 product 1umber of issues raised at

re-uirements inspetion

1umber of re-uirements issues open 1umber of re-uirements issues losed 1umber of issues raised during ode

inspetion 1umber of defets opened during unit

testing


32/33


uality of the wor0 product 1umber of defets opened during

system testing

1umber of defets opened during U,+ 1umber of defets still open

1umber of defets losed

Defet age


33/33


uality of the wor0 product +otal number of build failures

+otal number of defets fi%ed for a

given release +otal number of defets verified and

aepted

+otal number of defets verified and

re'eted

compatibilty maturity model

Documents