3.2.2 What DSM is Not
Implications for development work can also be inspected by describing situations that
are not typical for DSM.
IMPLICATIONS OF DSM FOR USERS 53
Modeling with Pure Code Concepts. In DSM models do not try to visualize
code or apply coding concepts as the constructs of the modeling language. Codingrelated
constructs are usually easy to add to the language later if needed, but not
necessarily the other way around. If the domain is close to the code, the domainspeci
?¬?c language can also apply code concepts. Most likely, however, the level of
abstraction will not then be raised much and the bene?¬?ts of code generation will
remain modest.
Modeling for Sketching or for Documentation Only. While models serve as
a mechanism to get a better understanding inDSM, they are also used as input for code
generators.DSMdoes not require are additional modeling phase for documentation as
it can be generated from the same single source.
Heavy Up-Front Modeling. For some people, modeling is seen as an inef?¬?cient
step creating a lot of unnecessary models at the beginning of the project. While this
might be true when models are separate from the application built, inDSMthe models
are the source. In DSM, we model only those aspects that are also needed in later
development stages, such as for generating production code, simulation, con?¬?guration,
or test cases.
Pages:
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121