DESIGN FOR SIX SIGMA (DFSS) TEAM AND TEAM SOFTWARE PROCESS (TSP) - Software Design for Six-Sigma: A Roadmap for Excellence - page 245

is evolving as fast or faster. Consequently, software belts can expect their jobs to
become more challenging every year. Software Six Sigma belt skills and abilities
thus must evolve with their jobs. If their processes do not evolve in response to these
challenges, those developmental processes will cease to be useful. As a result, their
processes may not be used (Humphrey, 1997).

10.4 PSP AND TSP DEPLOYMENT EXAMPLE

In this section, PSP and TSP processes will be used for three real-world applications in
the automotive embedded controls industry while working on a hybrid vehicle using
the Spiral Model, which is defined in Section 2.2, mapped to PSP and TSP as shown
in Figure 10.6. The Spiral Model was chosen as a base model over other models
because of its effectiveness for embedded applications with prototype iterations.
To evaluate these processes thoroughly, simple and small (S&S) software with a
size of 1 KLOC, moderately complex and medium (M&M) software with a size of

Risk
Analysis

Rapid
Prototype

Rapid
Prototype

Risk
Analysis

Risk
Analysis

Rapid
Prototype

Task &
Schedule
Planning

Finished
Product

Test
Planning

System
Concept

System
Concept

Fine-Defect
recording
Coding
Standard

Software
Requirements

Postmortem

Requirements
Validation

Design

Design
Validation

Integrate

Design
Review

Detailed
Design

Test

Code

Code
Review

Compile

FIGURE 10.6 Practicing PSP using the Spiral Model.