Software Requirements

Specification
for

ATM Cash Withdraw System

Version 1.0 approved

Prepared by Vikram Kumar

TMSL

18/07/2022

i|Page
Table of Contents
1. Introduction ............................................................................................................................................. 4
1.1 Purpose................................................................................................................................................... 4
1.2 Document Conventions ......................................................................................................................... 4
1.3 Scope ...................................................................................................................................................... 5
2. History/Background Study (Sources of Domain Knowledge) ............................................................. 5
2.1 Technical Literature ............................................................................................................................. 5
2.2 Existing Applications ............................................................................................................................ 5
2.3 Customer Surveys ................................................................................................................................. 6
2.4 Expert Advice ........................................................................................................................................ 8
2.5 Current/Future requirements:............................................................................................................. 8
Reference:- ................................................................................................................................................... 9
3 The Overall Description:-........................................................................................................................ 9
3.1 Product Prospective .............................................................................................................................. 9
3.2 Product Function:- ................................................................................................................................ 9
3.3 User Characteristic:- ............................................................................................................................ 9
3.4 Scenarios:- ............................................................................................................................................. 9
3.4.1 Initial assumption:- ........................................................................................................................ 9
3.4.2 Normal Case:-................................................................................................................................... 10
For the user:- ......................................................................................................................................... 10
For the operator:- ................................................................................................................................. 10
3.4.3 What can go wrong:- ....................................................................................................................... 10
3.5 Dependencies:-..................................................................................................................................... 10
4. System feature ....................................................................................................................................... 10
4.1.1 User Interfaces ................................................................................................................................. 10
4.1.2 Hardware interface ....................................................................................................................... 11
4.1.3 Software Interfaces ........................................................................................................................ 11
4.1.4 Communication Interfaces ............................................................................................................ 12
5. Functional Requirements ..................................................................................................................... 12
5.1 Authentication ................................................................................................................................. 12
5.1.2 Output Screen............................................................................................................................... 12
5.2 Banking transactions ...................................................................................................................... 12
5.1.1.1 Priority ....................................................................................................................................... 12

2|Page
5.1.1.2 Stimulus and Response ............................................................................................................... 12
5.3.1 Description and priority ................................................................................................................ 12
5.3.2 Stimulus and response ................................................................................................................. 13
5.3 User exit Interface .............................................................................................................................. 13
6 Other Nonfunctional Requirements ..................................................................................................... 13
6.1 Performance Requirements ........................................................................................................... 13
6.2 Safety Requirements ....................................................................................................................... 13
6.3 Security Requirements ................................................................................................................... 13
6.3 Software Quality Attribute ............................................................................................................ 13
7. Conclusion ............................................................................................................................................. 13

3|Page
1. Introduction
An ATM stands for Automated teller machine. Basically, it is type of computerized
telecommunication machine which provide banking services to the people in public area without
physical visit to the bank.
An ATM provides services like:-
1. Cash withdrawal
2. Online Banking
3. Check Balance
4. Pin Generation
5. Update phone Number.
Through ATM public can do various transactions with user friendly interface along with security
without wasting too much time in row in the bank.

1.1 Purpose
The purpose of this SRS is to provide well designed and documented details to the following
member:-
1. Developer (for the design and development as per the requirement).
2. Bank Management (for managing the status of ATM).
3. Tester

1.2 Document Conventions

• Accounts
A single account in a bank against which transaction can be applied. Accounts may be
of various type with at least checking and savings. A user can hold more than one
accounts.
• ATM
A station that allows user to enter their own transaction using cash card as
identification. The ATM interacts with the user to gather transaction information, send
the transaction information to the central for validation and processing and dispense
cash of customer.
• Cash Card

4|Page
 A cash card assigned to the bank user that authorizes access to accounts using an ATM
machine, Each card contains a bank code and a card number, corded accordance with
machine. Each card is owned by single user.

• Transaction
A single integral request for operation on the accounts of a single customer. We only
specified the ATMs must dispense cash, We may also provide the flexibility to operate
on accounts of different user. The different operations must balance properly.

1.3 Scope
The scope of this software is to user friendly interface or an interactive output to the user where
they can do their various transaction without visiting to the bank. This software provide various
facility like cash withdrawal, money transfer, pin generation, online banking, check balance and
many more feature to user profile for customers.
This software take input credentials like account number and pin with OTP for the login purpose
and validate the customers and provide user dashboard where they can choose their desirable
function for their action, or can simply insert their ATM card and login through pin into their
account.
The Software is expected to be complete under 4months with cost of 70k.

2. History/Background Study (Sources of Domain Knowledge)

2.1 Technical Literature

The first ATM was set up in June 1967 on a street in Enfield, London at a branch of Barclays
bank. A British inventor named John Shepherd-Barron is credited with its invention. The
machine allowed customers to withdraw a maximum of GBP10 at a time.

The first decade of the 21st century saw a rise in the number of ATM frauds via sophisticated
malware or technologies, such as skimming devices. To stay one step ahead, banks developed
software that could detect anomalies in transactional data that hint towards illegal activity.

2.2 Existing Applications

ATM’s system of different bank service provider’s like SBI,BOI,PNB etc.

5|Page
2.3 Customer Surveys

6|Page
7|Page
2.4 Expert Advice

2.5 Current/Future requirements:

• Primary function is withdrawal and balance checking must function without any errors.
• Future function include deposit cash, update account details or provide app platform
for cashless use.

8|Page
Reference:-
https://en.m.wikipedia.org/wiki/Automatedtellermachine
Content and materials provided by the teacher.

