ATM System Case Study

FUNCTIONAL SPECIFICATION
1 Introduction
XYZ Bank of India provides monetary service facilities to customers across many cities.
XYZ Bank of India plans to develop Automated Teller Machine - a web application where a
Customer can get services of the Bank.
Scope and Overview:
The scope of the Automated Teller Machine System (ATM) will be to provide the
functionality as described in Functional Requirements below. The system will be
developed on a Windows XP machine using J2EE, JSP/HTML, and JDBC.
2 Functional Requirements
The users of the ATM application are:
1. Administrator Add/modify/delete customer details and generate account statement
2. Customer - Perform operations withdraw/deposit cash and view balance
Below are the requirements specific to the types of users:
2.1
Administrator
Requirement
ID
AD-001
AD-002
AD-003
AD-004
AD-005
AD-006
2.2
Customer
Requirement
ID
CU-001
CU-002
CU-003
CU-004
CU-005
CU-006
2.3
2.4
Description
Priority
The Administrator should be able to add branch details of bank

The Administrator should be able create customers and their account
The Administrator should be able to modify customer details
The Administrator should be able to delete customer details
The Administrator should be able to verify the check dropped by
customer and clear the check credits to the customer account
The Administrator should be able to generate account statement for
customer
P1
P1
P1
P2
P1
Description
Priority
The customer should be able to change their pin

The customer should be able to withdraw cash(Get cash)
P1
P1
The customer should be able to withdraw cash(Fast cash)

The customer should be able to deposit cash(By check)
The customer should be able to view balance summary
The customer should be able to get mini statement
P1
Authentication & Authorization

Requirement
Description
ID
AA-001
All users logging into the system should be authenticated using a unique
login-id and password. (Operations to be supported based on type of
user)
Exit handlers
Requirement
ID
EX-001
P1
P1
P2
P1
Priority
P1
Description
Priority
The application should handle logout (close all open database

connections, invalidate sessions, etc)
P1
3 Interface Requirements
The Automated Teller Machine should be developed as a GUI application using HTML/JSP screens.
4 Non functional Requirements
The application should be intuitive to use and easy-to-maintain

The application should be able to handle simultaneous requests from multiple clients
Upon installation, the Administrator is expected to have default User ID and Password
The system may force the Administrator change his password to a non default one, upon initial
login
Target Environment:
Intel hardware machine (PC P4-2.26 GHz, 512 MB RAM, 40 GB HDD)
Windows XP
Server Apache Tomcat 6 or higher
Database Oracle 9i or higher
JRE
Eclipse IDE
5 Assumptions/Dependencies/Limitations
Each user will hold only one Customer_ID

The Administrator can also be a customer of the bank
The number of administrators is limited to 2
The account statement will be generated for customer by the administrator based on
From and To Date
A customer can open only one savings account in one branch
The customer can withdraw cash by specifying the required amount (Get Cash)
The customer can withdraw cash by specifying from the specified amount list (Fast Cash)
The mini statement should contain last ten transactions of the customer
6 Acceptance Criteria
The acceptance criteria will be defined in Acceptance Test Plan.
List of expected deliverables:
- Release note
- Use Cases document
- Design Document
- Test Plan documents
- Test Cases documents (with test results)
- Tested source code
Smita
7 Requirements Priority Table

Abbreviation
P1
P2
Remark
First Priority (Priorities have been specified along with the requirements)
Second Priority (Priorities have been specified along with the requirements)
8 Acronyms and Glossary

