SEI White Paper: Process Maturity Model Present by Hui Huang November 16, 2000 ® CMM is Registered in the US Patent and Trademark Office.

Slides:



Advertisements
Similar presentations
Requirements Engineering Processes – 2
Advertisements

Copyright © 2003 by Cooliemon TM, LLC 1 Causal Analysis & Resolution (CAR) at Level 1 Presenter: Ralph Williams, President SEI Authorized CBA IPI Lead.
SOFTWARE PROCESS IMPROVEMENT “Never Stop Learning”
DataSource & SEI’s Capability Maturity Model (CMM ® )
SEP1 - 1 Introduction to Software Engineering Processes SWENET SEP1 Module Developed with support from the National Science Foundation.
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.
SE 470 Software Development Processes James Nowotarski 12 May 2003.
Capability Maturity Model (CMM) in SW design
Computer Engineering 203 R Smith Process/Plan Model 7/ Development Process Models Development Process Models are different ways to look at the processes.
Capability Maturity Model (CMM) Done By :Delayel Alhajeree.
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.
Organizational Project Management Maturity: Roadmap to Success
Lecture 11 CMM CSCI – 3350 Software Engineering II Fall 2014 Bill Pine.
Capability Maturity Model
Project Management Methodology More about Quality Control.
Integrated Capability Maturity Model (CMMI)
Customized for the Seattle Area Software Quality Assurance Group Dave Brandes People Capability Maturity Model Services The Boeing Company July 19, 2001.
Capability Maturity Model. Reflection Have you ever been a part of, or observed, a “difficult” software development effort? How did the difficulty surface?
Software Engineering II Lecture 1 Fakhar Lodhi. Software Engineering - IEEE 1.The application of a systematic, disciplined, quantifiable approach to the.
Comparing CMMI® and OPM3®
Model-Based Process Improvement Module 2. Module Objectives This module will enable students to recall information about the history of CMMI fundamentals.
Capability Maturity Model Part One - Overview. History Effort started by SEI and MITRE Corporation  assess capability of DoD contractors First.
Software testing techniques Testing Maturity Model Presentation on the seminar Kaunas University of Technology.
N By: Md Rezaul Huda Reza n
1 Chapter 2 The Process. 2 Process  What is it?  Who does it?  Why is it important?  What are the steps?  What is the work product?  How to ensure.
J. R. Burns, Texas Tech University Capability Maturity Model -- CMM n Developed by the Software Engineering Institute (SEI) in 1989 –SEI is a spinoff.
CMMi What is CMMi? Basic terms Levels Common Features Assessment process List of KPAs for each level.
Software Engineering - Spring 2003 (C) Vasudeva Varma, IIITHClass of 39 CS3600: Software Engineering: Standards in Process Modeling CMM and PSP.
Software Engineering Lecture # 17
University of Sunderland CIFM03Lecture 2 1 Quality Management of IT CIFM03 Lecture 2.
Quality Concepts within CMM and PMI G.C.Reddy
Models of Quality Assessment
Georgia Institute of Technology CS 4320 Fall 2003.
SWEN 5130 Requirements Engineering 1 Dr Jim Helm SWEN 5130 Requirements Engineering Requirements Management Under the CMM.
CMMI. 1.Initial - The software process is characterized as ad hoc, and occasionally even chaotic. Few processes are defined, and success depends on individual.
Requirements Development in CMMI
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.
PMI is a registered trademark of the Project Management Institute Knowledge Exchange Forum October 28, 2003 Assessing Project Management in Your Organization.
1 SEI Capability Maturity Model Advanced Software Engineering COM360 University of Sunderland © 2000.
Testing Maturity Model (TMM). Introduction For the past decade, the software industry has put substantial effort in improving the quality of its products.
COMP 6710 Course NotesSlide 3-0 Auburn University Computer Science and Software Engineering Course Notes Set 3: Software Process Maturity Computer Science.
Paper Title Authors names Conference and Year Presented by Your Name Date.
SOFTWARE PROCESS IMPROVEMENT
Introduction to the Personal Software Process. Overview Process Fundamentals PSP Concepts and Structure PSP Planning and Measurement PSP Quality Management.
Pittsburgh, PA CMMI Acquisition Module - Page M5-1 CMMI ® Sponsored by the U.S. Department of Defense © 2005 by Carnegie Mellon University This.
Software Engineering (CSI 321) Software Process: A Generic View 1.
Project Management Strategies Hidden in the CMMI Rick Hefner, Northrop Grumman CMMI Technology Conference & User Group November.
UNIT 5.
The Software Process CpSc 372: Introduction to Software Engineering Jason O. Hallstrom Authorship Disclaimer. These slides are intended.
CMMI Overview Quality Frameworks. Slide 2 of 146 Outline Introduction High level overview of CMMI Questions and comments.
Cmpe 589 Spring Fundamental Process and Process Management Concepts Process –the people, methods, and tools used to produce software products. –Improving.
CMMI for Services, Version 1.3
PROCESS ASSESSMENT AND IMPROVEMENT. Process Assessment  A formal assessment did not seem financially feasible at the onset of the company’s process improvement.
Capability Maturity Model. What is CMM? n CMM: Capability Maturity Model n Developed by the Software Engineering Institute of the Carnegie Mellon University.
Software Engineering (CSI 321)
Capability Maturity Model Integration (CMMI)
Tor Stålhane IDI / NTNU Geir Skylstad SINTEF / IKT
Software Engineering Lecture 16.
Capability Maturity Model
Acknowledgment of achievement
Using the CMM. Using the CMM Maturity Levels CMM History.
Capability Maturity Model
PROJECT MANAGEMENT MATURITY MODEL (PMMM)
Requirements Development in CMMI
Presentation transcript:

