Copyright © 2000, Software Productivity Consortium NFP, Inc. All rights reserved. 1 Integrated Processes: On the Horizon PRODUCTIVIT Y CONSORTIUM SOFTWARE

Copyright © 2000, Software Productivity Consortium NFP, Inc. All rights reserved. 1

Integrated Processes:On the Horizon

PRODUCTIVITYCONSORTIUM

SOFTWARE

Carlos C. GalvanAugust 25, 2000


Agenda

Introduction

• CMMI Models

• CMMI Assessments

• Getting Started

• Summary


Software Division

I wonder when they’ll give us our

requirements?

•Management•Aeronautical•Communication•Electrical•Manufacturing•Payload

Current Situation

Adapted from “Transitioning to the CMMI via MBASE” briefing by Dr. Barry Boehm,presented to SEA2000.


Current Situation: Implications

• Organizational processes not aligned

• Business, acquisition

• Systems engineering, software engineering

• Hardware engineering, security engineering

• Separate Process Improvement efforts

• Compete for resources

• Create stove piped processes

• Resulting in sub-optimal enterprise processes!


Solution Areas

• Integrate Processes

• Create organizational processes with

– Well coordinated interfaces

– Common process where possible

– Careful consideration of negotiation and commitment process

– Emphasis on critical information flows

• Industry example responses:

– University of Southern California’s MBASE

– Consortium’s Integrated Systems and Software Engineering Process (ISSEP)

• Integrate Process Improvement initiatives

• Industry response: CMMISM

SM – CMMI and CMM Integration are service marks of Carnegie Mellon University


How

did we get here?

CMM for Software V1.01991

CMM® for Software V1.11993

SE-CMM V1.11996

SECAM1996

But, what about• SA-CMM• P-CMM• PSP• SPICE / ISO 15504• ISO 12207• and others?

SW-CMM V2.0 Draft C*1997

IPD-CMM V0.98*1997

* Not released

CMMI-SE/SW V1.0

EIA/IS 7311999

® Capability Maturity Model and CMM are registered with the U.S. Patent and Trademark Office

August 11, 2000


Objectives of

CMMI

• Encourage integration of disciplines

• Integrate models

• Eliminate duplication of material

• Remove conflicts between models

• More efficient to have an integrated model for:

• Process improvement

• Process assessment

• Improve the models

• Equally applicable and important to government (defense and civil) agencies, aerospace & defense and systems integration companies, as well as commercial organizations

CMM EIA/IS 731

IPD-CMM

CMMI


CMMI

Project

• Sponsored by DoD and NDIA

• Project team includes representatives from• Government

• Industry

• SEI

• Coordinated by SEI


CMMI Project


CMMI Project Plan

Task Name

Product Suite Development V1.0

Pilot Assessments

Product Suite Updates V1.1

CMM V1.1 Continuing Support

1997 1998 1999 2000 2001 2002 20031997 1998 1999 2000 2001 2002 2003

CMMI-SE/SW V1.0 published August 11, 2000

(Note: IPPD process areas are scheduled to be added within one month.)

http://www.sei.cmu.edu/cmmi/ for models, news, and plans


Agenda

• Introduction

CMMI Models


• Getting Started

• Summary


•0 •1 •2 •3 •4 •5

•Analyze Solutions

•Architecture

•Integrate System

•Verify & Validate

•Configuration Mgmt.

•Tracking

•Define Process

•Product Evolution

•Training

But the architectures are different...

CMM for Software - Staged ModelSEI Solution: Include both Model Representations – An elegant solution, but difficult to implement

• CMMI-SE/SW Staged or Continuous Representation• CMMI-SE/SW/IPPD Staged or Continuous Representation

Capability Levels

SE-CMM - Continuous Model

Sample

Results

Staged Maturity Level - Process Areas are assessed using the practicesContinuous Capability Level - Process Areas are assessed using the specific practices within an area and the generic practices required for a specific level

CMMI “Informative Material” provides implementation detail for representative or anticipated Systems, Software, and IPPD usages

Level Key Process Areas

ContinuousImprovement

Heroes

Focus

4

Optimizing

3

2

1

5Process change managementTechnology change managementDefect Prevention

Software quality managementQuantitative process management

Organization process focusOrganization process definitionPeer ReviewsTraining programIntergroup coordinationSoftware product engineeringIntegrated software managementRequirements managementSoftware project planningSoftware project tracking & oversightSoftware subcontract managementSoftware quality assuranceSoftware configuration management

