Introduction to the Software Engineering Institute (SEI) and the Capability Maturity Model (CMM)

1
Introduction to theSoftware Engineering
Institute (SEI)and theCapability Maturity Model
(CMM)

• Paul Sesto, Software Engineering Manager

2
Class Outline

• The Software Engineering Institute (SEI) and the
  Capability Maturity Model (CMM)
• Importance of SEI CMM in Industry
• Frame of Reference Project - IADS
• Major Components of the CMM
• Northrop Grumman Implementation of CMM
• Software Engineering Process Organization (SEPO)
• Organizational Standard Software Process (OSSP)
• Software Process Asset Library (SPAL)
• Software Project Planning
• Northrop Grumman Commercial

3
Evolution of the SEI

• Software Crisis Developed over Past Few Decades
• Questionable Quality of Delivered Products
• Cost Schedule Overruns Pervasive
• Department of Defense Catastrophes Persist
• Cost Overruns of Software Acquisition Rising by
  the Millions
• Schedule Delays of Not Months but Years
• Multi-Billion-Dollar Systems Dont Perform as
  Envisioned
• Projects Cancelled Due to Poor Software Quality
• Commercial Industry Suffered Similar Problems
• Complexity of Software Continues to Increase
• Industry Leaders Deemed Software Crisis to be a
  Management Problem and Not a Technical Problem

4
What is the SEI?

• Software Engineering Institute
• Federally Funded Research Development Center
• Sponsored by the U.S. Department of Defense
• Contract Competitively Awarded to Carnegie Mellon
  University in 1984
• CMU Staff is A Consortium of Government, Industry
  Academia
• SEI Mission
• Provide Leadership in Advancing the State of the
  Practice of Software Engineering to Improve the
  Quality of Systems that Depend on Software
• Visit the SEI at www.sei.cmu.edu

5
What is the Capability Maturity Model (CMM)

• Framework to Help Organizations Improve Their
  Processes
• Documented Practices for Software Development
• Model for Continuous Improvement
• Guidelines, not Rules, on how to Best Run
  Programs
• Evolving to Address Other Standards (ISO-9001)
• Method for Assessing Maturity of an
  Organization
• Five Maturity Levels
• Successive Foundations of Process Improvement
• Used by DoD to Evaluate Contractors
• Multiple CMMs Exist
• Software Development
• Integrated Product Team Development
• Systems Engineering
• Personal Software Process
• CMMI
• Initiative to Integrate Multiple Models

6
Fundamental Concepts of Process Maturity
Software Process set of activities, methods,
practices, and transformations that people employ
to develop and maintain software and the
associated products.
internal SDP
SW Product
Underlying Premise quality of a software
product is largely determined by the quality of
the process used to develop and maintain it.
7
Five Levels of Software Maturity

• Level 1 Initial
• Process is ad hoc, even chaotic
• Success depends on individual
• effort and heroics.

• Level 4 Managed
• Detailed measures of software process
• product quality collected
• SW process products are
• quantitatively understood controlled.

• Level 2 Repeatable
• Basic project mgt processes established
• Earlier successes can be repeated
• on projects with similar applications.

• Level 5 Optimizing
• Continuous process improvement
• enabled
• Quantitative feedback from the process
• Piloting innovative ideas technologies.

• Level 3 Defined
• Process for mgt and engineering
• documented, standardized, integrated
• at organization level
• All projects use version of standard
• software process.

8
Practices at Each Level
2 3 4 5
9
Practices At Each Level
2 3 4 5
Technology Assessment Technology support
established, X stable activities Planning
mgt data used by projects X New technologies
- evaluated qualitatively X Data collected
used in all defined processes X X X Data
systematically shared by projects X X X Data
definition collection standardized X X
across organization Data used to
understand process X X quantitatively
stabilize it Data used to evaluate
select X process improvements
10
Class Outline

• The Software Engineering Institute (SEI) and the
  Capability Maturity Model (CMM)
