1 Project

report

Acknowledgement

We hereby grab an opportunity to express our gratitude towards the

esteemed organization VSPACE SOFTWARE , Pune, for providing us
an excellent environment & facilities in order of completion of our
project.

.
I am very thankful to Mr. Saurav Sharma who gave us so many
key skills to get complete our project and helped us in learning many
things related to the project.

I am also thankful to all my friends and team members.

Last but not the least we thanks all the concern one’s who directly or
indirectly helped us in completing our project.

Kundan Kumar
 2 Project
report

Index

1. Abstract 3

2. Introduction 10

i. Existing system 11
ii. Proposed system 12

3. Analysis 14

i. Feasibility study 15

1. economic 16
2. technical 17
3. behaviors 18

ii. Structure analysis 19

1. System chart 20
2. DFD 23

4. Designing phase 29

i. Input forms 30
ii. Output forms 39
iii. Data base 50

5. Design & Specifications 51

6. Testing 57

7. Conclusion 65
 3 Project
report

8. Bibliography 67
 4 Project
report

This project is about the e-banking of the IMPERIAL BANK. The

project has the complete information regarding the services provided,
account details (including withdrawl, transfers, summary etc), its network
across the country. It also contains the information about the different
customers opening their account at the various Centers. This project also
helps to keep the information about all the details of The various
customers who have opened their account with the company. In this
project the various centre’s of banking are connected through the network
and if the responsible Person of the company such as (GM or MD) wants
to get the full Information about the facilities being provided by the bank,
then he can do so easily.
Modules of project:
The project can be divided in to nine main modules.

• loans
• online services
• deposits
• Insurance
• Branch locator
 5 Project
report

1. loans:
This module store the information regarding the various loans on offer
now. We have three loans namely HOME LOAN, PERSONAL LOAN.
Under HOME LOANS we have home, land and home equity loans which
have their own eligibility criteria’s and the loan amount. Sanctioning will
only be done after the verification is complete. Now taking loans is made
simple by just filling up a form which is available online for downloads
free of cost. Once the form is filled and sent to any of the branches listed
on the site, verification will begin
within 3 working days and only after full verification the loan process
will begin. The customer at any point of time can change/withdraw his
application for loan.

2. online services:
This module works with the online payment of bills. The customer has to
just sit at his house and get the comfort of paying his bills online. Under
online services we have paying of bills, charity, shopping online and
tickets. The only requirement is that the customer should have an
INTERNET ID. This can be applied for online also. The amount will get
deduced from the customer’s account immediately. Bill payment includes
 6 Project
report

electricity, phone, mobile, insurance premium etc. An extra feature which

has been added o this site is that if the customer wants he can allow the
bank to pay his bills on a regular basis without him worrying. A reminder

will also be sent to his account once the payment is done and once before
the payment is to be done. IMPERIAL bank has many esteemed partners
like EBAY, INDIAN RAILWAYS, AIR DECCAN, REDIFF etc and
many other companies which facilitate online shopping.
For charity also the partners are FIVE INDIA, THE CLAUSE,
VOLUNTEER, INFOCHANGE etc.

3. deposits:
This department deals with the different kinds of accounts a customer can
retain namely: savings, current, fixed deposits, multiple and recurring.
The customers can open such accounts online also but only after
verification. The criteria’s and features for different types of accounts
have been provided and one can read them before creating an account,
say for example a fixed deposit account will repay a customer a higher
amount than a savings account.
 7 Project
report

4. Insurance:
In this section the customers are provided with 2 types of insurance life
and general. General consists of motor, health and home. Motor
insurance consists of both 2 and 4 wheeler. Claiming conditions are given
under which these insurances can be claimed. These insurances can be
bought online by applying for it.
5. Bonds:
Under this section 2 kinds of bond schemes are embedded non taxable
and taxable.8% savings (taxable) bond schemes are issued in demat
form and tax shall be deducted at source. Schemes are available at
multiples of Rs.1000/-.customers can apply online by visiting the RBI
website. 6.5% savings(non taxable) bond schemes are repayable after
expiration of 5 years. Premature encashment is allowed after
minimum lock-in period of 3 years from the date of issue.
6.Branch locator:
The various ATM branches and the various branch centers can be
located using this section. The customer can just type in the name of the
city to get the names of the exact branches in that particular city .

