In this exercise, you create the Display Balance activity diagram. The display balance activity diagram shows the internal flow of events when a customer or teller displays the balance of an account.
Use case diagrams show behaviors, and identify the actors and functions of a system, but they do not show any temporal information such as workflows or processes. Activity diagrams are the UML equivalent of a flowchart, as they show the temporal order of events in a larger process. An activity diagram describes the flow of events that occur in a use case.
The Display Balance activity diagram describes the workflow of displaying the balance in a given account. The customer and the teller can both perform this task. The CityBank actor, which is really a system, validates the transaction.
The Display Balance activity diagram models the steps that occur when the user clicks the Display Balance item on the main menu. This procedure describes how to create the Customer/Teller activity partition.
You have now modeled the workflow of the Customer/Teller activity. Your diagram should look similar to the following figure:
The Display Balance activity diagram models the steps that occur when the user clicks the Display Balance item on the main menu. This procedure describes how to create the System activity partition.
You have now created the Display Balance activity diagram. Your diagram should look similar to the following figure:
The Display Balance activity diagram uses two activity partitions to show the simple workflows that occur when the user clicks Display Balance from the main menu.
You can insert a link to this diagram in the Account Operations use case diagram. This link can increase the readability of the model by enabling you to navigate between associated diagrams.
To continue, proceed to Exercise 1.7: Creating the Transfer Money activity diagram.