Intranet Banking System

Intranet Banking System 1
1. Introduction
TEEGALA KRISHNA REDDY ENGINEERING COLLEGE

1.1Organization Profile

1.1 ORGANIZATION PROFILE
3EMR TECHNOLOGIES is a leader in off shoring Enterprise

Applications and Outsourced Product Development established in the year 1999.
3EMR TECHNOLOGIES help its customers to optimize their investments

in enterprise business applications - ERP, CRM from leading vendors such as
Agile, Oracle, PeopleSoft, SAP and Siebel. It offers comprehensive
implementation, integration, upgrade services. The key products include CRMNet,
ECOLens, PORTALNet, SCMNet, QTPGenie.
It involves in developing, testing and supporting software products for

small to large Independent Software Vendors (ISVs) with a proven track record
over the last 10 years.
Services:
3EMR TECHNOLOGIES provides various services such as
Enterprise Application Services:

3EMR TECHNOLOGIES Atlantic helps Customers optimize their
investments in enterprise business applications - ERP, CRM or SCM - such as
Agile, Oracle, PeopleSoft, SAP and Siebel, through full lifecycle application
management - from implementation to ongoing support.

Product Development & Testing Services:

With over ten years of product experience, 3EMR TECHNOLOGIES
specializes in providing software development, testing, and support services to
software and appliance companies
Application Development & Maintenance

3EMR TECHNOLOGIES Application Development and
Maintenance expertise includes the domains of solution engineering, application
design & development, performance & reliability engineering, application
maintenance, and legacy application migration.
We can reduce our software and infrastructure development and

maintenance costs by one-half to two-thirds by utilizing 3EMR TECHNOLOGIES
application development and maintenance services.
3EMR TECHNOLOGIES have partnership with leading Enterprise

applications such as Agile, Oracle, PeopleSoft, SAP and Siebel enables us to make
development of custom integrations our area of excellence. Out expertise in
software engineering processes such as Rational RUP, and Agile development
methodologies such as extreme programming sets us apart.
Integration Services:
3EMR TECHNOLOGIES approach to integration is embodied in the

Business Process model, which integrates an organization's internal information
systems as well as those of customers, suppliers, and trading partners at a business
processes level, through the use of common business objects (based on standards

like OAG, Rosettanet, etc.) and business transforms using open industry standards
such as XML, XSLTs, Web services, etc.
3EMR TECHNOLOGIES’s differentiators include:
1. A history of successful productized integrations: It is the Application Networks

Company.
2. EAI expertise, with years of system integration and project management

experience
3. Relationships with leading EAI and middleware vendors through their strategic
alliance programs
4. Engineering relationships with product vendors like Oracle, Siebel, Agile,

Vitria, TIBCO, etc. - gives us the inside edge in integration

1.2 ABSTRACT
The Banking System automates the operations of a bank which were done
manually. It will reduce the overall administrative time of the various processes.
Every user of the system should have his own set of privileges, which determines
his/her scope. It deals with the operations of the bank like account creation and
manipulation, transaction management and other value added services depending
upon user requirements.
This system should create user-friendly environment to members of the

bank like manager, cashier and clerk etc., by providing interfaces for all of them. It
enables faster communication between different users of the system, which
reduces the overall administrative time. It increases the efficiency of the business
by providing efficient and timely service to customer, leading to customer
satisfaction thus increasing the overall business of the organization.

1.3 OVERVIEW OFS THE PROJECT
The Banking System automates the operations of a bank, which were done
manually. It will reduce the overall administrative time of the various processes.
Every user of the system should have his own set of privileges, which determines
his/her scope. It deals with the operations of the bank like account creation and
manipulation, transaction management and other value added services .
This system should creates user friendly environment to members of the
bank like manager, cashier and clerk etc., by providing interfaces for all of them. It
enables faster communication between different users of the system which reduces
the overall administrative time. It increases the efficiency of the business by
providing efficient and timely service to customer, leading to customer satisfaction
thus increasing the overall business of the organization.
The project when completed has the following advantages
• Hassle free system
• No Redundancy
• No chance of fraud
• User friendly
• Saving Resources

Scope of the system:
• Any bank, which wants to automate their internal operations, can use our
system.
• The system is being developed exclusively for offline banking, yet it can
easily be integrated with any existing online banking system.
• The scope of our system is limited to the accounts, transaction
management, and logins creation/editing.
• Our system is limited to the bank.

2. Software engineering Concepts

SYSTEM ANALYSIS
Efficient and effective management of Core banking activities has become an

increasingly imperative and complex activity. Thus automating the entire activity
for easier tracking of huge database has become indispensable, for providing cost
effective and reliable banking services thus leading customer satisfaction.
This module covers all the Core Banking aspects right from opening a bank
account to applying for loans. The system records basic demographic, address
data, transaction details, possessions data and also the customer business data.
Time consuming tasks such as opening an account, granting OD have become
extremely friendly, secure and error free. And also the assignment of privileges to
the employees has made the system more robust and secure.
Thus enabling the Bank officials to concentrate more on business development
rather than dealing with the current activities of the banks. This ultimately leads to
the innovation in the arena of core banking.
2.1 Existing system:

The existing system manually records the transactions of the bank like a/c
creation, crediting and debiting of accounts etc. It also grants different types of
loans to its customers like home loans, mortgage loans vehicle loans etc. Each
transaction in this system has to be manually signed. The following are the
problems of the existing system.
• Time consuming.
• Requires lot of paper work.
• Laborious
• Tedious
• More complexity
• Vulnerable to natural disasters.

Problem Statement:
The problem pertains to developing a offline baking system for XYZ Credit Union
Ltd., India. The three types of accounts to be covered are:
• Savings account – General savings account without a cheque book;
minimum balance required is Rs. 500.00.
• Checking account – General savings account with cheque book; minimum
balance is Rs. 1000.00.
• OD account – For corporate customers, this allows negative credit.
The other Details are:
• Approval of the manager is not required for withdrawing cash.
• For savings and checking accounts, a person holding an operational account
must introduce.
• Credit limits for OD accounts will be determined based on customers
record and history of operations with the bank.
• Customers will not have access to the system.

2.2 Feasibility Study:

Many feasibility studies are disillusioning for both users and analysts. First, the
study often presupposes that when the feasibility document is being prepared, the
analyst is in a position to evaluate solutions. Second, most studies tend to overlook
the confusion inherent in system development-the constraints and the assumed
attitudes. If the feasibility study is to serve as a decision document, it must answer
three key questions:
1) Is there a new and better way to do the job that will benefit the user?
2) What are the costs and savings of the alternatives?
3) What is recommended?
The most successful system projects are not necessarily the biggest or most
visible in a business but rather those that truly meet user expectations. More
projects fail because of inflated expectations than for any other reason.
Feasibility Considerations
Three key considerations are involved in the feasibility analysis: economic,
technical, and behavioral. Let’s briefly review each consideration and how it
relates to the systems effort.

