Decomposition of The Design Process: A. Kusiak
Decomposition of The Design Process: A. Kusiak
Decomposition of The Design Process: A. Kusiak
Process
A. Kusiak
J. Wang
Intelligent Systems Laboratory,
Department of Industrial Engineering,
The University of Iowa,
Iowa City, IA 52242
Introduction
Design may require the coordination of many design and
analysis procedures. Due to the decreasing life cycle of products, it is important to reduce the time and cost of product
development. It has been identified that 70-80 percent of the
final production cost is determined during the design stage
[20]. In recent years, the concept of concurrent design has
emerged. It attempts to incorporate various constraints related
to the product life cycle, i.e., manufacturability, quality, and
reliability, in the early design stages. Concurrent design aims
at improvement of product quality, reducing the development
time and cost. However, due to the interaction between various
tasks, the complexity of the design process increases and makes
the process difficult to manage. Decomposition might be a
tool for simplifying the design process.
Decomposition has long been recognized as a powerful tool
for analysis of large and complex systems [4]. The advantage
of decomposition is that it reduces the complexity of the design
problem. Consider a problem with 120 variables that decomposes into 6 independent subproblems each with 20 variables.
Assume that each subproblem is solved in 20 seconds and the
computational time of solving the problem is proportional to
the number of variables. The computational time of solving
the main problem is the 6 x 20 = 120 seconds. In fact, for
most problems, the solution time increases at a higher rate,
e.g., exponentially, as a function of the size of a problem. This
makes the computational time more sensitive to the increase
in the number of variables.
Contributed by the Design Theory and Methodology Committee for publication in the JOURNAL OF MECHANICAL DESIGN. Manuscript received August
1991; revised August 1992. Associate Technical Editor: E. K. Antonsson.
Most research advocates the use of decomposition that allows to exhibit a high degree of cohesion within modules, and
low coupling between modules. The literature concerning research of decomposition in design is not very extensive. Brown
and Chandrasekaran [2, 3] presented a "design refinement"
approach that views design as a hierarchical system. The problem is solved by a top-down approach and refining the design
at each level of the hierarchy. Zarefar et al. [23] developed a
program for the design of a drive system with parallel axis
gears that is divided into a gear design module, axis design
module, and lubricant selection module. The three modules
are controlled by a system coordinator. Verrilli et al. [18]
presented a computer program for hierarchical distributed
problem solving. Hoeltzel and Chieng [5] proposed the distributed system architecture and planning control for concurrent engineering design environment. Johnson and Benson [6]
developed a two-stage decomposition strategy for design optimization. The strategy assumes that all the subproblems are
independent of each other. Azarm [1] applied decomposition
to problem solving using the concept of monotonicity. Most
of the previous research used intuitive methods that consider
the physics of the system as the prime factor directing the
decomposition. However, the quality of the results generated
by an intuitive method depends heavily on designers' experience. With the growing interest in engineering design, need for
a formal decomposition approach is apparent.
Some of the earlier work in the decomposition applied to
design include the research performed at NASA [14, 15, 16]
is concerned with the implementation of Steward's partitioning
algorithm [17] for identification of coupled design tasks. StewDECEMBER 1993, Vol. 115 / 687
a b c d e f g h
1 * * *
2 * * *
3
*~~*~|
4
**
5
I< *
6
* * *
7
* * *
Fig. 1
]
2
3
4
5
a b c d
* * *
* * *
*
*
*
'
1
f g h
* *
* *
* * * *
* * * *
* * * *
>
1
iC)
a b c d e f
1 * * *
2 * * *
3
* * *
4
|* * *
5 * * * * * *
6
* * * * * *
2.1 Decomposition Concept. Design and analysis activities involve a large number of tasks, e.g., layout design, finite
element analysis, and testing. To design new products of high
quality in less time, one should explore the possibility of the
decomposition of the design task into a group of tasks. The
relationship between tasks is analyzed in order to detect potential tasks that can be performed simultaneously.
The decomposition problem is formulated as follows:
Decompose a task-parameter incidence matrix into mutually separable submatrices (groups of tasks and groups
of parameters) with the minimum number of overlapping
tasks subject to the following constraints:
Constraint CI: Empty groups of tasks or parameters
are not allowed.
Constraint C2: The number of tasks in a group cannot
exceed the upper limit b (or alternatively, the number of parameters in a
group is not to exceed, d).
Of course, other constraints, for example, a resource cannot be used for two different tasks at the same time, can
be considered.
The objective function is "to minimize the number of overlapping parameters." An alternative objective function may
be used, for example, "to maximize the measure of effectiveness" defined in McCormick et al. [13].
To deal with the overlapping tasks, the following actions
can be taken:
Al. One can take advantage of the special structure of
the matrix and apply appropriate solution approaches.
A2. One may replace an overlapping task with an alternative task that involves different parameters.
A3. The design parameter can be decomposed into subparameters and each subparameter assigned to a
group of tasks that have some commonality with
that subparameter.
A4. An overlapping task can be removed from the matrix.
A5. The duration of the overlapping task can be shortened (e.g., by better management of resources or
tools used).
The concept of decomposition simplifies the design process.
Also, it explores the potential concurrency among design tasks
and reduces the time involved in the design process. The challenge is to decompose the overall design process into groups
of tasks that are of acceptable size, can be easily solved, and
for which an overall solution can be generated from the partial
solutions.
The decomposition concept is illustrated in Example 1.
Example 1
Consider a hypothetical design scenario involving ten design
tasks and seventeen design parameters. The relationship between tasks and parameters is represented as a flow diagram
shown in Fig. 2. For example, xs is the input parameter and
#15 and xn are output parameters of task px.
The task-parameter incidence matrix corresponding to the
network in Fig. 2 is shown in matrix (1):
Transactions of the ASME
: Source or destination
: Design task
Parameter
x2
x
Task
X4
x
Pi
P2
P3
P4
Pj
P6
P7
P8
*
*
*
*
*
*
P9
*
*
*
*
*
*
PlO
17
(1)
Matrix (1) is nonstructured and it is difficult to recognize
any groupings among the tasks and parameters. The problem
to be solved is to cluster the incidence matrix into groups of
tasks and parameters.
Applying the cluster identification (CI) algorithm [8] to matrix (1) results in matrix (2):
Parameter
G-2
J
G-i
I
1I
X]3
x5
Task
Pi
Pi
GP-1
Ps
Pio
P3
GP-2
P4
Lp8
GP-3
X,
x, 5
* * *
*
X6
x3
* * *
*
*
*
*
JP6
'
X 16
X2
xn
I I
xu
X14
X9
x7
"* * *
*
* *
*
*
G-3
l_
x4
x,o
1
X 12
x8
~* *
* * *
*
* *
(2)
Three mutually exclusive groups of task GP-1 = \pu p2,
Ps,P\o], GP-2 = {p 3 ,p 4 ,p 8 ],GP-3 = {p6,Pi,P9} and three
groups of parameters G-l = {xu JC3, x5, x6, xn, x15, x, 7 |, G2 = \xj, Xyt Xg, Xn, Xis], G-3 = [X4, x$, Xio, X\2, X\$\, are
X4
X3
Department A
X6
Xg Xio X 1 2 X M X)6 X[g X20 X J J X24 X 2 6 X 2 g
X 5 X 7 X 9 X n X l 3 Xlj X17 X19 X21 X23 X25 X 2 7
(rs)*"'
XI X2X3 X20X4X6X9
P |
Pl
P6
X9X23X28X5
P2
PlS
P2P15
P2
Pl5
(a)
Department C
j * 2 i ^0
(j6)&~
x
(3)
P2
Pi
23
x 6 X7X23X 2 6 X 2 7XgXi3
P4P11P16
X4 X7X21XMX25X22Xio
P5 I * * * *
P s P 3 PloPl2
P
P3
PlO
Pl2
Pi
P2
P3
P4
Ps
Pe
P7
Pn
P9
PlO
pn
P12
P 13
Pl4
Pl5
Pl6
(d)
(C)
Department E
Pn
(4)
Pl
Ps
P3
PlO
Pl2
P2
Pis
Pll
Plfi
P7
P13
Pl4
X3
Pi
P6
P4
Pa
P8
P9
P7
Pl3
Pl4
Pl7
, , ,,
* **
* *
* *
* * * *
* *l
*
-fr-
(5)
Matrix (5) contains a valuable information. First of all, it has
been determined that the overlapping tasks p4, p6, and ps are
critical to the design process. In the absence of the three tasks,
the design process would decompose into seven separable processes (see Fig. 5) that could be performed simultaneously. A
product planner may develop strategies leading towards the
weakening of the precedence relationship between tasks p4, p&,
and ps and the remaining tasks. He may focus especially on
the critical tasks and those related to them. Close analysis of
these tasks should improve the design process. Each of the
seven subprocesses in Fig. 5 can be also closely analyzed for
potential inconsistencies and improvements. It should be
stressed that the decomposition approach simplifies analysis
of the design process.
2.3 Analysis of Design Tasks. Whenever a task-parameter flow diagram can be decomposed into mutually separable
groups, no analysis of relationships between groups is needed.
690 / Vol. 115, DECEMBER 1993
p8
P9
P7
Pl3
Pl4
Pl7
* * * * * * * \*****
* * \
* *\
*\ **
\* *
\ ** *
* * *;
Pn
Ps P9P7P13P14P17
x 5 xgxtoxisx^xuxtsxwxtextgxnxw
x 2 8 x 26 x27 x l l X16 x 17 x 12 X 6
X2o x 7 X 2 4 X22 x 9
x
x
X 4 X 2 , X 2 5 Xic X23 X 5 Xs
13 x 14 X18 XIS
15
*
* *
* *
* * ~*
(e)
: Source or destination
: Design task
: Parameter flow
1. Customer requirements
2. Cabinet design
3. Components available
4. Mechanical design
5. Electrical design
6. Design specifications
7. Test assembly
8. Complete assembly
9. Complete documentation
10. Circuit boards available
11. Make parts
12. Assemble boards
13. Field tests O.K.
14. Environmental tests O.K.
15. Make cabinet
16. Make castings
17. Begin production
Fig. 4 Flow diagrams, task-parameter matrices, and precedence matrices of the design process
GP-2
Fig. 5
max {T,\
i
X2
Xl
Pi
P5
p3
PiO
Pl2
P2
PlS
Pi I
Pl6
P4
P7
p13
Pl4
Pl7
P9
p6
Ps I
X3
3.2 Algorithm 2. The branch-and-bound algorithm presented in this section analyzes the constraint-variable matrix
and identifies the potential constraints that can be evaluated
simultaneously during the design process in order to reduce
the product development time.
The algorithm iteratively examines each unfathomed node
in the enumeration tree. The lower bound ZL on the objective
function is the number of overlapping variables in the matrix.
The upper bound Zy is calculated only after a feasible solution
has been determined. The decomposition algorithm for the
constraint management problem is identical to Algorithm 1
presented in Section 2 with the exception of Step 1, which has
to be replaced with Step 1 presented next.
* * * *
IT-*
1
.
*
*
*
^ ^
.
*
*
I
* *
. .
I*
__
(6)
Step 1.
(Branching)
Based on the depth-first search strategy, select an
active node (not fathomed). Apply the CI algorithm
to the submatrix at a node that does not satisfy constraint C2. When the matrix does not decompose into
mutually separable submatrices, apply a branching
scheme to the submatrices at the same level.
Branching scheme:
Calculate the value of the overlapping measure (OM)
for each variable (constraint) and remove the variable
(constraint) with the highest value of the overlapping
measure. The overlapping measure OMj for variable
(constraint) j is defined as the number of distinct
variables that are included in at least one constraint
required by the variable j .
The following two conditions are considered:
DECEMBER 1993, Vol. 115 / 691
A:
h:
fi:
FC = P<A
-4
144p<72
_
^d
(9)
gA
Fd
h-
(10)
=T
Gd4
8D*R
Ls = d(N+2)
N=5-
Fc
4C-1
0.61
* * *
f3
where:
Fd
Fc
A
5
d
Pc
q
=
=
=
=
=
=
-
q
Fd
S
R
5 4 2 3 3 3
D
F
N
K
Ls
G
Li
Lf
* *
u
n
* * * *
<
* *
*
V2
V]
(18)
(13)
Similarly, variables R, Fd, and constraint / 4 are removed
from the matrix (18). The enumeration tree of the branch-andbound algorithm for matrix (17) is shown in the Appendix.
The result is shown in matrix (19).
(15)
A
Pc
C-d
fl
Fc
/,o-
Pc
f7
fs
f9
fio
OMi
4 3 10 4 2 9 4 4 8 5
(12)
(14)
R
K
(11)
52
(8)
2.55FD
S= d,
K
f.
(17)
f,:
=
=
=
=
=
=
=
=
=
=
=
=
=
(7)
h'
R
S
F
D
K
N
G
Ls
Lf
L;
C
P
g
(16)
fl
f3
is
f6
f7
u
12
fio
Lf
q
Li
D
F
U
G
* * *
* *
*
* *
d
Fd
*
* * * *
*
* *
*
*
*
*
*
*
*
*
* *
*
*
*
*
* *
*
(19)
u
Fc
A
Pc
GV-2
I
GV-1
A
Lf
Pc
r f i
* * *
*
*
1 I
S
D
N
Ls
L;
F
K
G
C
f6
f?
*
(20)
GV-1
i
r
-\
Fc
A
Lf
8
(dY_S
D
N
Ls ( d L
Pc
q
Li
Fd
F
K G
C (8)
fl
f3
* * *
*
* *
f4
*
*
*
* *
*
_ _ _-
*
* *
* *
*
* *
*
*
*
* *
h
U
f?
O
f9
L
fio
Cu-
(21)
In the case when the value of the overlapping variable d
(wire diameter) is duplicated (action B2) and the value of variable R is assumed (action Bl), the resultant matrix is shown
in (22).
GV-2
GV-1
I
Fc
A
Pc
fl
f3
fs
f2
.f4
f5
is
0 . - f?
f9
D
fio
Lt
q
8
Li
* * *
* *
*
* *
"~-
1 r
S
Fd
D
F
N
K
* *
~
Ls
N
**
* *
S
C
Lr
**
* **
Conclusions
In this paper, a methodology was presented for the decomposition of the design process. The incidence matrix was used
to represent the relationship between design parameters (variables) and tasks (constraints). Two cases of decomposition
were discussed. In the first case, the incidence matrix was
decomposed into mutually separate submatrices. No analysis
of the relationship between groups of tasks (constraints) was
needed. In the case of overlapping tasks (constraints), analysis
of the relationships between the groups of tasks (constraints)
was required. Three observations can be drawn:
(1) The overlapping tasks should be performed as early
as possible during the design process in order not
to delay the completion time of other activities.
(2) One may redefine (reformulate) the overlapping
tasks (constraints) in order to enhance degree of
concurrency.
(3) Decomposition strategy simplifies the constraint
management and reduces the computational time
for solving the resultant subproblems.
Groups of tasks (constraints) involved in the design process
allow one to determine a potential group of tasks (constraints)
that might be performed simultaneously. The latter should
reduce the time of product development. Another advantage
of grouping tasks (constraints) is the simplification of scheduling and management of the design project (constraint management).
*
* * * *
*
*
* *
*
*
*~
*
*
*
* *
References
(22)
Journal of Mechanical Design
* **
* * #
K
D
Acknowledgment
The research presented in this paper has been partially supported by research grants (DDM-9007158 and DDM-9215259)
from the National Research Foundation and research contracts
from Rockwell International.
*
*
f7
f9
f 10
fs
f6
fs
f4
d
5
(23)
In some cases, the reformulation of the overlapping constraints (action D2) is possible. The reader interested in constraint reformulation may refer to Watton and Rinderle [22].
* *
*
*
fio
rh
u
* *
rfs
GP-2
I
Fc
q
Fd
(continued on p. 695)
A P P E N D I X
The Branch-and-Bound Tree for Branch-and-Bound Algorithm
*
5 2 4 3 10 4 2
9 4 4 8 5 5 4 2 3 3 3
FcnA
d q
S
D N It U
Pc
6 Fd R F
K G Lf C
fl
f2
f3
+ *
* *
*
*
*
*
f5
f6
f7
fg
f9
flO
* * * *
* *
,1,00
5 2 4 3 2
FcAT,q
P0 F d
7 3 3 7 4 4 3 1 3 3 2
S D N L, L;
F
K G Lf C
fl
tl
f4
f5
f
f7
* * *
* * *
*
*
+ * * *
+
* *
*
fl
f^
fs
\@0
N L Lj
K G Lf C
*
* *
*
* * * *
*
*
*
*
Lower bound
=2
* *
*
*
Algorithm
Fc
A
Pc
# * *
*
*
Li Lj
G Lf
* *
*
*
*
Algorithm
Fc A
L{ S
D N Ls
5 d
Pc
q
Li
F
K G C Fd R
fl
f3
fs
fs
f6
f7
f9
flO
f2
f4
N
F
* *
f7
fs
*
*
* *
S
R
* * *
fl
t3
f4
fs
* * * *
*
* *
*
*
*
Fd
Pc
Fc
* * *
f7
f8
f9
tio
s
q
@/
Pc
f9
flO
Fc
Lower bound
=1
+ *
*
*
*
*
*
*
* *
*
fl
f3
f4
f
f7
Is
ts
q
Fd
N
R
L Li F
G Lf S
* * *
* * *
*
*
* * *
*
*
*
* *
Lower bound
=2
* *
Fathomed
Upper bound = 2