Business Analyst Collect requirements with interaction of client.The collected Information will be Documented as BRS (Business Requirement Specification Or URS (User Requirement Specification) OR CRS (Customer Requirement Specification )

BRS is the First document prepared in SDLC Phase . Here is a real time Test cases created from FRS.
This document will be quoted with Brief description of client business needs Like USERS, TYPE OF USERS, User Permissions, SERVICES. After preparation of BRS doc Business Analyst will do/make Feasibility Study in Order to check whether project is Acceptable. If Project is Accepted Business Analyst will provide Intimation to client and Agreement will be made .

....................sample of BRS........................

E-Banking

Business Requirements Specifications v1.0

Document Name	Version Number	Start Date	Prepared By	Reviewed By	Modified Date	Present Status
BRS-Bank/Rel1.0	1.0	mm/dd/yy	xxxx	xxxxx	mm/dd/yy	Completed

Introduction:

Bank UK is a full service bank offering retail and corporate and investment banking services in the UK and Europe. The Bank delivers its products and services through five branches located in the UK and one branch in Antwerp, Belgium as well as through Internet and telephone banking. The Bank was incorporated in England and Wales on 11 February 2003 as a private company with the name Bank UK Ltd. and on 30 October 2006 converted to being a public limited company. The Bank's registered office is 21 Knightsbridge, London SW1X 7LY. The Bank is regulated by the Financial Services Authority (the FSA) and is a member of the Financial Services Compensation Scheme established under the Financial Services and Markets Act 2000. The Bank has a long-term foreign currency credit rating of Baa1 from Moody's, which is one notch higher than the UK sovereign rating.

About Bank

As at 30 September 2006, the Parent is UK's largest bank in the private sector with total consolidated assets of approximately US$ 61.5 billion and is the second largest company in UK including all public and private enterprises. The Parent and its subsidiaries offer not only comprehensive banking services in UK, but also life insurance, general insurance, asset management, investment banking and private equity/venture capital. The Parent has a presence, through its subsidiaries, branches and representative offices, in 16 countries in North America, the UK and Continental Europe, the Middle East, South Africa, South Asia and Hong Kong. In 2000, the Parent was the first UK banking company and the second bank from Asia to list on the New York Stock Exchange and currently has a financial strength rating of C- from Moody's Investors Service Limited (Moody's) and a long-term foreign currency credit rating of Baa2 from Moody's and BB+ from Standard & Poor's.

Bank is UK's foremost technology bank and has pioneered Internet banking in UK.

KeyMouze Systems will design and develop the following key business modules:

Bank is a web based and offers a full service such as personal, corporate and International Banking Services in the UK and Europe. The Bank delivers its products and services through five branches located in the UK and one branch in Antwerp, Belgium as well as through Internet.

The system would involve the following modules Admin, Banker, Personal, Corporate and International Banking Services But as part of the first release we would only concentrate on the following features.

Admin Tasks, Banker Tasks and Customer Tasks for personal banking.

Admin

Admin Tasks:

This module allows admin to define and manage master data such as Branches, Roles, Users and Employee of the Bank.

1.0 Branches:

Branches Feature allows admin to define a new branch for Bank and also he can modify or delete any Bank branches.

2.0 Roles

Roles feature allows admin to define a new role for Bank and also he can modify or delete any Bank roles.

3.0 Users:

Users feature allows admin to define a new user for any Bank customers. He can modify or delete any user information.

4.0 Employees:

Employees feature allows admin to define a new employee basic information for any Bank branch. He can modify or delete any employee information.

Banker

Banker’s Tasks

This module allows bankers to define and manage customers of his branch and also he can book receipts and payments.

5.0 Customers Registration

Customers feature allows him to define a new customer for his branch by filling registration form and sending it for the admin approval, and also he can modify or delete or view any customer information.

6.0 Receipts

Receipts feature allows him to book different kind of deposits from a customer such as cash deposits, cheque deposits, DD deposits and credit card payments etc.,

7.0 Payments

Payment feature allows him to book different payments made to customers such as Cash withdrawal, Cash withdrawal through cheques etc.

Customer

Personal Banking Customers Tasks

This Module allows the registered users to perform various activities such as Accounts Summary, Money Transfer, Smart Money Order, Online bill payments and Online request for cheque book etc.,

For present release only the mentioned key features only be constructed and the remaining features would be included in the upcoming releases.

8.0 Accounts Summary:

This feature should enable the user to generate their account summary reports, generating mini statements and detailed account statement for the specified period.

9.0 Money Transfer:

With , Transferring funds from your Bank Account is very simple. There are various options provided online for transferring funds.

With Funds Transfer on Bank, you can

Forget about writing out & sending cheques/ DD's or pay orders to the payee.

Free yourself from the worry of payment instruments getting lost/misplaced in transit.

Transact from the comfort of your home or office through Bank Internet Banking.

Transfer money to any Bank account, anywhere in UK.

Transfer money to specified non- Bank Accounts in over 100 cities across UK.

ECheques facility on Bank.com is absolutely free of charge.

10.0 Smart Money Order:

Smart Money Order is a unique service that allows you to send a money order anytime and to any destination in UK.

Sending a Smart Money Order is very simple. Just login to IBank.com and give the address of the person (receiver) and amount of money to be sent. You can then sit back & relax while your near & dear ones receive money conveniently at their door-step.

11.0 Bills Pay

Bank has tied up with major organizations across the country to facilitate payment of bills for Utility Companies (Electricity and Telephone) Bills, Bank credit card, Mobile Phone and Insurance Premium bills.

To pay your bills, all you need to do is complete a simple one time registration for each biller. You can also set up standing instructions online to pay your recurring bills, automatically.

12.0 Request for Cheque Book:

This feature allows the valid user to place an online checkbook request.

High Level Business Requirements:

Access banking, 24 hours a day, 7 days a week from anywhere in the world;
View balances of accounts and transaction history;
Transfer funds between own accounts;
Transfer funds to any other bank account
Ability to pay utility bills
Printout and export transaction history to own computer;
Request overseas payments (telegraphic transfers);
Send and receive messages to and from the Bank;

Security features which allow businesses to designate initiator users and authoriser users.

....................................................................................................................................................................FRS sample...

E-Banking_Admin_FRS v1.0

Document Name	Version Number	Start Date	Prepared By	Reviewed By	Modified Date	Present Status
FRS-Admin/Rel1.0	1.0	Mm/dd/yy	xxxxx	xxxxx	Mm/dd/yy	Completed

1.0 Home Page

1.1.0 Overview

Home page allows different users such as admin, bank employee, various customers (Individual customers, corporate customers, International Customers) to login and access the application for further usage and also it provides information about various services offered by Bank.

1.2.0 Prototype

Home Page

1.3.0 Page Elements

Home Page

Element Name	Element Type	User Action	System Response
Home	Button	Click	As per task flow diagram
Personal Banking	Button	Click	As per task flow diagram
Corporate Banking	Button	Click	As per task flow diagram
International Banking	Button	Click	As per task flow diagram
About Us	Button	Click	As per task flow diagram

Customer Login
Personal	Button	Click	As per task flow diagram
Corporate	Button	Click	As per task flow diagram
International	Button	Click	As per task flow diagram

Banker Login
Branch Name	Combo box	Select	System should accept
User Name	Textbox	Enter	System should accept
Password	Textbox	Enter	System should accept
Login	Link	Click	As per task flow diagram

User information Links
Customer Service	Link	Click	As per task flow diagram
Internet Banking FAQ’s	Link	Click	As per task flow diagram
Privacy	Link	Click	As per task flow diagram
Terms and Conditions	Link	Click	As per task flow diagram
Disclaimer	Link	Click	As per task flow diagram
Site map	Link	Click	As per task flow diagram
News	Scrolling Text	NA	NA

1.4.0 Input Validations & Error States

Element Name	Valid Data	Error state
User Name	1. Mandatory.	1. Blank/Invalid- “Enter a Valid User Name”
Password	1. Mandatory.	1. Blank/Invalid- “Enter valid password”
IF User login failed then System Should display a pop that Incorrect User Name / Password.

1.5.0 Task flow Diagram

1.5.1 Visitor Flow

1.6.0 Use Cases

1.6.1 Visitor Process flow in Home Page

Actors Action	System Response
1. Actor Enters Valid URL	2. System displays home page with login facility.
3. Actor clicks Home	4. System displays home page with login facility.
5. Actor clicks Personal Banking	6. System displays information and services offered for Personal banking.
7. Actor clicks Corporate Banking	8. System displays information and services offered for Corporate banking
9. Actor clicks International Banking	10. System displays information and services offered for International Banking.
11. Actor clicks About Us	12. System displays information about Bank.
13. Actor clicks Customer Service	14. System displays Customer Service information.
15. Actor clicks Internet Banking FAQ’s	16. System displays the information about internet banking FAQ’s.
17. Actor clicks Privacy	18. System displays Privacy commitment of Bank.
19. Actor clicks Terms & Conditions	20. System displays information about online banking terms and conditions.
21. Actor clicks Disclaimer	22. System displays the notice and copyrights of this site.
23. Actor clicks site map	24. System displays site map about this site.

1.6.2 Admin Process flow in Home Page

Actors Action	System Response
1. Actor Enters Valid URL	2. System displays home page with login facility.
3. Actor enters valid user name	4. System will accept.
5. Actor enters valid password	6. System will accept.
7. Actor clicks Login	8. System displays Admin module.

1.6.3 Customer Process flow in Home Page

Actors Action	System Response
1. Actor Enters Valid URL	2. System displays home page with login facility.
3. Actor clicks Personal	4. System displays login page for personal banking
5..Actor clicks Corporate	6. System displays login page for Corporate banking
7.Actor clicks International	8.System displays login page for International banking

1.6.4 Banker Process flow in Home Page

Actors Action	System Response
1. Actor Enters Valid URL	2. System displays home page with login facility.
3. Actor selects respective branch	4. System display the selected branch
5. Actor enters valid user name	6. System will accept.
7. Actor enters valid password	8. System will accept.
9. Actor clicks Login	10. System displays Banker module.

2.0 Admin Home Page

2.1.0 Overview

This page allows administrator to define and manage master data such as Branches, Roles , Users and Employees related to Bank.

2.2.0 Prototype

Admin Home Page

2.3.0 Page Elements

Element Name	Element Type	User Action	System Response
Branches	Button	Click	As per task flow diagram
Roles	Button	Click	As per task flow diagram
Users	Button	Click	As per task flow diagram
Employees	Button	Click	As per task flow diagram
Home	Button	Click	As per task flow diagram
Change Password	Button	Click	As per task flow diagram
Logout	Button	Click	As per task flow diagram

2.4.0 Input Validations & Error States

2.5.0 Admin Task flow diagram

2.6.0 Use Cases

Actors Action	System Response
1. Actor clicks Branches	2. System displays Branches details page.
3. Actor clicks Roles	4. System displays Roles details page
5. Actor clicks Users	6. System displays User details page.
7. Actor clicks Employees	8. System displays Employees details page.
9. Actor clicks Home	10. System displays Admin Home Page
11. Actor clicks Change Password	12. System displays Change Password page.
13. Actor clicks Logout	14. Current session will be closed and system displays Home Page.

3.0 Branches

3.1 Branches Details

3.1.1 Overview

Branches Feature allows admin to define a new branch, modify or delete any branches and also admin can search for branches information based on the given selection criteria.

3.1.2 Prototype

3.1.3 Page Elements

Element Name	Element Type	User Action	System Response
Country	List box	Select	As per use cases.
State	List box	Select	As per use cases.
City	List box	Select	As per use cases.
Search	Button	Click	As per use cases
Clear	Button	Click	As per use cases
New Branch	Button	Click	As per task flow diagram
Branches Details Table
Branch Id	Tab. element	NA	NA
Branch Name	Tab. element	NA	NA
Address	Tab. element	NA	NA
Area	Tab. element	NA	NA
City	Tab. element	NA	NA
State	Tab. element	NA	NA
Edit	Image Link	Click	As per task flow diagram
Delete	Image Link	Click	As per task flow diagram

3.1.4 Input Validations & Error States

3.1.5 Task flow diagram for Search and clear

3.1.6 Admin flow for Search and Clear.

Actors Action	System Response
1. Actor login	2.System displays Admin module
3. Actor clicks Branches	4. System displays branches details page.
5. Actor selects required criteria of Country/State/City and clicks Search.	6. System displays only the branches matching the selected criteria.
7. Actor clicks Clear.	8. System clears the given search criteria and all branches will be displayed.

3.2 New Branch Creation

3.2.1 Overview

This feature allows Admin to create a new branch for Bank.

3.2.2 Prototype

3.2.3 Page Elements

Element Name	Element Type	User Action	System Response
Branch Name	Text box	Enter/Edit	As per task flow diagram
Address1	Text box	Enter/Edit	System should accept
Address2	Text box	Enter/Edit	System should accept
Address3	Text box	Enter/Edit	System should accept
Area	Text box	Enter/Edit	System should accept
Zip code	Text box	Enter/Edit	System should accept
Country	List box	Select	As per Use cases
State	List box	Select	As per Use cases
City	List box	Select	As per Use cases
Submit	Button	Click	As per task flow diagram
Reset	Button	Click	As per task flow diagram
Cancel	Button	Click	As per task flow diagram

3.2.4 Input Validations & Error States

Element Name	Valid Data	Error state
Branch Name	1. Alphanumeric only 2. Start with alphabet 3. Min of 6 Chars 4. Max of 40 Chars 5. Mandatory 6. Unique	1. Blank – “Please fill in the following fields – Branch Name” 2. Invalid Chars- “This field should be alphanumeric starts with an alphabet” 3. Invalid Range- “This field should be with in 6 - 40 chars range. 4. Duplicate- “This branch already exists”
Address1	1. Alphanumeric and special Chars. 2.Mandatory 3. Min of 4 chars. 4. Max of 50 chars.	1. Blank – “Please fill in the following fields – Address1” 2. Invalid Range- “This field should be with in 4 - 50 chars range.
Address2	1. Alphanumeric and special Chars. 2. Max of 50 Chars.	1. Invalid Length- “This field accepts a maximum of 50 Chars.
Address3	1. Alphanumeric and special Chars. 2. Max of 50 Chars.	1. Invalid Length- “This field accepts a maximum of 50 Chars.
Area	1. Alphanumeric and special Chars. 2. Should start with alphabet. 3. Max of 50 Chars.	1. Invalid Length- “This field accepts a maximum of 50 Chars.
Zip	1. Numeric Only 2. It should be 5 Chars 3. Mandatory	1. Blank – “Please fill in the following fields – Zip” 2. Invalid Chars- “This field should be numeric” 3. Invalid Range- “It should be 5 chars in length”
Country	1. Mandatory	1. Blank – “Please fill in the following fields – Country”
State	1. Mandatory	1. Blank – “Please fill in the following fields – State”
City	1. Mandatory	1. Blank – “Please fill in the following fields – City”

3.2.5 Task flow diagram

3.2.6 Use Cases

Admin flow for Addition of New Branch.

Actors Action	System Response
1. Actor login	2.System displays Admin module
3. Actor select Branches	4. System displays branches details page.
5. Actor click New Branch	6. System displays New branch Entry Page.
7. Actor Enters necessary fields with valid data and clicks Submit.	8. System displays a message “New Branch Created successfully with Branch ID” with “Ok” Button
9. Actor enters necessary fields with valid data and clicks Reset.	10. System clears all fields.
11. actor enters necessary fields with valid data or with out entering any fields clicks Cancel.	12. System closes the new branch entry page and displays branches details page.

Admin flow for Addition of New Branch.

Actors Action	System Response
1. Actor login	2.System displays Admin module
3. Actor select Branches	4. System displays branches details page.
5. Actor click New Branch	6. System displays New branch Entry Page.
7. Actor Enters necessary fields with valid data and clicks Submit.	8. System displays a message “New Branch Created successfully with Branch ID” with “Ok” Button
9. Actor enters necessary fields with valid data and clicks Reset.	10. System clears all fields.
11. ACTOR Enters necessary fields with valid data or with out entering any fields clicks Cancel.	12. System closes the new branch entry page and displays branches details page.

3.3 Branch Updation

3.3.1 Overview

This feature allows Admin to modify the details of a branch.

3.3.2 Prototype

3.3.3 Page Elements

Element Name	Element Type	User Action	System Response
Branch Id	Auto Display	NA	NA
Branch Name	Text box	Enter/Edit	As per task flow diagram
Address1	Text box	Enter/Edit	System should accept
Address2	Text box	Enter/Edit	System should accept
Address3	Text box	Enter/Edit	System should accept
Area	Text box	Enter/Edit	System should accept
Zip code	Text box	Enter/Edit	System should accept
Country	List box	Select	As per Use cases
State	List box	Select	As per Use cases
City	List box	Select	As per Use cases
Update	Button	Click	As per task flow diagram
Cancel	Button	Click	As per task flow diagram

3.3.4 Input Validations & Error States

Refer 3.2.3

3.3.6 Use Cases

Admin flow for modification of Branch.

Actors Action	System Response
1. Actor login	2.System displays Admin module
3. Actor select Branches	4. System displays branches details page.
5. Actor click edit for any branch	6. System displays branch updation page.
7. Actor modifies necessary fields with valid data and clicks Update.	8. System displays a message “New Branch Updated successfully”
9. Actor modifies necessary fields with valid data or with out modifying any fields clicks Cancel.	12. System closes the branch updation page and displays branches details page.

3.4 Branch Deletion

3.4.0 Overview

This feature is useful for Admin to delete an unwanted branch

3.4.1 Task flow Diagram

3.3.5 Use Cases

Admin flow for Deletion of Branch.

Actors Action	System Response
1. Actor login	2.System displays Admin module
3. Actor select Branches	4.System displays branches details page.
5. Actor click Delete for any branch	6. System displays a confirmation “Are you sure you want to delete this record?” with “Ok” and “Cancel” buttons.
7. Actor click “ok” button	8.1 System Deletes Selected Branch (if there is no dependency) and displays ”Branch Deleted Successfully” message 8.2 If dependency exists, system will not allow to delete and displays a message “its a shared record cannot be deleted”
9. Actor clicks Cancel.	12. System closes the branch Deletion page and displays branches details page.

4.0 Roles

4.1 Roles Details Page

4.1.1Overview

This Page displays all existing roles and allows admin to create a new Role, modify and delete a Role

4.1.2Prototype

4.1.3Page Elements

Element Name	Element Type	User Action	System Response
Roles Details Table
Role Id	Tab. element	NA	NA
Role Name	Tab. element	NA	NA
Role Description	Tab. element	NA	NA
Edit	Image link	Click	As per Task flow Diagram
Delete	Image Link	Click	As per Task flow Diagram
New Role	Button	Click	As per Task flow Diagram

4.2 New Role Creation.

4.2.1Overview

This feature allows admin to create a New Role.

4.2.2Prototype

4.2.3Page Elements

Element Name	Element Type	User Action	System Response
Role Name	Text box	Enter/Edit	System should Accept
Role Description	Text box	Enter/Edit	System should Accept
Role Type	List box	Select	System should display the selected Role type.
Submit	Button	Click	As per task flow diagram
Reset	Button	Click	As per task flow diagram
Cancel	Button	Click	As per task flow diagram

4.2.4Input Validations & Error States

Element Name	Valid Data	Error state
Role Name	1. Mandatory 2. Alphabets Only. 3.Min of 4 Chars Max of 30 Chars 4. Unique	1.Blank – “Please fill in the following fields – Role Name” 2. Invalid Chars- “This field should be alphabets only” 3. Invalid Range- “It should be with in 4 – 30 chars in length” 4. Duplicate- “This Role already exists”
Role Description	1. Alphanumeric and special Chars. 2. Max of 50 chars.	1.Invalid Range- “This Field should be max of 50 chars.
RoleType	1. Mandatory	1. Blank – “Please fill in the following fields – Role type”

4.2.5 Task flow Diagram

4.2.6Use Cases

Admin flow for Addition of New Role.

Actors Action	System Response
1. Actor login	2.System displays Admin module
3. Actor select Roles	4. System displays Roles details page.
5. Actor click New Roles	6. System displays New Role Entry Page.
7. Enter necessary fields with valid data and clicks Submit.	8. System displays a message “New Role Created successfully with Role Id”
9. Enters necessary fields with valid data and clicks Reset.	10. System clears all fields.
11. Enters necessary fields with valid data or with out entering any fields clicks Cancel.	12. System closes the new role entry page and displays roles details page.

4.3 Role Updation

4.3.1 Overview

This feature allows admin to modify an existing Role.

4.3.2 Prototype

4.3.3 Page Elements

Element Name	Element Type	User Action	System Response
Role Id	Auto Display	NA	NA
Role Name	Text box	Enter/Edit	System should Accept
Role Description	Text box	Enter/Edit	System should Accept
Role Type	List box	Select	System should display the selected Role type.
Update	Button	Click	As per task flow diagram
Cancel	Button	Click	As per task flow diagram

4.3.4 Input Validations & Error States

Refer 4.2.4

4.3.5 Task flow Diagram

4.3.6 Use Cases

Admin flow for Edit of Existing Role Information.

Actors Action	System Response
1. Actor login	2.System displays Admin module
3. Actor select Roles	4. System displays Roles details page.
5. Actor click edit on the respective role to be edited	6. System displays Roles Update Page.
7. Update necessary fields with valid data and clicks Update.	8. System displays a message “Roles Updated Successfully”
9. Update necessary fields with valid data or with out entering any fields clicks Cancel.	10. System closes the Update role page and displays roles details page.

4. 4.0 Role Deletion

4.4.1 Overview

This feature allows admin to delete an unwanted role.

4.4.3 Use Cases

Admin flow for Deletion of Existing Role.

Actors Action	System Response
1. Actor login	2.System displays Admin module
3. Actor select Roles	4. System displays Roles details page.
5. Actor click Delete on the respective role to be deleted.	6. System displays a message “Are you sure you want to delete this record”
7. Actor Click Ok	8. System displays a message “Deletion Successful”
9. Actor Click cancel	10.System stops the process

5.0 Users

5.1 Users Details Page.

5.1.1 Overview

This page displays all users’ information and also allows admin to define and manage bank users.

5.1.2 Prototype

5.1.3 Page Elements

Element Name	Element Type	User Action	System Response
Branch	List box	Select	As per use cases.
Roles	List box	Select	As per use cases.
Search	Button	Click	As per Task flow Diagram
Clear	Button	Click	As per Task flow Diagram
New User	Button	Click	As per task flow diagram
Users Details Table
User Id	Tab. Element	NA	NA
User Name	Tab. Element	NA	NA
Role Name	Tab. Element	NA	NA
Branch name	Tab. Element	NA	NA
Edit	Image Link	Click	As per task flow diagram
Delete	Image Link	Click	As per task flow diagram

5.2 New User Creation

5.2.1 Overview

This feature allows admin to create a new user for Bank. The new user id is created for the existing customers. To create new user any customer should exist.

5.2.2 Prototype

5.2.3 Page Elements

Element Name	Element Type	User Action	System Response
User Name	Text box	Enter/ Edit	System should accept
Login Password	Text box	Enter/ Edit	System should accept
Transaction Password	Text box	Enter/ Edit	System should accept
Branch	List box	Select	Should display the selected branch
Role	List box	Select	Should display the selected role.
Customer Id	List box	Select	Should display Customer ID’s depending on selection of Role And branch.
Customer Name	Text Box	Auto Display	System displays customer name for the selected customer Id
Submit	Button	Click	As per task flow Diagram.
Reset	Button	Click	As per task flow Diagram.
Cancel	Button	Click	As per task flow Diagram.

5.2.4 input Validations

Element Name	Valid Data	Error state
User Name	1. Alphanumeric only. 2. Start with an Alphabet. 3. Min of 4 Chars. 4. Max of 16 Chars. 5. Mandatory. 6. Unique	1. Blank - “Please fill in the following fields – User Name” 2.Invalid Chars- “This field should be alphanumeric only” 3.Invalid Range- “It should be with in 4 - 16 chars in length”
Login Password	1. Alphanumeric and Special Chars. 2. Min of 4 Chars. 3. Max of 16 Chars. 4. Mandatory.	1. Blank - “Please fill in the following fields – Login Password” 2.Invalid Range- “It should be with in 4 - 16 chars in length”
Transaction Password	1. Alphanumeric and Special Chars. 2. Min of 4 Chars. 3. Max of 16 Chars. 4. Mandatory.	1. Blank - “Please fill in the following fields – Transaction Password” 2.Invalid Range- “It should be with in 4 - 16 chars in length”
RoleType	1. Mandatory	1. Blank – “Please fill in the following fields – Role type”
Branch	1. Mandatory	1. Blank – “Please fill in the following fields – Branch Name”
Customer ID	1.Mandatory	1. Blank – “Please fill in the following fields – Customer ID”
Customer Name	1.Mandatory 2.Read only	1. Blank – “Please fill in the following fields – Customer Name”

5.2.5 Task flow Diagram

5.2.6 Use Cases

Admin flow for Creation of New User.

Actors Action	System Response
1. Actor login	2.System displays Admin module
3. Actor select Users	4. System displays user details page.
5. Actor click New user	6. System displays New user creation Page.
7. Actor Enters necessary fields with valid data and clicks Submit.	8.System displays a message “New User Created successfully with User ID”
9. Actor enters necessary fields with valid data and clicks Reset.	10. System clears all fields.
11. ACTOR Enters necessary fields with valid data or with out entering any fields clicks Cancel.	12. System closes the new user creation page and displays user details page.

5.3 User Updation

5.3.1 Overview

This feature allows admin to modify existing user information.

5.3.2 Prototype

5.3.3 Page Elements

Element Name	Element Type	User Action	System Response
User Id	Auto display	NA	NA
User Name	Text box	Enter/ Edit	System should accept
Login Password	Text box	Enter/ Edit	System should accept
Transaction Password	Text box	Enter/ Edit	System should accept
Update	Button	Click	As per task flow Diagram.
Cancel	Button	Click	As per task flow Diagram.

5.3.4 Input Validations & Error States

Refer 5.2.4

5.3.5 Task flow Diagram

5.3.6 Use Cases

Admin flow for modification of User.

Actors Action	System Response
1. Actor login	2.System displays Admin module
3. Actor select Users	4. System displays users details page.
5. Actor click edit for any user	6. System displays user updation page.
7. Actor modifies necessary fields with valid data and clicks Update.	8. System displays a message “User Updated successfully”
9. Actor modifies necessary fields with valid data or with out modifying any fields clicks Cancel.	12. System closes the user updation page and displays user details page.

5.4 User Deletion

5.4.1 Overview

This feature allows admin to delete an unwanted bank user.

5.4.2 Task flow Diagram

5.4.3 Use Cases

Admin flow for Deletion of a User.

Actors Action	System Response
1. Actor login	2.System displays Admin module
3. Actor select Users	4. System displays users details page.
5. Actor click Delete for any user	6. System displays a confirmation window with “Yes” and “No” options.
7. If Actor clicks “Ok”	8. System deletes the user.
9. If actor clicks “Cancel”	10. System displays User details page.

6. Employees

6.1 Employee Details Page

6.1.0 Overview

This feature allows admin to view login user names of bank employees working with various branches and to define and manage logins for employees.

6.1.1 Prototype

6.1.2 Page Elements

Element Name	Element Type	User Action	System Response
Employee Id	Tab. Element	NA	NA
Employee Name	Tab. Element	NA	NA
Password	Tab. Element	NA	NA
Role	Tab. Element	NA	NA
Branch	Tab. Element	NA	NA
Edit	Button	Click	AS per task flow diagram
Delete	Button	Click	AS per task flow diagram
New Employee	Button	Click	AS per task flow diagram

6.2 New Employee Creation

6.2.1 Overview

This feature allows admin to create a new login for Bank branch employee.

6.2.2 Prototype.

6.2.3 Page Elements

Element Name	Element Type	User Action	System Response
Banker Name	Text box	Enter/Edit	Accepts
Login Password	Text box	Enter/Edit	Accepts
Role	List box	Select	Displays selected role
Branch	List box	Select	Displays selected role
Submit	Button	Click	As per task flow diagram
Reset	Button	Click	As per task flow diagram
Cancel	Button	Click	As per task flow diagram

6.2.4 Input Validations

Element Name	Valid Data	Error state
Banker Name	1. Alphanumeric only. 2. Start with an Alphabet. 3. Min of 4 Chars. 4. Max of 16 Chars. 5. Mandatory. 6. Unique	1. Blank/Invalid- “Enter a Valid Banker Name”
Login Password	1.Alphanumeric and Special Chars. 2. Min of 4 Chars. Max of 16 Chars. 3. Mandatory.	2. Blank/Invalid- “Enter valid password”
Role	1. Mandatory	1. Blank- “Select a Valid Role”
Branch	1. Mandatory	1. Blank- “Select a Valid branch”

6.2.5 Task flow Diagram

6.2.6 Use Cases

Admin flow for Addition of New Employee.

Actors Action	System Response
1. Actor login	2.System displays Admin module
3. Actor select Employee	4. System displays Employee details page.
5. Actor click New Employee	6. System displays New Employee Entry Page.
7. Enter necessary fields with valid data and clicks Submit.	8. System displays a message “Employee Created Successfully with Employee ID”
9. Enters necessary fields with valid data and clicks Reset.	10. System clears all fields.
11. Enters necessary fields with valid data or with out entering any fields clicks Cancel.	12. System closes the new Employee entry page and displays Employee details page.

6.3 Employee Updation

6.3.1 Overview

This feature allows admin to modify login information of a bank employee.

6.3.2 Prototype for Employee Updation

6.3.3 Page Elements

Element Name	Element Type	User Action	System Response
Banker Id	Auto Display	NA	NA
Banker Name	Text box	Enter/Edit	Accepts
Login Password	Text box	Enter/Edit	Accepts
Role	List box	Select	Displays selected role
Branch	List box	Select	Displays selected role
Update	Button	Click	As per task flow diagram
Cancel	Button	Click	As per task flow diagram

6.3.4 input Validations & Error States

Refer 6.2.4

3.4.1 Task flow diagram

6.3.6 Use Cases

Admin flow for Edit of Existing Employee Details.

Actors Action	System Response
1. Actor login	2.System displays Admin module
3. Actor select Employee	4.System displays Employee details page.
5. Actor click edit on the respective employee details to be edited	6. System displays Employee Update Page.
7. Update necessary fields with valid data and clicks Update.	8. System displays a message “Updated Successfully”
9. Update necessary fields with valid data or with out entering any fields clicks Cancel.	10. System closes the Update Employee details page and displays Employees details page.

6.4 Employee Deletion

6.4.1 Overview

This feature allows admin to delete an unwanted login of bank employee.

6.4.2 Task flow diagram

Admin flow for Deletion of Employee.

Actors Action	System Response
1. Actor login	2.System displays Admin module
3. Actor select Employee	4.System displays Employee details page.
5. Actor click Delete on the respective role to be deleted.	6. System displays a message “Are you sure you want to delete this record” with “Ok” and “Cancel” buttons
7. Actor Click Ok	8. System displays a message “Deletion Successfully”
9. Actor Click cancel	10.System stops the process

..............................................................................................................

TEST PLANS Sample
......................................................

System Test Plan

__________________________

Bank 1.1

Prepared by:

Merisa

Document History

Version	Revision Date	Name	Modification Summary
1.0	08/04/2008	xxxx	Initial Draft
1.1	08/04/2008	xxxx	Updated the QA schedules and Build schedules.

Approvals

Name	User Id	Role	Date
xxxxxxxxxxx		Project Manager	mm/dd/yy

Table of Contents

1.3 Referred Documents

2.0 Scope

2.1 In Scope

2.2 Out of Scope

3.0 Assumptions and Dependencies

3.1 Assumptions

3.2 Dependencies

4.0 Risks and Mitigations

5.0 System Testing Entry and Exit Criteria

10.0 High Level Test Scenarios

11.0 Test Approach

11.1 Test Preparation

11.2 Test Execution

Appendix A

1.0 Introduction

1.1 Project Overview

The objective of the BANK Admin module in project is to create new branches, to create the new users and Bankers along with the privileges. Admin is the super user, which has all the privileges for creating the Branches, Users and Bankers and along with all the other privileges.

The Objective of the BANK Banker module in project is to register and manage the customers of the bank and to book the day-to-day transactions in the bank such as deposits and withdrawals etc.

The Objective of the BANK Customer module in project is designed for the registered customers to perform various activities such as Accounts Summary, Money Transfer, Smart Money Order, Online bill payments and online request for chequebook etc.,

Purpose

The purpose of this document is to provide an overview for System Testing (ST) of Bank. This document covers the testing scope, Entry-Exit criteria, QA Deliverables, QA Schedule, High Level Test Scenarios, Assumptions & Dependencies, Test Management and Risks & Mitigations.

1.2 Referred Documents

The Bank Business Requirements Specifications (BRS)

The BANK Functional Specifications document (FRS)

2.0 Scope

2.1 In Scope

Testing the Admin, Banker and Customer (Personal Banking) modules in E-Banking project.
Functional / system testing of all test scenarios mentioned under sec 10.0.
Creation of Test Requirements, Test Cases and Test Sets in Quality Center 9.0.
Preparation of Test Data for executing the Test Cases.
Test case Execution for 2 cycles and defect Tracking.
Test case execution on the following Operating System Windows2000.
Test case execution using the following browsers - IE 6.0.

2.2 Out of Scope

· Load & Performance testing.

· Unit and Integration testing is not part of this scope.

3.0 Assumptions and Dependencies

3.1 Assumptions

· The main drivers for System Testing are the functionalities contained within the functional specification documents. These will define the scope of the testing and it is assumed that once functionality from these has been tested then full coverage has been achieved.

· Staging server will be accessible.

· Contact details of person(s) concerned with resolving environmental issues will be provided.

· Formal and Intensive Unit and Integration testing will be done by the Dev Team.

· Defects will be dealt with in timely fashion by all teams involved.

· New builds will be deployed in QA environment as per build schedule.

· All identified High-level test scenarios can be simulated in test environment.

3.2 Dependencies

· Knowledge transfer on Functionality as well as Technology to offshore testing team

· Availability of Development environment to validate test scripts.

· Availability of ACL connection to applications from offshore.

· Availability of ACL connection to Databases from offshore.

· Availability of Database schema description to understand the Database Structure.

· Availability of All necessary software’s and Operating System’s

Test data as specified by the QA team, injected into the stage environment.
All necessary User ID’s & passwords provided to the QA team

4.0 Risks and Mitigations

Risk	Likelihood	Impact	Mitigation
Application not accessible or not responding properly during test execution due to environmental issue.	Low	High	Perform an environment sanity check before starting the formal testing Obtain Mobile / Pager numbers of IT team members to escalate P1 environment issues.
Test team does not have enough knowledge of the application	Low	High	Organize extensive knowledge transfer sessions with offshore team
Development team having less knowledge of Quality Center 9.0.	Low	High	QA team will provide clarifications to the Development team.
Presence of large number of blocking Defect‘s during test execution, this would prevent or delay testing.	Low	High	Daily defect meeting will be utilized to prioritize defects QA co-ordinator will work closely with the IT team lead to provide
Changes to requirements	Medium	Medium	All new Requirements that arise are initiated through Change Control process

5.0 System Testing Entry and Exit Criteria

5.1 Entry Criteria

The following must be in place prior to the onset of QA System Testing

Business

· The Business Requirements Document is “frozen

· All new Requirements that arise are initiated through Change Control process

· Daily communication plan in place

· Test Cases Reviewed & signed-off

· Cross-functional, dependent teams & resources identified

· QA Data Requirements identified & all necessary passwords/accesses obtained

· Daily Defect Meeting Day/Time/Attendance established in the execution phase

· All appropriate team members have access to Quality Center 9.0

· Test cases have been linked to test sets in Quality Center 9.0

5.2 Exit Criteria

The following must be in place prior to the sign-off of QA System Testing:

· No open P1 or P2 defects

· All P3-P5 (enhancements) defects have a documented resolution plan

· A minimum of 2 test cycles (100% execution) is completed.

· 95% Pass Rate of all test cases

· Regression testing of defects fixed during system testing

· All defects logged in Quality Center 9.0

· QA sign-off on system test

· System test Close-out report Provided

· Documented list of any outstanding (open) defects

6.0 QA Deliverables

The following items will be delivered:

· System Test Plan

· Test Cases (Maintained in Quality Center–)

· Daily Test Execution Report

· System Test Exit Report

· Defect Log (Maintained in Quality Center–)

· Trace ability Matrix

· Exit Report.

· Project Metrics.

7.0 QA Schedule

QA Activities	QA Deliverable	Start Date	End Date
Analysis of the Documents	Understanding Document	16/03/2009	16/03/2009
Test Planning	Test plan document	17/03/2009	17/03/2009
Test Scenarios Identification & documentation	Test Scenarios document	18/03/2009	18/03/2009
Test case preparation and validation	Test cases, Test Data	19/03/2009	20/03/2009
Test Environment Setup	NA	20/03/2009	20/03/2009
Test case execution and Defect tracking	Complete the execution and defect log maintained in Quality Center	21/03/2009	23/03/2009
End-to-End Test Scenarios Identification & End-to-End test cases preparation	End-to-End Test Scenarios & End-to-End test cases	24/03/2009	24/03/2009
System Testing Sign-off	Exit report	25/03/2009	25/03/2009

8.0 Build Schedule

New builds will only be deployed in stage environment as per build schedule. Only emergency builds can be deployed on other dates. Each build should have version number. Email to QA coordinator has to be sent after successful installation of build. Sanity test by IT team should be conducted after build installation.

Sl.No	Activity	No of Resources	Start Date	End Date	No of Days
1	Build#1	1	21/03/2009	23/03/2009	2
2	Build#2	1	24/03/2009	24/03/2009	1

9.0 Test Environment

The following list of software will be required in the System Test Environment

QA URLs	BANK – http://192.168.1.101/Ebanking
Web Browser	IE 6.0
Test management Tool	Quality Center– 8.0 SP2 http://localhost/tdbin/start.htm Domain: Banking Project: E-Banking
Operating System	Microsoft windows 2000
H/W	Intel (R) Pentium, 2.8 GHZ, 501MB

10.0 High Level Test Scenarios

S#	Test Scenario
Admin Module
0.1	Home Page
0.2	Admin Home Page
1	Branches
1.1	New Branch Creation
1.2	Branch Edit
1.3	Branch Delete
1.4	Branch Search
2	Roles
2.1	New Role Creation
2.2	Role Edit
2.3	Role Delete
3	Users
3.1	New User Creation
3.2	User Edit
3.3	User Delete
3.4	User Search
4	Employee (Banker)
4.1	New Employee Creation
4.2	Employee Edit
4.3	Employee Delete
Banker
5	Customer
5.1	New Customer Registration
5.2	Edit Customer
5.3	Delete Customer
6	Receipts
6.1	Cash Deposit
6.2	DD Deposit
6.3	Cheque Deposit
7	Payments
7.1	Cash withdrawal
7.2	Cheque withdrawal
7.3	DD withdrawal
Customer (Personal Banking)
8.0	Accounts Summary
9.0	Money Transfer
10.0	Smart Money Order
11.0	Biils Pay
01.0	Request for Cheque Book

11.0 Test Approach

11.1 Test Preparation

· The QA Team will prepare Test Scenarios and Test Requirements based on all the project related documents provided by the project team.

· The QA Team will prepare the system test cases to validate each Test Scenario and Test requirement.

· The system test cases will check the application functionality by supplying a set of valid and invalid inputs.

· The system test cases will be reviewed by the development PL. The Test Lead/Analyst will approve the document. The test cases will be stored in QualityCenter from the draft stage itself. The test coordinator will export the test cases in excel format for ease of review.

· SQL queries will be attached to the relevant steps of the test scripts to validate the information on the screen will be validated against the information contained in the database.

11.2 Test Execution

· The test scripts will be executed manually. The results will be validated against the expected results listed in the test scripts. Any defect found in this process will be logged in Quality Centre 9.0.

· Where applicable the information on the screen will be validated against the information contained in the database. Pre-defined SQL queries will be attached to the relevant steps of the test scripts. The tester will copy and paste these queries in Toad SQL window and execute them to obtain the result. The comparison will be done by manual method.

· The application development team will review defects raised by the QA team. The tester will provide all necessary information about the defect in Quality Center 9.0. Attachment tab of Quality Center will be used for providing any screen shots, files required for investigating the defects.

· After the completion of the testing run, the peer team member of the Testing Team reviews the results. The test results are reported to the project PL who will approve the test results. This process may repeat till the number of bugs found is within the acceptable limits and the test exit criteria previously determined is achieved.

· There will be at least six complete cycles of tests executed. The last cycle should go through without any P1 or P2 defects. If there are P1 and P2 defects are found in the last cycle, more testing cycles will be executed until all P1 and P2s are removed.

Appendix A

1 Test Planning

1.1 Quality Center–

Test cases, test sets and defects will be stored and maintained in the BANK - (Domain – E-Banking) domain in Quality Center 9.0, http://localhost/tdbin/start.htm

Quality Center–: Requirements - Requirements will be documented in the Requirements module and associated with applicable test cases.

Quality Center–: Test Plan - Test cases will be written in the Test Plan tab. Test cases will be organized by subject (or function/ use case). At this time, all test cases are written for manual execution.

Quality Center–: Test Lab - Test Sets containing test cases to be executed during System Test will be created in and executed from the Test Lab tab. Test cases will be executed manually.

Quality Center–: Defects - The Quality Center Defects tab will be used to log and communicate status of defects. If a test case does not meet the expected result, the test case will be “failed” and a defect will be logged identifying the problem.

2 Defect Management

2.1 Prioritization of Defects

During system, business, and user-acceptance testing, defects will be logged in Quality Center and assigned a status and priority. Any “show stopper” issues will be assigned a priority of P1. Issue priorities are defined as follows:

P1– High - affects core functionality; prevents availability or interrupts testing; no workaround available. Must be resolved ASAP.

P2 – Medium High - affects core functionality; interrupts testing; workaround available. Must be resolved within 2 business days.

P3 – Medium - interrupts isolated test cases; UI problems; workaround available. Resolution pending schedule.

P4 – Medium Low - affects isolated test cases; nice-to-haves; UI enhancements; workaround available. Resolution pending schedule.

P5 – Low – Cosmetic defects; workaround available. Resolution pending schedule.

P6 – Very Low – Deferred for future releases

2.2 Entering Defects

Before entering a new defect, be sure to check for similar defects to avoid logging duplicates. If you find a potential defect that is within the functionality of another track/module, be sure to work with the appropriate member of your QA team. A daily defect meeting will be scheduled and is mandatory if you have any defects opened by you or assigned to you that are not of the status Closed. Appropriate developer(s) and Business team members will also attend this meeting.

When logging a new defect for this track/module, field values should be set as follows:

Field	Required	Values
Assigned To	Yes
Browser	Yes	Firefox Internet Explorer Konquerer Mozilla Multiple Browsers Netscape Safari
Created Date	N/A
Defect ID	N/A
Defect Status	Yes	New Open Fixed Rejected Reopen Deferred Duplicate Closed Pending
Description	Yes
Detected By	N/A
Detected in Version	Yes
Modified	N/A
Priority	Yes	P1 - High P2 - Med High P3 - Medium P4 - Med-low P5 - Low P6 - Very Low
Project	Yes
Subject	Yes	drop down values automatically will be populated through the requirements tab For UAT – The Use cases have been listed in Subject for each build
CR - Cross Reference	No
Actual Fix Time	No
Closed in version	N/A	Linked to Version defined
Closing Date	N/A
Comments	No
Estimated Fix Time	No
Fix Date	No
OS	Yes	Operating System – Windows 2000, Windows XP, Macintosh and Linux
Planned closing Version	No	Linked to Version defined in the requirement
Reproducible	N/A	y-n field = when NO, Status will be closed
Re-work Counter	No	Should be behind the scenes
Root Cause	No	Boundary System Duplicate Caused by Environment Design Issue Development Issue New Requirement Changed Requirement Deleted Requirement Not in Use Case Prod/ Env. Issue Not Reproducible Pre Existing User Training Not a bug Cosmetic/Grammatical Database Issue Data Issue
CR Type	No	In/Out Cycle

2.3 Defect Status Workflow

An email will automatically be created and sent to the person in the Detected By field as well as the person in the Assigned To and Biz Owner field each time an issue is created or updated within Quality Center 9.0. As many “Closed” issues as possible will be included in the regression testing to occur in the production environment (pre-go-live). Daily, cross-functional defect meetings will be held to ensure proper prioritization of all defects.

The following table lists the status values available for a defect, who a defect with each status should be assigned to, which Quality Centerfields require updating when the status is updated, and any notes regarding the status.

Status	Assign To	TD Fields to Update	Notes
New	Dev Lead	All required	IT Track leads listed above.
Open	Developer, IT QA Analyst, Business QA, Business Owner	Status, Assign to, R&D Comments, Estimated Fix Time	Developers should resolve P1 issues prior to P2, P3, or P4 issues. Open status is used for assigned, researching, in-progress, etc. tasks.
Fixed	QA team lead	Status, R&D Comments, Actual Fix Time	Coding completed and unit testing passed.
Closed	User who closed defect	Status, R&D Comments, Closing Date, Closed in Build, Closing Reason
Reopen	Dev Lead	Status, Assign to, R&D Comments	Include test scenario details during re-test.
Deferred	Business PM/ Business Owner	Status, Assign to, R&D Comments, Deferral Reason, Planned Closing Version	Business review and approval required for this status. Biz owners listed above.

Friday, May 15, 2020

Real Time BRS (BRD), FRS(FRD), Test Plans and test case For BA and QA

1.0 Branches:

2.0 Roles

5.0 Customers Registration

6.0 Receipts

E-Banking_Admin_FRS v1.0

1.0 Home Page

1.1.0 Overview

1.2.0 Prototype

1.3.0 Page Elements

1.6.0 Use Cases

Actors Action

System Response

Actors Action

System Response

Actors Action

System Response

Actors Action

System Response

2.0 Admin Home Page

2.1.0 Overview

2.2.0 Prototype

Admin Home Page

2.3.0 Page Elements

Actors Action

System Response

3.0 Branches

3.1 Branches Details

3.1.1 Overview

3.1.2 Prototype

3.1.3 Page Elements

Actors Action

System Response

3.2 New Branch Creation

Actors Action

System Response

Actors Action

System Response

3.3 Branch Updation

Actors Action

System Response

3.4 Branch Deletion

3.4.0 Overview

3.4.1 Task flow Diagram

Actors Action

System Response

4.0 Roles

4.1 Roles Details Page

4.1.1Overview

4.1.2Prototype

4.1.3Page Elements

4.2 New Role Creation.

4.2.1Overview

4.2.2Prototype

4.2.3Page Elements

Actors Action

System Response

4.3 Role Updation

4.3.1 Overview

4.3.2 Prototype

Actors Action

System Response

Actors Action

System Response

5.0 Users

Actors Action

System Response

Actors Action

System Response

Actors Action

System Response

Actors Action

System Response

Actors Action

System Response

Actors Action

System Response

Document History

1.0 Introduction