Online Banking System

Published on February 2017 | Categories: Documents | Downloads: 53 | Comments: 0 | Views: 199
of 24
Download PDF   Embed   Report

Comments

Content


PROJECT REPORT
on
Online Banking System





Submitted by:

Avishek Laha
Mrinmoy Purkayastha
Debapriya Sengupta
Soniya Vijaywargi
Madhusree Datta




Under guidance of :
Mr Naushad Akhtar














ACKNOWLEDGMENT



We take this occasion to thank God, almighty for blessing us with his grace and
taking our endeavour to a successful culmination. We extend our sincere and
heartfelt thanks to our esteemed guide, Mr.Naushad Akhtar for providing us with the
right guidance and advice at the crucial junctures and for showing us the right way.
We extend our sincere thanks to our capgemini group, for allowing us to use the
facilities available. Finally, we thank all those who have helped us directly or indirectly to
collect information for completing this project successfully.































Table Of Contents


Chapter Contents
1 Introduction
1.1 Purpose
1.2 Intended Audience and Suggestions
1.3 Existing System
1.4 Proposed System
2 Feasibility Study
3 Requirement Analysis and Specification
3.1 Functional Requirement
3.2 Other Non-Functional Requirements
4 Analysis and Design
4.1System Design
4.2 ER Diagram
4.3 Database of our Project
4.4 Snapshots of Modules
5 Future Scope
6 References














1. INTRODUCTION
1.1. Purpose

This project aims at creation of a secure Internet banking system. This will be
accessible to all customers who have a valid User Id and Password. This is an
approach to provide an opportunity to the customers to have some important
transactions to be done from where they are at present without moving to bank. In this
project we are going to deal the existing facts in the bank i.e.; the transactions which
takes place between customer and bank. It provides a real time environment for the
existing system in the bank. Through this system, the customer can use all the services
provided by bank in a second, since our project is an internet based computerized
approach.

1.2 Intended Audience and Reading Suggestions
This document is intended to be read by the developer team, project managers HCL
group Members, user SBIT. This is technical document and terms should be
understood by the customer. This SRS is designed for the persons present in this
whole project so that they come to know about project and what to change in the
project in future if want, such as :

 Developers: As different modules of a project are developed by different
members of a team. So to have knowledge of other modules of the project SRS
are designed. So that an individual member of a team come to know about the
whole modules of the project.

 Project Managers: Members who are going to manage this project must
know about the project that’s why this SRS is designed. So that the members
can manage the project according to its design.


 Marketing Staff: What the developed software/project can do, what was its
need, how it can be helpful to the users all this information’s are provided to the
marketing staff through this SRS. Through that a good marketing can be
provided to the project and its marketing price will be good.

 Users: Through this SRS the user come to know about the benefits of the
project and how to gain full performance from the project.

 Testers: The different tests through which the software/project must
undergo are described in SRS.

 Documentation writers: Different modules are designed by different
members, so the different logics are gathered together to develop a
software/project. In that case entry of a new member in the project will make
him confused so through documentation one can understand the logic behind
that. So this document is intended for the documentation writers also.


1.3 Existing system
The organization which is providing the overall information works manually.

1.3.1 Limitations of existing systems
The existing system is facing few limitations:
 The manual process of Statistics calculation using the statistical method is
error prone.
 Lack of data security.
 Does not have future estimation static’s.

1.4 Proposed system
Though the proposed system does not answer all the above mentioned

drawbacks, it certainly answers many. These suggested solutions will tackle all
major issues related to opening of account, transferring, viewing, updating the
status with minimal overheads.

USERS OF THE SYSTEM : 1.Administrator 2.Customers

MODULE - 1 : ADMINISTRATOR


REGISTER AN ACCOUNT

 The customer registers for new account and submit the form after filling it.
Upon successful submission, the customerid will be generated of a particular
customer through which he can login.
 When user login for the first time, he is allowed to use various services
provided by bank.

ACCOUNT :

 This section allows administrator to block a customer account.
 Then after no transaction is possible with that account.
This section allows administrator to approve the account requests by the
customer.


VIEW DETAILS OF AN ACCOUNT:

 It provides the facility to view the complete list of a customer

SEARCH:

 It provides the administrator to search the customer with their name and
branch name.






MODULE - 2: CUSTOMERS

USER ID & PASSWORD:

 To login to this online system, Customers must have a valid User Id and
password.
 Customer can change his password. For this he can click the 'Change
Password' link.

ACCOUNT DETAILS:

Customer can request for new account creation
 Customer can view his account details.
 Customer can see account statement from today to a specified no. of days.

CHANGE PASSWORD:

 Customer can change his password using this facility. He has to submit
current password and new password.



2. Feasibility Analysis

