These ?¬?gures can vary
highly, for example, depending on the organizational cultures and individual
backgrounds. There is, however, a place for traditional manual coding work??”areas
which cannot be automated with DSM. The capabilities of the best programmers can
be used there. In the DSM architecture, discussed later in Chapter 4, the more
experienced programmers can focus on making the generators, framework code, or
other components of the target environment.
2.4 THE ECONOMICS OF DSM
Domain-speci?¬?c approaches should generally be used whenever possible. They
normally produce better results than general-purpose approaches. Ready-to-useDSM
solutions, however, are normally not available. Because of the differences in the
problem domain, underlying architectures, target environments, and generators
targeting different programming languages, etc., it is often the case that a company
must consider building its own DSM solution, or at least modifying an available one.
The decision to create a DSM solution is both technical and economical. While the
remaining parts of this book mostly address the technical side, we focus next on the
economics of DSM.We will begin by discussing the investment and its payback and
then move on to ownership.
2.4.1 Use an Existing DSM Solution?
Often the use of existing DSM solutions is simply impossible because companies that
created them want to keep them in-house.
Pages:
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87