Modeling Dynamic Structures and Behavior The second major class of
modeling languages is the one specifying behavior and dynamic aspects of a system or
its part. State machines, interaction diagrams, and Petri-nets are perhaps the most
common modeling languages in this category, along with their many dialects. These
modeling languages are very typical in cases where the system can be considered as
event or state based.
We can also consider here various process and ?¬‚ow diagrams used for process
modeling, work?¬‚ow modeling, data ?¬‚ow, and signal processing. If we look at tools
for model-based development, Labview and its modeling language G (National
Instruments, 2005) and Matlab/Simulink toolboxes (Mathworks, 2007) focus on
LANGUAGE 71
describing behavior and functionality. Their languages are actually domain-speci?¬?c
and within their scope these languages work well. Provided by the tool, their
extensions and modi?¬?cations are done typically by the tool vendor.
In DSM, behavioral aspects need to be speci?¬?ed to generate code that deals with
functionality, business rules, and other application logic. In domain-speci?¬?c
languages, such behavior is often captured by extending some of the well-known
models of computation. Such extensions can deal with adding speci?¬?c business
process concepts and rules to the language, logic operations, conditions, decision
points, and other functional aspects.
Pages:
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156