[go: up one dir, main page]
More Web Proxy on the site http://driver.im/ skip to main content
Skip header Section
CMMI Guidlines for Process Integration and Product ImprovementFebruary 2003
Publisher:
  • Addison-Wesley Longman Publishing Co., Inc.
  • 75 Arlington Street, Suite 300 Boston, MA
  • United States
ISBN:978-0-321-15496-5
Published:01 February 2003
Pages:
663
Skip Bibliometrics Section
Reflects downloads up to 11 Dec 2024Bibliometrics
Skip Abstract Section
Abstract

From the Book: CMMI® (Capability Maturity Model® Integration) consists of best practices that address the development and maintenance of products and services covering the product life cycle from conception through delivery and maintenance. A product can be an airplane, a digital camera, a video game component, an automated teller machine, a missile guidance system, or a software package available from a commercial retailer. It can also be a service such as delivering a training class, technical support for a software product, long-distance telephone service, data-processing services, and online banking. CMMI integrates bodies of knowledge that are essential when developing products, but that have been addressed separately in the past, such as software engineering, systems engineering, and acquisition. By integrating these bodies of knowledge, CMMI provides a comprehensive solution for development and maintenance of products and services. Purpose of This Book This book is an extension of the CMMI Framework,1 which generated the full set of CMMI models released by the Software Engineering Institute (SEI) in January 2002. To use a CMMI model released by the SEI, you must choose from among the multiple models available based on your improvement needs. Therefore, to use the CMMI models published by the SEI, you need to know the content of each model and the area that you want to improve. Unfortunately for many users, selecting a model from the SEI Web site appears difficult because they must make the up-front decision about which bodies of knowledge they want to address in their organizations and the approach they want to take to their process improvementefforts. To facilitate CMMI use, this book provides a single source for all CMMI model information--a functional equivalent of the CMMI Framework. You do not have to select a particular model to get started--all of your choices are compiled here into one book. The book describes what is common across all CMMI models as well as what is different. It describes the basic concepts and the ways processes evolve as your organization improves. It will help you to understand the content of each CMMI model and to decide how CMMI can best address your needs. Audience The audience for this book includes anyone interested in process improvement--whether you are familiar with the concept of Capability Maturity Models or whether you are seeking information to get started on your improvement efforts. It is intended for people who want an appraisal2 to see where they are, those who already know what they want to improve, and those who are just getting started and want to develop a general understanding of CMMI. This book is a must-have for process appraisal teams; members of process improvement groups; product development managers; product developers and maintainers, including software and systems engineers; and project management, computer science, and engineering educators. Organization of This Book This book maintains the integrity of the CMMI v1.1 models available on the SEI's Web site and serves as a guide for improvement of organizational processes. It is organized into three main parts: Part One--About CMMI Part Two--The Process Areas Part Three--The Appendices and Glossary In writing this book, we enhanced and supplemented the original SEI materials. These improvements appear in Part One. Given the nature of the material in Part Two, we made only minor changes and added markings to identify and classify the content. In the glossary in Part Three, we've compiled a practical resource for understanding the "language" of CMMI. Part One, "About CMMI," consists of seven chapters: Chapter 1, "Introduction," offers a broad view of CMMI. It introduces you to the concepts of process improvement and describes the benefits of CMMI, the history of models used for process improvement, and different process improvement approaches. Chapter 2, "Process Area Components," describes all of the components of the CMMI process areas. Chapter 3, "Process Institutionalization," describes the model components that ensure that the implementation of processes is effective, repeatable, and lasting. Chapter 4, "Relationships among Process Areas," provides insight into the meaning and interactions of the major CMMI components. Chapter 5, "Tying It All Together," assembles the model components and process infrastructure into the representations and explains the concepts of maturity level and capability level. Chapter 6, "Using CMMI Models," describes paths to adoption and use of CMMI for process improvement and benchmarking. Chapter 7, "A CMMI Case Study: United Space Alliance, LLC," describes the real-life experiences of an organization as it prepared to adopt CMMI. This chapter may help you plan your own organization's adoption of CMMI. Part Two, "The Process Areas," contains 25 sections, one for each of the CMMI process them, these chapters are organized alphabetically by process area acronym. Each chapter contains descriptions of goals, best practices, and examples. Part Three, "The Appendices and Glossary," consists of four information resources: Appendix A, "References," contains references you can use to locate documented sources of information such as reports, process-improvement models, industry standards, and books that are related to CMMI. Appendix B, "Acronyms," defines the acronyms used in CMMI. Appendix C, "CMMI Project Participants," contains a list of people and their organizations who participated in the CMMI project. That project developed the models on which this book is based. The "Glossary" defines the terms used in CMMI. How to Use This Book Whether you are new to process improvement, new to CMMI, or already familiar with CMMI, this book can help you understand why CMMI is the best model to use for improving your product life-cycle processes. Readers New to Process Improvement If you are new to process improvement or new to the CMM® concept, we suggest that you read chapter 1, "Introduction," and the case study in chapter 7 first. Chapter 1 will give you an overview of process improvement and explain what CMMI is all about. Chapter 7 will help you to see how CMMI can be used by an organization. When you read chapter 7 the first time, don't be concerned about understanding all the terminology or details. Just read it to get an overall feel for what's going on in the case study. Then, go back and read chapters 1 through 7. When you read chapter 7 again, after reading the balance of Part One, you will understand the de better. Next, skim Part Two to get a feel for the scope of the best practices contained in CMMI. Pay closest attention to the statement of purpose at the beginning of each section. In Part Three, look through the references in Appendix A and select additional sources you think would be beneficial to read before moving forward with using CMMI. Read through the acronyms and glossary to become familiar with the language of CMMI. Then, go back and read the details of Part Two. Readers Experienced with Process Improvement If you are new to CMMI but have experience with other process-improvement models, such as the Software CMM or the Systems Engineering CM (i.e., EIA 731), you will immediately recognize many similarities. We recommend that you read Part One to understand how CMMI is different from other process-improvement models, but you may want to read some of the sections more quickly than others. Read Part Two with an eye open for best practices you recognize from the models you have already tried. Identifying familiar material gives you a feel for what is new and what has been carried over from the model you already know. Next, review the glossary to understand how some terminology may differ from that used in the process-improvement model you know. Many concepts will be repeated, but they may be called something different. Readers Familiar with CMMI If you have reviewed or used one of the CMMI models available on the SEI Web site, you will quickly recognize the CMMI concepts discussed and the best practices presented. The differences between this book and the SEI-released models are mainly found in Part One, "About CMMI." Although the continuous and staged representations of the models' best practices are presented together in Part Two, no changes were made that affect the meaning or applicability of these best practices. In Part One, we added information about the benefits of process improvement and historical information about process-improvement models for readers new to process improvement or to the CMM, concept. We explained the vast similarities of the two representations reflected in the models and included detailed discussions of both capability levels and maturity levels and their importance in CMMI. To understand how the two representations have been formatted for Part Two, see the descriptions and illustrations of typographical conventions (Figures 2.2, 2.3, and 2.4) in chapter 2. We also expanded the discussion of generic model components into a chapter that you will find more informative than what is found in the SEI-released models (see chapter 3). A chapter containing a case study of CMMI (chapter 7) was added to describe the real-life experience of an organization preparing to adopt CMMI. In Part Three, "The Appendices and Glossary," we combined all terms and their definitions into the glossary, so that you can find definitions more quickly and easily. Terms are no longer addressed in a separate chapter in Part One. As you read Part One, we recommend that you pay closest attention to chapter 3, "Process Institutionalization," and chapter 7, "CMMI Case Study: United Space Alliance, LLC." Review the format used in Part Two. This format helps you differentiate between the two representations. Additional Information and Reader Feedback You can find additional information from various other sources about CMMI, such as the background and history of the CMMI models, as well as the benefits of using CMMI models. Many of these sources are listed in Appendix A and are also documented on the CMMI Web site Suggestions for improving CMMI are welcomed by the SEI. For information on how to provide feedback, see the CMMI Web site at If you have questions about CMMI, send an e-mail to 0321154967P01292003

