Ebank Report
-
Upload
nitin-sharma -
Category
Documents
-
view
222 -
download
0
Transcript of Ebank Report
8/6/2019 Ebank Report
http://slidepdf.com/reader/full/ebank-report 1/38
1
ONLINE BANKING SYSTEM
Submitted in partial fulfillment of the requirements
for the award of the degree of
Bachelor of Technology
In
Computer Science Engineering
Guide(s): Submitted by:
Ms. Preeti Dhaka Nitin Sharma
Enroll - 0371562707
Northern India Engineering College,
Shastri Park, Delhi-54
(2007-11)
8/6/2019 Ebank Report
http://slidepdf.com/reader/full/ebank-report 2/38
2
Certificate
This is to certify that the dissertation/project report (ETCS 457) entitled
³ONLINE BANK ING SYSTEM´ done by
Mr. NITIN SHARMA, Roll No.- 0371562707, is
an authentic work carried out by him at NORTHER N INDIA ENGG.COLLEGE
under my guidance. The matter embodied in this project work has not been submitted
earlier for the award of any degree or diploma to the best of my knowledge and belief
Signature of the Guide:Date:
Ms. Preeti Dhaka
Lecturer,
CSE Department, NIEC
8/6/2019 Ebank Report
http://slidepdf.com/reader/full/ebank-report 3/38
3
ACKNOWLEDGEMENT
I would like to take this opportunity to express my gratitude towards all the people who
have in various ways, helped in the successful completion of my project.
I must convey my gratitude to my guide Ms. Preeti Dhaka for giving me the constant
source of inspiration and help in preparing the project, personally correcting my work and
providing encouragement throughout the project.
I also thank all my faculty members for steering me through the tough as well as easy phases of the project in a result oriented manner with concern attention.
8/6/2019 Ebank Report
http://slidepdf.com/reader/full/ebank-report 4/38
4
ABSTRACT
About Project
E-banking is one of the most challenging tasks in computer science for many reasons.
First, the number of end-users of this complex system is extremely high as e-payment
concerns the whole world. Second, financial transactions must be as secure as possible to
limit frauds while providing a fast service to users. Finally, the banking infrastructure
involves many different technologies in Electronics (smartcards, payment terminal) and
IT (server, networks etc.).
In this world of competitive environment and technological advances, most banks have
totally computerized their working methodology, and the rest have started planning to
incorporate it so as to increase their customer base. This rapid development has given rise
to a concept called as e-banking (also known as net banking or online banking). With
this concept the bank wants to move very nearer to the customers and increase its basic
operational strategies. Through e-banking the Bank wants to introduce the core concept
of IT based Enabled Services (ITES).
All the user interfaces has been designed using the basic HTML, CSS , Javascript andJSP. The database connectivity is planned using the ³Oracle 10g express edition´. The
standards of security have been maintained through the use of SSL (socket security
layer), a technology which enables 128-bit encryption. The application takes care of
different modules and their associated reports.
8/6/2019 Ebank Report
http://slidepdf.com/reader/full/ebank-report 5/38
5
CONTENTS
1. Introduction«««««««««««««««««« ..7
2. Requirements Analysis «««««««««««««..8
3. Design«««««««««««««««««««« ..13
4. Tools and Technologies used«««««««««««.21
5. Testing ««««««««««««««««««««24
6. System Implementation & Maintenance ««««««.27
7. Future Scope««««««««««««««««««31
8. Conclusion«««««««««««««««««««32
9. Bibliography«««««««««««««««««« .33
10. Appendix«««««««««««««««««««..34
8/6/2019 Ebank Report
http://slidepdf.com/reader/full/ebank-report 6/38
6
INTR ODUCTION
Online banking, also known as e banking , is a process by which a customer may perform
banking transactions through Internet without needing to visit the actual branch of a bank.
The following terms all refer to one form or another of online banking :
y Personal computer (PC) banking,
y Internet banking,
y Virtual banking,
y E banking,
y Home banking.
Banks having been providing online services to customers for years through software
programs. These software programs allowed the user¶s personal computer to dial up the
bank directly. In the past however, banks have been very reluctant to provide their
customers with banking via the Internet due to security concerns.
Today, banks seem to be jumping on the bandwagon of Internet banking. Why is there a
sudden increase of bank interests in the Internet? The first major reason is because of the
improved security and encryption methods developed on the Internet. The second reason
is that banks did not want to lose a potential market share to banks that were quick to
offer their services on the Internet.
8/6/2019 Ebank Report
http://slidepdf.com/reader/full/ebank-report 7/38
7
REQUIREMENTS ANALYSIS
3.1 EXISTING SYSTEM
In the Bank every Activity is handled manually, such as Opening Account, storing
Account holder Details, Transaction Details, and Reports Generation. The manual system takes
more time and the services to the customers are slow and more error prone.
The online banking system is designed for financial institutions to deal with their basic banking
services. The system allows customers to open accounts, view account balances and statement
details, transfer funds between accounts and change personal information and passwords. Any
customer is able to scan interest details, dong with frequently requested information for checking,
savings, and certificate of deposit accounts quickly and easily without interacting with bank
clerks. In addition multiple users can access it at the same time, rather than personally standing in
queues for ATM or banking clerks.
The online banking system provides access 24 hours a day to customers' accounts information.
Therefore, customers can enjoy the convenience of financial controls of their accounts through
Internet.
8/6/2019 Ebank Report
http://slidepdf.com/reader/full/ebank-report 8/38
8
3.2 PR OPOSED SYSTEM
To make online comprehensive solution to manage Internet banking.
Only those customers who already have one or more accounts in the bank will be able to
register for Online Banking services. This service will be accessible to all customers who
have a valid Customer reference no (given when a customer opens his first account in the
bank). After receiving the registration form from receiver, his password is generated by
an automatic process. The customer is notified with his password and asked to change it
on the spot.
This system provides the following facilities:
y Balance Enquiry
y Funds Transfer to another account in the same bank
y Request for cheque book/change of address/stop payment of cheques
y Viewing Monthly and annual statements.
Project justifies the need of computerization which is used to act as the interface which
provides following activities:
y Time Saving ± Customer don¶t have to stand in long queues and be physically
present in a bank branch.
y Convenience - All the banking transactions can be performed from the comfort
of the home or office or from the place a customer wants to.
y 24 x 7 availability ± Customers can access their accounts at any time and use
various services.
y Speed. The response of the medium is very fast; therefore customers can even
check their balances after performing fund transfer almost instantly.
y Security. It provides the security & secure data accessing. SSL security and
various encryption techniques are utilized to make the system & transaction
more secure.
8/6/2019 Ebank Report
http://slidepdf.com/reader/full/ebank-report 9/38
9
3 .3 REQUIREMENTS
FUNCTIONAL REQUIREMENTS
i. Customer must have a valid Customer reference no. and password to login to the
system.
ii. If a wrong password is given thrice in succession, that account will be locked and
the customer will not be able to use it. When an invalid password is entered a
warning is given to the user that his account is going to get locked.
iii. After the valid user logs in he is shown the list of accounts he has with the bank.
iv. User can request details of the transactions he has performed. A report can also be
taken of this.
v. User can make a funds transfer to another account in the same bank. User is
provided with a transaction password which is different from the login password.
vi. User can transfer funds from his account to any other account with this bank. If
the transaction is successful a notification should appear to the customer, in case it
is unsuccessful, a proper message should be given to the customer as to why it
failed.
vii. User can request for cheque book/change of address/stop payment of cheques
viii. User can view his monthly as well as annual statements. He can also take print out
of the same.
NON FUNCTIONAL REQUIREMENTS
i. Secure access of confidential data (user¶s details). SSL can be used.
ii. 365 X 24 X 7 availability.
iii. Flexible service based architecture will be highly desirable for future extension.
8/6/2019 Ebank Report
http://slidepdf.com/reader/full/ebank-report 10/38
10
3.4 FEASIBILITY STUDY
A feasibility study is defined as an evaluation or analysis of the potential impact of a
proposed project. It is conducted to assist decision makers in determining whether or notto implement a project. It is based on extensive research on both the existing practices
and the proposed practices. For few projects, technical feasibility may be very important,
however, for most of the projects, feasibility depends on non-technical issues.
Feasibility Considerations:
y Economic Feasibility:
Economic feasibility is most frequently used technique for evaluating the effectiveness of a proposed system. More commonly known as cost/benefit analysis; the procedure is to
determine the benefits and savings that are expected from a proposed system and
compare them with costs. If benefits outweigh costs, a decision is taken to design and
implement the system otherwise; further justification or alternative in the proposed
system will have to be made if it is to have a change of being approved. This is an
ongoing effort that improves in accuracy at each phase of the system life cycle.
As online banking is bound to increase the customer base of the bank, this project is
economically feasible.
y Technical Feasibility:
It means whether the work for the project can be done with current hardware
equipments, existing software technology and available personnel? If new technology is
needed, what is the likelihood that it can be developed?
This project can be easily developed using the hardware equipments available in the
market and existing software technology. We have used JSP technology and Oracle as
database server which are one of the most secure technologies of these times. Java has
been used in various projects for almost two decades and it may very well carry on the
load of the projects which needs extra security such as online banking. So, from future
point of view also, it is technically feasible.
8/6/2019 Ebank Report
http://slidepdf.com/reader/full/ebank-report 11/38
11
3.5 USE CASE DIAGRAM
Report generation
Update address and
other details
Login
View a/c summary,
Balance
View a/c statement
Cheque book issue
User
Administrator
Stop payment of
cheque
Fund Transfer
Change Password
8/6/2019 Ebank Report
http://slidepdf.com/reader/full/ebank-report 12/38
12
3.6 ER DIAGRAM
Customer
Cr no Password
Has Account
A/c type Balance
Performs Through
Transaction
A/c no
TidTdate
Amount
A/c
1
n
1
1
n
n
Has
Branch
1
n
Branch City
8/6/2019 Ebank Report
http://slidepdf.com/reader/full/ebank-report 13/38
13
DESIGN
3.1 SYSTEM DESIGN
In Analysis of the System, we have seen what a system should do. In System Design
phase the emphasis will be on how to do what a system should do.
There are two main approaches to design:
1. Data Centered Approach.
2. Process Centered Approach
The present project is designed based on Data Centered Approach as the modern school
of thinking on this subject is that if data is organized effectively the processes can always
be designed in such a way that the data is made available to them.
The principle of Object Oriented Design (OOD) is adapted where designing is defined as
a collection of data and its associated characteristics (processes) as objects. These objects
are inline with real life objects.
Data Structured approach is being adapted since data can be associated with physical
structures which can see and feel and it is therefore logical to start with data rather than
processes which are invisible--. They are there, but processes cannot be touched or felt.
Logical Design deals with aspects of design which can be implemented on any operating
environment i.e. one need not know on which machine or operating system or database
the system is going to be working.
In physical design, the output of logical design is implemented using the features of a
particular environment.
8/6/2019 Ebank Report
http://slidepdf.com/reader/full/ebank-report 14/38
14
DESIGN OF PR OCEDURE
Software design is both a process and a model. The design process is a sequence of steps
that¶s enable the designer to all aspects of the software to be built. Basic design principles
enable the software engineer to navigate the design process. The design should be
traceable to the analysis. Independence is measured using two qualitative criteria:
Cohesion and Coupling. Cohesion is a measure of the relative functional strength of a
module. Coupling is a measure of the relative interdependence among modules
PR OCESS FLOW
A defined process is followed for the module activities that include Addition of new
Member (either Guide or Trainee), Projects, and Modules etc-
This process is as below:
y At start up the Home Page will open .
y In Home Page all the basic link will be available like login for customer,information of organization, New user registration form, e.t.c
y If the user has CR no. he/she can enter in his/her account from the customer login page.
y After logging in, user can do online transaction, request for cheque book etc whileadmin can view and generate reports.
y Online TPN User can change their address; see the account statement, balance of their account and use other services.
8/6/2019 Ebank Report
http://slidepdf.com/reader/full/ebank-report 15/38
15
3.2 DATA FLOW DIAGRAM
DFDs show the flow of data from external entities into the system, showed how the data
moved from one process to another, as well as its logical storage.
y Level 0 DFD(Context diagram)
E-Banking
SystemUser
Data
Administrato
Server Database
Retrieve
Admin id/password CR no/ Password
8/6/2019 Ebank Report
http://slidepdf.com/reader/full/ebank-report 16/38
16
y Level 2 DFD
8/6/2019 Ebank Report
http://slidepdf.com/reader/full/ebank-report 17/38
17
y Level 3 DFD
Administrator Customer Login
Enter cr no,
password
Enter admin id,
password
Server Database
Login
Retrieve login
info
A/c summary Server Database
Retrieve a/c
details
View ac
summary
Customer
Account summary
Fund Transfer Customer
Enter source and
recipient a/c and
amount Server Database
Retrieve balance
details in source ac
if balance > 1000 ,
update database
if balance < 1000 ,
no fund transfer
Fund Transfer
8/6/2019 Ebank Report
http://slidepdf.com/reader/full/ebank-report 18/38
18
Customer Cheque
Book issue
Request for
cheque book Server Database
Issue Cheque Book
Request stored in
database
Update
Details Server Database
Enter new
details
Customer
Update Address and other details
Fund Transfer Customer
Enter old as well
as new password
Server Database
Retrieve old
password
Otherwise , update
database with new
password
if cust (old pwd)
not equals DB(old
pwd), no change
Change Password
Database updated
8/6/2019 Ebank Report
http://slidepdf.com/reader/full/ebank-report 19/38
19
3.3 DATABASE DESIGN
y ACCOUNT_DETAILS
y CUST_DETAILS
Foreign key ->
Foreign key ->
8/6/2019 Ebank Report
http://slidepdf.com/reader/full/ebank-report 20/38
20
y BRANCH_LOCATIONS
y TRANSACTION_DETAILS
cust_details
cr (pk)
pwd
account_details
ac (pk)
cr (fk)
branch(fk)
branch _details
branch (pk)
city(fk)
transaction_details
tid, ac (pk)
tdate
balance
8/6/2019 Ebank Report
http://slidepdf.com/reader/full/ebank-report 21/38
21
CONSTR UCTION
4.1 TECHNOLOGIES USED
y JAVA SER VER PAGES(JSP)
y SER VLET
y HTML
y JAVASCRIPT
y CASCADING STYLE SHEETS(CSS)
y JAVA BEANS
y JDBC (java database connectivity)
y SQL
4.2 TOOLS USED
y MYECLIPSE 7.5 (it is an IDE ± integrated development environment)
y ORACLE ( it is an RDBMS- relational database management system)
y TOMCAT 6.X ( web server)
y CSS3 MENU (software to create menus)
ORACLE R DBMS
� Oracle driver²oracle.jdbc.driver.OracleDriver
Database URL
� Oracle JDBC ThinDriver²jdbc:oracle:thin:@hostname:port :database.
The default Oracle port is 1521.
DYNAMIC WEB CONTENT (SERVLET & JSP)
Design of interactive & dynamic web pages was an evolutionary step in web history.
As the server became more complicated and versatile, paradigms like CGI (Common
Gateway Interface) and Microsoft¶s ASP gave servers the ability to dynamically generate
HTML files in response to user input. The client browser also became more
sophisticated, accepting and running small programs (applets and ActiveX controls).
8/6/2019 Ebank Report
http://slidepdf.com/reader/full/ebank-report 22/38
22
However, most server-side programming was limited to single-threaded, resource-
intensive executables (e.g., CGI systems), or to specific vendors and hardware platforms
(e.g., Netscape¶s Livewire server-side scripting). Client-side programming suffered from
slow download times, insecure environments, and incompatible interfaces.
Sun introduced Java Servlets as a means of leveraging the multiplatform nature of Java
for server-side programming. Servlets are compiled Java classes that are executed and
maintained by a Servlet container. Unlike traditional CGI programs, a Servlet can have a
life cycle greater than an individual page. In other words, Servlets can share resources.
Servlets are also designed to take advantage of state, or the ability to maintain user data
over extended periods of time.
JavaServer Pages
(JSPs) extend this functionality by allowing you to build web pages that are converted to
Servlets at runtime. The advantage of JSPs over Servlets is that the outer Servlet
framework is still available, yet you can develop HTML and Java interchangeably with
rapid turnaround. Once the HTML has been freed from the confines of pure Java code,
development of the web application can proceed along the natural division lines:
y Back-end functionality (Java)²Back-end components can be built and tested as
stand-alone Java classes (or EJBs). These classes can be built without any thoughtto web display or any knowledge of web languages such as HTML, DHTML, or
JScript.
y Application functionality (Servlets and/or JSP)²Application controllers or page-
specific components can be built as either Servlets or JavaServer Pages.
y Interface and Display (JSP, HTML, XML, etc.)²The purely visual and
interactive components can be built with traditional web tools such as HTML,
incorporating Java where necessary. The web developers do not necessarily need
to know or work with Java.
Although JavaServer Pages and Servlets share many capabilities, JSP is not a
replacement for Servlets. In fact, you can think of a JavaServer Page as a Servlet that has
been turned inside-out. The Servlet encapsulates the entire page in a stand-alone Java
8/6/2019 Ebank Report
http://slidepdf.com/reader/full/ebank-report 23/38
23
class. The JSP exposes the raw HTML and encapsulates the Java code in a set of HTML-
like tags. Thus, Servlets are better suited to application flow control and JSPs are better
suited to the building of interface and display components.
8/6/2019 Ebank Report
http://slidepdf.com/reader/full/ebank-report 24/38
24
TESTING
5.1 IN
TR ODU
CTION
Testing is the process of executing a program with the intent of finding errors. Testing
performs a very critical role for quality assurance and for ensuring the reliability of
software. The results of testing are used later on during maintenance also.
TESTING OBJECTIVES
The aim of testing is to find errors. We should .not test a program to show how it works;
rather we should start with the assumption that the program contains errors and then test
the program to find as many errors as possible. We can say,
y Testing is a process of executing a program with the intent of finding an error.
y A successful test is one that uncovers an as yet undiscovered error.
y A good test case is one that has a high probability of finding error, if it exists.
5.2 LEVELS OF TESTING
In order to uncover the errors present in different phases we have the concept of levels of
testing. The basic levels of testing are as shown below
y UNIT TESTING
Unit testing focuses verification effort on the smallest unit of software i.e. the module. It
is the process of taking a module and running it in isolation from the rest of the software
product by using prepared test cases and comparing the actual results with the results
predicted by the specifications and design of the module.
8/6/2019 Ebank Report
http://slidepdf.com/reader/full/ebank-report 25/38
25
In this project each service can be thought of a module. There are so many modules like
Login, BankAdmin, Transactions, New User etc. Giving different sets of inputs has tested
each module when developing the module as well as finishing the development so that
each module works without any error. The inputs are validated when accepting from the
user. In this application developer tests the programs. Unit testing is first done on
modules, independent of one another to locate errors.
y INTEGRATION TESTING
After the unit testing we have to perform integration testing. The goal here is to see if
modules can be integrated properly, the emphasis being on testing interfaces between
modules. This testing activity can be considered as testing the design and hence the
emphasis on testing module interactions.
In this project integrating all the modules forms the main system. When integrating all
the modules we have checked whether the integration affects working of any of the
services by giving different combinations of inputs with which the two services run
perfectly before Integration.
y SYSTEM TESTING
Here the entire software system is tested. The reference document for this process is the
requirements document, and the goal as to see if software meets its requirements.
Here entire µOnline TPN¶ has been tested against requirements of project and it is
checked whether all requirements of project have been satisfied or not.
8/6/2019 Ebank Report
http://slidepdf.com/reader/full/ebank-report 26/38
26
ACCEPTANCE TESTING
Acceptance Test is performed with realistic data of the client to demonstrate that the
software is working satisfactorily. Testing here is focused on external behavior of the
system; the internal logic of program is not emphasized.
In this project we have collected some data and tested whether project is working
correctly or not. Test cases should be selected so that the largest number of attributes of
an equivalence class is exercised at once. The testing phase is an important part of
software development. It is the process of finding errors and missing operations and also
a complete verification to determine whether the objectives are met and the user
requirements are satisfied.
8/6/2019 Ebank Report
http://slidepdf.com/reader/full/ebank-report 27/38
27
IMPLEMENTATION AND MAINTENANCE
6.1 INTR ODUCTION
In the Implementation Phase, the project reaches completion. After the
development phase of the SDLC is complete, the system is implemented. Any hardware
that has been purchased will be delivered and installed.
The System development life cycle during the implementation phase, both the
hardware and the software is tested. Although the programmer will find and fix many
problems, almost invariability, the user will uncover problems that the developer has
been unable to stimulate. This leads on to the sixth and final stage.
SITE PREPARATION
A crucial phase in SDLC is the successful implementation of the system;
implementation simply means bringing the new system into operation. Due to our well-
written documentation and user training methods developed by the experts will aid the
user staff so that they can use the system efficiently and effectively.
For this we need Tomcat web server and Oracle 10g express edition (RDBMS).
The site will be deployed on the web server from where clients will be able to access it
using their web browsers.
8/6/2019 Ebank Report
http://slidepdf.com/reader/full/ebank-report 28/38
28
6.2 SECURITY ISSUES
If there is one issue which has always pestered the computer software fraternity then
that is that of security. No matter what one does there always has been someone looking
for ways to break that security wall that has been built for the software. The security issue
has been categorized in three sections:
y Hacking
y Natural catastrophe
For the hacking purpose, we have made our site enabled with SSL (socket
security layer).It provides a 128 bit encryption for the data transferred between client and
server. Therefore, all the transactions take place in encrypted form which can¶t be hacked
easily. This issue has cropped up so as to facilitate online transaction. .
As far as to prevent natural catastrophe, which can destroy our servers, we have multiple
servers which are continuously updated and are different geographical places. With these
security measures we hope to counter any security breaches. Still, security on Internet is a
tricky issue so we keep our self-updated on this front and make necessary technical
changes as and when required.
8/6/2019 Ebank Report
http://slidepdf.com/reader/full/ebank-report 29/38
29
6.3 MAINTENANCE
Software maintenance is the last phase in the software Engineering process that
eliminates errors in the working system during its work span and to tune the system to
any variations in its working environment. The system requires maintenance as there may
be changes and requirements in the organizational needs, government policies, hardware
and software environment etc. often small system deficiencies are found as a system is
brought into operation and changes are made to remove them. System requirements may
be revised as a result of system usage or changing operational needs. Perhaps oversight
that occurred during the development process needs to be corrected. Often the
maintenance need arises to capture additional data for storage in a database or in
transaction files or perhaps it may be necessary to add error detection features to preventsystem users from in adversely taking an unwanted action.
Maintenance of the system after it is installed is concerned with an additional
factor in hardware. Once the system is delivered and installed there is a brief warranty
period during which time the vendor is responsible for maintenance. This is a typically a
90 day period after that time the purchaser has the option of acquiring maintenance from
various sources. Maintenance source excepting vendor is also available from companies
specializing in providing the service, called third party maintenance companies.
When the system is installed, it is generally used for long period. The average
life of system is 4-6 years, with the eldest applications often is used for over 10 years.
The need for debugging and correcting errors or failure on an emergency basic is
comparatively low: less than 20% of the task of correction. System and organization are
in constant state of flux; therefore the maintenance of the system also involved adoptions
for earlier version of software.
8/6/2019 Ebank Report
http://slidepdf.com/reader/full/ebank-report 30/38
30
Approximately 20% of all maintenance work is performed to accommodate changes in
report, files and database. The greatest amount of maintenance work is for user
enhancement,
improved documentation and recording system components or greater efficiency. About
60% of all maintenance is for this purposed.
The broad classes of maintenance found in development of information systems:
y Corrective Emergency fixes, routine debugging.
y Adaptive Accommodation of changes to data and to hardware and
software, changes in the external environment.
y Perfective User enhancement, improved documentation recording of
computational efficiency, user recommendations for new capabilities.
y Preventive Routine service of transactions & inquiry prevent breakdowns,
future maintainability reliability enhancement, recovering design information to
improve the overall quality.
MAINTAINABLE DESIGN
The points to reduce the needs for maintenance are:
y More accurately defining the user¶s requirements during the system
development.
y Assembling better system documentation.
y Using more effective methods for designing process logic and communicating it
to project team members.
y Making better use of existing tools and techniques.
y Managing the system engineering process effectively.
8/6/2019 Ebank Report
http://slidepdf.com/reader/full/ebank-report 31/38
31
FUTURE SCOPE OF THE PR OJECT
At present this project provides the following functionality:
y The project provides a relatively secure login and private data transaction is
maintained due to the use of encryption technique SSL.
y A customer can view details of all his savings bank accounts in the bank
y He can view balance, account statements of the transactions done.
y Other features include fund transfer within the accounts of TPN bank, issue of
cheque book, update address and other details, change password etc.
y Various forms such as new user registration form can be downloaded.
In the future this project can be enhanced to include the following:
y Making login more secure by incorporating virtual keypad feature so that no
one can trace fingerprints as was the case when userid and password are entered
through normal keyboard.
y Online Fund transfer to the accounts in other banks.
y Fixed deposit accounts can be opened using online banking.
y
View Credit card. Debit card cum ATM card details.
y Incorporate the features of online bill payment and online shopping.
8/6/2019 Ebank Report
http://slidepdf.com/reader/full/ebank-report 32/38
32
CONCLUSION
The primary purpose of this project is to replace the existing manual processing with
error free, high speed, low cost and user friendly online banking system.
This is a well defined job of our team that has taken seven weeks to analyze the situation
in which this project will work. It was a good experience for us to work in a team group
that has a very friendly environment and learning atmosphere.
Working on the project was good experience. I understand the importance of Planning
and designing as a part of software development. But it¶s very difficult to complete the
project for a single person. Developing the project has helped us some experience on
real-time development procedures. Well, it¶s my pleasure to make project based on ³E-BANK ING´. .
8/6/2019 Ebank Report
http://slidepdf.com/reader/full/ebank-report 33/38
33
BIBLIOGRAPHY
In this project, we consulted many books and also took help from world wide web. Following are
some references-
BOOK S CONSULTED:
y CodeNotes for J2EE by Gregory Brill
y J2EE tutorials from Sun Microsystems
y Tomcat Documentation
SITES REFERRED:
y www.online.ingvysysa.com
y www.onlinesbi.com
y www.w3schools.com
y www.java.sun.com
y www.4shared.com
y www.javaworld.com
y www.google.co.in (any thing else was searched using Google search engine)
8/6/2019 Ebank Report
http://slidepdf.com/reader/full/ebank-report 34/38
34
APPENDIX
There are only four symbols used in DFD notation:
1. Squares representing external entities, which are sources or destinations of data.
2. Rounded rectangles(or oval shaped) representing processes, which take data as
input, do something to it, and output it.
3. Arrows representing the d ata flows, which can either be electronic data or
physical items.
4. Open-ended rectangles representing d ata stores, such as databases or XML files
and physical stores such as or filing cabinets or stacks of paper.
External entities
8/6/2019 Ebank Report
http://slidepdf.com/reader/full/ebank-report 35/38
35
SNAPSHOTS
8/6/2019 Ebank Report
http://slidepdf.com/reader/full/ebank-report 36/38
36
8/6/2019 Ebank Report
http://slidepdf.com/reader/full/ebank-report 37/38
37
8/6/2019 Ebank Report
http://slidepdf.com/reader/full/ebank-report 38/38