8/14/2019 CMMLevel2

1/28

CAPABILITY MATURITY MODELfor Software (CMM)

Version 1.1Maturity Level 2 (RepeatableMaturity Level 2 (Repeatable

Level)Level)

8/14/2019 CMMLevel2

2/28

Characteristics of Level2Characteristics of Level2

organizationsorganizations

Planning and managing projects is based on experiencewith similar projects

Software project management processes aredocumented and followed

Organizational policies guide the projects inestablishing management processes

Successful practices developed on earlier projectscan be repeated

Data available are primarily related to size, effort and

schedule which are shared across projects throughinformal practices

8/14/2019 CMMLevel2

3/28

Key process areas - level 2Key process areas - level 2

Requirements management (RM)Requirements management (RM)

Software project planning (SPP)Software project planning (SPP)

Software project tracking and oversight (SPTO)Software project tracking and oversight (SPTO)

Software subcontract management (SSCM)Software subcontract management (SSCM)

Software quality assurance (SQA)Software quality assurance (SQA)

Software configuration management (SCM)Software configuration management (SCM)

8/14/2019 CMMLevel2

4/28

Requirements ManagementRequirements Management

Purpose

Establish a common understanding betweencustomer requirements and software project

This agreement with the customer is the basis forplanning the software project.

Following an effective change control process

RM involves Document and control of customer requirements

(technical and non-technical)

Keeping plans, products, and activities consistentwith the requirements

Reviewing the initial and revised system requirementsallocated

(Note : customer can be system engineering group,marketing group, another internal organization, or anexternal organization.)

8/14/2019 CMMLevel2

5/28

RM Goals & ActivitiesRM Goals & Activities

Goal 1 - allocated requirements are controlled toestablish baseline

Software engineering group reviews allocatedrequirements before they are incorporated into theproject

Goal 2 - software plans, products, activities are keptconsistent with the allocated requirements

Software engineering group uses the allocatedrequirements as the basis for software plans, work

products and activities. Changes to the allocated requirements are reviewedand incorporated into the software project

8/14/2019 CMMLevel2

6/28

RM Common FeaturesRM Common Features

Commitment Written organizational policy for managing systemrequirements

Ability

For each project, responsibility is established foranalyzing documenting requirements

Allocated requirements are documented

Adequate resources and funding are provided formanaging the allocated requirements

Members of the software engineering group and othersoftware related groups are trained to perform their RM

activities Measurements

Measurements are made and used to determine thestatus of the activities for managing the allocatedrequirements

8/14/2019 CMMLevel2

7/28

Software Project PlanningSoftware Project Planning

Purpose is to establish reasonable plans forperforming the software engineering and formanaging the software project

Involves

Developing estimates(size, cost, effort, schedule &resources) for the work to be performed

Establishing the necessary commitments

Defining the plan to perform the work

Using the plan as the basis for performing and

managing projects activities Assessing the risks

8/14/2019 CMMLevel2

8/28

SPP Common FeaturesSPP Common Features

Commitments

A project software manager is designated to beresponsible for project activities

Written organizational policy for planning a softwareproject

Ability

Approved statement of work

Responsibilities for developing softwaredevelopment plan

Resources and funding

Training on software estimation and planning

Measurements

To determine status of activities pertaining tosoftware planning

8/14/2019 CMMLevel2

9/28

SPP Goals & ActivitiesSPP Goals & Activities

Software estimates are documented for use in planningand tracking of software projects.

Estimates for size (or changes to size), effort andcost, critical computer resources, software scheduleare derived according to a documented procedure.

Software planning data are recorded.

Software project activities and commitments areplanned and documented.

Project planning is initiated in the early stages

A software life cycle with predefined stages ofmanageable size is defined

Software development plan is defined according to adocumented procedure and documented

Software work products are identified

8/14/2019 CMMLevel2

10/28

SPP Goals & ActivitiesSPP Goals & Activities

Software project activities and commitments are

planned and documented. Risks associated with cost, resource, schedule and

technical aspects of the software project areidentified, assessed and documented.

Plan for software engineering facilities and support

tools are prepared Affected groups and individuals agree to theircommitments Related to the software project.

Software engineering group participates in theproject proposal team and with other groups in theoverall project planning.

Project commitments made to individuals and groupsexternal / internal to the organization are reviewedwith senior management according to a documentedprocedure

8/14/2019 CMMLevel2

11/28

Software Project TrackingSoftware Project Tracking

and Oversightand Oversight

