Truly model-driven
development uses automated transformations in a manner similar to the way a pure
coding approach uses compilers. Once models are created, target code can be
generated and then compiled or interpreted for execution. From a modeler??™s
perspective, generated code is complete and it does not need to be modi?¬?ed after
generation. This means, however, that the ???intelligence??? is not just in the models
but in the code generator and underlying framework. Otherwise, there would be no
raise in the level of abstraction and we would be round-tripping again. The
completeness of the translation to code should not be anything new to code-only
developers as compilers and libraries work similarly. Actually, if we inspect
compiler development, the code expressed, for instance in C, is a high-level
speci?¬?cation: the ???real??? code is the running binary.
Model-Driven Development is Domain-Speci?¬?c To raise the level of
abstraction in model-driven development, both the modeling language and the
generator need to be domain-speci?¬?c, that is, restricted to developing only certain
kinds of applications. While it is obvious that we can??™t have only one code generator
for all software, it seems surprising to many that this applies for modeling languages
too.
This book is based on the ?¬?nding that while seeking to raise the level of
abstraction further, languages need to be better aware of the domain.
Pages:
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35