Economic Feasibility
Economic analysis is the most frequently used method for evaluating the
effectiveness of a candidate system. More commonly known as cost/benefit
analysis, the procedure is to determine the benefits and savings that are expected
from a candidate system and compare them with costs. If benefits outweigh costs,
then the decision is made to design and implement the system. Otherwise, further
justification or alterations in the proposed system will have to be made if it is to
have a chance of being approved. This is an ongoing effort that improves in
accuracy at each phase of the system life cycle.
Economic Feasibility – Banking system:
This project is economically feasible as this software has the following
benefits.
 Tangible benefits:
o Saving stationery
o Saving space
 Intangible benefits:
o Time saving
o Customer goodwill
Technical Feasibility
Technical feasibility centers on the existing computer system (hardware,
software, etc.) and to what extent it can support the proposed addition. For
example, if the current computer is operating at 80 percent capacity-an arbitrary
ceiling-then running another application could overload the system or require
additional hardware. This involves financial considerations to accommodate
technical enhancements. If the budget is a serious constraint, then the project is
judged not feasible.

Technical Feasibility – Banking system:

The software that is developed is technically feasible as it satisfies the
offline needs of a Bank. The software used to develop the system chosen is
Java1.5. The web pages were developed using HTML and JSPs. All the databases
can be connected to the forms, which were developed. It maintains the data in a
centralized server from where the data can be shared between clients.
2.3 Proposed system:

The proposed system automates the operations of a bank, which were done
manually. It reduces the overall administrative time of the various processes.
Every user of the system has his own set of privileges, which determines his/her
scope. This system deals with the operations like account creation and
manipulation, transaction management and other value added services depending
upon user requirements.
This system creates user-friendly environment to members of the bank like
manager, cashier and clerk etc., by providing interfaces for each of them. It
enables faster communication between different users of the system; whichs
reduces the overall administrative time. It increases the efficiency of the business
by providing efficient and timely service to customer, leading to customer
satisfaction thus increasing the overall business of the organization.
Advantages of the proposed system:
• Hassle free system

• No Redundancy
• No chance of fraud
• User friendly

• Saving Resources
Module description:
The proposed system has four modules
• Login
• Credit/Debit Transaction
• Search
• Create/Update/Delete account
Login: This module deals with the user logins. It is responsible for returning the
appropriate page to the user depending upon the type of the user.
Credit/Debit Transaction: This module deals with all the crediting/debiting
transactions of the bank. Where the crediting/debiting of the account may happen
through cheque or through voucher. And it is also responsible for recording the
details of the transactions in a separate database table.
Search: This module performs different kinds of search depending upon:
1. Type of account
2. Type of loan
3. Account balance
Create/Update/Delete account: This module is responsible for creating the new

customer accounts, updating the details of the accounts and the deletion of the
accounts.

2.4 Specifications:
Hardware specification
The following are the minimum Hardware Requirements.
Processor : Pentium III or above.
RAM : 512 MB or above.
Hard Disk : 20 GB.
Monitor : VGA Color (256).
A mouse or similar pointing devices.
Software specification
The following are the minimum Software Requirements.
Operating system : Windows2000/NT/XP.
Language : Java
Front-end : Scripting (HTML, JavaScript), JSP
Web-Server : Apache Tomcat 5.X
Database : Oracle 8i or above

2.5 Architecture


3. System Design

3.1 Detailed Design

Entities and Attributes used in ER Diagrams

Entity Name:-
Savings
Attributes:- DOB
Contact
Name
Balance
ID
Type
Date
Surety
Loan
Location
Nomini
Relation
Address

Surety A/C
Surety _name _no Nam
_A/C_ e Bala
Loan no nce
-ID Loca
Type- tion
of-loan Date_
ID- A/C
proo Nom
f
User inee
-ID Relation_n
Contact Savings_ omineeee
_no Addr
A/C
+ ess
Date_of
Hno State
_Birth
Area
City
1 Area
2
use use
s s
Transactions_S Transactions_
avings Loans
From Loan Loan_g

Amo
_A/C _IDto
Bal ranting
Loan_rep
unt
Type_of
TO_ pay aymentan
_Transa
A/C Loan saction
Trans ction Amo
A/C_ Status
fer Bal unt
User_ User_ A/C_
A/C_ ID
ID no no
Date Date Time
Time

3.2 INTRODUCTION TO UML (UNIFIED MODULE LANGUAGE)
The unified modeling language is a standard language for Specifying,

Visualizing, Constructing and Documenting the software system and its
components. It is a graphical language that provides a vocabulary and set of
semantics and rules. The UML focuses on the conceptual and physical
representation of the system. It captures the decisions and understandings about
systems that must be constructed. It is used to understand, design, configure,
maintain and control information about the systems.
Visualizing:
Through UML we see or visualize an existing system and ultimately we
visualize how the system is going to be after implementation. Unless we think we
cannot implement.
UML helps to visualize how the components of the system communicate
and interact with each other.
Specifying:
Specifying means building models that are precise, unambiguous and
complete UML addresses the specification of all the important Analysis Design,
Implementation decisions that must be made in developing and deploying a
software system.
Constructing:
UML’s models can be directly connected to a variety of programming
language through mapping a model from UML to a programming language like
Java or C++ or VB. Forward Engineering and Reverse Engineering is possible
through UML.
Documenting:
The deliverables of a project apart from coding are some artifacts which are
critical in controlling, measuring and communicating about a system during its

development viz. Requirements, Architecture, Design, Source code, Project plans,

Tests, Prototypes, Releases etc.
Diagrams in UML:
Diagrams are graphical presentation of set of elements. Diagrams project a
system, or visualize a system from different angles and perspectives.
The UML has nine diagrams these diagrams can be classified into the
following groups.
1. Static
a. Class diagrams.
b. Object diagrams.
c. Component diagrams.
d. Deployment diagrams
2. Dynamic
a. Use case diagram.
b. Sequence diagram.
c. Collaboration diagram.
d. State chart diagram.
e. Activity diagrams
Static or structural diagrams:

Class diagram:
This shows a set of classes, interfaces, collaborations and their
relationships. There are the most common diagrams in modeling the object
oriented systems and are used to give the static view of a system.
Object diagram:
Shows a set of objects and their relationships and are used to show the data
structures, the static snapshots of instances of the elements in a class diagram.

Like class diagram, the object diagrams also address the static design view or
process view of a system.
Component diagram:
Shows a set of components and their relationships and are used to illustrate
the static implementation view of a system. They are related to class diagrams
where in components map to one or more classes, interfaces of collaborations.
Deployment diagram:
Shows a set of nodes and their relationships. They are used to show the
static deployment view of the architecture of a system. They are related to the
component diagrams where a node encloses one or more components.
Dynamic or behavioral diagrams:

Use Case diagram:
Shows a set of use cases and actors and their relationships. These diagrams
illustrate the static use case view of a system and are important in organizing and
modeling the behaviors of a system.
Sequence diagram & collaboration diagram:

These two diagrams are semantically same i.e. the dynamics of a system
can be modeled using one diagram and transform it to the other kind of diagram
without loss of information. Both form the, Interaction diagram.
Sequence diagram:
Sequence diagram is an interaction diagram which focuses on the time
ordering of messages it shows a set of objects and messages exchange between
these objects. This diagram illustrates the dynamic view of a system.
Collaboration diagram:
This diagram is an interaction diagram that stresses or emphasizes the
structural organization of the objects that send and receive messages. It shows a

set of objects, links between objects and messages send and received by those
objects. There are used to illustrate the dynamic vies of a system.
State Chart Diagram:

State chart diagram shows a state machine consisting of states, transitions
and activities these illustrates the dynamic view of a system. They focus on the
event ordered Behavior of an object.
Activity Diagrams:
Activity diagram shows the flow from one activity to another within a
system. The activities may be sequential or branching objects that act and are
acted upon. These also show the dynamic view of the system.

3.2.1 UML Diagrams – Banking system
Use Case Diagrams
<<include>>
Login
<<include>> <<include>>
<<include>>
Cas hier Credit / Debit Trans actions <<include>>
<<include>>
<<include>>
Search <<include>>
Manager
<<include>>
<<include>>
Clerk <<include>> Crete /Delete /Update A/C
<<include>>
Report Generation
Managing Logins
Sub-Use Cases:
1. Login:
<<include>>
Verification
Login <<extend>>
ChangePwd

2. Credit/Debit Transactions:
<<extends >>
voucher
<<extends >>
Loan Repaym ent

<<extend>>
cheque
<<extends >>
<<extend>> cheque
<<extends >>
Credit / D ebit Credit

<<extend>>
<<extends >> voucher
voucher
<<extends >>
Debit
cheque

4. Create/Delete/Update A/C:
<<extends>>
current A/C
<<extends>>
Create A/C
<<extend>>
Saings A/C
<<extend>>
Delete A/C
<<extend>>
Crete /Delete/Update A/C
<<extend>> Update A/C <<extends>>
personal loan
<<extends>>
Applying For Loans

<<extends>> mortage loan
vehicle loan
Activity Diagrams

1 verification:
Activity
name:
Enter user id
and pwd verification
No Display invalid
Verify
login
yes
Return appropriate
interface
Description: When the user enters the loginID and password, first loginID and
password are verified in the database if it is correct then the appropriate user
interface is displayed. If the given input is incorrect then a message invalid login is
displayed.
Fund Transfer:

fill transfer form

details
CSV no in sufficient
details
yes
check balance
from A/C
if Sufficient no Specify sufficient amt

not existing
yes
Transfer the
Amount
Update in DB
Activity name: Fund Transfer
Description: As soon as the user fills in the fund transfer form, client side
validation is done if it is successful then account details including balance is
verified, if there is sufficient balance in the account then the fund is transferred lest
the message insufficient balance is displayed.
Update A/c:

entre A/C no to
be updated
if A/C exists specify invalid

no a/C no
yes
display details
in the form
update the
details
update the details

in the DB
Activity name: Update A/C
Description: when the account number to be updated is entered first the

existence of the account is checked if it exists then complete details of account
holder is displayed. After making changes to details the database is updated.
Class diagrams:

Sequence Diagrams

Login:
Login Database
Actor
1: submit()
2: verification()
3: process
4: response
5: return_appr_page
1 Every user who logs into the system should undergo the login process.
2. The user should enter the user_ID and password, then he/she selects the submit
button.
3. As soon as he selects the submit button, the data moves to the servlet.
4. The verification process is carried out. Which checks whether the user is valid
user or not.
5. If the user is the valid user, then the appropriate page is returned.
2. Change password:

1. When user selects change pwd option, then he is asked the current pwd
which is verified and change pwd form is returned to the user if successful.
2. Then the user fills in the changepwd form and submits, where the client
side verification is carried out and then the form data is sent to the database.
3. Finally the acknowledgement is returned to the user.
Crediting accounts:

1. The cashier enters the customer account number and then, appropriate
details of the customer are displayed.
2. The cashier enters the crediting amount and then selects the submit button.
3. The amount is credited into the customer account and the success message
is displayed to the user.
3.3 Dtabase Tables & Data dictionary:

Current_AC Table:
Savings_AC Table:

Login Table:
Ledger Table:

Transactions_current Table:
Transactions_savings Table:
Transactions_OD Table:

4. Concepts and Techniques
4. SYSTEM IMPLEMENTATION

4.1 INTRODUCTION TO JAVA

Introduction
James Gosling, Patrick Naughton, Chris Warth, Ed Frank and Mike

Sheridan conceived Java at SUN Micro Systems Inc Corporation in 1991. It took
18months to develop the first working version. This language was initially called
"OAK", but was renamed "JAVA" in 1995. Before the initial implementation of
OAK in 1992 and the public announcement of Java in1995, many more
contributed to the design and evolution of the language.
Overview:
Java is powerful but lean on Object Oriented programming language. It has

generated a lot of excitement because it makes it possible to program for Internet
by creating applets, programs that can be embedded in web page. The context of
an applet is limited only by one's imagination. For example, an applet can be an
animation with sound, an interactive game or a ticker tape with constantly updated
stock prices. Applets can be just little decorations to liven up web page, or they
can be serious applications like word processors or spreadsheet.
But Java is more than a programming language for writing applets. It is

being used more and more for writing standalone applications as well. It is
becoming so popular that many people believe it will become standard language
for both general purpose and Internet programming.
There are many buzzwords associated with Java, but because of its
spectacular growth in popularity, a new buzz word has appeared ambiguous,
Indeed, all indications are that it will soon be everywhere.
Java builds on the strength of C++. It has taken the best features of C++
and discarded the more problematic and error prone parts. To this lean core, it has
I . ex e
added garbage collection (automatic memory management), multithreading (the

capacity for one program to do more than one thing at a time), security
capabilities. The result is that Java is simple, elegant, powerful and easy to use.
Java is actually a platform consisting of three components:

Java programming language.
Java is library of classes and interfaces.
Java is a Virtual Machine.
The following sections will say more about these components:
JAVA IS PORTABLE:
One of the biggest advantages Java offers is that it is portable. An

application written in Java will run on all the major platforms. Any computer with
a Java based browser can run the applications or applets written in the Java
programming language. A programmer no longer has to write one program to run
on a Macintosh, another program to run on a Windows machine, still another to
run on a UNIX machine, and so on. In other words, with Java, developers write
their programs only once. The Virtual Machine is what gives Java its cross
platform capabilities. Rather than being compiled into Machine language, which is
different for each operating systems and computer architecture, Java code is
compiled into byte codes.
JAVA IS OBJECT-ORIENTED:
The Java programming language is object oriented, which makes program

