CMMiIEEE

7/28/2019 CMMiIEEE

http://slidepdf.com/reader/full/cmmiieee 1/47

6/19/09 osgg.net 1

Using IEEE Software Standards in

the CMMi v1.2 maturity level 2

Modelos y métodos para laevaluación y mejora de procesos

Omar Salvador Gómez Gómez

7/28/2019 CMMiIEEE


6/19/09 Omar Gómez – www.osgg.net 2

Objective

To show the set of IEEE software standardsthat can be used to provide the basic

beginning framework in CMMi v1.2

maturity level 2

7/28/2019 CMMiIEEE



Agenda

Previous Work Process Area Components

IEEE Software Standards used in CMMi v1.2

Level 2

Conclusions

7/28/2019 CMMiIEEE



History of CMMS

7/28/2019 CMMiIEEE



Staged representation & Process Areas

7/28/2019 CMMiIEEE


6/19/09 OG v3.0 6

Staged Representation: PAs by MaturityLevel

7/28/2019 CMMiIEEE



Maturity Level 2

At this level, projects of the organizationhave ensured that processes are planned and

executed in accordance with policy

The work products and services satisfy their

specified process descriptions, standards

and procedures.

7/28/2019 CMMiIEEE



IEEE Software Standards

The IEEE Computer Society is the largest association for computer professionals in the world.

Any IEEE Computer Society standards project is assigned

to one of a dozen or so "sponsors.”

For software engineering standards, the sponsor is the

Software Engineering Standards Committee (SESC).

The SESC traces its roots back to 1976

Its first standard, IEEE Std 730™, IEEE Standard for

Software Quality Assurance Plans

7/28/2019 CMMiIEEE


6/19/09 OG v3.0 9

IEEE Software Standards

IEEE Standards can be used as tools to help in the processof ‘self-documentation’

Many of the standards provide detailed procedure

explanations, they offer section by section guidance on

building the necessary documentation

Most importantly, they provide the best practice as defined

by those from the software development industry who sit

on the panels of reviewers

7/28/2019 CMMiIEEE


6/19/09 OG v3.0 10

Relation between CMMi and IEE SoftwareStandards

CMMi is a compendium of software engineering practices,which act as the motivator for the continuous evolution of

improved software engineering processes

IEEE standards can be used to provide the basic beginning

framework for software process improvement

IEEE set of software engineering standards can be applied to facilitate CMMi level 2

7/28/2019 CMMiIEEE


6/19/09 OG v3.0 11


CMMi Provide guidance for improving the processes

within an Organization

IEEE software standards Provide a family of products and services based on

software engineering standards

7/28/2019 CMMiIEEE


6/19/09 OG v3.0 12


The standards specify format and content with norecommendation of the exact techniques to be

used

The standards represent industry best practices having been developed by domain experts with

broad expert consensus

The standards specify the minimum required contents for each CMMi support document

7/28/2019 CMMiIEEE


6/19/09 OG v3.0 13


IEEE standards can be used to develop your baseline process documentation

IEEE standards provide documentation

templates and describe in detail what the

processes should contain

7/28/2019 CMMiIEEE


6/19/09 OG v3.0 14

IEEE Standard structure

Each standards contain the following structure: Introduction

Participants

Contents

1. Overview

2. References

3. Definitions and Acronyms

4. Standard description

..

Annex ..

7/28/2019 CMMiIEEE


6/19/09 OG v3.0 15

IEEE Standards and Process Areas Process Area Standard

REQM Requirements Management IEEE Std 830 - 1998, IEEE Recommended Practice for Software Requirements

SpecificationsIEEE Std 1233-1998(R2002), IEEE Guide for Developing System Requirements

Specifications

PP Project Planning IEEE Std 1058 - 1998, IEEE Standard for Software Project Management Plans

IEEE Std 1490-1998, IEEE Guide Adoption of PMI Standard, A guide to the Project

Management Body of Knowledge

PMC Project Monitoring and Control

IEEE Std 1058 - 1998, IEEE Standard for Software Project Management Plans

SAM Supplier Agreement

Management

IEEE Std 1062 - 1998, IEEE Recommended Practice for Software Acquisition

