An activity diagram can be used to supplement the use case text in order to show complex iteration and selection and to get an overview of the flow of the use case. Do not, however, allow the activity diagram to replace the use case text.
![]() | Activities, in oval boxes, are named starting with an active verb |
|
|
![]() | The arrow indicates the order in which the activities occur. It is the thread of activity |
![]() | A condition, in square brackets, may be used to hold up the thread until the condition becomes true. |
![]() | If there are multiple exits from an activity, as from 'Find Customer Record, then all exit threads should have non-overlapping conditions. This indicates a switch inside the activity |
![]() | The above also applies to a decision, a diamond shape, which can be used to indicate a switch between activities |
![]() | The activity diagram must contain a 'start state' and may contain an 'end state' |