Engineering Processes-CMMI Version 1.3

CMMI- Dev V1.
3
PRODUCT MANAGEMENT
Author : Đoàn Đức Đề

E-mail: dedoan@gmail.com
Cell phone: (+084)938491888
@Author : Đoàn Đức Đề dedoan@gmail.com

Agenda
2
►Product Development Process Areas

►Requirement Development
►Technical Solution (TS)
►Product Integration (PI)
►Verification (VER)
►Validation (VAL)
►Product Development Summary
►Q&A

Organization of Process Areas
3
Purpose Project
Plans Process Area Sampling of
describes the purpose of the process Work Products – graphic
area showing a sampling of work
products in relation to PA specific
Relevant Terminology practices
definitions of important terms DAR SP 1.6
from the model glossary Select Process Area Sampling of
Solutions
PA Relationships – graphic
When a PA Is Not Done Well… showing a sampling of PA
discussion points for when a relationship to PA specific
PA is not done well practices
SG 1 Process Area Specific Goals Focus PA Case Study Example –

Areas
PA specific goal statements example application of the PA
to the case study
SP 1 Process Area Specific Practices
PA specific practice titles*
* Only PA specific practice titles are presented, not PA specific practice statements which may provide more information.
For example, the specific practice statement for PP SP 1.1, “Establish a top-level work breakdown structure (WBS) to estimate
the scope of the project.” provides more information than the specific practice title, “Estimate the Scope of the Project”.

This Module Focuses On
4
Managing the
PAs Project
REQM
PP, PMC Organizing
Managing
and
RSKM the Work
SAM,IPM
Project and Org PAs Product Product

PAs Support Development
Development
CM TS,PI Doing the Work of the
Providing Doing the Work of
Organization
PPQA Infrastructure for RDOrganization
the * Understanding the
MA Projects and * UnderstandingWork
VER
DAR Organizations VALthe Work
* Performing the Work
Improvement
PAs Infrastructure
OPF
OPD Enabling
Improvement of
IPM the Work
OT

Product Development Involves - 1
5
Establishing and maintaining sets of requirements

 customer requirements
 product requirements
 product component requirements
 managing the requirements as the product evolves

Product Development Involves - 2
6
Designing the product and its components
Managing the interfaces among the components and between

the product and other products
Building the components
Integrating the components to form the product
Ensuring the requirements are satisfied
Ensuring the product will perform as intended
Delivering the product

Topics
7
Product Development Process Areas

Requirement Development
Technical Solution (TS)
Product Integration (PI)
Verification (VER)
Validation (VAL)
Product Development Summary

Requirements Development (RD)
8
Purpose
Elicit, analyze, and establish customer, product, and product
component requirements.

Relevant Terminology - 1
9
Allocated Requirement
Requirement that results from levying all or part of a higher level
requirement on a lower level architectural element or design
component.
Derived Requirements
Requirements that are not explicitly stated in the customer
requirements, but are inferred (1) from contextual requirements (e.g.,
applicable standards, laws, policies, common practices,
management decisions), or (2) from requirements needed to specify
a product or service component.
Derived requirements can also arise during analysis and design of

components of the product or system.

Relevant Terminology - 2
10
Quality Attribute
A property of a product or service by which its quality will be
judged by relevant stakeholders. Quality attributes are
characterizable by some appropriate measure.
Quality attributes are non-functional, such as timeliness,

throughput, responsiveness, security, modifiability, reliability, and
usability. They have a significant influence on the architecture.

When Requirements Development Is Not Done Well…
11
Unstated requirements or poorly stated requirements lead to confusion

among staff and customers.
Design, implementation, and test work products inconsistently interpret the

requirements.
It takes an inordinately long time to get agreement on product design.
There is an increased potential for higher costs to meet customer

expectations.

Requirements Development Goals
12
Develop Customer Requirements

Stakeholder needs, expectations, constraints, and
SG 1 interfaces are collected and translated into customer
requirements.
Develop Product Requirements

SG 2 Customer requirements are refined and elaborated to
develop product and product component requirements.
Analyze and Validate Requirements

SG 3 The requirements are analyzed and validated.
The process area also has generic goals to support institutionalization.

Requirements Development Specific Practices -1
13
Develop Customer Requirements