Abbreviation
Remark
Smita
1. Introduction
1.1 Background
1.2 Purpose
1.3 Scope
The scope of the Automated Teller Machine System (ATM) will be to provide the functionality as
described in Functional Requirements below. The system will be developed on a Windows XP
machine using J2EE, JSP/HTML, and JDBC.
2. Systems Overview
2.1 System Description
The Automated Teller Machine System should support the following users:
Administrator (A)
Customer (C)
The common functional requirements are explained below.
2.1.1 Authentication
Any end-user should be authenticated using a unique login ID and password.
2.1.2 Authorization
The operations supported and allowed would be based on the user type. For example,
Administrator has the rights to create/modify/delete and view customer details. He can
also view customer transaction details.
Database
Files
ATM Application
Client
Administrator
Customer
HTTP/Respons
HTTP/GET
e
Server
ATM
Automated Teller Machine System
Project Code:
Project Name:
ATM-01
Automated Teller Machine
Smita
1. Introduction
1.1 Background
1.2 Purpose
1.3 Scope
2. Systems Overview
Administrator (A)
Customer (C)
2.1.2 Authorization
Database
Files
ATM Application
Client
Administrator
Customer
HTTP/Respons
HTTP/GET
e
Server
Smita
1. Introduction
1.1 Background
1.2 Purpose
1.3 Scope
2. Systems Overview
Administrator (A)
Customer (C)
2.1.2 Authorization
Database
Files
ATM Application
Client
Administrator
Customer
HTTP/Respons
HTTP/GET
e
Server
Smita
1. Introduction
1.1 Background
1.2 Purpose
1.3 Scope
2. Systems Overview
Administrator (A)
Customer (C)
2.1.2 Authorization
Database
Files
ATM Application
Client
Administrator
Customer
HTTP/Respons
HTTP/GET
e
Server
15-Sep-2011
Smita
1. Introduction
1.1 Background
1.2 Purpose
1.3 Scope
2. Systems Overview
Administrator (A)
Customer (C)
2.1.2 Authorization
Database
Files
ATM Application
Client
Administrator
Customer
HTTP/Respons
HTTP/GET
e
Server
Prepared by/Date
Reviewed by/Date
Approved by/Date
Smita
1. Introduction
1.1 Background
1.2 Purpose
1.3 Scope
2. Systems Overview
Administrator (A)
Customer (C)
2.1.2 Authorization
Database
Files
ATM Application
Client
Administrator
Customer
HTTP/Respons
HTTP/GET
e
Server
Revision History
Version
(x.yy)
1.00
Date of
Revision
Description of Change
Reason for
Change
Affected
Sections
Approved By
Initial Draft
Smita
1. Introduction
1.1 Background
1.2 Purpose
1.3 Scope
2. Systems Overview
Administrator (A)
Customer (C)
2.1.2 Authorization
Database
Files
ATM Application
Client
Administrator
Customer
HTTP/Respons
HTTP/GET
e
Server
Affected Groups
Development Engineering
Smita
1. Introduction
1.1 Background
1.2 Purpose
1.3 Scope
2. Systems Overview
Administrator (A)
Customer (C)
2.1.2 Authorization
Database
Files
ATM Application
Client
Administrator
Customer
HTTP/Respons
HTTP/GET
e
Server
Quality Assurance
XYZ Bank Of India
List of Reference Documents

Name
Version No.
1. Request For Proposal
1.2
Smita
1. Introduction
1.1 Background
1.2 Purpose
1.3 Scope
2. Systems Overview
Administrator (A)
Customer (C)
2.1.2 Authorization
Database
Files
ATM Application
Client
Administrator
Customer
HTTP/Respons
HTTP/GET
e
Server
2.
3.
4.
Smita
1. Introduction
1.1 Background
1.2 Purpose
1.3 Scope
2. Systems Overview
Administrator (A)
Customer (C)
2.1.2 Authorization
Database
Files
ATM Application
Client
Administrator
Customer
HTTP/Respons
HTTP/GET
e
Server
Table of Contents
1.
INTRODUCTION.................................................................................................................................................4
2.
SYSTEMS OVERVIEW......................................................................................................................................4
3.
SUB-SYSTEM DETAILS.....................................................................................................................................5
4.
DATA ORGANIZATION.....................................................................................................................................7
5.
ASSUMPTIONS....................................................................................................................................................8
Smita
1. Introduction
1.1 Background
1.2 Purpose
1.3 Scope
2. Systems Overview
Administrator (A)
Customer (C)
2.1.2 Authorization
Database
Files
ATM Application
Client
Administrator
Customer
HTTP/Respons
HTTP/GET
e
Server
6.
EXPECTATIONS..................................................................................................................................................8
7.
ACCEPTANCE CRITERIA................................................................................................................................8
8.
TRACEABILITY TO REQUIREMENTS.........................................................................................................8
9.
ACRONYMS AND GLOSSARY.........................................................................................................................9
Smita
1. Introduction
1.1 Background
1.2 Purpose
1.3 Scope
2. Systems Overview
Administrator (A)
Customer (C)
2.1.2 Authorization
Database
Files
ATM Application
Client
Administrator
Customer
HTTP/Respons
HTTP/GET
e
Server

ATM System Case Study

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

ATM System Case Study

Uploaded by

Copyright:

Available Formats

FUNCTIONAL SPECIFICATION

The Administrator should be able to add branch details of bank

The customer should be able to change their pin

The customer should be able to withdraw cash(Fast cash)

Authentication & Authorization

The application should handle logout (close all open database

4 Non functional Requirements

The application should be intuitive to use and easy-to-maintain

Each user will hold only one Customer_ID

7 Requirements Priority Table

8 Acronyms and Glossary

Automated Teller Machine System

List of Reference Documents

1. Request For Proposal

ACRONYMS AND GLOSSARY.........................................................................................................................9

You might also like