Cited By

  1. Ilyas M, Khan S, Khan H and Rashid N (2023). Software integration model, Journal of Software: Evolution and Process, 36:4, Online publication date: 3-Apr-2024.
  2. Akbar M, Khan A, Mahmood S and Mishra A (2023). SRCMIMM: the software requirements change management and implementation maturity model in the domain of global software development industry, Information Technology and Management, 24:3, (195-219), Online publication date: 1-Sep-2023.
  3. Alqmase M, Alshayeb M and Ghouti L (2022). Quality assessment framework to rank software projects, Automated Software Engineering, 29:2, Online publication date: 1-Nov-2022.
  4. Pérez Pupo I, Piñero Pérez P, García Vacacela R, Bello R and Acuña L Discovering Fails in Software Projects Planning Based on Linguistic Summaries Rough Sets, (365-375)
  5. ACM
    Russo D, Ciancarini P, Falasconi T and Tomasi M (2018). A Meta-Model for Information Systems Quality, ACM Transactions on Management Information Systems, 9:3, (1-38), Online publication date: 30-Sep-2018.
  6. ACM
    Rossi R, Notargiacomo P and Hirama K Review of eQETIC Model based on Academic Analytics Proceedings of the 9th International Conference on Education Technology and Computers, (157-161)
  7. ACM
    Coelho J and Valente M Why modern open source projects fail Proceedings of the 2017 11th Joint Meeting on Foundations of Software Engineering, (186-196)
  8. ACM
    Nielsen P and Heeager L The dynamics of agile practices for safety-critical software development Proceedings of the XP2017 Scientific Workshops, (1-6)
  9. ACM
    Raza M and Faria J ProcessPAIR: a tool for automated performance analysis and improvement recommendation in software development Proceedings of the 31st IEEE/ACM International Conference on Automated Software Engineering, (798-803)
  10. Ali S and Khan S (2016). Software outsourcing partnership model, Journal of Systems and Software, 117:C, (402-425), Online publication date: 1-Jul-2016.
  11. Magdaleno A, de Oliveira Barros M, Werner C, de Araujo R and Batista C (2015). Collaboration optimization in software process composition, Journal of Systems and Software, 103:C, (452-466), Online publication date: 1-May-2015.
  12. ACM
    Marques A, Ramalho F and Andrade W Towards a requirements traceability process centered on the traceability model Proceedings of the 30th Annual ACM Symposium on Applied Computing, (1364-1369)
  13. Raschke W, Zilli M, Loinig J, Weiss R, Steger C and Kreiner C Patterns of Software Modeling Proceedings of the Confederated International Workshops on On the Move to Meaningful Internet Systems: OTM 2014 Workshops - Volume 8842, (428-437)
  14. Kaewkiriya T, Saga R and Tsuji H Transparent digital contents sharing for science teachers Proceedings of the 15th international conference on Human Interface and the Management of Information: information and interaction for learning, culture, collaboration and business - Volume Part III, (53-62)
  15. ACM
    Sun C, Du J, Chen N, Khoo S and Yang Y Mining explicit rules for software process evaluation Proceedings of the 2013 International Conference on Software and System Process, (118-125)
  16. ACM
    Lami G, Fabbrini F and Fusani M A methodology to derive sustainability indicators for software development projects Proceedings of the 2013 International Conference on Software and System Process, (70-77)
  17. Chen N, Hoi S and Xiao X Software process evaluation Proceedings of the 26th IEEE/ACM International Conference on Automated Software Engineering, (333-342)
  18. Reinhartz-Berger I and Aharoni A (2011). Semi-Automatic Composition of Situational Methods, Journal of Database Management, 22:4, (1-29), Online publication date: 1-Oct-2011.
  19. Lami G, Fabbrini F and Fusani M ISO/IEC 15504-10 Proceedings of the 30th international conference on Computer safety, reliability, and security, (284-295)
  20. Grbac T and Huljenić D Defect detection effectiveness and product quality in global software development Proceedings of the 12th international conference on Product-focused software process improvement, (113-127)
  21. ACM
    Hattori L, Lungu M and Lanza M Replaying past changes in multi-developer projects Proceedings of the Joint ERCIM Workshop on Software Evolution (EVOL) and International Workshop on Principles of Software Evolution (IWPSE), (13-22)
  22. Jwo J, Cheng Y, Hsu T and Liu C Rapid Application Lifecycle Management Proceedings of the 2010 conference on New Trends in Software Methodologies, Tools and Techniques: Proceedings of the 9th SoMeT_10, (212-217)
  23. McLoughlin F and Richardson I The rosetta stone methodology – a benefits driven approach to software process improvement Proceedings of the 11th international conference on Product-Focused Software Process Improvement, (366-379)
  24. Nielsen P and Tjørnehøj G (2010). Social networks in software process improvement, Journal of Software Maintenance and Evolution: Research and Practice, 22:1, (33-51), Online publication date: 1-Jan-2010.
  25. Sakoda M, Wada Y, Tsuji H and Seta K Social network service with maturity level for science teachers Proceedings of the 2009 IEEE international conference on Systems, Man and Cybernetics, (1656-1661)
  26. ACM
    Mettler T and Rohner P Situational maturity models as instrumental artifacts for organizational design Proceedings of the 4th International Conference on Design Science Research in Information Systems and Technology, (1-9)
  27. Jung H and Goldenson D (2009). Evaluating the relationship between process improvement and schedule deviation in software maintenance, Information and Software Technology, 51:2, (351-361), Online publication date: 1-Feb-2009.
  28. ACM
    Sharma M and Chandwani M Maturing capability in unified paradigm Proceedings of the International Conference on Advances in Computing, Communication and Control, (737-746)
  29. Larrucea X, Fernandez R, Soriano J, Martínez A and Gonzalez-Barahona J A Service Based Development Environment on Web 2.0 Platforms Proceedings of the 1st European Conference on Towards a Service-Based Internet, (38-48)
  30. ACM
    da Silveira D, Netto P and Schmitz E Um método de validação da conformidade entre processos e regras de negócio através da animação Companion Proceedings of the XIV Brazilian Symposium on Multimedia and the Web, (279-286)
  31. ACM
    da Cruz J and Ruiz D Uma experiência em mineração de processos de manutenção de software Companion Proceedings of the XIV Brazilian Symposium on Multimedia and the Web, (247-253)
  32. Kapur P, Ngo-The A, Ruhe G and Smith A (2008). Optimized staffing for product releases and its application at Chartwell Technology, Journal of Software Maintenance and Evolution: Research and Practice, 20:5, (365-386), Online publication date: 1-Sep-2008.
  33. Hsueh N, Shen W, Yang Z and Yang D (2008). Applying UML and software simulation for process definition, verification, and validation, Information and Software Technology, 50:9-10, (897-911), Online publication date: 1-Aug-2008.
  34. Lucrédio D, dos Santos Brito K, Alvaro A, Garcia V, de Almeida E, de Mattos Fortes R and Meira S (2008). Software reuse, Journal of Systems and Software, 81:6, (996-1013), Online publication date: 1-Jun-2008.
  35. Fabbrini F, Fusani M, Lami G and Sivera E Integrating joint reviews with automotive SPICE assessments results Proceedings of the Software process, 2008 international conference on Making globally distributed software development a success story, (357-368)
  36. Rungratri S and Usanavasin S Project assets ontology (PAO) to support gap analysis for organization process improvement based on CMMI v.1.2 Proceedings of the Software process, 2008 international conference on Making globally distributed software development a success story, (76-87)
  37. Lee C, Wang M and Chen J (2008). Ontology-based intelligent decision support agent for CMMI project monitoring and control, International Journal of Approximate Reasoning, 48:1, (62-76), Online publication date: 1-Apr-2008.
  38. ACM
    Sarkar S, Sindhgatta R and Pooloth K A collaborative platform for application knowledge management in software maintenance projects Proceedings of the 1st Bangalore Annual Compute Conference, (1-7)
  39. von Konsky B and Ivins J Assessing the capability and maturity of capstone software engineering projects Proceedings of the tenth conference on Australasian computing education - Volume 78, (171-180)
  40. Montoni M and Rocha A A methodology for identifying critical success factors that influence software process improvement initiatives Proceedings of the 14th European conference on Software Process Improvement, (175-186)
  41. Chen X and Staples M Using practice outcome areas to understand perceived value of CMMI specific practices for SMEs Proceedings of the 14th European conference on Software Process Improvement, (59-70)
  42. Poort E, Postema H, Key A and de With P The influence of CMMI on establishing an architecting process Proceedings of the Quality of software architectures 3rd international conference on Software architectures, components, and applications, (215-230)
  43. Poort E, Postema H, Key A and With P The Influence of CMMI on Establishing an Architecting Process Third International Conference on Quality of Software Architectures on Software Architectures, Components, and Applications - Volume 4880, (215-230)
  44. Santos G, Montoni M, Figueiredo S and Rocha A SPI-KM - lessons learned from applying a software process improvement strategy supported by knowledge management Proceedings of the 8th international conference on Product-Focused Software Process Improvement, (81-95)
  45. Irigoyen Ferreiro Ferreira A, Santos G, Cerqueira R, Montoni M, Barreto A, Soares Barreto A and Rocha A Applying ISO 9001 Proceedings of the 29th international conference on Software Engineering, (642-651)
  46. Jablonski S and Faerber M Integrated Management of Company Processes and Standard Processes Proceedings of the 5th International Workshop on Software Quality
  47. Montoni M, Santos G, Rocha A, Weber K and Araujo E MPS Model and TABA Workstation Proceedings of the 5th International Workshop on Software Quality
  48. Kim S and Kyung T A study on the priority selection for information system project management model Proceedings of the 6th Conference on WSEAS International Conference on Applied Computer Science - Volume 6, (639-647)
  49. Chang C and Chu C (2007). Defect prevention in software processes, Journal of Systems and Software, 80:4, (559-570), Online publication date: 1-Apr-2007.
  50. Hämäläinen N Quality management activities for software architecture and software architecture process Proceedings of the 25th conference on IASTED International Multi-Conference: Software Engineering, (347-352)
  51. Lutteroth C, Luxton-Reilly A, Dobbie G and Hamer J A maturity model for computing education Proceedings of the ninth Australasian conference on Computing education - Volume 66, (107-114)
  52. Mc Caffery F, Taylor P and Coleman G (2007). Adept, IEEE Software, 24:1, (24-31), Online publication date: 1-Jan-2007.
  53. Richardson I and von Wangenheim C (2007). Guest Editors' Introduction, IEEE Software, 24:1, (18-22), Online publication date: 1-Jan-2007.
  54. Figueiredo S, Santos G, Montoni M, Rocha A, Barreto A, Barreto A and Ferreira A Taba workstation Proceedings of the 6th international conference on Practical Aspects of Knowledge Management, (61-72)
  55. Ferreira A, Santos G, Cerqueira R, Montoni M, Barreto A, Rocha A, Figueiredo S, Barreto A, Filho R, Lupo P and Cerdeiral C Taba workstation Proceedings of the 13th European conference on Software Process Improvement, (207-218)
  56. Yoo C, Yoon J, Lee B, Lee C, Lee J, Hyun S and Wu C (2006). A unified model for the implementation of both ISO 9001, Journal of Systems and Software, 79:7, (954-961), Online publication date: 1-Jul-2006.
  57. Regnell B, Olsson H and Mossberg S Assessing requirements compliance scenarios in system platform subcontracting Proceedings of the 7th international conference on Product-Focused Software Process Improvement, (362-376)
  58. Montoni M, Santos G, Rocha A, Figueiredo S, Cabral R, Barcellos R, Barreto A, Soares A, Cerdeiral C and Lupo P Taba workstation Proceedings of the 7th international conference on Product-Focused Software Process Improvement, (249-262)
  59. ACM
    Mutchalintungkul A, Oonhawat J, Pholpipatanaphong K, Sutivong D and Prompoon N Experience from applying RIM to educational ERP development Proceedings of the 28th international conference on Software engineering, (620-623)
  60. ACM
    Wang Q, Jiang N, Gou L, Liu X, Li M and Wang Y BSR Proceedings of the 28th international conference on Software engineering, (585-594)
  61. ACM
    Komuro M Experiences of applying SPC techniques to software development processes Proceedings of the 28th international conference on Software engineering, (577-584)
  62. Li M Assessing 3-d integrated software development processes Proceedings of the 2006 international conference on Software Process Simulation and Modeling, (15-38)
  63. Ebert C (2006). Understanding the Product Life Cycle, IEEE Software, 23:3, (19-25), Online publication date: 1-May-2006.
  64. Thompson E Using a subject area model as a learning improvement model Proceedings of the 8th Australasian Conference on Computing Education - Volume 52, (197-203)
  65. Pries-Heje J and Johansen J AIM – ability improvement model Proceedings of the 12th European conference on Software Process Improvement, (71-82)
  66. Rocha A, Montoni M, Santos G, Mafra S, Figueiredo S, Albuquerque A and Mian P Reference model for software process improvement Proceedings of the 12th European conference on Software Process Improvement, (130-141)
  67. Yang Y, Bhuta J, Boehm B and Port D (2005). Value-Based Processes for COTS-Based Applications, IEEE Software, 22:4, (54-62), Online publication date: 1-Jul-2005.
  68. Taipale V and Taramaa J Process improvement solution for co-design in radio base station DSP SW Proceedings of the 6th international conference on Product Focused Software Process Improvement, (16-28)
  69. Jedlitschka A, Hamann D, Göhlert T and Schröder A Adapting PROFES for use in an agile process Proceedings of the 6th international conference on Product Focused Software Process Improvement, (502-516)
  70. Bornstein C, Kubrusly L, Zambalde A and Rocha A Impacts of software deployment in the coffee agribusiness of brazil Proceedings of the 6th international conference on Product Focused Software Process Improvement, (257-271)
  71. Li M Expanding the horizons of software development processes Proceedings of the 2005 international conference on Unifying the Software Process Spectrum, (54-67)
  72. ACM
    Ebert C and De Man J requirements uncertainty Proceedings of the 27th international conference on Software engineering, (553-560)
  73. McKeever K, Morrison J and Peterson E Assuring Assessment Success Proceedings of the 28th Annual International Computer Software and Applications Conference - Volume 01, (30-37)
  74. ACM
    Huang S and Tilley S Towards a documentation maturity model Proceedings of the 21st annual international conference on Documentation, (93-99)