SP 1.1 Elicit Needs
SG 1 SP 1.2 Transform Stakeholder Needs into
Customer Requirements
Develop Product Requirements

SP 2.1 Establish Product and Product Component
SG 2 Requirements
SP 2.2 Allocate Product Component Requirements
SP 2.3 Identify Interface Requirements

14

SP 3.1 Establish Operational Concepts and
Scenarios
SP 3.2 Establish a Definition of Required
SG 3 Functionality and Quality Attributes
SP 3.3 Analyze Requirements
SP 3.4 Analyze Requirements to Achieve Balance
SP 3.5 Validate Requirements

Requirements Development Specific Practices - 1
15
Requirements Development
Develop Customer Develop Product Analyze and Validate

Requirements Requirements Requirements
• Results of requirements elicitation activities such as

Elicit Needs the list of needs, expectations, constraints, and
interfaces; or survey of market; . . .
Transform Stakeholder • Customer Requirements

needs Into Customer • Customer Constraints on the Conduct of Verification
Requirements • Customer Constraints on the Conduct of Validation
Goals
Practices
Typical Work Products

16

Establish Product and • Derived Requirements

Product-component • Product Requirements
Requirements • Product-Component Requirements
• Requirement Allocation Sheets

• Provisional Requirement Allocations
Allocate Product-component
• Design Constraints
Requirements
• Derived Requirements
• Relationships among derived requirements
Goals
Practices Identify Interface • Interface Requirements

Requirements

17

• Operational Concept
• Product or Product Component Installation,
Establish Operational Operational, Maintenance, and Support Concepts
Concepts and Scenarios • Disposal Concepts
• Use Cases
• Timeline Scenarios
• New Requirements
Establish a Definition of
• Functional Architecture
Required Functionality and
• Activity Diagrams and Use Cases
Quality Attributes
• Object-Oriented Analysis With Services Identified
• Requirements Defects Reports

Goals Analyze Requirements • Proposed Requirements Changes to Resolve Defects
• Key Requirements
Practices • Technical Performance Measures
Analyze Requirements to
• Assessment of Risks Related to Requirements
Achieve Balance
Validate Requirements • Record of Analysis Methods and Results

Requirements Development - Sampling of Work Products
18
SP 1.1 SP 1.2 SP 2.1 SP 3.2 SP 2.3

Transform Establish Establish a
Stakeholder Product and Definition of Identify
Elicit Needs Needs into Product Required Interface
Customer Functionality Requirements
Component and Quality
Requirements Requirements Attributes
Customer Product, Product

Requirements Component, and
Interface Requirements
Stakeholder
Needs
SP 2.2 SP 3.1 SP 3.3 SP 3.4 SP 3.5
Allocate Establish Analyze
Product Operational Analyze Requirements Validate
Component Concepts and Requirements to Achieve Requirements
Requirements Scenarios Balance

Requirements Development - Sampling of PA Relationships
19
SP 1.1 SP 1.2 SP 2.1 TS SP 1.2

Transform Establish Select
Stakeholder Product and Product
Elicit Needs Needs into Product Component
Customer Component Solutions
Requirements Requirements
SP 2.2 SP 2.3 SP 3.1 REQM SP 1.3

Allocate Identify Establish Manage
Product Interface Operational Requirements
Component Requirements Concepts and Changes
Requirements Scenarios
SP 3.2 SP 3.3 SP 3.4 SP 3.5

Establish a
Definition of Analyze
Required Analyze Requirements Validate
Functionality Requirements to Achieve Requirements
and Quality Balance
Attributes

Applying Process Areas in the Multiple Layers of a Product
20
Engineering process areas are written to support recursion

throughout the product architecture.
This means that the specific practices need to be interpreted

according to the needs of the product.
Engineering process areas can be applied to a product that has

several layers of product components.

Process Area Applicability in a Product Hierarchy
21
Process areas can be applied in more than one instance in a

product structure.
Product requirements
exist here.
Product component
requirements exist here.
One person’s product component may be another person’s product.

Requirements Development - Case Study Example Focus Areas
22

SP 3.1 Establish Operational Concepts and
Scenarios
SP 3.2 Establish a Definition of Required
SG 3 Functionality and Quality Attributes
SP 3.3 Analyze Requirements
Focus
Areas SP 3.4 Analyze Requirements to
Achieve Balance
SP 3.5 Validate Requirements