Managed

Defined

Repeatable

Initial

Product and Process Quality

EngineeringProcess

ProjectManagement

Model Architectures

Pro

cess

Are

as


Staged Model Structure

Informative Material

MaturityLevels

Process Areas

SpecificGoals

Process Areasare assessedto determine the Maturity Level

Specific Practices

Directing Implementation

Verifying Implementation

Ability to Perform

Commitment to Perform

GenericGoals

Generic Practices


Continuous Model Structure

Process Areasare assessedusing the Genericsto determine the capability level

ContinuousModels

Informative Material

Process Areas

Specific Practices

SpecificGoals

Capability Levels

Generic Goals

Generic Practices

Process ManagementProject ManagementEngineering Support

Categories


Major Sources of Changes

• Generalized wording to applied to both systems and software engineering

• Took “union” of source models

• “Raised the bar” on some legacy elements

• Expanded Software Product Engineering KPA• Requirements Development

• Technical Solution

• Product Integration

• Verification

• Validation


5Optimizing

Optimizing

4Managed

Quantitatively

Managed

3Defined

Defined

2Repeatable

Managed

Maturity Levels of

Staged Models

1Initial

Performed

The names of the levels have changed,but the concepts remain the same.


Level 2 - Repeatable

CMM V1.1

Level 2 - Managed

CMMI

Software

Model Relationships

Requirements Management

Project Planning (incls DM)

Project Monitoring and

Control

Supplier Agreement

Management

Measurement and Analysis

Process and Product Quality

Assurance

Configuration Management


Software Project Planning

Software Project Tracking

and Oversight

Software Subcontract

Management

Software Quality Assurance

Software Configuration

Management

Generalize

Generalize

Generalize

CMM V2.0 C

Consolidate

Generalize

EIA/IS 731

Generalize

Source of Change

CMMI Level 1 – Performed (No Process Areas)


Level 3 - Defined

CMM V1.1

Level 3 - Defined

CMMI

Organizational Process FocusOrganizational Process

DefinitionOrganizational TrainingIntegrated Project

ManagementRequirements Development

Technical SolutionProduct IntegrationVerificationValidationRisk ManagementDecision Analysis and

Resolution

Organization Process FocusOrganization Process

Definition Training Program Integrated Software

ManagementSoftware Product

EngineeringIntergroup CoordinationPeer Reviews*

*(Now part of CMMI Product Verification Required Goal)

GeneralizeGeneralize

GeneralizeGeneralize

EIA/IS 731

EIA/IS 731EIA/IS 731EIA/IS 731EIA/IS 731EIA/IS 731EIA/IS 731

Software

Model Relationships

Source of Change


The Engineering Process AreasSoftware Product Engineering KPA has been expanded to five new process areas

SoftwareProduct

Engineering


Adapted from “Transitioning to the CMMI Product Suite” briefing by Jon Gross, presented to SSQ on 4/11/2000.


RequirementsDevelopment

TechnicalSolution

ProductIntegration

Verification Validation


Level 4 - Managed

CMM V1.1Level 4 –

Quantitatively Managed

CMMI

Quantitative Project Management

Organizational Process Performance

Causal Analysis and Resolution

Organizational Innovation and Deployment

Quantitative Process Management

Software Quality Management

Defect PreventionTechnology Change

ManagementProcess Change

Management

Generalize + statistical

Generalize

Generalize

Generalize

Generalize

Source of Change

Level 5 - Optimizing Level 5 – Optimizing

Software

Model Relationships


Engineering

PA06 Understand Customer Needs and Expectations

PA02 Derive and Allocate Requirements

PA03 Evolve System Architecture

PA01 Analyze Candidate Solutions

PA05 Integrate SystemPA07 Verify and Validate

SystemPA04 Integrate

Disciplines

SE-CMMEngineering

CMMITechnical

1.1 Define Stakeholder and System Level Requirements

1.2 Define Technical Requirements

1.3 Define Solution1.4 Assess and

Select1.5 Integrate System1.6 Verify System1.7 Validate System

SECM

2.3

Req’s Management

Req’s Development

Technical Solution

Product Integration

Verification

Validation

Support

SW

System Model Relationships

EIA/IS 731


Project ManagementProject Planning

Project Mon and Ctl

Supplier Agree Mgt

Integrated Proj Mgt

Risk Management

Quantitative Proj Mgt

* Not in SE-CMM

