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

10 KLOCs, and finally complex and large (C&L) software with a size of 90 KLOCs
were chosen.
Here an S&S application was started after an M&M application, and fault tree
analysis 1 (FTA) was conducted during the execution of the applications. FTA is a
logical, structured process that can help identify potential causes of system failure
before the failures actually occur. FTAs are powerful design tools that can help ensure
that product performance objectives are met. FTA has many benefits such as identify
possible system reliability or safety problems at design time, assess system reliability
or safety during operation, improve understanding of the system, identify components
that may need testing or more rigorous quality assurance scrutiny, and identify root
causes of equipment failures (Humphrey, 1995). It was required for these applications
to understand various human factors to have engineers with different educations
backgrounds, years of experience, and level of exposure to these systems and to have
personal quality standards. However, in this case, to simplify error calculations, all
of these engineers were considered to be at the same level. An accurate log was
maintained during the execution of the various application trials as well as available
scripts in a UNIX environment to calculate the compilation, parse and build time,
error count, and so on. There was one more factor where server compilation speed
was changing day-to-day depending on the number of users trying to compile their
software on a given day and time. For these reasons, time was averaged out for a day
to reduce time calculation discrepancies. The errors also were logged systematically
and flushed per the software build requirements.

10.4.1 Simple and Small-Size Project

Figure 10.6 shows a working software model using both PSP and Spiral Model
software processes (Shaout and Chhaya, 2008, 2009; Chhaya, 2008). The model will
be applied to an engine control subsystem with approximately 10 input and output
interfaces and a relatively easy algorithm with approximately 1 KLOC.

10.4.1.1 DeploymentExample:Start-StopModuleforaHybridEngine
ControlsSubsystem. DFSS Identify Phase— While working on various modules
within engine controls, a start-stop module with approximately 1 KLOC was chosen.
This involved gathering software interface and control requirements from internal
departments of the organization. The time line was determined to be two persons
for approximately four weeks of time. The following were the software variable
requirements:

Hybrid Selection Calibration
Hybrid Mode
Engine Start Not Inhibit
Over Current Fault Not Active

1 See Chapter 15.