design focus on what you are dealing with rather than on how you are going to do
something. This makes it more useful for programming in sophisticated projects
because one can break the things down into understandable components. A big
benefit is that these components can then be reused.

Java includes inheritance, or the ability to derive new classes from existing
classes. The derived class, also called a subclass, inherits all the data and the
functions of the existing class, referred to as the parent class. A subclass can add
new data members to those inherited from the parent class. As far as methods are
concerned, the subclass can reuse the inherited methods, as it is, change them,
and/or add its own new methods.
JAVA MAKES IT EASY TO WRITE CORRECT CODE:
In addition to being portable and object oriented, Java facilitates writing

correct code. Programmers spend less time writing Java code and a lot less time
debugging it. In fact, developers have reported slashing development time by as
much as two thirds. The following is a list of some of Java's features that make it
easier to write correct code.
GARBAGE COLLECTION:
Automatically takes care of allocating and de allocating memory, a huge
potential source of errors. If an object is no longer being used (has no references
to it), then it is automatically removed from memory, or "Garbage Collected".
Programmers don't have to keep track of what has been allocated and de allocated
themselves, which makes their job a lot easier, but, more importantly it stops
memory leaks.
NO POINTERS:
Eliminates big source errors. By using object references instead of many
pointers, problems with pointer arithmetic are eliminated, and problems with
inadvertently accessing the wrong memory address are greatly reduced.
STRONG TYPING:
Cuts down runtime errors. Because Java enforces strong type checking,
many errors are caught when code is compiled. Dynamic binding is possible and

often very useful, but static binding with strict type checking is used when
possible.
SIMPLICITY:
Java is made easier to learn and use correctly. Java keeps it simple by
having just one way to do something instead of having several alternatives, as in
some languages. Java also stays lean by not including multiple inheritance, which
eliminates the errors and ambiguity that arise when you create a subclass that
inherits from two or more classes. To replace capabilities, multiple inheritances
provide Java lets you add functionality to a class throw the use of interfaces.
JAVA INCLUDES A LIBRARAY OF CLASSES AND INTERFACES:

The Java platform includes an extensive class library so that programmers
can use already existing classes as it is, create subclasses to modify existing
classes, or implement interfaces to augment the capabilities of classes.
Both classes and interfaces contain data members (fields) and functions
(methods), but there are major differences. In a class, fields may be either variable
or constant, and methods are fully implemented. In an interface, fields must be
constants, and methods are just prototypes with no further implementations. The
prototypes give the method signature (the return type, the function name, and the
number of parameters, with the type for each parameter), but the programmer must
supply implementations. To use an interface, a programmer defines a class,
declares that it implements the interface, and then implements all the methods in
that interface as part of the class.
These methods are implemented in a way that is appropriate for the class in
which the methods are being used. Interfaces let one add functionality to a class
and give a great deal of flexibility in doing it. In other words interfaces provide
most of the advantages of multiple inheritance without its disadvantages.

A package is a collection of related Java classes and interfaces. The

following list, though not complete, gives examples of some Java packages and
what they cover.
Java.Lang – This package is so basic that it is automatically included in any Java

program. It includes classes dealing with numeric, strings, objects, runtime,
security and threads.
Java.io -- Classes that manages reading data from input streams and writing data to
the output streams.
Java.util -- Miscellaneous utility classes, including generic data structures, bit sets,
time, date, the string manipulation, random number generation, system properties,
notification and enumeration of data structures.
Java.net -- Classes for network support.
Java.awt --Classes that manage user interface components such as windows,

dialog boxes, buttons, check boxes, lists, menus, scrollbars, and text fields; the
“AWT" stands Abstract Window Toolkit.
Java.awt.image -- Classes for managing image data, including color models,

dropping, color filtering, setting pixel values, and grabbing snapshots.
Java.applet -- The Applet class, which provides the ability to write applets, this
package also includes several interfaces that connect an applet to its document and
to resources for playing audio.
Java.sql -- The JDBC API, classes and interfaces that access databases and send
SQL statements.
The first three packages listed, java.lang, java.io, and java.util form the
foundation, and they are the basic classes and interfaces for general-purpose
programming. Java Development Kit Version1.1 added some new packages, with
JDBC is being one of them. Other new packages include such things as Remote

Method Invocation, Security and Java Beans the new API for creating reusable
components.
JAVA IS EXTENSIBLE:
A big plus for Java is the fact it can be extended. It was purposely written
to be lean with the emphasis on doing what it does very well; instead of trying to
do everything from the beginning, it was return so that extending it is very easy.
Programmers can modify existing classes or write their own new classes or they
can write a whole new package. The JDBC API, the java.sql package, is one
example of a foundation upon which extensions are being built. Other extensions
are being added or worked on in area such as multimedia, Internet Commerce,
conferencing, and Telephony.
JAVA IS SECURE
It is important that a programmer unable to write subversive code for
applications or applets. This is especially true with the Internet being used more
and more extensively for services such as electronic commerce and electronic
distribution of software and multimedia contents. The Java platform builds
security in four ways.
The way memory is allocated and laid out: In Java an object's location in
memory is not determined until the runtime, as opposed to C and C++, where the
compiler makes memory layout decisions. As a result, a programmer not looks at a
class definition and figure out how it might be laid in memory.
The way incoming code is checked: The Java Virtual Machine doesn't trust
any incoming code and subjects it to what is called Byte Code Verification. The
byte code verifier, part of the virtual machine, checks that
The format of incoming code is correct
Incoming code doesn't forge pointers
It doesn't violate access restrictions

JAVA PERFORMS WELL:

Java's performance is better than one might expect. Java's many
advantages, such as having built in security and being interpreted as well as
compiled, do have a cost attached to them. However, various optimizations have
been built in, and the byte code interpreter can run very fast the cost it doesn't have
to do any checking. As a result, Java has done quite respectably in performance
tests. Its performance numbers for interpreted byte codes are usually more than
adequate to run interactive graphical end user applications.
JAVA IS ROBUST:
The multi platform environment of the WEB places extraordinary demands
on a program, because it must execute reliably in a variety of systems. Thus the
ability to create robust programs was given a high priority in the design of Java.
To gain reliability, Java restricts you in a few key areas to force you to find your
mistakes early in program developments. At the same time, Java frees you from
having to worry about many of the most common causes of programming errors.
Because Java is strictly typed language, it checks your code at compile time.
However, it also checks your code at run time. In fact, many hard to track down
bugs that often turn up in hard to reproduce runtime situations are simply
impossible to create in Java. Knowing that what you have written will behave in a
predictable way under diverse conditions is a key feature of Java.
JAVA SCALES WELL:

Java platform is designed to scale well, from portable consumer electronic
devices to powerful desktop and server machines. The Virtual Machine takes a
small footprint and Java byte code is optimized to be small and compact. As a
result, Java accommodates the need for low storage and for low bandwidth
transmission over the Internet. In addition the Java Operating System offers a

standalone Java platform that eliminates host operating system overhead while still
supporting the full Java platform API. This makes Java ideal for low cost network
computers whose sole purpose is to access the Internet.
JAVA IS MULTITHREADED:
Multithreading is simply the ability of a program to do more than one thing
at a time. For example an application could be faxing a document at the same time
it is printing another document. Or a program could process new inventory figures
while it maintains a feed for current prices. Multithreading is particularly
important in multimedia: a multimedia program might often be running a movie,
running an audio track and displaying text all at the same time.
4.2 JAVA DATABASE CONNECTIVITY (JDBC)
JDBC overview:
JDBC is a Java API for executing SQL statements. (JDBC is a trademarked

name and is not an acronym; nevertheless, JDBC is often thought of as
understanding for "Java Database Connectivity".) It consists of a set of classes and
interfaces written in the Java programming language. JDBC provides a standard
I . ex e
API for tool/database developers and makes it possible to write database

applications using a pure Java API.
Using JDBC, it is easy to send SQL statements to virtually any relational

database. In other words, with the JDBC API, it is not necessary to write one
program to access a Sybase database, another program to access a Oracle database,
another program to access a Informix database, and so on.. One can write a single
program using the JDBC API, and the program will be able to send SQL
statements to the appropriate database. And with in an application written in Java
programming language, one also doesn't have to worry about writing different
applications to run on different platforms. The combination of Java and JDBC lets
a programmer to write it once run it anywhere.
JDBC extends the concepts, which can be done in Java. For example, with
Java and JDBC API, it is possible to publish a web page containing an applet that
uses information obtained from a remote database or an enterprise can use JDBC
to connect all this employees (even if they are using conglomeration of Windows,
Macintosh, and Unix machines) to one or more internal databases via an Internet.
With more and more programmers using the Java programming language, the need
for easy database access from Java is continuing to grow.
MIS managers like the combination of Java and JDBC because it makes
disseminating information easy and economical. Businesses can continue to use
their installed databases and access information easily even of it is stored on
different database management systems. Development time for new applications is
short. Installation and version controls are greatly simplified. A programmer can
write an application or an update once, put it on the server, and everybody has
access to the latest version. And for business selling information services, Java and
JDBC offer a better way of getting out information updates to external customers.
What does JDBC do?

Simply put, JDBC makes it possible to do three things:

1. Establish a connection with the database
2. Send SQL statements
3. Process the results
The following code fragment gives a basic example of these three steps:
Connection con=DriverManeger.getConnection(“Jdbc:odbc:dsnName”, “login”,
“password”);
JDBC is a low-level API and a base for high-level APIs:
JDBC is a “low-level” interface, which means that it is used to invoke (or

“call’) SQL commands directly. It works very well in this capacity and is easier to
use than other database connectivity. JDBC APIs were also designed to be a base
upon which to build higher-level interfaces and tools. A higher-level interface is
“user-friendly”, using a more understandable or more convenient API that is
translated behind the scenes into a low-level interface such as JDBC. At present,
two kinds of higher-level APIs are under development on top of JDBC:
An embedded SQL for Java: At least one vendor plans to build this. DBMS
implement SQL, a language designed specifically for use with databases. JDBC
requires that SQL statements be passed as strings to Java methods. An embedded
SQL processor allows a programmer to instead mix SQL statements directly with
Java: for ex: a Java variable can be SQL statement to receive or provide SQL mix
into Java with JDBC calls.
JDBC Interfaces:
Connection Overview:
A connection object represents a connection with a database. Connection
session includes the SQL statements that are executed and the results are returned

over that connection. A single application can have one or more connections with
a single database, or it can have connections with many different databases.
Opening a connection:
The standard way to establish a connection with a database is to call the
method DriverManager.getConnection. This method takes a string containing a
URL. The DriverManager class, referred to as the JDBC manager layer, attempts
to locate a driver than it connects to the database represented by that URL. The
DriverManager class maintains a list of registered Driver classes, and when the
method getConnection is called, it checks with each driver in the list until it finds
one that can connect to the database specified in the URL. The driver method
connects uses this URL to actually establish the connection.
The user can by pass the JDBC management layer and call driver methods
directly. This could be useful in the rare case that two drivers can connect to a
database and the user wants to explicitly select a particular driver. Normally,
however, it is much easier to just let the DriverManager class handle opening a
connection.
The following code exemplifies opening a connection to a database located

at the URL "jdbc: ODBC: wombat" with the user ID of "oboy" and "12Java" as
the password:
String URL = "jdbc: ODBC: wombat";
Connection con=DriverManager.getConnection (url,"oboy","12Java");
DriverManager Overview:
The DriverManager class is the management layer of JDBC, working
between the user and the drivers. It keeps track of the drivers that are available and
handles establishing a connection between a database and the appropriate driver.
In addition, the DriverManager class attends to things like driver login time limits
and the printing of log and tracing messages.

For simple applications, the only method in this class that a general needs
to use directly is DriverManager.getConnection. As its name implies, this method
establishes a connection to a database. JDBC allows the user to call the
DriverManager methods getDriver, getDrivers, and registerDriver as well as the
driver method connect, but in most cases it is better to let the DriverManager class
manage the details of Establishing a Connection Statement:
Statement Overview:
A statement object is used to send SQL statements to a database. There are
actually three kinds of statement objects, all of which act as containers for
executing SQL statements on a given connection: Statement, Prepared statement,
which inherits form statement, and callable statement, which inherits from
prepared statement. They are specialized for sending particular type of SQL
statements; a Statement object is used to execute a simple SQL statement with no
parameters; a Prepared Statement object is used to execute a precompiled SQL
statement with or without IN parameter; and a callable statement object is used to
execute a call to the database stored procedure.
The statement interface provides basic methods for executing statements

and retrieving results. The PreparedStatement interface adds methods for dealing
with IN parameters; CallableStatement adds methods for dealing with OUT
parameters.

4.3 ORACLE
ORACLE is a relational Databse management system that as a transparent

interface between the physical storage and logical presentation of data and
provides the user with a set of flexible & sophiesticated tools to perform the
operations basing on data and the data structures. Oracle is a modular system that
consists of the Oracle database and several functional packages .
Oracle tools do 3 major kinds of work :

• Database Management
• Data access & manipulation
• Programming
For handling information the user can use these tools to:
• Define a database
• Query a databse
• Add,update,edit & delete data
• Modify the structure of database
• Export & Import data.
• Connectivity between back-end & front-end
Database Management tools:

This usually includes the ćore programming of oracle's database
management system .The oracle database with its associated tables & views are
stored in the oracle data dictionary.The data dictionary stores information related
to every fact of the database sytem
Data access & manipulation tools:

ORACLE uses the SQL command set for the purpose of data access & its
manipulation .Structured Query Language(SQL) includes ali commands which are
used for data access.


Reason for choosing ORACLE:

1) Applications developed on Oracle are completely portable to other versions of
programming .Programmers create a complex application in a single user
environment and then move it to multiuser platform.
2) Oracle has several features that ensures integrity of user database.Database can
be made secure by restrictions access to only authorized users using the tools
available in ORACLE.
3) Oracle can perform effectively on large database .It offers unique

clustering technique for storing data on the disk. ORACLE database works
effectively in a Intranet/Internet environment. Since the Internet applications
demands the data to be secure, ORACLE can be chosen as the right tools for
maintaining databases.

4.4 JAVA SERVER PAGES (JSP)
Based on servlet technology, and currently shaping up at breakneck speed,

Java Server Pages (JSP) is set to be one of the important elements of Java Server
Programming. Java Server Pages, they combine markup (whether HTML or XML)
with nuggets of java code to produce a dynamic web page. Each page
automatically compiled to a servlet by the JSP engine, the first time it is requested
and then executed. JSP provides a variety of ways to talk to java classes, servlets,
applets and the web server.
Architecture of Java Server Pages:
A Java Server Page is a simple text file consisting of HTML or XML

content along JSP elements (a sort of short hand for java code). When a client
request a JSP page of the web server and it has not been run before, the page is
first passed to a JSP Engine, which compiles the page to a servlet, runs it and
returns the resulting content to the client. There after, the web server’s servlet
engine will run the compiled page. It is possible to view the finished servlet code
that is generated by locating it with in the directory structure of the servlet engine.
For example with the JRun, you can find the source code for your JSP files (in
servlet form) in the Jrun/jsm-default/services/jse/servlets/jsp directory. This is
very helpful when trying to debug the JSP files.
In the javax.servlet.jsp package we can find the following classes

• JspPage
• HttpJspPage
They define the interface for the compiled JSP page-namely that it must
have three methods
• JspInit ()
• JspDestroy ()

• JspService (HttpServletRequest request, HttpServletResponse response)

The JSP author can define the first two methods, but the third is the
compiled version of the JSP page, and its creation is the responsibility of the JSP
engine.
Elements of Java Server Page:
Directives – These provide global information to the page, for example, import
statements, the page for error handling or whether the page is part of a session.
Declaratives – These are for page-wide variables and method declarations.
Scriptlets – The Java code embedded in the page.
Expressions – Formats the expression as a string for inclusion in the output of the
page.
JSP Directives:
A JSP directive is a statement that gives the JSP engine information for the
page that follows. The general syntax of a JSP directive is
<%@ directive {attribute =”value”} %>
Where the directive may have a number of (optional) attributes. Each directive has
an optional XML equivalent, but these are intended for future JSP TOOLS.
Possible directive in JSP1.0 are:
Page – information for that page

Include – files to be included verbatim
Taglib – the URL for a library of tags that you’ll use in the page (implemented at
the time of writing)
As is to be expected, the page directive has many possible attributes.
Specifying these are optional, as the mandatory ones has default values.
Attribute and Possible values Description

language = “java” The language variable tells the

server what language will be used
in the file. Java is the only
supported syntax for a JSP in the
current specification.
extends = “package.class” The extends variable defines the
parent class of the generated
servlet. It isn’t normally necessary
to use anything other than the
provided class.
import = “package.*; The import variable is similar to
the first section of any java
program. As such it should always
be placed at the top of the JSP
file. The value of the import
variable should be a comma-
separated list of the packages and
classes that you wish to import.
session = true/false” By default, the session variable is
true, meaning that session data is
available to a page.
info = “text” Information on the page that can
be Accessed through the page’s
servlet.getservletsetinfo() method
ErrorPage = “pathToErrorPage” Gives the relative path to the JSP
page that will handle unhandled
exceptions. That JSP will have
isErrorPage set to true.
IsErrorPage = “true/false” Marks the page as an error page.

A JSP declaration can be thought of as the definition of class-level

variables and methods that are to be used throughout the page. To define a
declarative block, begin the block of code with <%! declaration>.
JSP Scriptlets:
Scriptlets are defined as any block of valid java code that resides <% and
%> tags. This code will be placed in the generated servlet’s _jspService() method.
Code that is defined within a scriptlet can access any variable and any bean that
have been declared. There are also a host of implicit objects available to a scriptlet
from the servlet environment.
Implicit Objects Description
request The client request. This is usually a subclass of

HttpServletRequest. This has the parameter list
if there is one.
response The JSP page’s response, a subclass of
HttpServletResponse.
pageContext Page attribute and implicit objects need to be
accessible through a uniform API, to allow the
JSP engine to compile pages. But each server
will have specific implementation of these
attributes and objects.
The solution to this problem is for the JSP
engine to compile in code that uses a factory
class to return the server’s implementation of
the pageContext class. That pageContext class
has been initialized with the request and
response objects and some of the attributes from

the page directive and provides the other

implicit objects for the page request.
session The HTTP session object associated with the
request.
application The servlet context returned by a call to
getServletConfig(). getContext().
out The object representing the output stream.
config The servletConfig object for the page.
page The page’s way of referring to itself.
exception The uncaught subclass of Throwable that is
passed to the error page URL.
JSP Expression:
A JSP expression is a very nice tool for embedding values with in your
HTML code. Anything between <% and %> tags will be evaluated, converted to a
string, and then displayed. Conversion from a primitive type to a string is handled
automatically. JSP expression doesn’t close with a semicolon. That’s because the
JSP engine will put the expression within an out.println() call.
JSP engine allow you to essentially parameterize HTML (just as you would
parameterize a SQL query that differs by only a couple of values). Again and
again, your code will setup conditions and loops using a one-line JSP scriptlet and
then include the HTML code directly beneath it.
Coding JSP pages:

A big advantage in developing a Java Server Page is that you can code the
HTML without enclosing it in Java code, as you must do in a servlet. You can then
take advantage of HTML editors to develop your content. So from the drudgery of
coding HTML output in servlets, we’ve arrived at the flexibility of coding Java
snippets into the HTML page.

The “third way” is a mixture of presentation-based calls to a bean or servlet,

which components can be better tested, are well-encapsulated and good OOP citizens.
This moves from embedding code to embedding components and action tags in the page.

4.5 HTML
HTML stands for Hyper Text Markup Language, which is an application of

