TITLE OF THE PROJECT

ONLINE BANKING
SYSTEM
Submitted by:

Group No. PR201201

Name : Shruthi.ks
Reg_no :102300757
Email_id :[email protected]

Name :Seema.mn
Reg_no :102300727
Email_id :[email protected]

Name : Roopa.mariya
Reg_no :102300753
Email_id :[email protected]

Under guidance of:

Internal guide: External guide:
Mr.Vinaychandra Mr.M.V.Arvinda Nayak.
Lecturer Project developer
St.philomena college Technopulse
Puttur Mangalore
 Chapter-1
SYNOPSIS

1.1.Introduction and Objectives

1.1.1.Introduction
Online banking is the wave of the future. It provides enormous benefits to
consumers in terms of ease and cost of transactions, either through
Internet,telephone or other electronic delivery.
Online Banking System is specifically developed for online banking for Balance
Enquiry, Funds Transfer to another account in the same bank, Loan details,
Request for cheque book/ change of address/ stop payment of cheques, Mini
statements (Viewing Monthly and annual statements).
 

1.1.2. Objectives
.
 The administrators have grates accessibility in collecting the consistent infor
mation that is very much necessary for the system to exist and coordinate.

 The system at any point of time can give the customers information related
to their :
 Accounts and accounts status
 The balance enquiry
 The fund transfer standards
 The cheque book request

 The system can provide information related to the different types of accounts

that are existing within the bank.

 The system can provide the bank administration with information on the
number of customers who are existing in the system.
  The system at any point of time can provide the information related to the
executed transactions by the customer.

 The system with respect to the necessities can identify all the history details
of thetrial participants along with their outcome of the results.

 The system with respect to the necessities can provide the status of research
and development process that is under schedule within the organization
currently.

 With proper storage of the data in a relational environment  the

system can applegate itself to cater to the standards of providing a clear and
easy path for future research standards that may arise due to organizational
policies

1.2. Project Category:

RDBMS (Relational Database Management System)

1.3.HARDWARE AND SOFTWARE REQUIREMENT

1.3.1. Software Specifications:

Technology Implemented : Apache Server
Language Used : PHP 5.3
Database : My SQL 5.5
User Interface Design : HTML, AJAX
Web Browser : Mozilla, Google Chrome, IE8

1.3.2. Hardware Requirements:

Operating System :Windows XP/ Windows 7/ Linux
Programming Language :PHP 5.3
Software : XAMPP Server

MySQL: MySQL is the most popular open-source database system

PHP: PHP stands for PHP: Hypertext Preprocessor

1.4. Scope
The project’s aim is to automate the system, pre-checking the inclusion of
allrequired material and automatically process the transactions used in a banking.
The criterions which include over here is to creation of an account and its all
respective perspectives. The data used by the system is stored in a database that
will be the centre of all information held about the customer and the base for the
remainder of the process after initial signing up been made. This enables things
to be simplified and considerably  quickened, making the jobs of the involved
people easier. It supports the current process but centralizes it and makes it
possible for decisions to be made earlier and easier way.

 To Manage large number of customer details with ease.

 T o M a n a g e a l l d e t a i l s o f t h e s t u d e n t w h o ar e r e g i s t e r e d w i t h
t h e b a n k a n d s e n d   appropriate details about latest policy of the bank to
each of its customer.

 To Create customer account and maintain its data efficiently and effectively.

 To View all the details of the customer.

 To Create a statistical report to facilitate the finance department work.

 To make Activities like updating, modification, deletion of records should be

easier

1.5. Process Description:

 Login module:
Introduction: This module allows valid customers to access the
functionalities provided by the bank.

 Admin module:
Introduction: Using this module Admin can log into the website. Admin
should enter correct username and password for entry into the system.
 My Accounts module :
Introduction: Stores the account details with respect to the bank.

 Fund Transfer module :

Introduction: This menu provide you to make fund transfers between your
different accounts as well as making a transfer to a third party. You can even
make an enquiry about your transfers and view the pending transfers through
this menu.

 Pay loans :
Introduction: This menu provides you with details about your loan accounts
such as Account Summary, Account Details, Query selection, etc.

 Check book request module:

Introduction: This menu help you to make request for a cheque book. You can
even check the status of your request in this menu.

 Personalize module:
Introduction: Personalize menu will help you in changing your password (both
login as well as transaction). You can even change the nick name of your
account from this menu.

 Logout Module:
Introduction: This module allows the user to logout from their account.

1.6. Data Flow Diagram(DFD) :

Data Flow Diagram is a graphical representation of a system or a portion of the

system. It consist of data flow, process, sources and sink and stores all the
description through the use of easily understandable symbols. DFD is one of the
most important modeling tools. It is used to model the system, components that
interact with the system, uses the data and information flows in the system. DFD
shows the information moves through the and how it is modified by a series of
transformations. It is a graphical technique that depicts information moves from
input or output. DFD is also known as bubble chart or Data Flows Graphs. DFD
may be used to represent the system at any level of abstraction.
DFD Level 0:

