ONLINE HELP DESK

A PROJECT REPORT SUBMITTED ON PARTIAL

FULFILLMENT FOR THE AWARD OF THE DEGREE

OF

BACHELOR OF TECHNOLOGY

IN

COMPUTER SCIENCE AND ENGINEERING

BY

D.VARDHANI (06531A0545)

I.USHA V LAKSHMI (06531A0544)

CH.SRIKANTH REDDY (06531A0534)

Y.S.N.MURTHY (06531A0541)

Under the esteemed guidance of

T.RAJESH M.TECH

DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING

AKULA SREE RAMULU COLLEGE OF ENGINEERING

(AFFILIATED TO JNTU, KAKINADA)

TETALI , TANUKU-534 211 W.G.DT., (A .P.)

 AKULA SREE RAMULU COLLEGE OF ENGINEERING

TETALI, TANUKU-534211

(AFFILIATED TO JNTU, KAKINADA,A.P)

BONAFIDE CERTIFICATE

This is to certify that, the project entitled “ONLINE HELP DESK” is the bonafied work done
D.VARDHANI(06531A0545), I.USHA V LAKSHMI (06531A0544),CH.SRIKANTH REDDY
(06531A0534), Y.S.N.MURTHY (06531A0541),Of IV B.TECH submitted in partial fulfillment
of the requirement for the award of the Award of the Degree of

BACHELOR OF TECHNOLOGY

IN

COMPUTER SCIENCE AND ENGINEERING

Internal guide Head of the Department

External Examiner
 Acknowledgement

I would like to thank Dr. T.Madhu, principal for his timely suggestions.

I would like to express my grateful thanks to Mr.Ch.Yuvraju, M.tech, H.O.D., C.S.E DEPT.
for his valuable suggestions and guidance in regarding the software Analysis. Design and also
for his continuous effort in successful completion of the Project.

My deep gratitude to my internal guide Mr.T.Rajesh M.tech. I thank him for his dedication,
guidance, council and keen interest at every stage of the project. And also I would like to express my
deep indebtedness and whole hearted thanks for his full-fledged support and encouragement.

Last but not least, I am debited to all people who have contributed in some way or the other in the
completion of this project work.

D.VARDHANI

I.USHA V LAKSHMI

CH.SRIKANTH REDDY

Y.S.N.MURTHY
ONLINE HELP DESK
 Index
1. Introduction

1.1) About the Project

1.2) About the Company

2. System Requirements

2.1) Hardware Requirements

2.2) Software Requirements

2.3) Installation Procedure

2.4) Software Description

3. System Analysis

3.1) Existing System

3.2) Proposed System

4. System Design

4.1) Project description

4.2) Data Flow Diagram

4.3) Table Structure

5. System Testing and Implementation

5.1). Testing Fundamentals

5.2). Implementation
6. Maintenance

6.1). Corrective Maintenance

6.2). Adaptive Maintenance

6.3). Enhance Maintenance

7. Appendix
7.1). Sample forms

7.2). Sample codlings

8. Conclusion

9. Bibliography
 INTRODUCTION

ABOUT THE PROJECT

This project aimed is at Online Service and Information Management System for
campus to provide services for the facilities in the campus. This is an Intranet based
application that can be accessed throughout the campus .This system can be used to
automate the work flow of service requests for the various facilities in the campus .This
is one integrated system that covers different kinds of facilities like library, classroom
and canteen .Registered users (students, faculty ,lab- assistants and others) will be able
to login a request for service for any of the supported facilities. These requests will be
sent to the concerned people, who are also valid users of the system, to get them
resolved. There are features like a additional of a new facility to the system, report
generators, displaying general campus information etc in this system.
ABOUT THE COMPANY

SRI JAIN TECHNOLOGIES established in 1995, has been actively involved in the

development of Customized Software for various clients since its inception and also has its

presence strongly felt in the areas of Training and Consulting. Market Leadership through

customer satisfaction, a commitment to excellence & high growth rate, these have

