We start by
outlining the architecture of DSM in Section 4.1 and then the following sections
describe each architectural element in further detail. Finally in Section 4.6, we inspect
the organizational structure and roles in creating a DSM solution, and outline its
creation process.
4.1 INTRODUCTION
To get the DSM bene?¬?ts of improved productivity, quality, and complexity hiding, we
need to specify howthe automation from high level models to running systems should
work. For this task DSM proposes a three-level architecture on top of the target
environment, as illustrated in Fig. 4.1:
. A domain-speci?¬?c language provides an abstraction mechanism to deal with
complexity in a given domain. This is done by providing concepts and rules
within a language that represent things in the application domain, rather than
concepts of a given programming language. Generally, the major domain
concepts map to modeling language objects, while others will be captured as
object properties, connections, submodels, or links to models in other
languages. Thus, the language allows developers to perceive themselves as
working directly with domain concepts. The language is de?¬?ned as a
Domain-Speci?¬?c Modeling: Enabling Full Code Generation, Steven Kelly and Juha-Pekka Tolvanen
Copyright # 2008 John Wiley & Sons, Inc.
Pages:
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140