Problem statement

Banking is an important part of our day to day life. Almost every person
has a bank account whether he is an employee or a student or an
employer.
When we go in a bank to deposit and withdraw money, people have to
stand in long queues for each and every kind of transaction in the bank.
Online banking helps people to corporate up with this situation. They
can do any kind of transaction just sitting anywhere when we are
traveling about and want to do transaction in our account, the problem
arise how to do the task. Through online banking we can solve this
problem. We can do transaction in our account sitting in any part of the
world.
Moreover a lot of paper work is required when we use traditional
banking system. Moreover it is quite hectic to keep the record of bank
account manually.
Automation would help to reduce the paper work and would be less error
prone as compared to the traditional system of banking. Automation of
traditional banking system will help us to access our bank account 24*7
or round the clock.
 Use Case Diagram

Manage user
Account

Service Update

Branch Detail
Vie
w Branch
Administr Bank Employee
Manager
ator
Login

Account
opening
Update

Account Detail
Update View

Transaction
Employe Customer
Report
e
Generation

Report view

Service view
 USE CASE TEMPLATES

(A) Login

1. Brief Description : This use case describes how a

user login into the online banking system.

2. Actors: Administrator, Manager, Bank employee,

customer.

3. Flow of events
3.1 Basic Flow : If username & password is correct
the particular actor logs into the system.
3.2 Alternative Requirement: If username &
password is not correct the particular actor can’t
enter into the system.
4. Special Requirements: These are includes
success or failure scenario.
5. Pre Condition: Actors have username & password.
6. Post Condition: Username & password are valid or
not.
7. Related use case: user account management
system.

(B) Branch detail

1. Brief Description: This use case describes about

the branches of the bank

2. Actors: Administrator, customer.

3. Flow of events
3.1 Basic Flow:
3.2 Alternative Requirement: .
4. Special Requirements: These are includes
success or failure scenario.
5. Pre Condition: Actors have username & password.
6. Post Condition: Username & password are valid or
not.
7. Related use case: user account management
system .
1. Brief Description: This use case describes how a
user into the online banking system.

2. Actors: Administrator, Manager, Bank employee,

customer.

3. Flow of events
3.1 Basic Flow: If username & password is correct
the particular actor logs into the system.
3.2 Alternative Requirement : If username &
password is not correct the particular actor can’t
enter into the system.
4. Special Requirements : These are includes
success or failure scenario.
5. Pre Condition : Actors have username & password.
6. Post Condition : Username & password are valid or
not.
7. Related use case : user account management
system .
1. Brief Description : This use case describes how a
user into the online banking system.

2. Actors : Administrator, Manager, Bank employee,

customer.

3. Flow of events
3.1 Basic Flow : If username & password is
correct the particular actor logs into the system.
3.2 Alternative Requirement : If username &
password is not correct the particular actor can’t
enter into the system.
4. Special Requirements : These are includes
success or failure scenario.
5. Pre Condition : Actors have username & password.
6. Post Condition : Username & password are valid or
not.
7. Related use case : user account management
system .
1. Brief Description : This use case describes how a
user into the online banking system.

2. Actors : Administrator, Manager, Bank employee,

customer.

3. Flow of events
3.1 Basic Flow : If username & password is
correct the particular actor logs into the system.
3.2 Alternative Requirement : If username &
password is not correct the particular actor can’t
enter into the system.
4. Special Requirements : These are includes
 success or failure scenario.
5. Pre Condition : Actors have username & password.
6. Post Condition : Username & password are valid or
not.
7. Related use case : user account management
system .

1. Brief Description : This use case describes how a

user into the online banking system.

2. Actors : Administrator, Manager, Bank employee,

customer.
3. Flow of events
3.1 Basic Flow : If username & password is
correct the particular actor logs into the system.
3.2 Alternative Requirement : If username &
password is not correct the particular actor can’t
enter into the system.
4. Special Requirements : These are includes
success or failure scenario.
5. Pre Condition : Actors have username & password.
6. Post Condition : Username & password are valid or
not.
7. Related use case : user account management
system .
1. Brief Description : This use case describes how a
user into the online banking system.

2. Actors : Administrator, Manager, Bank employee,

customer.

3. Flow of events
3.1 Basic Flow : If username & password is
correct the particular actor logs into the system.
3.2 Alternative Requirement : If username &
password is not correct the particular actor can’t
enter into the system.
4. Special Requirements : These are includes
success or failure scenario.
5. Pre Condition : Actors have username & password.
6. Post Condition : Username & password are valid or
not.
7. Related use case : user account management
system .
1. Brief Description : This use case describes how a
user into the online banking system.

2. Actors : Administrator, Manager, Bank employee,

customer.

3. Flow of events
3.1 Basic Flow : If username & password is
correct the particular actor logs into the system.
3.2 Alternative Requirement : If username &
password is not correct the particular actor can’t
enter into the system.
4. Special Requirements : These are includes
success or failure scenario.
5. Pre Condition : Actors have username & password.
6. Post Condition : Username & password are valid or
not.
7. Related use case : user account management
system .

1. Brief Description : This use case describes how a

user into the online banking system.

2. Actors : Administrator, Manager, Bank employee,

customer.

3. Flow of events
3.1 Basic Flow : If username & password is
correct the particular actor logs into the system.
3.2 Alternative Requirement : If username &
 password is not correct the particular actor can’t
enter into the system.
4. Special Requirements : These are includes
success or failure scenario.
5. Pre Condition : Actors have username & password.
6. Post Condition : Username & password are valid or
not.
7. Related use case : user account management
system .

