In this exercise, you create the Account Operations use case diagram by modeling the relationships between the actors of the system and the use cases.
The account operations use case model describes the interactions between the actors and the use cases of the PiggyBank online banking system. In the previous exercises, you identified the use cases and actors. You can now describe the interactions of the users and the system by modeling the relationships between the actors and the use cases.
You can complete the use case diagram by modeling the relationships between the actors and the use cases. Customer is a primary actor in this use case diagram.
You have now modeled the relationships of the Customer actor in the use case diagram. The Customer actor can display the balance of an account, and can transfer money from one account into another.
You can complete the use case diagram by modeling the relationships between the actors and the use cases. Teller is a primary actor in this use case diagram.
You have now modeled the relationships of the Teller in the use case diagram. The Teller actor can display the balance of an account, can transfer money from one account into another, and can cash a check.
You can complete the use case diagram by modeling the relationships between the actors and the use cases. CityBank is a secondary actor in this use case diagram.
You have now modeled the relationships of the CityBank actor in the use case diagram. The CityBank actor is responsible for validating checks that PiggyBank customers cash. The CityBank actor is the only nonhuman actor in the diagram. Your diagram should look similar to the following figure:
The use case diagram in the figure shows the cardinalities of the relationships. Cardinalities can make simple diagrams appear cluttered. To remove the cardinalities in the diagram, right-click in the diagram editor; then click
.To continue, proceed to Exercise 1.6: Creating the Display balance activity diagram.