lec22_notes_cocomo,cmmi and case tool

7/23/2019 Lec22_Notes_cocomo,Cmmi and Case Tool

1/35

Capability Maturity Model

Integration


2/35

Capability Maturity Model Integration(CMMI)is a process improvement approach whose goal is to

help organizations improve their performance. CMMIcan be used to guide process improvement across aproject, a division, or an entire organization.

CMMI in software engineering and organizationaldevelopment is a process improvement approach

that provides organizations with the essentialelements for eective process improvement. CMMIis registered in the !.". #atent and $rademar% &'ceb Carnegie Mellon !niversit.

ccording to the "oftware *ngineering Institute ("*I,

+-), CMMI helps integrate traditionall separateorganizational functions, set process improvementgoals and priorities, provide guidance for /ualitprocesses, and provide a point of reference forappraising current processes.


3/35

3

CMM developed by the Software EngineeringInstitute to helporganizations which develop software

to improve their software processes

organizations which acquire softwareto assess the quality of their contractors


4/35

4

Immature organizationprocesses are improvised during the course of a

proect to resolve unanticipated crisesproducts often delivered late and their quality

is questionable Mature organization

organization!wide standard approach tosoftware processes" #nown and accepted by all

engineers focus on continuous improvement both in

performance and product quality


5/35


6/35

The organization

Does not have an environment for developing and

maintaining software.

At the time of crises, projects usually stop using allplanned procedures and revert to coding and testing.


7/35

Effective management process having establishedwhich can be

Practiced

DocumentedEnforced

Trained

Measured

mprovised


8/35

!tandard defined software engineering and managementprocess for developing and maintaining software.

These processes are put together to ma"e a coherentwhole.


9/35

#uantitative goals set for both software products andprocesses.

The organi$ational measurement plan involvesdetermining the productivity and %uality for all importantsoftware process activities across all projects.


10/35

Emphasis laid on

Process improvement

Tools to identify wea"nesses e&isting in their processes

Ma"e timely corrections


11/35$$

Organizational Innovation and DeploymentCausal Analysis and Resolution5 Optimizing

4 QuantitativelyManaged

3 Defined

2 Managed

ContinuousProcess

Improvement

QuantitativeManagement

ProcessStandardization

BasicProjectManagement

Organizational ro!ess erforman!eQuantitative ro"e!t Management

Re#uirements Development$e!%ni!al &olutionrodu!t Integration'erifi!ation'alidation

Organizational ro!ess (o!usOrganizational ro!ess DefinitionOrganizational $rainingIntegrated ro"e!t Management for IDRis) ManagementIntegrated $eamingIntegrated &upplier ManagementDe!ision Analysis and ResolutionOrganizational *nvironment for Integration

Re#uirements Managementro"e!t lanningro"e!t Monitoring and Control&upplier Agreement ManagementMeasurement and Analysisro!ess and rodu!t Quality Assuran!eConfiguration Management

Quality

rodu!tivity

Ris)+

Re,or)

- Initial

ro!ess Areas.evel (o!us

None


12/35


13/35

C&C&M& is one of the most widel usedsoftware estimation models in the world

It was developed b 0arr 0oehm in 12-1

C&C&M& predicts the eort and schedule

for a software product developmentbased on inputs relating to the size ofthe software and a number of costdriversthat aect productivit


14/35

C%C%M% has three different models thatreflect the complexity&

the 0asic Model

the Intermediate Model

and the 3etailed Model


15/35

Organic Mode4 5elativel small, simple software projects4 Small teams with good application

experience wor% to a set of less than rigidre/uirements

4 Similarto the previousl developed projects4 relativel smalland re/uires little innovation

Semidetached Mode4 Intermediate (in size and comple6it)

software projects in which teams withmixed experiencelevels must meet ami6 of rigid and less than rigidre/uirements.


16/35

Embedded Mode

4"oftware projects that mustbe developed within a set oftight hardware,

software, and operationalconstraints.


17/35

#rimar cost driver is the number ofDelivered Source Instructions(3"I) 7 Delivered ine Of Codedeveloped b the project

C&C&M& estimates assume that theproject will enjo good managementb both the developer and thecustomer

ssumes the re/uirements speci8cationis not substantially changed afterthe plans and re/uirements phase


18/35

0asic C&C&M& is good for !uic"#early# rough order of magnitudeestimatesof software costs

It does not account for dierences inhardware constraints# personnel!uality and experience, use ofmodern tools and techni/ues, andother project attributes %nown tohave a signi8cant in9uence onsoftware costs, which limits itsaccuracy


19/35

*:ab(;


20/35

Software pro'ect ab bbcb db

&rganic +.> 1.?+.? .@-

"emi=detached @. 1.1++.? .@?

*mbedded @.A 1.++.? .@+


21/35

Mode Effort Schedule

Organic E=2.4*(KDSI)-/05

TDEV=2.5*(E)0/31

Semidetached E=3.0*(KDSI)-/-2

TDEV=2.5*(E)0/35

Emedded E=3.!*(KDSI)-/20

TDEV=2.5*(E)0/32


22/35

Its accurac is necessaril limitedbecause of its lac" of factorswhich

have a signi8cant in9uence onsoftware costs

$he 0asic C&C&M& estimates arewithin a factor of ()*onl +,-of thetime, and within a factor of + onl./-of the time


23/35

Be have determined our project 8ts thecharacteristics of Semi0Detachedmode

Be estimate our project will have *+#///3elivered "ource Instructions. !sing the

formulas, we can estimate

E1ort: @.D(@+) ()(+ : 1>A man=months

Schedule: +.?D(1>A)/)*2

: 1> months &roductivity : @+, 3"I 7 1>A MM

: +12 3"I7MM 3verage Sta4ng : 1>A MM 71> months

: 1 E"#


24/35


25/35

Software engineering tools consisted solelyof translators" compilers" assemblers"

lin#ers" loaders" etc' ( the software )EE*E*to build code'

Computers weren+t powerful enough or

advanced yet to support higher!levelfunctioning


26/35

Software engineering often follows specificstandardized methods

,here are lots of diagrams anddocumentation involved

So now computers can be used to deal with

the higher!level aspects of softwareengineering


27/35

5hat is a C3SE Environment6

C"* is the use of computer=basedsupport in the software development

process.

5hat is a C3SE 7ool6

C"* tool is a computer=based

product aimed at supporting one ormore software engineering activitieswithin a software developmentprocess.


28/35

"uppl basic functionalit, do routine tas%sautomaticall 0e able to support editing of code in the particular

programming language, suppl refactoring tools

*nhance productivit Fenerate code pieces automaticall

Increase software /ualit

Intuitive use

Integration with other tools Eor e6ample, code editor wor%s with code repositor


29/35

#roject management software

"stem design tools

Code storage Compilers

$ranslation tools

$est software


30/35

Code generation tools (Gisual"tudio .H*$)

Code analsis (0orland udits)

3evelopment of data models(!M< editors)

Cleaning up code (refactoringtools)

0ug trac%er

Gersion control (CG", etc.)


31/35

C"* tools do more than justoutput code

Can be used to generate "*

documents3atabase schema

3ata 9ow diagrams

*ntit relationship diagrams#rogram speci8cations

!ser documentation


32/35


33/35


34/35


35/35

!pper C3SE $ools for the analsisand design phase of the softwaredevelopment lifeccle

(diagramming tools, report andform generators, analsis tools)

lec22_notes_cocomo,cmmi and case tool

Documents