Software Requirements

Specification
for

Bank Management System

Version 1.0 approved

Prepared by: Chirag Misra, Gaurav Vaishnav, Avish Dhirawat

Swami Keshwanand Institute of Technology Management and

Gramothan, Jaipur

October 2018

1
Software Requirements Specification for Bank Management System.

Table of Contents
Table of Contents...........................................................................................................................2
1. Introduction..............................................................................................................................3
1.1 Purpose...........................................................................................................................................3
1.2 Document Conventions...................................................................................................................3
1.3 Intended Audience and Reading Suggestions.................................................................................3
1.4 Product Scope.................................................................................................................................4
1.5 References......................................................................................................................................4
2. Overall Description..................................................................................................................5
2.1 Product Perspective.........................................................................................................................5
2.2 Product Functions...........................................................................................................................5
2.3 User Classes and Characteristics.....................................................................................................6
2.4 Operating Environment...................................................................................................................6
2.5 Design and Implementation Constraints.........................................................................................6
2.6 User Documentation.......................................................................................................................7
2.7 Assumptions and Dependencies......................................................................................................7
3. External Interface Requirements...........................................................................................8
3.1 User Interfaces................................................................................................................................8
3.2 Hardware Interfaces........................................................................................................................8
3.3 Software Interfaces.........................................................................................................................9
3.4 Communications Interfaces.............................................................................................................9
4. System Features.....................................................................................................................10
4.1 Login............................................................................................................................................10
4.2 New Customer Registration..........................................................................................................10
4.3 Updating Customer Information….….………….……….………………………………………. 11
4.4 Logout System………………………..………….……………………………………………….
11
5. Other Nonfunctional Requirements.....................................................................................13
5.1 Performance Requirements...........................................................................................................13
5.2 Safety Requirements.....................................................................................................................13
5.3 Security Requirements..................................................................................................................13
5.4 Software Quality Attributes..........................................................................................................13
Appendix A: Glossary..................................................................................................................15

2
Software Requirements Specification for Bank Management System.

Appendix B: Analysis Models.....................................................................................................15

2
Software Requirements Specification for Bank Management System.

1. Introduction
This Software Requirements Specification (SRS) specifies the requirements of the Bank
Management System (BMS) which will be used in the banks. This document will be used by the
customer to ensure all specifications are correct and verified by the software engineer to design
the system.

1.1 Purpose
Purposes are following: -
 To develop a software for solving financial applications of a customer in banking
environment in order to nurture the needs of an end banking user by providing various
ways to perform banking tasks.
 Also, to enable the user a workspace to have additional functionalities which are not
provided under a conventional banking software.

1.2 Document Conventions

We have used following conventions in the project: -
 Main Section Title:
o Font: Times New Roman.
o Font Style: Bold.
o Font Size: 18.
 Sub Section Title:
o Font: Times New Roman.
o Font Style: Bold.
o Font Size: 14.
 Other Text Matter:
o Font: Times New Roman.
o Font Size: 12.

4
Software Requirements Specification for Bank Management System.

1.3 Intended Audience and Reading Suggestions

This SRS would be used by the following persons:
 Bank Employees: They would be using the bank management system to perform the
various banking functionalities.
 Bank Customers: They would be using the to view their account details.
 Research Students: Research students are advised to read all the sections of this
document to get an overall idea of the workflow and technicalities of the software.
 Testers: It can be used as a documentation to know the interfaces.

1.4 Product Scope

As competition has intensified and customer needs have also increased, so too have the
challenges faced by banks. The pressure on margins has increased, often driven by new market
entrants with lower cost bases, and the avalanche of new regulations and compliance seems to
gather pace daily. Customers demand access to their financial information regardless of their
location or the time of day, and if their current financial institution can’t provide it they can
always go to someone else who can.
Often installed decades ago, legacy core banking systems just can’t cope – it may be impossible
to support the latest products and when it is, the process is complex, time consuming and
expensive. Just keeping these systems running can often consume more than 70% of the IT
budget leaving little money to gain advantage over competitors. Gaining insight into customer
needs can be extremely difficult, involving the collation of a large amount of data from disparate
systems held in different formats. And by the time the data is collected it is often too late – the
customers’ needs have moved on. We can see long queues of customers in a bank every now and
then. This queue is the final result of the slow processing speed (Due to manual entries or
noninteractive software) of the bank. So, a highly interactive and user-friendly solution should be
developed.