MA Measurement and Analysis IEEE Std 1045 - 2002, IEEE Standard for Software Productivity Metrics

PPQA Process and Product Quality

Assurance

IEEE Std 730 - 2002, IEEE Standard For Software Quality Assurance

CM Configuration Management IEEE Std 828 - 1998, IEEE Standard for Software Configuration Management Plans

7/28/2019 CMMiIEEE


6/19/09 OG v3.0 16

Requirements Management REQM

Purpose Manage the requirements of the project’s

products and product components and

identify inconsistencies between those

requirements and the project’s plans and

work products.

7/28/2019 CMMiIEEE


6/19/09 OG v3.0 17


Goals SG 1: Manage Requirements

Requirements are managed and inconsistencies

with project plans and work products are

identified

7/28/2019 CMMiIEEE


6/19/09 OG v3.0 18


IEEE Std 830-1998, IEEE Recommended Practice for SoftwareRequirements Specifications

Outlines the requirements for what comprises a good SoftwareRequirements Specification (SRS):

Establish the basis for agreement between the customers and

suppliers on what the software product is to do Reduces the development effort

Provides a basis for estimating costs and schedules

Provides a baseline for validation and verification

Facilitates transfer Serves as a basis for enhancement

Does not directly address Requirements Traceability

7/28/2019 CMMiIEEE


6/19/09 OG v3.0 19

Mapping between REQM and IEEE Std 830-1998

Requirements Management REQM IEEE Std 830-1998

IEEE Recommended Practice for Software

Requirements Specifications

SG 1 Manage Requirements

SP 1.1 Obtain an Understanding of

Requirements

Yes

SP 1.2 Obtain Commitment to

Requirements

Yes, clause 4.4 Joint preparation of

the SRS

SP 1.3 Manage Requirements Changes Yes, In the clause 4.5 SRS evolution,

the standard suggest two ways of

formal change process

SP 1.4 Maintain Bidirectional Traceability

of Requirements

Traceable, as characteristic that a

SRS must have (clause 4.3.8)

SP 1.5 Identify Inconsistencies Between

Project Work and Requirements

SRS must be verifiable (clause 4.3.6)

7/28/2019 CMMiIEEE


6/19/09 OG v3.0 20

Project Planning PP

Purpose Establish and maintain plans that define

project activities

7/28/2019 CMMiIEEE


6/19/09 OG v3.0 21

Project Planning PP

Goals

SG 1: Establish Estimates

Estimates of project planning parameters areestablished and maintained

SG 2: Develop a Project Plan

A project plan is established and maintained as the basis for managing the project

SG 3: Obtain Commitment to the Plan Commitments to the project plan are established and

maintained

7/28/2019 CMMiIEEE


6/19/09 OG v3.0 22

Project Planning PP

IEEE Std 1058, IEEE Standard for Software Project

Management Plans Specifies a suggested format for a project management

plan

This document may be used as a guide for documentingthe practices and procedures unique to eachorganization for all types of software efforts

The IEEE Standard for Project Management Plans can

be used as a model for this CMMi level process The purpose of CMMi level 2 Software Project Planning is

to establish reasonable plans for performing softwareengineering and software project management

7/28/2019 CMMiIEEE


6/19/09 OG v3.0 23

Mapping between PP and IEEE Std 1058-1998

Project Planning PP IEEE Std 1058-1998

IEEE Standard for Software ProjectManagement Plans

SG 1 Establish Estimates clause 4.1.1.1 Purpose, scope, and objectives

clause 4.5.1.1 Estimation plan

clause 4.1.1.3 Project deliverables

clause 4.5.2.1 Work activities

SG 2 Develop a Project Plan clause 4.1.1.4 Schedule and budget summary

clause 4.5.4 Risk management plan

clause 4.5.2.3 Resource allocation

clause 4.4.3 Roles and responsibilitiesSG 3 Obtain Commitment to the Plan

7/28/2019 CMMiIEEE


6/19/09 OG v3.0 24

Project Monitoring and Control PMC

Purpose Provide understanding of the project’s

progress so that appropriate corrective

actions can be taken when the project’s

performance deviates significantly from the

plan