Purpose is to provide adequate visibility intoactual progress so that management can takeeffective actions when performance deviatessignificantly from the plan.

Involves

Tracking and reviewing software accomplishmentsand results against documented estimates,commitments, and plans.

Adjusting plans based on actual accomplishmentsand results.

When plans are not being met, take corrective

actions by re-planning or taking actions to improvethe performance

8/14/2019 CMMLevel2

12/28

SPTO - Common FeaturesSPTO - Common Features Commitment

Project software manager is designated to beresponsible for the projects activities and results.

Written organizational policy for managing softwareprojects

Ability

Software development plan is documented and

approved Responsibility for every work product is assigned

explicitly

Resources and funding for tracking

Training on technical and personnel on software

project Orientation on technical aspects of the project for

software managers.

Measurements

To determine the status of project tracking activities

8/14/2019 CMMLevel2

13/28

SPTO Goals & ActivitiesSPTO Goals & Activities Actual results and performances are tracked against the

software plans.

A documented SDP is used

The size of the work product, effort and cost, criticalcomputer resources, software schedule, softwareengineering and technical activities are tracked andcorrective action taken when necessary.

Risks associated with cost, resource, schedule andtechnical aspects are tracked

Actual measurement data and re-planning data arerecorded

Software engineering group conducts periodic internal

reviews and track technical progress, plan,performance, and issues against the softwaredevelopment plan.

Formal reviews to address the accomplishments andresults of the project are conducted at selected projectmilestones according to a doc.Proc

8/14/2019 CMMLevel2

14/28

Corrective actions are taken and managed to closure whenactual results and performance deviate significantly fromthe software plans. The projects software development plan is revised

The size of the work products, changes to size, effort andcosts, critical computer resources, software schedule andengineering technical activities are tracked and correctiveactions are taken as necessary.

Actual measurement data and re-planning data for thesoftware project are recorded.

Changes to software commitments are agreed to by theaffected groups and individuals. Software project commitments and changes to commitments

made to individuals and groups external to the organizationare reviewed with senior management

Approved changes to commitments that affect the softwareproject are communicated to the members of the SEG andother software related groups.

SPTO Goals & ActivitiesSPTO Goals & Activities

8/14/2019 CMMLevel2

15/28

Changes to software commitments are agreed to by theaffected groups and individuals.

Software project commitments and changes tocommitments made to individuals and groupsexternal to the organization are reviewed with senior

management according to a documented procedure. Approved changes to commitments that affect the

software project are communicated to the membersof the software engineering group and othersoftware related groups.

SPTO Goals & ActivitiesSPTO Goals & Activities

8/14/2019 CMMLevel2

16/28

Software S/C ManagementSoftware S/C Management

Purpose is to select qualified software subcontractorsand manage them effectively

Involves

Selecting a software subcontractor.

Establishing plans, requirements , standards andcommitments with the subcontractor.

Tracking and reviewing the subcontractorsperformance and result.

Managing a software sub contractor and managing thesoftware component that is sub contracted whichincludes software and hardware.

Performing tracking and oversight activities for thesubcontracted work.

Ensuring that the software products delivered by thesubcontractor satisfy the acceptance criteria.

8/14/2019 CMMLevel2

17/28

SSM - Common FeaturesSSM - Common Features

Commitment

Written organizational policy for managing thesoftware sub contract.

A sub contract manager is designated to beresponsible for establishing and managing thesoftware sub contract.

Ability Adequate resources and funding

Training for those who manage sub contract activityon performing sub contract related activities andtechnical aspects.

Measurements To determine the status of the activities for

managing the software sub contract.

8/14/2019 CMMLevel2

18/28

SSM - ActivitiesSSM - Activities

The prime contractor selects qualified software subcontractors

The work to be sub contracted is defined and plannedaccording to a documented procedure.

The software subcontractor is selected, based on anevaluation of the subcontract bidders ability to perform

the work, according to a documented procedure. The prime contractor and the software subcontractor agree

to their commitments to each other

The contractual agreement between the primecontractor and the software subcontractor is used as the

basis for managing the subcontract. A documented subcontractors software development

plan is reviewed and approved by the prime contractor

8/14/2019 CMMLevel2

19/28

Prime contractor and the software subcontractor agree

to their commitments to each other. Changes to the software subcontractors statement

of work, subcontract terms and conditions and othercommitments are resolved according to adocumented procedure

The prime contractor and the software subcontractormaintain ongoing communications.

The prime contractor's management conductsperiodic status/ coordination reviews with thesoftware subcontractors management

