In this exercise, you identify the significant use cases in the PiggyBank online banking system. The use cases describe the functional tasks that the PiggyBank application performs.
The use cases define the most basic functional tasks that the users of the application perform. In the PiggyBank online banking system, customers can display the balance of their accounts and transfer money from one account to another. Only a teller can cash a check; however, the system must verify that the transaction is valid.
To create the use case diagram, you must first identify the functional area. Because all use cases are related to banking activities, the functional area is called Account Operations.
You now have a functional area. The functional area represents the most basic building block of the use case model. You can now populate the functional area with use cases.
After you identify the functional area, you can import the use cases and begin to build the use case model.
The use case model template contains an overview package called «perspective» Overviews that provides additional documentation about the model. Although this step is optional and does not impact the model, you should organize and document the actors and use cases in the PiggyBank online banking system.
You have increased the readability of this use case model by documenting the project’s significant use cases. You can add a title to the diagram by using the text tool. Your project should now look similar to the following figure:
Because this model contains only one functional area, you can remove the «ModelLibrary» Use-Case Building Blocks project from your project. You no longer need this empty package and it clutters the model hierarchy. To delete the package, right-click, then click Delete.
Now you are ready to begin Exercise 1.4: Identifying actors.