7/28/2019 CMMiIEEE


6/19/09 OG v3.0 25


Goals SG 1: Monitor Project Against Plan

Actual performance and progress of the project

are monitored against the project plan

SG 2: Manage Corrective Action to Closure

Corrective actions are managed to closure whenthe project’s performance or results deviate

significantly from the plan

7/28/2019 CMMiIEEE


6/19/09 OG v3.0 26


IEEE Std 1058, IEEE Standard for SoftwareProject Management Plans

It contains clauses regards project monitoring and

control

7/28/2019 CMMiIEEE


6/19/09 OG v3.0 27

Mapping between PMC and IEEE Std 1058-1998

Project Monitoring and Control PMC IEEE Std 1058-1998

IEEE Standard for Software Project

Management Plans

SG 1 Monitor Project Against Plan clause 4.5.3 Control Plan

clause 4.7.2 Verification and

validation plan

SG 2 Manage Corrective Action to

Closure

clause 4.5.5 Project closeout plan

clause 4.7.6 Problem resolution plan

7/28/2019 CMMiIEEE


6/19/09 OG v3.0 28

Supplier Agreement Management SAM

Purpose Manage the acquisition of products from

suppliers

7/28/2019 CMMiIEEE


6/19/09 OG v3.0 29


Goals SG 1: Establish Supplier Agreements

Agreements with the suppliers are established

and maintained

SG 2: Satisfy Supplier Agreements

Agreements with the suppliers are satisfied by both the project and the supplier

7/28/2019 CMMiIEEE


6/19/09 OG v3.0 30


IEEE Std 1062-1998, IEEE Recommended Practice for SoftwareAcquisition

Provides information on the recommended practice for acquiring software: Describes the software acquisition life cycle

Offers support in preparing contract requirements, proposalevaluation, and supplier selection

Provides insight into the management of a software supplier and product acceptance

Offers a series checklists which consist of information designed tohelp organizations establish their own software acquisition process

This standard describes a set of quality practices that can be applied during one or more steps of the software acquisition process

7/28/2019 CMMiIEEE


6/19/09 OG v3.0 31

Mapping between SAM and IEEE Std 1062-1998

Supplier Agreement Management SAM IEEE Std 1062-1998

IEEE Recommended Practice for SoftwareAcquisition

SG 1 Establish Supplier Agreements clause 5.3 Defining the software requirements

clause 5.4 Identify potential suppliers clause 5.3.3 Establish acquirer and supplier

obligations

clause 5.5 Preparing contract requirements

SG 2 Satisfy Supplier Agreements clause 5.7.1 Manage the contract during

execution

clause 5.7.2 Monitor supplier’s progress

clause 5.8 Accepting the software

clause 5.9 Using the software

7/28/2019 CMMiIEEE


6/19/09 OG v3.0 32

Measurement and AnalysisMA

Purpose Develop and sustain a measurement

capability that is used to support

management information needs

7/28/2019 CMMiIEEE


6/19/09 OG v3.0 33


Goals

SG 1: Align Measurement and Analysis Activities

Measurement objectives and activities are aligned with

identified information needs and objectives SG 2: Provide Measurement Results

Measurement results that address identified information

needs and objectives are provided

7/28/2019 CMMiIEEE


6/19/09 OG v3.0 34


IEEE Std 1045, IEEE Standard for SoftwareProductivity Metrics

Provides a framework for measuring and

reporting software productivity. It is meantfor those who want to measure the

productivity of the software process in

support of their software product

7/28/2019 CMMiIEEE


6/19/09 OG v3.0 35

Mapping between MA and IEEEStd 1045-1992(R2003)

Measurement and Analysis MA IEEE Std 1045-1992(R2003)

IEEE Standard for Software

Productivity Metrics

SG 1 Align Measurement and Analysis

Activities

clause 5 Output primitives

clause 6 Input primitives

clause 7.1 Productivity ratios

SG 2 Provide Measurement Results Annex B Characteristics data

collection form

7/28/2019 CMMiIEEE


6/19/09 OG v3.0 36

Process and Product Quality Assurance PPQA

Purpose Provide staff and management with

objective insight into processes and

associated work products