1. Brief Description : This use case describes how a

user into the online banking system.
2. Actors : Administrator, Manager, Bank employee,
customer.

3. Flow of events
3.1 Basic Flow : If username & password is
correct the particular actor logs into the system.
3.2 Alternative Requirement : If username &
password is not correct the particular actor can’t
enter into the system.
4. Special Requirements : These are includes
success or failure scenario.
5. Pre Condition : Actors have username & password.
6. Post Condition : Username & password are valid or
not.
7. Related use case : user account management
system .
1. Brief Description : This use case describes how a
user into the online banking system.

2. Actors : Administrator, Manager, Bank employee,

customer.

3. Flow of events
3.1 Basic Flow : If username & password is
correct the particular actor logs into the system.
3.2 Alternative Requirement : If username &
password is not correct the particular actor can’t
enter into the system.
4. Special Requirements : These are includes
success or failure scenario.
5. Pre Condition : Actors have username & password.
6. Post Condition : Username & password are valid or
not.
7. Related use case : user account management
system .
Report Generation

1. Brief Description : This use case describes how a

user logs into the rental book management system.
2. Actors : Administrator, Student, Librarian, Data
entry operator.

3. Flow of events
3.1 Basic Flow : If username & password is
correct the particular actor logs into the system.
3.2 Alternative Requirement : If username &
password is not correct the particular actor can’t
enter into the system.
4. Special Requirements : These are includes
success or failure scenario.
5. Pre Condition : Actors have username & password.
6. Post Condition : Username & password are valid
or not.
7. Extension Point:-

1. INTRODUCTION

The main purpose that banks have been serving since their inception is
keeping our money safe for us. While keeping our money safe, they also
let us earn a certain amount of interest on the money deposited with
them. Traditional banks have been doing this, and internet banks
continue the same function. The only difference is in the way the
transactions are made.

We all know about internet banking and most of us use it quite often as
well, but few of us actually understand about the history of internet
banking and how it all came out. Knowing the history of internet
banking can be incredibly useful, especially since it will allow us to have
more respect for the little things that we take for granted.
Computers themselves have really come an enormous way since their
initial establishment, as the earliest electronic computers were so large
that they would take up the entire area of a room, while today some are
so small that they can hardly be seen at all.

In today's world, computers play an incredibly large role in the way the
world exists in general, and the majority of tasks could actually not be
completed if not for the use of computers. Although there are certainly
some areas and jobs that cannot yet be completed solely by computers
and which thus still require actual manpower, for the most part,
computers have helped to make life significantly easier, productive, and
more convenient for us all.

Internet banking has been around for quite a few years now, but has
really only become prominent over the past year or so in particular.
Internet banking offers an array of different advantages to the user,
including: account balances and history including year-to-date
information, the ability to transfer money from one account to another
and to payees for bill payments, check history, reorders, and stop
payments, check credit card balances and statements, complete online
loan applications, secure interactive messaging with staff, and much
more.

Internet banking basically allows you to be able to do everything that

you can in your regular banking institution, only with the benefit that
you can do it all right from the convenience of your own home. Not only
is this great because you can be comfortable and have peace of mind
knowing that you can keep track yourself of all your banking issues, but
as well it allows for more ease because you never have to worry about
rushing out and making it to the bank.

1.1 PURPOSE OF THE STUDY

The aim of this project is to develop a secured online banking system
with the following objectives:

· Create a banking system that is easily accessible by customers from the

comfort of their homes, offices etc.

· Reduce the flow of human traffic and long queues at banks

· Reduce the time wasted in going to banks to stay on queues.

· Promote efficient and effective banking for the banks by focusing on

those services that still require physical presence at the banking hall.

1.2 SCOPE OF THE STUDY

The scope of this project is limited to the activities of the operations unit
of the banking system which include opening of Account, Deposit of
funds, Withdrawal of funds and transfer.
Definition acronyms and abbreviation

“In the 21st century there will be a lot of banking, but there will be no
banks.
“Says Bill Gates.

The term "online banking" or "internet banking" covers both computer

and telephone banking. Using computer banking, a customer either uses
his computer to dials directly into its bank's computer or gains access to
the bank’s computer over the internet.

Using telephone banking, the customer can controls its bank

accounts by giving the bank instructions over the telephone. Both
computer and telephone banking involve the use of passwords which
give access to the customer’s accounts.
Using these methods, banking transactions can be actioned 24 hours a
day. Online banking allows the person, for instance, to view recent
transactions, print out statements and transfer funds between accounts
and make payments.

Many banks also have the facility for someone to set up, amend or
cancel standing orders. Internet banking also allows payments to be
made to the customer, i.e. acceptance of credit card donations. Most
people that use internet banking will also continue to use some of the
elements of more traditional methods of banking, such as a cheque book.

1.4 References

• Software Engineering- K.K.Agarwal

• Fundamentals Of Software Engineering- Rajib Mall

• Software Engineering A practitioner’s Approach- Roger S.

Pressman

• Software Engineering- Pankaj Jalote

• IEEE Recommended Practice for Software Requirement

Specifications- IEEE Std 830-1993
1.5 Overview
As the world becomes more of a global village being runned by
paperless systems, the idea of a cashless society is the hope of the future.
Thus more innovations will still evolve which will make cashless
transactions easily accessible and affordable.

3.Enter 6.User
book request
details processed
7.Report
generati
on