CMMI-DEV 1.3 ATM培训 Mod_03

? 2010 Carnegie Mellon University

SM

CMM Integration, SCAMPI, SCAMPI Lead Appraiser, TSP , and IDEAL are service marks of Carnegie Mellon University.

?CMMI, Capability Maturity Model, Capability Maturity Modeling, CMM, and Carnegie Mellon are registered in the US Patent and T rademark Office by Carnegie Mellon University. For more information on CMU/SEI T rademark use, please visit http://www https://www.sodocs.net/doc/a610577849.html,/about/legal-trademarks.html

Software Engineering Institute Carnegie Mellon University Pittsburgh, PA 15213

Module 3:

Overview of CMMI Model Components

Introduction to CMMI-DEV v1.3 –Module 3? 2010 Carnegie Mellon University 2

2010-11-01

Topics

Contents of the CMMI Model Document Process Area Components

Supporting Informative Components

Required, Expected, and Informative Model Components Additions

Glossary Summary

Introduction to CMMI-DEV v1.3 –Module 3? 2010 Carnegie Mellon University 3

2010-11-01

CMMI for Development Model Document Contents

Note 1: Chapter 6 is in the Addison Wesley book. It does not appear in the technical report form of the model.

Generic Goals

and Generic Practices, and the Process Areas

Part Two

A.References

B.Acronyms

C.CMMI V1.3 Project

Participants D.Glossary

Part Three

The Appendices Part One

About CMMI for Development

Preface

1.Introduction

2.Process Area Components

3.Tying It All Together

4.Relationships Among Process Areas

https://www.sodocs.net/doc/a610577849.html,ing CMMI Models

6.Essays and Case Studies

Introduction to CMMI-DEV v1.3 –Module 3? 2010 Carnegie Mellon University

4

2010-11-01

Process Areas (PAs) -1

The 22 process areas (in alphabetical order by acronym) are Causal Analysis and Resolution CAR Configuration Management CM Decision Analysis and Resolution DAR Integrated Project Management IPM Measurement and Analysis MA Organizational Process Definition OPD Organizational Process Focus

OPF Organizational Performance Management

OPM

Organizational Process Performance OPP Organizational Training

OT

Introduction to CMMI-DEV v1.3 –Module 3? 2010 Carnegie Mellon University

5

2010-11-01

Process Areas (PAs) -2

Product Integration

PI Project Monitoring and Control PMC Project Planning

PP Process and Product Quality Assurance PPQA Quantitative Project Management

QPM

Requirements Development RD Requirements Management REQM Risk Management

RSKM

Supplier Agreement Management SAM T echnical Solution TS Validation

VAL

Verification VER

Introduction to CMMI-DEV v1.3 –Module 3? 2010 Carnegie Mellon University 6

2010-11-01

Topics

Contents of the CMMI Model Document Process Area Components Supporting Informative Components

Required, Expected, and Informative Model Components Additions

Glossary Summary

Introduction to CMMI-DEV v1.3 –Module 3? 2010 Carnegie Mellon University 7

2010-11-01

Expected

Informative

Required

Process Area Components We Will Be Discussing

Specific Practices (SP)

Generic Practice Elaborations

Subpractices

Subpractices Example Work Products

Introductory Notes

Related Process Areas

Purpose Statement

Generic Goals

(GG)Specific Goals

(SG)Generic Practices (GP)

Process Area (PA)

Introduction to CMMI-DEV v1.3 –Module 3? 2010 Carnegie Mellon University 8

2010-11-01

Process and Process Area

Process –a sequence of steps performed for a given purpose (IEEE)?It is how you perform your work.

CMMI Definition of a Process –a set of interrelated activities, which transform inputs into outputs, to achieve a given purpose.

These activities can be mapped to one or more practices in CMMI process areas to allow a model to be useful for process improvement and process appraisal.

Introduction to CMMI-DEV v1.3 –Module 3? 2010 Carnegie Mellon University 9

2010-11-01

Process Area

A cluster of related practices in an area that, when implemented collectively, satisfies a set of goals considered important for making improvement in that area.

All CMMI process areas are common to both continuous and staged representations.

They are organized by ?maturity level in the staged representation

?process area category (i.e., Process Management, Project Management, Support, and Engineering) in the continuous representation.

