After month 5 you then
have 15 applications ready. We assume here that one developer would still be
improving the DSM solution. After month 6 you have 25 applications ready
compared to the 10 you would have had without DSM. Getting those same 25
applications without DSM would have taken until the end of month 25! To decide
whether to invest in DSM, you can calculate your own costs of application
development to see the difference.
Usually, the cost of waiting is much larger than the original cost of building aDSM
solution and introducing it. If the target environment is ready, the cost of de?¬?ning
modeling languages and generators is usually a matter of man-weeks and in worst
cases not longer than a few man-months. The development times are described in
relation to practical examples in Part III, where we describe different DSM solutions
and their development.
2.4.3 Ownership of Your DSM Solution
A DSM approach, like all automation, requires two different teams: one building the
automation and one using it. While users get the bene?¬?ts, it is also relevant to know
who develops the DSM solution. Generally, it could be your own developer, an
external consultant, or a tool vendor. The pros and cons of each are as follows.
THE ECONOMICS OF DSM 39
Made In-House In-house development is often seen as the preferred choice
simply because it guarantees control of the automation.
Pages:
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98