Engineering Processes-CMMI

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

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

3
Process Area Sampling of
Work Products – graphic
showing a sampling of work
products in relation to PA specific
practices
Process Area Sampling of
PA Relationships – graphic
showing a sampling of PA
relationship to PA specific
practices
PA Case Study Example –
example application of the PA
to the case study
Organization of Process Areas
SG 1
SP 1
Select
Solutions
DAR SP 1.6
Focus
Areas
Purpose
describes the purpose of the process
area
Relevant Terminology
definitions of important terms
from the model glossary
When a PA Is Not Done Well…
discussion points for when a
PA is not done well
Process Area Specific Goals
PA specific goal statements
Process Area Specific Practices
PA specific practice titles*
Project
Plans
* 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”.

4
This Module Focuses On
PAs
OPF
OPD
IPM
OT
Enabling
Improvement of
the Work
Improvement
Infrastructure
PAs
CM
PPQA
MA
DAR
Providing
Infrastructure for
Projects and
Organizations
Project and Org
Support
PAs
REQM
PP, PMC
RSKM
SAM,IPM
Organizing and
Managing
the Work
Managing the
Project
Doing the Work of
the Organization
* Understanding
the Work
Product
Development
Doing the Work of the
Organization
* Understanding the
Work
* Performing the Work
Product
Development
PAs
TS,PI
RD
VER
VAL

5
Establishing and maintaining sets of requirements
 customer requirements
 product requirements
 product component requirements
 managing the requirements as the product evolves
Product Development Involves - 1

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
Product Development Involves - 2

7
Product Development Process Areas
Requirement Development
Technical Solution (TS)
Product Integration (PI)
Verification (VER)
Validation (VAL)
Product Development Summary
Topics

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

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 - 1

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.
Relevant Terminology - 2

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.
When Requirements Development Is Not Done Well…

12
Requirements Development Goals
Customer requirements are refined and elaborated to
develop product and product component requirements.
Develop Customer Requirements
Stakeholder needs, expectations, constraints, and
interfaces are collected and translated into customer
requirements.
SG 1
Develop Product Requirements
SG 2
The process area also has generic goals to support institutionalization.
The requirements are analyzed and validated.
Analyze and Validate Requirements
SG 3

13
Requirements Development Specific Practices -1
Develop Customer Requirements
SP 1.1 Elicit Needs
SP 1.2 Transform Stakeholder Needs into
Customer Requirements
SG 1
Develop Product Requirements
SP 2.1 Establish Product and Product Component
Requirements
SP 2.2 Allocate Product Component Requirements
SP 2.3 Identify Interface Requirements
SG 2

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

15
Develop Customer
Requirements
Requirements Development
Develop Product
Requirements
Analyze and Validate
Requirements
Elicit Needs
Transform Stakeholder
needs Into Customer
Requirements
• Customer Requirements
• Customer Constraints on the Conduct of Verification
• Customer Constraints on the Conduct of Validation
Goals
Practices
Typical Work Products
• Results of requirements elicitation activities such as
the list of needs, expectations, constraints, and
interfaces; or survey of market; . . .
Requirements Development Specific Practices - 1

16
Develop Customer
Requirements
Develop Product
Requirements
Requirements
Establish Product and
Product-component
Requirements
Allocate Product-component
Requirements
Identify Interface
Requirements
Goals
Practices
• Derived Requirements
• Product Requirements
• Product-Component Requirements
• Requirement Allocation Sheets
• Provisional Requirement Allocations
• Design Constraints
• Derived Requirements
• Relationships among derived requirements
• Interface Requirements

17
Develop Customer
Requirements
Develop Product
Requirements
Requirements
Establish Operational
Concepts and Scenarios
Establish a Definition of
Required Functionality and
Quality Attributes
Analyze Requirements
Analyze Requirements to
Achieve Balance
Validate Requirements
• Operational Concept
• Product or Product Component Installation,
Operational, Maintenance, and Support Concepts
• Disposal Concepts
• Use Cases
• Timeline Scenarios
• New Requirements
• Functional Architecture
• Activity Diagrams and Use Cases
• Object-Oriented Analysis With Services Identified
• Requirements Defects Reports
• Proposed Requirements Changes to Resolve Defects
• Key Requirements
• Technical Performance Measures
• Assessment of Risks Related to Requirements
• Record of Analysis Methods and Results
Goals
Practices