There are 22 process areas.

Introduction to CMMI-DEV v1.3 –Module 3? 2010 Carnegie Mellon University 10

2010-11-01

Process Area Contents

All process areas contain the following ?Purpose Statement ?Introductory Notes ?Related Process Areas

?Specific Goal and Practice Summary ?Specific Practices by Goal

-Specific Goals and Specific Practices ?Generic Practices by Goal

-Generic Goals and Generic Practices

In “Generic Goals and Generic Practices” section in the model.

Introduction to CMMI-DEV v1.3 –Module 3? 2010 Carnegie Mellon University 11

2010-11-01

Expected

Informative

Required

Process Area Components -1

Specific Practices (SP)

Generic Practice Elaborations

Subpractices

Subpractices Example Work Products

Introductory Notes

Related Process Areas

Purpose Statement

Generic Goals

(GG)Specific Goals

(SG)Generic Practices (GP)

Process Area (PA)

Introduction to CMMI-DEV v1.3 –Module 3? 2010 Carnegie Mellon University 12

2010-11-01

Purpose Statement

Describes the purpose of the process area

Project Planning example

Purpose

The purpose of Project Planning (PP) is to establish and maintain plans that define project activities.

DESCRIPTION

EXAMPLE

Introduction to CMMI-DEV v1.3 –Module 3? 2010 Carnegie Mellon University 13

2010-11-01

Introductory Notes

This section describes the major concepts covered in the process area.

Project Planning example

Planning includes estimating the attributes of work products and tasks, determining the resources needed, negotiating commitments, producing a schedule, and identifying and analyzing project risks.

DESCRIPTION

EXAMPLE

Introduction to CMMI-DEV v1.3 –Module 3? 2010 Carnegie Mellon University 14

2010-11-01

Related Process Areas

This section lists references to related process areas and reflects the high-level relationships among the process areas.

Project Planning example

Refer to the Risk Management process area for more information about identifying and analyzing risks and mitigating risks.

DESCRIPTION

EXAMPLE

Introduction to CMMI-DEV v1.3 –Module 3? 2010 Carnegie Mellon University 15

2010-11-01

The titles of the specific goals and specific practices for that process area are summarized at the beginning of each process area.

Project Planning example

SG 1 Establish Estimates

SP 1.1 Estimate the Scope of the Project

SP 1.2 Establish Estimates of Work Product and Task Attributes SP 1.3 Define Project Lifecycle Phases SP 1.4 Estimate Effort and Cost

Specific Goal and Practice Summary

DESCRIPTION

EXAMPLE

Introduction to CMMI-DEV v1.3 –Module 3? 2010 Carnegie Mellon University 16

2010-11-01

Expected

Informative

Required

Process Area Components -2

Specific Practices (SP)

Generic Practice Elaborations

Subpractices

Subpractices Example Work Products

Introductory Notes

Related Process Areas

Purpose Statement

Generic Goals

(GG)Specific Goals

(SG)Generic Practices (GP)

Process Area (PA)

Introduction to CMMI-DEV v1.3 –Module 3? 2010 Carnegie Mellon University 17

2010-11-01

Specific Goals (SGs)

A specific goal is a required model component that describes the unique characteristics that must be present to satisfy the process area.

Project Planning example

SG 1: Estimates of project planning parameters are established and maintained.

Specific goals are numbered starting with the prefix SG (e.g., SG 1). The number is only there to uniquely identify the goal.

DESCRIPTION

EXAMPLE

NUMBERING

Introduction to CMMI-DEV v1.3 –Module 3? 2010 Carnegie Mellon University 18

2010-11-01

Specific Practices (SPs)

Project Planning example

SP 1.4: Estimate the project’s effort and cost for work products and tasks based on estimation rationale.

Specific practices are expected model components that are considered important in achieving the associated specific goal.

Specific practices are of the form SP x.y where

x is the same number as the goal to which the specific practice maps. y is the sequence number of the specific practice under the specific goal.

DESCRIPTION

EXAMPLE

NUMBERING

Introduction to CMMI-DEV v1.3 –Module 3? 2010 Carnegie Mellon University 19

2010-11-01

Example Work Products

Example work products are informative model components that provide sample outputs from a specific practice.

