In contrast, if we have just one developer and we are creating a product
only once, automation is unlikely to prove bene?¬?cial.
Repetition, however, is not the only factor when estimating value. With a DSM
solution, less experienced developers can create applications or the work can be
allocated differently than with traditional manual practices. This is possible because
the technical details can be hidden from application developers. In some cases, the
development work can be radically reallocated by giving it to domain experts, who do
not necessarily have programming experience.
The Cost of Building a DSM Solution The bene?¬?ts of DSM are not free;
someone must create the DSM solution. This is the initial investment. In Fig. 2.1, the
cost of using DSM is therefore larger at the beginning than when continuing with
current practice, which does not require any additional investment.
The initial building cost for DSM is usually comprised almost entirely of human
resource costs, namely, domain experts and experienced developers. Earlier, the
cost of tool development was also relatively high since companies needed to
THE ECONOMICS OF DSM 37
build tools from scratch or by using supporting libraries and frameworks. For
example, implementation of a UML-based modeling tool with Eclipse and related
frameworks is calculated to have taken over 20 man-years to complete (Stro??
bele,
2005).
Pages:
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94