Customer
Enter user_id
Invalid and password
login_id Check login
and information Customer
password Login process

If valid

Customer
account
Retrieve
customer
information

Figure 1.1. DFD Level 0

1.7. ER Diagram
Entity relationship model is the high level conceptual data model. ER model helps
in depicting the entire problem requirement in the form of ER diagram. This is the
application development for any given problem.

Entity: an entity is anything that exits in the real world with an independent
existence.
E.g.: Employee, Department.

Attribute: The properties of an entity can be described as an attribute.

E.g.: Name, Address, Phone No etc.

Composite Attribute: The attributes that can be sub-divided into some

more attributes are called as composite attributes.
E.g.: An address is generally composed of street name, area, city, etc.
C
 customer_id

Figure 1.2. ER-Diagram.

 1.8. TESTING

1.8.1. Introduction:
A project is incomplete without successful testing and implementation. A program
or system design is perfect only when the communication between the user and the
designer is complete and clear. A successful system design helps in efficient
testing and implementation. Testing is vital to the success of the system.

1.8.2. Objective of Testing:

 Testing is a process of executing a program with the intent of finding

an error.
 A good test case is the one that has high probability of finding an as-
yet undiscovered error.
 A successful case is one uncovers as yet undiscovered error.

System testing is a stage of implementation, which is aimed at ensuring that the

system works accurately and efficiently as per the user needs, before the live
operation commences. As stated before the live operation commences. As stated
before testing is vital to the success of the system. System testing makes a logic
assumption that if all the parts of the system are correct, the goal will be
successfully achieved. The candidate system is subjected to a variety of tests. A
series of tests are performed before the system is ready for the user acceptance
tests.

1.9. Testing Techniques:

Different types of testing are:
 Unit Testing
 Integrated Testing
 Black Box Testing
 Validation Testing
 User Acceptance Testing
1.9.1.Unit Testing:

In this testing each sub module is tested individually with test data and then
integrated to the overall system. Unit testing focuses verification effort on the
smallest unit of the software design in the module or component. In fund flow
analysis all modules of the system are tested separately. The testing was carried out
during the coding stage itself. Each module was tested and it was being developed.
All the modules were correct for error and finally worked satisfactorily.

1.9.2.Integrated Testing:

This is a systematic technique for constructing the program structure while at the
same time conducting tests to uncover errors with interfacing. Data can be lost
across an interface; one module can have effect on other module; sub functionality
may not be achieved. The testing was done with simple data. The developed data
was run successfully with the test data. The need to integrate testing is to find
overall system performance. All modules are combined and tested as a whole. Here
errors uncovered are corrected for next testing steps.

1.9.3.Black Box Testing:

It focuses on the functional requirements of the software. Black Box testing

attempts to find errors in the following categories:

 Incorrect or missing functions

 Interface error
 Errors in external device access
 Performance error
 Initialization and termination errors
The above testing was successfully carried out for the developed system.

1.9.4.Validation Testing:

At the accumulation of integrated testing, software is completely assembled as a

package, interfacing errors have been uncovered and corrected, and final series of
software tests namely validation tests namely validation tests are performed.
Validation succeeds when the software functions in a manner that can be easily
accepted by the customer. After validation tests have been conducted, one of the
possible conditions is satisfied:
  The functions or performance characteristics confirmed to
specialization are accepted.
 The deviation from specifications is uncovered and a note of what is
lacking is made.
The developed system has been tested satisfactorily and is also satisfactory. It is
working efficiently.

1.9.5.User Acceptance Testing:

User acceptance testing is key factor for the success of any system. The system
under consideration was tested for user acceptance constantly, by keeping the users
informed of the progress and incorporated changes suggested, at the development
time itself.

1.10. Security Mechanism:

Only the account holder with user id and password can login and if at all the
password or user id is entered wrong thrice then the account will be blocked.
Password is encrypted with MD5 technology.

1.11. Scope:
The project’s aim is to automate the system, pre-checking the inclusion of all
required material and automatically process the transactions used in a banking. The
criterions which include over here is to creation of an account and its al respective
perspectives. The data used by the system is stored in database that will be the
center of all information held about the customer and the base for the reminder of
process after initial signing up been made. This enables things to be simplified and
considerably quickened, making the jobs of the involved people easier. It supports
the current process but centralizes it and makes it possible for decisions to be made
earlier and easier way.

1.12. Limitations :
 There is a chance of hacking if we login our account in browsing centers and
cyber and all.
 We cannot access or login to our account where there is no network.

1.13. Future Scope of the Project:

The present system is developing as web application. In future we would like to
develop it for portable devices like cell phones, wap or GPRS connections.
1.14. Conclusion :
Thus reaching to the conclusion of the synopsis we can say that the online banking
system project has made transactions very fast by a click. And this project has been
reduced manual work and we can sit at home and do all the transactions or check
account details etc….

1.15. Bibliography :
Website: http//google.com

Text books:
An Integrated approach to software engineering by Pankaj Jalote.