Use cases

The following information applies to the Java(TM) Client Sample Application, and was used to develop use cases:

Actors: Customer, User, Application.

Context: A customer asks a bank teller (the user) to perform a cash transaction from a personal account and the bank teller also wants to view the recent statements for one of his accounts.

Trigger request: The customer request.

Assumptions: The user has signed onto the system, and has access to the required processes in a graphical interface context.

Overview:

  1. The user asks the customer for his identifier.
  2. The customer provides his identifier.
  3. The user starts the operation to verify the identity of the customer, and enters the customer identifier into the system.
  4. The application submits the corresponding backend system transaction, which validates the customer identifier and gets the customer's information.
  5. The application displays the customer information, and remains prepared for accepting new orders.
  6. The customer requests a cash transaction, and specifies the account number, the amount, and the type of operation (withdrawal or deposit).
  7. The user enters this input data into the application.
  8. The application submits the corresponding backend system transaction, which executes the business operation. When it completes, the result is displayed.
  9. The customer now asks for statement information and provides the necessary data. The user enters the data into the application, and submits the backend system transaction. When the operation is complete, the results are displayed.
  10. All submitted backend system transactions are recorded in an electronic journal, with entries that include both the request and the reply messages.

The following use cases were developed from the information above:

Table 1. List of use cases for the sample
Step Actor Action
1 User Starts the customerSearchClientOp operation.
2 Application Displays a view asking the user for the customer identifier.
3 User Enters the customer identifier and launches the customerSearchClientOp operation.
4 Application
  1. Performs syntactic validations of entered data.
  2. Performs semantic validations of entered data.
  3. Collects and formats the data to be stored in the Electronic Journal.
  4. Calls the dummy Electronic Journal service with the formatted data.
  5. Collects the data to be sent to the backend system.
  6. Sends the data to the backend system.
  7. Gets the result of the submitted backend system transaction.
  8. Unformats the received data in the operation context.
  9. Collects and formats the data to update the dummy Electronic Journal.
  10. Calls the dummy Electronic Journal service with the formatted data.
  11. Opens a new view that displays the result of the operation with the following customer information:
    • Account number list
    • Customer name
5 Application Asks the user for the following information:
  • Account number (select one from the list)
  • Amount
  • Operation type (withdrawal or deposit)
6 User Selects an account from the list, enters the amount, selects the operation to be executed, and starts execution.
7 Application
  1. Performs syntactic validations of entered data.
  2. Performs semantic validations of entered data.
  3. Maps the input data from the view to the operation.
  4. Collects and formats the data to be stored in the dummy Electronic Journal.
  5. Calls the dummy Electronic Journal service with the formatted data.
  6. Collects the data to be sent to the backend system.
  7. Gets the result of the submitted backend system transaction.
  8. Unformats the received data in the operation context.
  9. Collects and formats the data to update the dummy Electronic Journal.
  10. Calls the dummy Electronic Journal service with the formatted data.
  11. Maps the output data to the view.
  12. Displays the result of the operation, with the account balance.
8 Customer Asks to check the last statements on his account.
9 User Selects an account and launches the execution of the operation Account Statement.
10 Application
  1. Collects and formats the data to be stored in the dummy Electronic Journal.
  2. Calls the dummy Electronic Journal service with the formatted data.
  3. Collects the data to be sent to the backend system.
  4. Gets the result of the submitted backend system transaction.
  5. Unformats the received data in the operation context.
  6. Collects and formats the data to update the dummy Electronic Journal.
  7. Calls the dummy Electronic Journal service with the formatted data.
  8. Displays the result of the operation in a new view, which presents a list with the following fields:
    • Date
    • Operation description
    • Amount
    • Account balance