The choice of a language involves not only choosing a particular modeling
language or computational model per se but also the selection of a subset of
modeling constructs and extending them for a given domain. Regarding the subset,
in every domain where a state diagram is used it is not necessary to apply a history
state to remember the state of the system before it was interrupted. Similarly, using
combined fragments and specifying inner connections between objects in a
sequence diagram based on UML2 are not needed in most cases. A language
providing these constructs just adds extra burden for most modelers. Regarding the
language extensions, adding new syntactic and semantic constructs is usually
necessary to specify software systems adequately. These constructs are domainspeci
?¬?c as their naming, properties, constraints, connections to other language
constructs, and overall semantics are formalized keeping only one domain in mind.
Remember that seeking automation makes the difference here! While it is ?¬?ne to
apply different approaches in models for sketching and documentation, code
generation sets more detailed requirements for choosing the computational model.
72 ARCHITECTURE OF DSM
In other words, models need to capture enough data to provide input for code
generators.
4.2.3 Integrating Languages for Modeling Multiple Aspects
Larger software systems usually require specifying different views, aspects, and
levels of detail.
Pages:
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158