characterized HSL in its rapid climb in the information Technology Industry.

DEVELOPMENT:

Our software development strives to develop innovative software that

meets customer needs. A team of developed with exclusive educational background and excellent

computing skills, exert their maximum efforts and endeavors to satisfy the specialized requirement of

our esteemed clients. Our expertise and vast exposure qualifies us in developing software in

Information Systems, Web Based Applications, Internet Solutions, Web Page Designing and Hosting.

Our team consists of expertise in Java, VC++, VB, Oracle and all Internet Application Development

Tools.
CONSULTING:

The training division gives us an opportunity to meet variety of candidates

with various skill sets. Our database consists of details regarding more than 1000

professionals. So we are fit to assist all sort of IT Human resource consultancies and IT

Companies in India and Abroad.

Excellence through “TEAM WORK” – The Philosophy of Total

Quality Management is inculcated in every HSL employee through intensive training

programmers. Our investment on a highly skilled and motivated manpower

constitutes towards establishing HSL as a truly quality conscious company,

continually striving to bring the finest solution to the discerning customers.

 SYSTEM REQUIREMENTS

Hardware Requirements

 Processor : PENTIUM IV

 RAM : 128 MB

 Hard Disk : 40 GB

Software Requirements

 Web Server : Apache Tomcat Server 4.0

 Browser : Internet Explorer

 Server side scripting : JSP, Java

 Database : MS-Access

 Language : J2EE

 Client side scripting : HTML

 Operating System : Windows 2000/Windows XP

SYSTEM ANALYSIS

System analysis focuses on specifying for what the system or the

application is required to do. It allows the individuals to see the logical elements (what the
system should do) apart from the physical components it uses (computers, terminals and
storage system). It is the process of gathering and interpreting facts, diagnosing problems and
using the information to recommend improvements to the system.

1 Existing System

The existing system is the system its containing file downloading options
only for selecting particular domain, after domain selected it will display all domain related
topics. And it will show the all related links. User may select the particular link and they may
download the specified topics. But in this Existing system there is no option for file uploading.
There are chances for changing the scheme report and do malpractice. This system involves a
lot of manual entries with the applications to perform the desired task.

Less efficiency, less accuracy and less productivity. Time delay for selecting the
domain area’s as well as the file. Persons who are present in different part of the LAN
cannot transact efficiently.

3.2 Proposed System:

The proposed system is designed to eliminate the drawbacks of the existing

system. It is designed by keeping to eliminate the drawbacks of the present system in order to

provide a permanent solution to the problems. The primary aim of the new system is to
speedup transactions. The report is prepared for the schemes and implemented by the

concerned officials. User can uploading the specified file to the particular domain.

Since the advent of Virtual Class Room services in the Middle Ages Student

have used windows Explorer, select the particular Drive, Folder, the specified file. It comes as

no surprise to one that when everything is being converted to easily. User can upload the file

for the specified

 SYSTEM DESIGN

The word system is possibly the most overused and abused term in the technical
lexicon. System can be defined as the “a set of fact, principles, rules etc., classified and
arranged in an orderly form so as to show a logical plan linking the various parts” here the
system design defines the computer based information system. The primary objective is to
identify user requirements and to build a system that satisfies these requirements.

Design is much more creative process than analysis. Design is the first step in the
development of any system or product. Design can be defined as “the process of applying
various techniques and principles for the purpose of defining a device, a process or a system in
sufficient detail to permit its physical realization”.

It involves four major steps they are

1. Understanding how the system is working now;

2. Finding out what the system does now;

3. Understanding what the new system will do; and

4. Understanding how the new system will work.

In this Online Help Desk, User does not view the specified file directly. Then the Admin
can upload the specified file in to the particular domain as well as the Area. So as to avoid these
difficulties, a new system was designed to keep these requirements in mind. Therefore the long
process operation has been changed into easy GUI based environment, such that the user can
retrieve the records in a user-friendly manner and it is very easy to navigate to the
corresponding information.
 PROJECT DESCRIPTION