Objective of the project:

 8 Project
report

1. To give all the facilities to a customer as soon as he/she opens an

account with the INDIAN OVERSEAS bank such as loans, deposits,
insurance etc.

2. To get the full information of a particular customer regarding his

account details, withdrawal, transfers etc accessing his account from
anywhere in the country.
3. To help our customers pay all his/her bills online through this site.
He/She can pay for tickets, charity, online bills, can shop online.
4. To help the customers get full comfort and facilities while working on
the net without even having to come to the respective branches for daily
requirements.

Scope of the project:

This project has the following scope.

1. Administrator has full information about a particular customer because
the database is in his hands and can see any particular record through the
database.
2. Online updating of customer details.
3. Online shopping of items, tickets, charity and paying of bills .
4. Customer can complaint and contact us online about the different
features being posted online. A 24 hrs calling service has been provided
which the customers can use to contact the customer service.
 9 Project
report

5. Online downloading of different forms for issuing ATM cards,

applying for different kinds of loan, opening different kinds of accounts,
bonds and insurance.
 10 Project
report

Existing System till 1990’s

Study of the existing system before the 1990’s showed that the
banks generally didn’t go online to communicate with the customers.
They believed in direct contact with the customers rather than interacting
with them through any other medium. This meant the customers were
supposed to do all the work themselves by having to come directly to the
respective branches to get their requests fulfilled.
All the information about the services being provided by the bank
or about the details of the customers were stored on papers. This led to
lots of human errors and thus discrepancies crept into the working of
these banks. The requests of the customers were handled by employees
on the help desk of their respective branches which were then fed into the
computers of the bank and the response generated took days to complete
and the customers again had to come to the branch to enquire about the
completion of his request. This was pure harassment for the customers.
 11 Project
report

People couldn’t enquire about their own account by without going to the
branches again and again, rather for every small request they had to go to
the branch.
The system then was manual, in which various authorized
branches of IMPERIAL BANK had persons to manage the services
provided by the bank, the information of the customers. They also
recorded the problems and faults that most occurred during any
transaction or the problems occurred due to manual problems or due to
some other reason. The regional office of IOB used to take that

information from the various centers and made a record which was then
forwarded to the head office for report and survey purpose. In the head
office the responsible person used to process the records and make a
report and then find the relevant information. This was a daily process
and did take time to complete on a daily basis. Thus the system resulted
into a wastage of time, money, efforts and energy.

Proposed system

This project is an attempt to make the task of administrator as well as

customers easier. This project ensures the consistency by enabling the
 12 Project
report

customers to register themselves and to find the nearest service dealer at

their region, get themselves involved with the bank and can access the
different services provided by the banks.
The administrator has the right to know everything. He has the right to
know the account details of the customers, has the right to change any
service that the bank is currently providing or can add services which are
not being provided currently. Even the customer’s passwords and hidden
details are accessible by the administrator.

The customers can also contact the bank officials through email or
directly talk to the customer care the grievances, but first they have to
register themselves as a member by filling up a form which can be
downloaded online. Once registered, customers can access their account
and register for any services being provided by IOB, that too online by
sitting at home within a fraction of a second by a flick of a button.
Aim of this project is to provide an environment helpful for administrator
and customers as well, so that, the banks find it easy to implement it
without any harassment for the customers also. This project is developed
after a thorough study of the existing manual system & the user
requirements. Requirement analysis is concerned with identifying the
basic function of software component in a hardware & software system.
 13 Project
report
 14 Project
report
 15 Project
report

Economic feasibility
The benefits of this project include four types:

 Cost – saving benefits

This project reduces the administrative and

operational cost. Because of the reduction in the

use of paper, the cost also reduces.

 Improve-service-level benefits
 16 Project
report

Proposed system improves the system’s

performance because the current system is based

on manual processing while the proposed system

is based on computer processing.

 Improve-information benefits

It provides better information in the stipulated

space and time for decision-making.

 Time – saving benefits

It saves lots of time and provides the same result

in a far lesser period of time.

Technical Feasibility

 System Specification

• Proces s or I N T E L PE N TI U M –I V
 17 Project
