Activity Diagram Elements

See Also

The following table describes the elements that you can add to Activity diagrams. The elements are grouped by Context Palette and Modeling Palette section and are also listed if they appear on the Context Menu.

Element Icon Description
Basic Section
Invocation The use of a behavior within an Activity.
Activity Group Sets of invocation nodes and activity edges in an Activity. A generic grouping construct for nodes and edges.
Initial Node A control node at which flow starts when the Activity is invoked.
Activity Final Node The final node that stops all flows in an Activity.
Flow Final The final node that terminates a flow and destroys all tokens that arrive at it.
Comment A Notepad notation. Use Comments to record information for a element or link in a diagram. This information is not included in generated code but is for information only. Each Comment can contain unlimited text, and can be numbered. You can also define a stereotype, and enter a noted element.
Control Section
Decision A control node that chooses between outgoing flows.
Vertical Join A vertical control node that splits a flow into multiple concurrent flows.
Horizontal Join A horizontal control node that splits a flow into multiple concurrent flows.
Data Section
Parameter Usage An object node for inputs and outputs to invocations. Parameter usage nodes flow directly to or from invocations.
Data Store A central buffer node for non-transient information. Object node for mapping flows from multiple sources and destinations.
Signal An object node that sends or receives signals.
Partition A special kind of grouping of invocations and activity edges. Partitions divide the nodes and edges to constrain and show a view of the contained nodes. Partitions often correspond to organizational units in a business model.
Context Palette
Activity Edge An abstract class for directed connections between two Activity nodes.
Link Comment The connection between the comment element and the associated element.
Dependencies Section on Context Palette
Dependency The relationship between two elements whose definitions depend on one another in such a way that changes to one can result in changes to the other. For example, when one class mentions another as an operation parameter, or as part of its data, the two classes exhibit dependency.
Realize A semantic relationship between classifier. One classifier specifies a contract that another classifier guarantees to carry out. These relationships are used in two places: between interfaces and the classes that realize them, and between Use Cases and the Collaborations that realize them.
Usage A dependency in which one element (the client) requires the presence of another element (the supplier) for its correct functioning or implementation.
Permission A dependency that signifies granting of access rights from the supplier model element to a client model element, in which the client requires access to some or all of the constituent elements of the supplier.
Abstraction A boundary relative to the perspective of the viewer. The essential characteristics of an entity that distinguish it from all other kinds of entities.
See Also
About Activity Diagrams
Diagram Elements

Legal Notices