BANKING MANAGEMENT

SYSTEM

AP18110010468- B. Rajya Lakshmi

AP18110010491- T. Vani

AP18110010518- V. Mounika
 ABSTRACT
The main purpose of our project is to provide additional security while conducting
online transactions by providing valid authentication etc. In the existing system, we can perform
all operations using a single user id and password. Once this password is stolen, it becomes easier
for others to access all the functions such as transfers etc, so that the customer pays the biggest
losses. It is therefore not safe to tag. In our project, we offer greater security to customers while
using online banking service in the following ways. A customer using an online banking service
will be given a user id and two other passwords. One is called Login Password and the other is
called transaction password. By using the login password the customer can login to the account
and we can perform certain (limited) tasks such as viewing A / C balance and personal information
but only to make transactions or transactions online, the user needs to provide a transaction
password and other secure details to complete the transaction successfully.

If a customer’s login password and id are stolen by someone else, they can see the details but
cannot make an online transaction or transfer. In addition to the transaction password the customer
needs to be confirmed by providing the grid values available on the credit card that will be
requested at random. So there is no chance for a person who steals passwords to make a transaction
because he or she also needs to enter the numbers available on the customer's bank card.

The system after careful analysis has been identified to be presented with the following modules:

The modules involved are

1. Management.

2. User

3. Registration

4. Security and Verification

The " Banking" program is designed to overcome the problems that exist in the bookkeeping
orientation system. This software is supported to eliminate and in some cases reduce the complexity of
the existing program. In addition the program is tailored to the specific need of the company to
perform operations in a smooth and efficient manner. The app is minimized as much as possible to
avoid errors while entering data. It also provides an error message while entering invalid data. No
official information is required for the user to use this program. So all of this proves to be practical.
The Online Banking System, as described above, can lead to the management of a seamless, secure,
reliable and fast system. It can help the user to focus on other tasks instead of focusing on keeping
records. It will therefore help to streamline the better use of resources.

Every organization, whether large or small, has the challenges of overcoming and managing Bank,
Accounts, Transaction, Balance, Internet Banking. Every Online Banking System has different
Account requirements, so we create specialized employee management systems that fit your
management needs. This is to help you plan strategies, and will help you ensure that your organization
has the right level of information and details of your future goals. Also, for those busy managers who
are constantly on the move, our systems come with remote access features, which will allow you to
manage your employees at any time, at any time. These programs will ultimately allow you to better
manage resources.

Existing system with limitations:

In the current system, we can perform all tasks using a single user id password. If this password is
stolen it becomes easier for others to access all the functions such as transfers etc. Until now the
password will be set by the user and will be reset depending on the user's requirement which can be
easily hacked when there is no good security of your postal service so that the customer can pay for
significant losses. It is therefore not safe to tag.
Proposed system feature:

In our project, we offer greater security to customers while using online banking service in the
following ways.

A customer using an online banking service will be given a user id and two other
passwords. One is called Login Password and the other is called transaction password.

By using the login password the customer can login to become an account and we can
blow up certain (limited) tasks such as keeping A / C balance and personal details etc.

But to make a transaction or transaction online, you need to provide a transaction

If a customer login password and id are stolen by someone else, they can see the details but
can still make online transactions or transfers. In addition to the transaction password the customer
needs to be verified by providing the grid values available on the credit card to be randomly asked

So there is no chance for a person who steals passwords to make a transaction because he
or she also needs to enter the values available on the customer's bank card.

In the proposed system we will be able to give the user the opportunity to make the postal service more
secure by creating a random password each time he wants to sign in and encrypting a random
password will be sent to the user's post id where he will provide a link to transfer his written password
to email.

Acronyms and Abbreviations:

ACC:Account

Pwd:password

Uid:user id

Facc:From Account

Tacc:To Account
 SYSTEM REQUIREMENTS

DFD SYMBOLS:
In DFD, there are four symptoms

1. A square defines a source (founder) or area of system data

2. The arrow indicates the flow of data. It is a pipe through which information flows

3. A circle or foam represents a process that converts incoming data flow into outgoing data flow.

4. Rectangular open data store, data at rest or temporary data repository

Source or Destination of data

Data flow

Data Store

CONSTRUCTING A DFD:

Many of the six rules are used to design DFD's:

The process should be named and numbered to make it easier to identify. Each word should represent
a process.
2. Direction of flow from top to bottom and from left to right. Data usually flows from source to
destination even though it may return to the source. One way to show this is to draw a long flow line
back to the source. One way is to repeat the source sign as your destination. Used more than once in
DFD it is written in a short diagonal.

2. When the process explodes into low-level data, they are not counted.

3. The names of the stores and locations are written in capital letters. Process and flow of data are the
first letters of each capitalized function

DFDs usually show less content in a data store. Each data store must contain all data items that flow in
or out.

Questionnaires should contain all the data items that flow in and out. Lack of non-existent social
media and liking is often calculated through conversations.

ZERO DFD:
DFD-1:

USE CASE DIAGRAMS:

The use case describes a sequence of actions that give something of value to the
character and is drawn as an ellipse horizontal character, person, organization, or external system
that plays a role in one or more sharing of your character.

Its purpose is to describe the Piece of morality. Defines both internal (use case) and external
(character)

System behavior. Describes what the system does.

These drawings contain:

• Actors

The case for using action sequence specifications, including different sequences and error
sequences, which can be performed by a program, sub-system or category in collaboration with
external actors.

A character can be anything that works with a system, a person, a hardware device or another
program etc.
DATA DICTIONARIES:
CLASSDIAGRAMS:
The class diagram describes the vertical structure of the symbols in your new
system. It is a clear introduction to the static concept that reflects the collection of descriptive
(vertical) model elements, such as classes, genres, and content and relationships. Classes are
arranged in sequence sharing structure and common behavior, and are associated with other classes
OBJECT DIAGRAM:
SEQUENCE DIAGRAMS:

UML sequence diagrams model the flow of ideas within your system in a visual way, allowing
you to both write and use your logic, and is often used for analytical and design purposes.
Sequential drawings are the most popular UML art objects of dynamic modeling, focused on seeing
performance within your program.
Collaboration Diagram

State chart Diagram

Activity diagrams are used to record the work flow in a system, from the business level down
to the operational level. If you look at the job diagram, you will see things from the state diagram,
the job diagram is a variation of the state diagram where the "provinces" represent performance,
and the change represents the activities that take place when the work is completed. The general
purpose of Work Drawings is to focus on the flow of internal processing compared to external
events.
Component Diagram

Deployment Diagram
 System Testing and Implementation

TESTING CONCEPTS:

• Testing
Testing Methodologies

 Black box Testing:

• Levels of Testing
 Unit Testing.
 Module Testing.
 Integration Testing.
 System Testing.
 User Acceptance Testing.

Levels of Testing:

Module1 Module2 Module3

I/p Integration o/p I/p Integration o/p

System Testing: Presentation + business +Databases

UAT: user acceptance testing

Conclusion:
Here we provide security and authentication of online bank account, for the customers, managers and
cashiers who are using the online banking service will be provided with a user id and password. By
using the login password the customer can login to the account and we can perform certain (limited)
tasks such as viewing A / C balance and personal information but only to make transactions or
transactions online, the user needs to provide a transaction id to complete the transaction successfully.
Sample Screenshots
THANK YOU!