SEI White Paper: Process Maturity Model Present by Hui Huang November 16, 2000 ® CMM is Registered in the US Patent and Trademark Office

Overview of the article (CMM for Software) Overview of CMM Background discussion: Why CMM is crucial Developing History Detailed Summary Description of Uses for Process Improvement Evaluation of software supplier Pros and Cons State of Practices and Future Directions

Clarification of Terms Software process Software process capability Expected results Software process performance Actual results Software process maturity

What is CMM ? A SEI Patent A Five-Level Hierarchical Model A set of known GMPs and an improvement strategy for building consistent and predictable software products

Why CMM is crucial Determine the current process maturity level Identify a vital few issues Focus on limited set of activities Enable steady, continual and lasting gains

Maturity Levels in CMM Maturity Level FocusKPAs (e.g.) 5 Optimizing Continue Process Improvement Change Management 4 Managed Product and Process Quality Quality Management 3 Defined Engineering Process & Organizational Support Product Engineering 2 Repeatable Project Management Processes SCM, QA/QC 1 Initial Competent People and heroics

Key Process Areas (KPAs) Each KPA identifies a cluster of related activities that achieve a set of goals considered important for process capability The path of a key process may differ

The IDEAL approach to using the CMM The five phase of the IDEAL approach I: Initiating (the groundwork) D: Diagnosing (the distance to the goal) E: Establishing ( the plan) A: Acting (doing the work) L: Learning (from the experience) CMM is part of the IDEAL approach

Cons: CMM is Not comprehensive non-software disciplines are not addressed Counter-argument: CMM is deliberately focused on software process CMM is Difficult to Understand The solution is for Large organization The maturity levels oversimplifies issues The KPAs are static

Pros Normative components are short: 18 KPAs and 52 Goals organized in hierarchical model CMM has been reviewed by many software developers and has many successful applications Training available from SEI and authorized distribution partners

State of the Practices In 1989, 90% of the organization assessed are at level one and only 1 at level 5 In 1999, >70 of the organization assessed are at level 4 or 5 Commercial Users: 60% Government/Military Users: 40%

Suggested Reading Paulk Mark et al The Capability Maturity Model: Guidance for Improving the Software Process Questions ?