Cmmi A Comprehensive Overview

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,2001

2

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 performthat 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 MaturityModel®, 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

staged

software development

System Engineering CMM

continuous

system engineering

System Engineering Capability Model

continuous

system engineering

Software Acquisition CMM

stagedsoftware acquisition

System Security Engineering CMM

continuous

security engineering

Personal Software Process

staged

individual software
development

FAA-iCMM

continuous

software engineering,
systems engineering,
and acquisition

IPD-CMM

continuous

integrated product
development

People CMM

staged

workforce

SPICE Model

continuous

softwaredevelopment

CMMI User Group Nov 13, 2001

5

So Many Models, So Little Time
Software
Software
CMM
CMM

EIA 731
EIA 731

Systems
Systems
Engr
Engr
CMM
CMM
IPD
IPD
CMM
CMM

FAA
FAA
iCMM
iCMM

ZZZ
ZZZ
CMM
CMM

People
People
CMM
CMM

Software
Software
Acq
Acq
CMM
CMM
Systems
Systems
Security
Security
Engr CMM
Engr CMM

CMMI User Group Nov 13, 2001•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 to use multiple
models in supplier
selection
6

Bridging the Divide
• Systems and software
disciplines have
traditionally not been well
integrated

Systems

• The importance of software
insystems has increased
dramatically
– Example: % of
requirements allocated to
software: *

Software

Mike Phillips
CMMI

» B-2 -- 65%
» F-22 -- 80%

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

* Source: Standish Group Chaos Report

CMMI User Group Nov 13, 2001

7

CMMI to the Rescue!
• Integrates systems and softwaredisciplines 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 sponsored collaboration
between industry, Government, academia
• Over 100 people involved
•
•
•
•
•
•
•
•
•
•
•
•
•
•

U.S. Army, Navy, Air Force
Federal Aviation Administration
National SecurityAgency
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...