report

• RAM 256 MB

• HD D 40 GB

 Software

• Platform WI ND OWS /L I N UX

• A rch itectu re J2E E

• R D B MS Oracle- 9i

 Backup Media

• FL OPPY D IS K, CD R OM

Behavioral Feasibility

Employees of the company are habitual of working with manual

system and don’t have the knowledge of working in a computer
 18 Project
report

application based environment that is used in their intranet and are

generally resistant to make changes in their working attitude.
People are inherently resistant to change and computers have
been known to facilitate changes. An estimate should be made of how
strong a reaction the staffs are likely to have towards the development of
an online computerized system because now this may lead to expulsion
of some of the staffs from their jobs.
So a system has to be chosen which will provide them much more
facilities and less mental disturbance to check weather correct entry is
entered and that too at its right place. The System will provide them
automatic reporting and checks on entries while storing as well as
entering. So the front end has been made user friendly for both the
customers and the employees.
 19 Project
report

Symbols Used

In order to create DFD’s we used following symbols.

Input/Output
 20 Project
report

Data Processing

Flow of data
1. one way data flow.

2.two way data flow.

Data store

Database
 21 Project
report

Stores and retrieves information

about insurance policies

insurance
module
All entries from bonds
module are store in the data Stores and retrieve
base. information about loans.
bonds services loan module

Data Base
 22 Project
report

Stores and retrieves

information about deposits Stores information
about online services

deposits module Online service

module

.
 23 Project
report

Client
Enter User ID
And Password

Invalid login

Database Verification
ChecksSubmit Information
Valid login
to database
 24 Project
report

Database Connectivity

Different Database
Updating Option such
as withdraw, transfer

Commitment
of data

Login User Module DFD:

Client
Request for a
particular static
page

Data Store
 25 Project
report

Requested Module

Returns Required
Information

DFD for other pages:

Client
Enter client
password, id

Invalid login

Verification
Checks

Valid login
Withdraw Module
 26 Project
report

Balance>Amount Balance < Amount

Check the
Withdraw Amount Required Error Message
Amount

Data Commitment

Withdraw Module DFD:

Client
Enter id and
password

Invalid login

Verification
Checks

Valid login
Transfer Module
Check for amount in
users account
 27 Project
report

Check for the

required amount in Error Page
……
user’s account

Valid Amount

Check for the

……validity of
Data Commitment
destination account
Valid Account

Transfer Module DFD:

Client
Enter login id
and Password

Invalid login

Verification
Stop Payment
……Data Checks
Module
Store Valid login
 28 Project
report

Store the Information

Stop Payment Module DFD:

 29 Project
report

Input Forms
 30 Project
report

There are five input pages in this project. The descriptions of some pages are:
 User Login Page
 Money Withdraw Page
 Money Transfer Page
 Payment Cancellation Page
 31 Project
report

 User Login Page:

Any User who has already opened his account in the bank can
access online facilities of the bank. For this purpose he must have to enter
his unique identification id and password. This id and password should
be taken by user at the time of opening account. This page interact with
Java Server Page which check validate the user id and password.
 32 Project
report
 33 Project
report

 Withdraw Page:

After login in any user can withdraw amount from his/her

account. But there is only one condition for doing this is that there should
be sufficient amount in the account. After putting amount and Shipment
Method it will interact with database and do the required job.
 34 Project
report

 Money Transfer Page:

This is the most exciting feature of the E-Banking that

merely by sitting in front of computer you can transfer your money to
someone in few seconds. Only your account number and destination
account number is required. Now there is no need to sign any more
checks just do it by E-Banking.
 35 Project
report
 36 Project
report

 Payment Cancellation Page:

E-Banking has provided a reliable feature for the

businessmen that if they want to cancel the payment or list of payments
they can do it by login in and using Check Cancellation fascility.
 37 Project
report
 38 Project
report
 39 Project
report

Output Forms
There are some outputs pages are as fallows:

 Successful client entry output.

 Successful Money Transaction.
 Successful Payment Cancellation Page
 Insufficient money alert
 Error Page
 40 Project
report

 Successful entry of User.

This page shows the account summary of the logged in user.

His Balance account number and other links through which
he can update the database.
 41 Project
report
 42 Project