INPUT DESIGN

Input design is the bridge between users and

information system. It specifies the manner in which data enters the system for
processing it can ensure the reliability of the system and produce reports from accurate
data or it may results in output of error information.

Online Service and Information Management System is an IT Solution provider for a dynamic
environment where the entire information about the organization in coagulated. This approach
focuses basically on building and interface between the user and organization to submit their
queries and requests.

SIM’SRANGE OF EXPERTISE INCLUDES:

 Advanced information providing

 Data ware Housing
 Data Integration
 ConsultingThe application aims at applying technology with innovation and
responsibility to achieve two broad objectives:

 Effectively address the queries and requests of the users.

 Provide the full fledged information about the organization coagulated
at one place.
 This approach rests on :

 A strategy where we architect, integrate and manage technology

services and solutions-we call it AIM for success.
 A robust off shore development methodology and reduced demand on
customer resources.

The product offers customers the advantages of:

SPEED:

They understand the importance of timing .Instead of striving for different information of
sources situated at different locations the entire information about each and every field is
coagulated at one single place and provides the customer to place his queries or requests any
there itself.

EXPERTISE:
Our teams combine cutting edge technology skills with rich domain expertise. What’s
equally important – they share strong customer orientation that means they actually start by
listening to the customer. They ‘re focused on coming up with solutions that serve customer
requirements today and anticipate future needs.
 A FULL SERVICE PORT FOLIO
They offer customers the advantage of being able to architect, integrate and manage technology
services .This means that they can really on one, fully accountable source instead of trying to
integrate disparate multi vendor solutions.
 DATAFLOW DIAGRAM
Online Help Desk

Home Service Information

Admin Admin Help

HOD General Help

Faculty About SIM

Student About
Organization

Library

Transport

Canteen

Home

Database
 Table Structure

File Table

Field name Data type Size

Administrator Text 50

HOD Text 50

Faculty Text 50

Student Text 150

Librarian Text 150

Transport Text 50

Canteen Text 50
 Java Technology Over View

Java technology is both a programming language and a platform.

The Java Programming Language

The Java programming language is a high-level language that can be characterized by all
of the following buzzwords:

 Simple  Architecture neutral

 Object oriented  Portable

 Distributed  High performance

 Interpreted  Multithreaded

 Robust  Dynamic

 Secure

Simple:-

It is simple for professional programmer to learn & they can use it effectively. If we
already know object oriented programming, then learning java is very easy. It inherits syntax
from c & object oriented features from c++, so if the user knows c\c++ then it will be a easy way
to do effective java programming.

Secure:-
 As we know many people are effected by viral infection when they download an
executable file or program. Rather than, virus programs we have malicious programs that can
gather private information, such as credit card number, bank account balances & passwords by
searching the contents of your computers local file system. Java has a better answer for this
effects i.e., “FIREWALL” between networked application and your computer.

Portable:-

As already we have discussed about compatibility of operating system, computers, chips.

In Internet the programs have to be dynamically downloaded to all the various types of
platforms. For this purpose java program will generate a byte code (which is not a executable
code). Byte code is a highly optimized set of instructions designed to be executed by java run
system, which is called as JVM (Java Virtual Machine).

Object-Oriented:-

Java is purely object oriented. The object model in java is simple and easy to extend,
while simple types, such as integers, are kept as high-performance non-objects.

Robust: -

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 development. At the same time, java frees you from having to worry about many of the
most common causes of programming errors. Because java is a strictly typed language, it checks
your code at Compile time. Java is robust for two reasons; they are Memory management &
mishandled exceptional task in traditional programming environments.
With most programming languages, you either compile or interpret a program so that you can
run it on your computer. The Java programming language is unusual in that a program is both
compiled and interpreted. With the compiler, first you translate a program into an intermediate
language called Java byte codes —the platform-independent codes interpreted by the interpreter
on the Java platform. The interpreter parses and runs each Java byte code instruction on the
computer. Compilation happens just once; interpretation occurs each time the program is
executed. The following figure illustrates how this works.