18
Customer
Requirements
Product, Product
Component, and
Interface Requirements
Establish
Product and
Product
Component
Requirements
SP 2.1
Transform
Stakeholder
Needs into
Customer
Requirements
SP 1.2
Elicit Needs
SP 1.1
Identify
Interface
Requirements
SP 2.3
Allocate
Product
Component
Requirements
SP 2.2
Analyze
Requirements
SP 3.3
Establish
Operational
Concepts and
Scenarios
SP 3.1
Validate
Requirements
SP 3.5
Analyze
Requirements
to Achieve
Balance
SP 3.4
Stakeholder
Needs
Establish a
Definition of
Required
Functionality
and Quality
Attributes
SP 3.2
Requirements Development - Sampling of Work Products

19
Establish
Operational
Concepts and
Scenarios
SP 3.1
Identify
Interface
Requirements
SP 2.3
Establish
Product and
Product
Component
Requirements
SP 2.1
Transform
Stakeholder
Needs into
Customer
Requirements
SP 1.2
Elicit Needs
SP 1.1
Validate
Requirements
SP 3.5
Analyze
Requirements
to Achieve
Balance
SP 3.4
Analyze
Requirements
SP 3.3
Select
Product
Component
Solutions
TS SP 1.2
Establish a
Definition of
Required
Functionality
and Quality
Attributes
SP 3.2
Manage
Requirements
Changes
REQM SP 1.3
Requirements Development - Sampling of PA Relationships
Allocate
Product
Component
Requirements
SP 2.2

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.
Applying Process Areas in the Multiple Layers of a Product

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.
Process Area Applicability in a Product Hierarchy

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

23
Verification (VER)
Validation (VAL)
Topics

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

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.

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.
When Technical Solution Is Not Done Well…

27
Technical Solution Goals
Product or product component designs are
developed.
Select Product Component Solutions
Product or product component solutions are
selected from alternative solutions.
SG 1
Develop the Design
SG 2
Product components, and associated support
documentation, are implemented from their designs.
Implement the Product Design
SG 3

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

29
Select Product-
Component
Solutions
Technical Solution
Develop the Design
Implement the
Product Design
Select Product-component
Solutions
Develop Alternative
Solutions and Selection
Criteria
• Alternative Solution Screening Criteria
• Evaluation Reports of New Technologies
• Alternative Solutions
• Selection Criteria for Final Selection
• Evaluation Reports of COTS Products
• Product-Component Selection Decisions and Rationale
• Documented Relationships Between Requirements and Product Components
• Documented Solutions, Evaluations, and Rationale
Goals
Practices
Technical Solution Specific Practices - 1

30
Select Product-
Component
Solutions
Technical Solution
Develop the Design
Implement the
Product Design
Design the Product or
Product Component
Perform Make, Buy, or
Reuse Analyses
Design Interfaces Using
Criteria
Establish a Technical Data
Package
• Product Architecture
• Product-Component Designs
• Technical Data Package
• Interface Design Specifications
• Interface Control Documents
• Interface Specification Criteria
• Rationale for Selected Interface Design
• Criteria for Design and Product-Component Reuse
• Make-or-Buy Analyses
• Guidelines for Choosing COTS Product Components
Goals
Practices

31
Select Product-
Component
Solutions
Develop the Design
Implement the
Product Design
Implement the Design
Develop Product Support
Documentation
Goals
Practices
• Implemented Design
• End-User Training Materials
• User’s Manual
• Operator’s Manual
• Maintenance Manual
• Online Help
Technical Solution

