Most of the literature describing model-based development uses modeling to
generate structural aspects of software systems. As systems almost always have a
behavioral side too, and structural aspects tend to be easier, in this book we want to
focus on dynamic and behavioral aspects. In Part III, we mostly address cases that
capture dynamic behavior and generate code for nonstatic structures. On the
modeling language side, state machines and various ?¬‚ow, process, and interaction
diagrams are used. Using the models produced by these languages, generators can
produce functional code, not just con?¬?guration or static code.
Combining MOCs and Extending the Languages Some languages fall into
more than one category as they can be seen to capture both static structures and
dynamic behavior. Usually they are stronger on one side but also address the other. For
instance, in business process modeling, a work?¬‚ow language describing the behavior
can also have modeling constructs that specify structures for the data that is passed
between the processes. Conversely, a data model can also include modeling constructs
that specify how the data is used by the system. A single language can usually be
extended this way only to a certain limit, motivating the use of multiple languages.
Several languages are needed not only because of the different models of computation
needed but also because of the size of the domain and its rules, having different people
creating and using the model or sharing designs with various stakeholders, such as
subcontractors.
Pages:
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157