Software Requirements Specification

For
Automated Teller Machine System

Afshan Siddiqui
October 12, 2016
Version

Changes Made

Date

1.0
1.2
1.3
1.4

First Pass for Review

Second Pass for Review
Third Pass for Review
CRM Review Version

10/24/2000
11/07/2000
11/28/2000
12/04/2000

1. Problem Statement.
To develop an ATM system, this is required to perform the following functions:
1.1 The Customer logs into the system using card no: & pin no: The system checks for
validation.
1.2 The system queries the customer for the type of account either fixed deposit or credit
account .After getting type of account the system show the balance left.
1.3 The system Shows Queries the customer for the transaction type either withdraw or deposit
and the required amount. The user enters the amount & the transaction if carries out.
2. Software Requirements Specification
2.1 Introduction.
2.1.1 Purpose.
This document describes the software requirements for the Automated teller machine
(ATM) system. The document is intended for the customer and the developer (tester,
designer, maintainers).
2.1.2 Scope.

The network enables customers to complete simple bank account services via automated
teller machines (ATMs).

The ATM identifies a customer by a cash card and password.

It collects information about a simple account transaction.

To the customers bank, and dispenses cash to the customer.

The banks provide their own software for their own computers.

2.1.3 Definitions, Acronyms, and Abbreviations.

ATM - Automated Teller Machine
PP - Project Plan
DFD - Data Flow Diagram
SRS - Software Requirement Specification
SDS - Software Design Specification
SPMP - Software Project Management Plan
ERD - Entity Relationship Diagram
TBD - To be determined
UML - Unified Modeling Language

2.1.4 References.

www.google.com.
www.scrid.com.
Ali Bahrami Object Oriented System
http://www.edutechlearners.com/object-oriented-system-development-by-ali-bahrami/

2.1.5 Overview.
The first topic of the SRS provides information about the users and they require this software it
gives the external behavior of the system. The second topic of SRS describes the functionalities
and design of the system. The third topic of SRS describes the Operational and supplementary
requirements for building that system.
2.2 The Overall Description.
There are two primary types of ATMs. Basic units allow customers to withdraw cash and receive
reports of their account balances only. The more complex machines accept deposits, facilitate
line of credit payments and report account information. To access the advanced features of the
complex units, a user must be an account holder at the bank that operates the machine.
2.2.1.1 Hardware Interface
The hardware should have following specifications:
Ability to read the ATM card
Ability to count the currency notes
Touch screen for convenience
Keypad
Continuous power supply
Ability to connect to banks network
2.2.1.2 Software Interface
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
5. Argo Uml
2.2.1.2.1 Back End
2.2.1.2.2 Front End

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.
Functions of the system are:
1. Login
2. Get Balance Information
3. Withdraw Cash
4. Generate receipt
2.2.3

User Characteristics.

There are several users of the ATM network.

Customer.
Maintainers.
It should be easy to maintain the whole system.
It must be very easy for them to use the ATM.
The customer interacts with the ATM network via the ATM.

2.2.4

Constraints

2.3. Specific Requirements.

This section of SRS should contain all of the software requirements and specifications.
All interfaces to the system
1. Every input to the system
2. Every output from the system
All functions performed by the system
1. Validity checks on inputs
2. Relationship of outputs to inputs
2.4. Front -End Description.
2.5. Back -End Description.
2.6. Data Structure.

2.7. Data Flow Diagram.

Use Case Diagram

Class Diagram

Sequence Diagram

Entity Relationship Diagram

Data Flow Diagram

3. Testing

Verify the slot for ATM Card insertion is as per the specification

Verify that user is presented with options when card is inserted from proper side

Verify that no option to continue and enter credentials is displayed to user when card is
inserted correctly

Verify that font of the text displayed in ATM screen is as per the specifications

Verify that touch of the ATM screen is smooth and operational

Verify that user is presented with option to choose language for further operations

Verify that user asked to enter pin number before displaying any card/bank account detail

Verify that there are limited number of attempts upto which user is allowed to enter pin
code.

4. Sample Forms

5. Result
Thus the software requirement specification report has been completed.