- Overview
- Elements of an activity diagram
An activity diagram represents the behavior of a method or the flow of a use case. For example, the following diagram presents the flow of a dam:
Elements of an activity diagram An activity diagram includes the following elements: - activity: represents a specific step in a workflow. For example: "Create a quote", "Open a window", "Evaluate", etc.
- synchronization bar: synchronizes different activities:
- by indicating the activities that must be performed before a given activity. For example: "Press clutch" and "Change gear" before "Release clutch".
- by indicating the activities that will happen in parallel.
- object: relates activities to the object that performs them. For example, the "Order" and "Pay" activities are related to the "Customer" object; the "Teach" and "Evaluate" activities are related to the "Teacher" object.
- send signal: represents a signal sent to an object.
- accept event: represents the acceptance of an event coming from an object.
- transition: shows the passage from a terminated activity to another activity. For example: "Too much water", "Enough money", etc.
- package: divides and organizes the diagram representation (in the same way that directories organize files).
- initial state: represents the status of the process before the activity starts. Several different initial states can be found.
- final state: represents the state of the process at the end of the activity. Several different final states can be found.
For more details on the actions available on activity diagrams, see Operations performed on activity diagrams.
This page is also available for…
|
|
|
|