32 BUSINESS VALUE
There can be multiple reasons for negative attitudes, but generally, those losing
their position as ???top coders??? may see DSM as a threat.With DSM, less experienced
developers can produce code that is as good as, if not better than, code written
manually by more experienced developers. This change must be taken into account
when introducingDSM. Most likely the same kind of situation exists as when the need
for assembly programming was reduced while introducing languages like Fortran and
Basic. In DSM, there is still a need for developing components and supporting
framework code along with generators, although most developers can use the domainspeci
?¬?c languages.
Learning the Domain and Modeling Languages Introduction of DSM
requires that the modeling languages be learned. Learning them, however, can be
easier than say learningUML since the domain concepts are known, or at least need to
be known regardless of how the software is developed. For example, an empirical
study in a telecom company (Ruuska, 2001) showed that a maximum of 2.5 days was
needed to learn the DSM solution. The study showed that most developers (11 of 17)
received less than a day??™s training but were soon capable of creating nontrivial
applications.
Preserving Domain Knowledge Although a DSM solution may seem to offer
the possibility of developing applications without preserving further knowledge
about the internal structure of the DSM solution, such a scenario is usually not viable.
Pages:
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84