3 The Overall Description:-

3.1 Product Prospective

An ATM’s software is to run on an new ATM hardware machine that local banks wants to
setup for their users or customers. The product will be developed from existing system of the same
local bank or from another bank that similar characteristics of the specified local bank. The system
will be designed in such a way that the user will access and use the ATM to access banking system
which update, configure and access the bank details of the customers from the database. The
system also accommodate an operator who will load money in the ATM machine, and make sure
the system hardware is always power on.

3.2 Product Function:-

• Login
• Balance Inquiry
• Cash withdraw
• Pin Generation
• Account update
• Cash Deposit

3.3 User Characteristic:-

• Open to all type of customer but access level is dependent on the knowledge of the system.
• Bank security person should have special training or education
• Maintainers must be experienced system handler.

3.4 Scenarios:-
3.4.1 Initial assumption:-
• In the display system user at first choose his /her desirable language.
• The user with valid account number and password or by swiping card and correct pin
attempt to access the banking services using the ATM.
• The ATM machine has money loaded that will be able to withdrawn by a user.
• The user knows how to handle ATM machine.

9|Page
3.4.2 Normal Case:-
For the user:-
• The user enters the correct credentials like account number and pin and validate the banking
system services using the ATM.
• In the prompt screen there will function of the machine whatever the user want to choose.
• Let the user logged in with correct credentials and withdraw cash from the ATM.
• The user is logged in with correct account number and pin and deposit cash into his
account.
• The user can query for balance enquiry of his/her account.
• The user can update their account detail like phone number.
For the operator:-
• The operator can successfully update the users accounts database after the amount deposit
of the user.
• He/she able to keep ATM power on all the time.
• He/she able load money in the ATM which user will have to withdraw.

3.4.3 What can go wrong:-

• Unauthorized access to the account by the user who is not the owner of the particular
account.
• Failure to update bank account database after the user makes a transaction.
• Operator making accounting error and updating a users account wrongly after a deposit
transection by the user.
• A user is trying to withdraw cash grater then the balance available in his/her account.

3.5 Dependencies:-
• Hardware never fails
• Limited amount of money withdraw per day.
• Limited number of transection per day.
• ATM casing is impenetrable.

4. System feature

4.1.1 User Interfaces

The interface of the ATM must fulfill ergonomic requirements. The foll0owing is just an example
for a possible interface to the ATM.

10 | P a g e
 Message for the user

0 1 2 3 4

5 6 7 8 9

ENTER

Card slot Receipt Slot Cash Slot

4.1.2 Hardware interface

The ATM network has to provide hardware interface to:
• A screen that displays messages to the user.
• A keyboard receives numeric input from the user.
• A cash dispenser that dispenses cash to the user.
• A receipt slot that dispense the receipt to the user.

4.1.3 Software Interfaces

The ATM network has to provide different software interfaces to:
• Windows XP.
• Windows 7,8,10 etc.
• Language Supported C++
• Database

11 | P a g e
4.1.4 Communication Interfaces
No restriction of the ATM network to specify network protocol as long as the performance
requirements are satisfied.

5. Functional Requirements
A brief outline and description of the main features and functionalities of the ATM software
system.
5.1 Authentication
5.1.1 Description and priority
The ATM provides access to the banking system services, In order for a user to perform
a transaction with bank system needs the system need to validate the user through their
credential.

5.1.2 Output Screen

• The Welcome Screen.
• Please insert Your Card or Enter Your account number
• Enter user pin.

OUTPUT: Main Menu

5.2 Banking transactions

5.1.1.1 Priority
The utility is executable from the main menu displayed a numbered option. It enables
various users to request balance enquiry, perform cash withdrawals and carryout
deposits.

5.1.1.2 Stimulus and Response

• Balance enquiry option
• Withdrawal Cash
• Receipt
• Pin Generation
• Account Update

5.3.1 Description and priority

This feature enables user not to overdraw their accounts and update from the main menu that their
accounts when deposits have been carried out.
If the user makes balance inquiry, the screen displays the user’s accounts balance.

12 | P a g e
 5.3.2 Stimulus and response
If the withdrawn amount chosen is greater than the users account balance: the screen should show
error and ask the user to enter amount under his/her available balance.
If the withdrawn amount is acceptable then it proceeds for the next steps.

5.3 User exit Interface

After completing a transaction there should be exit option for the user.

6 Other Nonfunctional Requirements

6.1 Performance Requirements
• It must be able to perform in adverse conditions.
• Must having data transfer rate.
6.2 Safety Requirements
• Must be safe in physical aspect, stay in a both
• Must be scaled to the floor to prevent any kind of theft
• There must be a guard just outside of the booth for security.
6.3 Security Requirements
• User are advised to change their pin on first use.
• User are advised not to share their pin to anyone.
• The maximum number of attempts to enter PIN are limited to three.
6.3 Software Quality Attribute
• Easy to learn for an ordinary person.
• Easy to understand operation from an engineering perspective.
• The system will be down for an hour in each 24hr.
• System can be easily integrate with bank system.
• Software can be installed on a number of ATMs without affecting current operation status.
• Easy to troubleshoot and maintain in case system fails abruptly

7. Conclusion
The overall conclusion of this SRS is here the user gets a medium or an public station from
where a user can access their account as per their requirement without wasting too much time
in bank line. This software provides a platform where user can withdraw cash, do balance
enquiry.
Or the bank administration gets a software platform from where they can handle their number
of user without too much crowd or workload, This provide administrative features to the bank
employ.

13 | P a g e
14 | P a g e