Topics
23

Verification (VER)
Validation (VAL)

24
Purpose
Select, design, and implement solutions to requirements. Solutions,
designs, and implementations encompass products, product
components, and product related lifecycle processes either singly or
in combinations as appropriate.
Design Implementation

Relevant Terminology
25
Product Related Lifecycle Processes

Processes associated with a product or service throughout
one or more phases of its life (e.g., from conception through
disposal), such as manufacturing and support processes.
Sustainment
The processes used to ensure that a product or service
remains operational.

When Technical Solution Is Not Done Well…
26
An ineffective solution is chosen.
Products may not meet technical performance requirements

or user needs.
Increased testing and rework is required to resolve design

issues.
The product may not be able to accommodate technology

upgrades and future growth if the technical solution is not well
conceived.

Technical Solution Goals
27
Select Product Component Solutions

SG 1 Product or product component solutions are
selected from alternative solutions.
Develop the Design

SG 2 Product or product component designs are
developed.
Implement the Product Design

SG 3 Product components, and associated support
documentation, are implemented from their designs.

Technical Solution Specific Practices
28

SP 1.1 Develop Alternative Solutions and
SG 1 Selection Criteria
SP 1.2 Select Product Component Solutions
Develop the Design
SP 2.1 Design the Product or Product Component
SG 2 SP 2.2 Establish a Technical Data Package
SP 2.3 Design Interfaces Using Criteria
SP 2.4 Perform Make, Buy, or Reuse Analyses
Implement the Product Design
SG 3 SP 3.1 Implement the Design
SP 3.2 Develop Product Support Documentation

Technical Solution Specific Practices - 1
29
Technical Solution
Select Product-
Implement the
Component Develop the Design
Product Design
Solutions
• Alternative Solution Screening Criteria

Develop Alternative
• Evaluation Reports of New Technologies
Solutions and Selection
• Alternative Solutions
Criteria
• Selection Criteria for Final Selection
• Evaluation Reports of COTS Products
Select Product-component • Product-Component Selection Decisions and Rationale

Solutions • Documented Relationships Between Requirements and Product Components
• Documented Solutions, Evaluations, and Rationale
Goals
Practices

30
Technical Solution
Select Product-
Implement the
Component Develop the Design
Product Design
Solutions
Design the Product or • Product Architecture

Product Component • Product-Component Designs
Establish a Technical Data • Technical Data Package

Package
• Interface Design Specifications

Goals Design Interfaces Using • Interface Control Documents
Criteria • Interface Specification Criteria
Practices
• Rationale for Selected Interface Design
Perform Make, Buy, or • Criteria for Design and Product-Component Reuse

Reuse Analyses • Make-or-Buy Analyses
• Guidelines for Choosing COTS Product Components

31
Technical Solution
Select Product-
Implement the
Component Develop the Design Product Design
Solutions
Implement the Design • Implemented Design
• End-User Training Materials

Develop Product Support • User’s Manual
Goals Documentation • Operator’s Manual
• Maintenance Manual
Practices • Online Help

Technical Solution Sampling of Work Products
32
SP 1.1 SP 1.2 SP 2.2 SP 2.4

Develop Select Perform
Alternative Product Establish a Make, Buy, or
Solutions and Component Technical Reuse
Selection Solutions Data Package Analyses
Criteria
Implemented
Designs Designs and
Documentation
SP 2.1 SP 2.3 SP 3.1 SP 3.2

Design the Design Develop
Product or Interfaces Implement Product
Product Using Criteria the Design Support
Component Documentation

Technical Solution Sampling of PA Relationships
33
PI SP 3.2 SP 3.1 SP 1.1 SP 2.1 RD SP 2.1

Develop Design the Establish
Assemble Implement Alternative Product or Product and
Product the Design Solutions and Product Product
Components Selection Component Component
Criteria Requirements
DAR SP 1.6 SP 1.2 SP 2.2 SP 2.3 RD SP 2.3

Select Establish a Design Identify
Select Product Technical Interfaces Interface
Solutions Component Data Package Using Criteria Requirements
Solutions
SAM SP 1.2 SP 2.4 SP 3.2

Perform Develop
Select Make, Buy, or Product
Suppliers Reuse Support
Analyses Documentation

Technical Solution Case Study Example Focus Area
34

