|
Activity Diagram Sample
|
|
The Activity Diagram can help to describe the flow of control of the target system.
|
|
| |
|
AcceptEventAction
|
|
AcceptEventAction is an action that waits for the occurrence of an event meeting specified conditions.(OMG Unified Modeling Lanauge Specification - UML 2.0 Superstructure Specification, p. 249)
|
|
| |
|
Action
|
|
An action may have sets of incoming and outgoing activity edges that specify control flow and data flow from and to other nodes. An action will not begin execution until all of its input conditions are satisfied. The completion of the execution of an action may enable the execution of a set of successor nodes and actions that take their inputs from the outputs of the action.(OMG Unified Modeling Lanauge Specification - UML 2.0 Superstructure Specification, p. 336)
|
|
| |
|
ActivityFinal
|
|
An activity may have more than one activity final node. The first one reached stops all flows in the activity.(OMG Unified Modeling Lanauge Specification - UML 2.0 Superstructure Specification, p. 356)
|
|
| |
|
DataStore
|
|
A data store keeps all tokens that enter it, copying them when they are chosen to move downstream. Incoming tokens containing a particular object replace any tokens in the object node containing that object.(OMG Unified Modeling Lanauge Specification - UML 2.0 Superstructure Specification, p. 386)
|
|
| |
|
DecisionNode
|
|
A decision node is a control node that chooses between outgoing flows.(OMG Unified Modeling Lanauge Specification - UML 2.0 Superstructure Specification, p. 387)
|
|
| |
|
FlowFinal
|
|
A flow final destroys all tokens that arrive at it. It has no effect on other flows in the activity.(OMG Unified Modeling Lanauge Specification - UML 2.0 Superstructure Specification, p. 403)
|
|
| |
|
ForkNode
|
|
A fork node has one incoming edge and multiple outgoing edges.(OMG Unified Modeling Lanauge Specification - UML 2.0 Superstructure Specification, p. 404)
|
|
| |
|
InitialNode
|
|
An activity may have more than one initial node.(OMG Unified Modeling Lanauge Specification - UML 2.0 Superstructure Specification, p. 406)
|
|
| |
|
JoinNode
|
|
A join node has multiple incoming edges and one outgoing edge.(OMG Unified Modeling Lanauge Specification - UML 2.0 Superstructure Specification, p. 411)
|
|
| |
|
MergeNode
|
|
A merge node is a control node that brings together multiple alternate flows. It is not used to synchronize concurrent flows but to accept one among several alternate flows.(OMG Unified Modeling Lanauge Specification - UML 2.0 Superstructure Specification, p. 416)
|
|
| |
|
ObjectNode
|
|
An object node is an activity node that indicates an instance of a particular classifier, possibly in a particular state, may be available at a particular point in the activity. Object nodes can be used in a variety of ways, depending on where objects are flowing from and to, as described in the semantics section.(OMG Unified Modeling Lanauge Specification - UML 2.0 Superstructure Specification, p. 422)
|
|
| |
|
SendSignalAction
|
|
SendSignalAction is an action that creates a signal instance from its inputs, and transmits it to the target object, where it may cause the firing of a state machine transition or the execution of an activity.(OMG Unified Modeling Lanauge Specification - UML 2.0 Superstructure Specification, p. 302)
|
|
| |
|
ControlFlow
|
|
Objects and data cannot pass along a control flow edge.
|
|
| |
|
ObjectFlow
|
|
An object flow models the flow of values to or from object nodes.(OMG Unified Modeling Lanauge Specification - UML 2.0 Superstructure Specification, p. 383)
|
|
| |
|
Activity
|
|
An activity specifies the coordination of executions of subordinate behaviors, using a control and data flow model. The subordinate behaviors coordinated by these models may be initiated because other behaviors in the model finish executing, because objects and data become available, or because events occur external to the flow.(OMG Unified Modeling Lanauge Specification - UML 2.0 Superstructure Specification, p. 341)
|
|
| |
|
ActivityPartition
|
|
Partitions divide the nodes and edges to constrain and show a view of the contained nodes. Partitions can share contents. They often correspond to organizational units in a business model. They may be used to allocate characteristics or resources among the nodes of an activity.(OMG Unified Modeling Lanauge Specification - UML 2.0 Superstructure Specification, p. 367)
|
|
| |
|
InterruptibleActivityRegion
|
|
An interruptible region contains activity nodes. When a token leaves an interruptible region via edges designated by the region as interrupting edges, all tokens and behaviors in the region are terminated.(OMG Unified Modeling Lanauge Specification - UML 2.0 Superstructure Specification, p. 409)
|
|
| |
|
ExceptionHandler
|
|
An exception handler is an element that specifies a body to execute in case the specified exception occurs during the execution of the protected node.(OMG Unified Modeling Lanauge Specification - UML 2.0 Superstructure Specification, p. 390)
|
|
| |
|
ExpansionRegion
|
|
An expansion region is a strictly nested region of an activity with explicit input and outputs (modeled as ExpansionNodes). Each input is a collection of values. If there are multiple input pins, each of them must hold the same kind of collection, although the types of the elements in the different collections may vary. The expansion region is executed once for each element (or position) in the input collection.(OMG Unified Modeling Lanauge Specification - UML 2.0 Superstructure Specification, p. 395)
|
|
| |
|
Local pre- and postconditions
|
|
In CompleteActivities, action is extended to have pre- and postconditions.(OMG Unified Modeling Lanauge Specification - UML 2.0 Superstructure Specification, p. 336)
|
|
| |
|
ParameterSet
|
|
An parameter set acts as a complete set of inputs and outputs to a behavior, exclusive of other parameter sets on the behavior.(OMG Unified Modeling Lanauge Specification - UML 2.0 Superstructure Specification, p. 430)
|
|
| |