standard generalized markup language. It is a simple language used to define and
describe the layout of a web page.
Hyper Text:
Hyper text is an ordinary text that has been dressed up with extra features
such as formatting, imaging, multimedia and links to other documents.
Markup:
Markup is the process of taking ordinary text and adding extra symbols.
Each of the symbols used for markup in HTML is a command that tells a browser
how to display the text. Markup can be very simple or it can be very complicated.
Language:
It is actually a key point to remember about HTML. HTML is a computer
language related to programming languages like BASIC, C etc. HTML has its own
syntax, and rules for proper communication.
HTML Elements:
HTML comprises of three major elements that render a well structures look
for a document. Some of these elements are optional yet their assures a better
presentation
• Head
• Body
• Footer
The first HTML tag is used to identify a HTML document. The entire
document should be written inside <HTML> </HTML> tags. The title of the
document can be included in the <TITLE> </TITLE> tags.

Basic Elements:
An HTML document contains of text and tags used to convey the data of a
document and to mark it issues. The “<” and ”>” symbols that to a new user might
seem to dominate an HTML are the beginnings and endings of the tags that mark a
document’s structure with an understanding of what these tags do a developer can
quickly learn about tags mark familiar structure like titles, headings, paragraphs
and lists.
The “<” and “>” symbols in HTML are used to make tags to delimit
elements. These elements identify the document structure. The letters into the
element tag are case-sensitive. Some elements such as line break elements can be
delimited by one tag i.e., <BR>. Elements such as paragraph element <P> can be
delimited by both start and end tag.
Some elements also have attributes, the image element <IMG> uses SRC
(source) to identify the file of the image to be included in the document.
Body elements:
Body elements are used to mark text as context of a document. Unlike the
head elements almost all of these marks lead to some visual expression in the
browser body. The element starts with <BODY>. The tags mark the contents of
the HTML document.
<A>, this is an anchor element, which is based on for linking documents together
Attribute:
HREF: This attribute identifies the URL of hypertext reference for this anchor in
the form of HREF = “URL”. Where the URL given will be the resource that the
browser receives and the user clicks the anchor hotspot.
OL: For ordered list of elements.
DL: A definition list or glossary has three parts a term details explanation of the
term identified with the DT element.

HR: Horizontal rule, divides section of text

P: This element signals a paragraph start it can have a stop tag</P>
BR: This element forces a break.
IMG: The IMG element allows graphical browser to place graphic images in a
document at the location of the tag.
SRC: This attribute indicates the source file of the image.
ALIGN: This attribute sets the positioning relationship between the graphic and
text that follows it. TOP, MIDDLE, LEFT, RIGHT, BOTTOM are the option for
this alignment.
FORM ELEMENTS:
Forms are used to present an interface consisting of fill in the blank boxes.
Checklist radio buttons or other features to gather input from the user, the form
elements brackets an input data form. The elements INPUT, SELECT OPTION
and TEXTAREA are used to setup areas within the form input.
FORM: This delimits the start and end of a data input form. Forms can’t be nested
although there may be several forms in each document. Forms can handle other
elements such as lists<PRE>.
SELECT: This element allows the user to choose one of a set of alternatives. The
option element is used to define each alternative.
OPTION: This element occurs within the select element and is used to represent
each choice of the select.
3
TEXT AREA: This element is used to collect multiple lines of text from the user. The
user is presented with a scrollable pane in which text can be written.
TABLE ELEMENTS:
TABLE: The <TABLE> tag is used to define tables and has an ending tag
</TABLE>

Attributes:
Border: Causes border to render around the table. If missing the table has no grid
around it or its data.
Width: Specifies how wide the table will be. If given as NN% then the width is
NN% of the width of the display.
Col span: specifies the alignment of items in the columns.
Caption: Used to label a figure or table.
TH: Identifies the table header cell.
TD: Identifies a row of table’s cells.
Attributes:
Col span: The number of columns that the cell spans.
Row Span: The number of rows that the cell spans.

4.6JAVA SCRIPT
Java script is a general purpose, prototype based, object oriented scripting
language developed jointly by sun and netscape and is meant for the WWW .It is
designed to be embedded in diverse applications and systems, with out consuming
much memory. Java script borrows most of its syntax from java but also inherits
from Awk and Perl, with some indirect influence from self in its object prototype
system.
Java scripts dynamically typed that is programs don’t declare variable

types, and the type of variable is unrestricted and can change at runtime. Source
can be generated at run time and evaluated against an arbitrary scope. Typical
implementations compile by translating source into a specified byte code format,
to check syntax and source consistency. Note that the availability to generate and
interpret programs at runtime implies the presence of a compiler at runtime.
Java script is a high level scripting language that does not depend on or
expose particular machine representations or operating system services. It provides
automatic storage management, typically using a garbage collector.
FEATURES:
• Java script is embedded into HTML documents and is executed with
in them.
• Java script is browser dependent
• Java script is an interpreted language that can be interpreted by the
browser at run time.
• Java script is loosely typed language
• Java script is an object-based language.
• Java script is an Event-Driven language and supports event handlers
to specify the functionality of a button.

ADVANTAGES
1. Java script can be used for client side application

2. Java script provides means to contain multiframe windows
for presentation of the web.
3. Java script provides basic data validation before it is sent to
the server. Eg : login and password checking or whether the values entered
are correct or whether all fields in a from are filled and reduced network
traffic
It creates interactive forms and client side lookup tables

5. Screens

Homepage
Admin Login

Customer Login

Back Details
Adding a Designation into Database

Designation Search
Details

Adding Employee
Employee Information

Bank Information Adding A branch of Bank
Atm Branch Search

ATM Details

Adding ATM Machine
Adding ATM Service

ATM Service Search

Security

Adding Admin
Customer Details
Customer Home Page

CurrentBalance
Transfer the Amount

Change Password

6. Testing

TESTING
Testing is the process of detecting 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.
Psychology of Testing
The aim of testing is often to demonstrate that a program works by showing

that it has no errors. The basic purpose of testing phase is to detect the errors that
may be present in the program. Hence one should not start testing with the intent
of showing that a program works, but the intent should be to show that a program
doesn’t work.
Testing is the process of executing a program with the intent of finding

errors.
Testing Objectives:
The main objective of testing is to uncover a host of errors, systematically

and with minimum effort and time. Stating formally, we can say, Testing is a
process of executing a program with the intent of finding an error.
A successful test is one that uncovers an as yet undiscovered error.

A good test case is one that has a high probability of finding error, if it exists.
The tests are inadequate to detect possibly present errors.
The software more or less confirms to the quality and reliable standards.
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

Client Needs Acceptance Testing
Requirements System Testing
Design Integration Testing
Code Unit Testing
Unit testing:
Unit testing focuses verification effort on the smallest unit of software i.e.,
the module. Using the detailed design and the process specifications testing is
done to uncover errors within the boundary of the module. All modules must be
successful in the unit test before the start of the integration testing begins.
In this project each service can be thought of a module. 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.
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 I have checked whether the integration effects working
of any of the services by giving different combinations of inputs with which the
two services run perfectly before Integration.
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 ‘HR Database’ has been tested against requirements of project
and it is checked whether all requirements of project have been satisfied or not.
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 ‘HR Database’ I 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.
White Box Testing
This is a unit testing method where a unit will be taken at a time and tested
thoroughly at a statement level to find the maximum possible errors.

