Cmmi a comprehensive overview

Solo disponible en BuenasTareas
  • Páginas : 39 (9597 palabras )
  • Descarga(s) : 0
  • Publicado : 26 de enero de 2011
Leer documento completo
Vista previa del texto
CMMI: A Comprehensive Overview

Rushby Craig

(801) 775-5739

Software Technology Support Center

Bruce Allgood

(801) 777-3207

Computer Resources Support Improvement Program Hill AFB, UT

Agenda
• Project History • CMMI Structure • Comparisons with SW-CMM v1.1, SE-CMM, and EIA/IS 731_ • Process Areas Overview • Assessment Methodology • Training

CMMI User Group Nov 13, 20012

What Model do I use?

• Historically: Depends on the discipline that you want to model. –Software Engineering –Systems Engineering –Software Acquisition –Systems Security –etc.

CMMI User Group Nov 13, 2001

3

What is a CMM?
• Capability Maturity Model: A reference model of mature practices in a specified discipline, used to assess a group’s capability to perform that discipline• CMMs differ by –Discipline (software, systems, acquisition, etc.) –Structure (staged versus continuous) –How Maturity is Defined (process improvement path) –How Capability is Defined (institutionalization) • “Capability Maturity Model®” and CMM® are used by the Software Engineering Institute (SEI) to denote a particular class of maturity models
Capability Maturity Model®, CMM®, CMM Integration,and CMMI are service marks and registered trademarks of Carnegie Mellon University CMMI User Group Nov 13, 2001 4

Commonly Used CMMs
Software CMM System Engineering CMM System Engineering Capability Model Software Acquisition CMM System Security Engineering CMM Personal Software Process FAA-iCMM staged continuous continuous staged continuous staged continuous software development systemengineering system engineering software acquisition security engineering individual software development software engineering, systems engineering, and acquisition integrated product development workforce software development
5

IPD-CMM People CMM SPICE Model

continuous staged continuous
CMMI User Group Nov 13, 2001

So Many Models, So Little Time
Software Software CMM CMM ZZZ ZZZ CMM CMMEIA 731 EIA 731

Systems Systems Engr Engr CMM CMM IPD IPD CMM CMM Software Software Acq Acq CMM CMM

People People CMM CMM

FAA FAA iCMM iCMM

Systems Systems Security Security Engr CMM Engr CMM

•Different structures, formats, terms, ways of measuring maturity •Causes confusion, especially when using more than one model •Hard to integrate them in a combined improvement program •Hard touse multiple models in supplier selection
6

CMMI User Group Nov 13, 2001

Bridging the Divide
• Systems and software disciplines have traditionally not been well integrated • The importance of software in systems has increased dramatically – Example: % of requirements allocated to software: *
» B-2 -- 65% » F-22 -- 80%
Systems Software

Mike Phillips CMMI

• The DOD has emphasizedthe need to make the systems/software interface more seamless

* Source: Standish Group Chaos Report
7

CMMI User Group Nov 13, 2001

CMMI to the Rescue!
• Integrates systems and software disciplines into one process improvement framework.

• Provides a framework for introducing new disciplines as needs arise.

CMMI User Group Nov 13, 2001

8

The CMMI Project
• DoD sponsoredcollaboration between industry, Government, academia • Over 100 people involved
• • • • • • • • • • • • • • U.S. Army, Navy, Air Force Federal Aviation Administration National Security Agency Software Engineering Institute ADP, Inc. AT&T Labs BAE Boeing Computer Sciences Corporation EER Systems Ericsson Canada Ernst and Young General Dynamics Harris Corporation • • • • • • • • • • • • • • •Honeywell KPMG Lockheed Martin Motorola Northrop Grumman Pacific Bell Q-Labs Raytheon Reuters Rockwell Collins SAIC Software Productivity Consortium Sverdrup Corporation Thomson CSF TRW
9

CMMI User Group Nov 13, 2001

Air Force Involvement in CMMI Project
Air Force involved in development of CMMI from beginning Steering Group Co-chair: Phil Babel, Ajmel Dulai, Mike Nicol (ASC) Product...
tracking img