0% found this document useful (0 votes)
20 views

Lecture 5

The document discusses the Capability Maturity Model (CMM) which is a framework used to assess an organization's software development process and provide guidelines for improvement. It describes the five levels of CMM maturity from Initial to Optimizing. Each higher level includes additional Key Process Areas that define basic requirements for effective management and quality control practices. The document provides details on the goals and focus of each maturity level and Key Process Area to give students an understanding of CMM and how it is used to enhance an organization's software development capabilities.
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
20 views

Lecture 5

The document discusses the Capability Maturity Model (CMM) which is a framework used to assess an organization's software development process and provide guidelines for improvement. It describes the five levels of CMM maturity from Initial to Optimizing. Each higher level includes additional Key Process Areas that define basic requirements for effective management and quality control practices. The document provides details on the goals and focus of each maturity level and Key Process Area to give students an understanding of CMM and how it is used to enhance an organization's software development capabilities.
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 14

Department of Computer Science

University Institute of Engineering


DEPARTMENT OF COMPUTER SCIENCE
& ENGINEERING
Bachelor of Engineering
Subject Name: Software Engineering
Subject Code: CST-220

Quality Management DISCOVER . LEARN . EMPOWER


1
Introduction to Software Engineering
Department of computer Science

Course Outcome
CO Title Level
Number

C01 Students will be able to learn how to apply  Understand


the software engineering lifecycle by
demonstrating competence in
communication, planning, analysis, design,
construction, and deployment.

C02 Students will be able to gain knowledge of Understand


software design and UI design.  

CO3 Students will be able to apply testing Understand


guidelines.

2
Department of computer Science

Chapter-8
Quality Management
• SEICMM

3
Capability maturity model (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
analyze 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.

4
Capability maturity model (CMM)

• It is based on profound feedback and development practices adopted


by the most successful organizations worldwide.

• This model describes a strategy for software process improvement


that should be followed by moving through 5 different levels.

• Each level of maturity shows a process capability level. All the levels
except level-1 are further described by Key Process Areas (KPA’s).

5
Key Process Areas 
• Each of these KPA’s defines the basic requirements that should be met
by a software process in order to satisfy the KPA and achieve that
level of maturity. 

• Conceptually, key process areas form the basis for management


control of the software project and establish a context in which
technical methods are applied, work products like models,
documents, data, reports, etc. are produced, milestones are
established, quality is ensured and change is properly managed. 

6
Levels of CMM
• The 5 levels of CMM are as follows: 
• Level-1: Initial –  
• No KPA’s defined. 
 
• Processes followed are adhoc and immature and are not well defined.
• Unstable environment for software development.
• No basis for predicting product quality, time for completion, etc.

7
Levels of CMM
• Level-2: Repeatable – 
 
• Focuses on establishing basic project management policies.
• Experience with earlier projects is used for managing new similar natured projects. 
• Project Planning- It includes defining resources required, goals, constraints, etc. for the project. It
presents a detailed plan to be followed systematically for successful completion of a good quality
software.
• Configuration Management- The focus is on maintaining the performance of the software
product, including all its components, for the entire lifecycle.
• Requirements Management- It includes the management of customer reviews and feedback
which result in some changes in the requirement set. It also consists of accommodation of those
modified requirements.
• Subcontract Management- It focuses on the effective management of qualified software
contractors i.e. it manages the parts of the software which are developed by third parties.
• Software Quality Assurance- It guarantees a good quality software product by following certain
rules and quality standard guidelines while development.
8
Levels of CMM
• Level-3: Defined – 
 
• At this level, documentation of the standard guidelines and procedures takes place.
• It is a well defined integrated set of project specific software engineering and management
processes. 
• Peer Reviews- In this method, defects are removed by using a number of review methods like
walkthroughs, inspections, buddy checks, etc.
• Intergroup Coordination- It consists of planned interactions between different development
teams to ensure efficient and proper fulfillment of customer needs.
• Organization Process Definition- It’s key focus is on the development and maintenance of the
standard development processes.
• Organization Process Focus- It includes activities and practices that should be followed to improve
the process capabilities of an organization.
• Training Programs- It focuses on the enhancement of knowledge and skills of the team members
including the developers and ensuring an increase in work efficiency.
9
Levels of CMM
• Level-4: Managed – 
 
• At this stage, quantitative quality goals are set for the organization for
software products as well as software processes.
• The measurements made help the organization to predict the product and
process quality within some limits defined quantitatively.
• Software Quality Management- It includes the establishment of plans and
strategies to develop a quantitative analysis and understanding of the
product’s quality.
• Quantitative Management- It focuses on controlling the project performance
in a quantitative manner.
10
Levels of CMM
• Level-5: Optimizing – 
 
• This is the highest level of process maturity in CMM and focuses on continuous process
improvement in the organization using quantitative feedback.
• Use of new tools, techniques and evaluation of software processes is done to prevent
recurrence of known defects. 
• Process Change Management- Its focus is on the continuous improvement of organization’s
software processes to improve productivity, quality and cycle time for the software product.
• Technology Change Management- It consists of identification and use of new technologies
to improve product quality and decrease the product development time.
• Defect Prevention- It focuses on identification of causes of defects and to prevent them
from recurring in future projects by improving project defined process. 

11
12
Department of computer Science

References

• https://www.geeksforgeeks.org/software-engineering-capability-matu
rity-model-cmm
/
• https://
www.javatpoint.com/software-engineering-institute-capability-maturi
ty-model
• https://
www.tutorialspoint.com/software_testing_dictionary/capability_matu
rity_model.htm

13
THANK YOU

14

You might also like