Focus
Area SP 1.1 Develop Alternative Solutions and
SG 1 Selection Criteria
SP 1.2 Select Product Component Solutions

Design Alternative 1 - 3 Types of Sensors
35
Motion Sirens Display

Sensors
Door 1: Low Battery
Window 2 : No Response
Door
Sensors
Door Motion Sirens Display

Sensors Sensors SW SW
SW SW
Keypad
Window Beeper On/Off Keypad
Sensors Speaker Button SW 1 2 3
Window SW SW SW
Sensors Controller SW 4 5 6
Beeper 7 8 9
Speaker On/Off * 0 #
Button
Off On

Design Alternative 2 - All Sensors in One Component
36
Sirens Display
Door 1: Low Battery
Window 2 : No Response
Sensors
Sensors Sirens Display

SW SW SW
Keypad
Beeper On/Off Keypad
Speaker Button SW 1 2 3
SW SW
Controller SW 4 5 6
Beeper 7 8 9
Speaker On/Off * 0 #
Button
Off On

Topics
37

Verification (VER)
Validation (VAL)

38
Purpose
Assemble the product from the product components,
ensure that the product, as integrated, behaves properly
(i.e., possesses the required functionality and quality
attributes), and deliver the product.
Integrators

When Product Integration Is Not Done Well…
39
Subsystems do not operate together.
There is increased integration test time.
The integration environment is inadequate to support the integration

activities.
A product is released without all the component integration fully

tested.

Product Integration Goals
40
Prepare for Product Integration

SG 1 Preparation for product integration is conducted.
Ensure Interface Compatibility

SG 2 The product component interfaces, both internal
and external, are compatible.
Assemble Product Components and Deliver

the Product
SG 3 Verified product components are assembled and
the integrated, verified, and validated product is
delivered.

Product Integration Specific Practices -1
41
Prepare for Product Integration

SP 1.1 Establish an Integration Strategy
SP 1.2 Establish the Product Integration
SG 1 Environment
SP 1.3 Establish Product Integration Procedures
and Criteria
Ensure Interface Compatibility

SP 2.1 Review Interface Descriptions for
SG 2 Completeness
SP 2.2 Manage Interfaces

Product Integration Specific Practices -2
42

the Product
SP 3.1 Confirm Readiness of Product
Components for Integration
SG 3 SP 3.2 Assemble Product Components
SP 3.3 Evaluate Assembled Product Components
SP 3.4 Package and Deliver the Product or
Product Component

Product Integration Specific Practices - 1
43
Product Integration
Assemble Product
Prepare for Product Ensure Interface
Components and
Integration Compatibility
Deliver the Product
Establish an Integration • Product Integration Strategy

Strategy • Rationale for Selecting or Rejecting Integration Strategy
Establish the Product • Verified Environment for Product Integration

Integration Environment • Support Documentation for the Product Integration Environment
Goals
Establish Product Integration • Product Integration Procedures
Procedures and Criteria • Product Integration Criteria Practices

44
Product Integration
Assemble Product
Components and
Deliver the Product
Review Interface • Categories of Interfaces

Descriptions for • List of Interfaces Per Category
Completeness • Mapping of the Interfaces to the Product Components
and Product Integration Environment
• Table of Relationships Among the Product Components and the

External Environment (e.g., Main Power Supply, Fastening Product,
Goals Manage Interfaces and Computer Bus System)
• Table of Relationships Between the Different Product Components
Practices • List of Agreed-to Interfaces Defined for Each Pair of Product
Components, When Applicable
Typical Work Products • Reports from the Interface Control Working Group Meetings
• Action Items for Updating Interfaces
• Application Program Interface (API)
• Updated Interface Description or Agreement

45
Product Integration
Assemble Product
Components and
Deliver the Product
• Acceptance Documents for the Received Product Components
Confirm Readiness of • Delivery Receipts
Product Components for • Checked Packing Lists
Integration • Exception Reports
• Waivers
Assemble Product
Components • Assembled Product or Product Components
Goals • Exception Reports

Evaluate Assembled Product
Components • Interface Evaluation Reports
Practices • Product Integration Summary Reports
Package and Deliver the
Product or Product • Packaged Product or Product Components
Component • Delivery Documentation

