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

TABLE 2.3 ( Continued )

Software
Process Simple and Small Moderate and Medium Complex and Large

Joint
Application
Development
(JAD)

In comparison with the more
traditional practice, it is
thought to lead to faster
development times and
greater client satisfaction,
because the client is
involved throughout the
development process.

Rapid
Application
Development
(RAD)

A variation on JAD, Rapid
Application Development
(RAD) creates an
application more quickly
through such strategies as
using fewer formal
methodologies and
reusing software
components.

Six Sigma 9 1. Six Sigma DMAIC was mostly concerned with

problem solving to enhance processes by
reducing defects and variation that would cause
customer dissatisfaction for existing products.
2. Six Sigma DFSS was created to address low
yields in high-volume electronics manufacturing,
which required near perfect levels of quality. The
process starts with and is guided by conformance
to customer needs and product specifications. Six
Sigma provides infrastructure, including Green
Belts, Black Belts and Master Black Belts, to
enable team-based problem solving to work
outside the normal work processes and minimize
disruptions to normal operations (except when
warranted).

Model-Driven
Engineering
(MDE)

1. It focuses on creating models that capture the
essential features of a design.
2. A modeling paradigm for MDE is considered
effective if its models make sense from the
point of view of the user and can serve as a
basis for implementing systems.
3. The models are developed through extensive
communication among product managers,
designers, and members of the development
team.

9 See Chapter 7.