32
Designs
Implemented
Designs and
Documentation
Design the
Product or
Product
Component
SP 2.1
Select
Product
Component
Solutions
SP 1.2
Develop
Alternative
Solutions and
Selection
Criteria
SP 1.1
Establish a
Technical
Data Package
SP 2.2
Implement
the Design
SP 3.1
Perform
Make, Buy, or
Reuse
Analyses
SP 2.4
Design
Interfaces
Using Criteria
SP 2.3
Develop
Product
Support
Documentation
SP 3.2
Technical Solution Sampling of Work Products

33
Design
Interfaces
Using Criteria
SP 2.3
Establish a
Technical
Data Package
SP 2.2
Design the
Product or
Product
Component
SP 2.1
Select
Product
Component
Solutions
SP 1.2
Develop
Alternative
Solutions and
Selection
Criteria
SP 1.1
Develop
Product
Support
Documentation
SP 3.2
Implement
the Design
SP 3.1
Perform
Make, Buy, or
Reuse
Analyses
SP 2.4
Select
Solutions
DAR SP 1.6
Establish
Product and
Product
Component
Requirements
RD SP 2.1
Select
Suppliers
SAM SP 1.2
Identify
Interface
Requirements
RD SP 2.3
Assemble
Product
Components
PI SP 3.2
Technical Solution Sampling of PA Relationships

34
Technical Solution Case Study Example Focus Area
SP 1.1 Develop Alternative Solutions and
Selection Criteria
SP 1.2 Select Product Component Solutions
SG 1
Focus
Area

35
Beeper
Speaker
SW
Window
Sensors
SW
Controller SW
On/Off
Button
SW
Keypad
SW
Door
Sensors
SW
Motion
Sensors
SW
Sirens
SW
Display
SW
1 2 3
5 6
7 8 9
0
* #
4
Keypad
Door
Sensors
Window
Sensors
On
Off
Beeper
Speaker On/Off
Button
Door 1: Low Battery
Window 2 : No Response
Display
Design Alternative 1 - 3 Types of Sensors
Sirens
Motion
Sensors

36
Beeper
Speaker
SW
Controller SW
On/Off
Button
SW
Keypad
SW
Sirens
SW
Display
SW
1 2 3
5 6
7 8 9
0
* #
4
Keypad
On
Off
Beeper
Speaker On/Off
Button
Door 1: Low Battery
Window 2 : No Response
Display
Design Alternative 2 - All Sensors in One Component
Sirens
Sensors
SW
Sensors

37
Verification (VER)
Validation (VAL)
Topics

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

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.
When Product Integration Is Not Done Well…

40
Product Integration Goals
The product component interfaces, both internal
and external, are compatible.
Prepare for Product Integration
Preparation for product integration is conducted.
SG 1
Ensure Interface Compatibility
SG 2
Verified product components are assembled and
the integrated, verified, and validated product is
delivered.
Assemble Product Components and Deliver
the Product
SG 3

41
Product Integration Specific Practices -1
Prepare for Product Integration
SP 1.1 Establish an Integration Strategy
SP 1.2 Establish the Product Integration
Environment
SP 1.3 Establish Product Integration Procedures
and Criteria
SG 1
Ensure Interface Compatibility
SP 2.1 Review Interface Descriptions for
Completeness
SP 2.2 Manage Interfaces
SG 2

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

43
Prepare for Product
Integration
Product Integration
Establish an Integration
Strategy
Ensure Interface
Compatibility
Assemble Product
Components and
Deliver the Product
Establish Product Integration
Procedures and Criteria
Establish the Product
Integration Environment
Goals
Practices
• Product Integration Strategy
• Rationale for Selecting or Rejecting Integration Strategy
• Verified Environment for Product Integration
• Support Documentation for the Product Integration Environment
• Product Integration Procedures
• Product Integration Criteria
Product Integration Specific Practices - 1

