1 / 12

SEI White Paper: Process Maturity Model

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

rheanna
Télécharger la présentation

SEI White Paper: Process Maturity Model

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

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

  2. 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

  3. Clarification of Terms • Software process • Software process capability • Expected results • Software process performance • Actual results • Software process maturity

  4. 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

  5. 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

  6. Maturity Levels in CMM

  7. 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

  8. 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

  9. 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

  10. 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

  11. 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%

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

More Related