use cases for inb

7/31/2019 Use Cases for iNB

1/5

Use Case: UC1 - Customer Registration ........................................................................ 1

Use Case: UC2 - Banks Acceptance of Customer Registration .................................... 1Use 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 ........................................................................... 4Use Case: UC7 - Transfer funds online .......................................................................... 4

Use Case: UC1 - Customer Registration

Actors: Customer

Pre-conditions: NonePost-conditions: The registration information submitted by the customer was recorded.

Flow:-1. Customer visits the Bank Web Site2. Confirms acceptance of terms3. Customer enters personal details4. Selects Account Type5. Enters Initial deposit and mode of payment6. Submits the data.7. System asks for confirmation from Customer8. Customer confirms9. System records the registration information10.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. Banker navigates to page listing new Registration Applications2. Checks list of Registration Applications3. Confirms validity of documents and data4. Accepts Registration


2/5

5. System asks for confirmation from Banker6. Banker confirms7. System creates a new Customer object.8. 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 Applications13.System displays the updated list on the page.

Alternate Flow:

4. Banker Rejects Registration with reasons for rejection4.1.System records the Bankers decision4.2.System logs the rejected Registration into a separate History Log4.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 Password2. System verifies the same3. System grants access and takes User to his Home Page.

Alternate Flow:

2. System fails to verify the User2.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 customersmachine.


3/5

Flow:-

1. Customer navigates to the page for Bank Deposit Slips.2. Customer fills in bank deposit slip online3. System fills in the Status as Not Received4. Customer submits5. System asks for confirmation from Customer6. Customer confirms7. 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. Banker navigates to page to View Deposit Slips2. Views list of Online Slips3. Physically verifies Cheque/Slip received by mail with that on the site4. Changes the Status to Sent For Clearance5. Sends cheque for clearance6. System records the status7. Cheque is cleared.8. Banker navigates to the page again.9. Banker selects the deposit slip and sets the Status to Cleared and asks the system

to update the customers Balance.

10.System asks for confirmation11.Banker confirms12.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.


4/5


5/5

Alternate Flow:

7a.System detects that the account has insufficient funds7.1.System displays the status message to the customer7.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 effectany changes.

use cases for inb

Documents