Product Integration Sampling of Work Products
46
SP 1.1 SP 1.2 SP 1.3 SP 2.1 SP 2.2

Establish the Establish Review
Establish an Product Product Interface Manage
Integration Integration Integration Descriptions Interfaces
Strategy Environment Procedures for
and Criteria Completeness
Integration Strategy,
Procedures, Criteria, Assemblies
and Environment
SP 3.1 SP 3.2 SP 3.3 SP 3.4

Confirm Evaluate Package and
Readiness of Assemble Assembled Deliver the
Product Product Product Product or
Components Components Components Product
for Integration Component

Product Integration Sampling of PA Relationships
47
TS SP 2.3 SP 1.1 SP 1.2 SP 1.3 SP 2.1

Establish the Establish Review
Design Establish an Product Product Interface
Interfaces Integration Integration Integration Descriptions
Using Criteria Strategy Environment Procedures for
and Criteria Completeness
VER SP 3.1 SP 2.2 SP 3.1 SP 3.2

Confirm
Perform Manage Readiness of Assemble
Verification Interfaces Product Product
Components Components
for Integration
VAL SP 2.1 SP 3.3 SP 3.4

Evaluate Package and
Perform Assembled Deliver the
Validation Product Product or
Components Product
Component

Product Integration Case Study Example Focus Area
48

the Product
Focus
Area SP 3.1 Confirm Readiness of Product
Components for Integration
SG 3 SP 3.2 Assemble Product Components
SP 3.3 Evaluate Assembled Product Components
SP 3.4 Package and Deliver the Product or
Product Component

Rejected Components from Engineering
49
Integrator confirms that components

are ready for integration
• Rejected door sensor software. No

peer review proof.
• Rejected keypad software. COTS

not under CM control.
• Rejected controller software. No

proof of unit/component test.
• Rejected siren hardware. No proof

of QA assembly inspection.

Topics
50

Verification (VER)
Validation (VAL)

Verification (VER)
51
Purpose
Ensure that selected work products meet their specified
requirements.
Testers

Relevant Terminology
52
 Verification
Confirmation that work products properly reflect the
requirements specified for them.
In other words, verification ensures that “you built it
right.”.
 Validation
Confirmation that the product or service, as provided (or
as it will be provided), will fulfill its intended use.
In other words, validation ensures that “you built the right
thing.”.
Both are applicable throughout the product development

lifecycle.

When Verification Is Not Done Well…
53
There is disagreement among technical staff as to whether the

different components meet the requirements.
The product being tested does not meet design requirements.
Product reliability suffers because defects are not detected or

corrected prior to customer release.
Added rework occurs because defects that could have been caught
early escape into later lifecycle phases.

Verification Goals
54
Prepare for Verification

SG 1 Preparation for verification is conducted.
Perform Peer Reviews

SG 2 Peer reviews are performed on selected work
products.
Verify Selected Work Products

SG 3 Selected work products are verified against their
specified requirements.

Verification Specific Practices
55

SP 1.1 Select Work Products for Verification
SG 1 SP 1.2 Establish the Verification Environment
SP 1.3 Establish Verification Procedures and
Criteria
Perform Peer Reviews
SP 2.1 Prepare for Peer Reviews
SG 2 SP 2.2 Conduct Peer Reviews
SP 2.3 Analyze Peer Review Data
Verify Selected Work Products
SG 3 SP 3.1 Perform Verification
SP 3.2 Analyze Verification Results

Verification Specific Practices - 1
56
Verification
Prepare for Perform Peer Verify Selected Work

Verification Reviews Products
Select Work Products for • List of Work Products Selected for Verification
Verification • Verification Methods for Each Selected Work Product
Establish the Verification

• Verification Environment
Environment
Establish Verification • Verification Procedures Goals

Procedures and Criteria • Verification Criteria
Practices

57
Verification

• Peer Review Schedule

• Peer Review Checklist
Prepare for Peer Reviews • Entry and Exit Criteria for Work Products
• Criteria for Requiring Another Peer Review
• Peer Review Training Material
• Selected Work Products to Be Reviewed
• Peer Review Results

Conduct Peer Reviews • Peer Review Issues
Goals • Peer Review Data
Practices

• Peer Review Data
Analyze Peer Review Data
• Peer Review Action Items

58
Verification

