UML Diagrams Zicomi Systems publishes some UML example diagrams online from the world famous UML dictionary. more...
Version 2.5 Released Zicomi Systems is delighted to announce that version 2.5 of Zicomi Mentor is released. With support for UML 2.0 and all thirteen UML diagrams more...
Zicomi Systems' Director speaks about the UML at Objects by Design - an informative interview more...
Partner Programme Zicom Systems is delighted to announce a new world wide partner programme, become a partner today. more...
OMG Member Zicom Systems is made a member of the OMG!
Activity Final Node
An activity final node is a type of final node that stops an activity. When a token arrives at an activity final node all flows in the enclosing activity are stopped and the activity is terminated. The token arriving at the activity final node is itself destroyed. Any tokens that are offered on the incoming edges of the activity are accepted and object nodes declared as outputs are offered to the output edges of the enclosing activity.
Explanation
An activity final node is used to stop an activity. An activity typically contains a number of actions, control nodes and flows that connect them. When a token arrives at any one activity final node enclosed within the activity all flows are terminated. In our daily lives we see similar situations for instance in a ball game: if the ball goes out of bounds the referee blows the whistle and the play that is underway is stopped. There is another type of final node called a flow final node, which can be used to consume the tokens arriving at it but it does not stop the other flows in the activity.
Important Points
An activity final node cannot have outgoing flows (edges).
Since an activity final node results in the enclosing activity terminating, and it consumes the token it may not have any outgoing edges, regardless of whether they are control flows or object flows.
An enclosing activity can have any number of activity final nodes.
The activity that encloses the activity final node may have any number of activity final nodes representing different ways that the activity can terminate. The first activity final node to receives a token terminates the activity including the flows into all other final nodes, regardless of whether they are activity final or flow final nodes.
An activity final node can have any number of incoming flows.
It is possible for an activity final node to have one or more incoming flows (edges). This provides a mechanism that allows the modeler to terminate the activity in a particular way from a number of different parts of the activity.
All flows regardless of whether they are incoming or outgoing must be either all control flows or all object flows.
An activity final node is a type of control node and therefore can only manage a single type of flow. So all incoming and outgoing flows must all be of a single type: either control flows carrying control tokens, or object flows carrying data or object tokens, but not a mixture of both types of flows.
A flow final is related to an activity final as they are both final nodes used in activity and interaction overview diagrams. A flow final acts like a drain destroying all incoming tokens but it has no affect on the enclosing activity. When an activity final receives a token all flows in the enclosing activity are stopped and the activity is terminated.
An initial node is related to an activity final as they are paired elements an initial node is the point at which token flow originates and the activity final is one of two types of final nodes where token are destroyed.