63
metamodel with related notation and tool support. We inspect the role of
languages in DSM further in Section 4.2.
. A generator speci?¬?es how information is extracted from the models and
transformed into code. In the simplest cases, each modeling symbol produces
certain ?¬?xed code, including the values entered into the symbol as arguments.
The generator can also generate different code depending on the values in the
symbol, the relationships it has with other symbols, or other information in the
model. This code will be linked with the framework and compiled to a ?¬?nished
executable. While creating a working DSM solution the objective is that after
generation, additional manual effort to modify or extend the generated code is
not needed. The generated code is thus simply an intermediate by-product on
the way to the ?¬?nished product, like .o ?¬?les in C compilation. We describe
generator characteristics in more detail in Section 4.4.
. A domain framework provides the interface between the generated code and
the underlying platform. In some cases, no extra framework code is needed: the
generated code can directly call the platform components, whose existing
services are enough. Often, though, it is good to de?¬?ne some extra utility code
or components to make the generated code simpler. This framework code can
range in size from components down to individual groups of programming
language statements that occur commonly in code in the selected domain.
Pages:
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141