The applicability of DSM is demonstrated
with ?¬?ve different examples, each targeting a different kind of domain and generating
code for a different programming language. These cases are then used to
exemplify the creation and use of DSM.
New technologies often require changes from an organization: What if most
code is generated and developers work with domain-speci?¬?c models? For managers,
we describe the economics of DSM and its introduction process: how to estimate the
suitability of the DSMapproach and what kinds of expertise and resources are needed.
Finally, we need to recognize the importance of automation for DSM creation: tools
for creating DSM solutions. This book is not about any particular tool, and there is a
range of new tools available helping to make creation of a DSM solution easier,
allowing expert developers to encapsulate their expertise and make work easier, faster,
and more fun for the rest.
1.2 CODE-DRIVEN AND MODEL-DRIVEN DEVELOPMENT
Developers generally differentiate between modeling and coding. Models are used
for designing systems, understanding them better, specifying required functionality,
and creating documentation. Code is then written to implement the designs.
Debugging, testing, and maintenance are done on the code level too. Quite often
these two different ???media??? are unnecessarily seen as being rather disconnected,
although there are also various ways to align code and models.
Pages:
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31