With DSM, there is no longer any need to make
error-prone mappings from domain concepts to design concepts and on to
programming language concepts. In this sense, DSM follows the same recipe that
made programming languages successful in the past: offer a higher level of abstraction
and make an automated mapping from the higher level concepts to the lowerlevel
concepts known and used earlier. Today, DSM provides a way for continuing
to raise the description of software to more abstract levels. These higher
abstractions are based not on current coding concepts or on general-purpose
concepts but on concepts that are speci?¬?c to each application domain.
In the vast majority of development cases general-purpose modeling languages
like UML cannot enable model-driven development, since the core models are
at substantially the same level of abstraction as the programming languages
SUMMARY 19
supported. The bene?¬?ts of visual modeling are offset by the resources used in
keeping all models and code synchronized with only semiautomatic support.
In practice, part of the code structure is duplicated in the static models, and the
rest of the design??”user view, dynamics, behavior, interaction, and so on??”and the
code are maintained manually.
Domain-speci?¬?c languages always work better than general-purpose languages.
Pages:
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57