Scribd
Upload
16 views

Document 4 (6)

srs for bank management system

Uploaded by

Anagh
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
16 views

Document 4 (6)

srs for bank management system

Uploaded by

Anagh
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 11

SRS FOR BANK MANAGEMENT SYSTEM

ANAGH P
08
Table of Contents
1. Introduction
1.1 Purpose
1.2 Scope
1.3 Overview
1.4 Additional Information
2. General Description
3. Functional Requirements
3.1 Description
3.2 Technical Issues
4. Interface Requirements
4.1 GUI
4.2 Hardware Interface
4.3 Software Interface
5. Performance Requirements
6. Design Constraints
7. Non-Functional Requirements
7.1 Security
7.2 Reliability
7.3 Availability
7.4 Maintainability
7.5 Reusability

1. Introduction
1.1 Purpose
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.2 Scope
This Product will automate of banking transaction
process.

1.3 Overview
The system provides easy solution to banks.
1.4 Additional 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.1 Description
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.2 Technical 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.
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.1 Security
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.2 Reliability
The application should be highly reliable and it should
generate all the updated information in correct order.

7.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.

7.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.

7.5 Portability
The application should be portable on any windows based
system.

You might also like