For example, project cost estimates might be an example work product for the Project Planning specific practice SP 1.4,

“Estimate the project’s effort and cost for work products and tasks based on estimation rationale.”

DESCRIPTION

EXAMPLE

Introduction to CMMI-DEV v1.3 –Module 3? 2010 Carnegie Mellon University 20

2010-11-01

Subpractices

Subpractices are informative model components that provide guidance for interpreting and implementing specific or generic practices.

The following is an example of a subpractice from the “Identify and analyze project risks” specific practice (SP 2.2) in the Project Planning process area:

3. Review and obtain agreement with relevant stakeholders on the completeness and correctness of documented risks.

DESCRIPTION

EXAMPLE

Introduction to CMMI-DEV v1.3 –Module 3? 2010 Carnegie Mellon University 21

2010-11-01

Expected

Informative

Required

Process Area Components We Will Be Discussing

Specific Practices (SP)

Generic Practice Elaborations

Subpractices

Subpractices Example Work Products

Introductory Notes

Related Process Areas

Purpose Statement

Generic Goals

(GG)Specific Goals

(SG)Generic Practices (GP)

Process Area (PA)

Introduction to CMMI-DEV v1.3 –Module 3? 2010 Carnegie Mellon University

22

2010-11-01

Generic Goals (GGs) -1

Generic goals are required model components that describe characteristics that must be present to institutionalize processes that implement a process area.

Achievement of a generic goal in a process area signifies improved control in planning and implementing the processes associated with that process area.

Generic goals are called generic because the same goal statement applies to multiple process areas.

Generic goal example

The process is institutionalized as a defined process.

DESCRIPTION

EXAMPLE

Introduction to CMMI-DEV v1.3 –Module 3? 2010 Carnegie Mellon University 23

2010-11-01

Generic Goals (GGs) -2

Generic goals are numbered starting with the prefix GG (e.g., GG 2). The number corresponds to the capability level of the GG.Note: We will talk more about generic goals in Module 4.

NUMBERING

Introduction to CMMI-DEV v1.3 –Module 3? 2010 Carnegie Mellon University 24

2010-11-01

Generic Practices (GPs) -1

Generic practices are expected model components that are considered important in achieving the associated generic goal.Generic practices are called generic because the same practice appears in multiple process areas.

Generic practice example

GP 2.5: Train the people performing or supporting the process as needed.

DESCRIPTION

EXAMPLE

Introduction to CMMI-DEV v1.3 –Module 3? 2010 Carnegie Mellon University 25

2010-11-01

Generic Practices (GPs) -2

Generic practices are of the form GP x.y where x corresponds to the number of the generic goal.

y corresponds to the sequence number of the generic practice.Note: We will talk more about generic practices in Module 4.

NUMBERING

Introduction to CMMI-DEV v1.3 –Module 3? 2010 Carnegie Mellon University 26

2010-11-01

Generic Practice Elaborations

Generic practice elaborations are informative model components that appear after a generic practice to provide guidance on how the generic practice could be applied uniquely to a process area.

Project Planning process area example GP 2.8:

Monitor and Control the Process

Examples of measures and work products used in monitoring and controlling include the following:-Number of revisions to the plan

-Cost, schedule, and effort variance per plan revision -Schedule for development and maintenance of program plans

DESCRIPTION

EXAMPLE

Introduction to CMMI-DEV v1.3 –Module 3? 2010 Carnegie Mellon University 27

2010-11-01

Topics

Contents of the CMMI Model Document Process Area Components

Supporting Informative Components

Required, Expected, and Informative Model Components Additions Glossary Summary

Introduction to CMMI-DEV v1.3 –Module 3? 2010 Carnegie Mellon University 28

2010-11-01

Supporting Informative Components

There are many places in CMMI models where further information is provided.

This further information is provided in the form of the following components:?Examples

?References ?Notes

Introduction to CMMI-DEV v1.3 –Module 3? 2010 Carnegie Mellon University 29

2010-11-01

Examples

An example is a component comprising text and often a list of items, usually in a box, that can accompany nearly any other component and provides one or more examples to clarify a concept or described activity.

Project Planning SP 1.2 example

Examples of attributes to estimate include the following:?Number of functions ?Function points

