32
 CAPABILITY MATURITY MODEL for Software (CMM) Version 1.1 Maturity Level – 3 (Defined Level) Maturity Level – 3 (Defined Level)

CMMLevel3

Embed Size (px)

Citation preview

8/14/2019 CMMLevel3

http://slidepdf.com/reader/full/cmmlevel3 1/32

 CAPABILITY MATURITY MODELfor Software (CMM)

Version 1.1Maturity Level – 3 (Defined Level)Maturity Level – 3 (Defined Level)

8/14/2019 CMMLevel3

http://slidepdf.com/reader/full/cmmlevel3 2/32

Characteristics of a Level3Characteristics of a Level3

OrganizationOrganization

• At CMM level 2, the focus is on projects• At CMM level 3, the emphasis shifts to the

organization

– Best practices are gathered across the organization

– Processes are tailored as appropriate

• The organization supports the projects by establishing– Common processes for engineering and management

– Common measurements

– Training

• The process capability is based on a common, organization

wide understanding of the activities, roles andresponsibilities

8/14/2019 CMMLevel3

http://slidepdf.com/reader/full/cmmlevel3 3/32

Key Process AreasKey Process Areas

• Organization process focus (OPF)

• Organization process definition (OPD)

• Training program (TP)

• Integrated software management (ISM)• Software product engineering (SPE)

• Intergroup coordination (IGC)

• Peer reviews (PR)

8/14/2019 CMMLevel3

http://slidepdf.com/reader/full/cmmlevel3 4/32

Organization Process FocusOrganization Process Focus

• Purpose is to establish the organizationalresponsibility for software process activities thatimproves the overall process capability

• Involves

– Establishing a group such as a software engineering

process group (SEPG).

– Developing and maintaining and understanding of the organization’s processes via this group.

– Coordinating the activities to assess, develop,maintain and improve these processes

8/14/2019 CMMLevel3

http://slidepdf.com/reader/full/cmmlevel3 5/32

OPF - Common FeaturesOPF - Common Features

• Commitment

– Written organization policy (A documentedprocedure) for coordinating softwareprocess development and improvementacross the organization.

– Participation of senior management incarrying out the activities cited above.

– Activities are overseen by seniormanagement.

8/14/2019 CMMLevel3

http://slidepdf.com/reader/full/cmmlevel3 6/32

OPF - Common FeaturesOPF - Common Features

• Ability

– Group that is responsible for softwareprocess activity should always exist

– Providing adequate resources

– Training to perform the activities pertainingto process definition and improvement tothe group/s including SEPG

• Measurements

– To determine status of activities pertainingto organization process focus

8/14/2019 CMMLevel3

http://slidepdf.com/reader/full/cmmlevel3 7/32

OPF - ActivitiesOPF - Activities

• The strengths and weaknesses of the softwareprocesses used are identified relative to aprocess standard– The software process is assessed periodically, and

action plans are developed to address the assessmentfindings

• Organizational-level process development andimprovement activities are planned– The organization develops and maintains a plan for its

software process development and improvement

activities. 

8/14/2019 CMMLevel3

http://slidepdf.com/reader/full/cmmlevel3 8/32

OPF - ActivitiesOPF - Activities

• Software process development andimprovement activities are coordinated acrossthe organization.

– The organization's and projects' activities fordeveloping and improving their software processes are

coordinated at the organization level.

– The use of the organization's software processdatabase is coordinated at the organizational level.

– New processes, methods, and tools used in theorganization are monitored, evaluated, and, where

appropriate, transferred to other parts of theorganization.

8/14/2019 CMMLevel3

http://slidepdf.com/reader/full/cmmlevel3 9/32

Organization ProcessOrganization Process

DefinitionDefinition

• Purpose is to develop and maintain a usable setof software process assets that improve processperformance and provide a basis for cumulative,long-term benefits.

• Involves

– Developing and maintaining the organization’sstandard software process such as descriptions of software life cycle, process tailoring guidelines andcriteria, process database and related processdocumentation.