• Verification Results
• Verification Reports
Perform Verification • Demonstrations
• As-run Procedures Log
• Analysis Report (such as statistics on performances,

causal analysis of non-conformances, comparison of the
Goals behavior between the real product and models, and trends)
Analyze Verification Results
• Trouble Reports
Practices • Change Requests for the Verification Methods, Criteria,
and Environment

Verification Sampling of Work Products
59
SP 1.1 SP 1.3 SP 2.1 SP 1.2
Select Work Establish Establish the

Products for Verification Prepare for Verification
Verification Procedures Peer Reviews Environment
and Criteria
Verification Verification
Plans Results
SP 2.2 SP 2.3 SP 3.1 SP 3.2
Conduct Analyze Perform Analyze

Peer Reviews Peer Review Verification Verification
Data Results

Verification Sampling of PA Relationships
60
SP 1.1 SP 1.2 SP 1.3
Select Work Establish the Establish

Products for Verification Verification
Verification Environment Procedures
and Criteria
SP 2.1 SP 2.2 SP 2.3 MA SP 2.2
Prepare for Conduct Analyze Analyze

Peer Reviews Peer Reviews Peer Review Measurement
Data Data
SP 3.1 SP 3.2
Perform Analyze
Verification Verification
Results

Verification Case Study Example Focus Area
61

SP 1.1 Select Work Products for Verification
SG 1 SP 1.2 Establish the Verification Environment
Focus
Area SP 1.3 Establish Verification Procedures and
Criteria

Verification Case Study Example
62
Which of the following are adequate for verification procedures and

criteria?
1. Peer review criteria that says, “Ensure products are complete,

consistent, and correct.”
2. Checklists for peer reviews.
3. A test procedure that lists test steps and how to judge whether each
test step passed or failed
4. A procedure on how to do the verification process.

5. A procedure on how to do peer reviews.

Topics
63

Verification (VER)
Validation (VAL)

Validation (VAL)
64
Purpose
Demonstrate that a product or product component fulfills its
intended use when placed in its intended environment.
Breaking into an Actual Home

When Validation Is Not Done Well…
65
There are arguments among the technical staff as to what the user
really wants.
The released product does not meet user expectations.
Customers do not pay for products that do not meet their needs.
End users refuse to use the product as delivered.

Validation Goals
66
Prepare for Validation

SG 1 Preparation for validation is conducted.
Validate Product or Product Components

The product or product components are validated
SG 2 to ensure they are suitable for use in their intended
operating environment.

Validation Specific Practices
67
Prepare for Validation

SP 1.1 Select Products for Validation
SG 1 SP 1.2 Establish the Validation Environment
SP 1.3 Establish Validation Procedures and
Criteria
Validate Product or Product Components

SG 2 SP 2.1 Perform Validation
SP 2.2 Analyze Validation Results

Validation Specific Practices - 1
68
Validation
Prepare for Validate Product or

Validation Product Components
• Lists of Products and Product Components Selected for Validation

Select Products for • Validation Methods for Each product or Product Component
Validation • Requirements for Performing Validation for Each Product or Product Component
• Validation Constraints for Each Product or Product Component
Establish the Validation

Environment • Validation Environment
Establish Validation • Validation Procedures

Procedures and Criteria • Validation Criteria
• Test and Evaluation Procedures for Maintenance, Training, and Support
Goals
Practices

Validation Specific Practices - 2
69
Validation
Prepare for Validate Product or

Validation Product Components
• Validation Reports
• Validation Results
Perform Validation • Validation Cross-Reference Matrix
• As-run Procedures Log
• Operational Demonstrations
Goals • Validation Deficiency Reports

Analyze Validation Results
• Validation Issues
Practices • Procedure Change Request

Validation Sampling of Work Products
70
SP 1.1 SP 1.3 SP 1.2
Select Establish Establish the

Products for Validation Validation
Validation Procedures Environment
and Criteria
Validation Validation
Plans Results
SP 2.1 SP 2.2
Perform Analyze
Validation Validation
Results

Validation Sampling of PA Relationships
71
SP 1.1 SP 1.2 SP 1.3
Select Establish the Establish

Products for Validation Validation
Validation Environment Procedures
and Criteria
RD SP 3.5 SP 2.1 SP 2.2
Validate Perform Analyze

Requirements Validation Validation
Results

Validation Case Study Example
72
Which are verification vs. validation?

