sdsoft solutions(india) pvt. ltd.dspace.cusat.ac.in/jspui/bitstream/123456789/4243/... · sdsoft...

ACE-CUSTOMER SUPPORT TOOL

Dept of Computer Applications (DCA) MCA (2008-11) CUSAT KOCHI-22

Major Project Report on ACE-CUSTOMER SUPPORT TOOL

At

SDSOFT Solutions(India) Pvt. Ltd. DISSERTATION SUBMITTED IN PARTIAL FULFILMENT OF THE REQUIREMENTS FOR THE AWARD OF THE DEGREE OF MASTER OF COMPUTER APPLICATIONS OF COCHIN UNIVERSITY OF SCIENCE AND TECHNOLOGY.

SUBMITTED BY:

PPrriiyyeesshh KKuummaarr RReegg.. nnoo::-- 9955558800003344 MM..CC..AA..::-- 22000088--22001111

April 2011

DDEEPPAARRTTMMEENNTT OOFF CCOOMMPPUUTTEERR AAPPPPLLIICCAATTIIOONNSS



CCOOCCHHIINN UUNNIIVVEERRSSIITTYY OOFF SSCCIIEENNCCEE AANNDD TTEECCHHNNOOLLOOGGYY

DDEEPPAARRTTMMEENNTT OOFF CCOOMMPPUUTTEERR

AAPPPPLLIICCAATTIIOONNSS

CCOOCCHHIINN UUNNIIVVEERRSSIITTYY OOFF SSCCIIEENNCCEE AANNDD

TTEECCHHNNOOLLOOGGYY

Certificate

This is to certify that the report entitled “ACE-CUSTOMER SUPPORT

TOOL” submitted to Cochin University of Science and Technology in partial fulfillment of the requirement for the award of the degree of Master of Computer Applications is the confide record of the project work done by Priyesh Kumar, Reg. no.:- 9955558800003344 under our supervision and guidance during January 2011 to April 2011. Signature: Signature: Signature: Head of the Department Internal examiner External Examiner



Acknowledgement

The satisfaction and euphoria that accompany the successful completion of any task would be incomplete without mentioning the names of people who made it possible, whose constant guidance and encouragement crowns all efforts with success. I extend my gratitude to Dr.K.V Pramod ,Head-Department of Computer Applications ,Cochin University of Science and Technology ,Kochi ,Kerala for providing me with excellent infrastructure and awesome environment that laid potentially strong foundation for my professional life . I would like to express my profound thanks to Dr.B.Kannan, Dr.A.Sree Kumar, and Dr.Malathi s for their help and guidance thought my project nature . I would like to express my deep sense of gratitude to Team Lead, Nagarjuna, SDSOFT Solutions(India) Pvt. Ltd., Bangalore, for selecting me in being the part of his team, and sharing his knowledge and experience with me. My endeavors shall remain incomplete if I forget to extend my thanks to all my teachers ,classmates and friends who have helped me to complete the project

Priyesh Kumar



DECLARATION

I hereby declare the dissertation entitled “ACE-CUSTOMER SUPPORT TOOL” that is a being submitted by Mr. Priyesh Kumar(Reg no: 9955558800003344) during VI SEMESTER, MCA course and has been prepared in partial fulfillment for the award of MASTER OF COMPUTER APPLICATIONS from COCHIN UNIVERSITY OF SCIENCE AND TECHNOLOGY, Kochi , Kerala , is a bonafied student work carried out under the guidance and supervision of Nagarjuna. This report has not been submitted to another university/institute for the award of any other degree.

Priyesh Kumar



ABSTRACT

ACE-Customer support tool is a mobile Banking Application. It provides very useful features to the bank customers who can call to the customer care executives and enquiry for the current balance in the account, cheque clearance. Customer can also request for his change in contact information like his address, phone, email and so on. He can also request for the statements for monthly or half-yearly basis. Customer can also make request to reset the password for debit card, net-banking and for online transaction and so on. Based on the request, executive adds the request and issues the request id for the customer. This application is limited to the saving accounts only. This application is comprised of the following modules:

� Admin Module

� Customer Executive Module

� Back Office Team

SYSTEM REQUIREMENT SPECIFICATION: 1) HARDWARE REQUIREMENTS:

PROCESSOR PENTIUM-IV RAM 1GB MINIMUM HARD DISK MINIMUM 80 GB PROCESSOR SPEED 2.6 GHZ 2) SOFTWARE REQUIREMENT: OPERATING SYSTEM WINDOWS 2000/ XP/VISTA TECHNOLOGIES JSP, SERVLETS, STRUTS,JDBC,HIBERNATE DATABASE My-SQL/ORCALE WEB SERVER APACHE TOMCAT



TABLE OF CONTENTS:

CChhaapptteerr TTiittllee

1. Introduction

1.1 Organization Profile 1.2 Synopsis

2. System Analysis 2.1 Problem Definition 2.2 Problem Domain 2.3 Need for Computation 2.4 Objective of System

3. Modules Description 4. Requirement Analysis

4.1 Introduction 4.2 Feasibility Study 4.3 Technical Feasibility 4.3.1 Economical Feasibility 4.3.2 Operational Feasibility

5 Data Modeling 5.1 Introduction

5.2 ER Diagram 5.3 DFD 5.4 Class Diagram 5.5 Use case Diagram 5.6 Sequence Diagram 5.7 Data Dictionary

6. System Design 6.1 Introduction

6.2 Database Design 6.3 Normalization 6.4 Architectural Design 6.5 User Interface Design

7. Table Analysis 8. Screen Layouts 9. System Testing 9.1 Introduction 9.2 Test Case Design 9.3 Black Box Testing 9.4 White Box Testing 9.5 Testing Strategies



10. System Implementation 10.1 Introduction 10.2 Software and Hardware 10.3 System Maintenance 11. Features of Technology Used 11.1 Java 11.2 JSP 11.3 Servlet 11.4 Struts Frame work 11.5 Hibernate 11.6 My-Sql 12. Conclusion 13. Bibliography 13.1 Reference Books 13.2 Reference Websites



1.



1.1 INTRODUCTION

(About Organization) SDSOFT Solutions(India) Pvt. Ltd. :

SDSOFT Solutions (India) Pvt. Ltd. is a leading edge technology and IT consulting firm

focused on delivering the best quality and most cost-effective solutions to our clients. SDSOFT

consider IT as the backbone of a business efficiency eco-system and we provide complete

solutions to address all aspects of your business, and across the entire chain - from

conceptualization to implementation and actually running the process for you. Office in

Bangalore, India.

SDSOFT is one of the few companies in the world to integrate technology and operations

with a global services model. We provide highly customized application development,

integration, internet services and maintenance for a wide range of businesses.

SDSOFT want our clients to focus on what they do best while we took care of the rest, by

innovating and adding value. Outsourcing to SDSOFT gives you more time and resources to

concentrate on your core competencies. Our range includes out- of-the-box solutions, technology

consulting, customization and maintenance of applications, enterprise application integration,

prototyping and architecture frame working. SDSOFT Company offers a complete range of the

consulting, technology, operations and process outsourcing value chain. We develop competent

solutions in the fields of website and application design and development, spanning a range of

industries including but not limited to



1 E-learning

2 Financial Services

3 E-business

4 Application Engineering

5 Publishing, Media and Technology

6 Healthcare

At SDSOFT we are committed to deliver our clients Total Quality on budget, on time

every time.

Total Quality

We make sure that all products and services we deliver pass through the most stringent

testing and review process and that they are 100% defect free. We won’t stop at “good enough”

because GOOD is not enough for our customers, and we won’t stop at anything less than BEST

for our customers. At SDSOFT, Quality is not just about implementing a system or working

towards a set of standards. It is an attitude, a way of working, which not only improves

businesses but the way people work and live. We strive to facilitate and promote the use of

quality to add value to our customers and enhance the standing of quality professionals. It shows

our clients that quality forms an integral part of everything we do. This makes sure those high