– Defining standards for documenting standardsoftware processes and tailored software processesand revised tailored processes.

8/14/2019 CMMLevel3

http://slidepdf.com/reader/full/cmmlevel3 10/32

OPD - Common FeaturesOPD - Common Features

• Commitment

– Written organizational policy (A documented procedure)for developing and maintaining a standard softwareprocess and related process assets.

• Ability

– Providing adequate resources– Training to individuals on process definition and

maintenance.

• Measurement

– To determine the status of process definition activities.

• Verification

– By quality assurance group through review / audit.

8/14/2019 CMMLevel3

http://slidepdf.com/reader/full/cmmlevel3 11/32

OPD-activitiesOPD-activities• A standard software process for the ORGANISATION is

developed and maintained– The organization's standard software process is documented

according to established organization standards.

– The organization's standard software process is developedand maintained according to a documented procedure.

– Descriptions of software life cycles that are approved for use

by the projects are documented and maintained.– Criteria for process tailoring for projects' are developed andmaintained.

• Information related to the use of the organization’sstandard software process is collected, reviewed, andmade available

– The organization's software process database is establishedand maintained.

– A library of software process-related documentation isestablished and maintained

8/14/2019 CMMLevel3

http://slidepdf.com/reader/full/cmmlevel3 12/32

Training ProgramTraining Program

• Purpose is to develop the skills and knowledge of individuals so they can perform their roles effectivelyand efficiently.

• Involves

– Establishing a group for fulfilling the training needs of the organization

– Defining and establishing standards for training

– Identifying the training needs of the organization,projects, and individuals

– Selecting appropriate method / process for training

– Developing and/or procuring training to addressthese needs

– Evaluating the effectiveness of training imparted

8/14/2019 CMMLevel3

http://slidepdf.com/reader/full/cmmlevel3 13/32

TP - Common FeaturesTP - Common Features

• Commitment

– Written organizational policy for meeting the trainingneeds

• Ability

– Training group should exist

– Providing necessary resources– Necessary skills and knowledge to perform their

training activities

– Orientation on the training program

• Measurement

– To determine the status of the training program

– To determine the quality of the training program

8/14/2019 CMMLevel3

http://slidepdf.com/reader/full/cmmlevel3 14/32

TP - ActivitiesTP - Activities

• Training activities are planned

– Each software project develops and maintains atraining plan that specifies its training needs.

– The organization's training plan is developed andrevised according to a documented procedure.

– The training for the organization is performed in

accordance with the organization's training plan.• Training for developing the skills and knowledge needed

to perform software management and technical roles isprovided.

– Training courses prepared at the organization level are

developed and maintained according to organizationstandards.

8/14/2019 CMMLevel3

http://slidepdf.com/reader/full/cmmlevel3 15/32

TP - ActivitiesTP - Activities

• Individuals in the software engineering group and

software related groups receive the training necessary toperform the roles.

– A waiver procedure for required training is establishedand used to determine whether individuals alreadypossess the knowledge and skills required to perform

in their designated roles.– Records of training are maintained.

8/14/2019 CMMLevel3

http://slidepdf.com/reader/full/cmmlevel3 16/32

Integrated SoftwareIntegrated Software

ManagementManagement

• Purpose is to integrate the software engineeringand management activities into a defined softwareprocess, tailored from the organization’s softwareprocess assets.

• Involves

– Developing the projects defined software processby tailoring the organization’s standard softwareprocess

– Managing the software project according to thisdefined software process.

– Managing project’s size, effort, cost, schedule, staffing

and other resources.– Sharing the process data and the lessons learned

across software projects.

8/14/2019 CMMLevel3

http://slidepdf.com/reader/full/cmmlevel3 17/32

ISM - Common FeaturesISM - Common Features

• Commitment

– Written organizational policy for planning andmanaging the project

• Ability

– Adequate resources and funding

– Training on how to tailor the organization's standardsoftware process