Feasibility Analysis of a project is performed with the aim to determine that whether it
would technically and economically feasible to undertake the project. In other words,
is there sufficient resources, technical and economical, available to develop the
product. It involves the analysis of the problem and collection of all the relevant
information relating to the project such as inputs to the system, processing of the
inputs, the output required to be produced by the system and various constraints on
the behaviour of the system.

Feasibility Analysis is mainly of two types:


1) Technical Feasibility: Technical feasibility refers to the analysis that
whether the technical support required to develop the product is available in
sufficiency or not. In this, we opted for the J2EE platform to develop the
product because it seemed ideal for the project to be developed in J2EE
platform due to its unmatched features and very much user-friendliness.
Moreover, using HTML, JSP to develop the front-end provide an excellent
layout to the project. At the back-end, Oracle 10g express edition as the
database as it in the most commonly used database and most people could
access it with ease. Thus, it is quite obvious that the project is technically
feasible.

2) Economic Feasibility: Whether the project to be undertaken is economically
feasible or not is determined by the Economic Feasibility Analysis. It involves
the study that if there is sufficient finance available to complete the project. It is
quite obvious that in order to develop a product, technical backup alone is not
sufficient. Adequate capital is very much necessary for the successful
completion of the project. Moreover, it also has to be determined that whether
the capital spent on developing the project would fetch handsome returns or
not; otherwise there is no point in developing the product, if it does not fetch
any profit at all. In this case, the software is scheduled to develop with
optimized cost in order to make the project economically feasible.

3. Requirement Analysis and Specification (SRS):
The purpose of this SRS (Software Requirements Specification) document is to
provide a detailed description of our software project, specifications, and goals. This
document describes the features included that are included in our project, its user
interface, and its functionality. The application is to be fully-functional bank software.
It will consist of a few different modules. The first module is to be a software
application that can be used by bank customers. This application will allow the user

to deposit, withdraw funds, check balance, and transfer funds. The second module is
to be a software application that is used within the bank by the bank tellers and
managers. This application will allow everything the ATM allows as well as some
additional features. These features include: account creation, account deletion,
customer records, and reports. Both pieces of software will be linked to a central
bank server. This server will handle multiple threads and will therefore allow for
simultaneous access of multiple users. It will provide for user authentication and will
store all data.

3.1 Functional Requirements
 The database must be in a workable state.
 The registered users must have a valid userid for getting login.
 It should be easy for the novice user.
 There should be proper interconnectivity between different pages in the
website.
 Different commands for different functions will ensure reliability.

3.1.1 External Interface Requirements
User Interfaces
The internet banking system has a simple User Interface which has the following
components:-

1. User sign-in panel

The registered users have to sign in for browsing our website and also can give
feedback.

2. New user Sign-up panel

To add a new user to the system.



3.1.2 Hardware Interfaces
Processor - Intel inside Pentium-III
Hard Disk - 80 GB
RAM - 512 MB
Processor speed - 2.6 GHZ

3.1.3 Software Interfaces

Web Server - Apache Tomcat 6.0
Web Technologies - Java, JSP, Struts2.0
Database – OracleXE



Apache Tomcat
Apache Tomcat is an open source web server and servlet container developed by
the Apache Software Foundation (ASF). Tomcat implements the Java Servlet and
the JavaServer Pages (JSP) specifications from Sun Microsystems, and provides a
pure Java HTTP web server environment for Java code to run in. Apache Tomcat
includes tools for configuration and management, but can also be configured by
editing XML configuration files.

JavaServer Pages
JavaServer Pages (JSP) is a technology that helps software
developers create dynamically generated web pages based on HTML, XML, or
other document type. JSP is similar to PHP, but it uses the Java programming
language. JSP can be used independently or as the view component of a

server-side model–view–controller design, normally with JavaBeans as the
model and Java servlets (or a framework such as Apache Struts) as the
controller. JSPs are usually used to deliver HTML and XML documents, but
through the use of OutputStream, they can deliver other types of data as well.

Struts2.0
Apache Struts is an open-source web application framework for
developing java EE web applications. It uses and extends the Java Servlet
API to encourage developers to adopt a model-view controller (MVC)
architecture. The goal of Struts is to separate the model (application logic that
interacts with a database) from the view (JSP pages presented to the client)
and the controller (instance that passes information between view and model).
Struts provides the controller (a servlet known as ActionServlet) and facilitates
the writing of templates for the view or presentation layer.

OracleXE

A database management system (DBMS) such as Access, FileMaker Pro, Oracle or
SQL Server provides you with the software tools you need to organize that data in a
flexible manner. It includes facilities to add, modify or delete data from the database,
ask questions (or queries) about the data stored in the database and produce reports
summarizing selected contents.
OracleXE is a multithreaded, multi-user SQL database management system(DBMS).
The basic program runs as a server providing multi-user access to a number of
databases. The data is stored in database objects called tables. A table is a
collections of related data entries and it consists of columns and rows. Databases are
useful when storing information categorically.