You
can think of Java bytecodes as the machine code instructions for the Java Virtual Machine (Java
VM). Every Java interpreter, whether it’s a development tool or a Web browser that can run
applets, is an implementation of the Java VM. Java bytecodes help make “write once, run
anywhere” possible. You can compile your program into bytecodes on any platform that has a
Java compiler. The bytecodes can then be run on any implementation of the Java VM. That
means that as long as a computer has a Java VM, the same program written in the Java
programming language can run on Windows 2000, a Solaris workstation, or on an iMac.
The Java Platform
A platform is the hardware or software environment in which a program runs. We’ve
already mentioned some of the most popular platforms like Windows 2000, Linux,
Solaris, and MacOS. Most platforms can be described as a combination of the operating
system and hardware. The Java platform differs from most other platforms in that it’s a
software-only platform that runs on top of other hardware-based platforms.

The Java platform has two components:

 The Java Virtual Machine (Java VM)
 The Java Application Programming Interface (Java API)
You’ve already been introduced to the Java VM. It’s the base for the Java platform and is
ported onto various hardware-based platforms.
The Java API is a large collection of ready-made software components that provide many
useful capabilities, such as graphical user interface (GUI) widgets. The Java API is
grouped into libraries of related classes and interfaces; these libraries are known as
packages. The next section, What Can Java Technology Do?, highlights what
functionality some of the packages in the Java API provide.
The following figure depicts a program that’s running on the Java platform. As the figure
shows, the Java API and the virtual machine insulate the program from the hardware.

Native code is code that after you compile it, the compiled code runs on a specific
hardware platform. As a platform-independent environment, the Java platform can be a
bit slower than native code. However, smart compilers, well-tuned interpreters, and just-
in-time bytecode compilers can bring performance close to that of native code without
threatening portability.

JAVASCRIPT OVERVIEW
INTRODUCTION

JavaScript is an interpreted, object-based scripting language. Although it

has fewer capabilities that full-fledged object-oriented like C++ and Java, JavaScript is
more than sufficiently powerful for its intended purposes. JavaScript is not a cut-down
version of any other language; it is not a simplification of anything. It is, however,
limited. You cannot write standalone application in it, and it has little capability for
reading or writing files. Moreover, JavaScript script can run only in the presence of an
interpreter, either in a web server or a web browser.

JavaScript is loosely typed language. That means you do not have to declare that data
types of variables explicitly.

It is scripting language used to develop Internet applications mostly for

client side validations. It has the features of windows, frames, buttons, forms, images,
list boxes, applets and so on.

MAIN FEATURES:

Most of the browsers support JavaScript. It has all the functionalities of a high level
language. It supports OOPS.

JAVASCRIPT IN VB SCRIPT:
 Microsoft Visual Basic Scripting Edition, the newest member of the
Visual Basic family of programming languages, brings active scripting to a wide
variety of environments, including web client scripting to a wide variety of
environments, including web client scripting in Microsoft Internet Explorer and Web
server scripting in Microsoft Internet Information Server.

VBScript talks with host applications using ActiveX scripting. With

ActiveX scripting, browsers and host applications do not require special integration
code for each scripting component. ActiveX scripting enables a host to compile
scripts, obtain and call entry points, and manage the namespace available to the
developer.

HYPERTEXT MARKUP LANGUAGE (HTML)

INTRODUCTION

HTML is a major language of the Internet’s World Wide Web. Web sites
and web pages are written in HTML. HTML files are plain-text files so they can be
edited on any type of Computer IBM, Mac, UNIX, Intel etc. The World Wide Web is
a collection of linked documents or pages on millions of computers spread over the
entire internet. HTML which defines their appearance and layout and more
importantly creates the links to other documents.

A set of instructions embedded in a document is called Markup

Language. These instructions describe what the document text means and how it
should look in a display. The language also tells you how to make a document with
other document on your local system, the World Wide Web and other Internet
resources such as FTP.

