In DSM, the languages built for internal use are normally de?¬?ned by just one
or a few people. The role of models in development is therefore a little different from
what you may be used to: In DSM, models are the source and primary artifacts with
which to work. We describe the role of models in more detail in Section 4.3.
The generator structure is usually not visible to modelers and can be considered
similar to a compiler. Following this analogy, the transformation from models to
FIGURE 4.3 DSM de?¬?nition and DSM use
INTRODUCTION 67
running product code is unidirectional and modi?¬?cation of the generated code is
not needed. This completeness has been the cornerstone of other successful shifts
made with programming languages. The DSM architecture also shows that all code is
not necessarily generated. The domain framework and target environment may be
available as code or as interfaces the generator can integrate with. Generated code can
also be integrated with manually written code if needed. The code generator and
domain framework are often made by the same people, and it is a task that only a few
developers perform: most developers are not involved in generator de?¬?nition, they just
use it.
In the following, we describe each elementary architectural unit of DSM in more
detail, namely, the language, models, generators, and domain framework.
Pages:
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147