1. PASS conducts a formal design review with SaveAll
2. PASS has a peer review with the systems engineers, software
engineers, and QA
3. PASS demonstrates a prototype to SaveAll to get their
feedback
4. PASS formally tests the product prior to delivery with SaveAll
and QA witnesses the test
5. PASS integrates the components and tests the system

Topics
73

Verification (VER)
Validation (VAL)

74
PAs Product Product

DevelopmentDevelopment
TS, Doing the Work of the
DoingPI,the Work of
Organization
RD,VER
the Organization
* Understanding the Work
*VAL
Understanding
* Performing the Work
the Work
TS: Technical Solution
Focuses on designing and building the solutions.
PI: Product Integration
Addresses integrating the solutions and delivering the products.
VER: Verification
Emphasizes ensuring the solutions satisfy the requirements.
VAL: Validation
Emphasizes ensuring the solutions satisfy the need.
RD: Requirements Development
Emphasizes the establishment of customer,
product, and product component requirements

QUESTIONS AND ANSWERS

Engineering Processes-CMMI Version 1.3

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Engineering Processes-CMMI Version 1.3

Uploaded by

Copyright:

Available Formats

CMMI- Dev V1.

Author : Đoàn Đức Đề

@Author : Đoàn Đức Đề dedoan@gmail.com

►Product Development Process Areas

@Author : Đoàn Đức Đề dedoan@gmail.com

SG 1 Process Area Specific Goals Focus PA Case Study Example –

@Author : Đoàn Đức Đề dedoan@gmail.com

Project and Org PAs Product Product

@Author : Đoàn Đức Đề dedoan@gmail.com

Establishing and maintaining sets of requirements

@Author : Đoàn Đức Đề dedoan@gmail.com

Designing the product and its components

Managing the interfaces among the components and between

Building the components

Integrating the components to form the product

Ensuring the requirements are satisfied

Ensuring the product will perform as intended

Delivering the product

@Author : Đoàn Đức Đề dedoan@gmail.com

Product Development Process Areas

@Author : Đoàn Đức Đề dedoan@gmail.com

@Author : Đoàn Đức Đề dedoan@gmail.com

Derived requirements can also arise during analysis and design of

@Author : Đoàn Đức Đề dedoan@gmail.com

Quality attributes are non-functional, such as timeliness,

@Author : Đoàn Đức Đề dedoan@gmail.com

Unstated requirements or poorly stated requirements lead to confusion

Design, implementation, and test work products inconsistently interpret the

It takes an inordinately long time to get agreement on product design.

There is an increased potential for higher costs to meet customer

@Author : Đoàn Đức Đề dedoan@gmail.com

Develop Customer Requirements

Develop Product Requirements

Analyze and Validate Requirements

The process area also has generic goals to support institutionalization.

@Author : Đoàn Đức Đề dedoan@gmail.com

Develop Customer Requirements

Develop Product Requirements

@Author : Đoàn Đức Đề dedoan@gmail.com

Analyze and Validate Requirements

@Author : Đoàn Đức Đề dedoan@gmail.com

Develop Customer Develop Product Analyze and Validate

• Results of requirements elicitation activities such as

Transform Stakeholder • Customer Requirements

@Author : Đoàn Đức Đề dedoan@gmail.com

Develop Customer Develop Product Analyze and Validate

Establish Product and • Derived Requirements

• Requirement Allocation Sheets

Practices Identify Interface • Interface Requirements

@Author : Đoàn Đức Đề dedoan@gmail.com

Develop Customer Develop Product Analyze and Validate

• Requirements Defects Reports

Validate Requirements • Record of Analysis Methods and Results

@Author : Đoàn Đức Đề dedoan@gmail.com

SP 1.1 SP 1.2 SP 2.1 SP 3.2 SP 2.3

Customer Product, Product

@Author : Đoàn Đức Đề dedoan@gmail.com

SP 1.1 SP 1.2 SP 2.1 TS SP 1.2

SP 2.2 SP 2.3 SP 3.1 REQM SP 1.3

SP 3.2 SP 3.3 SP 3.4 SP 3.5

@Author : Đoàn Đức Đề dedoan@gmail.com

Engineering process areas are written to support recursion

This means that the specific practices need to be interpreted

Engineering process areas can be applied to a product that has