Capability Maturity Model. Reflection Have you ever been a part of, or observed, a “difficult” software development effort? How did the difficulty surface?

Slides:



Advertisements
Similar presentations
SOFTWARE PROCESS IMPROVEMENT “Never Stop Learning”
Advertisements

More CMM Part Two : Details.
How ISO9001 Compares with CMM Mark C. Paulk JAN,1995 CMM version 1.1 ISO9001 July 1994 presented by Zhilan Zhou.
Chapter 2 The Software Process
©2006 OLC 1 Process Management: The Foundation for Achieving Organizational Excellence Process Management Implementation Worldwide.
CPIS 357 Software Quality & Testing I.Rehab Bahaaddin Ashary Faculty of Computing and Information Technology Information Systems Department Fall 2010.
Capability Maturity Model (CMM) in SW design
1 R&D SDM 1 Software Project Management Capability Maturity Model 2009 Theo Schouten.
CMM Overview - 1 © Paul Sorenson CMPUT Software Engineering refs. IEEE Software, March 1988, 73-79, and IEEE Software, July 1993, (Capability.
Chapter 3 The Structure of the CMM
CMMI Overview Quality Frameworks.
Software Process CS 414 – Software Engineering I Donald J. Bagert Rose-Hulman Institute of Technology December 17, 2002.
Standardization. Introduction A standard is a document. It is a set of rules that control how people should develop and manage materials, products, services,
Lecture 11 CMM CSCI – 3350 Software Engineering II Fall 2014 Bill Pine.
Capability Maturity Model
Chapter : Software Process
CMMI Course Summary CMMI course Module 9..
Capability Maturity Model Integration
Integrated Capability Maturity Model (CMMI)
Capability Maturity Model Part One - Overview. History Effort started by SEI and MITRE Corporation  assess capability of DoD contractors First.
N By: Md Rezaul Huda Reza n
J. R. Burns, Texas Tech University Capability Maturity Model -- CMM n Developed by the Software Engineering Institute (SEI) in 1989 –SEI is a spinoff.
College of Engineering and Computer Science Computer Science Department CSC 131 Computer Software Engineering Fall 2006 Lecture # 1 (Ch. 1, 2, & 3)
Introduction to Software Engineering LECTURE 2 By Umm-e-Laila 1Compiled by: Umm-e-Laila.
Lecture 1 Introduction to Software Engineering
Software Engineering Lecture No:16. Lecture # 7 CMMI Fahim Khan Assistant Professor of Computer Science UOL, Sargodha
Capability Maturity Models Software Engineering Institute (supported by DoD) The problems of software development are mainly caused by poor process management.
Software Engineering Lecture # 17
Capability Maturity Model. History Effort started by SEI and MITRE Corporation  assess capability of DoD contractors First version published in.
10/16/2015Bahill1 Organizational Innovation and Deployment Causal Analysis and Resolution 5 Optimizing 4 Quantitatively Managed 3 Defined 2 Managed Continuous.
University of Sunderland CIFM03Lecture 2 1 Quality Management of IT CIFM03 Lecture 2.
Models of Quality Assessment
1 ISO 9001:2000 ISO 9001 is the creation of the International Organisation for Standardisation (ISO), a Swiss-based federation of national standards bodies.ISO.
1 © Mahindra Satyam 2009 Mahindra Satyam Confidential Welcome To CMMI Introduction.
SWEN 5130 Requirements Engineering 1 Dr Jim Helm SWEN 5130 Requirements Engineering Requirements Management Under the CMM.
Software Engineering - I
CS Process Improvement CMM Hans Van Vliet, Software Engineering, Principles and Practice, 3 rd edition, John Wiley & Sons, Chapter 6. W. Humphrey,
©Ian Sommerville 2004 Software Engineering. Chapter 28Slide 1 Chapter 28 Process Improvement.
UNIVERSITY OF MARYLAND CENTER FOR ADVANCED TRANSPORTATION TECHNOLOGY Organizational Maturity Prepared for the Operations Summit by Philip J. Tarnoff.
Process Improvement. It is not necessary to change. Survival is not mandatory. »W. Edwards Deming Both change and stability are fundamental to process.
CMMI. 1.Initial - The software process is characterized as ad hoc, and occasionally even chaotic. Few processes are defined, and success depends on individual.
CMMI FRAMEWORK SRIKANTH DEVINENI. Process failure is recognised when Project is delivered late Too much redundancy Customer complaints after delivery.
Cmpe 589 Spring 2006 Lecture 2. Software Engineering Definition –A strategy for producing high quality software.
Ch-1 Introduction The processes used for executing a software project have major effect on quality of s/w produced and productivity achieved in project…
Level 1 Level 1 – Initial: The software process is characterized as ad hoc and occasionally even chaotic. Few processes are defined, and success depends.
Page 1 The Capability Maturity Model (CMM) distinguishes between immature and mature software organizations. Immature software organizations are typically.
Process Improvement. It is not necessary to change. Survival is not mandatory. »W. Edwards Deming.
Purpose: The purpose of CMM Integration is to provide guidance for improving your organization’s processes and your ability to manage the development,
COMP 6710 Course NotesSlide 3-0 Auburn University Computer Science and Software Engineering Course Notes Set 3: Software Process Maturity Computer Science.
An Introduction. Objective - Understand the difference between CMM & CMMI - Understand the Structure of CMMI.
SOFTWARE PROCESS IMPROVEMENT
Software Engineering (CSI 321) Software Process: A Generic View 1.
COMPGZ07 Project Management CMMI Project Planning Lecture 5b Graham Collins, UCL.
The Capability Maturity Model for Software: An Overview
CMMI Overview Quality Frameworks. Slide 2 of 146 Outline Introduction High level overview of CMMI Questions and comments.
Done By: Asila AL-harthi Fatma AL-shehhi Fakhriya AL-Omieri Safaa AL-Mahroqi.
Capability Maturity Model. CS460 - Senior Design Project I (AY2004)2 Immature Organisations Software processes are often rigorously followed. Organisation.
1 These slides are designed to accompany Software Engineering: A Practitioner’s Approach, 7/e (McGraw-Hill 2009). Slides copyright 2009 by Roger Pressman.
CMMI for Services, Version 1.3
Capability Maturity Model. What is CMM? n CMM: Capability Maturity Model n Developed by the Software Engineering Institute of the Carnegie Mellon University.
CS4311 Spring 2011 Process Improvement Dr
CMMI Overview Quality Frameworks.
Software Engineering (CSI 321)
Information Technology Project Management – Fifth Edition
Level 1 Level 1 – Initial: The software process is characterized as ad hoc and occasionally even chaotic. Few processes are defined, and success depends.
CMMI Overview.
CMMI – Staged Representation
Software Engineering Lecture 16.
Capability Maturity Model
Capability Maturity Model
Presentation transcript:

Capability Maturity Model

Reflection Have you ever been a part of, or observed, a “difficult” software development effort? How did the difficulty surface? What made it difficult? How was the difficulty addressed? Was the difficulty addressed?

The “Typical” Development Problem The system is Late Over cost Lacking full functionality Doesn’t meet specifications

Characteristics of Immature Development No general understanding of the process or how a specific activity fits Not documented Not disseminated No faith in the process “I have to take care of everything” No measurement of efficiency or effectiveness No way to judge success No way to address problems No way to clearly identify needs e.g., infrastructure for development

Characteristics of Immature Development Grab the FIRE HOSE Reactionary A lack of control

Control Required Elements: A well-defined goal state A correct picture of the current state An ability to compare the two states An ability to draw a valid conclusion based upon the comparison An ability to design appropriate change An ability to implement the change Absence of any one element restricts control

Characteristics of Mature Development Processes are known Responsibilities are clear Players have confidence in the process framework They are disciplined

From Whence CMM Came? Carnegie Mellon University chosen by US government to head effort to improve software and systems development Note: CMM seeks to improve the development PROCESS not the product of the process

Software Engineering Institute Established by the US government (DoD) Housed at Carnegie Mellon University See “Its core purpose is to help organizations improve their software engineering capabilities and develop or acquire the right software, defect free, within budget and on time, every time.”

CMMI Institute Oversight of CMMI transferred to the CMMI Institute Still housed at CMU For more information, see

From Whence It Came? Watts Humphrey, formerly of IBM, at the forefront Deming’s Total Quality Management

TQM The application of quantitative methods and human resources to improve the materials and services provided as inputs to an organization and to improve all of the processes within the organization

Where Does the Customer Fit? CMM sees the client in a contractual relationship, a part of the process User satisfaction is not THE direct, stated goal of CMM IS that expectation reasonable?

Pillars of the CMM Model Based on actual practices Reflects the best state of the practices Reflects needs of individuals performing software process improvement and software process appraisals Documented Publicly available

Some Definitions Process Sequence of steps to accomplish a given purpose Software process Set of activities, methods, practices and transformations used to develop and maintain software

Some Definitions Software process capability Range of anticipated results from the process Software process performance Actual results achieved through applying the process Software process maturity Degree to which the process is Defined Managed Measured Controlled Effective

CMM Addresses... Processes How they exist and are changed People Attitudes toward and involvement in the process and its structure Technology Why and how technology is introduced to support the process Measurement How data about the process and product are obtained and used

CMM Models Continuous Model Focuses on individual process areas Reflected in “capability” levels Useful for internal improvement Staged Model Focuses on the entire model Reflected in “maturity” levels Applicable with external appraisals

Maturity Levels A specified stage in moving toward a “mature software process” An indicator of maturity, an organization’s capability to produce software in an organized and predictable manner allowing for improvements to the development process A status symbol?

The CMM for Software (SW-CMM) The Five Maturity Levels Initial Repeatable Defined Managed Optimizing

The CMM for Software (SW-CMM) From The Capability Maturity Model: Guidelines for Improving the Software Process

Initial Level One Software process is Ad hoc Chaotic Undefined Tied to individual standards

The CMM for Software (SW-CMM) From The Capability Maturity Model: Guidelines for Improving the Software Process

Repeatable Level Two Processes track cost, schedule and functionality Can repeat the process on a like development project

The CMM for Software (SW-CMM) From The Capability Maturity Model: Guidelines for Improving the Software Process

Defined Level Three Processes for engineering AND management are Documented Standardized Integrated ALL processes follow the standard, that has been tailored to the organization, for development and maintenance

The CMM for Software (SW-CMM) From The Capability Maturity Model: Guidelines for Improving the Software Process

Managed Level Four Detailed measures are collected for The development/maintenance process The quality of the software product Process and product control is based on quantitative analysis of measurement results For a survey of software assurance measurement, see 013_004_001_72891.pdf 013_004_001_72891.pdf

The CMM for Software (SW-CMM) From The Capability Maturity Model: Guidelines for Improving the Software Process

Optimizing Level Five Improvement is continuous through ongoing feedback and modification of the process New ideas and technologies are explored and evaluated through measurements

Management View Improves From The Capability Maturity Model: Guidelines for Improving the Software Process

Progress Through Levels Progress through levels should be linear Skipping a level is difficult e.g., it is difficult to measure and compare against a standard (level 4) unless the standards have been identified (level 3) Specific exploratory use of a higher level may give insight into the migration path through the levels, but it will be difficult without a firm underlying foundation

The Structure of CMM Maturity Levels Indicate process capability Contain Key Process Areas Achieve Goals Organized by Common Features Address implementation or institutionalization Contain Key Practices Describe activities of infrastructure

From Capability Maturity Model for Software, Version 1.1 – Fig 3.3 An example of the structure of CMM

Expected Results of CMM Improved predictability Time, cost, people, Improved control Improved effectiveness (quality)

Expected Results of CMM From The Capability Maturity Model: Guidelines for Improving the Software Process

CMMI(ntegrated) CMM, as a foundation, is now applied to different organizational processes: CMMI-Software Engineering (SW) Developing software systems Systems Engineering (SE) Systems which may or may not involve software

CMMI(ntegrated) CMM, as a foundation, is now applied to different organizational processes: Integrated Product and Process Development (IPPD) An extension of other selected approach(es) with emphasis on integration with other processes Supplier Sourcing (SS) When project development incorporates suppliers into the project

CMMI(ntegrated) These areas are now placed in three categories: CMMI-DEV engineering and development processes in an organization that develops products CMMI-SVC management and service delivery processes CMMI-ACQ supplier management processes

CMMI As different CMM models were developed for these areas, CMMI integrates the models into one common structure CMMI varies from CMM

Comparison of Levels CMM Initial Repeatable Defined Managed Optimizing CMMI Initial Managed Defined Quantitatively managed Optimizing

CMM / CMMI An extensive mapping of components between the models is availableextensive mapping

Assessing Your Level SCAMPI – Standard CMMI Appraisal Method for Process Improvement Assessments may be done internally or by an external SCAMPI Lead Appraiser SEI provides training to become a Lead Appraiser

Where Do Organizations Stand? See annual profiles of organizations seeking SCAMPI appraisals at maturity-profiles/ maturity-profiles/

Criticisms of CMM/CMMI CMM is not comprehensive enough Does not address reuse Does not completely describe the real development world High cost to progress through CMM There is a risk of failure (no ROI) May lead to bureaucratic rigidity Capable and Mature? By Gary H. Anthes, ComputerWorld, Dec 15, 1997

Support for CMM Establishes a common framework for addressing the software development process Provides an object assessment method of an organization’s development process Is based upon substantial experiences by a variety of organizations

The Complete Picture For the complete description of CMMI- DEV, see /10tr033.pdf /10tr033.pdf