• Importance of SEI CMM in Industry
• Frame of Reference Project - IADS
• Major Components of the CMM
• Northrop Grumman Implementation of CMM
• Software Engineering Process Organization (SEPO)
• Organizational Standard Software Process (OSSP)
• Software Process Asset Library (SPAL)
• Software Project Planning
• Northrop Grumman Commercial

11
Benefits of Software Process Maturity
12
Why Bother With CMM Certification?
Level 4 is necessary to remain a leader in
todays market!
13
CMM Level 3 is a DOD Requirement
14
Class Outline

• The Software Engineering Institute (SEI) and the
  Capability Maturity Model (CMM)
• Importance of SEI CMM in Industry
• Frame of Reference Project - IADS
• Major Components of the CMM
• Northrop Grumman Implementation of CMM
• Software Engineering Process Organization (SEPO)
• Organizational Standard Software Process (OSSP)
• Software Process Asset Library (SPAL)
• Software Project Planning
• Northrop Grumman Commercial

15
IADS - The Real World

• Air Defense Requires Centralized Facility
• Integrates Country Wide Infrastructure
• Data Voice Communications
• Network of Workstations PCs
• Distributed Architecture Displays
• 1.5 Million Lines of Software
• Written in Ada95, Java, PWB SQL
• Object Oriented Design Development
• 85 Software Engineers at Peak on 15 Integrated
  Product Teams
• Started with a Specification and Statement of
  Work of 600 Pages
• Standard Processes Procedures Facilitated On
  Target Completion

16
Class Outline

• The Software Engineering Institute (SEI) and the
  Capability Maturity Model (CMM)
• Importance of SEI CMM in Industry
• Frame of Reference Project - IADS
• Major Components of the CMM
• Northrop Grumman Implementation of CMM
• Software Engineering Process Organization (SEPO)
• Organizational Standard Software Process (OSSP)
• Software Process Asset Library (SPAL)
• Software Project Planning
• Northrop Grumman Commercial

17
Structure of the CMM
18 Total KPAs
5 Per KPA
18
CMM Defined Key Process Areas (KPAs)
19
Each KPA Has 5 Common Features

• 1. Commitment to Perform
• Written organizational policy required addresses
  every KPA
• ESSS Software Process Manual

• 2. Ability to Perform
• Adequate resources/training required for every
  KPA
• ESSS WSAs at organization and project level

• 3. Activities Performed
• Activities, roles, procedures necessary to
  implement a KPA
• ESSS management plans, procedures, technical
  directives

20
Each KPA Has 5 Common Features

• 4. Measurement and Analysis
• Basic measurement practices necessary to
  determine status related to the process
• ESSS metrics (technical management), Level 4
  Software Quantitative Management

• 5. Verifying Implementation
• Steps to ensure that the activities are performed
  in compliance with the process that has been
  established.
• ESSS Project and senior management reviews,
  software quality audits, SEI and ISO audits,
  reports to SEPO

21
KPA Example - Peer Reviews

• Peer review activities are planned
• Defects in the software work products are
  identified and removed

22
Peer Review - Key Practices

• 1. Commitment to Perform
• The project follows a written organizational
  policy for performing peer reviews.

• 2. Ability to Perform
• Adequate resources and funding are provided for
  performing peer reviews on each software work
  product to be reviewed.
• Peer review leaders receive required training in
  how to lead peer reviews.
• Reviewers who participate in peer reviews receive
  required training in the objectives, principles,
  and methods of peer reviews.

WSAs
23
Peer Review - Key Practices

• 3. Activities Performed
• Peer reviews are planned, and the plans are
  documented.
• Peer reviews are performed according to a
  documented procedure.
• Data on the conduct and results of the peer
  reviews are recorded

• 4. Measurement and Analysis
• Measurements are made and used to determine the
  status of the peer review activities

