COBIT Mapping: Mapping of CMMI for Development V1.2 With COBIT 4.1 

 

COBIT Mapping: Mapping of CMMI for Development V1.2 With COBIT  4.1  Download (Member Only, 1M)
Bookstore Purchase the Book

  Provide feedback on this document
Knowledge Center  Visit the COBIT - Implementation Knowledge Center community
Knowledge Center  Visit the COBIT - Use it Effectively Knowledge Center community

This document contains a detailed mapping of Capability Maturity Model (CMM) Integration (CMMI) for Development (CMMI-DEV), Version 1.2 (CMMI-DEV, V1.2), with COBIT 4.1. This document is an update of COBIT® Mapping: Mapping of CMMI® for Development With COBIT® 4.0. There are changes from COBIT 4.0 to COBIT 4.1 and additional mapping of IT governance strategic focus and COBIT process controls to CMMI generic practices.

A brief overview of the standards mapped against each other in this document follows:

  • COBIT— Released as an IT process and control framework linking IT to business requirements, COBIT initially was used mainly by the assurance community in conjunction with business and IT process owners. With the addition of management guidelines in 2000, COBIT was used more frequently as a management framework, providing management tools such as metrics and maturity models to complement the control framework. With the release of COBIT 4.0 in 2005, it became a more complete IT governance framework. Incremental updates to COBIT 4.0 were made in 2007; they can be seen as a fine-tuning of the framework, not fundamental changes. The current version is COBIT 4.1.
  • Capability Maturity Model® Integration (CMMI) for Development— CMMI is a process improvement capability maturity model for the processes that control development, implementation and maintenance of systems and software products. It contains leading practices that address development and maintenance activities that cover the system development product life cycle from conception through delivery and maintenance. This latest iteration of the model represents an integration of bodies of knowledge that address software engineering, systems engineering, hardware and design engineering, and acquisition. The model is used mainly by organizations engaged in relatively large and complex software and systems engineering projects to develop and maintain products and services. The US government requires CMMI-assessed capabilities to qualify for certain US government contracts. In 2006, the Software Engineering Institute(SEI) published CMMI-DEV, V1.2.

The mapping is performed in two layers:

  • Compare COBIT process name, goals and detailed control objectives with CMMI process area purpose, specific goals and generic goals.
  • Compare COBIT management guidelines—inputs, outputs, activities and metrics—with CMMI process diagrams and related process area cross-references for Measurement and Analysis (MA).