quality standards that not only meet, but consistently exceed our client's expectations.



Application and Product Development

SDSOFT develops and designs state-of-the-art web page applications on new age

technologies for its clients. All these applications have been critically acclaimed globally and

have created a benchmark in their respective fields. The credit for all this goes to our highly

specialized software development team who through their time tested development technology

deliver all the projects in time and according to the budget. All the activities in business analysis,

design, development and testing are conducted through the flexible and module based approach

which ensures minimum client risk and also implementation of clients' requirements as per

accepted international standards. Thus, we comply best with our committed deliverables and

provide the best solution to our clients.

SDSOFT software development team is highly qualified, specialized and experienced

software developers who are skilled in a wide variety of programming languages including Java,

Servlets, JSP, EJB, JDBC, Struts JSF, Hibernate, Spring, Web Services and many more. The

average experience among them is more than three years in developing complex software

solutions and in handling international projects so as to ensure that the client's expectations are

met and the issues and needs are prioritized accordingly.

We deliver a high quality software application that matches the international standards

and assures smooth processes and timely results-all at an affordable cost.

Salient Features of SDSOFT provided Dedicated Offshore Development Teams

We specialize as an offshore development centre wherein requirement based dedicated

resources are provided



1 All required infrastructure for effective offshore development is provided

2 Ability to ramp up and ramp down resources

3 Client specified development processes adopted.

4 Project management by the client or SDSOFT.

5 Regular reporting and account management.

6 Onsite coordinator for large projects

Our Technology Expertise lies in the following.

1 Java / j2ee

2 Microsoft Technologies

3 Testing

4 SAP

5 Mainframe

6 Data warehouse

7 Telecom

8 Embedded Systems, Networking



1.2 SYNOPSIS ACE-Customer support tool is a mobile Banking Application. It provides very useful features to the bank customers who can call to the customer care executives and enquiry for the current balance in the account, cheque clearance. Customer can also request for his change in contact information like his address, phone, email and soon. He can also request for the statements for monthly or half-yearly basis. Customer can also make request to reset the password for debit card, net-banking and for online transaction and soon. Based on the request, executive adds the request and issues the request id for the customer. This application is limited to the saving accounts only. The tools used are JSP, Servalt , HTML, JAVA SCRIPT, Struts, Hibernate and MySql(used as a backend for storing data), Apache Tomcat (web -Server).



2. System Analysis Analysis is the process of breaking the problem into the successively manageable

parts for individual study. System analysis is the study of various operations that has to

be done to solve problem. One aspect of the system analysis is defining the boundaries of

the system and determining whether or not the proposed system should consider other

related systems. During analysis data are collected on the available files, decision points,

and transactions handled by the existing system.

Various tools are available to perform system analysis. Some of the tools are Data

Flow Diagrams, interviews, on-site observations, and questionnaires regarding the

proposed system. Interviews and Data Flow Diagrams are the commonly used tool in

analysis. The interview is the face-to-face interpersonal role situation in which the

designed questions are asked to gather information about the problem area. The interview

is the oldest and most often used device for gathering information in system analysis. The

two main purpose of interview are used as an exploratory device to identify relations or

verify information. To capture information as it exists.

Interview is an efficient technique for eliciting information about complex subjects

and offers a better opportunity, Data Flow Diagrams are used to analyze the

transactions involved in the proposed system, processing the debit and credit balance

so on. In developing a system, bias in the data collection may be a problem. Thus the area

of problem should be analyzed properly and clearly to develop a successful system



2.1 Problem Definition:

In the modern age the life is going to be faster and faster everyone wants to save Time,

Money and Energy. Keeping it mind we tried to develop such an environment that could help

people a lot. Before developing this system the Bank Manager , Bank Employee,Bank Customer

has to move form one center to another to be updated this causes loss of money, time and energy.

Present world of technology all the Multi National Companies of IT firms,all banks have

their branches at different places throughout the world. These firms are taking their

customers in GCST (Global Customer Support System ). So it is not possible to maintain

all the information about the Customers which is not taking in GCST process.

A software tool is required to maintain and the entire details of customer that do not

work under GCST process. Keeping this type of problems in mind we have developed

this system named “Customer Support System”.

The Customer Support System is designed to support Customer management. It

is useful to keep a list with all known activities. Managing such a list of details and

managing a customers with all its changes go to a large part .



2.2 Problem Domain:

Today enterprise globally are looking for service providers who can bring value

to the relationship in terms of innovation, creativity, committed to delivery quality with in

schedules, budget and having business models supporting the fast change in global economics

scenarios. To achieve these service providers should be passionate about their own business,

highly creative, customer centric and innovative to create vale to its customers, employees and

shareholders.

2.3 Need for Computerization / Objective:

The basic and most valuable Objective of this Project is to save Customer Time, Cost and

Energy. Today enterprise globally are looking for service providers who can bring value to the

relationship in terms of innovation, creativity, committed to delivery quality within schedules,

budget and having business models supporting the fast change in global economics scenarios. To

achieve these service providers should be passionate about their own business, highly creative,

customer centric and innovative to create vale to its customers.

2.4 Objectives of this System: Some of the major features of this site are:

� Fully web based Project

� Faster and Easier way of solve the problem of customers .

� Saving Time, Money and Energy together with quality of services.

� Administrator is managing the system.

� If problems occur employee team members can contact to the Administrator.

� Administrator loggings from the home page.



4. Modules Description:

This application is comprised of the three modules: � Admin Module

� Customer Executive Module

� Back Office Team

Admin Module:

He is allowed to do the following tasks.

Branch-admin login

� Branch-admin must have a valid User Id and password to login to the

system.

Add Employee

� Activating employee account by entering all the employee data into

computer and generating employee name, employee Id, password, and

for each employee.

Update Employee

� Updation required if any employee requests for it. This work is done by

Admin.

Disable Employee

� When any employee has resigned or removed from the branch then

branch admin can disable the employee login. By making employee

account active or inactive Admin can use this functionality.



View Employee by Employee ID

� In order to get the employee related information then branch admin

requires this functionality. By putting the Employee ID of any employee

Admin can see the whole details about corresponding employee.

View Employee by Employee Name

� In order to get the employee related information then branch admin

requires this functionality. This is another way to search or view

employees which all are working there either presently or before.

Reset password

� If employee forgets his/her password and requests to change the

password then his/her login needs to be updated with newly generated

password. This can be done by Admin.

Log out

This is to be logged out from the system.

Customer Executive Module

Employee Login

� Customer executive must have a valid employee Id and password to

login to the system.

� If a wrong password is given thrice in succession, that Customer

executive will be locked and the Customer executive will not be able to

use it. When an invalid password is entered a warning is given to the

user that his account is going to get locked.

Search By Customer Account Number

� Customer executive gets information of customer based on the customer

account number to process the request given by the Customer.

Security Verification for Customer

� This is required to check whether the customer who requested is a valid

customer or not. When this verification is successfully done Customer

executive will get whole details about Customer.



Check Balance Info

� Customers can get the information about the balance in their account

through customer care executive.

Cheque Clearance Enquiry

� Customer can get the information about the cheque clearance which they

had put for the collection through customer care executive.

Add Requests

� Customer can request for blocking the transactions through debit card in

the case when he losses the card. Customer has to provide his account

number to blocking the lost card.

� Request for new card.

� Request for resetting the pin number to the debit card. If customer forgot

his password then he/she is not able to access his card. By making a

request to resetting password he/she can get new password for future

access.

� Customer can request for change of address.

� Customer can request for change of contact number.

� Customer can request for change of email.

� Customer can request for monthly e-statements.

� Customer can request for monthly statements physically.

� Executive adds the request and issues a request id for the customer.

� Track the requests based on the request id. If any customer made any

request before. At the time of request an unique request id is generated

and it is given to the customer for future inquiry. By this request id any

customer can get his/her request status. Customer executive uses this

request id for tracking status of any request made by customers.

Logout

� This is to be logged out from the system



Back-Office Module Functionality:

Back-Office employee login

