You are on page 1of 5

<Project Name> Version: <1.

0>
Software Requirements Specification Date: <14/sep/08>
Team name:kitsmca09

Kakatiya Institute of Technology and Science

Internet Banking System


Software Requirements Specification
Version <1.0>

Team Name
kitsmca09

Team Members:
Vinod Kumar Kanaparthi
Samuel Sheelam
Venkata Ram Kumar
Nagaraju Kirna

Project Guide
Bhaskar Adepu

<kitsmca09>, 2008 Page 1


<Project Name> Version: <1.0>
Software Requirements Specification Date: <14/sep/08>
Team name:kitsmca09

Table of Contents
1.1 Purpose: In traditional banking system of a bank must go to that bank to perform
transactions like 3
1.2 Scope: 3
1.1 Definitions, Acronyms and Abbreviations 4
1.2 References 4
1.3 Technologies to be used 5
1.4 Overview 5

2. Overall Description 5
2.1 Use-Case Model Survey 5
2.2 Architecture diagram & database design 5
2.3 Assumptions and Dependencies 5

3. Specific Requirements 5
3.1 Supplementary Requirements 5

4. Supporting Information 5

5. Concerns / Queries / Doubts if any: 5

<kitsmca09>, 2008 Page 2


<Project Name> Version: <1.0>
Software Requirements Specification Date: <14/sep/08>
Team name:kitsmca09

Software Requirements Specification

Introduction

1.1 Purpose: In traditional banking system of a bank must go to that bank


to perform transactions like
• Funds Transfer from one account to another account in the same bank,
• Requesting a cheque book,
• Requesting edit of his address,
• Requesting stoppage of cheque payment.
For transactions like balance enquiry the customer can go to bank or it’s ATM.
Using internet banking system we can perform all the above transactions securely
without going to bank i.e.through internet by building a website thereby saving
time and effort.

1.2 Scope:
The system to be built has seven users.They are
 Administrator
 Customers
 Industrialists
 Enterpreneuers
 Organisations
 Acadamicians

 Administrator enables all other users of the system to use


the system by assigning them userid and password.
 Administrator stores the information of all other users
profiles.
 Administrator informs a valid user his id or password
when that user loses his password or his userid
 Customer logs in to the website by his userid and
password

<kitsmca09>, 2008 Page 3


<Project Name> Version: <1.0>
Software Requirements Specification Date: <14/sep/08>
Team name:kitsmca09

 Customer can view type of accounts he has with the


bank
 Customer can view balance in his accounts
 Customer can transfer funds from his account to another
account within the same bank
 Customer can request for change of address,cheque
book,stop payment of cheque.
Industrialist logs in with his userid and password.
Industrialist can transfer salaries

1.1Definitions, Acronyms and Abbreviations

1.2References
Problem definition(provided by IBM)
Software Engineering By Roger s.Pressman
Sample SRS(provided by IBM)

<kitsmca09>, 2008 Page 4


<Project Name> Version: <1.0>
Software Requirements Specification Date: <14/sep/08>
Team name:kitsmca09

1.3Technologies to be used
Uml
J2ee
Xml
Ajax
Web 2.0
Web services
SOA
DB2
1.4Overview

2.Overall Description
2.1Use-Case Model Survey

2.2Architecture diagram & database design

2.3Assumptions and Dependencies

3.Specific Requirements
3.1Supplementary Requirements

4.Supporting Information
5.Concerns / Queries / Doubts if any:

<kitsmca09>, 2008 Page 5