If there are input pins at the action, then
they are mapped on input parameters of the behavior. Similarly, the output pins
correspond to the output parameters. If the invoked behavior is an activity, then
a fork symbol is denoted in the lower right corner of the action rectangle to symbolize
the call hierarchy of activities ( Figure 3.42 ).
OpaqueAction integrates an implementation in an arbitrary language in the
model. This can be something executable (e.g., something written in a programming
language) or a natural-language text that explains the implementation. The
purpose of OpaqueAction is to formally embed such user-specifi c instructions in
the entire model. For example, the step check emergency driving in Figure 3.42 is
an OpaqueAction . You can ??™ t see this in the notation, but this information is stored
in the model.
We even used the SendSignalAction twice in Figure 3.42 ??”both times for sending
the signal status display . The notation of this action differs of those of the
other actions. It ??™ s a kind of arrow symbolizing that something is being sent.
Pages:
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360