report

 Successful Money Transaction Page-

This Page shows that transaction has been

committed on the database and money has been transferred from his/her
account to the destination account.
 43 Project
report
 44 Project
report

 Successful Payment Cancellation Page-

This Page shows that Payment Cancellation has

been committed on the database and it is recorded in the database that
these checks will not be valid any more in any bank.
 45 Project
report
 46 Project
report

 Insufficient fund Page -

This Page shows that balance is less then required

amount so the operation which is requested will be cancelled. If this page
comes then it shows that database is unaffected during this process.
 47 Project
report
 48 Project
report

 Error Page -

This Page shows that any software or hardware

problem has occurred so operation will be canceled for precaution and
database will be un affected during this process.
 49 Project
report
 50 Project
report
 51 Project
report

DATABASE DESIGN

In our data flow diagram, we give names to data flows, processes and
data stores. Although the names are descriptive of data, they do not dive
details .So following DFD, our interest is to build some details of the
contents of data flows, processes and data store. A data dictionary is a
structured repository of data about data .It is a set of rigorous definitions
of all DFD data elements and data structures .The data dictionary for the
current system has been given as under:
 52 Project
report

Tables For Project:

Register Table: This table stores information corresponding to user id
and its password and general information about user, for online
registration. Which are unique and cannot be not null.

username1 text Not Null (Primary Key)

Password1 Text Not Null
Cpassword1 Text Not Null
Salutation1 Text Not Null
f name1 Text
mname1 Text
lname1 Text
Sex Text NOT NULL
Salary Double NOT NULL
Pan Number Text NOT NULL
House Number Text
House Street Text
House City Text NOT NULL
Qualification Text
Date Of Birth Date NOT NULL
Profession Text NOT NULL
 53 Project
report

Account table: This table stores the information about the balance and
type of the account which is used by the customer. According to
customer id a particular account number is given to them.

Customer ID Integer NOT NULL

Account Number Text NOT NULL
Balance Double Should be Greater Than
1000
Last Date of Update Date
Type Text
 54 Project
report

Stop Payment Table:

This table stores the information of all the checks which are cancelled by
the customer.

Customer Id Integer NOT NULL

First Check Text NOT NULL
Last Check Text

Withdraw table: This table stores the information about the any
withdraw made by any logged in user.

Customer ID Integer NOT NULL

Amount Double NOT NULL, should be
greater than 1000
Date Date NOT NULL
 55 Project
report
 56 Project
report

Design is the first step in the development phase for any product or
system. Goal of design is to produce a model or representation of an
entry that will later be built. Software design is the first of the first of
three technical activities-design, code generation and testing are required
to build and verify the software. Each activity transforms information in a
manner that ultimately results in validated computer software.
To convert the user requirements into a broad level design
document the following are required:
• Identifying various modules of the proposed design and
their interfaces i.e. listing down all its input/output, data
structures and procedures
• Include algorithms if they need to be included as part of
design instead of coding for each of the procedures.
• Verify that all the requirements identified in Customer
Requirement Specification are mapped on to the design.

Design is the first level of translation of the Customer requirement

specifications into broad architecture modules. Quality of the design
at this stage reflects on the final quality of the product or service.
Therefore, extreme care is to be taken to ensure that some module or
the other address each customer requirement in an effective and
efficient manner. A software project design can be function oriented,
data oriented or object oriented. Based on the quality plans, specific
detailed design modules are subjected to review and approval.
 57 Project
report
 58 Project
report

Testing plays a critical role in quality assurance for software .Due

to the limitation of the verification method for the previous phases,
design and requirement fault also appear in the code. Testing is used to
detect these errors, in edition to the error introduced during coding phase.
Testing is a dynamic method for verification and validation,
where the system is to be tested is executed and behavior of the system is
observed. Due to this testing the failure of the system can be observed,
from which the presence of fault can be deduced. However, separate
activities have to be performed to identify the faults.
There are two method of testing: functional and structural.
In functional testing, the internal logic of the system under testing is not
considered and the test cases are decided from the specification or the
requirements. It is often called “Black Box Testing”. Equivalence class
partitioning, boundary analysis, and cause effect graphing are examples
of methods for selecting test cases for functional testing. In structural
testing, the test cases are decided entirely on the internal logic of the
program or module being tested.
As the goal of testing is to detect any errors in the programs
different flavor of testing are often used. Unit testing are used to test a
module or a small collection of modules and the focus is on detecting
coding errors in modules. During integration testing modules are
 59 Project