• 5. Verifying Implementation
• The SW Quality Group reviews and/or audits the
  activities and work products for peer reviews and
  reports the results.

QA
24
KPA Summary
KPAs Describe What is to be Done to Satisfy the
Desired Goals

• Key Process Area
• Goals
• Common Features
• Commitment to Perform
• Ability to Perform
• Activities Performed
• Measurement and Analysis
• Verifying Implementation

During an Assessment Each KPA is Evaluated for
Objective Evidence of the Common Features for
Organizational Institutionalization
25
Class Outline

• The Software Engineering Institute (SEI) and the
  Capability Maturity Model (CMM)
• Importance of SEI CMM in Industry
• Frame of Reference Project - IADS
• Major Components of the CMM
• Northrop Grumman Implementation of CMM
• Software Engineering Process Organization (SEPO)
• Organizational Standard Software Process (OSSP)
• Software Process Asset Library (SPAL)
• Software Project Planning
• Northrop Grumman Commercial

26
Software Engineering Process Organization

• SEPO is the Enterprise Governing Organization
• Provides Project Support
• Software Project Planning
• Process Definition
• Process Improvement
• Artifact Collection

27
Process Definition Project Planning
28
SEPO Provides Process Improvement
Process Pilots
29
Organizational Standard Software Process

• OSSP Facilitates Organizational Standard
  Processes
• Accessible via Corporate Intranet Web-Site
• Supports SEI Level-4 Objectives
• Promotes Standardization
• Increases Software Productivity Quality

30
Software Process Asset Library (SPAL)

• Policies
• Procedures
• Compliance Checklists
• iSDP Generation
• Tailoring Process
• Training

31
Software Project Planning is Simplified
. . . When Projects Tailor from the Standard
Process
32
Templates Exist for Each Plan
33
Standard Tool Usage . . .
. . . Reduces Software Development Costs
34
Training is CMM Requirement
35
OSSP Core Curriculum
Introductory
Intermediate
Specialty Topics
Integrated Product Teams (IPTs) (ESSS Development
Course)
Software Development Overview for Program
Managers
Quantitative Software Mgmt for Executives
Executives Program Managers
Introduction to the CMM and the ESSS Organizatl
Standard Software Process
Requirements Management
Managing Software Development
Work Product Inspections
Software Engineering Lifecycle Overview
Software Managers Software Technical Leads
Software Project Estimation
Software Project Planning
Training Plan Development
Legal Issues Associated with Software Development
Subcontract Management
Quantitative Software Mgmt
Software Creation
Engineers
Software Testing
Software Quality Assurance
Software Configuration Mgmt
36
Software Standard Tools Web Page

• Electronic Format of the Software Tools Web Page
  Is Located on the Intranet At
• http//spal.md.essd.northgrum.com
• ? click on SPAL
• ? click on Tools on the SPAL diagram

37
Standard Metrics . . .
Refine Project Process Improve Organizational Pro
cess Support New Project Planning Efforts
Metrics Database
Provide Project Process Insight
38
Class Outline

• The Software Engineering Institute (SEI) and the
  Capability Maturity Model (CMM)
• Importance of SEI CMM in Industry
• Frame of Reference Project - IADS
• Major Components of the CMM
• Northrop Grumman Implementation of CMM
• Software Engineering Process Organization (SEPO)
• Organizational Standard Software Process (OSSP)
• Software Process Asset Library (SPAL)
• Software Project Planning
• Northrop Grumman Commercial

39
Summary
SEI
The SEI was established and funded by the DoD to
address the Software Crisis. It provides
leadership to advance the practice of software
engineering to improve the quality of systems.
The CMM represents the model by which software
organizations are assessed to establish
organizational process maturity (5 Levels).
CMM
Process Maturity
The quality of a software product is largely
determined by the quality of the process used
to develop and maintain it.
Northrop Grumman
Northrop Grummans CMM Implementation is governed
by SEPO and implemented using OSSP SPAL.