Brief History of HTML:

HTML was originally developed by time Berners lee which at CERN, and popularized
by the mosaic browser developed at NCASA. During of the course of the 1990’s it has
blossomed with the explosive growth of the Web. During this time, HTML has been
extended in a number of ways. The Web depends on Web page authors and vendors
sharing the same conversions for HTML. This has motivated the join work on
specifications for HTML. HTML 2.0 was developed under the aegis of the Internet
Engineering Task Force (IETF) to codify common practice in late 1994. HTML has
been developed with the version that all manner of devices should be able information
the Web. Computers with high or low and bandwidth.
 Document Structure Elements:
HTML documents are composed of four parts:

A HTML document begins with a line declaring which version of HTML is being used to
create the document.

A HTML document that describes the documents as a HTML document.

A declarative header section which is enclosed in the <HEAD> element

The main body of the document which contains the actual document content. The body
can be contained within either the <BODY> elements.

The “head” section is opened and closed by <HEAD> and </HEAD> tags.
Information about the document such as the title, indexing information and ownership.
The “body” section is opened and closed by <BODY> and </BODY> tags. The text
and images of the document itself to be displayed by the Web browser.

JAVA DATABASE CONNECTIVITY (JDBC)

 JDBC AND ODBC IN JAVA:
Most popular and widely accepted database connectivity called Open
Database Connectivity (ODBC) is used to access the relational databases. It offers the
ability to connect to almost all the databases on almost all platforms. Java applications
can also use this ODBC to communicate with a database. Then we need JDBC why?
There are several reasons:

 ODBC API was completely written in C language and it makes an

extensive use of pointers. Calls from Java to native C code have a number of
drawbacks in the security, implementation, robustness and automatic portability of
applications.
 ODBC is hard to learn. It mixes simple and advanced features together,
and it has complex options even for simple queries.
 ODBC drivers must be installed on client’s machine.
Architecture of JDBC:
JDBC Architecture contains three layers:

JDBC Application

JDBC Drivers

JDBC Drivers

1. Application Layer: Java program wants to get a connection to a database. It

needs the information from the database to display on the screen or to modify the
existing data or to insert the data into the table.
2. Driver Manager: The layer is the backbone of the JDBC architecture. When
it receives a connection-request form.
3. The JDBC Application Layer: It tries to find the appropriate driver by
iterating through all the available drivers, which are currently registered with Device
Manager. After finding out the right driver it connects the application to appropriate
database.
4. JDBC Driver layers: This layer accepts the SQL calls from the application
and converts them into native calls to the database and vice-versa. A JDBC Driver is
responsible for ensuring that an application has consistent and uniform m access to
any database.

when a request received by the application, the JDBC driver passes the request to
the ODBC driver, the ODBC driver communicates with the database and sends the
request and gets the results. The results will be passed to the JDBC driver and in turn
to the application. So, the JDBC driver has no knowledge about the actual database, it
knows how to pass the application request o the ODBC and get the results from the
ODBC.

The JDBC and ODBC interact with each other, how? The reason is both the
JDBC API and ODBC are built on an interface called “Call Level Interface” (CLI).
Because of this reason the JDBC driver translates the request to an ODBC call. The
ODBC then converts the request again and presents it to the database. The results of
the request are then fed back through the same channel in reverse.
 Structured Query Language (SQL):

SQL (Pronounced Sequel) is the programming language that defines and

manipulates the database. SQL databases are relational databases; this means simply
the data is store in a set of simple relations. A database can have one or more table.
You can define and manipulate data in a table with SQL commands. You use the data
definition language (DDL) commands to creating and altering databases and tables.

You can update, delete or retrieve data in a table with data manipulation
commands (DML). DML commands include commands to alter and fetch data.

The most common SQL commands include commands is the SELECT

command, which allows you to retrieve data from the database.

In addition to SQL commands, the oracle server has a procedural

