In
UML, activities are container elements that describe the highest level of
behavior in an activity diagram. Activities contain several activity nodes
and activity edges that represent the sequence of tasks in a workflow that
result in a behavior.
An activity is composed of a series of discrete activity nodes, such as
actions, that are connected by control flows or object flows. The actions
in an activity are invoked when one of the following events occur:
- Other actions finish executing
- Objects and data become available to the action
- Events that are external to the flow occur
Each activity has a unique name that describes the purpose for the activity.
You can use activities to do the following things:
- Create organizational models of business processes where events can originate
from inside or outside the system
- Create information system models that specify the system-level processes
that occur