SE-CMM

Management

2.1 Plan and Organize2.2 Monitor and

Control 2.3 Integrate

Disciplines 2.4 Coordinate with

Suppliers2.5 Manage Risk2.6 Manage Data2.7 Manage

Configurations2.8 Ensure Quality

SECM

*

Project

PA12 Plan Technical Effort

PA11 Monitor and Control Technical Effort

PA10 Manage RiskPA09 Manage

ConfigurationsPA08 Ensure Quality

CMMI

PA04

PA18

SupportConfiguration Mgt

Proc and Prod QA

Meas and Analysis

Causal Anl and Res

Decision Anl and Resolution

1.4

L2 GP


EIA/IS 731

L4 GP

L5 GP


SE-CMMEnvironment

3.1 Define and Improve the SE Process

3.2 Manage Competency

3.3 Manage Technology

3.4 Manage SE Support Environment

SECMOrganization

PA13 Define Organization’s SE Process

PA14 Improve Organization’s SE Process

PA17 Provide Ongoing Knowledge and Skills

PA15 Manage Product Line Evolution

PA16 Manage SE Support Environment

PA18 Coordinate With Suppliers

CMMI

Org Process Focus

Org Process Definition

Organizational Tng

Org Process Perf

Org Innovation and Deployment

Process Management

2.4

L4 GP

SW



Integrated Product and Process Development

IPPD Model Components Additions• Additions and amplifications of CMMI SE/SW process areas

• Additional IPPD process areas:

• Level 2

• Collaborative Leadership

• Shared Vision Building

• Level 3

• Organizational Environment for Integration

• Integrated Team

From CMMI-SE/SW/IPPD Staged Representation, initially released December 1999

To be Released, concurrently, as part of the CMMI, either in August 2000 (CMMI 1.0 release date, as announced by DOD, Dr. Delores Etter, Deputy Under Secretary of Defense (Science & Technology), at the STC Conference May 2, 2000) or within one month after release of the CMMI


Agenda

• Introduction

• CMMI Models

CMMI Assessments

• Getting Started

• Summary


CMMI Process Assessments• Plan is to support a variety of

assessment types

• Quick-look assessments

• First assessments

• Reassessments

• First effort will focus on CBA IPI like assessment method called:

• Standard CMMI Assessment Method for Process Improvement “SCAMPI”


Assessment Challenges• Assessment method issues to be resolved

• Breadth versus depth

• Spot checks versus complete coverage

• Interpretations in SW, SE, and integrated environments

• Assessment team

• Number of team members increased

• Domain expertise of team members

• Length (and cost) of assessment related to number of practices

• CMM V1.1: 316 practices

• EIA/IS 731: 383 practices

• CMMI V0.2 SE/SW: 431 practices

• CMMI SE/SW/IPPD: 501 practices


Agenda

• Introduction

• CMMI Models


Getting Started

• Summary


What Should You Do Now?

• Identify your business objectives

• Evaluate current processes

• Identify areas of the process infrastructure that overlaps and will support integration efforts

• Identify threads that cross discipline boundaries that are critical

• Identify processes that are used by both systems and software engineering

• Decide on Staged vs. Continuous PI Approach


Business Objectives

• Identify your business objectives

Reduce costs of PI, while continuing to improve

Align organizational processes

Develop common processes across organization

Maintain maturity level credentials


Evaluate Processes

• Evaluate current processes

• Map existing processes to models and standards of interest: CMM, EIA/IS 731, SE-CMM, ISO 9000, high level enterprise processes

• Map existing processes to CMMI V1.0

• Perform a quick-look evaluation

®

® Quagmap is registered with the U.S. Patent and Trademark Office


Process Infrastructure• Identify areas of the process infrastructure that

overlap and can support integration efforts

SponsorshipSteering committeeProcess groupProcess asset libraryProcess database

Begin now to consolidate the infrastructure


Process Threads• Identify threads that cross discipline boundaries and

are critical

Requirements processIntegrationVerification

Begin now to improve these processes


Common Processes• Identify processes that are used by both systems and

software engineering

Quality assuranceConfiguration

managementInspectionsRisk managementProject management

Begin now to create one common process


Agenda

• Introduction

• CMMI Models


• Getting Started

Summary


Consortium CMMI Plans

• Author team participation and review

• Assessment methods

• Training and other deployment support products

• Impact Assessment

• Summarize changes

• Transition course

• Consortium product and service updates