3.2 Other Non-functional Requirements
3.2.1 Performance Requirements
The internet banking system should be able to support multiple users at a
time.
3.2.2 Security Requirements
Any system developed should be secured and protected against possible
hazards. Security measures are provided to prevent unauthorized access of the
database at various levels. Password protection and simple procedures to
prevent the unauthorized access are provided to the users .The system allows
the user to enter the system only through proper user name and password.
3.2.3 Software Quality Attributes
This application can be used in all sectors where the file transfer is an
important task to be performed. Some of its quality attribute includes:-

1. Checking:- Authentication Checking: With this checking, the system will
not allow unauthorized user to perform functionalities that he/she does not
allowed to do.

2. Portability: - The internet banking system must be portable between
Microsoft Windows and Linux.

3. Maintainability: - The internet banking system should be modular.
Specifically, file contents should be easy to maintain as the contents of the
database change often.

4. Performance: - The internet banking system should be able to support
multiple users at a time.


4. Analysis and Design

4.1 System Design


System design provides the understanding and procedure details necessary for
implementing the system recommended in the system study. Emphasis is on
translating the performance requirements into design specifications. The Design
phase is a transition from a user-oriented document (system proposal) to a
documented oriented to the programmers or database personnel. Systems design is
the process or art of defining the architecture, components, modules, interfaces, and
data for a system to satisfy specified requirements. One could see it as the
application of systems theory to product development. This project has to design and
implement a software for the purpose of preparing cashbook. The system must be
designed to retrieve from a database browser and display the results in a formatted
manner. Any modifications to the data must also be done through an interface
provided by the browser.

4.1.1 ARCHITECTURAL DESIGN

It defines the relationship between major structural elements of the program.
This design representation the modular framework of a computer program can
be derived from the analysis models and the interaction of the subsystems
defined within the analysis models. The primary objective is to develop a
modular program structure and data structure, defining interfaces that enable
the conceptual view of software product. This means performing a number of
tasks that such as decomposing the specification into software modules,
indentifying the interfaces and interconnections among the functions and sub
functions, identifying the data used and passed among the functions and
finally identifying where data is stored.
The basic architecture for the proposed system is like that



Fig. 4.1.1 Architectural Diagram

Presentation Layer: All the JSP and HTML pages are designed in this tier.
Business Layer: All the business logic and service code are written here.
DAO Layer: All the database connections and resultset related codes are written here

4.2 E-R Diagram

E-R diagrams are simple and clear quality that may well account in large part for
widespread use of the ER model such a diagram consists of major components.
 Rectangles, which represents entity sets.
 Elipses, which represent attributes.
 Diamonds, which represent relationship sets.
 Lines, which link attributes to entity sets and entity sets to relation sets.
 Double ellipses, which represent multivalued attributes.
 Dashed elipses, which represents derived attributes.

 Double lines, which indicate total participation of an entity in a relationship set.
 Double rectangles, which represent weak entity sets.
E-R diagram of e – Accommodation system representing the user, admin and
various process involved is:




Fig. 4.2 ER Diagram





4.3 Databases of our project (Table Structure):-

4.3.1 Customer database

Table Name : customer_table
Description : used to store the details of end users.



4.3.2 Account database

Table Name : account_table
Description : used to store the details of account of different customers.







4.3.3 Transaction database

Table Name : transaction_table
Description : used to store the transaction details of a particular customers.





4.3.4 User database

Table Name : user_table
Description : used to store the specific details of a customers.










4.4 Snapshots and Modules



Fig. 4.4.1 Home Page





Fig. 4.4.2 Login Page





















Fig. 4.4.3 Registration Page



Fig. 4.4.4 Customer Activities Page



Fig. 4.4.5 Account Creation Page



Fig. 4.4.6 Account Activities Page


5. SCOPE FOR FUTURE WORK

 We would like to implement e-mail facilities as soon as transaction happens
from an account holder’s account.
 Also, message alerts to the customer mobile number can be implemented in
the future.
 We would like to explore the intricacies of inter and intra account fund transfer









6. REFERENCES

This is a list of resources used in preparing this project.this sites have been gone
through for getting informtion about various functions.

 http://php.net/manual/en/function.mysql-query.php


 http://www.w3schools.com/php

 http://www.stackoverflow.com

 www.mysql.com/click.php?e=35050

 www.apache.org/

























Sponsor Documents

Or use your account on DocShare.tips

Hide

Forgot your password?

Or register your new account on DocShare.tips

Hide

Lost your password? Please enter your email address. You will receive a link to create a new password.

Back to log-in

Close