Skip to main content

Capability Maturity Model Integration

  • Chapter
  • First Online:
Introduction to Software Process Improvement

Part of the book series: Undergraduate Topics in Computer Science ((UTICS))

Abstract

The SEI was founded by the US Congress in 1984 and has worked successfully in advancing software engineering practices in the USA and worldwide. It performs research to find solutions to key software engineering problems, and its proposed solutions are validated through pilots. These solutions are then disseminated to the wider software engineering community through its training programme. The SEI’s research and maturity models have played an important role in helping companies to deliver high-quality software consistently on-time and on-budget.

This is a preview of subscription content, log in via an institution to check access.

Access this chapter

eBook
USD 16.99
Price excludes VAT (USA)
  • Available as EPUB and PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD 16.99
Price excludes VAT (USA)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Purchases are for personal use only

Institutional subscriptions

Notes

  1. 1.

    The SEI was founded by the US Congress in 1984 and has worked successfully in advancing software engineering practices in the USA and worldwide. It performs research to find solutions to key software engineering problems, and its proposed solutions are validated through pilots. These solutions are then disseminated to the wider software engineering community through its training programme. The SEI’s research and maturity models have played an important role in helping companies to deliver high-quality software consistently on-time and on-budget. The SEI opened a European office in Frankfurt, Germany, in 2004.

  2. 2.

    Of course, the fact that a company has been appraised at a certain CMM or CMMI rating is no guarantee that it is performing effectively as a commercial organization. For example, the Motorola plant in India was appraised at CMM level 5 in the late 1990s while Motorola lost business opportunities in the GSM market.

  3. 3.

    ISO 15504 (popularly known as SPICE) is an international standard for software process assessment.

  4. 4.

    This book is focused on the implementation of the staged representation of the CMMI rather than the continuous representation. This is my preferred approach to process improvement as it provides a clearly defined roadmap and also allows benchmarking of organizations. Appraisals against the staged representation are useful since a CMMI maturity level rating is awarded to the organization, and the company may use this to publicize its software engineering capability.

  5. 5.

    Discipline amplification is a specialized piece of information that is relevant to a particular discipline. It is introduced in the model by text such as “For Systems Engineering”.

  6. 6.

    A SCAMPI appraisal is a systematic examination of the processes in an organization to determine the maturity of the organization with respect to the CMMI. An appraisal team consists of a SCAMPI lead appraiser, one or more external appraisers, and usually one internal appraiser. It consists of interviews with senior and middle management and reviews with project managers and project teams. The appraisers will review documentation and determine the extent to which the processes defined are effective as well as the extent to which they are institutionalized in the organization. Data will be gathered and reviewed by the appraisers, ratings produced, and the findings presented to the organization.

  7. 7.

    Small organizations may not have the budget for a formal SCAMPI Class A appraisal. They may be more interested in an independent SCAMPI Class B or C appraisal, which is used to provide feedback on their strengths and opportunities for improvement. Feedback allows the organization to focus its improvement efforts for the next improvement cycle.

  8. 8.

    Institutionalization is a technical term and means that the process is ingrained in the way in which work is performed in the organization. An institutionalized process is defined, documented, and followed in the organization. All staff have been appropriately trained in its use and process discipline is enforced via audits. It is explained by the phrase “That’s the way we do things around here”.

References

  1. Chrissis, M.B., Conrad, M., Shrum, S.: CMMI. Guidelines for Process Integration and Product Improvement. SEI Series in Software Engineering, 2nd edn. Addison Wesley (2006)

    Google Scholar 

  2. Crosby, P.: Quality Is Free. The Art of Making Quality Certain. McGraw Hill (1979)

    Google Scholar 

  3. Deming, W.E.: Out of Crisis. MIT Press (1986)

    Google Scholar 

  4. Humphry, W.: Managing the Software Process. Addison Wesley (1989)

    Google Scholar 

  5. Juran, J.: Juran’s Quality Handbook, 5th edn. McGraw Hill (2000)

    Google Scholar 

  6. O’ Regan, G.: A Practical Approach to Software Quality. Springer, New York (2002)

    Google Scholar 

  7. Software Engineering Institute: CMMI Impact. Presentation by Anita Carleton. Aug 2009

    Google Scholar 

Download references

Author information

Authors and Affiliations

Authors

Corresponding author

Correspondence to Gerard O’Regan .

Rights and permissions

Reprints and permissions

Copyright information

© 2011 Springer-Verlag London Limited

About this chapter

Cite this chapter

O’Regan, G. (2011). Capability Maturity Model Integration . In: Introduction to Software Process Improvement. Undergraduate Topics in Computer Science. Springer, London. https://doi.org/10.1007/978-0-85729-172-1_3

Download citation

  • DOI: https://doi.org/10.1007/978-0-85729-172-1_3

  • Published:

  • Publisher Name: Springer, London

  • Print ISBN: 978-0-85729-171-4

  • Online ISBN: 978-0-85729-172-1

  • eBook Packages: Computer ScienceComputer Science (R0)

Publish with us

Policies and ethics