Docsity
Docsity

Prepare for your exams
Prepare for your exams

Study with the several resources on Docsity


Earn points to download
Earn points to download

Earn points by helping other students or get them with a premium plan


Guidelines and tips
Guidelines and tips

SRS ATM system project, Papers of Software Engineering

It's SRS of software engineering

Typology: Papers

2023/2024

Uploaded on 04/28/2025

priyanshu-bhardwaj-2
priyanshu-bhardwaj-2 🇮🇳

1 document

1 / 8

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
Table of Contents
1. Introduction
1.1 Purpose
1.2 Scope
1.3 Definitions, Acronyms, and Abbreviations
1.4 References
1.5 Overview
2. Overall Description
2.1 Product Perspective
2.2 Product Functions
2.3 User Classes and Characteristics
2.4 Operating Environment
2.5 Design and Implementation Constraints
2.6 User Documentation
2.7 Assumptions and Dependencies
3. Specific Requirements
3.1 Functional Requirements
3.1.1 User Authentication
3.1.2 Balance Inquiry
3.1.3 Cash Withdrawal
3.1.4 Deposit
3.1.5 Funds Transfer
3.1.6 Change PIN
3.1.7 Print Receipt
3.2 Non-Functional Requirements
3.2.1 Performance Requirements
3.2.2 Security Requirements
3.2.3 Availability and Reliability
3.2.4 Usability
3.2.5 Maintainability
3.3 External Interface Requirements
3.3.1 User Interfaces
3.3.2 Hardware Interface3.3.3 Software Interfaces
3.3.4 Communication Interfaces
pf3
pf4
pf5
pf8

Partial preview of the text

Download SRS ATM system project and more Papers Software Engineering in PDF only on Docsity!

Table of Contents

  1. Introduction 1.1 Purpose 1.2 Scope 1.3 Definitions, Acronyms, and Abbreviations 1.4 References 1.5 Overview
  2. Overall Description 2.1 Product Perspective 2.2 Product Functions 2.3 User Classes and Characteristics 2.4 Operating Environment 2.5 Design and Implementation Constraints 2.6 User Documentation 2.7 Assumptions and Dependencies
  3. Specific Requirements 3.1 Functional Requirements 3.1.1 User Authentication 3.1.2 Balance Inquiry 3.1.3 Cash Withdrawal 3.1.4 Deposit 3.1.5 Funds Transfer 3.1.6 Change PIN 3.1.7 Print Receipt 3.2 Non-Functional Requirements 3.2.1 Performance Requirements 3.2.2 Security Requirements 3.2.3 Availability and Reliability 3.2.4 Usability 3.2.5 Maintainability 3.3 External Interface Requirements 3.3.1 User Interfaces 3.3.2 Hardware Interface3.3.3 Software Interfaces 3.3.4 Communication Interfaces
  1. Appendices 4.1 Sample Error Messages 4.2 Future Enhancements (Optional)

Software Requirements Specification

(SRS)

Project: Automated Teller Machine (ATM) System

1. Introduction

1.1 Purpose

This Software Requirements Specification (SRS) provides a detailed overview of the requirements for the Automated Teller Machine (ATM) System. The purpose of the ATM System is to enable bank customers to access their bank accounts for financial transactions without the need for human assistance from bank staff.

1.2 Scope

The ATM System will allow users to perform a variety of banking transactions including cash withdrawal, balance inquiry, funds transfer, PIN change, and cash deposits. The system will consist of both software and hardware components and will connect securely to the bank’s central server. The ATM will be user-friendly, secure, and available 24/7.

1.3 Definitions, Acronyms, and Abbreviations

  • ATM – Automated Teller Machine
  • PIN – Personal Identification Number
  • GUI – Graphical User Interface
  • SRS – Software Requirements Specification
  • User – A person with an active bank account and ATM card
  • Admin – Bank personnel authorized to maintain or update the ATM

2.3 User Classes and Characteristics

  • Regular Customer : Individuals who hold accounts with the bank. Limited technical knowledge.
  • Admin/Maintenance Staff : Authorized bank employees responsible for system maintenance and monitoring.

2.4 Operating Environment

  • Touchscreen ATM machine
  • Encrypted communication with bank servers over secure networks
  • Software: Linux-based embedded OS or Windows ATM platform
  • Languages supported: English + 1 regional language (e.g., Hindi)

2.5 Design and Implementation Constraints

  • Must comply with security standards (e.g., PCI DSS)
  • Limited to the ATM hardware specifications
  • Must support transaction processing within 5 seconds
  • Daily withdrawal limit set by bank policies

2.6 User Documentation

  • On-screen instructions for users
  • User manual for bank staff
  • Admin troubleshooting guide

2.7 Assumptions and Dependencies

  • The ATM is connected to the bank server at all times
  • The customer has a valid account and ATM card
  • External services (e.g., SMS alerts) are available and working

3. Specific Requirements

3.1 Functional Requirements

3.1.1 User Authentication

  • The system shall prompt the user to insert their card and enter their PIN.
  • The system shall verify the PIN with the bank server.
  • If PIN is incorrect more than 3 times, the card shall be blocked temporarily. 3.1.2 Balance Inquiry
  • The system shall retrieve the user’s account balance from the server.
  • The balance shall be displayed on screen and optionally printed. 3.1.3 Cash Withdrawal
  • The system shall ask the user to enter the withdrawal amount.
  • It shall check if the balance is sufficient and if the amount is within the allowed limit.
  • The system shall dispense cash and print a receipt. 3.1.4 Deposit
  • The system shall accept cash or cheque deposits.
  • It shall validate and update the user’s balance.
  • A receipt shall be printed confirming the deposit. 3.1.5 Funds Transfer
  • The system shall allow users to transfer money between accounts.
  • It shall validate the destination account before proceeding.
  • The system shall update both accounts after successful transfer. 3.1.6 Change PIN
  • The system shall verify the old PIN.
  • The user shall enter a new PIN twice for confirmation.
  • Logs should help in diagnosing issues effectively.

3.3 External Interface Requirements

3.3.1 User Interfaces

  • Graphical touchscreen interface with clear icons and text
  • Numeric keypad for PIN entry
  • Receipt printer and cash dispenser 3.3.2 Hardware Interfaces
  • Card reader
  • Receipt printer
  • Cash dispenser
  • Deposit slot
  • Speaker for audio alerts (optional) 3.3.3 Software Interfaces
  • Bank central server APIs for account verification and transaction processing
  • Operating system (Linux/Windows)
  • Encryption libraries for secure communication 3.3.4 Communication Interfaces
  • Secure TCP/IP connection with bank server
  • Optional GSM or mobile data module for remote alerts 4. Appendices

4.1 Sample Error Messages

  • “Invalid PIN. Please try again.”
  • “Insufficient balance.”
  • “Card blocked. Please contact your bank.”
  • “Transaction successful. Please take your cash and receipt.”

4.2 Future Enhancements (Optional)

  • Voice assistance for visually impaired users
  • Biometric authentication (fingerprint or iris scan)
  • NFC-based cardless withdrawals