IBM WebSphere Multichannel Bank Transformation Toolkit, Version 7.1

Use cases

The following information applies to the Multi-Channel Sample Application, and was used to develop use cases:

Actors: Customer, User, Application.

Context: 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 their accounts.

Trigger request: The customer request.

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

Overview:
  1. The user asks the customers for their identifiers.
  2. The customers provide their identifiers.
  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 host 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 host 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 host transaction. When the operation is complete, the results are displayed.
The following use cases were developed from the information:
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. Calls the Dummy Journal service with the formatted data.
  4. Collects the data to be sent to the host.
  5. Sends the data to the host.
  6. Gets the result of the submitted host transaction.
  7. Unformat the received data in the operation context.
  8. Calls the Dummy Journal service with the formatted data.
  9. 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 Electronic Journal.
  5. Calls the Electronic Journal service with the formatted data.
  6. Collects the data to be sent to the host.
  7. Gets the result of the submitted host transaction.
  8. Unformats the received data in the operation context.
  9. Collects and formats the data to update the Electronic Journal.
  10. Calls the 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 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 Electronic Journal.
  2. Calls the Electronic Journal service with the formatted data.
  3. Collects the data to be sent to the host.
  4. Gets the result of the submitted host transaction.
  5. Unformats the received data in the operation context.
  6. Collects and formats the data to update the Electronic Journal.
  7. Calls the 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


Feedback