TABISH HAIDER RIZVI 2K11 / IT / 083 IV SEMESTER

CONTENTS
I. II. III. IV. V. VI. VII. Software Requirement Specification (SRS) Data Flow Diagram (DFD) Data Dictionary Entity Relationship (ER) Diagram Class Diagram Use Case Diagram Sequence Diagram

Software Requirement Specification (SRS)

Outline:
1. Introduction

Purpose Definitions, Acronyms, Abbreviations References Product Perspective Product Functions User Characteristics Constraints Assumptions and Dependencies External Interface Requirements Features Performance Requirements Design Constraints Software System Attributes Other Requirements

2. Overall Description

3. Specific Requirements

1. INTRODUCTION This document is to provide the software requirement specification of the computerized solutions for certain banking services. It keeps track of the account holders details.
1.1 PURPOSE:

The main purpose of this software is to enable the easy maintenance of account holders details, their transaction etc.
1.2. SCOPE:

The software has the ability to keep a track on the account holders details.
1.2.1. Benefits:

Saves time. Reduce errors. Customer friendly. Provides fully automated banking services. Efficient functioning of the bank.

1.2.2. Objectives:

1.3 DEFINITIONS, ACRONYMNS, ABBREVIATIONS:

DFD: Data Flow Diagram Sequence Diagram: A Diagram that shows the sequence of occurrence of activities. Class Diagram: A Diagram consisting of all classes and their relationship with each other. JVM: Java Virtual Machine J2EE: Java 2 Enterprise Edition

1.4 REFERENCES:

Software Engineering- by KK Aggarwal

2. OVERALL DESCRIPTION
2.1 PRODUCT PERSPECTIVE:

The Bank Management System is an application that remains to be independent. The system interfaces, user interfaces and the hardware interfaces related with this software are defined below:
2.1.1 Hardware Interfaces:

The consumer will use a home computer or a terminal installed at the bank. The bank side software will also use PC configured with windows XP/7/8, Linux, and Mac.
2.1.2. System Interfaces:

The client system must be able to share the data available in the database through the network.
2.1.3. User Interfaces:

The screen formats and the menu structure should be in such a way that the user should find it easy to use the product. The product should be userfriendly. The functionality provided by the system like displaying error messages should adapt itself to the different users of the product.
2.1.4. Hardware & Memory Constraints:

The PC must have USB 2.0 ports or a CD/DVD drive. The memory of the system must be above 256MB. The system must also have a working internet connection for the working of the software.

3. SPECIFIC REQUIREMENTS
3.1 EXTERNAL INTERFACE REQUIREMENTS: 3.1.1. User Interfaces:

The interface used in GUI must be easy to understand. This interface serves as a bridge between the user and the software. It also makes the user interaction with the system easy. The user interface includes: Screen formats / Organizations: The introductory screen will be the first to be displayed which allows the user to log in using their id and password. Windows formats / Organizations: When the user chooses a particular topic then the information pertaining to that topic will be displayed in a new window, which will allow multiple windows to be available on the screen, and the user can switch between them. Data Format: The data entered by the user will be alphanumeric.

End Message: When there are some exceptions, error messages will be displayed promptly by the user to re-enter the details when an event has taken place successfully.

3.1.2 Communication Interfaces

The client and server will be communicating through the internet via a Transmission Control Protocol of the TCP/IP Suite. This protocol is particularly suited for this application because it is a connection oriented protocol that allows for an ordered and reliable delivery of packets. The use of a non connection oriented protocol would not be well suited for this application due to the complications of dropped packets and unordered delivery of packets.

3.1.3. Hardware interfaces:

The system must basically support certain hardware and these must be an interface between them.

NAME OF THE ITEM

DESCRIPTION OF PURPOSE To get the details of from the user. To print the details of the account holder.

SOURCE OF INPUT / DESCRIPTION OF OUTPUT Source of input

Keyboard

Printer

Destination of output

3.2 FEATURES: 3.2.1 Server Requirements

The server shall load data at startup The server shall save data at shutdown

The server shall save account and user data anytime it is modified (i.e. after a deposit, withdraw, creation of account, etc.) The server shall handle requests in a separate thread

The server shall lock accounts/user to prevent errors due to simultaneous access The server shall properly handle client requests The server shall handle simultaneous access to join accounts

3.2.2 Bank Client Requirements

The client shall require user authentication in order to perform any operations.

 The client shall send requests to the server to complete basic bank operations (withdraws, deposits, transfers, and balance checks) The client shall send requests to the server to complete user/account related operations (create/remove user, create/remove account) The client shall allow user passwords to be changed The client shall be able to print monthly/yearly reports of accounts

3.2.3 Terminal Software Requirements (END User)

The software shall present an error message if the user enters invalid login information and allow the user to attempt a login again. The ATM shall allow customers to deposit/withdraw/transfer money and check balances of accounts
3.3 PERFORMANCE REQUIREMENTS

A large database for storing the records. The system shall run with multiple threads. The system shall be free of deadlock relating to the multiple threads.

The system shall be able to support ten users with no user experiencing more than a one second lag.
3.4 DESIGN CONSTRAINTS

The software must be valid and accessible only by authorized users. The Banking Software documentation shall use IEEE standard 830-1993.
3.5 SOFTWARE SYSTEM ATTRIBUTES 3.5.1. Reliability:

The factors needed to establish the software expected reliability are: The user inputs should be valid and within the given range Normal termination of the program

3.5.2. Availability:

The factors that generate the software availability include proper termination and correct input details. Also the resource used for the project development is Microsoft certified which speaks of the high quality standards.
3.5.3. Security:

It must ensure that the access is provided to authorized users only through password. The user of the service will provide network security.

3.5.4. Maintainability:

Implementing the concept of modularity, which in turn reduces the complexity involved in maintaining it, will develop the software.
3.5.5. Portability:

The application is very adaptable; it can be used in different computer systems with different operating systems and folders.

3.6 OTHER REQUIREMENTS

[NONE]

Data Flow Diagram (DFD)

LEVEL 0 DFD (Context Level):

LEVEL 1 DFD:

Data Dictionary

Data element description Name of customer/employee

Internal name Name

Permissible values (a-z) and (0-9), special characters (a-z) and (0-9), (0-9) Any character Any character (0-9) (0-9) Any character (a-z) and (0-9) (0-9) Any character

Unique ID Phone number Place of residence Email address Credit card number Account no of customer Loan No Cheque Number Rate of interest Pass book

ID phone Add email CC AC LN CN RI PB

Class Diagram

Use Case Diagram

Sequence Diagram