– Training to software managers in managing thetechnical, administrative and personnel aspects of software project.

• Measurement

– To determine the effectiveness of the integratedsoftware management activities.

8/14/2019 CMMLevel3

http://slidepdf.com/reader/full/cmmlevel3 18/32

ISM - ActivitiesISM - Activities

• The project’s defined software process is a tailored

version of the ORGANISATION’S standard softwareprocess.

– The project's defined software process is developedand revised by tailoring the organization's standardsoftware process

• The project is planned and managed according to theproject’s defined software process

– The project's software development plan, whichdescribes the use of the defined software process, isdeveloped and revised according to a documented

procedure

8/14/2019 CMMLevel3

http://slidepdf.com/reader/full/cmmlevel3 19/32

ISM - ActivitiesISM - Activities

• The project is planned and managed according to the

project’s defined SOFTWRE process– The organization's software process database is usedfor software planning and estimating.

– The size of the software work products (or size of changes to the software work products) is managed

– The project's software effort and costs are managed

– The project's critical computer resources are managed

– The critical dependencies and critical paths of theproject's software schedule are managed

– The project's software risks are identified, assessed,documented, and managed

– Reviews of the software project are periodicallyperformed to determine the actions needed to bring thesoftware project's performance and results in line withthe current and projected needs of the business,customer, and end users, as appropriate

8/14/2019 CMMLevel3

http://slidepdf.com/reader/full/cmmlevel3 20/32

Software ProductSoftware Product

EngineeringEngineering

• Purpose is to consistently perform a well designedengineering process that integrate all the softwareengineering activities to produce correct, consistentsoftware products effectively and efficiently.

• Involves

– Performing the engineering tasks to build andmaintain the software using appropriate tools andmethods.

– Documentation required is developed and reviewed toensure they are appropriate for subsequent tasks.

– Revising the appropriate documents when changesare approved.

8/14/2019 CMMLevel3

http://slidepdf.com/reader/full/cmmlevel3 21/32

SPE - Common FeaturesSPE - Common Features

• Commitment

– Written organizational policy for performing softwareengineering activities.

• Ability

– Providing adequate resources

– Training to members of software engineering group to

perform their technical assignments.– Orientation to related software engineering disciplines.

– Orientation in the technical aspects of the softwareproject.

• Measurement

– To determine the functionality and quality of thesoftware products.

– To determine the status of software productengineering activities

8/14/2019 CMMLevel3

http://slidepdf.com/reader/full/cmmlevel3 22/32

SPE - ActivitiesSPE - Activities

• The software engineering tasks are defined, integrated,

and consistently performed to produce the software– Appropriate software engineering methods and tools areintegrated into the project's defined software process

– The software requirements are developed, maintained,documented, and verified by systematically analyzing theallocated requirements according to the project's defined

software process– The software design is developed, maintained, documented,and verified, according to the project's defined softwareprocess, to accommodate the software requirements and toform the framework for coding

– The software code is developed, maintained, documented,and verified, according to the project's defined softwareprocess, to implement the software requirements andsoftware design

– Software testing is performed according to the project'sdefined software process

8/14/2019 CMMLevel3

http://slidepdf.com/reader/full/cmmlevel3 23/32

SPE - ActivitiesSPE - Activities

• The software engineering tasks are defined, integrated,

and consistently performed to produce the software.– Integration testing of the software is planned and performed

according to the project's defined software process.

– System and acceptance testing of the software are plannedand performed to demonstrate that the software satisfies its

requirements– The documentation that will be used to operate and maintain

the software is developed and maintained according to theproject's defined software process

– Data on defects identified in peer reviews and testing arecollected and analyzed according to the project's defined

software process

8/14/2019 CMMLevel3

http://slidepdf.com/reader/full/cmmlevel3 24/32

SPE - ActivitiesSPE - Activities

• Software work products are kept consistent with each

other