I tested step wise every piece of code, taking care that every statement in
the code is executed at least once. The white box testing is also called Glass Box
Testing.
I have generated a list of test cases, sample data. This is used to check all
possible combinations of execution paths through the code at every module level.
Black Box Testing
This testing method considers a module as a single unit and checks the unit
at interface and communication with other modules rather getting into details at
statement level. Here the module will be treated as a block box that will take some
input and generate output. Output for a given set of input combinations are
forwarded to other modules.

Test Cases
Test Condition Id: 3.1 Tester: chandrika
Requirements Addressed: User interface/usability.
Test Objective: Test conducted to check if the feasibility” three mouse click rule” .
Data Field: Value Entered:

NA NA
Expected Result: A test conducted to check if the user is able to navigate from main page
to any action within three mouse clicks for all the products offered by the team.
Observed Result : The team members were able to navigate from main page to any action
within three mouse clicks
Test Passed / Failed: The test was successful.

Test Condition Id: 4.1 Tester: phani
Requirements Addressed: Use scenario
Test Objective: Test conducted to explain the result of data entry when a correct format of
data entry was used
Data Field: Value Entered:
Login page. Respective passwords.
Money market page Data.
Mortgage page Data.
Certificate of deposit page Data.
Credit card page. Data.
Update field Data.
New product Data.
Expected Result: The interface is expected to use the data ( in the correct format
only)provided by the users and produce appropriate result to let the user know the changes
that were made.
Observed Result: The interface produced a message confirming the entry of a new product
after processing the data provided by the users.
Test Passed / Failed: The test was successful.

7. Maintenance

MAINTENANCE AND SUPPORT
This phase provides the necessary software for the system to continue to
comply with the original specifications. The quality assurance goal is to develop a
procedure for correcting errors and enhancing software. This procedure improves
quality assurance by encouraging complete reporting and logging of problems,
ensuring that reported problems are promptly forwarded to the appropriate group
for resolution, and reducing redundant effort by making known problem reports
available to any department that handles complaints.

8. Scope of the Project

FUTURE SCOPE OF THE PROJECT
The system deals only with core banking offline needs of any bank. Yet is
can seamlessly integrate with any of the online banking applications if there is a
need for the system to be expanded in future. As the system is built using the
platform independent language-java, this system is independent of OS limitations,
thus allowing the system cross platform independence.

9. Conclusion

CONCLUSION
This application can be used by any bank, which wants to

automate their offline banking services. It can be used by the banks to provide
their customers with robust and hassle free service.
The application has been so well
designed that in case of newer modules to be added it can plug the new modules
without affecting the already present modules. The application was tested and
found to execute successfully.

10.BIBLIOGRAPHY & WEBLIOGRAPHY
• The Complete reference. -Naughton.

• The complete reference. -Hanna.
• Head First -Bert Bates, Kathy Sierra.
• SQL/PLSQL -Ivan Bayross
• HTML: Black Book
www.javaranch.com
www.java.com
www.javaarchive.com
www.javapassion.com
www.sun.com
www.windows.com
www.w3schools.com

Intranet Banking System

Transféré par

Informations du document

Description originale:

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Intranet Banking System

Transféré par

Droits d'auteur :

Formats disponibles

Intranet Banking System 1

TEEGALA KRISHNA REDDY ENGINEERING COLLEGE

TEEGALA KRISHNA REDDY ENGINEERING COLLEGE

1.1 ORGANIZATION PROFILE

3EMR TECHNOLOGIES is a leader in off shoring Enterprise

3EMR TECHNOLOGIES help its customers to optimize their investments

It involves in developing, testing and supporting software products for

Enterprise Application Services:

TEEGALA KRISHNA REDDY ENGINEERING COLLEGE

Product Development & Testing Services:

Application Development & Maintenance

We can reduce our software and infrastructure development and

3EMR TECHNOLOGIES have partnership with leading Enterprise

3EMR TECHNOLOGIES approach to integration is embodied in the

TEEGALA KRISHNA REDDY ENGINEERING COLLEGE

3EMR TECHNOLOGIES’s differentiators include:

1. A history of successful productized integrations: It is the Application Networks

2. EAI expertise, with years of system integration and project management

4. Engineering relationships with product vendors like Oracle, Siebel, Agile,

TEEGALA KRISHNA REDDY ENGINEERING COLLEGE

This system should create user-friendly environment to members of the

TEEGALA KRISHNA REDDY ENGINEERING COLLEGE

1.3 OVERVIEW OFS THE PROJECT

The project when completed has the following advantages

• Hassle free system

TEEGALA KRISHNA REDDY ENGINEERING COLLEGE

Scope of the system:

TEEGALA KRISHNA REDDY ENGINEERING COLLEGE

2. Software engineering Concepts

TEEGALA KRISHNA REDDY ENGINEERING COLLEGE

Efficient and effective management of Core banking activities has become an

2.1 Existing system:

TEEGALA KRISHNA REDDY ENGINEERING COLLEGE

TEEGALA KRISHNA REDDY ENGINEERING COLLEGE

2.2 Feasibility Study:

TEEGALA KRISHNA REDDY ENGINEERING COLLEGE

TEEGALA KRISHNA REDDY ENGINEERING COLLEGE

Technical Feasibility – Banking system:

2.3 Proposed system:

• Hassle free system

TEEGALA KRISHNA REDDY ENGINEERING COLLEGE

Create/Update/Delete account: This module is responsible for creating the new

TEEGALA KRISHNA REDDY ENGINEERING COLLEGE

TEEGALA KRISHNA REDDY ENGINEERING COLLEGE

TEEGALA KRISHNA REDDY ENGINEERING COLLEGE

TEEGALA KRISHNA REDDY ENGINEERING COLLEGE

TEEGALA KRISHNA REDDY ENGINEERING COLLEGE

3.1 Detailed Design

TEEGALA KRISHNA REDDY ENGINEERING COLLEGE

Entities and Attributes used in ER Diagrams

TEEGALA KRISHNA REDDY ENGINEERING COLLEGE

From Loan Loan_g

TEEGALA KRISHNA REDDY ENGINEERING COLLEGE

3.2 INTRODUCTION TO UML (UNIFIED MODULE LANGUAGE)

The unified modeling language is a standard language for Specifying,

TEEGALA KRISHNA REDDY ENGINEERING COLLEGE

development viz. Requirements, Architecture, Design, Source code, Project plans,

Static or structural diagrams:

TEEGALA KRISHNA REDDY ENGINEERING COLLEGE

Dynamic or behavioral diagrams:

Sequence diagram & collaboration diagram:

TEEGALA KRISHNA REDDY ENGINEERING COLLEGE

State Chart Diagram: