0
Software Requirements Specification 20.12.10
Kirti_it_2010
Kirti_it_2010
Version 1.0
State: Maharashtra
Kirti_it_2010/ Kirti. M. Doongursee College
1
Internet Banking System Version 1.0
Software Requirements Specification 20.12.10
Kirti_it_2010
Revision History
2
Internet Banking System Version 1.0
Software Requirements Specification 20.12.10
Kirti_it_2010
Table of Contents
Description Page
1.2 Scope…………………………………………………………………….. 5
3
Internet Banking System Version 1.0
Software Requirements Specification 20.12.10
Kirti_it_2010
2.9.2 Schema……………………………………………………….....18
4
Internet Banking System Version 1.0
Software Requirements Specification 20.12.10
Kirti_it_2010
A bank is a financial intermediary that accepts deposits and channels those deposits into lending activities,
either directly or through capital markets. A bank connects customers with capital deficits to customers with capital
surpluses.Banks act as payment agents by conducting checking or current accounts for customers,
paying cheques drawn by customers on the bank, and collecting cheques deposited to customers'
current accounts. Banks also enable customer payments via other payment methods such as ATM.
Banks provide almost all payment services, and a bank account is considered indispensable by most
businesses, individuals and governments. Non-banks that provide payment services such as remittance
companies are not normally considered an adequate substitute for having a bank account.
1.1 Purpose:
To create a internet banking system to facilitate customers to conduct financial transactions on a
secure website operated by their retail bank, credit union or building society
i)Support
• IBS will support virtual banking environment which is fully automated, customizable and
user-friendly, available to customers through the web.
ii)Provision
• IBS will also provide concrete security features like creating logins for the users and
assigning privileges to users of the system.
5
Internet Banking System Version 1.0
Software Requirements Specification 20.12.10
Kirti_it_2010
iii)Capability
• System will provide valid authentication mechanisms to allow a user to access the account
and take appropriate measures to security breaches on the system.
• System will be capable to keep logs of all the Transactions of the user and provide user all
the necessary account information.
iv)Availability
• Various reports will be available online any time for the Administrators, Managers.
• System will be able to handle extremely large volumes of data (i.e. large database support).
(v)Security
• For Secure access of confidential data (i.e. user’s details), SSL will be used.
(vi)Service
• IBS-Services (E-commerce &Internet Service) & Telecommunication (SMS) will be
available for 24 X 7 Online Support.
• This E-Service will be designed in such a way that it can speed up the process for giving
effective as well as efficient performance even during work load.
• IBS helps to sort out problems which arise during Peak Time during summer holidays,
Christmas Vacation and others.
6
Internet Banking System Version 1.0
Software Requirements Specification 20.12.10
Kirti_it_2010
HTML (Hyper Text Markup Language): It is used to create static web pages.
platform, which is used for developing and running distributed java applications.
that runs and supports the J2EE and the web service applications.
designed to develop more complex projects by providing a complete dynamic web service.
DB2 (IBM Database 2): It is a database management system that provides a flexible and
HTTP (Hyper Text Transfer Protocol): It is a transaction oriented client/ server protocol
Ajax (Asynchronous Java Script and XML): It is a technique used in java script to create
Web 2.0: It is commonly associated with web applications which facilitate interactive
information sharing, interoperability, user-centered design and collaboration on the World Wide
Web.
Kirti_it_2010/ Kirti. M. Doongursee College
7
Internet Banking System Version 1.0
Software Requirements Specification 20.12.10
Kirti_it_2010
1.4 References:
8
Internet Banking System Version 1.0
Software Requirements Specification 20.12.10
Kirti_it_2010
Ex :
9
Internet Banking System Version 1.0
Software Requirements Specification 20.12.10
Kirti_it_2010
The client will have client interface in which he can interact with the banking system. It is a
web based interface which will be the web page of the banking application. Starting a page is
displayed asking the type of customer he is whether ordinary or a corporate customer. Then the
page is redirected to login page where the user can enter the login details. If the login particulars
are valid then the user is taken to a home page where he has the entire transaction list that he can
perform with the bank. All the above activities come under the client interface.
The administrator will have an administrative interface which is a GUI so that he can view
the entire system. He will also have a login page where he can enter the login particulars so that he
can perform all his actions. This administrative interface provides different environment such that
he can maintain database & provide backups for the information in the database. He can register
the users by providing them with username, password & by creating account in the database. He
can view the cheque book request & perform action to issue the cheque books to the clients.
10
Internet Banking System Version 1.0
Software Requirements Specification 20.12.10
Kirti_it_2010
11
Internet Banking System Version 1.0
Software Requirements Specification 20.12.10
Kirti_it_2010
4- Server Side:
Server Side
V5.0
12
Internet Banking System Version 1.0
Software Requirements Specification 20.12.10
Kirti_it_2010
1) Login Process: This module allows valid customers to access the functionalities
provided by the bank.
2) Balance Enquiry: This module maintains the balance details of a particular account.
3) Update Profile: This module allows the customer to update profile of their account.
4) Funds Transfer: This module allows the customers to transfer funds from one
account to another within the same bank.
5) Change of Password: This module allows customers to change their password.
6) Mini Statements: This module allows customers to view their transaction details.
2.6 Constraints:
• Login and password is used for identification of customer’s account and there
is no facility for non users to login.
• This system works only on a single server.
• GUI is only in English
• Limited to HTTP/HTTPS protocols
13
Internet Banking System Version 1.0
Software Requirements Specification 20.12.10
Kirti_it_2010
Login
Account
list
Balance
enquiry
Fund
transfer
Update
profile
Request
cheque
Customer book
Corporate
Mini
stateme
Help
Log out
14
Internet Banking System Version 1.0
Software Requirements Specification 20.12.10
Kirti_it_2010
Login
Request
check book
Log out
initializes
Start
session
Data
backup
Administrator Cash
recovery
End
session
shutdown
15
Internet Banking System Version 1.0
Software Requirements Specification 20.12.10
Kirti_it_2010
Created_On
Service
Service_Id
Created_By
Service_Type
Customer_Id
Service
Employee_Desg. Contact_Details
Balance
details
Account_Id
Balance details
Transaction
Transactions_Id
Transactions_Date
Funds
16
Internet Banking System Version 1.0
Software Requirements Specification 20.12.10
Kirti_it_2010
Account Service
Create Request
Deposit/Withdrawal/ Checks
Transfer
Balance
Funds
details
17
Internet Banking System Version 1.0
Software Requirements Specification 20.12.10
Kirti_it_2010
2.9.2 Schema:
Client_Master
6 Date_Of_Birth Date
7 Occupation Varchar 20
11 Resi_Landmark Varchar 20
18
Internet Banking System Version 1.0
Software Requirements Specification 20.12.10
Kirti_it_2010
16 Resi_Tel_No Varchar 10
17 Resi_Mob_No Varchar 12
18 Email_ID Varchar 40
20 Photo BLOB
21 Off_Bldg_Room_No Varchar 10
24 Off_Landmark Varchar 20
29 Off_Tel_No Varchar 10
30 Off_Fax_No Varchar 10
31 Off_Email_ID Varchar 40
32 Off_Website Varchar 40
33 Pan No Varchar 10
34 Login_Id Varchar 20
35 Password Varchar 20
19
Internet Banking System Version 1.0
Software Requirements Specification 20.12.10
Kirti_it_2010
Employee_master
6 Date_Of_Birth Date
7 Designation Varchar 20
11 Resi_Landmark Varchar 20
20
Internet Banking System Version 1.0
Software Requirements Specification 20.12.10
Kirti_it_2010
16 Resi_Tel_No Varchar 10
17 Resi_Mob_No Varchar 12
18 Email_ID Varchar 40
20 Photo BLOB
Account_Type_Master
Account_Facilities
21
Internet Banking System Version 1.0
Software Requirements Specification 20.12.10
Kirti_it_2010
Account_Type_Scheme_Details
3 Deposit Decimal
Account_Type_Facilities_Link
Account_master
22
Internet Banking System Version 1.0
Software Requirements Specification 20.12.10
Kirti_it_2010
5 Date Date
6 Balance Decimal
9 Debit_Card_No Varchar 25
10 Credit_Card_No Varchar 25
11 Transaction_Id Varchar 20
12 Transaction_Password Varchar 20
Transaction_Master
23
Internet Banking System Version 1.0
Software Requirements Specification 20.12.10
Kirti_it_2010
6 Balance Decimal
Cheque_Book_Request
3 Date Date
5 Cheque_No_From Varchar 15
6 Cheque_No_To Varchar 15
9 Completion_Date Date
24
Internet Banking System Version 1.0
Software Requirements Specification 20.12.10
Kirti_it_2010
3. Specific Requirements:
25
Internet Banking System Version 1.0
Software Requirements Specification 20.12.10
Kirti_it_2010
funds transfer, balance enquiry, cheque book request, etc by sitting at their home
on internet.
1) Performance Requirements
System will be capable of handling users at peak times, like huge traffic congestion.
System can withstand crashes on reading corrupt data and immunized to bad sectors on
the disk.
26
Internet Banking System Version 1.0
Software Requirements Specification 20.12.10
Kirti_it_2010
2) Safety Requirements
By incorporating a robust and proven DB2 UDB into the system, reliable
performance and integrity of data is ensured. There must be a power backup for server
system. Since the product is of 24x7 availability there should be power backup for server
which provides the information .Every day the data should be backup even when the
operation of an user is not successful i.e., while performing the operation power failure
occurs then data should be backup.
3) Security Requirements
27