Experiment 3: Aim: - Write The Software Requirement Specification Document of ATM Management System. Introduction
Experiment 3: Aim: - Write The Software Requirement Specification Document of ATM Management System. Introduction
Aim: - Write the software requirement specification document of ATM Management System.
Introduction: -
The software ATMExcl 3.0TM version1.0 is to be developed for Automated Teller Machines (ATM).
An automated teller machine (ATM) is computerized telecommunications device that provides a
financial institution's customers a secure method of performing financial transactions, in a public
space without the need for a human bank teller. Through ATMExcl 3.0TM ,customers interact with
a user-friendly interface that enables them to access their bank accounts and perform various
transactions.
This SRS defines External Interface, Performance and Software System Attributes requirements of
ATMExcl 3.0TM. This document is intended for the following group of people:-
Developers for the purpose of maintenance and new releases of the software.
Management of the bank.
Documentation writers
Testers
Scope: -
This document applies to Automated Teller Machine software ATM 3.0TM. This software facilitates
the user to perform various transaction in his account without going to bank. This software offers
benefits such cash withdrawals, balance transfers, deposits, inquiries, credit card advances and
other banking related operations for customers. It also allows the administrator to fix the tariffs
and rules as and when required.
The software takes as input the login Id and the bank account number of the user for login
purposes. The outputs then comprise of an interactive display that lets the user select the
desirable function that he wants to perform..
The software is expected to complete in duration of six months and the estimated cost is Rs18
lakhs.
Performance Requirements
The following list provides a brief summary of the performance requirements for the software:
Capacity: - The ATM shall provide customers a 24 hour service.
Dynamic requirements
• The card verification time must not exceed 0.8 sec. under normal server workload and 1
sec. under peak server workload.
• The pin number verification time must not exceed 0.3 sec. under normal server workload
and 0.5 sec. under peak server workload.
• Account balance display time must not exceed 2 sec. under normal server workload and 3
sec. under peak server workload.
• Account balance transfer time must not exceed 3 sec. under normal server workload and 4
sec. under peak server workload.
• Cash withdrawal transaction time must not exceed 4 sec. under normal server workload
and 5 sec. under peak server workload.
• Deposit transaction time after insertion of the deposit envelope must not exceed 5 sec.
under normal server workload and 6 sec. under peak server workload.
• Receipt printing time after must not exceed 3 sec. under normal server and peak server
workload.
• Touch screen and button response time must not exceed 5000ms.
• Credit card advance time must not exceed 6 sec. under normal traffic and server and peak
traffic and server workload.
Quality – The primary objective is to produce quality software. As the quality of a piece of software
is difficult to measure quantitatively, the following guidelines will be used when judging the quality
of the software:
Consistency – All code will be consistent with respect to the style. (This is implied when adhering
to the standard).
Test cases – All functionality will be thoroughly tested
• Maintainability
• The system components i.e. modem, memory, disk, drives shall be easily serviceable
without requiring access to the vault.
• The system should have the mechanism of self-monitoring periodically in order to detect
any fault.