INTRODUCTION TO SOFTWARE DESIGN FOR SIX SIGMA (DFSS) - Software Design for Six-Sigma: A Roadmap for Excellence - page 182

In practicality the divide between a formal DFSS project and a “simple” Six
Sigma project can be indistinct—at times there is a need for a Six Sigma project to
improve radically the capability (rather than, or as well as, performance) of a broken
or nonexistent process using design or redesign.
DFSS brings about a huge change of roles in an organization. The DFSS team is
cross-functional, as the key factor is covering all aspects for the product from market
research to process launch. DFSS provides tools to get the improvement process
done efficiently and effectively. It proves to be powerful management technique for
projects. It optimizes the design process so as to achieve the level of Six Sigma for
the product being designed.
The DFSS methodology should be used when a product or process is not in
existence at your company and one needs to be developed or when the product or
process exists and has been optimized and reached their entitlement (using either
DMAIC, for example) and still does not meet the level of customer specification or
Six Sigma level.
It is very important to have practical experience of Six Sigma, as DFSS builds
on the concepts and tools from a typical DMAIC approach. Becuase DFSS works
with products and services rather than with processes and because design and cre-
ativity are important, a few new tools are common to any DFSS methodology. Strong
emphasis is placed on customer analysis, an the transition of customer needs and re-
quirements down to process requirements, and on error and failure proofing. Because
the product/service often is very new, modeling and simulation tools are important,
particularly for measuring and evaluating in advance the anticipated performance of
the new process.
If DFSS is to work successfully, it is important that it covers the full life cycle
of any new software product. This begins when the organization formally agrees
with the requirement for something new, and ends when the new software is in full
commercial delivery.
The DFSS tools are used along the entire life cycle of product. Many tools are used
in each phase. Phases like (DOE), which are used to collect data, assess impact, predict
performance, design for robustness, and validate performance. Table 8.1 classifies
DFSS tools used by design activity. In the next section, we will discuss the DFSS
tool usage by ICOV phase.

8.7 A REVIEW OF SAMPLE DFSS TOOLS BY ICOV PHASE

The origin of DFSS seems to have its beginnings with NASA and the U.S. Department
of Defense. In the late 1990s, early 2000s, GE Medical systems was among the
forerunners in using DFSS for new product development with its use in the design of
the light speed computed tomography (CT) system.
DFSS provides a systematic integration of tools, methods, processes and team
members throughout product and process design. Initiatives vary dramatically from
company to company but typically start with a charter (linked to the organization's
strategic plan), an assessment of customer needs, functional analysis, identification