report

combined into sub-system, which are then tested. The goal here is to test
the system design. In system testing and acceptance testing, the entire
system is tested. The goal here is to test the requirement themselves.
Structural testing can be used for unit testing while at higher level mostly
functional testing is used.
In the project Monthly Materialization Report System we
used the unit testing and functional testing. System testing is a critical
phase in systems implementation. Testing of a system involves hardware
device testing and debugging of computer programs and testing
information processing procedures. Testing can be done with test data,
which attempts to simulate all possible conditions that may arise during
processing. The plane for testing are prepared and then implemented.
The testing methods adopted in the testing of the system
were Independent Unit Testing and System Testing

Independent Unit Test (IUT)

IUT focuses first on the modules, independently of one another, to

locate errors. This enables the tester to detect errors in coding and logic
that are contained within that module alone. Those resulting from the
interaction between modules are initially avoided.
IUT is generally white box oriented which is predicted
on the close examination of procedural detail. It exercises all the logical
 60 Project
report

decisions on their true and false side, executes all loops at their
boundaries and within their operational bounds and checks whether the
required validations have been met. White box testing exercises internal
data structure to assure their validity.

System Testing (ST)

It is a systematic technique for testing the whole integrated system.

First all the modules are integrated to form a system and then this
integrated system is tested according to the test plan initially prepared. It
helps to uncover errors associated with interfacing. It also tests to find
discrepancies between the system and its original objectives.
In the testing of IAS, both these testing methods were
applied. The different units were initially tested independently, and then
all the units were combined into one to form the system. This system was
again tested. All the test conditions were planned in advance and
documented in the Unit Test Plan (UTP) and System Test Plan (STP).

Role in Testing
IUT: Extensive testing was done for the Endorsement report. The
errors that were found were later on removed.
UTP: Unit testing was done for the Release order Report,
Checklist Report, renewal entry form, release order entry form and
 61 Project
report

Acknowledge Report. All the testing was done according to the test
plans, which were designed by us
Major Role in Testing was during the time in which we assisted
the management setup to be done at client end.
 62 Project
report

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
prevent system 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.
 63 Project
report

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.
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.

Following table summarized the broad classes of

maintenance found in development of information systems:
 64 Project
report

CATEGORY ACTIVITY

 Corrective Emergency fixes, routine debugging.

 Adaptive Accommodation of changes to data

and to hardware and software,
changes in the external environment.

 Pre effective User enhancement, improved

Documentation recording of
computational efficiency, user
recommendations for new
capabilities.

 Preventive Routine service of cleaning and

adjusting the equipment to prevent
breakdowns, future maintainability
reliability enhancement, recovering
 65 Project
report

design information to improve the

overall quality.

Maintainable Design

The points to reduce the needs for maintenance are:

 More accurately defining the user’s requirements during the
system development.
 Assembling better system documentation.
 Using more effective methods for designing process logic
and communicating it to project team members.
 Making better use of existing tools and techniques.
 Managing the system engineering process effectively.

The maintenance for Integrated Advertising System was performed

with the above-mentioned points as the underlying principles and
according to the demands of the users.
 66 Project
report
 67 Project
report

This is a well defined job of our team that has taken six weeks to
analyze the situation in which this project will work and the environment
of the company that will use this project.
It was a good experience for us to work in a company that has a
very friendly environment and learning atmosphere.
I am very thankful to Mr. Saurav Sharma who gave a lot of good
programming skills and so many company related skills that will help me
in the future.

I am also thankful to all my friends and team members.

 68 Project
report
 69 Project
report

BIBLIOGRAPHY

• BOOKS CONSULTED:

 The complete reference J2EE

By: Jim Keogh
Publication: TATA McGraw Hill
 The complete reference JAVA 2.0
By: Herbert Schildt
Publication: TATA McGraw Hill
 JSP in 24 Hours
By: SAMS

SITES REFERRED:

http://www.java.sun.com/
 70 Project
report