Use Case: UC1 - Customer Registration ........................................................................ 1 Use Case: UC2 - Banks Acceptance of Customer Registration ....................................

1 Use Case: UC3 - Login to Bank Web Site ...................................................................... 2 Use Case: UC4 - Customer Prints Cheque Deposit Slip................................................. 2 Use Case: UC5 - Bank records Cheque Deposit ............................................................. 3 Use Case: UC6 - Bill payments online ........................................................................... 4 Use Case: UC7 - Transfer funds online .......................................................................... 4

Use Case: UC1 - Customer Registration

Actors: Customer
Pre-conditions: None Post-conditions: The registration information submitted by the customer was recorded.

Flow:1. Customer visits the Bank Web Site 2. Confirms acceptance of terms 3. Customer enters personal details 4. Selects Account Type 5. Enters Initial deposit and mode of payment 6. Submits the data. 7. System asks for confirmation from Customer 8. Customer confirms 9. System records the registration information 10. System informs the customer that his registration has been submitted for approval.

Use Case: UC2 - Banks Acceptance of Customer Registration

Actors: Banker
Pre-conditions: Customers registration was on record with the system. Banker has logged in successfully Post-conditions: Customers registration information was moved into a History Log. A Customer object was created. A Credential object was created. An Account object was created. A letter with customer credentials for internet access was created. The user interface was updated.

Flow:1. 2. 3. 4. Banker navigates to page listing new Registration Applications Checks list of Registration Applications Confirms validity of documents and data Accepts Registration

5. 6. 7. 8.

System asks for confirmation from Banker Banker confirms System creates a new Customer object. System creates a new Account object from the Registration information and associates it with the Customer object. 9. System logs the Registration information into a separate History Log. 10. System generates Customer Credentials for logging onto site. 11. System prints out Customers User ID and Password along with Customer Name and Mailing Address to be sent to customer. 12. System removes the Registration from the list of Registration Applications 13. System displays the updated list on the page.

Alternate Flow:
4. Banker Rejects Registration with reasons for rejection 4.1. System records the Bankers decision 4.2. System logs the rejected Registration into a separate History Log 4.3. The use case continues at step 12.

Use Case: UC3 - Login to Bank Web Site

Actors: User (Customer, Banker)
Pre-conditions: None Post-conditions: The User was taken to his Home Page

Flow:1. User enters UserId and Password 2. System verifies the same 3. System grants access and takes User to his Home Page.

Alternate Flow:
2. System fails to verify the User 2.1. The User returns to step 1 and gets another 2 tries before the system locks the account.

Use Case: UC4 - Customer Prints Cheque Deposit Slip

Actors: Customer
Pre-conditions: Customer has logged in successfully. Post-conditions: The system recorded the Cheque Deposit Slip. A soft copy of the cheque deposit slip was saved to the customers machine.

Flow:1. 2. 3. 4. 5. 6. 7. Customer navigates to the page for Bank Deposit Slips. Customer fills in bank deposit slip online System fills in the Status as Not Received Customer submits System asks for confirmation from Customer Customer confirms System records the slip and allows the customer to save it for printing on the Customers machine. 8. Customer mails cheque with slip attached to bank.

Use Case: UC5 - Bank records Cheque Deposit

Actors: Banker
Pre-conditions: The system has a record of the Cheque Deposit Slip online. Banker has logged in successfully. Post-conditions: The status of the Cheque Deposit Slip was set. The balance of the customers account was updated. The User Interface was updated.

Flow:1. 2. 3. 4. 5. 6. 7. 8. 9. Banker navigates to page to View Deposit Slips Views list of Online Slips Physically verifies Cheque/Slip received by mail with that on the site Changes the Status to Sent For Clearance Sends cheque for clearance System records the status Cheque is cleared. Banker navigates to the page again. Banker selects the deposit slip and sets the Status to Cleared and asks the system to update the customers Balance. 10. System asks for confirmation 11. Banker confirms 12. System records the information and returns Banker to updated Online Slips page.

Alternate Flow:
7. Cheque returns bounced. 7.1. Banker sets the status to Bounced and asks the system to levy the applicable fine. 7.2. Use case continues at step 10.

Use Case: UC6 - Bill payments online

Actors: Customer
Pre-conditions: Customer has logged in successfully. Post-conditions: The Bill Payment transaction was recorded. The customers account was debited. The vendors account was credited.

Flow:4. Customer logs into Bank Site 5. Navigates to page for Bill Payments 6. Customer enters details of the bill to be paid (vendor, bill number, date, amount) 7. Customer selects Immediate payment method 8. Submits 9. System asks for confirmation from Customer 10. Customer confirms 11. Systems debits customer account and credits vendor 12. System informs customer that the payment has been made.

Alternate Flow:
7. Customer selects Scheduled payment method 7.1. System records the transaction for execution on the scheduled day. 7.2. System informs customer that the Bill Payment has been scheduled. 11. System detects that the account has insufficient funds 11.1. System displays a status message to the customer 11.2. The customer is returned to the Bill Payments page.

Use Case: UC7 - Transfer funds online

Actors: Customer
Pre-conditions: Customer has logged in successfully. Post-conditions: The Transfer transaction was successfully recorded. The Customers account was debited. The Transferees account was credited.

Flow:1. 2. 3. 4. 5. 6. 7. Customer logs into Bank Site Enters Account No. to transfer to Enters amount to transfer Submits System asks for confirmation from Customer Customer confirms System effects the transfer transaction

Alternate Flow:
7a. System detects that the account has insufficient funds 7.1. System displays the status message to the customer 7.2. The customer is returned to the Bill Payments page. 7b. The Transferees account does not exist. 7.1. The system informs the customer of the invalid account no. and doesnt effect any changes.