1.5 References
Following references are used,

5
Software Requirements Specification for Bank Management System.

 https://krazytech.com/projects/sample-software-requirements-specificationsrs-report-airline-
database
 www.slideshare.com
 http://www.muengineers.in/computer-project-list/visual-basic-projects-list/bank-management-
system

2. Overall Description
Our product consists mainly of two parts i.e. the Bank Management System (BMS). The BMS
would deal with the internal banking functions like new account registration, withdrawal,
deposit, account closure etc. The BMS would be exclusively for the customers, who could access
it from anywhere having an internet connection. The BMS uses a well interfaced GUI whereas
the BMS uses well designed web forms for specific actions required by the users. Both of them
connect to a main database server for storing and retrieving the data of the customers.

2.1 Product Perspective

Our product consists mainly of two parts i.e. the Bank Management System (BMS). The BMS
would deal with the internal banking functions like new account registration, withdrawal,
deposit, account closure etc. The BMS would be exclusively for the customers, who could access
it from anywhere having an internet connection. The BMS uses a well interfaced GUI whereas
the BMS uses well designed web forms for specific actions required by the users.
Both of them connect to a main database server for storing and retrieving the data of the
customers.
Our bank management deals with two approaches: -
 Core Banking System (CBS).
 E-Banking System (EBS).
The CBS would deal with the internal banking functions like new account registration, deposit, 
account closure etc. The EBS would be exclusively for the customers, who could access it from
anywhere having an internet connection. The CBS uses a well interfaced GUI (Graphical User
Interface).

6
Software Requirements Specification for Bank Management System.

Whereas the EBS uses well designed web forms for specific actions required by the users.
Both of them connect to a main database server for storing and retrieving the data of the
customer

2.2 Product Functions

Main functions of the Bank Management are as follow:
 Login into the account
 Registration of a new account
 Update account information
 Transaction
 Transaction statements
 Branch details

2.3 User Classes and Characteristics

There are four different ways for a user to interact with the system:
 User:
Who all visited that bank webpage or heard about the bank those persons getting ready to
start account in bank. They register the bank application form, submit and start account in
the nearest bank. Each users have their own account and registered or authorized login
access. The Existing user can login in online to their account perform the operation of
deposit, withdrawn, transfer, balance queries and transactions. All the operation of the
banking does in online it helpful for user because save time and efficient process.
 Administrator:
Admin is master user of the system because they are main role of the systematic grant
and maintain the database of the existing user and grant the permissions to users. It
overrules all other users.

7
Software Requirements Specification for Bank Management System.

2.4 Operating Environment

The bank management system is a platform independent software. This software can operate in
any operating system like windows or linux. The essential requirement for working of the bank
management software is an internet connection (network requirements).
The essential network requirements are as follow:
 The project needs internet to fully demonstrate its capabilities.
 A minimum of 5KBps continuous connection is required for showing any improvement      
brought forth by the product.
 Enhancements to the security features might lead to performance overhead.

2.5 Design and Implementation Constraints

2.5.1 Software Language Used

The languages that shall be used for coding online banking system are C, C++, Java, PHP,
MYSQL, and HTML.
2.5.2 Database design
In our database design, we give names to data flows, processes and data stores. Although the
names are descriptive of data, they do not give details. A data dictionary is a structured
repository of data about data. It is a set of definitions of all DFD data elements and data
structures.
2.5.3 Implementation constraints
 Enhancements to the security features might lead to performance overhead.
 Recommended bandwidth is 64 KBps
 Central server should be online round the clock

2.6 User Documentation

After the completion of the project, a well-documented user manual will be provided.

2.7 Assumptions and Dependencies

We have made the following assumptions:

8
Software Requirements Specification for Bank Management System.

 The information of all the users must be stored in a database that is accessible by the on-
line banking system.
 The online banking system is connected to the computer and is running all 24hours a day.
 The CBS will be connected to the internet during the working hours of the bank.
The main server would never go offline
 The users access the online banking system from any computer that has internet browsing
capabilities and an Internet connection.
 The users must have their correct usernames and passwords to enter into the online
banking system.
 The BMS will be connected to the internet during the working hours of the bank.
 The main server would never go offline.

9
Software Requirements Specification for Bank Management System.

3. External Interface Requirements

1.1 User Interfaces

1.1.1 For CBS:

It will mainly consist of the login screen which would ask for the username and password of the
user. On successful verification, it would transfer the user to the main page of CBS. On clicking
on the desired button or menu item, the user will be shown the respective screen. The user would
then enter the required data for processing and press the 'confirm or done’ butt n, after which the
processing would be done and the user would be returned to the main page. There would also be
a logoff button which would help the user to end his session with the CBS and he will be
transferred back to the login screen.

3.1.1 For EBS:

The first page of EBS would be a login screen which would ask for the username and password
of the customer and on successful verification would transfer the user to the main page where the
user would be able to see all his/her linked accounts. The user would then be able to use the
different functionalities of the EBS by clicking on various links that are provided on each page.
There would be a logout link, pressing which, the user would be logged of the EBS immediately.

1.2 Hardware Interfaces

The minimum hardware requirement for the smooth working of the software are following:
  Pentium IV 1.7 GHz class or better processor
 128MB or more RAM (256 recommended)
 At least 500 MB Hard disk space.
 Continuous battery backup
 Printer which can produce the hard copy.
 Interface that connects the device to bank’s computer.
 An interface that can count currency notes.

10
Software Requirements Specification for Bank Management System.

1.3 Software Interfaces

Essential software requirements are:
 Any operating system.
 The PHP must be installed. For the database handling MYSQL must be installed. These
products are open source products.
 The final application must be packaged in a set up program, so that the products can be
easily installed on machines. This application must be networked to corresponding banks.

On each system and internet connections there are processes responsible for it. They perform all
online functions needed for a single banking system. If the systems that hardware (server and
user’s system) is able to make the banking function properly. In the server there is a master
control panel, which maintains and accesses all the systems as a system customers and bank
staffs. This hardware has to work in conjunction with the wire or wireless connections.

1.4 Communications Interfaces

This product uses an internet connection to connect to the main database server of the bank. The
main control of server shall communicate with the customer systems. It shall do so in a safe
manner. It can request actions for the online server, but the decision to comply with the request
shall remain in the server. Client or customers request the service to (server) admin.

11
Software Requirements Specification for Bank Management System.

4. System Features

1.5 Login
1.5.1 Description and Priority
This feature will be used to LOG IN into the system (only permitted users can use the CBS). It is
done in order to prevent any misuse of system.

1.5.2 Stimulus / Response Sequence
When the user gives correct username and password combination, he/she is transferred to the
main screen or the main page.
1.5.3 Functional Requirements
Purpose:
To check the credibility of a user and to prevent any misuse of the product
Inputs:
The input will be username and password combination.
Output:
The user will be transferred to the main page on successful validation and will be alerted if the va
lidation is unsuccessful.

1.6 New Customer Registration  

1.6.1 Description and Priority
Its purpose is to create a new customer of the bank. A customer must be registered before he/she
can create any new accounts in any of the branches.
1.6.2  Stimulus / Response Sequence
On successful validation of each data field (customer details), the registration takes place and the
success message is displayed.
1.6.3   Functional Requirements
Purpose:
To register a new customer.
Inputs:

12
Software Requirements Specification for Bank Management System.

The required data for registration of a new customer in the bank (Like Name, Address,
Designation etc.)
Output:
A success message be displayed on successful registration or else an error message will be
displayed. Number will be displayed on successful registration or else error message will be
displayed.

1.7 Updating Customer Information

4.3.1 Description and Priority
To update and change the customer profile 
4.3.2 Stimulus / Response Sequence
On successful validation of each data field, the updation procedure takes place 
4.3.3 Functional Requirements
Purpose:
To update the customer profile
Inputs:
The required data for updating the information of a customer would be given 
Output:
Either a successful acknowledgment is displayed or else an error message is displayed.

4.1 Logout System

4.1.1 Description and Priority

This feature would enable the user to successfully end his session and logout of the system. After
logging out, he/she would not be able to perform any of the system operations until he/she is
again logged in.
4.4.2  Stimulus / Response Sequences
On clicking the logout button, the session is terminated and the login screen appears.  
4.4.3  Functional Requirements

Purpose:

13
Software Requirements Specification for Bank Management System.

To successfully end the user session and logout of the CBS. 
Inputs:
Not allowed
Output:  
On successful termination of the session, the login screen is displayed

4.5 Transaction Details

4.5.1 Description and Priority
This feature would display the transaction details of an account when account number hyperlink
is clicked in the account summary page or main page
4.5.2 Stimulus / Response Sequences
On clicking the hyperlink, the transaction details are displayed.  
4.5.3 Functional Requirements
Purpose:
To display the transactional details of an account
Inputs:
The user has to click on the account number hyperlink in the account summary page or main pag
e
Output:   
The transaction details are displayed in a tabular format.

14
Software Requirements Specification for Bank Management System.

5. Nonfunctional Requirements

1.8 Performance Requirements

The system is compatible enough to hold the general traffic. It does not get hang or show some
other problems arising out due to large no of concurrent users. The system is fast enough to meet
the customer the high and low temperature does not affect the performance of the device. An
uninterrupted transaction is performed by the software.
The most important factor in the working of the whole project is its connectivity with the server 
and the mode of connection. If the connection is a 64 KBps one then the performance of the Prod
ucts (EBS & CBS) would be much better than that with a 10 KBps connection.

1.9 Safety Requirements

Following are requirements for safety: -
 Backup, recovery & business continuity banks should ensure adequate backup of data as
may be required by their operations. Banks should also have, well documentation and
tested business continuity plans that address all aspect of the bank’s business.
 Both data and software should be backed up periodically.
 An off-site backup is necessary for recovery from major failures/ disasters to ensure
business continuity.

1.10 Security Requirements

The banking system is fully accessible only to the authentic user. It requires pin for entry to a
new environment.

1.11 Software Quality Attributes

Some of the quality attributes of the bank management system are following:
5.4.1 Correctness:
 The flight should reach start from correct start terminal and should reach the correct destination.
5.4.2 Reliability:
The application should be highly reliable and it should generate all the updated information in
correct order.

15
Software Requirements Specification for Bank Management System.

5.4.3 Availability:
Any information about the account should be quickly available from any computer to the
authorized user. The previously visited customer’s data must not be cleared.
5.4.4 Maintainability:
The application should be maintainable in such a manner that if any new requirement occurs then
it should be easily incorporated in an individual module.
5.4.5 Portability:
The application should be portable on any windows-based system. It should not be machine
specific.
5.4.6 Maintainability:
The administrators and flight in chargers should maintain correct schedules of flights.
5.4.7 Usability:
 The flight schedules should satisfy a maximum number of customer’s needs.

16
Software Requirements Specification for Bank Management System.

Appendix A: Glossary
BMS: - Bank Management System
EBS: - E-Banking System
CBS: - Core Banking System
GUI: - Graphical User Interface
SRS: - Software Requirement Specification
DFD: - Data Flow Diagram
ERD: - Entity Relational Diagram
KBps: - Kilo Byte per second
Admin: - Administrator

Appendix B: Analysis Models

DFD Level 0: -
DFD Level 0 Template. A level 0 data flow diagram (DFD), also known as a context diagram,
shows a data system as a whole and emphasizes the way it interacts with external entities. This
DFD level 0 example shows how such a system might function within a typical retail business.
In DFD level 0 for Bank Management System the data is flowing between User and
Administrator.
DFD level 0 for the Bank Management System is given below:

17
Software Requirements Specification for Bank Management System.

DFD Level 1: -
DFD Level 1 Template. A level 1 data flow diagram (DFD) is more detailed than a level 0 DFD
but not as detailed as a level 2 DFD. It breaks down the main processes into subprocesses that
can then be analyzed and improved on a more intimate level.
In DFD level 1 for Bank Management System the data is flowing between User and
Administrator.
DFD level 1 for the Bank Management System is given below:

18
Software Requirements Specification for Bank Management System.

ERD: -
An entity-relationship diagram (ERD) is a data modeling technique that graphically illustrates an
information system's entities and the relationships between those entities. An ERD is a
conceptual and representational model of data used to represent the entity framework
infrastructure.
ERD for Bank Management System contains different Entities like bank, branches, customer,
accounts, loan and withdrawal/deposit. These entities contain different attributes as per their
needs.
ERD for Bank Management System is given below:

19
Software Requirements Specification for Bank Management System.

20