44
Prepare for Product
Integration
Product Integration
Ensure Interface
Compatibility
Assemble Product
Components and
Deliver the Product
Review Interface
Descriptions for
Completeness
Manage Interfaces
Goals
Practices
• Categories of Interfaces
• List of Interfaces Per Category
• 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,
and Computer Bus System)
• Table of Relationships Between the Different Product Components
• List of Agreed-to Interfaces Defined for Each Pair of Product
Components, When Applicable
• Reports from the Interface Control Working Group Meetings
• Action Items for Updating Interfaces
• Application Program Interface (API)
• Updated Interface Description or Agreement

45
Prepare for Product
Integration
Ensure Interface
Compatibility
Assemble Product
Components and
Deliver the Product
Confirm Readiness of
Product Components for
Integration
Package and Deliver the
Product or Product
Component
Evaluate Assembled Product
Components
Assemble Product
Components
Goals
Practices
• Acceptance Documents for the Received Product Components
• Delivery Receipts
• Checked Packing Lists
• Exception Reports
• Waivers
• Assembled Product or Product Components
• Exception Reports
• Interface Evaluation Reports
• Product Integration Summary Reports
• Packaged Product or Product Components
• Delivery Documentation
Product Integration

46
Integration Strategy,
Procedures, Criteria,
and Environment
Assemblies
Establish the
Product
Integration
Environment
SP 1.2
Establish an
Integration
Strategy
SP 1.1
Review
Interface
Descriptions
for
Completeness
SP 2.1
Establish
Product
Integration
Procedures
and Criteria
SP 1.3
Assemble
Product
Components
SP 3.2
Confirm
Readiness of
Product
Components
for Integration
SP 3.1
Manage
Interfaces
SP 2.2
Package and
Deliver the
Product or
Product
Component
SP 3.4
Evaluate
Assembled
Product
Components
SP 3.3
Product Integration Sampling of Work Products

47
Confirm
Readiness of
Product
Components
for Integration
SP 3.1
Manage
Interfaces
SP 2.2
Review
Interface
Descriptions
for
Completeness
SP 2.1
Establish
Product
Integration
Procedures
and Criteria
SP 1.3
Establish an
Integration
Strategy
SP 1.1
Establish the
Product
Integration
Environment
SP 1.2
Package and
Deliver the
Product or
Product
Component
SP 3.4
Evaluate
Assembled
Product
Components
SP 3.3
Assemble
Product
Components
SP 3.2
Perform
Verification
VER SP 3.1
Design
Interfaces
Using Criteria
TS SP 2.3
Perform
Validation
VAL SP 2.1
Product Integration Sampling of PA Relationships

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

49
• 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.
Rejected Components from Engineering
Integrator confirms that components
are ready for integration

50
Verification (VER)
Validation (VAL)
Topics

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

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.

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.
When Verification Is Not Done Well…

54
Verification Goals
Peer reviews are performed on selected work
products.
Prepare for Verification
Preparation for verification is conducted.
SG 1
Perform Peer Reviews
SG 2
Selected work products are verified against their
specified requirements.
Verify Selected Work Products
SG 3

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

56
Prepare for
Verification
Verification
Select Work Products for
Verification
Perform Peer
Reviews
Verify Selected Work
Products
Establish Verification
Establish the Verification
Environment
Goals
Practices
• List of Work Products Selected for Verification
• Verification Methods for Each Selected Work Product
• Verification Environment
• Verification Procedures
• Verification Criteria
Verification Specific Practices - 1

57
Prepare for
Verification
Verification
Perform Peer
Reviews
Products
Prepare for Peer Reviews
Analyze Peer Review Data
Conduct Peer Reviews
Goals
Practices
• Peer Review Schedule
• Peer Review Checklist
• 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
• Peer Review Issues
• Peer Review Data
• Peer Review Data
• Peer Review Action Items

58
Prepare for
Verification
Verification
Perform Peer
Reviews
Products
Perform Verification
Analyze Verification Results
Goals
Practices
• Verification Results
• Verification Reports
• Demonstrations
• As-run Procedures Log
• Analysis Report (such as statistics on performances,
causal analysis of non-conformances, comparison of the
behavior between the real product and models, and trends)
• Trouble Reports
• Change Requests for the Verification Methods, Criteria,
and Environment

