Summary of Changes in PI Made no substantive changes to specific goals

Changed SP 1.1 to focus on an “integration strategy” rather than an “integration sequence” to reflect the complexity of the activity (This change caused additional revisions to SP 3.2 and informative material throughout the process area.)

Added material to incorporate modern engineering practices, such as quality attributes, product lines, system of systems, architecture-centric practices, allocation of product capabilities to release increments, and technology maturation (This change resulted in further changes to SP 3.1 and informative material throughout the process area.)

Added information on how Product Integration works with Agile methodologies

Added examples and guidance to the informative material

CMMI Version 1.3 Model Upgrade Training November 2010

Terminology

Revised the terminology used from a emphasis on “integration sequence” to an emphasis on “integration strategy”

The product integration strategy describes the approach for receiving,

assembling, and evaluating the product components that comprise the product.

Established a new phrase, “integration strategy, procedures, and criteria” to use for clarity throughout the process area

Specific Practice Changes

₁

Changed the SP 1.1 title and statement to replace “integration sequence” with “integration strategy”

SP 1.1 Establish an DetermineIntegrationStrategy Sequence

Establish and maintain a Determine the product componentintegration

strategy sequence..

Changed the SP 3.1 statement to replace “function” with “behavior” in order to encompass non-functional requirements

SP 3.1 Confirm Readiness of Product Components for Integration

Confirm, prior to assembly, that each product component required to assemble the product has been properly identified, behaves functions according to its description, and that the product component interfaces comply with the interface descriptions.

CMMI Version 1.3 Model Upgrade Training November 2010

Specific Practice Changes

₂

Changed the SP 3.2 statement to replace “integration sequence” with “integration strategy”

SP 3.2 Assemble Product Components

Assemble product components according to the product integration

strategy sequenceandavailable procedures.

Changed the SP 3.4 statement to remove the subjective word “appropriate”

SP 3.4 Package and Deliver the Product or Product Component

Package the assembled product or product component and deliver it to the appropriatecustomer.

Informative Material Changes

₁

Added material to incorporate modern engineering practices, such as quality attributes, product lines, system of systems, architecture-centric practices, allocation of product capabilities to release increments, and technology maturation (This change resulted in changes to informative material throughout the process area.)

Changed “integration sequence” to “integration strategy,” adding guidance throughout the process area informative material where appropriate

CMMI Version 1.3 Model Upgrade Training November 2010

Informative Material Changes

₂

Introductory Notes

• Added information on how Product Integration works with Agile methodologies • Added additional guidance that managing interfaces is not limited to user

interfaces, but also apply to interfaces among components of the product, including internal and external data sources, middleware, and other components that may or may not be within the development organization’s control but on which the product relies

SP1.1 Establish an Integration Strategy

• Removed notes regarding preparation for integration • Added a list of items that an integration strategy addresses

• Notes that the results of developing a product integration strategy are typically documented in a product integration plan

• Added guidance for identifying and selecting from alternative integration strategies

Verification (VER)

CMMI Version 1.3 Model Upgrade Training November 2010

Summary of Changes in VER

Made no substantive changes to specific goals, specific practices, or terminology

Added information on how Verification and Validation work with Agile methodologies

Informative Material Changes

₁

Introductory Notes

• Added guidance for product lines

For product lines, core assets and their associated product line variation mechanisms must also be verified.

• Added “deliberate refactoring” and “pair programming” as additional examples of peer review methods

• Added discussion of verification and validation in Agile environments

SG 1 Prepare for Verification

• Added “architecture evaluations” as an additional method of verification

SP 1.1 Select Work Products for Verification

• Added additional examples of verification methods – software architecture evaluation

– conformance evaluation

– continuous integration (i.e., Agile approach)

CMMI Version 1.3 Model Upgrade Training November 2010

Informative Material Changes

₂

SP 1.3 Establish Verification Procedures and Criteria

• Added new example of sources of verification criteria

embedded customers reviewing work products collaboratively with developers

SP 2.1 Prepare for Peer Reviews

• In subpractice 1, added an additional example of types of peer reviews

architecture implementation conformance evaluation.

SP 2.3 Analyze Peer Review Data

• In subpractice 4, added additional examples of peer review data that can be analyzed

user stories or case studies associated with a defect and the end users and

Validation (VAL)

