The document discusses the Capability Maturity Model (CMM) developed by the Software Engineering Institute (SEI) to enhance software quality management through a structured framework. It outlines five maturity levels from 'Initial' to 'Optimizing,' detailing the characteristics and key process areas (KPAs) at each level. The document also emphasizes the importance of systematic processes and the role of training and measurement in achieving software process improvement.

1. Software Project Management
Unit No 4
The SEI Capability Maturity Model CMM)
Lecture No. 10
Mr. Suraj Sharma
Assistant Professor, CSA/SOET

2. Outlines
• Prerequisite of topic
• Problem Objective
• Introduction
• CMM
• Software Quality Model
• Assignment
• Learning Outcomes
• Student Effective Learning Outcome
• References

3. Prerequisite of topic
To understand the CMM the knowledge of basic software management
concepts is required.

4. Problem Objective
The objective is to provide systematic and disciplined approach towards the
Quality Management of software with the help of Software engineering
concepts.

5. Introduction
Software Engineering Institute (SEI) developed Capability Maturity Model
(CMM)
CMM describes the prime elements - planning, engineering, managing
software development and maintenance CMM can be used for
• Software process improvement
• Software process assessment
• Software capability evaluations
SELO: 1,8 Reference No.: R1, R2, R3

6. O: 1,8 Reference No.: R1, R2
CMM
SEL , R3

7. CMM
CMM was developed by the Software Engineering Institute (SEI) at
Carnegie Mellon University in 1987.
•It is not a software process model. It is a framework which is used to
analyse the approach and techniques followed by any organization to
develop software products.
•It also provides guidelines to further enhance the maturity of the process
used to develop those software products.
SELO: 1,8 Reference No.: R1, R2, R3

8. CMM – Common Features
Common features are attributes that indicate whether the implementation
and institutionalization of KPAs are effective, repeatable, and lasting.
These are:
1. Commitment to Perform (CO) - Describes the actions the organizations
must take to ensure that the process is established and will endure. It
includes practices on policy and leadership.
2. Ability to Perform (AB) – Describes the preconditions that must exist. It
includes practices on resources, organizational structure, training and
tools.
3. Activities Performed (AP) – Describes role and procedures necessary to
implement a KPA.
4. Measurement and Analysis (ME) – Describes the need to measure the
process and analyze the measurements.
5. Verifying Implementation (VE) – Reviews, audits etc.
SELO: 1,8 Reference No.: R1, R2, R3

9. CMMI
CMMs were developed for disciplines such as System Engineering (SE-CMM),
People Management (PCMM), Software Acquisition (SA-CMM) etc.
• CMMI is generalized to be applicable to many domains using a single framework;
thus making CMMI much more abstract – all the terminologies used are very
generic in nature, and even the word software does not appear in the definition
document of CMMI.
• CMMI, however, follows same five levels of maturity. The KRAs are more or
less on the similar lines with slight modifications to make them generic.
SELO: 1,8 Reference No.: R1, R2, R3

10. CMM – Level 1 – Initial Level
The organization
•Does not have an established and documented environment for developing
and maintaining software.
•Haphazard activities by the members of the project team
•No systematic project management process
•At the time of crises, projects usually stop using all planned procedures and
revert to coding and testing.
•Adhoc Processes (No formal process)
•Success, if any, depends on heroic actions of few members in the team -
Individual dependent outcomes
SELO: 1,8 Reference No.: R1, R2, R3

11. CMM – Level 2 – Repeatable level
Effective management process having established which can be
• Practiced
• Documented
• Enforced
•Trained
• Measured
• Improvised KPAs:
1.Requirements Management (RM)
2. Software Project Planning (PP)
3. Software Project Tracking and Oversight (PT)
4. Software Subcontractor Management (SM)
5. Software Quality Assurance (QA)
6. Software Configuration Management (CM)
SELO: 1,8 Reference No.: R1, R2, R3

12. CMM – Level 3 – Defined level
•Standard defined software engineering and management process for
developing and maintaining software.
•These processes are put together to make a coherent whole – organization-
wide understanding of activities, roles, and responsibilities.
KPAs:
7. Organization Process Focus (PF)
8. Organization Process Definition (PD)
9. Training Program (TP)
10. Integrated Software Management (IM)
11.Software Product Engineering (PE)
12. Inter group Coordination (IC)
13. Peer Reviews (PR)
SELO: 1,8 Reference No.: R1, R2, R3

13. CMM – Level 4 – Managed level
•Quantitative goals set for both software products and processes.
•The organizational measurement plan involves determining the productivity
and quality for all important software process activities across all projects.
KPAs:
14. Quantitative Process Management (QP)
15. Software Quality Management (QM)
SELO: 1,8 Reference No.: R1, R2, R3

14. CMM – Level 5 – Optimizing level
Organizations working at this level not only collect process and product
metrics, but analyze them to identify scopes for improving and optimizing
the various development (engineering) and management activities. Lessons
learnt from specific projects are incorporated in relevant processes.
Emphasis laid on
•Process improvement
•Tools to identify weaknesses existing in their processes
•Make timely corrections
•Identification and use of latest tools and technologies including
assimilation of innovative ideas. KPAs:
16. Defect Prevention (DP)
17. Technology Change Management (TM)
18. Process Change Management (PC)
SELO: 1,8 Reference No.: R1, R2, R3

15. Assignment
1. What do you mean by SEI Capabilities CMM.

16. Learning Outcomes
The main purpose behind the topic is to provide the knowledge about
the software quality concepts which will help to develop the software.

17. References
1. R. S. Pressman, “Software Engineering –Apractitioner’s approach”.
2. Pankaj Jalote “Software Engg” Narosa Publications.
3. Ian Sommerville : Software Engineering 6/e (Addison-Wesley).

18. SELO
1.Ability to solve problems through application of theoretical & practical
concept.
2. Critical & innovative thinking skills.
7. Ability to develop emotional quotient to be socially intelligent.
9. Application of concepts of topic & it’s technological application.
.