AXIOMATIC DESIGN IN SOFTWARE DESIGN FOR SIX SIGMA (DFSS) - Software Design for Six-Sigma: A Roadmap for Excellence - page 340

One of the final outputs of ADo-oSS is the system architecture, which is rep-
resented by the flow diagram. The flow diagram can be used in many different
applications for a variety of different purposes such as:
Improvement of the proposed design through identification of coupled designs.
Diagnosis of the impending failure of a complex system.
Reduction of the service cost of maintaining machines and systems.
Engineering change orders.
Job assignment and management of design tasks.
Management of distributed and collaborative design tasks.
Reusability and extensionality of software.

In axiomatic design, a “module” is defined as the row of design matrix that
yields the FR of the row when it is multiplied by the corresponding DP (i.e., data).
The axiomatic design framework ensures that the modules are correctly defined and
located in the right place in the right order. A “V” model for software, shown in
Figure 13.5 (El-Haik, 1999), will be used here to explain the concept of ADo-oSS.
The first step is to design the software following the top-down approach of axiomatic
design, build the software hierarchy, and then generate the full-design matrix (i.e.,
the design matrix that shows the entire design hierarchy) to define modules.
The final step is to build the object-oriented model with a bottom-up approach,
following the axiomatic design flow diagram for the designed system. Axiomatic
design of software can be implemented using any software language. However, in
the 1990s most software is written using an object-oriented programming language
such as C or Java. Therefore, axiomatic design of software is implemented using

object-oriented methodology.
To understand ADo-oSS, it is necessary to review the definitions of the words used
in OOT and their equivalent words in axiomatic design. The fundamental construct
for the object-oriented method is object 2, which is equivalent to FRs. An object-
oriented design decomposes a system into objects. Objects “encapsulate” both data

++

Customer
needs

Software
product

Coding with system
architecture
Establish
interfaces
Identify
classes

Define FRs

Map to DPs

Decompos

Define
modules

Identify leaves
(full-design matrix)

FIGURE 13.5 Axiomatic design process for object-oriented software system (the V model).