CatchDialN: Activity with AcceptEventAction for a SignalEvent and a CallBehaviorAction

Gallery
Tutorial
HOWTO simulate UML-2.5.1 'Figure 14.7 Composite State with two States' in Cameo Simulation Toolkit - Operation-driven Transition case study
Section
UML keywords
Behavior
Activity
AcceptEventAction
CallBehaviorAction
Slide kind
UML Activity Diagram
The Activity CatchDialN receives SignalEvents corresponding to numbered buttons on a telephone using AcceptEventAction items, then invokes a usage of Activity DialN(n:int[1]) via a CallBehaviorAction:
Click on the image to view it full size
We'll be processing many digits during the dialing of an entire phone number, so we need to embed this in a higher level "loop" as shown next
Up next
The Controller Activity (classifierBehavior of the Controller class)
Notes
Snippets (quotes/extracts)
  [UML-2.5.1] If an AcceptEventAction is used in an Activity, there are special rules for when it is enabled ..
  [UML-2.5.1] If the AcceptEventAction has no incoming edges, by the usual rules, it is enabled when its immediately containing Activity (or StructuredActivityNode) begins execution.
  [UML-2.5.1] AcceptEventAction is an Action with Triggers for one or more Events. When an AcceptEventAction is executed, it waits for an Event occurrence to be dispatched from the event pool of the context object for its execution that matches one of its Triggers.
  [UML-2.5.1] An AcceptEventAction is a wait point ... except only the AcceptEventAction waits, rather than the whole Activity (Activities can have other Actions executing while AcceptEventActions are waiting).
  [UML-2.5.1] An AcceptEventAction with a trigger for a SignalEvent is informally called an accept signal action.
  [UML-2.5.1] If it has isUnmarshall=true, then it must have result OutputPins corresponding to each of the attributes of the Signal of the SignalEvent (in order), and the attribute values of the Signal instance associated with an accepted SignalEvent occurrence ...
  [UML-2.5.1] A CallBehaviorAction is a CallAction that invokes a Behavior directly, rather than calling a BehavioralFeature that, in turn, results in the invocation of a Behavior.
  [UML-2.5.1] The argument Pins of a CallAction are matched, in order, to the sublist of input Parameters, while the result Pins are matched, in order, to the sublist of output Parameters.
Related slides (includes other tutorials)
Related slides (backlinks, includes other tutorials)
uml101 - Activity Diagram - notation - REFERENCE CARD
Visit also
Visit also (backlinks)