?Source lines of code ?Number of pages

DESCRIPTION

EXAMPLE

Introduction to CMMI-DEV v1.3 –Module 3? 2010 Carnegie Mellon University 30

2010-11-01

References

A reference is a pointer to additional or more detailed information in related process areas and can accompany nearly any other model component. A reference is an informative model component.

Project Planning SP 2.2 example

Refer to the Risk Management process area for more information about identifying potential problems before they occur so that risk handling activities can be planned and invoked as needed across the life of the product or project to mitigate adverse impacts on achieving objectives.

DESCRIPTION

EXAMPLE

Introduction to CMMI-DEV v1.3 –Module 3? 2010 Carnegie Mellon University 31

2010-11-01

Notes

A note is text that can accompany nearly any other model component. It may provide detail, background, or rationale. A note is an informative model component.

The example below shows a note that accompanies the specific practice 1.3 in the Project Planning process area. Project Planning SP 1.3 example

The determination of a project’s lifecycle phases provides for planned periods of evaluation and decision making. . . .

DESCRIPTION

EXAMPLE

Introduction to CMMI-DEV v1.3 –Module 3? 2010 Carnegie Mellon University 32

2010-11-01

Topics

Contents of the CMMI Model Document Process Area Components

Supporting Informative Components

Required, Expected, and Informative Model Components Additions

Glossary Summary

Introduction to CMMI-DEV v1.3 –Module 3? 2010 Carnegie Mellon University 33

2010-11-01

Required, Expected, and Informative Model Components

Process area components are grouped into three categories . These categories reflect how to interpret the process area components.

Informative

Required

Expected

12

3Three Categories

Introduction to CMMI-DEV v1.3 –Module 3? 2010 Carnegie Mellon University 34

2010-11-01

Required Components

Required components are CMMI components that are essential to achieving process improvement in a given process area. This achievement must be visibly implemented in an organization’s processes.

Goal satisfaction is used in appraisals as the basis for deciding whether a process area has been achieved and satisfied.Specific goals and generic goals are the required components in CMMI models.

Introduction to CMMI-DEV v1.3 –Module 3? 2010 Carnegie Mellon University 35

2010-11-01

Expected Components

Expected Components are CMMI components that describe the activities that are important in achieving a required CMMI component. Expected components guide

?those who implement improvements ?those who perform appraisals

Specific practices and generic practices are the expected components in CMMI models.

Before goals can be considered to be satisfied, either their practices as described, or acceptable alternatives to them, must be present in the planned and implemented processes of the organization.

Introduction to CMMI-DEV v1.3 –Module 3? 2010 Carnegie Mellon University 36

2010-11-01

Informative Components

Informative components are CMMI components that help model users understand the required and expected components of a model.Examples of informative components include ?subpractices

?example work products

?generic practice elaborations ?goal and practice titles ?notes

?references

Introduction to CMMI-DEV v1.3 –Module 3? 2010 Carnegie Mellon University 37

2010-11-01

Expected

Informative

Required

Reviewing Process Area Components

Specific Practices (SP)

Generic Practice Elaborations

Subpractices

Subpractices Example Work Products

Introductory Notes

Related Process Areas

Purpose Statement

Generic Goals

(GG)Specific Goals

(SG)Generic Practices (GP)

Process Area (PA)

Introduction to CMMI-DEV v1.3 –Module 3? 2010 Carnegie Mellon University 38

2010-11-01

Topics

Contents of the CMMI Model Document Process Area Components

Supporting Informative Components

Required, Expected, and Informative Model Components Additions

Glossary Summary

Introduction to CMMI-DEV v1.3 –Module 3? 2010 Carnegie Mellon University 39

2010-11-01

Additions

Additions are clearly marked model components that contain information of interest to particular users.

Additions can be informative material, a specific practice, a

specific goal, or an entire process area that extends the scope of a model or emphasizes a particular aspect of its use.

There are no additions in the CMMI-DEV model.

DESCRIPTION

Introduction to CMMI-DEV v1.3 –Module 3? 2010 Carnegie Mellon University 40

2010-11-01

Topics

Contents of the CMMI Model Document Process Area Components

Supporting Informative Components

Required, Expected, and Informative Model Components Additions

Glossary Summary