� Employee must have a valid employee ID and password to login to the

system. This valid employee ID and password is generated by Admin

View Requests

� The requests added by the Customer executives can be viewed by the

Back-Office employee to process the request. The status of request may

be either pending or complete.

Update Requests

� The Back-Office employee after processing the request updates the

status of the request. If any request is pending then Back-Office

employee has to process the request and after processing it he/she has to

update the requests.

Logout

� This is to be logged out from the system.



4. REQUIREMENTS ANALYSIS

4 .1 Int roduct ion:

Requirement Analysis is a software Engineering task that bridges the gap between

System level requirement Engineering and Software design. Any computer based system

development phase will begin with preliminary analysis of the system scope and

feasibility. This phase is also known as Survey phase.

This phase determines whether or not significant resources to be committed to the other

phases of the life cycle. During the survey phase, we will define the scope of the system,

including all end-users perceived the problems and opportunities, business and technical

constraints, system goals and possible situations.

4.2 Feasibility Study:

Once the problem is clearly understood, the next step is to conduct the feasibility

study, which is a high level capsule version of the entire system analysis and design

process. The objective is to determine whether the proposed system is feasible. The

feasibility study documents the analysis of the business problem, including the

determination of whether it can be solved effectively. The operational (will it work?),

economical (costs and benefits?) and technical (can it be built?) aspects are part of the

study. Results of the phase determine whether the solution should be implemented.

The purpose of the feasibility study was two fold. Its first objective was to

develop a verification methodology that the gap between formal verification and

simulation in a way that would integrate into an existing design flow. The second

objective was to gather some quantitative evidence to support the idea that such a

methodology would offer advantages over our existing simulation based verification

techniques. This selection reflected the importance we place on the functional verification

of leading edge processors; however the methodology is applicable to most designs. The



choice of the decoder made it possible to investigate the problems of modeling and test

specification while simplifying other tasks, in particular the translation from abstract to

concrete tests. The feasibility study is conducted on following aspects.

4.3 Technical feasibility:

The technical issues usually raised during the feasibility stage of the investigation

include these

� Does the necessary technology exist to do what is suggested (and can not

be acquired).

� Does the proposed equipment have the technical capacity to hold the data

required using the new system?

� Will the proposed system provide adequate responses to inquiries

regardless of the number or location of users?

� Can the system be expanded if developed?

� Are there technical guarantees of accuracy, reliability, ease of access, and

data security?

4.3.1 Economical Feasibility:

A system that can be developed technically and that will be used if installed must still be

a good investment for the organization. Financial benefits must equal or exceed the cost.

The financial and economic questions raised by analysts during the preliminary

investigation for the purpose of estimating the following.

� The cost to conduct a full systems investigation.

� The cost of hardware and software for the class of application being

considered.

� The benefits in the form of reduced costs or fewer costly errors.