CMM EIA/IS 731

IPD-CMM

CMMI


SW-CMM

Also see: www.software.org/quagmire

The Frameworks QuagmireThe Frameworks QuagmireMIL-Q -9858

Trillium Baldrige

IEEE Stds. 730,828 829, 830,1012,1016

1028,1058,1063ISO 15504(SPICE)

People CMM

IPD-CMM*

DOD IPPD

SECAMAF IPD Guide

SDCCR

SCE

NATO AQAP1,4,9

BS5750

MIL-STD-

498

DOD-STD -2167A

DOD-STD -7935A

MIL-STD-499B*

ISO/IEC12207

IEEE1220 ISO 10011

SDCE

SE-CMMSECM(EIA/IS 731)

EIA/IS 632

ISO 9000Series

EIA/IEEEJ-STD-016

IEEE/EIA 12207

EIA 632

MIL-STD-1679

IEEE 1074

TickITSSE-CMM

ISO 15288*

EQA

* Not released** Aug 11, 2000

CMMI**

PSP

SA-CMM

Q9000

DOD-STD-2168

FAA-iCMM

DO-178B

SW-CMM


The Future???The Future???MIL-Q -9858

Trillium Baldrige

IEEE Stds. 730,828 829, 830,1012,1016

1028,1058,1063

ISO 15504(SPICE)

DOD IPPD

AF IPD Guide

NATO AQAP1,4,9

BS5750

MIL-STD-

498

DOD-STD -2167A

DOD-STD -7935A

MIL-STD-499B*

ISO/IEC12207

IEEE1220 ISO 10011EIA/IS

632

ISO 9000Series

EIA/IEEEJ-STD-016

IEEE/EIA 12207

EIA 632

MIL-STD-1679

IEEE 1074

TickIT

ISO 15288*

EQA

* Not released

CMMI

PSP

Q9000

DOD-STD-2168

DO-178B

• Software• Systems• IPPD• Acquisition• Security• People


Conclusions: A Recommended Approach• Begin now to:

• Integrate your Processes

• Integrate your Process Improvement Initiatives and Infrastructures

• Begin or Continue to Improve your Systems Engineering Processes

• Complete “Next/Near Term” Scheduled Assessment

• Study CMMI and Impact on PI Program

• Determine Business Case for CMMI

• Formulate CMMI Transition Strategy Plans

• Determine how to Establish, Expand, Update, and/or Integrate SE/SW/IPPD Process Areas

• Determine Staged vs. Continuous PI Business Case Approach for SE/SW/IPPD

The Consortium can provide a wide variety of Products and Services to support your CMMI Systems and Software Engineering Process Integration and Improvement efforts.


CMMI – Web Links

• Software Engineering Institute (SEI)

• http://www.sei.cmu.edu/cmmi

• Software productivity Consortium (SPC)

• http://www.software.org

• Software Technology Support Center

• http://www.stsc.hill.af.mil


AcronymsCBA IPI CMM Based Appraisal for Internal Process Improvement

CMM Capability Maturity Model for Software

CMMI Integrated Capability Maturity Model

DoD Department of Defense

EIA/IS Electronics Industries Alliance / Interim Standard

FAA Federal Aviation Administration

GP Generic Practice

IPD-CMM Integrated Product Development Capability Maturity Model

IPPD Integrated Product and Process Development

ISO International Organization for Standardization

ISSEP Integrated Systems and Software Engineering Processhttp://www.software.org for more information

KPA Key Process Area

MBASE Model Based (System) Architecting and Software Engineeringhttp://sunset.usc.edu/research/MBASE/index.html for more info

NDIA National Defense Industrial Association


AcronymsNSA National Security Agency

PA Process Area

P-CMM People Capability Maturity Model

PDT Product Development Team

PI Process Improvement

PSP Personal Software Process

SA-CMM Software Acquisition Capability Maturity Model

SCAMPI Standard CMMI Assessment Method for Process Improvement

SE Systems Engineering

SECAM Systems Engineering Capability Assessment Model

SE-CMM Systems Engineering Capability Maturity Model

SEI Software Engineering Institute

SPC Statistical Process Control

SPICE Software Process Improvement and Capability deTermination

SW Software

SW-CMM Software Capability Maturity Model

Documents

Copyright © 2000, Software Productivity Consortium NFP, Inc. All rights reserved. 1 Integrated Processes: On the Horizon PRODUCTIVIT Y CONSORTIUM SOFTWARE