Initial, Final and Flow Final Node

Initial Node (Start State)

1. The starting state before an activity takes place is depicted using the initial state.
2. A process can have only one initial state unless we are depicting nested activities. We use a black filled circle to depict the initial state of a system.
3. The Initial State from the UML Activity Diagram marks the entry point and the initial Activity State.

Final Node (End State)

In the UML, a final action state is shown using a circle surrounding a small solid filled circle (a bull's eye). An activity diagram may have only one initial action state, but may have any number of final action states.

Flow Final Node

UML 2.0 has an additional control node type called Flow Final that is used as an alternative to the Activity Final node to terminate a flow. It is needed because in UML 2.0, when control reaches any instance of Activity Final node, the entire activity (including all flows) is terminated. The Flow Final simply terminates the flow to which it is attached.

Note: This was not an issue in UML 1.5 because of the run-to-completion semantics, but with the unrestricted parallelism of UML 2.0, you might not want all flows stopped and all tokens destroyed.

Action and Activity State

An activity, also known as an activity state, on a UML Activity diagram typically represents the invocation of an operation, a step in a business process, or an entire business process.

Action is a named element which represents a single atomic step within activity i.e. that is not further decomposed within the activity.

Flow Transition

Given a collection of action states, how are those action states related to one another? Flow transitions address this issue, a flow transition shows how action states are ordered or sequenced. There are various types of flow transitions, including control-flow and object-flow transitions.

Control Flow

Action flows or Control flows are also referred to as paths and edges. They are used to show the transition from one activity state to another. An activity state can have multiple incoming and outgoing action flows. We use a line with an arrow head to depict a Control Flow. If there is a constraint to be adhered to while making the transition it is mentioned on the arrow.

In the UML, a control-flow transition is shown as a solid line from a source action state to a target action state.

Object Flow

In the UML, an object-flow transition is shown as a dashed arrow between an action state and an object. An action state that uses an object as input is shown with the object-flow transition arrow pointing from the object to the action state. An action state that updates or produces an object as output is shown with the object-flow transition arrow pointing from the action state to the object.

1. An object produced or used by actions. This allows us to model object flows.

Decision Nodes and Branching

When we need to make a decision before deciding the flow of control, we use the decision node, such as one incoming transition, and multiple outgoing parallel transitions and/or object flows.

Decision Node

1. A decision node accepts tokens on an incoming edge and presents them to multiple outgoing edges.
2. Which of the edges is actually traversed depends on the evaluation of the guards on the outgoing edges.

Merge Node

1. A merge node is a control node that brings together multiple alternate flows.
2. It is not used to synchronize concurrent flows but to accept one among several alternate flows.
3. A merge node has multiple incoming edges and a single outgoing edge.

Fork Node

1. A fork node is a control node that splits a flow into multiple concurrent flows.
2. A fork node has one incoming edge and multiple outgoing edges.

Join Node

1. A join node is a control node that synchronizes multiple flows.
2. A join node has multiple incoming edges and one outgoing edge.

Guard

A guard is a condition that must be true in order to traverse a transition.

Object Node

UML 2.0 activity modeling also supports object nodes. An object node is an activity node that indicates that an instance of a particular classifier, possibly in a particular state, might be available at a particular point in the activity (for example, as output from, or input to an action). Object nodes act as containers to and from which objects of a particular type (and possibly in a particular state) might flow.

Data Store

A datastore is a stereotype for an object which stores objects persistently.

Note

1. A note (comment) gives the ability to attach various remarks to elements.
2. A comment carries no semantic force, but may contain information that is useful to a modeler.

Swimlane

A swimlane activity diagram groups the activities into swimlanes columns that contain all of the activities which fit into the category represented by that swimlane. Swimlanes can represent many categories of information such as actors which perform the activities (i.e., role or department), the stage of the process in which the activity takes place, or whatever else the creator of the document feels should be emphasized and communicated by the swimlane diagram. The term swimlane was adopted due to the visual similarity between the horizontal rows of the diagram to that of the swimlanes found within a swiming pool.

In the UML, a swimlane is shown as a visual region separated from neighboring swimlanes by vertical solid lines on both sides and labeled at the top with the element responsible for action states within the swimlane.

Time Event & Event Signal

Time event flows when the time expression is true, while event signal flows when a event occurs. An hourglass symbol can be used to represent the acceptance of a time event.

Accept Event Action is an important element for business processes in activity diagrams. Accepting action waits for an event to occur. After the event is accepted, the flow that comes from this action is executed.

Send Signal Action is a signal being sent to an accepting activity which can react accordingly.