language called PL/SQL. PL/SQL enables the programmer to program SQL statement.
It allows you to control the flow of a SQL program, to use variables, and to write
error-handling procedures
Architecture

JPS pages are high level extension of servlet and it enable the developers to embed java code in
html pages. JSP files are finally compiled into a servlet by the JSP engine. Compiled servlet is
used by the engine to serve the requests.

javax.servlet.jsp package defines two classes:

 JSP Page

 Http JSP Page

These classes defines the interface for the compiled JSP page. These interfaces are:

 jspInit()
  jspDestroy()
 _jspService(HttpServletRequest request,HttpServletResponse response)
  

In the compiled JSP file these methods are present. Programmer can define jspInit() and
jspDestroy() methods, but the _jspService(HttpServletRequest request,HttpServletResponse
response) method is generated by the JSP engine.

INTRODUCTION TO JSP TAGS

In this lesson we will learn about the various tags available in JSP with suitable examples. In JSP
tags can be divided into 4 different types. These are:
    

1. Directives:
In the directives we can import packages, define error handling pages or the session
information of the JSP page.
    
2. Declarations
This tag is used for defining the functions and variables to be used in the JSP.
   
3. Scriptlets
In this tag we can insert any amount of valid java code and these codes are placed in
_jspService method by the JSP engine.
   
4. Expressions
We can use this tag to output any data on the generated page. These data are
automatically converted to string and printed on the output stream.
   

Now we will examine each tags in details with examples.

DIRECTIVES

Syntax of JSP directives is:

<%@directive attribute="value" %>

Where directive may be:

1. page: page is used to provide the information about it.

Example: <%@page language="java" %> 
   
2. include: include is used to include a file in the JSP page.
Example: <%@ include file="/header.jsp" %> 
  
3. taglib: taglib is used to use the custom tags in the JSP pages (custom tags allows us to
defined our own tags).
Example: <%@ taglib uri="tlds/taglib.tld" prefix="mytag" %> 
   

and attribute may be:

1. language="java"
This tells the server that the page is using the java language. Current JSP specification
supports only java language.
Example: <%@page language="java" %> 
   
2. extends="mypackage.myclass"
This attribute is used when we want to extend any class. We can use comma(,) to import
more than one packages.
Example: <%@page language="java" import="java.sql.*,mypackage.myclass" %> 
   
3. session="true"
When this value is true session data is available to the JSP page otherwise not. By default
this value is true.
Example: <%@page language="java" session="true" %> 
  
4. errorPage="error.jsp"
errorPage is used to handle the un-handled exceptions in the page.
Example: <%@page language="java" session="true" errorPage="error.jsp"  %> 
   
5. contentType="text/html;charset=ISO-8859-1"
Use this attribute to set the mime type and character set of the JSP.
Example: <%@page language="java" session="true"
contentType="text/html;charset=ISO-8859-1"  %
 INTRODUCTION TO JSP SCRIPTLETS

Syntax of JSP Scriptles are:

  <%
  //java codes
   %>

JSP Scriptlets begins with <% and ends %> .We can embed any amount of java code in the JSP
Scriptlets. JSP Engine places these code in the _jspService() method. Variables available to the
JSP Scriptlets are:

 request:
request represents the clients request and is a subclass of HttpServletRequest. Use this
variable to retrieve the data submitted along the request.
Example:
  <%
  //java codes
   String userName=null;
   userName=request.getParameter("userName");
   %>
 response:

Syntax of JSP Scriptles are:

<%
  //java codes
   %>

JSP Scriptlets begins with <% and ends %> .We can embed any amount of java code in the JSP
Scriptlets. JSP Engine places these code in the _jspService() method. Variables available to the
JSP Scriptlets are:

 request:
request represents the clients request and is a subclass of HttpServletRequest. Use this
variable to retrieve the data submitted along the request.
 Example:
  <%
  //java codes
   String userName=null;
   userName=request.getParameter("userName");
   %>
 response:
response is subclass of HttpServletResponse.
 
 session:
session represents the HTTP session object associated with the request.
 
 out:
out is an object of output stream and is used to send any output to the client.
 Other variable available to the scriptlets are pageContext, application,config and
exception.

JSP EXPRESSIONS

Syntax of JSP Expressions are:

  <%="Anything"   %>

JSP Expressions start with 

Syntax of JSP Scriptles are with <%= and ends with  %>. Between these this you can put
anything and that will converted to the String and that will be displayed.

Example:
  <%="Hello World!" %>
Above code will display 'Hello World!'.
 IMPLEMENTATION
Once the system has been designed, the next step is to convert the
designed one in to actual code, so as to satisfy the user requirements as excepted. If
the system is approved to be error free it can be implemented.

When the initial design was done for the system, the
department was consulted for acceptance of the design so that further proceedings of
the system development can be carried on. After the development of the system a
demonstration was given to them about working of the system. The aim of the system
illustration was to identify any malfunctioning of the system.

Implementation includes proper training to end-users. The

implemented software should be maintained for prolonged running of the software.

Initially the system was run parallel with manual system.

The system has been tested with data and has proved to be error-free and user-friendly.
Training was given to end -user about the software and its features.
 MAINTENANCE

The term “software maintenance” is used to describe the software

engineering activities that occur following delivery of a software product to the customer. The
maintenance phase of the software life cycle is the time period in which a software product
performs useful work.Maintenance activities involve making enhancement to software
products, adapting products to new environments and correcting problems. Software product
enhancement may involve providing new functional capabilities, improving user display and
modes of interaction, and upgrading external documents. Adaptation of software to a new
environment may involve moving the software to a different machine. Problem correction
involves modification and revalidation of software to correct errors. The enhancement of this
project can be accomplished easily. That is, any new functional capabilities can be added to the
project by simply including the new module in the homepage and giving a hyperlink to that
module. Adaptation of this project to a new environment is also performed easily.

Corrective Maintenance

Even with the best quality assurance activities, it is likely that they
customer will uncover defects in the software. Corrective maintenance changes the software to
correct defects

Adaptive Maintenance

An activity that modifies the software to properly interface with a

changing environment. The system has been modified so that various change include to the
new system.
In case of Fund Transfer, adoptive maintenance has been performed, that is in earlier system
(character based UNIX system) changes are fixed and if any new changes are to be included,
was a difficult task. Now provisions are given so that the user can define various changes. Such
as it designed to accommodate the new change in further.

Enhancement Maintenance

As software is used, the customer/user will recognize additional

functions that will provide benefit. Perceptive maintenance extends the software
beyond its original functional requirements.
 SYSTEM TESTING AND IMPLEMENTATION

TESTING FUNDAMENTALS

Software testing is an important element of S/W quality assurance and

represents the ultimate review of specification, design and coding. The increasing
visibility of S/W as a system element and the costs associated with a S/W failure are
motivating forces for well planned, through testing.

Though the test phase is often thought of as separate and

distinct from the development effort--first develop, and then test--testing is a
concurrent process that provides valuable information for the development team.

There are at least three options for integrating Project Builder

into the test phase:

Builder into the test phase:

 Testers do not install Project Builder, use Project Builder functionality to compile
and source-control the modules to be tested and hand them off to the testers, whose
process remains unchanged.
 the testers import the same project or projects that the developers use.

 Create a project based on the development project but customized for the testers (for
example, it does not include support documents, specs, or source), who import it.

A combination of the second and third options works best.

Associating the application with a project can be useful during the testing phase, as
well. We can create actions to automatically run test scripts or add script types and
make them dependent on the modules to test.
 TESTING OBJECTIVES

There are several rules that can serve as testing objectives.

They are

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

2. A good test case is one that has a high probability of finding an undiscovered
error.

3. A successful test is one that uncovers an undiscovered error.

If testing is conducted successfully according to the objectives stated

