First, they need to learn that they can trust the models just as
they trusted the code. Later, ef?¬?cient model creation, modi?¬?cation, and reuse practices
must follow. Diagrammatic languages, matrix representation, or tables offer
representations other than linear text. We discuss the difference of modeling with
DSM versus traditional manual coding in Chapter 3.
To introduce DSM, it is especially relevant to know how developers, those doing
the modeling, react when the nature of development work changes from manual
coding to modeling and generating the code. This topic is a less studied area, but we
can expect that, like all new technology that changes working practices, attitudes
toward DSM can vary from highly accepted to rejected. In Ruuska (2001), 17
developers in a telecom company, all working with the same DSM solution, were
interviewed to examine their attitudes toward changed working practices. Every
developer interviewed had experience with traditional manual development practices.
Out of the 17, only two developers preferred the earlier manual coding practices to
DSM. Interestingly, those two developers preferring manual coding were still using
DSM although the manual coding approach was also available. Nine of the 17
developers found DSM better than earlier manual practices and the remaining six
developers could not say their preference.
Pages:
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83