3.1 DSM CHARACTERISTICS
Raising the level of abstraction and using automation can be done in multiple ways:
for example, using software platforms, frameworks, or component libraries. These
offer abstractions that help in managing complexity but usually still require
developers to program and specify mappings to the components manually, in code.
Traditional modeling languages, such as UML, IDEF, and SSADM, usually do not
help developers much here since the languages are normally based on coding concepts
and other concepts with loosely de?¬?ned semantics. InUML, an example of the former
is class diagrams and of the latter, state machines, activity diagrams, or use case
diagrams. In both cases, the modeling concepts do not relate to any particular problem
domain or, on the implementation side, to any particular software platform,
Domain-Speci?¬?c Modeling: Enabling Full Code Generation, Steven Kelly and Juha-Pekka Tolvanen
Copyright # 2008 John Wiley & Sons, Inc.
45
framework, or component library. Modelers can therefore create models and connect
their elements together regardless of the rules of the domain or particular
implementation.
DSM changes this. It allows one to continue raising the level of abstraction and
provides the necessary automation. A key element in raising the level of abstraction is
having modeling languages that map more closely to the problem domain.
Pages:
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104