above, it will uncover errors in the software. Also, testing demonstrates that software
functions appear to the working according to specification, that performance
requirements appear to have been met.
OBJECT ORIENTED TESTING

UNIT TESTING

Unit testing focuses the verification effort on the smallest unit of

S/W design i.e., the module. The unit testing is always white-box oriented and the step
can be conducted in parallel for modules.

During unit test, testers can use the same project or projects as
the developers, if functional units organize the project, or separate projects have been
created for functional units. The project or projects can also be exported, so unit test
can take place in a variety of environments and on a variety of platforms.

UNIT TEST CONSIDERATIONS

The tests that occur as part of unit testing. The module

‘interface’ is tested to ensure that information properly flows into and out of the
program unit under test. The ‘local data structures’ are examined to ensure that data
stored temporarily maintains its integrity during all steps in an algorithms execution.

‘Boundary Conditions’ are tested to ensure that the module operates

properly at boundaries established to limit or restrict processing. All ‘independent

paths’ through the control structures are exercised to ensure that all statements in a

module have been executed at least once. Finally, all ‘error-handling paths’ are tested.
UNIT TEST PROCEDURES

Unit testing is considered an equivalent to the coding step. After

the source level code has been developed, reviewed and verified for correct syntax,
unit test case design begins since a module is not a stand alone program, ‘driver’
and/or ‘stub’ S/W must be developed for each unit test. In most applications, a driver
is nothing more than a main program that accepts test case data, passes such data to
the module to be tested, and prints the relevant results. The stubs serve to replace
modules that are subordinates called by the modules to be tested. A stub or a dummy
stub or a dummy subprogram uses the subordinate modules interface, may do minimal
data manipulation, prints verification of entry, and returns. The drivers and scrubs
represent overhead i.e., both are S/W that must be written but that is not delivered with
the final S/W product. If the drivers and the stub are kept simple, then the overhead is
low.

The Unit Test is carried out in this project, and is found successful.
The data is flowing correctly to all part of the project.

INTEGRATION TESTING

Integration testing is a systematic technique for constructing the

program structure while at the same time conducting test to uncover errors associated
with interfacing. The objective is to take unit-tested modules and build a program
structure that has been dictated by design.
 TOP-DOWN INTEGRATION

1. This method is an incremental approach to the construction of program

structure. Modules are integrated by moving downward through the control hierarchy,
beginning with the main program module.

Importing the test project and setting up the testing environment

The process of importing a test project and setting

up a testing environment is the same as the process for importing a project and setting
up the environment for development.

Adding test scripts and test data to the project

You may need to add some items, such as

test scripts, to the project. In addition, you may need to add connection strings to
database accounts containing test data.

Remember that you can automate the running of test scripts

just as you can automate actions associated with the modules in your application.

Modifying actions and macros to facilitate testing

If actions specifying "run with debugging" have not already been

provided, you can either modify existing actions to include a debug flag, or create new acti
 SCREENSHOTS

Online Help Desk Home Page

Service Management System Page
Login Page For Administrator
Login Page For HOD System
Login Page for Faculty
Login Page For Librarian
Information Management System Page
Information About The Organization
Information About CSE Department
Information About Mechanical Department
 CONCLUSION

There is popular saying that no activity in this world is complete. There is always a better
and easier of doing the same activity. This applies to this project also. There can be further
enhancements that can be done to this project.

As the fast changing trend in the software field clearly indicates, there will be new
software and efficient methods will be found to do the current things better.

We therefore, agree to the fact that ‘Change is the only permanent thing in life’. As time
changes, there will be new things but the old ones will not fade away. There will always be there
to help the new things to have a better footing.

BIBILOGRAPHY

 Java The Complete Reference - Herbert Schildt

 Jrun Web Application Construction Kit - Drew Falkman.
 JavaServerPages Application Development Kit - Stirling. M. Scott
 More Servlets and JavaServerPages - Prentice Hall PTR,2000.
 JavaServerPages (Developer’sGuide) - Blarry Burd, Hungry Minds Inc.,2001