In this exercise, you identify the actors of the system. The account operations use case diagram identifies the key actors and the roles that they perform in the system. You must identify all actors before you can create the diagram.
You should understand who the users of the system are before you begin to model it. In a use case diagram, users of the system are depicted as actors. Each actor performs a specific role in the system, called a use case. More than one actor can perform a single use case. An actor can be a person, such as a customer, or a computer, such as a database system or server.
The users of the system are depicted as actors. You must identify all the actors in the system before you create the use case diagram.
You have now organized the use case diagram according
to proper Rational® UML
model structure guidelines. The prime actor appears in the top
left corner of the diagram and the most important use case appears
above all other use cases. The secondary use case, CityBank, appears
to the left of the use cases. Your diagram should look similar to
the following figure:
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 now increased the readiability of this use case model by documenting the project’s significant actors. You can add a title to the diagram by using the text tool. Also note that the use case template contains a Versatile Actors package for documenting all actors that participate in multiple functional areas. Because this model contains no versatile actors, you can delete this package by right-clicking it; then clicking Delete from Model.
To continue, proceed to Exercise 1.5: Creating the Account Operations use case diagram.