Models are the primary source to edit. All coding,
however, does not disappear for everybody since we need developers who implement
the generators, provide framework code, and make reusable libraries and components.
Part IV of this book gives guidelines for de?¬?ning the DSM solution.
No Need to Learn New Languages and Semantics. Problem domain
concepts are typically already known and used. They have well-de?¬?ned semantics and
are considered ???natural??? as they are formed internally. Because these domain-speci?¬?c
semantics must be mastered anyway, in DSM they are given ?¬?rst class status.
Developers do not need to learn additional semantics (e.g., UML) and map back and
forth between domain andUMLsemantics. This unnecessary mapping takes time and
resources, is error prone, and is carried out by all designers??”some doing it better, but
often all doing it differently.
Routine Tasks Are Minimized. Generators can??™t provide intelligence but rather
automate repetitive tasks. This is not new, for decades we have successfully used, for
example, compilers to automate similar kinds of repetitive tasks. Now generators
provide the same automation but in the context of a speci?¬?c application domain. This
52 DSM DEFINED
automation allows developers to focus on more interesting topics and address
application functionality rather than its implementation details.
Pages:
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118