Periodic technical reviews and interchanges are held

with the software subcontractor.

SSM - ActivitiesSSM - Activities

8/14/2019 CMMLevel2

20/28

Software Quality AssuranceSoftware Quality Assurance

Purpose is to provide management with appropriate

visibility into the process being used and the productsbeing built.

Involves

Establishing a quality assurance group who hasrequired independence.

Participation of SQA in establishing the plans,standards and procedures for the project.

Reviewing and auditing the software products andactivities to ensure that they comply with theapplicable procedures and standards.

Providing the software project and otherappropriate managers with the results of thosereviews and audits.

Escalating unresolved issues to an appropriate level ofmanagement.

8/14/2019 CMMLevel2

21/28

SQA - Common FeaturesSQA - Common Features

Commitment

Written organizational policy for implementing softwarequality assurance

Ability

A group that is responsible for coordinating andimplementing SQA for the project exists

Adequate resources and funding Members of SQA group are trained to perform their SQAactivities.

Orientation to members of the projects on SQA activitiesand roles and responsibilities

Measurement

To determine the status, cost and schedule of SQAactivities.

Verification

Experts independent of the SQA group periodically reviewthe activities of SQA group

8/14/2019 CMMLevel2

22/28

SQA Goals & ActivitiesSQA Goals & Activities

Software quality Assurance activities are planned

A SQA plan is prepared for the software project accordingto a documented procedure.

The SQA groups activities are performed in accordancewith the SQA plan.

Adherence of software products and activities to be applicablestandards, procedures, and requirements is verifiedobjectively. The SQA groups activities are performed in accordance

with the SQA plan

The SQA group participates in the preparation and reviewof the projects software development plan, standards and

procedures. The SQA group reviews the software engineering activitiesto verify compliance

The SQA group audits designated software work products toverify compliance.

8/14/2019 CMMLevel2

23/28

SQA Goals & ActivitiesSQA Goals & Activities

Affected groups and individuals are informed ofsoftware quality assurance activities and results.

The SQA group periodically reports the results of itsactivities to the software engineering group.

Deviations identified in the software activities and

software work products are documented and handledaccording to a documented procedure.

The SQA group conducts periodic reviews of itsactivities and findings with customers SQApersonnel, as appropriate.

8/14/2019 CMMLevel2

24/28

Software ConfigurationSoftware Configuration

ManagementManagement

Purpose is to establish and maintain the integrityof the products of the software project throughoutthe software life cycle.

Involves

Establishing a group for managing configuration

management activities for a project.

Identifying configuration items/units.

Establishing baselines as they are developed.

Systematically controlling changes through change

control and baseline audits. Maintaining integrity and traceability of theconfiguration throughout the software life cycle.

8/14/2019 CMMLevel2

25/28

SCM Common FeaturesSCM Common Features

Commitment A written organizational policy for implementing

SCM.

Ability

A software configuration control board exists.

SCM group for a project exist Adequate resources and funding

Training to SCM group on objectives, proceduresand methods of performing SCM activities.

Training to software engineering group to perform

SCM activities Measurements

To determine the status of the SCM activities

8/14/2019 CMMLevel2

26/28

SCM Goals & ActivitiesSCM Goals & Activities

Software configuration management activities are

planned. A SCM plan is prepared for each software project according to

a documented procedure. (Part of SDP in Tarang)

A documented and approved SCM plan is used as the basisfor performing the SCM activities.

Selected software work products are identified, controlled,and available. A documented and approved SCM plan is used as the basis

for performing the SCM activities.

A configuration management library system is established asa repository for the software baselines.

The software work products to be placed under configurationmanagement are identified.

Products from the software baseline library are created andtheir release is controlled according to a documentedprocedure

8/14/2019 CMMLevel2

27/28

SCM Goals & ActivitiesSCM Goals & Activities

Changes to identified software work products are

controlled. Change requests and problem reports for all configuration

items/units are initiated, recorded, reviewed, approved, andtracked according to a documented procedure.

Changes to baselines are controlled according to adocumented procedure.

Affected groups and individuals are informed of the statusand content of software baselines.

The status of configuration items/units is recorded accordingto a documented procedure.

Standard reports documenting the SCM activities and thecontents of the software baseline are developed and madeavailable to affected groups and individuals.

Software baseline audits are conducted according to adocumented procedure.

8/14/2019 CMMLevel2

28/28

End of Repeatable Level (L2) KPAsEnd of Repeatable Level (L2) KPAs