The Capability Maturity Model: Guidelines for Improving the Software Process by Software Engineering Institute Carnegie Mellon Process, Software Engineering Institute Staff

From Barnes & Noble

Fatbrain Review

From the Publisher

Principal Contributors and Editors:
Mark C. Paulk, Charles V. Weber, Bill Curtis, Mary Beth Chrissis

"In every sense, the CMM represents the best thinking in the field today... this book is targeted at anyone involved in improving the software process, including members of assessment or evaluation teams, members of software engineering process groups, software managers, and software practitioners..." From the Foreword by Watts Humphrey

The Capability Maturity Model for Software (CMM) is a framework that demonstrates the key elements of an effective software process. The CMM describes an evolutionary improvement path for software development from an ad hoc, immature process to a mature, disciplined process, in a path laid out in five levels. When using the CMM, software professionals in government and industry can develop and improve their ability to identify, adopt, and use sound management and technical practices for delivering quality software on schedule and at a reasonable cost.

This book provides a description and technical overview of the CMM, along with guidelines for improving software process management overall. It is a sequel to Watts Humphrey's important work,Managing the Software Process,in that it structures the maturity framework presented in that book more formally.

• Compares the CMM with ISO 9001
• Provides an overview of ISO's SPICE project, which is developing international standards for software process improvement and capability determination
• Presents a case study of IBM Houston's Space Shuttle project, which is frequently referred to as being at Level 5

Booknews

The first part of the book describes the evolution of the CMM (Capability Maturity Model), the concepts of software process maturity, the structure of the model, how to interpret and use it, and the case study of IBM Houston. The second part consists of the key practices of the CMM, which describe the software management engineering practices of a maturing software process. Also includes a number of useful appendices. Annotation c. Book News, Inc., Portland, OR (booknews.com)

Details from Seller

• ISBN: 0201546647
• Publisher: Addison Wesley Professional
• Pub. Date: October 1995
• Condition:

Comments from the Seller: Former Library book. Shows some signs of wear, and may have some markings on the inside. 100% Money Back Guarantee. Shipped to over one million happy customers. Your purchase benefits world literacy!

• Table of Contents
• Forewords & Introductions
• Read an Excerpt

Table of Contents

Forewords & Introductions

The Capability Maturity Model for Software is one of the best known products of the Software Engineering Institute. Thousands of copies of the two technical reports that comprise the CMM Paulk93a, Paulk93b have been distributed around the world. The CMM and related process products are having a significant impact on the software community, as evidenced by the current international standards effort on software process described in Appendix G.

This book integrates and elaborates the description of the CMM and how to interpret its practices. It contains the text of the key practices from Paulk93b verbatim, except for a few minor grammatical corrections listed in Appendix H.

• A case study of IBM Houston's Space Shuttle project, which is frequently referred to as being at Level 5 (Chapter 6)
• Mapping between the key practices and the goals of the key process areas (Appendix E)
• A comparison of ISO 9001 and the CMM (Appendix F)
• An overview of ISO's SPICE project, which is developing international standards for software process improvement and capability determination (Appendix G)

The book is divided into two main parts. The first part consists of the chapters describing the evolution of the CMM, the concepts of software process maturity, the structure of the model, how to interpret and use the CMM, and the case study of IBM Houston. The second part consists of the key practices of the CMM, which describes the software management engineering practices of a maturing software process. Also included are a number of appendices that provide useful reference material.

Thisbook is targeted at anyone involved in improving the software process, including members of appraisal teams, members of software engineering process groups, software managers, and software practitioners. It complements Humphrey's Managing the Software Process by formalizing the maturity framework described in that book.

This book does not describe all of the work being done by the SEI's Software Process Program. In particular, the SEI's work on software process definition, measurement, and organizational change may be of value to individuals working to improve the software process. For further information regarding the SEI, the CMM, or its associated products, contact:

SEI Customer Relations
Software Engineering Institute
Carnegie Mellon University
Pittsburgh, PA 15213-3890
Telephone: (412)268-5800
Fax: (412)268-5758
E mail:

The CMM is a living document, shaped by the needs of the software community. The SEI solicits feedback from our customers. Instructions for requesting changes to the CMM and a form for doing so are contained in Appendix I.

0201546647P04062001

Read an Excerpt

The Capability Maturity Model for Software is one of the best known products of the Software Engineering Institute. Thousands of copies of the two technical reports that comprise the CMM Paulk93a, Paulk93b have been distributed around the world. The CMM and related process products are having a significant impact on the software community, as evidenced by the current international standards effort on software process described in Appendix G.

This book integrates and elaborates the description of the CMM and how to interpret its practices. It contains the text of the key practices from Paulk93b verbatim, except for a few minor grammatical corrections listed in Appendix H.

The authors have added the following material:

• A case study of IBM Houston's Space Shuttle project, which is frequently referred to as being at Level 5 (Chapter 6)
• Mapping between the key practices and the goals of the key process areas (Appendix E)
• A comparison of ISO 9001 and the CMM (Appendix F)
• An overview of ISO's SPICE project, which is developing international standards for software process improvement and capability determination (Appendix G)

The book is divided into two main parts. The first part consists of the chapters describing the evolution of the CMM, the concepts of software process maturity, the structure of the model, how to interpret and use the CMM, and the case study of IBM Houston. The second part consists of the key practices of the CMM, which describes the software management engineering practices of a maturing software process. Also included are a number of appendices that provide useful referencematerial.

This book is targeted at anyone involved in improving the software process, including members of appraisal teams, members of software engineering process groups, software managers, and software practitioners. It complements Humphrey's Managing the Software Process by formalizing the maturity framework described in that book.

This book does not describe all of the work being done by the SEI's Software Process Program. In particular, the SEI's work on software process definition, measurement, and organizational change may be of value to individuals working to improve the software process. For further information regarding the SEI, the CMM, or its associated products, contact:

SEI Customer Relations
Software Engineering Institute
Carnegie Mellon University
Pittsburgh, PA 15213-3890
Telephone: (412)268-5800
Fax: (412)268-5758
E mail:customer-relations@sei.cmu.edu

The CMM is a living document, shaped by the needs of the software community. The SEI solicits feedback from our customers. Instructions for requesting changes to the CMM and a form for doing so are contained in Appendix I.