Capability Maturity ModelSM - SEI Digital Library .Figure 2.2 The Juran Trilogy Diagram: Quality

  • View
    212

  • Download
    0

Embed Size (px)

Text of Capability Maturity ModelSM - SEI Digital Library .Figure 2.2 The Juran Trilogy Diagram: Quality

  • Technical ReportCMU/SEI-93-TR-024ESC-TR-93-177February 1993

    Capability Maturity ModelSM

    for Software, Version 1.1

    Mark C. Paulk

    Bill Curtis

    Mary Beth Chrissis

    Charles V. Weber

  • Software Engineering InstituteCarnegie Mellon University

    Pittsburgh, Pennsylvania 15213

    Unlimited distribution subject to the copyright.

    Technical ReportCMU/SEI-93-TR-024

    ESC-TR-93-177February 1993

    Capability Maturity ModelSM

    for Software, Version 1.1

    Mark C. Paulk

    Bill Curtis

    Mary Beth Chrissis

    Charles V. Weber

  • This report was prepared for the

    SEI Joint Program OfficeHQ ESC/AXS5 Eglin StreetHanscom AFB, MA 01731-2116

    The ideas and findings in this report should not be construed as an official DoD position. It is published in theinterest of scientific and technical information exchange.

    FOR THE COMMANDER

    (signature on file)

    Thomas R. Miller, Lt Col, USAFSEI Joint Program Office

    This work is sponsored by the U.S. Department of Defense.

    Copyright 1996 by Carnegie Mellon University.

    Permission to reproduce this document and to prepare derivative works from this document for internal use isgranted, provided the copyright and No Warranty statements are included with all reproductions and derivativeworks.

    Requests for permission to reproduce this document or to prepare derivative works of this document for externaland commercial use should be addressed to the SEI Licensing Agent.

    NO WARRANTY

    THIS CARNEGIE MELLON UNIVERSITY AND SOFTWARE ENGINEERING INSTITUTE MATERIALIS FURNISHED ON AN AS-IS BASIS. CARNEGIE MELLON UNIVERSITY MAKES NO WARRAN-TIES OF ANY KIND, EITHER EXPRESSED OR IMPLIED, AS TO ANY MATTER INCLUDING, BUT NOTLIMITED TO, WARRANTY OF FITNESS FOR PURPOSE OR MERCHANTIBILITY, EXCLUSIVITY, ORRESULTS OBTAINED FROM USE OF THE MATERIAL. CARNEGIE MELLON UNIVERSITY DOESNOT MAKE ANY WARRANTY OF ANY KIND WITH RESPECT TO FREEDOM FROM PATENT,TRADEMARK, OR COPYRIGHT INFRINGEMENT.

    This work was created in the performance of Federal Government Contract Number F19628-95-C-0003 withCarnegie Mellon University for the operation of the Software Engineering Institute, a federally funded researchand development center. The Government of the United States has a royalty-free government-purpose license touse, duplicate, or disclose the work, in whole or in part and in any manner, and to have or permit others to do so,for government purposes pursuant to the copyright license under the clause at 52.227-7013.

    This document is available through Research Access, Inc., 800 Vinial Street, Pittsburgh, PA 15212.Phone: 1-800-685-6510. FAX: (412) 321-2994. RAI also maintains a World Wide Web home page. The URL ishttp://www.rai.com

    Copies of this document are available through the National Technical Information Service (NTIS). For informa-tion on ordering, please contact NTIS directly: National Technical Information Service, U.S. Department ofCommerce, Springfield, VA 22161. Phone: (703) 487-4600.

    This document is also available through the Defense Technical Information Center (DTIC). DTIC provides ac-cess to and transfer of scientific and technical information for DoD personnel, DoD contractors and potential con-tractors, and other U.S. Government agency personnel and their contractors. To obtain a copy, please contactDTIC directly: Defense Technical Information Center, Attn: FDRA, Cameron Station, Alexandria, VA 22304-6145. Phone: (703) 274-7633.

    Use of any trademarks in this report is not intended in any way to infringe on the rights of the trademark holder.

  • Table of Contents

    Acknowledgments.......................................................................................................vTo the Reader.............................................................................................................viiWhat is the Purpose of This Paper?.....................................................................viiiWho Should Read This Paper?............................................................................viiiHow is This Paper Organized?.................................................................................ixWhat Are the Other CMM Products?.......................................................................xHow Do You Receive More Information?............................................................xi1 The Process Maturity Framework.......................................................................1

    1.1 Immature Versus Mature Software Organizations................................11.2 Fundamental Concepts Underlying Process Maturity...........................31.3 Overview of the Capability Maturity Model............................................4

    2 The Five Levels of Software Process Maturity.................................................72.1 Behavioral Characterization of the Maturity Levels.............................9

    2.1.1 Level 1 - The Initial Level..............................................................102.1.2 Level 2 - The Repeatable Level.....................................................102.1.3 Level 3 - The Defined Level...........................................................112.1.4 Level 4 - The Managed Level........................................................122.1.5 Level 5 - The Optimizing Level....................................................13

    2.2 Understanding the Maturity Levels........................................................142.2.1 Understanding the Initial Level...................................................152.2.2 Understanding the Repeatable and Defined Levels.................152.2.3 Understanding the Managed and Optimizing Levels.............16

    2.3 Visibility Into the Software Process.........................................................192.4 Process Capability and the Prediction of Performance.........................222.5 Skipping Maturity Levels...........................................................................25

    3 Operational Definition of the Capability Maturity Model...........................273.1 Internal Structure of the Maturity Levels..............................................273.2 Maturity Levels............................................................................................303.3 Key Process Areas.........................................................................................303.4 Common Features.......................................................................................373.5 Key Practices..................................................................................................39

    4 Using the CMM.....................................................................................................434.1 Software Process Assessment and Software Capability

    Evaluation Methods....................................................................................444.2 Differences Between Software Process Assessments and

    Software Capability Evaluations...............................................................474.3 Other Uses of the CMM in Process Improvement...............................49

    CMU/SEI-93-TR-24 Capability Maturity Model i

  • Table of Contents

    5 Future Directions of the CMM...........................................................................515.1 What the CMM Does Not Cover..............................................................515.2 Near-Term Activities..................................................................................515.3 Long-Term Activities..................................................................................525.4 Conclusion....................................................................................................53

    6 References...............................................................................................................55Appendix A: Goals for Each Key Process Area....................................................59

    A.1 The Key Process Areas for Level 2: Repeatable.....................................59A.2 The Key Process Areas for Level 3: Defined..........................................61A.3 The Key Process Areas for Level 4: Managed........................................62A.4 The Key Process Areas for Level 5: Optimizing...................................63

    ii Capability Maturity Model CMU/SEI-91-TR-24

  • List of Figures

    Figure 2.1 The Five Levels of Software Process Maturity..................................8Figure 2.2 The Juran Trilogy Diagram: Quality Planning, Quality

    Control, and Quality Improvement..................................................17Figure 2.3 A Management View of Visibility into the Software Process

    at Each Maturity Level..........................................................................20Figure 2.4 Process Capability as Indicated by Maturity Level...........................23Figure 3.1 The CMM Structure..............................................................................29Figure 3.2 The Key Process Areas by Maturity Level.........................................31Figure 3.3 Building the CMM Structure: An Example of a Key Practice......40Figure 4.1 Common Steps in Software Process Assessments and

    Software Capability Evaluations.........................................................45

    CMU/SEI-93-TR-24 Capability Maturity Model iii

  • List of Figures

    iv Capability Maturity Model CMU/SEI-91-TR-24

  • Acknowledgments

    The description of the Capability Maturity Model for Software was initiallyproduced by a dedicated group of people who spent many hours discussingthe model and its features and then trying to document it in CMM v1.0.This group consisted of Mark Paulk,