CMMI Version 1.3 Model Upgrade Training November 2010

Summary of Changes in VAL

Made no substantive changes to specific goals, specific practices, or terminology

Clarified when validation occurs in the product lifecycle

Listed incremental delivery of a working product as an example validation method

Informative Material Changes

Introductory Notes

• Expanded the definition of when validation occurs, including that validation is performed early “(concept/explorations phases)” and incrementally throughout the project lifecycle “(including transition to operations and sustainment)”

SP 1.1 Select Products for Validation

• Added additional examples of products and product components that can be validated

– access protocols

– data interchange reporting formats • Added an example of a validation method

incremental delivery of working and potentially acceptable product

SP 2.2 Analyze Validation Results

• Added a new subpractice 6 to address corrective action (similar to VER) 6. Provide information on how defects can be resolved (including validation

methods, criteria, and validation environment) and initiate corrective action.

CMMI Version 1.3 Model Upgrade Training November 2010

Summary: Specific Goal Changes

SG 3 The requirements are analyzed and validated, and a definition of required functionality is developed.

Summary: Specific Practice Changes

₁

SP 1.2 Transform Stakeholder Needs into Develop the Customer

Requirements

Transform stakeholder needs, expectations, constraints, and interfaces into prioritized customer requirements.

SP 3.2 Establish a Definition of Required Functionalityand Quality Attributes Establish and maintain a definition of required functionalityand quality attributes.

SP 1.2 Select the product component solutions based on selection that best satisfy the criteriaestablished.

CMMI Version 1.3 Model Upgrade Training November 2010

Summary: Specific Practice Changes

₂

SP 1.1 Establish an DetermineIntegrationStrategy Sequence

SP 3.1 Confirm, prior to assembly, that each product component required to assemble the product has been properly identified, behaves functions according to its description, and that the product component interfaces comply with the interface descriptions.

SP 3.2 Assemble product components according to the product integration

strategy sequenceandavailable procedures.

SP 3.4 Package the assembled product or product component and deliver it to the appropriatecustomer.

Software Engineering Institute Carnegie Mellon University Pittsburgh, PA 15213

CMMI

_{Version 1.3 Model}

Upgrade Training

® CMMI and Carnegie Mellon are registered in the US Patent and Trademark Office by Carnegie Mellon University. For more information on CMU/SEI Trademark use, please visit

http://www.sei.cmu.edu/legal/marks/index.cfm

CMMI Version 1.3 Model Upgrade Training November 2010

This material is distributed by the SEI only to course attendees for their own individual study. Except for the U.S. government purposes described below, this material SHALL NOT be reproduced or used in any other manner without requesting formal permission from the Software Engineering Institute [email protected].

This material was created in the performance of Federal Government Contract Number FA8721-05- C-0003 with Carnegie Mellon University for the operation of the Software Engineering Institute, a federally funded research and development center. The U.S. Government's rights to use, modify, reproduce, release, perform, display, or disclose this material are restricted by the Rights in Technical Data-Noncommercial Items clauses (DFAR 252-227.7013 and DFAR 252-227.7013 Alternate I) contained in the above identified contract. Any reproduction of this material or portions thereof marked with this legend must also reproduce the disclaimers contained on this slide. Although the rights granted by contract do not require course attendance to use this material for U.S. Government purposes, the SEI recommends attendance to ensure proper understanding. THE MATERIAL IS PROVIDED ON AN “AS IS” BASIS, AND CARNEGIE MELLON DISCLAIMS ANY AND ALL WARRANTIES, IMPLIED OR OTHERWISE (INCLUDING, BUT NOT LIMITED TO, WARRANTY OF FITNESS FOR A PARTICULAR PURPOSE, RESULTS OBTAINED FROM USE OF THE MATERIAL, MERCHANTABILITY, AND/OR NON-INFRINGEMENT).

Purpose

This module provides a description of the changes for each of the process areas that are unique to CMMI-SVC.

CMMI Version 1.3 Model Upgrade Training November 2010

Topics

Capacity and Availability Management (CAM) Incident Resolution and Prevention (IRP) Service Continuity (SCON)

Service Delivery (SD)

Service System Development (SSD) Service System Transition (SST) Strategic Service Management (STSM)

Capacity and Availability

In document CMMI-Dev V1.3 Training (Page 137-147)