59
Verification
Plans
Verification
Results
Establish
Verification
Procedures
and Criteria
SP 1.3
Establish the
Verification
Environment
SP 1.2
Select Work
Products for
Verification
SP 1.1
Analyze
Verification
Results
SP 3.2
Analyze
Peer Review
Data
SP 2.3
Conduct
Peer Reviews
SP 2.2
Prepare for
Peer Reviews
SP 2.1
Perform
Verification
SP 3.1
Verification Sampling of Work Products

60
Conduct
Peer Reviews
SP 2.2
Prepare for
Peer Reviews
SP 2.1
Establish
Verification
Procedures
and Criteria
SP 1.3
Establish the
Verification
Environment
SP 1.2
Select Work
Products for
Verification
SP 1.1
Analyze
Peer Review
Data
SP 2.3
Analyze
Verification
Results
SP 3.2
Perform
Verification
SP 3.1
Analyze
Measurement
Data
MA SP 2.2
Verification Sampling of PA Relationships

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

62
Verification Case Study Example
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.

63
Verification (VER)
Validation (VAL)
Topics

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

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.
When Validation Is Not Done Well…

66
Validation Goals
The product or product components are validated
to ensure they are suitable for use in their intended
operating environment.
Prepare for Validation
Preparation for validation is conducted.
SG 1
Validate Product or Product Components
SG 2

67
Validation Specific Practices
Prepare for Validation
SP 1.1 Select Products for Validation
SP 1.2 Establish the Validation Environment
SP 1.3 Establish Validation Procedures and
Criteria
SG 1
Validate Product or Product Components
SP 2.1 Perform Validation
SP 2.2 Analyze Validation Results
SG 2

68
Prepare for
Validation
Validation
Select Products for
Validation
Validate Product or
Product Components
Establish Validation
Establish the Validation
Environment
Goals
Practices
• Lists of Products and Product Components Selected for Validation
• Validation Methods for Each product or Product Component
• Requirements for Performing Validation for Each Product or Product Component
• Validation Constraints for Each Product or Product Component
• Validation Environment
• Validation Procedures
• Validation Criteria
• Test and Evaluation Procedures for Maintenance, Training, and Support
Validation Specific Practices - 1

69
Prepare for
Validation
Validation
Validate Product or
Product Components
Perform Validation
Analyze Validation Results
Goals
Practices
• Validation Reports
• Validation Results
• Validation Cross-Reference Matrix
• As-run Procedures Log
• Operational Demonstrations
• Validation Deficiency Reports
• Validation Issues
• Procedure Change Request
Validation Specific Practices - 2

70
Validation
Plans
Validation
Results
Establish the
Validation
Environment
SP 1.2
Select
Products for
Validation
SP 1.1
Establish
Validation
Procedures
and Criteria
SP 1.3
Analyze
Validation
Results
SP 2.2
Perform
Validation
SP 2.1
Validation Sampling of Work Products

71
Establish
Validation
Procedures
and Criteria
SP 1.3
Analyze
Validation
Results
SP 2.2
Perform
Validation
SP 2.1
Establish the
Validation
Environment
SP 1.2
Select
Products for
Validation
SP 1.1
Validate
Requirements
RD SP 3.5
Validation Sampling of PA Relationships

72
Validation Case Study Example
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

73
Verification (VER)
Validation (VAL)
Topics

74
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
Doing the Work of
the Organization
* Understanding
the Work
Product
Development
Doing the Work of the
Organization
* Understanding the Work
* Performing the Work
Product
Development
PAs
TS, PI,
RD,VER
VAL

QUESTIONS AND ANSWERS

Engineering Processes-CMMI

Recommandé

Recommandé

Contenu connexe

Similaire à Engineering Processes-CMMI

Similaire à Engineering Processes-CMMI (20)

Dernier

Dernier (20)

Engineering Processes-CMMI