The cost if nothing changes (i.e., the proposed system is not developed



4.3.2 Operational Feasibility:

Proposed projects are beneficial only if they can be turned into information

systems that will mettle that will organization’s operation requirements.

� Is their sufficient support for the project from management? From users?

If the current system is well liked and used to the extend that persons will

not be able to see reasons for a change, There may be resistance.

� Are current business methods acceptable to the users? If they are not users

may welcome a change that will bring about a more operation useful

system.

� Have the users been involved the planning and development of the

project? Early involvement reduced the chances of resistance to the system

and changes in general and increases the likelihood of successful projects.

� Will the proposed system cause harm? Will it produce poorer results in

respect area? Will use of control result in any area will accessibility of

information be lost? Will individual customers be affected in an

undesirable way? Will the system show performance in any areas?



5. DATA MODELING

5 .1 In t roduct ion:

Underlying the structure of database is the data model. A collection of conceptual tools

for describing data, data relationships, data semantics and consistency constraints is called data

model. The various data models that have been proposed fall into three groups, object-based

models and physical models

The Entity-Relationship Diagram:

The ERD depicts a relationship between data objects. The ERD is the notation that is used to

conduct the data modeling activity. The attributes of each data object noted in the ERD can be

described using a data object description. At first a set of primary components is identified for

ERD that is data objects, attributes, relationships and various type indicators. Data objects are

represented by labeled rectangles; relationships are indicated with labeled line connecting

objects.

DATA MODELING (E-R DIAGRAMS):

The over logical structure of a database can be expressed graphically by an E-R

diagrams. The relative simplicity and pictorial clarity of this diagramming technique may

well account in large part for the widespread use of the E-R model. Such a diagram

consists of the following major components.

� Rectangles, which represent entity sets

� Ellipse, which represent attributes

� Diamonds, which link attributes to entity sets and entity sets to relationship

sets.

� Lines, which link attributes into entity sets and entity sets to relationship sets.

� Dashed ellipse, which denote derived attributes

� Double lines, which indicate total participation of an entity



Notations:

Entity Sets

Attributes

Relationships

Links between entities and attributes



5.2 E-R Diagram:

Admin

Admin ID Paw

Manage

View all Emp

Create Emp Disable Emp

View Emp by Email

Update Emp

View Emp By Id

Employee Emp_id

Emp_age

Emp_mail

Emp_ph

Password

Emp_Name

Emp_Gender

Emp_Status

Emp_Add_ID

Emp_Quali Emp_Type

Res_No

Mobile_No State

Door_No

Street City

Emp_Type

Manage

Status Of req.

Add new Req.

Processing Req

Search Cus.Inf.

Reset Pass

Search Req Change Add

Block Card

Account No



Update Inf. Change phone

Req. Card

Back Office Emp.

Manage

View all Req

View req. by status

View req. by date

Update The Req

Send req. to Back office team

Customer

Cus.ID Cus.Name

Cus.Name

Password

Account Id

Email-Id

Phone-Id Add. Id

Res._no Mob-No

Door_no. Street State



5.3 Data Flow Diagram:

DATA FLOW DIAGRAM (DFD) is one of the most important modeling tools. It is

used to model the system components. These components are the system process, the

process, an external entity that interacts with the system, uses the data and the

information flows in the system.

DFD shows how the information moves through the system and how it is

modified by a series of transactions. It is a graphical technique that depicts information

flow and that information that is applied as data moves from input to output.

A level 0 DFD, also called as the context diagram represents the entire system as

a single module with input and output indicated by incoming and outgoing arrows

respectively. Additional process and information flow paths are represented as the level 0

DFD is portioned to reveal more details. The context diagrams for the project

management system are shown in the figure.

A level 1 DFD, also called as top-level DFD represents the system major module

and data stores. The other level will show each module in the top-level DFD in more

detailed fashion. The top-level and other level DFD’S for our system are shown below.

Notations:

DATA FLOW : Data move in specific direction from an origin to a destination. The data

flow is a “packet” of data.

PROCESS: People, procedures or devices that produce data the physical component

is not identified.



SOURCE OR DESTINATION OF DATA: External sources or destination of data,

which may be people of organization or other entities.

DATA STORE: Here the data referenced by a process in the system.

0 –Level

Level -1

Input Output System

CST

Admin

Employee



Level Admin Panel Database Database

Admin Home

Login

Restore password

Add Emp

View Emp by ID

Update Emp

View Emp by Name

Change Password

Logout



Level-2 For Employee Module (Customer Executive Panel): Database

Database

Customer Executive Panel

Login

Logout

View Request by Request ID

Add Request

Search by Customer Account No

Track Request by Request ID



Level-2 Back-Office Team: Database Database

Back Office Team Panel

Login

Logout

View Requests

Update Request



Level-3 Add Request (in Customer Executive Module): Database Database

Add Request

Block Card

Request for New Card

Request for Contact Change

Request for E-mail Change

Request for Account Statement

Request for New Cheque Book



5.4 CLASS DIAGRAM:

Admin Module

AdminId:Admin Name Pwd :Password

Add Employe Employe Name Employe Id Password Address Phone E-mail Update Employe Disable Employe View Employe by Id Reset Employe Password Logout

Employe Id:Employe Name Pwd :Password Employe Login Search Customer Account No. Customer security Verification Chuck balance inf. Cheque clearance enquiry Add Requests Add Requests

Employe Module

Back Office Module

login for Back office employe

View requests Update requests Logout Monthly

e-statements monthly

physical statements

Track the Requests Logout



5.5Use Case Diagram For Administrator: Administrator

Login

Logout

Create Employee

Update Employee

Add Employee

Disable Employee

View Emp. By Email id

View Emp.by Eid



Use Case Diagram For Employee

Login

Search Requests

Add Requests

Cheque clearance enquiry

Search Customer Account No.

Customer security Verification

Processing Req.

Search Status Req.

Block Card

Reset Pin

Update Req.

new debit

card



Use Case Diagram For Back Office Module:

Back office Login

Monthly e-statements

monthly physical

statements

Request for

cheque book

Track the requests

Logout



5.5 SEQUENCE DIAGRAMS : Sequence diagram for ADMINISTRATOR: 1. Login 2. Check details 3. Add Employee Update Employee 4. Disable Employee 5. Create login 6. Update login 7. View Emp.by Eid

:Administrator

:Login :Update Employee

:Disable Employee

:Create :Update : View Emp.by Eid



Sequence diagram for Executive Module:

Login/Register : Employee

Login

CategoryAction

View Category

Register Register Failed

Login Failed

Security verify

AddRequest

Action

ViewByAccNo

View account

AddRequest



Sequence diagram for Back Office Module:

Login/Register : Employee

Login

CategoryAction

View Category

Register Register Failed

Login Failed

Track the requests

Monthly e-tatements

Action

monthly hysical statements



5.7 DATA DICTIONARY:

A DATA DICTIONARY (DD), as the name implies, is a repository of

information about data. In some database systems, the stored definitions of data

(schemas) provide all the necessity data dictionary information. In others, the DATA

DICTIONARY is supplementary. The information in the DATA DICTIONARY is about

types of data and uses of data.

The DATA DICTIONARY provides lists of data items sequenced alphabetically

classification, keyword etc, the DATA DICTIONARY provides a consistent description

of data as well as consistent data names for programming and retrieval. The advantages

of a DATA DICTIONARY are not only consistent of data description and naming, but

also ease of updating where one data description serves many purposes.

DATA DICTIONARY may be used by the database administrator to enforce

standards for names and descriptions; those who create data must follow these standards.

Creating and DATA DICTIONARY requires significant effort to remove past

inconsistencies and ambiguities.

FIELD DATATYPE SIZE CONSTRAINT

AD_UserID INT 11 NOT NULL

AD_UName VARCHAR 20 NOT NULL

AD_Pwd VARCHAR 20 NOT NULL

EMP_ID INT 11 PRIMARY KEY

EMP_FNAME VARCHAR 20 NOT NULL

EMP_MNAME VARCHAR 20 NOT NULL

EMP_LNAME VARCHAR 20 NOT NULL

EMP_UNAME VARCHAR 20 NOT NULL

EMP_PWD

VARCHAR 20 NOT NULL

EMP_TYPE

VARCHAR 20 NOT NULL

EMP_QUALI

VARCHAR 20 NOT NULL

EMP_EMAIL VARCHAR 20 NOT NULL

EMP_AGE

INT 11 NOT NULL

EMP_GENDER

VARCHAR 20 NOT NULL



EMP_STATUS

VARCHAR 20 NOT NULL

EMP_ADDR_ID INT 11 PRIMARY KEY

DOOR_NO VARCHAR 20 NOT NULL

STREET VARCHAR 20 NOT NULL

CITY VARCHAR 20 NOT NULL

STATE VARCHAR 20 NOT NULL

EMP_PHONE_ID INT 11 PRIMARY KEY

MOBILE_NO LONG 20 NOT NULL

RESD_NO LONG 20 NOT NULL

CUSTOMER_ID INT 11 PRIMARY KEY

USER_NAME VARCHAR 20 NOT NULL

PASSWORD VARCHAR 20 NOT NULL

FIRST_NAME VARCHAR 20 NOT NULL

LAST_NAME VARCHAR 20 NOT NULL

EMAIL_ID VARCHAR 20 NOT NULL

ADDRESS_ID INT 11 PRIMARY KEY

STREET VARCHAR 20 NOT NULL

CITY VARCHAR 20 NOT NULL

STATE VARCHAR 20 NOT NULL

PHONE_ID INT 11 PRIMARY KEY

MOB_NO LONG 20 NOT NULL

RES_NO LONG 20 NOT NULL

ACCOUNT_NO INT 11 PRIMARY KEY

ACCOUNT_TYPE VARCHAR 20 NOT NULL MIN_BALANCE DOUBLE 20 NOT NULL

ACC_BALANCE DOUBLE 20 NOT NULL

BRANCH_NAME VARCHAR 20 NOT NULL

DEBIT_CARD_NO LONG 20 PRIMARY KEY

INITIAL_PIN_NO

INT 11 NOT NULL

PRESENT_PIN_NO

INT 11 NOT NULL

VALIDITY DATE 40 NOT NULL

CHEQUE_BOOK_ID INT 11 PRIMARY KEY

CHEQUE_NO

DOUBLE 20 NOT NULL

CHEQUE_STATUS

VARCHAR 20 NOT NULL

TRANSACTION_ID INT 11 PRIMARY KEY



TRANSACTION_DATE

DATE 40 NOT NULL

AMOUNT

DOUBLE 20 NOT NULL

TRANSACTION_TYPE

VARCHAR 20 NOT NULL

REQUEST_ID INT 11 PRIMARY KEY

REQUEST_DATE

DATE 40 NOT NULL

REQUEST_TYPE

VARCHAR 20 NOT NULL

REQUEST_STATUS

VARCHAR 20 NOT NULL

DESCRIPTION

VARCHAR 20 NOT NULL

REQ_COMPLETED

DATE 40 NOT NULL



6. SYSTEM DESIGN:

6 .1 In t roduct ion:

Design is the first step in the development phase of any engineered process or

system. It may be defined as “the process of applying various techniques and principles

for the purpose of defining a device, a process, or a system insufficient detail to permit its

physical realization”.

Software design is an interactive process through which requirements are

translated into a “Blue Print” for construction of the software. The design is represented

at a high level of abstraction a level that can be directly translated to specific data,

functional and behavioral requirements.

Preliminary design is concerned with the transformation of requirements into a

data and software architecture. Detail design focuses on refinements to the architectural

representation. That leads to detailed data structure and algorithmic representation of

software.

System design is the process of planning of new system or one to replace an

existing system. It is an interactive process through which requirements are translated

into the software. During this stage the analyst works with the user to develop a physical

model of the system. In the design step, the element of the analyst model gets converted

into a data design, an architectural design, an interface design and a procedural design

In the design step the element of the analysis model gets converted into a data design, an

interface design, and a procedural design. The data design transforms the information

domain model created during the analysis into the data structures that will be required to

implement software. The architectural design defines the relationship among major

structural elements of the program. The interface design describes how the software

communicates with in itself, to systems that interoperate with it, and humans who use it.

An interface implies a flow of information (e.g., data and/ or control). Therefore, the data

and control flow diagrams provide the information required for interface design .



Design principles:

Basic design principles that enable the software engineer to navigate the design process

are:

� The design process should not suffer from ‘tunnel vision’.

� The design should be traceable to the analysis model.

� The design should not reinvent the wheel.

� The design should minimize the intellectual distance between the software and

the problem, as it exists in the real world.

� The design should exhibit uniformity and integrity.

� The design should be structured to accommodate the changes.

� The design should be reviewed to minimize.

Design Process

The three characteristics that serve as a guide for the evolution of good design of

a software design are as follows.

� The design must implement all of the explicit requirements contained in the

analysis model and it must accommodate all the implicit requirements of

customer.

� The design must be readable, understandable, guide for those who generates

code and for those who test and subsequently maintain the software.

� The design should provide a complete picture of the software addressing the

data functional and behavioral domains from an implementation perspective.



6.2 DATA BASE DESIGN:

The goal of database design is to generate a set of relation schemas that allows us to retrieve information easily. We can achieve optimization, ease of use in maintenance by designing the database using relational model in which data is stored in the form of tables and there exists a relation between or among the table.

The design objectives must be:

� To reduce redundancy.

� To arrive at loss-less join.

� To reduce the times as compared to the preset system, and

� To reduce the number of errors.

6.3 NORMALIZATION:

Normalization is a process of minimization of redundancy related to non-primary keys.

Before designing any system, normalization of databases is done for the following

reasons,

� To reduce the redundancy of stored data.

� To avoid loss of data.

� To structure the data, and

� To permit simple retrieval of data

First normal form: a relation is in 1NF if the insertion of any column and row contains

only one value (no repeating groups).

Second normal form: A table in 2NF is also in 1NF if the values in every column are

functionality dependent on the complete primary key ’’.

Third normal form: Columns are not transitively dependent on the primary key. A

relation is in 2NF is also in 3NF if the value in every non-key columns are not

transitively dependent on the primary key. Conversion to third normal form removes

transitive dependences by splitting the relation into two relations technique so that it

should be flexible to access and store the value in it. So the third normal form is applied

and all the tables are normalized accordingly.



6.4 ARCHITECTURAL DESIGN: Response User Page

Response Response user request with unnamed

& password

Login page with login Page Forward Forward If name & Password not matched If name & Password matched Database Fig: Two tier- Architecture

Admin

Login Validation User page



As shown in the diagram Admin will request for login page and system responds with login page. Users fill the login form with user name password and again sense this as request to system. Then validation will be done and if user name and password are correct then action is forward to user requested page otherwise again login pages are sent response to Admin.

6.5 USER INTERFACE DESIGN:

A GUI uses icons to represent objects, a pointing device to select operations, and

graphic imaginary to represent relationships. Once the analysis is complete, developers

can start designing the user interfaces for the objects and determining how these objects

are to be presented. The main goal of the user interface is to display and obtain needed

information in an accessible, efficient manner

The design of the software’s interface, more the any thing else, affects how a user

interacts and therefore experiences an application. It is important for a design to provide

users the information it they need and clearly tell them how to successfully complete the

task. A well-designed UI has visual appeal that motivates users to use the application. In

addition it should use the limited screen space efficiently.

1. The design of interface interfaces between software modules-internal interfaces.

2. The design interfaces interact between the software and other external entities like

non-human producers and consumers of information external interface.

3. The design interface between a human and the computer.

Navigation

Navigation design represents the navigation flow between content objects of the

system. Navigation should be simple and consistent. It should also be designed in a

manner, which is intuitive and predictable the user should understand hoe o move from

one screen to another without having to search for navigation links or instructions.



Error massages

Error messages provide timely help to the novice users that what data is to be giving to the system, which correct and which is not correct. This system provides complete set of error

message in a timely manner and helps a lot to the new user. Our system provides

the error messages wherever needed and provides timely help to the new users. Some of

the error messages that are provided in our system are:

For example, if the learner miss field by giving the data at particular field then the

system will give error message.” Blanks fields are not allowed”. Thus appropriate error

message help the data entry operator to give correct values and see to that field of a form

are entered.

The following are the possible error messages while working with the system:

Error messages Description

Invalid username or password Incorrect username or password

Field should not be empty Appropriate field will not left blank

Table problems Would not connect properly

Invalid date Defect date must be older than rectified

date



7. Table Analysis:

In order to construct effective database, the normalization technique applied

according to the process that is proposed to make effective retrieval and storage of data

and analysis has gives as follows.

TABLE STRUCTURE :

Table 1: ADMIN_TABLE:

SNO COLUMN NAME DATA TYPE CONSTRAINT

1 AD_UserID INT NOT NULL

2 AD_UName VARCHAR NOT NULL

3 AD_Pwd VARCHAR NOT NULL

Table 2: EMPLOYE_INFO_TABLE:


1 EMP_ID INT PRIMARY KEY

2 EMP_FNAME VARCHAR NOT NULL

3 EMP_MNAME VARCHAR NOT NULL

4 EMP_LNAME VARCHAR NOT NULL

5 EMP_UNAME VARCHAR NOT NULL

6 EMP_PWD

VARCHAR NOT NULL

7 EMP_TYPE

VARCHAR NOT NULL

8 EMP_QUALI

VARCHAR NOT NULL

9 EMP_EMAIL

VARCHAR NOT NULL

10 EMP_AGE

INT NOT NULL

11 EMP_GENDER

VARCHAR NOT NULL

12 EMP_STATUS

VARCHAR NOT NULL

13 EMP_ADDR_ID

INT FOREIGN KEY (1 to n) 14 EMP_PHONE_ID

INT FOREIGN KEY

(1 to 1)



Table 3: EMPLOYE_ADDRESS_TABLE:


1 EMP_ADDR_ID INT PRIMARY KEY

2 DOOR_NO VARCHAR NOT NULL

3 STREET VARCHAR NOT NULL

4 CITY VARCHAR NOT NULL

5 STATE VARCHAR NOT NULL

Table 4: EMPLOYE_PHONE_TABLE:


1 EMP_PHONE_ID INT PRIMARY KEY

2 MOBILE_NO LONG NOT NULL

3 RESD_NO LONG NOT NULL

Table 5: CUSTOMER_TABLE:


1 CUSTOMER_ID INT PRIMARY KEY

2 USER_NAME VARCHAR NOT NULL

3 PASSWORD VARCHAR NOT NULL

4

FIRST_NAME VARCHAR NOT NULL

5

LAST_NAME VARCHAR NOT NULL

6

EMAIL_ID VARCHAR NOT NULL

7

ADDRESS_ID INT FOREIGN KEY (1 TO 1) 8

PHONE_ID INT FOREIGN KEY

(1 TO 1) 9

ACCOUNT_ID INT FOREIGN KEY (1 TO 1)



Table 6: CUSTOMER_ADDRESS_TABLE:


1 ADDRESS_ID INT PRIMARY KEY

2 DOOR_NO INT NOT NULL

3 STREET VARCHAR NOT NULL

4 CITY VARCHAR NOT NULL

5 STATE VARCHAR NOT NULL

Table 7: CUSTOMER_PHONE_TABLE:


1 PHONE_ID INT PRIMARY KEY

2 MOB_NO LONG NOT NULL

3 RES_NO LONG NOT NULL

Table 8: CUSTOMER_ACCOUNT_TABLE:


1 ACCOUNT_NO INT PRIMARY KEY

2 ACCOUNT_TYPE VARCHAR NOT NULL

3 MIN_BALANCE DOUBLE NOT NULL

4 ACC_BALANCE DOUBLE NOT NULL

5 BRANCH_NAME VARCHAR NOT NULL

6 CUSTOMER_ID

INT FOREIGN KEY FOREIGN KEY

Table 9: CUSTOMER_DEBITCARD_TABLE:


1 DEBIT_CARD_NO LONG PRIMARY KEY

2 INITIAL_PIN_NO

INT NOT NULL

3 PRESENT_PIN_NO

INT NOT NULL

4

VALIDITY DATE NOT NULL

5 ACCOUNT_NO

INT FOREIGN KEY



Table 10: CUSTOMER_CHEQUE_TABLE:


1 CHEQUE_BOOK_ID INT PRIMARY KEY

2 CHEQUE_NO

DOUBLE NOT NULL

3 CHEQUE_STATUS

VARCHAR NOT NULL

4 ACCOUNT_NO

INT FOREIGN KEY

Table 11: CUSTOMER_TRANSACTION_TABLE:


1 TRANSACTION_ID INT PRIMARY KEY

2 TRANSACTION_DATE

DATE NOT NULL

3 AMOUNT

DOUBLE NOT NULL

4 TRANSACTION_TYPE

VARCHAR NOT NULL

5 ACCOUNT_NO

INT FOREIGN KEY

Table 12: CUSTOMER_REQUEST_TABLE:


1 REQUEST_ID INT PRIMARY KEY

2 REQUEST_DATE

DATE NOT NULL

3 REQUEST_TYPE

VARCHAR NOT NULL

4 REQUEST_STATUS

VARCHAR NOT NULL

5 DESCRIPTION

VARCHAR NOT NULL

6 REQ_COMPLETED

DATE NOT NULL



1.Welcome Page



2. Admin Login Page



3.When fields are empty



4.When characters are less

5.When username and password not matched with Database



6. Home Page of Admin



7.To create a new Employee



8. validations for the form



9. added employee



10. diableing employee by email-1d



11. validations for diableing employee



12. Disableing success



13. 13. view employees



14. view employee results



15.view employee by eid



16.validations



17. search results



18. Updating the employee info



19. Updated



20. view by email



21.results



22.update



23.updated



1. Employee login page



9. SYSTEM TESTING: 9.1 In t roduct ion:

The extent of testing a system is controlled by many factors, such as risks involved,

limitations on resources, and deadlines. In light of this issue, we must deploy a testing

strategy that does the “Best” job of finding the defects in a product with in the given

constraints. There are many testing strategies, but mostly testing uses a combination of

these: Black box testing, White box testing, Top down testing, Bottom up testing.

TESTING OBJECTIVES:

� Testing is a process of executing a program with the intent of finding an error

� A good case is not that has a high probability of finding an error.

A successful test one that uncovers a yet undiscovered error. If testing is conducted

successfully it will uncover error in the software. Testing cannot show the absence of

defects. It can only show the software defects are present.

TESTING PRINCIPLES:

Before applying methods to design effective test cases, A software engineer must

understand the basic principles that guide a software testing (1).

� All tests should be traceable to customer requirements

� Test should be planned long before testing beginnings.

� Testing should begin “in small” and progress towards testing “in large”.

� Exhaustive testing is not possible.

� To be most effective, an independent third party should conduct testing.

9.2 TEST CASE DESIGN:

The primary objective for test case is to drive a set of tests that has the highest

likelihood for uncovering defects in software. Testing is the process of executing a

program with the intent of finding as a yet and discovered error. To accomplish these

objectives, two different categories of test case technique is used.



After test plan and before going to test design test case is important. According to

the system requirements we have to test some conditions to ensure the quality of

software. For the purpose of testing these conditions we have to prepare test cases.

9.3 BLACK BOX TESTING:

In a black box, the test item is treated as “black” since its logic unknown: all that is

known is what goes in and what comes out, or the input and output. In black box testing

you try various inputs and examine the resulting outputs, you can learn what the box does

but nothing more about how its conversion is implemented. Black box testing works very

nicely in the testing objects in an object oriented environment.

TEST CASE 1:

In this test case we check the overall performance of the system from first page to last

page. It means that, 1st the administrator enters into the system and checks for the

module and performs all actions accordingly and produces the output. Thus black box

testing tells that the system works well for the given set of inputs and produces the

outputs as expected.

Test Case Examples

1. First, the administrator enters into the system by giving their user name and

password, if it is correct he or she enters the main menu. Otherwise the system

should display error message like “invalid user”.

2. If the production people try to select the audit process, then the system shows the

error message like “your are not right people to do this process”

9.4 WHITE BOX TESTING:

White box testing assumes that the specific logic is important and must be tested

to guarantee the system’s proper functioning. The main use of the white box testing is in

error based testing. It is predict on close examination of procedural detail logical



providing test cases that exercise specific sets of conditions and/or loops tests path

enough the software.

White box testing technique is also called basis path testing. The basis path

method enables the test case designer to derive a logical complexity of a procedural

design and use this measure as a guide for defining as basis set of execution path.

9.5 TESTING STRATEGIES:

Software testing is known element of verification and validation.

Verification refers to the set of activities that ensure the software correctly implement a

specific function. Validation refers to the different set of activities that ensure that the

software has been built is traceable to user requirements.

UNIT TESTING:

Unit testing focuses on the verification effort on the smallest unit of software

design. This is white box oriented. In the keying application system each and every

module is tested in the following ways. The modules interfaces are tested ensure the

information properly flows into and put the program unit and test.

All independent paths through the control structure are exercised to ensure that

all statements in a module have been executed at least once. Error handling paths are

tested.

INTEGRATION TESTING

Integrating testing is a systematic technique for constructing the program structure

while conducting tests to uncover errors associated with interfacing. The objective is to

take unit tested modules and build a program.

TOP DOWN INTEGRATION :

It is an incremental approach to construct a program structure. Modules are

integrated by moving down ward through hierarchy, beginning with the main control

module.



BOTTOM UP INTEGRATION:

Bottom up integration testing, as the name implies, begins construction and

testing with atomic modules. Because modules are integrated from the bottom up,

processing required for modules subordinates to a given level is always available.

REGRESSION TESTING:

Each time new module added as a part of integration testing, the software

changes. New data flow paths are established. Regression testing is the re-execution of

some subsets of tests that have been conducted to ensure that changes have not

propagated and intended side effects. It is the activity that helps to ensure that changes do

not introduce additional errors.

The regression testing is done in this system because each module depends on the

other module. For example mismatch module depends on key, and verify.

VALIDATION TESTING:

At the culmination of integration testing, software is completely assembled as a

package, interfacing errors has been uncovered and corrected and a final series of

software tests-validation testing begins.

Validation testing can be defined in many ways, but a simple definition that

validation succeeds when the software functions in a manner that can be reasonably

expected by the user/customer. Software validation is achieved through a series of black

box tests that demonstrates conformity with requirements.

After validation test has been conducted one of the possible conditions exists. The

function or performance characteristics conform to specification and are accepted. The

primary goal of the validation is:



� To assess and improve the quality of various products generated during

software development and modification.

� High quality is best achieved by careful attention to the details of systematic

planning, analysis and implementation.

� It is incorrect to view source code testing as a primary vehicle for quality

improvement.

10. SYSTEM IMPLEMENTATION:

10 .1 Introduct ion:

Implementation includes all those activities that take place to convert from the old

system to the new. The new system may be totally new; replacing an existing manual or

automated system, or it may be a major modification to an exiting system. In either case,

proper implementation is essential to provide reliable system to meet organization

requirements.

During the implementation stage, the system is physically created. Necessary

programs are coded, debugged and documented. The test plan is implementation includes

the following activities.

Obtaining and installing the system hardware:

� Installing the system and making it run on its intended hardware.

� Providing use access to the system.

� Training the users on the new system.

� Documenting the system for its users and for those who will be responding

for maintaining it in the future.

� Making arrangement to support the as the system is used.

� Transferring on going responsibility for the system from its developers to

the operations or maintenance part.

� Evaluating the operation and use of the system.



The most visible component of implementation process is the system conversion. The

four basic conversion strategies include:

� Direct Conversion

� Parallel Conversion

� Pilot Conversion

� Phased Conversion

Direct Conversion:

In direct conversion, the organization stops using the old system and starts

using the new one at the same time.

Parallel Conversion:

Parallel conversion involves running both old system and new system and

comparing their results. The new system is accepted only the results have

matched for an acceptable period.

Pilot Conversion:

Pilot conversion means introducing the new system to a small part of the

organization, expanding its use once it is know to operate properly there.

Eventually, it will be in use by the entire organization.

Phased Conversion:

Phased conversion means introducing a system in stages, one component

or module at a time, waiting until that one is operating properly before

introducing the next.

The product that is being developed is proposed to be implemented using

parallel Conversion approach that will increase the user’s faith on the system.

10.2 Software and Hardware



Front end or User Interface Design

The entire user interface is planned to be developed in browser specific

environment with a touch of Intranet-Based Architecture for achieving the Distributed

Concept. The browser specific components are designed by using the dynamism of the

designed by concentrating on the constructs of the Java Server Pages.

Communication or Database Connectivity Tier

The Communication architecture is designed by concentrating on the Standards of

Hibernate. The database connectivity is established by using the Hibernate. The standards

of three-tire architecture are given major concentration to keep the standards of higher

cohesion and limited coupling for effectiveness of the operations.

SYSTEM MAINTENANCE

The system is completely maintained at any client system to handle all the efficient

process that is to be authorized.

User manual:

1. User manual is like a guide to the novice user

2. Each and every developed system should provide this manual.

3. The detail of the learner should be entered into the learner form.

4. Any additional services will be provided to the learner based on the learner

requirements.

5. The payments may be charged on course on course selection

11. Features of the Technology Used:



11.1 About Java

Initially the language was called as “oak” but it was renamed as “Java” in 1995.

The primary motivation of this language was the need for a platform-independent (i.e.,

architecture neutral) language that could be used to create software to be embedded in

various consumer electronic devices.

� Java is a programmer’s language.

� Java is cohesive and consistent.

� Except for those constraints imposed by the Internet environment, Java gives the

programmer, full control.

Finally, Java is to Internet programming where C was to system programming.

Importance of Java to the Internet

Java has had a profound effect on the Internet. This is because; Java expands the

Universe of objects that can move about freely in Cyberspace. In a network, two

categories of objects are transmitted between the Server and the Personal computer. They

are: Passive information and Dynamic active programs. The Dynamic, Self-executing

programs cause serious problems in the areas of Security and probability. But, Java

addresses those concerns and by doing so, has opened the door to an exciting new form

of program called the Applet.

Features Of Java

� Security

� Portability

� The Byte code

� Java Virtual Machine (JVM)

� Simple

� Object-Oriented



� Robust

� Network-Savvy

� Architecture Neutral

� High Performance

� Multithreaded

Overall Description

Picture showing the development process of JAVA Program

Java programming uses to produce byte codes and executes them. The first box

indicates that the Java source code is located in a. Java file that is processed with a Java

compiler called javac. The Java compiler produces a file called a. class file, which

contains the byte code. The. Class file is then loaded across the network or loaded locally

on your machine into the execution environment is the Java virtual machine, which

interprets and executes the byte code.

Java Architecture:

Java architecture provides a portable, robust, high performing environment for

development. Java provides portability by compiling the byte codes for the Java Virtual

Machine, which is then interpreted on each platform by the run-time environment. Java is

a dynamic system, able to load code when needed from a machine in the same room or

across the planet

.

Compilation of code:

Java source Java byte code JVM

Java .Class



When you compile the code, the Java compiler creates machine code (called byte

code) for a hypothetical machine called Java Virtual Machine (JVM). The JVM is

supposed to execute the byte code. The JVM is created for overcoming the issue of

portability. The code is written and compiled for one machine and interpreted on all

machines. This machine is called Java Virtual Machine.

Compiling and interpreting Java Source Code

During run-time the Java interpreter tricks the bytecode file into thinking that it is

running on a Java Virtual Machine. In reality this could be a Intel Pentium Windows 95

or SunSARC station running Solaris or Apple Macintosh running system and all could

receive code from any computer through Internet and run the Applets.

11.2 JAVA SERVER PAGES (JSP)

Source Code ……….. ………..

PC Compiler

Macintosh Compiler

SPARC

Java Byte code (Platform indepen dent)

Java Interpreter (PC)

Java Interp reter (Macintosh)

Java Interpreter (Sparc)



Java server Pages is a simple, yet powerful technology for creating and

maintaining dynamic-content web pages. Based on the Java programming language, Java

Server Pages offers proven portability, open standards, and a mature re-usable component

model .The Java Server Pages architecture enables the separation of content generation

from content presentation. This separation not eases maintenance headaches, it also

allows web team members to focus on their areas of expertise. Now, web page designer

can concentrate on layout, and web application designers on programming, with minimal

concern about impacting each other’s work.

Features of JSP

Portability:Java Server Pages files can be run on any web server or web-enabled

application server that provides support for them. Dubbed the JSP engine, this support

involves recognition, translation, and management of the Java Server Page lifecycle and

its interaction components.

Components :It was mentioned earlier that the Java Server Pages architecture can include

reusable Java components. The architecture also allows for the embedding of a scripting

language directly into the Java Server Pages file. The components current supported

include Java Beans, and Servlets.

Processing: Java Server Pages file is essentially an HTML document with JSP scripting

or tags. The Java Server Pages file has a JSP extension to the server as a Java Server

Pages file. Before the page is served, the Java Server Pages syntax is parsed and

processed into a Servlet on the server side. The Servlet that is generated outputs real

content in straight HTML for responding to the client.

Access Models:A Java Server Pages file may be accessed in at least two different ways. A

client’s request comes directly into a Java Server Page. In this scenario, suppose the page

accesses reusable Java Bean components that perform particular well-defined

computations like accessing a database. The result of the Beans computations, called



result sets is stored within the Bean as properties. The page uses such Beans to generate

dynamic content and present it back to the client.

In both of the above cases, the page could also contain any valid Java code. Java

Server Pages architecture encourages separation of content from presentation.

11.3 Servlet:

A Servlet is a java class that runs on a server (web server ) and does the

processing for the dynamic web pages of a web application that’s why servlet for a web

applications are written by web programmers not web designers.After the processing is

dome by using the println method of an object.

11.4 Introduction to Struts Framework

Servlet technology’s the primary base on which you can create web applications

with Java. Java Server Pages (JSP) technology is based on Servlet technology but extends

it by allowing HTML content to be created easily.

JSP technology doesn’t replace Servlet Technology, but rather builds on it, to

address some of its deficiencies. Struts follow MVC design pattern, and build on servlet

and JSP technologies to address their shortcomings. These shortcomings are in two broad

areas.

What is Struts?

Struts Frame work is the implementation of Model-View-Controller (MVC) design

pattern for the JSP. Struts is maintained as a part of Apache Jakarta project and is open

source. Struts Framework is suited for the application of any size.

Model-View-Controller (MVC) Architecture:



Model-View-Controller architecture is all about dividing application components into

three different categories Model, View and the Controller. Components of the MVC

architecture have unique responsibility and each component is independent of the other

component. Changes in one component will have no or less impact on other component.

Model: Model is responsible for providing the data from the database and saving the data

into the data store. All the business logic are implemented in the Model. Data entered by

the user through View are check in the model before saving into the database. Data

access, Data validation and the data saving logic are part of Model.

View: View represents the user view of the application and is responsible for taking the

input from the user, dispatching the request to the controller

and then receiving response from the controller and displaying the result to the user.

HTML, JSPs, Custom Tag Libraries and Resources files are the part of view component

Controller:Controller is intermediary between Model and View. Controller is responsible

for receiving the request from client. Once request is received from client it executes the

appropriate business logic from the Model and then produce the output to the user using

the View component. ActionServlet, Action, ActionForm and struts-config.xml are the

part of Controller.



The Struts framework separates the View, Controller and Model layers of MVC

architecture. It does not concern itself with the implementation details of business-logic

and data-access tiers.

Basic Directory Structure for Developing a Web-Based Application

using Struts Framework

Struts Flow

web.xml

<servlet> <servlet-name>action</servlet-name> <servlet-class>org.apache.struts.action.ActionServlet </servlet-class> <init-param> <param-name>config</param-name> <param-value>WEB-INF/struts-config.xml</param-value> </init-param> <load-on-startup>1</load-on-startup> </servlet> <servlet-mapping>



<servlet-name>action</servlet-name> <url-pattern>*.do<url-pattern> </servlet-mapping>

11.5 HIBERNATE:

Hibernate is the persistence framework which deals with database interaction

mainly. Hibernate framework was introduced by “Red hat” division. Architect of

Hibernate is “garin king”. Some other product from “Red hat”

are“JBOSS”,”Linux”,”a4j”(ajax4jsf)etc.

APPLICATION SERVER DESCRIPTION:

Tomcat is the flagship of the Apache software foundation’s Jakarta project. Apache

tomcat is the servlet container that is used in the official reference implementation for the

java servlet and java server pages technology.The Java servlet and java server pages

specifications are developed by Sun under the java community process.

Apache tomcat is developed in an open an participatory

environment and released under the Apache S/W license. Apache tomcat is intended to be

a collaboration of the best of breed developers from around the world.



Apache tomcat powers numerous large scales, mission critical web

applications across a diverse range of industries and organizations.

Features of Hibernate:

Hibernate is a persistence framework which sits on top of JDBC Technologies. in Hibernate we

are not responsible to get the do the connection, to create JDBC connection, to prepare SQL

query etc. hibernate will do all those for the developer.

Hibernate is “ORM” tool and is No:1 among other existing ORM tools available in the market.

ORM stands for “Object Relation Mapping”. ORM means mapping the java objects to

corresponding underlying database tables. Hibernate is providing various kinds of powerful

mapping techniques

1. Simple ORM mapping

2. Collection mapping

3. Inheritance mapping

4. Polymorphic mapping /interface mapping

5. Association mapping

Hibernate use batch update internally to avoid the traffic between application and

database information server, powerful catching techniques to increase the application

performance, flexible transaction model that deals internally with JDBC transaction

management and JTA transaction. Hibernate provides easiest locking machine for the

concurrent transaction and powerful object-oriented query language called HQL and also

Hibernate provide other query language supports like QBC(query by criteria),QBE(query

by example) and many more features.

Configuration class:

1. Configuration object is the first object going to use to interact with the hibernate

2. System.

3. Configuration object is light weight single threaded object which provides session

4. Factory object.

5. Configuration object contains all the properties specified in the Hibernate



6. Configuration file and all the mappings documents defined with this

Configuration

7. Object builds the session factory.

8. Once session factory is constructed there is no use with Configuration object.

Session factory :( org.Hibernate package)

� Session factory object is long live, single threaded object.

� Session factory will be constructed with the help of Session factory object.

� There will be one Session factory object for entire application for database.

� Session factory is a factory of Session factory object.

� Session factory is high level object which will be used by Hibernate developer.

Session Object: (org.Hibernate)

� Session Object is short live, single threaded object.

� Session Object will be taken from Session factory and there will be one session

for user.

� This Session represents amount of time user is interacting with the database.

� Session is a factory of transaction.

� Some time Hibernate Session may span to multiple transactions.

� Session Object is also called as “Persistent manager” because it is playing the key

role in persistent operation.

� Session Object is the high level object which will be used by Hibernate developer.

Transaction factory: (org.hibernate.package)

� This is low level object which will be used hibernate system internally.

� It is a factory of transactions.

� Transaction objects created by Transaction factory will be supplied to session

object from the session user will take the transaction.

1. Local Transaction

2. JTA Transaction



� Hibernate, by default provides JDBC Transaction because internally Hibernate

uses JDBC Transaction factory class by default.

� This default mechanism is not good enough for the Production system.

� We can change the default transaction factory class with your own Transaction

factory class this provides to property inside hibernate configuration file.

Connection Provider: (org.hibernate.package)

� ConnectionProvider: is the low level object which will be used by hibernate

system internally.

� It is a factory of database connections.

� ConnectionProvider: object provides the following 2 types of Connections.

1. DriverManager Connection (JDBC Connection)

2. Data Source Connections.

� By default Hibernate provides Driver Manager Connections. Which are not good

enough for the production systems.

� By providing a property in the Hibernate Configuration file we can change the

default connection management to your own data source connection management.

Transactions:

� Transactions are the high level object which is used to perform unit of work.

� In one Transaction we can perform multiple database operations.

Types of object:

� In hibernate we can see three types of object

� Transient object

� Persistent object

� Detached object



� When object is not involved in Hibernate session operation then that

object is called as transient object. The state of this object is called

Transient state.

� Transient object doesn’t contain any identity i.e., value will not be

assigned to primary key of Persistent object.

� Persistent object will have an identity which means Hibernate generates a

value for the primary key fields.

� That value can be access in 2 ways

� using getIdentifer() method of session

� Ex: sas.getIdentifier (stu);

� By using corresponding getter method

� Ex: stu.getsid ();

� When object is remote from hibernate system then it is called detached object.

� Detached object will contain the value for the primary key fields. But will not

be accessed by get Identifier () methods.

� Hibernate is using the following 3 J2EE API’s internally

1. JDBC API

2. JNDI API

Types of Hibernate mapping:

1. Simple or Mapping

2. Collections Mappings

3. Inheritance Mapping

4. Association Mapping



Association Mapping

This mapping is used to establish the relationship between persistent classes. We

can establish following three types of relationships between various Hibernate persistent

classes

1. one-one relationship

2. one-many relationship

3. many- many relationship

� The above 3 relationship can be establish in two ways

1. Unidirectional

2. Bi-directional

� Specifying the direction of relationship is called directionality

11.6 OVERVIEW OF MySql:

MySQL(Connector/JDriver)

MySQL Connector/J is an implementation of Sun's JDBC 3.0 API for the

MySQL relational database server. It strives to conform as much as possible to the JDBC

API as specified by JavaSoft. It is known to work with many third-party products,

including Application Servers (Apache Tomcat, JBoss, Weblogic, and IBM WebSphere),

Object Relational Mapping Tools (Hibernate, Apache ObjectRelationalBridge,

CocoBase, Kodo), Development Environments (Eclipse, Borland JBuilder, IBM

WebSphere Studio)

Driver file: The .jar, .zip or .class file that contains the JDBC driver

Download link: http://dev.mysql.com/downloads/

Connection URL: Specify the location of the JDBC data provider

<host_name>: The IP address or the domain name of the database server

<port_number>: The port number to the database. Default is 3306

<database_name>: The name of the database to connect



User: User name to login to the database

Password: Password of the user name specified

Standard & Requirement Software’s:

Required Technical Skills: JSP, Servlet, Struts, MySql, JAVA, J2EE, Hibernate,

Tomcat Server, My Eclipse.

Software Requirements:

Web Server - Apache Tomcat 4.0

Front end - HTML

Script - JavaScript

Middle Tier - Servlets2.0

Back end - My-sql

Standard Environment:

Software Version

OS Windows VISTA/XP/ Windows 2003

Memory 2GB

CPU 2.8GHz

RAM 1GB

JDK/JRE Sun J2SDK 1.4.01

Enterprise Edition Sun J2EE 1.4

JSP JSP1.2

Struts Jakarta stuts2.0

Database MySql 5.0

Hibernate Hibernate3.0

Tomcat Server Jakarta Tomcat5.5



My Eclipse MyEclips6.0

12. CONCLUSION:

This project plays as heart of the one banking company without

developing or having this type of Customer Support Tool..

Fundamentally this was developed for supporting the customer by customer care

executives who are working in any banking company customer care unit. When any

request is done by any customer by making a phone call to the customer care executives,

they have to process their request according the request. If solution can be done at same

time then executives have to clear request on spot. But if request done by customer is not

done at the same time then executives has to generate a request id for corresponding

customer. This request id will be use by customer for future correspondence. The

processed request will be send to the back-office team. This team has to view the request

and solve this. After completing the request back-office team has to make the status of

that request as complete which was earlier as pending or in progress.



13.



13.1 Reference Books:

� Roger S Pressman, “Software Engineering – A Practitioner’s approach” McGraw

– Hill International Editions, Fifth Edition, 2001

� Herbert Schildt & Patrick Naughton, “Java2 Complete Reference”, Tmh 3/e, 1999

� George Mc Daniel, “IBM Dictionary of Computing”, Tata McGraw Hill, Tenth

Edition, 1993

� Neelesh Shaw, “History of MySql and Database”, Published by Tata Mc Graw

Hill 3 rd Edition, 2002

13.2 Reference Websites:

� www.google.com � www.sun.java.com � www.java.net

sdsoft solutions(india) pvt. ltd.dspace.cusat.ac.in/jspui/bitstream/123456789/4243/... · sdsoft...

Documents