Software

Requirement
specification for 2021
Bank Management
System
SOFTWARE REQUIREMENTS SPECIFICATIONS DOCUMENT OF
BANKING SYSTEM
1. INTRODUCTION

1.1 Need and Purpose

Banking transactions have evolved over the years. As a major economic industry,
it is now digitally driven. The use of databases which enable easier storage and
retrieval of transactions from anywhere and anytime with the application of
appropriate rights. Update is done almost automatically and is much faster. Users
can access their accounts directly without going to a bank, making transfers,
transactions and accessing cash directly without standing in long queues as was
prevalent earlier using ATM machines.

On employee-side the data is much more organized, and accessing and performing
actions on user accounts is easier for them. Due to this the bank has better work
efficiency and customer experience improves as well.

Intended Audience

This SRS would be used by the following persons:

Bank Employees: They would be using the EWS to perform the various banking
functionalities.

Research Students: Research students are advised to read all the sections of this
document to get an overall idea of the work-flow and technicalities of the software.

Testers: It can be used as a documentation to know the interfaces

OVERVIEW OF DOCUMENT
The first section of SRS gives a brief introduction on BankMan banking system.
This section also provides the reference information for further study, intended
audience and need & purpose of the product.

The second section provides an overall description of the application, product

features & functions, users and operating environment (hardware, software and
external).
The third section is about the specific requirements like external interfaces,
performance requirements, design constraints and additional comments.

The last section deals with the details of ATM design and implementation

2. DESCRIPTION

2.1 Features and Functions

Features
BankMan (Bank Management System) can be used by Bank Employees and/or
Customers depending on bank policy. It can be used by several employees of the
bank at the same time with required rights. It can be accessed using any general
web browser with graphical interface.

Our Product consists mainly of two parts i.e. the Employee Work-Space (EWS)
and the ATM-Banking. The EWS would deal with the internal banking functions
like new account registration, withdrawal, deposit, money transfer etc. The ATM
banking would be for direct access of customers, who could use it for Cash-
Withdrawal, Transfers and Account-Summary. Both of them connect to a main
database server for storing and retrieving the data of the customers.

Functional Requirements:

EWS requires employee login. It handles following

1. Accounts opening – enrol a new customer into the system

2. Transactions - deposits, withdrawals , loans ,

a. Detail Updation

b. Deposit

i. Cheque

ii. Cash

c. Debit

d. Transfer
e Account Summary

ATM transaction requires ATM No. and PIN that will be available to Bank's
customer. It doesn't require Employee login.

It performs following

1. Cash withdrawal

2. Transfer

3. Account Summary

Users classes and Characteristics

Bank Front-end Employees : The Bank Employees would be the main users of the
BankMan Systems. They may perform banking functions using EWS or may
facilitate customer in using ATM, as per bank's policy.

Bank Customers : The customers would be able to use ATM-Login, if bank

wants to provide user with direct access, otherwise they may use ATM via. Bank
Employee

2.3 Operating Environment

2.3.1 Hardware
BankMan requires an entry-level PC for smaller number of bank accounts (like,
when data is being stored locally). For larger no. of bank accounts, a server class
machine is recommended.

2.3.2 Software

The BankMan server can run on any recent version of Linux, such as Ubuntu,
Debian, Fedora Core, Redhat Enterprise, etc. It requires:

1. Apache 4.5 or later

2. Tomcat 5.6 or later

3. PHP 5.6
The BankMan user-interface works with any of the following graphical
browsers on any hardware and OS:

1. Firefox 5.0

2. Internet Explorer 7.2

3. Chrome 2.0

4. Opera 2.3

Higher versions of these browsers are likely to work but cannot be guaranteed.
With update of HTML, the interface may get deformed, so it is recommended the
BankMan software be updated on a regular basis.

All forms would be validated to take only appropriate data.

2.3.3 External

The banking systems like BankMan requires 24-hr electricity supply and
communications for data update to be timely.

3. Specific Requirements

3.1 Performance Requirements

Database can store details of up to about a Hundred Thousand accounts,

but that can vary according to Bank's need, and would depend on data storage
capacity of server and not on database.

The response time depends on size of database due to searching process, but still
the response by server will be just the time to search, as it would be accessed from
specific devices in the bank and there is no system for accessing it online.

3.2 Design Constraints

• Enhancements to the security features might lead to performance overhead.

• Central Server should be on-line round the clock.

3.3 Overview of Data Requirements

The product is completely data oriented.

In EWS, the employees would input the various details of Customer for updating,
processing or retrieval of data and for new customers, required fields for
registration will be filled.

In ATM-Banking, the users would input less amount of data (only ATM number
and pin) and be able to have faster cash-withdrawal and transfer money to other
accounts

3.4 Additional Comments

This document describes a MySQL and PHP based application, for purpose of
implementing a Bank Management System, for a BS.c Information Technology
Education. ITC 357

Software engineering at AA-MUSTED, Ghana, 2022

This document describes a fictitious software product purely for the above
mentioned academic purpose. It is not related in any way to a particular existing or
proposed real product. This document doesn't guarantee the implementation to be
secure, efficient or error-free.

BANKING ATM SYSTEM

1. Introduction

1.1Purpose
This document gives detailed functional and non functional
requirements for the bank management system. This product
will support online banking transaction using ATM. The
purpose of this document is that the requirements mentioned in
it should be utilized by software developer to implement the
system.
1.2Scope
 This Product will automate of banking transaction process.
1.3Overview
The system provides easy solution to banks.
1.4Additional Information
This system will work together with bank’s computer.
It will not be operated independently. Various banks might be
networked together.

2. General Description

Using Automatic Teller Machine (ATM) customer can withdraw the

desired amount of money. ATM is basically computerized
telecommunication device that helps the customer to perform banking
transactions. The customer is identified by inserting a plastic ATM
card with a magnetic stripe or a plastic smartcard with a chip. This
magnetic media contains a unique card number and some security
information. Security is provided by the customer entering a Personal
Identification Number (PIN). When a customer wants to perform
some transaction, he/she will enter the ATM card in the machine and
then enter the PIN. Only authentic customer will be allowed to
perform this transaction.

3. Functional Requirements

This section provides the requirement overview of the product. The

project will require the PHP as a front end and at the back end the
database MYSQL will be running. Various functional modules that
can be implemented by the product will be –

1. Login
2. Validation
3. Get balance information
4. Withdrawal of money
5. Transfer Money
 6. Report Generation

3.1Description

Login:
Customer logins by entering the card and typing the PIN.
Validation:
When a customer enters the ATM card, its validity must be
ensured. Then customer is allowed to enter the valid PIN.
The validation can be for following conditions –

 Validation for lost or stolen card

When card is already reported as lost or stolen then the
message “Lost/Stolen card!!!”.
 Validation for card’s expiry date
If the card inserted by the customer has crossed the
expiry date then the system will prompt “Expired Card”.
 Validation for PIN
After validating the card, the validity of PIN must be
ensured. If he/she fails to enter valid code for three times
then the card will not be returned to him. That means the
account can be locked.

The counter for number of logins must be maintained

Get balance information:

This system must be networked to the bank’s computer. The updated database of
every customer is maintained with bank. Hence the balance information of every
account is available in the database and can be displayed to the customer.

Withdrawal of Money:
A customer is allowed to enter the amount which he/she wishes to withdraw. If the
entered amount is less than the available balance and if after withdraw if the
minimum required balance is maintained then allow the transaction.

Transfer of Money:

The customer can deposit or transfer the desired amount of money.

Report:

The bank statement showing credit and debit information of corresponding account
must be printed by the machine.

3.2Technical Issues
This product will work on client-server architecture. It will
require an internet server and which will be able to run PHP
applications. The product should support some commonly used
browsers such as Internet Explorer, Mozilla Firefox.

4. Interface Requirements

4.1 GUI
This is interface must be highly intuitive or interactive because there
will not be an assistance for the user who is operating the ATM. The
sample GUI for withdrawal of money can be
 Bank’s Name of Bank
Logo

Withdrawal of Money

Enter the amount of money to be withdrawn and press enter key

500 Rs. 5000 Rs.

1000 Rs. 10000 Rs.

If user wants to perform another transaction he will press – Enter key otherwise
press Quit. After pressing the Quit button the card must be ejected.

4.2 Hardware Interface

Various interfaces for the product could be

1. The Hardware interface that can read the ATM card.

2. Touch screen/Monitor
3. Keypad
4. Continuous battery backup
5. Printer which can produce the hard copy.
6. Interface that connects the device to bank’s computer.
7. An interface that can count currency notes.

4.3 Software Interface

 1. Any windows operating system.

2. The PHP must be installed. For the database handling MYSQL must be
installed. These products are open source3 products.

3. The final application must be packaged in a set up program, so that the

products can be easily installed on ATM machines. This application must be
networked to corresponding banks.

5. Performance Requirements

The high and low temperature should not affect the performance of the device.
An uninterrupted transaction must be performed.

6. Design Constraints

None.

7. Non Functional Requirements

7.1Security
The ATM system must be in separate cabin.
Its door must have ATM card swipe slot so that it can be opened to
only authentic user.
There must be emergency phone located outside the cabin.
Some security watchman should be at ATM center.

7.2Reliability
The application should be highly reliable and it should generate all
the updated information in correct order.

7.3Availability
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.
 7.4Maintainability
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.
7.5Portability
The application should be portable on any windows based system.

8. Preliminary Schedule

This product must be completed in 7 months.

ARCHITECTURAL, HIGH LEVEL AND DETAILED DESIGN
FOR A BANKING SYSTEM
Creating account detail flowchart