SOFTWARE REQUIREMENT SPECIFICATION

ATM

SYSTEM

1. Introduction
1.1.
Purpose
To develop software required for supporting computerized banking network.
1.2.
Document conventions
a. Account
A single account at a bank against which transactions can be applied. Accounts may be of
various types with at least checking and savings. A customer can hold more than one acc
ount.
b. Max Daily Withdrawal
The maximum amount of cash that a customer can withdraw from an account in a day
via ATMs.
c. PIN
It refers to Personal Identification Number. Used to identify and validate the login of an A
TM user.
1.3.

Intended audience and reading suggestions

Software designers
Software developers
Software testers
Customers

1.4.

Product scope
The ATM identifies a customer by a cash card and password. It collects
information about a simple account transaction (example deposit, withdrawal,
transfer, bill payment), communicates the transaction information to the
customers bank, and dispenses cash to the customer.

1.5.

References

2. Overall description

2.1.

Product perspective

An automated teller machine (ATM) is a computerized telecommunications device that

Provides the customers of a financial institution with access to financial trnsactions in a
Public space without the need for a human clerk or bank teller. On most modern ATMs,
The customer is identified by inserting a plastic ATM card with a magnetic stripe or a
Plastic smartcard with a chip that contains a unique card number and some security
Information, such as an expiration date or CVC (CVV). Security is provided by the customer ent
ering a personal identification number (PIN).

Figure showing ATM network

2.2.

Product functions

Using an ATM, customers can access their bank accounts in order to make cash withdrawals (or
credit card cash advances) and check their account balances.
The functions of the system are:
1. Login
2. Get Balance Information
3. Withdraw Cash
4. Generate receipt

2.3.

User classes and characteristics

No classes

2.4.

Operating environment

Any standard format like

Ability to read the ATM card

Ability to count currency notes
Ability to connect to bank
Ability to take input from user
Touch screen convenience

2.5.

Design and implementation constraints

2.6.

NA
User Documentation
NA

2.7.

Assumptions and dependencies

Hardware never fails

Limited amount of money per transaction

3. External interface requirements

3.1.
User interfaces
The customer user interface should be intuitive, such that 99.9% of all new ATM users
Are able to complete their banking transactions without any assistance.
3.2.

Hardware interfaces

The hardware should have following specifications:

Ability to read the ATM card
Ability to count the currency notes

Touch screen for convenience

Keypad (in case touchpad fails)
Continuous power supply
Ability to connect to banks network
Ability to take input from user
Ability to validate user.

3.3.
Software interfaces
The software requirements at the user end are:
1. Operating system: windows 98/2000/xp/Vista
2. Languages supported: java (Front end)
3. Database: Microsoft Access (Back end)
4. MS-Office
3.4.
Communication interfaces
These are protocols that are needed to directly interact with the customers. Apart from
these protocols, to maintain a healthy relationship with the customer, both formal and
informal meetings, group discussions and technical meetings will be conducted
frequently.

3. System features
3.1. Authorization
The authorization starts after a customer has entered his card in the ATM, The ATM has to
check if the entered card is a valid cash card
Input
Customer enters the cash card
Processing
Check if it is a valid cash card It will be valid if
1. the information on the card can be read
2. it is not expired
Output
Display error message and return cash card if it is invalid Functional.
3.2. Issue money
The client enters inserts into the ATM machine. It asks for PIN and checks authorization,
If the client has enough credit in his account, he will be permitted to carry out a valid
transaction. The momentary value of the transaction will be deducted from his system. Then
ATM will issue the currency notes and thus transaction is completed.
3.3. Transaction Summery
After a complete transaction, the client will get receipt, if the client request details about his
last transaction and current balance in the account.

3.4.

Value Added Services

Other value added services include transact money from one ATM to another ATM.

4. Other Non-functional Requirements

4.1. Performance Requirements:
It must be able to perform in adverse conditions like high/low temperature etc.
Uninterrupted Interrupted connections
High Data transfer rate

4.2. Safety requirements:

Must be safe kept in physical aspects, say in a cabin
Must have emergency phone outside the cabin
The cabin door must have a TM card swipe slot

4.3. Security requirements

Users accessibility is censored in all the ways

Users are advised to change their PIN in first issue
Users are advised not to tell their PIN to anyone
The maximum number of attempts to enter PIN will be 3

Software quality attributes: NA