TRADITIONAL SOFTWARE DEVELOPMENT PROCESSES - Software Design for Six-Sigma: A Roadmap for Excellence - page 24

4. V-Model
5. V-Model XT
6. Spiral
7. Chaos Model
8. Top Down and Bottom Up
9. Joint Application Development
10. Rapid Application Development
11. Model Driven Engineering
12. Iterative Development Process
13. Agile Software Process
14. Unified Process
15. eXtreme Process (XP)
16. LEAN method (Agile)
17. Wheel and Spoke Model
18. Constructionist Design Methodology
In this topic, we are developing the Design for Six Sigma (DFSS) 5 as a replacement
for the traditional software the development processes discussed here by formulating
for methodologies integration, importing good practices, filling gaps, and avoiding
failure modes and pitfalls that accumulated over the years of experiences.
2.3.1.1 PSP and TSP. The PSP is a defined and measured software develop-
ment process designed to be used by an individual software engineer. The PSP was
developed by Watts Humphrey (Watts, 1997). Its intended use is to guide the plan-
ning and development of software modules or small programs; it also is adaptable to
other personal tasks. Like the SEI CMM, the PSP is based on process improvement
principles. Although the CMM is focused on improving organizational capability,
the focus of the PSP is the individual software engineer. To foster improvement at
the personal level, PSP extends process management and control to the practitioners.
With PSP, engineers develop software using a disciplined, structured approach. They
follow a defined process to plan, measure, track their work, manage product quality,
and apply quantitative feedback to improve their personal work processes, leading
to better estimating and to better planning and tracking. More on PSP and TSP is
presented in Chapter 11.
2.3.1.2 Waterfall Process The Waterfall Model (2008) is a popular version of
the systems development life-cycle model for software engineering. Often considered
the classic approach to the systems development life cycle, the Waterfall Model
describes a development method that is linear and sequential. Waterfall development
has distinct goals for each phase of development. Imagine a waterfall on the cliff of
5 See Chapters 10 and 11.