7/28/2019 CMMiIEEE


6/19/09 OG v3.0 37


SG 1: Objectively Evaluate Processes and Work Products

Adherence of the performed process and

associated work products and services toapplicable process descriptions, standards, and procedures is objectively evaluated

SG 2: Provide Objective Insight Noncompliance issues are objectively tracked

and communicated, and resolution is ensured

7/28/2019 CMMiIEEE


6/19/09 OG v3.0 38


IEEE Std 730-2002, IEEE Standard for Software Quality Assurance Plans

This Standard provides uniform a minimum

acceptable requirements for the preparationand content of Software Quality Assurance

Plans

7/28/2019 CMMiIEEE


6/19/09 OG v3.0 39

Mapping between PPQA and IEEE Std 730-2002

Process and Product Quality AssurancePPQA IEEE Std 730-2002IEEE Standard for Software Quality

Assurance Plans

SG 1 Objectively Evaluate Processes

and Work Products

clause 4.4.2.3 Verification and

validation plans

clause 4.6 Software reviews

SG 2 Provide Objective Insight clause 4.8 Problem reporting and

corrective action

clause 4.12 Records collection,

maintenance, and retention

7/28/2019 CMMiIEEE


6/19/09 OG v3.0 40

Configuration Management CM

Purpose Establish and maintain the integrity of work

products using configuration identification,

configuration control, configuration statusaccounting, and configuration audits

7/28/2019 CMMiIEEE


6/19/09 OG v3.0 41


SG 1: Establish Baselines Baselines of identified work products are established

SG 2: Track and Control Changes

Changes to the work products under configurationmanagement are tracked and controlled

SG 3: Establish Integrity

Integrity of baselines is established and maintained

7/28/2019 CMMiIEEE


6/19/09 OG v3.0 42


IEEE Std 828-1998, IEEE Standard for Software Configuration Management Plans

7/28/2019 CMMiIEEE


6/19/09 OG v3.0 43

Mapping between CM and IEEE Std 828-1998

Configuration Management CM IEEE Std 828-1998

IEEE Standard for Software Configuration

Management Plans

SG 1 Establish Baselines clause 4.3.1 Configuration Identification

SG 2 Track and Control Changes clause 4.3.2 Configuration control

SG 3 Establish Integrity clause 4.3.3 Configuration status

accounting

clause 4.3.4 Configuration audits and

reviews

7/28/2019 CMMiIEEE


6/19/09 OG v3.0 44

Conclusions

Do not consider each standard in isolation,rather consider the complete set of those

most directly supporting CMMi level 2

items Use IEEE standards to develop your

baseline process documentation

7/28/2019 CMMiIEEE


6/19/09 OG v3.0 45

Conclusions

IEEE Software standards can be used to

provide the basic beginning framework in

CMMi v1.2 maturity level 2

7/28/2019 CMMiIEEE


6/19/09 OG v3.0 46

Thank You!!!

7/28/2019 CMMiIEEE


6/19/09 www.osgg.net 47

References Mike Konrard Mary Beth Chrissis & Sandy Shrum. CMMI Second Edition

Guidelines for Process Integration and Product Improvement . , AddisonWesley, 2007.

IEEE Std 830 - 1998, IEEE Recommended Practice for Software RequirementsSpecifications, Institute of Electrical and Electronics Engineers

IEEE Std 1058 - 1998, IEEE Standard for Software Project Management Plans, Institute of Electrical and Electronics Engineers

IEEE Std 1490-1998, IEEE Guide Adoption of PMI Standard, A guide to the

Project Management Body of Knowledge, Institute of Electrical and Electronics Engineers

IEEE Std 1062 - 1998, IEEE Recommended Practice for Software Acquisition,Institute of Electrical and Electronics Engineers

IEEE Std 1045 - 2002, IEEE Standard for Software Productivity Metrics,

Institute of Electrical and Electronics Engineers IEEE Std 730 - 2002, IEEE Standard For Software Quality Assurance,

Institute of Electrical and Electronics Engineers

IEEE Std 828 - 1998, IEEE Standard for Software Configuration Management Plans, Institute of Electrical and Electronics Engineers

CMMiIEEE

Documents