– Consistency is maintained across software workproducts, including the software plans, processdescriptions, allocated requirements, softwarerequirements, software design, code, test plans, and

test procedures.

8/14/2019 CMMLevel3

http://slidepdf.com/reader/full/cmmlevel3 25/32

Intergroup CoordinationIntergroup Coordination

• Purpose is to establish a means for the softwareengineering group to participate actively with otherengineering groups so that the project is able tosatisfy the customer’s needs effectively andefficiently.

• Involve

– Disciplined interaction and coordination of theproject engineering groups with each other toaddress system-level requirements, objectives, andplans.

– Defining working interfaces and interactions betweenvarious engineering groups and support groups.

8/14/2019 CMMLevel3

http://slidepdf.com/reader/full/cmmlevel3 26/32

IGC - Common FeaturesIGC - Common Features

• Commitment

– Written organizational policy for establishinginterdisciplinary engineering teams

• Ability

– Adequate resources

– Support tools used by different engineering groups are

compatible– Training on team work to all managers

– Orientation in processes, methods and standards usedby various groups.

– Orientation to engineering group in working as a team.

• Measurements– To determine the status of Intergroup coordination

activities.

8/14/2019 CMMLevel3

http://slidepdf.com/reader/full/cmmlevel3 27/32

IGC - ActivitiesIGC - Activities

• The customer’s requirements are agreed to by all affected

groups.– The software engineering group and the other engineeringgroups participate with the customer and end users, asappropriate, to establish the system requirements.

• The commitments between the engineering groups areagreed to, by the affected groups.

– A documented plan is used to communicate Intergroupcommitments and to coordinate and track the workperformed.

– Critical dependencies between engineering groups areidentified, negotiated, and tracked according to adocumented procedure.

– Work products produced as input to other engineeringgroups are reviewed by representatives of the receivinggroups to ensure that the work products meet their needs.

8/14/2019 CMMLevel3

http://slidepdf.com/reader/full/cmmlevel3 28/32

IGC - ActivitiesIGC - Activities

• The engineering groups identify, track, and resolve

INTERGROUP issues.

– Representatives of the project's software engineeringgroup work with representatives of the otherengineering groups to monitor and coordinatetechnical activities and resolve technical issues.

– Intergroup issues not resolvable by the individualrepresentatives of the project engineering groups arehandled according to a documented procedure.

– Representatives of the project engineering groupsconduct periodic technical reviews and interchanges.

8/14/2019 CMMLevel3

http://slidepdf.com/reader/full/cmmlevel3 29/32

Peer ReviewsPeer Reviews

• Purpose is to remove defects from the software

work products early and efficiently. An importanteffect is to develop a better understanding of thesoftware work products and of defects that might beprevented

• Involves– Methodical examination of work products by the

producer’s peers to identify defects and areas wherechanges are needed.

– Identifying products that will undergo a peer review inthe project’s defined software process and schedule aspart of the project planning activities.

– Identifying and training the review team for performing

effective reviews.– Recording the review defects and removing them from work

products.

8/14/2019 CMMLevel3

http://slidepdf.com/reader/full/cmmlevel3 30/32

PR - Common FeaturesPR - Common Features

• Commitment

– Written organizational policy for performing peerreviews

• Ability

– Adequate resources.

– Training for peer review leaders on how to lead peerreviews

– Training for reviewers on objectives, principles andmethods of peer reviews.

• Measurements

– To determine the status of peer review activities.

8/14/2019 CMMLevel3

http://slidepdf.com/reader/full/cmmlevel3 31/32

PR - ActivitiesPR - Activities

• Peer review activities are planned

– Peer reviews are planned, and the plans aredocumented.

• Defects in the software work products are identified andremoved.

– Peer reviews are performed according to a documentedprocedure.

– Data on the conduct and results of the peer reviewsare recorded.

8/14/2019 CMMLevel3

http://slidepdf.com/reader/full/cmmlevel3 32/32

End of Defined Level (L3) KPAsEnd of Defined Level (L3) KPAs