Contributors
  • Software Engineering Institute

Reviews

A.K. Krishna Menon

The Capability Maturity Model (CMM) is a framework for improving software and software-related processes, defined by the Software Engineering Institute, around 1987. The principles of this framework were used for defining the Capability Maturity Model for Software (SW-CMM), which focused on improving software; the People's Capability Maturity Model (P-CMM), which focused on the capability of people involved in software environments; the Systems Engineering Capability Model (SECM); and the Integrated Product Development Capability Model (IPD-CMM). Capability Maturity Model Integration (CMMI) models have elevated the CMM concept to a new level, to enable further growth and expansion of the concept to multiple disciplines. CMMI models are tools that help organizations improve their product and service development, acquisition, and maintenance processes. The design of each CMMI model allows it to be used along with other CMMI models, making it easier for organizations to implement the model across the organization with flexibility. The authors of this book were members of the CMMI product team that integrated SW-CMM, SECM, and IPD-CMM into a cohesive model, which became the CMMI framework and the CMMI v1.1. The CMMI framework supports two representations of the model. The implementing organization can select either the staged or the continuous model, or, in special circumstances, a carefully chosen approach involving both. The staged representation of the model provides an easy migration from SW-CMM to CMMI; a proven sequence of improvements, starting with basic management practices; and facilitation of comparisons across organizations, by the use of maturity levels. The continuous representation allows an implementing organization to select the sequence of improvement that aligns with its business objectives and mitigates its risk areas; compare across and among organizations, in terms of process area; and use the SECM and the IPD-CMM. The CMMI terminology refers to the broad disciplines that impact process improvement as bodies of knowledge. They are also called disciplines. In the current version, CMMI V1.1, four bodies of knowledge are available to an implementing organization when selecting a CMMI model: systems engineering, integrated product and process development, and supplier sourcing. Other bodies of knowledge will be integrated into the CMMI framework later on. CMMI defines 25 process areas. A subset of these process areas will be relevant for each of the four disciplines. For systems engineering, under the continuous model, only 22 process areas are applicable. Under the continuous model, for the software engineering discipline, the number of process areas is the same as that for systems engineering, but certain process areas receive special focus. Special consideration because of the nature of the discipline is termed discipline amplification. The integrated product and process development discipline requires two additional process areas, in addition to those for the two disciplines noted above. The staged model has the same number of process areas as the continuous model. Unlike the continuous representation of CMMI, however, and similar to the SW-CMM, the 25 process areas are categorized into five maturity levels. This similarity facilitates ease of migration from SW-CMM to CMMI (staged). The continuous model uses so-called capability levels to indicate an organization's path towards improvement in product and services development. These levels indicate improvement from an undefined state to a managed and measured state. An organization reaches a particular level of capability in a process area, or a set of process areas, when all the goals specified for the process area or areas are satisfied. There are six capability levels, numbered zero through five, for the continuous model. Essentially, therefore, the staged representation focuses on organizational maturity as measured by maturity levels, while the continuous representation focuses on process area capability as measured by capability levels. For organizations with different product lines, which desire to improve processes across the entire organization, the staged model will be preferable to start with. Such an approach will allow the organization to prioritize its processes, and focus on critical ones. If the same organization prefers to improve the processes of product lines one by one, it will find the continuous model to be a prudent approach, since the model will yield separate capability ratings for the organization for each product line. The book is divided into three parts. Part 1 contains seven chapters: "Introduction," "Process Area Components," "Process Institutionalization," "Relationships Among Process Areas," "Tying It All Together," "Using CMM Models," and "CMMI Case Study: United Space Alliance, LLC." Part 2 is not divided into chapters, but instead individually discusses the features of each of the twenty-five process areas. Part 3 lists relevant references and acronyms, and also contains a list of participants in the CMMI project. The book is organized well, and is written in a lucid style. It will be understandable to software practitioners, product designers, business development teams, and management students. The publisher's editorial staff has proven that books free from editorial irritants can indeed be published. Online Computing Reviews Service

Access critical reviews of Computing literature here

Become a reviewer for Computing Reviews.

Please enable JavaScript to view thecomments powered by Disqus.

Recommendations