You are on page 1of 67

1

UNIVERSITY COLLEGE OF ENGINEERING


KARIAVATTOM
THIRUVANATHAPURAM – 695581

JOBFINDER.COM
Mini - Project Report

Project report submitted in partial fulfillment of the requirement for


the award of Degree of Bachelor of Technology on Information
Technology under The University of Kerala.

By,
Krishna V P
krishna_vp@yahoo.co.in

DEPARTMENT OF INFORMATION TECHNOLOGY


2009-2010

CERTIFICATE
2

Department of information TECHNOLOGY


Uce, KARYAVATOM

Mini Project Report

Year 2010

Register No. :

Name : Krishna V P

Email : krishna_vp@yahoo.co.in

Branch : Information Technology

Semester : V1

CERTIFICATE
Department of information TECHNOLOGY
3

Uce, KARYAVATOM

This is to certify that the project work entitled


“JOB MANAGEMENT SYSTEM” is a bona fide work of
Krishna V P of the Department of Information Technology,
University of Kerala in partial fulfillment of the requirements for
the award of the B.Tech Degree in Information Technology of the
University of Kerala

Internal Guide External Examiner

TABLE OF CONTENTS

1. CERTIFICATION

2. ACKNOWLEGMENT
4

3. INTRODUCTION……...……………………..………..….……….01

4. ABSTRACT………………………………………………………..03

5. J2EE-AN OVERVIEW………………………………………….…05
i. INTRODUCTION…………. ……………...…….…06
ii. SECURITY………………. ……….….……………07

6. TECHNOLOGIES USED…………………………….…………..10
i. HTML……………………...………………………..11
ii. CSS……………………….…..…………………….11
iii. JAVASCRIPT……………..….………..…………..12
iv. SQL…………………………………...…………….12
v. SERVLET……………...………………….………..13
vi. JSP………………….…………………..…………..14
vii. SYNTAX SUMMARY………………………...……18
viii. THE JSP PAGE DIRECTIVE……………………. 21
ix. THE jsp:usebean ACTION………………………. 23
x. THE jsp:setProperty ACTION…………………….24
xi. CONVENTIONS……………………………………26
xii. AJAX………………….……………………………..27
xiii. APACHE TOMCAT………………………………..27

7. SCOPE OF THE PROJECT……………………………………..29

8. INTRODUCTION TO SYSTEM DESIGN AND


IMPLEMENTATION…………………………………………….…31
i. INTRODUCTION……………………...…….…….32
ii. JMS……………………………….………..……….32
iii. INPUT-OUTPUT DESIGN……………..…………33

9. SYSTEM ANALYSIS……………………………………………...34

10. DATABASE DESIGN………………………………………37


i. TABLES USED………………………….…………38
ii. SCHEMA DESCRIPTION…………….....………..39

11. USECASE DIAGRAMS AND CLASS DIAGRAM……….42


5

12. INTRODUCTION TO SYSTEM TESTING AND


IMPLEMENTATION……………………………….……….47

13. SYSTEM REQUIREMENTS………………………………56

14. CONCLUSION………….…………………………………..58

15. REFERENCES…………….……………………………….60

16. APPENDIX………...…….….………………………………62
6

INTRODUCTION

In this changing era, there is influence of Internet and electronic commerce


everywhere. Job sites replace employment exchangers. Employers as well as
jobseekers can register at the job site. Employers can post jobs, search resume,
etc and job seekers can apply for jobs. In this project named “Job Management
7

System” the same thing is done. Employers and job seekers have got separate
areas for registering. The employers can also post the job opportunities,
minimum qualification for the job and the details regarding the job. The job
seekers can search their jobs according to their skills and qualifications.

The platform used is J2EE (Java 2 Enterprise Edition). The front end of the
project is JSP (Java Server Pages) and the back end or database used is
MySQL.

The project is having high degree of security. The project is very user friendly.
The colorful and spectacular interface is another thing about the project.
Advanced technology is used for searching the job, viewing the resume and
posting the job. Advanced type of search technology will help the jobseekers to
find a very suitable job. The job seekers can also view the status of their applied
jobs .The employers can recruit skilled job seekers after viewing their resume
.The database used for the project is highly encrypted .The database is up-to-
date .Therefore the job seekers can apply for the latest and better jobs available.
This will help the employers to have the very best persons in their organization.

As told earlier ,the database is highly encrypted . Therefore no intruders can get
into it
or duplicate or edit the details. The project is having a logical 3 tier structure. This
is another feature of the project. The multi tiered structure will give a fast access
to all the places.
8

ABSTRACT

Job Management System is software which offers a simple, efficient and


consistent user experience in searching and offering jobs. It models the online
job websites. It is of great use and boom to both job seeker and employer.
9

Through a Job Management System the candidates can post their profile and
can be expected to be noticed by suitable employers. The employers can search
for suitable candidates matching their needs for qualifications and previous
experience.

The project is mainly divided in to three modules

1. Administrator
2. Employers
3. Job Seeker

ADMINISTRATOR:
Administrator has the overall control.
 User Registration Process
 Database Control
 View Details
Job Seekers
The person looking for job. He can perform the following functions
 Post personal details
 Search for companies
 Apply for job
Employers
Job seeker is the person who applies to the company for getting
job. He can perform the following functions.
 Search for candidates
 Post their vacancy details
Objective

 To aid all job seekers to find suitable opportunities

 To aid all possible employers to find suitable candidates based on


their requirements and qualifications without any hassle.
10

J2EE- AN OVERVIEW

INDRODUCTION
11

Today, more and more developers want to write distributed transactional


applications for the enterprise and thereby leverage the speed, security, and
reliability of server-side technology. In the fast-moving and demanding world of e-
commerce and information technology, enterprise applications must be designed,
built, and produced for less money, with greater speed, and with fewer resources
than ever before. To reduce costs and fast-track application design and
development, the Java 2 Platform, Enterprise Edition (J2EE) provides a
component-based approach to the design, development, assembly, and
deployment of enterprise applications. The J2EE platform offers a multitiered
distributed application model, reusable components, a unified security model,
flexible transaction control, and web services support through integrated data
interchange on Extensible Markup Language (XML)-based open standards and
protocols. Not only can you deliver innovative business solutions to market faster
than ever, but also your platform-independent J2EE component-based solutions
are not tied to the products and application programming interfaces (APIs) of any
one vendor. Vendors and customers enjoy the freedom to choose the products
and components that best meet their business and technological requirements.

Enterprises today need to extend their reach, reduce their cost, and lower their
responses times by providing easy-to-access services to their customers,
employees, and suppliers. Typically, applications that provide these services
must combine existing Enterprise Information Systems (EISs) with new business
functions that deliver services to a broad range of users. These services need to
be:

 Highly available, to meet the needs of today’s global business


environment.
 Secure, to protect the privacy of users and the integrity of the enterprise
 Reliable and Scalable, to insure that business transactions are accurately
and promptly processed.

In most cases, these services are architected as multi-tier applications. A middle


tier that implements the new services needs to integrate existing EISs with
business functions and data of the new service. The service middle-tier shields
first-tier clients from the complexity of the enterprise and takes advantage of
rapidly maturing web technologies to eliminate or drastically reduce user
administration and training while leveraging existing enterprise assets.

The Java 2 Platform, Enterprise Edition (J2EE) reduces the cost and complexity
of developing these multi-tier services, resulting in services that can be rapidly
deployed and easily enhanced as the enterprise responds to competitive
pressures.

J2EE achieves these benefits by defining a standard architecture that is


delivered as the following elements:
12

J2EE Application Model  A standard application model for developing multi-tier,


thin-client services.

J2EE Platform  A standard platform for hosting J2EE applications

J2EE Compatibility Test Suite  A suite of compatibility tests for verifying that a
J2EE platform product complies with the J2EE platform standard.

J2EE Reference Implementation  A reference implementation for


demonstrating the capabilities of J2EE and for providing an operational definition
of the J2EE platform.

Security
An enterprise contains many resources that can be accessed by many users.
Sensitive information often traverses unprotected open networks (example
Internet). In such an environment, almost every enterprise has security
requirements and specific mechanisms and infrastructure to meet them. Although
the quality assurances and implementation details may vary, they all share some
of the following characteristics:

 Authentication  The means by which communicating entities prove to


one another that they are acting on behalf of specific identities(example,
client to server or server to client)
 Access Control for Resources  The means by which interactions with
resources are limited to collections of users or programs for the purpose of
enforcing integrity, confidentiality, or availability constraints.
 Data Integrity  The means used to prove that information could not have
been modified by a third party (some entity other than the source of the
information). For example, a recipient of data sent over a open network
must be able to detect and discard messages that were modified after
they were sent.
 Confidentiality or Data Privacy  The means used to ensure that
information is only made available to users who are authorized to access
it.
 Non-Reputation  This means is used to prove that a user performed
some action such that the user cannot reasonably deny having done so.
 Auditing  this means is used to capture a tamper-resistant record of
security related events for the purpose of being able to evaluate the
effectiveness of security policies and mechanism.

The security behavior of a Java EE environment may be better understood by


examining what happens in a simple application with a web client, a JSP user
interface, and enterprise bean business logic.
13

In the following example the web client relies on the web server to act as its
authentication proxy by collecting user authentication data from the client and
using it to establish an authenticated session.

Step 1: Initial Request

In the first step of this example, the web client requests the main application URL

Since the client has not yet authenticated itself to the application environment,
the server responsible for delivering the web portion of the application (here after
referred to as web server) detects this and invokes the appropriate authentication
mechanism for this resource.

Step 2: Initial Authentication

The web server returns a form that the web client uses to collect authentication
data (for example, user name and password) from the user. The web client
forwards the authentication data to the web server, where it is validated by the
webserver.

The validation mechanism may be local to a server, or it may leverage the


underlying security services. On the basis of the validation, the web server sets a
credential for the user.

Step 3: URL Authorization

The credential is used for future determinations of whether the user is authorized
to access restricted resources it may request. The web server consults the
security
policy (derived from the deployment descriptor) associated with the web resource
to determine the security roles that are permitted access to the resource. The
web container then tests the user’s credential against each role to determine if it
can map the user to the role.
14

The web server’s evaluation stops with an “is authorized” outcome when the web
server is able to map the user to a role. A “not authorized” outcome is reached if
the web server is unable to map the user to any of the permitted roles.

Step 4: Fulfilling the Original Request

If the user is authorized, the web server returns the result of the original URL
request,

the response URL of a JSP page is returned, enabling the user to post form data
that needs to be handled by the business logic component of the application.
15

TECHNOLOGIES USED
16

HTML
HTML stands for Hyper Text Mark-up Language. HTML is not a programming
language, but rather a markup language. HTML is a set of code symbols used to
format text files for electronic display.

Words to know in HTML are:


 Tag  Used to specify ("mark-up") regions of HTML documents for the
web browser to interpret. Tags look like this: <tag>
 Element  A complete tag, having an opening <tag> and a closing
</tag>.
 Attribute  Used to modify the value of the HTML element. Elements will
often have multiple attributes.

A tag is a command the web browser interprets, an element is a complete


tag, and an attribute customizes or modifies HTML elements.

When a tag envelopes a particular part of a text file, the text is affected by a
web browser, the text that is surrounded by the tag appears in a formatted
manner. Unlike C or C++, there is no separate compiler for HTML.

Cascading Style Sheet (CSS)


Cascading Style Sheet is a style sheet language used to describe
the presentation that is, the look and formatting of a document written in
a markup language. Its most common application is to style web pages written
in HTML and XHTML. CSS is designed primarily to enable the separation of
document content (written in HTML or a similar markup language) from
document presentation, including elements such as the layout, colors, and fonts.
This separation can improve content accessibility, provide more flexibility and
control in the specification of presentation characteristics, enable multiple pages
to share formatting, and reduce complexity and repetition in the structural content
CSS can also allow the same markup page to be presented in different styles for
different rendering methods, such as on-screen, in print, by voice.

While the author of a document typically links that document to a CSS style
sheet, readers can use a different style sheet, perhaps one on their own
computer, to override the one the author has specified.

JAVASCRIPT
17

JavaScript is a scripting language created by Netscape and hence best with


Netscape Navigator. Java has so less in common with JavaScript. JavaScript is
object based not object oriented as Java.

Uses of JavaScript:

1. Creating Forms: The most efficient use of JavaScript is to handle the client
side forms which traditionally has been done with CGI.

2. Input Validations: When a user inputs data in a text field of a form, the user
has to submit the data to a server and wait to find out if he or she made any
mistake. With JavaScript you can check the type of data as users keep fill out
each field.

3. Object Manipulation: JavaScript has many built in function and predefined


object. JavaScript lets you to manipulate the document of an HTML page so that
the user can change the background, text or link color.

4. Handling Events: JavaScript is mostly is event driven. An event such as on


load lets you to play an .a sound file when a user loads your HTML document.

SQL
SQL stands for Structured Query Language. SQL lets you access and
manipulate databases. SQL is an ANSI (American National Standards Institute)
standard. SQL is a standard language for accessing databases.

The most common operation in SQL is the query, which is performed with the
declarative SELECT statement. SELECT retrieves data from one or more tables, or
expressions. 

SQL can execute queries against a database. SQL can retrieve data from a
database. SQL can insert records in a database. SQL can update records in a
database. SQL can delete records from a database. SQL can create new
databases. SQL can create new tables in a database. SQL can create stored
procedures in a database. SQL can create views in a database. SQL can set
permissions on tables, procedures, and view

To build a web site that shows some data from a database, you will need the
following: An RDBMS database program (i.e. MS Access, SQL Server, MySQL),
A server-side scripting language, like PHP or ASP, SQL, HTML / CSS.

SERVELETS
18

A servlet is a java class that dynamically extends the function of web server.
Because it is written in java, it has full access to java’s advances features-
database connectivity, network awareness, object orientation and built-in support
for multithreaded processes. These features can be used to deliver full
functional applications to web clients without requiring any special client side
configuration. Because they use the ordinary HTTP as their interface, they run
same in any browser environment.

A servlet runs in a java virtual machine (JVM) managed by a servlet engine. Like
a CGI script, it is invoked to handle a request a from a web client. But unlike CGI,
which requires a new process to be created, a servlet remains loaded in the
virtual machine, available to handle new request. Each new request uses the
same copy of the servlet in memory while running its own thread of execution for
optimal performances.

THE SERVLET LIFE CYCLE

The life cycle of a servlet is controlled by the container in which the servlet has
been deployed. When a request is mapped to a servlet, the container performs
the following steps.

1. If an instances of the servlet does not exist, the web container

a. Loads the servlet class

b. Creates an instances of the servlet class

c. Initializes the servlet by calling the init method. Initialization is covered in


covered in initializing a servlet

2. Invokes the servlet instances method, passing a request and response object.
If the container needs to remove the servlet, it finalizes the servlet by calling the
servlet’s destroy method

There are three types of events in the life of each servlet instances and they
correspond to three methods that are invoked by the servlet engine.

Init()  when a servlet is first loaded ,the servlet engine calls its init() method
exactly once. A servlet is guaranteed to be not handle any request until its()
method has completed successfully.

Service  This is the heart of the servlet, the place where request are actually
handled.
For each request, the servlet engine will call the servlet’s service method,
passing it references to a servlet request object and a servlet response object.
19

The request object, which implements ate servlet request interface, encapsulates
the information about the clients and particulars about the request . Similarly, the
response object which implements the servlet response, contains a reference to
the output stream that will be used to write the results back to the client

Destroy  This is the optional counterpart to init(), called by the servlet engine
when the servlet is about to be unloaded . Ordinarily, servlet classes remain
loaded and active until the servlet engine is shutdown. However, if the servlet
engine detects that a servlet has been recompiled since the last time it serviced a
request, the new servlet class will be loaded, replacing the old one.

JAVA SERVER PAGES (JSP)


Java server pages is a technology based on the java language and enables the
development of dynamic web site. JSP was developed by Sun Microsystems to
allow server side development. JSP files are HTML files with special tags
containing java source code that provide the dynamic content.

The following shows the typical web server, different clients connecting via the
internet to a web server. In this example, the web server is running on UNIX and
is the very popular Apache web server.

First static web pages were displayed . Typically these were people’s first
experience with making web pages so considered of My Home Page sites and
company marketing information. Afterward perl and c were language used on the
web server to provide dynamic content. soon most language including Visual
Basic, Delphi, C++ and java could be used to write applications that provided
dynamic content using data from text files or database requests. These were
known as CGI server side applications. ASP was developed by Microsoft to allow
Html developers to easily provide dynamic content supported as standard by
Microsoft’s free web server. Internet Information server (IIS). JSP is the
equivalent from sun Microsystems, a comparison of ASP and JSP will be
presented in the following section.
20

The following diagram shows a web server that supports JSP files. Notice that
the web server also is connected to database.

JSP source code runs on the web server in the JSP servlet Engine. The JSP
servlet Engine dynamically generates the HTML and sends the HTML output to
the client’s web browser.

SCRIPTING IN JSP

JSP scripting elements allow you to use java programming language statements
in your JSP pages. Scripting elements are typically used to create and access
objects, define methods ,and manage the flow of control. Many tasks that
require the use of scripts can be eliminated by using custom tag libraries, in
particular the JSP Standard Tag Library. Since one of the goals of JSP
technology is to separate static template data from the code needed to
dynamically generate content, very sparing use of JSP scripting is
recommended. Nevertheless, there may be some circumstances that require its
use. There are three ways to create and use objects in scripting elements
:Instance and class variables of the JSP page's servlet class are created in
declarations and accessed in scrip lets and expressions.

 Local variables of the JSP page's servlet class are created and
used in script lets and expressions

 Attributes of scope objects are created and used in scrip lets and
expressions.

WHY USE JSP?


21

JSP is easy to learn and allows developers to quickly produce websites and
applications in and open and standard way. JSP is based on java, an object
oriented language. JSP offers a robust platform for web development.

MAIN REASONS TO USE JSP


 Multiplatform
 Component reuse by using Java Beans and EJB
 Advantages of Java

HTML and graphics displayed on the web browser are classed as the
presentation layer. The Java code(JSP) on the server is classed as the
implementation. By having a separation of presentation and Java developers
concentrate on implementing the application.

JSP COMPARED TO ASP

JSP and ASP are fairly similar in the functionality that they provide. JSP may
have
slightly higher learning curve. Both allow embedded code in an HTML page,
session
variables and database access and manipulation. Where as ASP is mostly found
on
Microsoft platforms, i.e.NT. JSP can operate on any platform that conforms to
the J2EE specification. JSP allow component reuse by using JavaBeans and
EJBs.
ASP provides the use of COM/ActiveX controls.

JSP COMPARED TO SERVLETS


A servlet is a Java class that provide special server side service. It is hard work
to write HTML code in servlets. In servlet’s you need to have lots of println
statements to generate HTML.

STEPS REQUIRED FOR A JSP REQUEST

1. The user goes to a website made using JSP. The user goes to JSP page.
The
browser makes the request via the internet.
2. The JSP request gets sent to the web server
3. The web server recognizes that the file required is special, therefore passes
the
JSP file to the JSP servlet Engine.
4. If the JSP file has been called the first time, the JSP file is parsed, otherwise
go
22

to step 7.
5. The next step is to generate a special servlet from the JSP file. ALL the HTML
required is converted to println statements.
6. The servlet source code is compiled into a class.
7. The servlet is instantiated, calling the init and service methods.
8. HTML from the servlet output is sent via the Internet.
9. HTML results are displayed on the user’s web browser.
Syntax Summary

JSP SYNTAX INTERPRETATION NOTES


Element
JSP <%=expression Expression is XML equivalent is
Expression %> evaluated and placed <jsp:expression>
in output expression
</jsp:expression>
Predefined
variables are
request,
response,out,sessio
n,application,config
and pageContext
JSP scriptlet <%code%> Code is inserted in XML equivalent is
service method <jsp:declaration>
code
</jsp:declaration >
JSP <%!code%> Code is inserted in XML equivalent is
Declaration body of servlet class <jsp:declaration>
outside of service code
method> </jsp:declaration >
JSP Page <%@page Directions to the XML equivalent is
Directive att=”val”%> servlet about general <jsp:directive.page att="v
setup attributes
with default values in bol
 import=
"package.class"
 contentType
="MIME-Type"
 isThreadSafe
="true/false"
 session=
23

"true/false"
 buffer=
"sizekb/none"
autoflush="true
/false"
 extends=
"package.class"
 info=
"message"
 errorPage=
"url'
 *isErrorPage
="true/false"
 language=
"java"
JSP include < A file on the local XML equivalent is
Directive %@includefile="ur system to be included <jsp:directive.includ
l"%> when the JSP page is e file="url"\>.The
translated into a URL must be
servlet relative one.Use the
jsp:include action to
include a file at
request time instead
of translation time.
24

The <jsp:include Include a file at the If you want to


jsp:include page="relative time the page is include the file at
Action URL" requested the time the
flush="true"/> page is
translated,
use the page
directive
with
the include
attribute instead.
WARNING:
On some servers, the
included file
must be an
HTML file or
JSP file as
determined by the server
based on the
file extension)
The JSP: <jsp:useBean Find or build a Possible attributes are
useBean att=value*/>or JavaBean  id="name"
Action <jsp:useBean  scope="page
att=val*>---- /request/
</jsp:useBean> session/
application"
 class=
"package.class"
 type=
"package.class"
 beanName=
"package.class"

The jsp: jsp:setProperty Set bean properties, Legal attributes


setProperty att=val*/> either explicitly or are
Action designating that  name=
values comes from a "beanName"
request parameter.  property=
"propertyName"
 param=
25

"parameterName"
 value="val"

The jsp: <jsp:getPropertyn Retrieve and output


getProperty ame="propertyNa bean properties
Action me"value="val"/>

The <jsp:forward Forward request to


jsp:forward page="relative another page
Action URL"/>
The <jsp:plugin Generates OBJECTS
jsp:plugin att="val"*>--- or EMBED tags, as
Action </jsp:plugin> appropriate to the
browser type, asking
that an applet be run
using the Java Plugin

JSP PAGE DIRECTIVE

ATTRIBUTE DESCRIPTION
import="package.class" This lets you specify what packages should
be imported. The import attribute is the only
one that is allowed to appear multiple times.
contentType="MIME- This specifies the MIME type of the
TYPE or output.The default is text/html.The directive
contentTYPE="MIME- has the same effect as the Scriplet.
TYPE;charSet=Character-
Set"
isThreadSafe="true/false" A value of true indicates normal servlet
processing,where multiple requests can be
processed simultaneously with a single
servlet instance, under the assumption that
the author synchronized access to instance
variables.A value of false indicates that the
servlet should implement"Single Thread
Model",with requtss being given seperate
26

servlet instances
session="true/false" A value of true indicates that the predefined
variable session should be bound to the
existing session if one exists,otherwise a
new session should be created and bound
to it. A value of false indicates that no
sessions willbe used and attempts to access
the variables session will result in errors at
time the JSP page is translated into a
servlet.

buffer="sizekb/none" This specifies the buffer size for the JSP


writer "out".The default is server specific,but
must be atleast 8kb.
autoflush="true/false" A value of true, the default,indicates that the
buffer should be flushed when it is full.A
value of false,rarely used, indicates that an
exception should be thrown when the buffer
overflows.A value of false is illegal when
also using buffer="none".
extends="package.class" This indicates the super class of servlet that
will be generated.Use this with extreme
caution,since the server may be using a
custom super class already.
info="message" This defines a string that can be retrieved
via the "getServletInfo"method.
errorPage="url" This specifies a JSP page that should
process any throwables thrown but not
caught in the current page.
isErrorPage="true/false" This indicates whether or not the durrent
page can at the error page for another JSP
page.
language="java" At some point ,this is intended to specify the
underlying language being use.
27

THE jsp:useBean ACTION

ATTRIBUTE DESCRIPTION
id Gives a name to the variable that will reference
the bean. A previous bean object is used intead
of insantiating a new one if one can be found with
the same id and scope.
class Designates the full package name of the bean.
scope Indicates the context in which the bean should be
made available.Therefore possible
values:page,request,session,and application.The
default, page,indicates that the bean is only
available on the current page. A value of request
indicates that the the bean is only available for the
current client request. A value of session indicates
that the object is available to all pages during the
life of the current HTTP session. Finally, a value of
application indicates that it is available to all pages
28

that share the same servlet context. The reason


that the scope matters is that the gsp: use Bean
entry will only result in a new object being
instantiated if there is no previous object with the
same id and scope. Otherwise,the previously
existing object is used any jsp:setparameter
elements or other entries between the
jsp:useBean start and end tags will be ignored.

type Specifies the type of the variable that will refer to


the object. This must match the class name or be
a super class or an interface that the class
implements. Remember that the name of the
variable designated via the id attribute.
beanName Gives the name of the bean, as you would supply
it to the instantiate method of beans. It is
permissible to supply a type and a bean Name
and omite the class attribute.

THE jsp:setProperty ACTION

ATTRIBUTE DESCRIPTION
name This required attribute designates the bean
whose property will be set . The jsp:useBean
element must appear before the jsp:setProperty
element .
property This required attribute indicates the property you
want to set . However, there is one special
case:a value of "*" means that all request
parameters whose names match bean property
names will be passed to the appropriate setter
methods .
value This required attribute specifies the value for the
property . String values are automatically
converted to numbers,
Boolean,Boolean,byte,Byte,char and Character
via the standard "valueOf" method in the target or
29

wrapper class . For e.g.,a value of "true" for


aBoolean or Boolean property will be converted
via Boolean .valueOf and a value of 42 for an int
or integer property will be converted via integer.
valueOf. You can not use both value and
param ,but it is permissible to use neither .
param This optional attribute designates the
request parameter from which the property should be derived.
If the current request has no such
parameter,nothing is done:the system
doesnot pass null to the setter method of
the property.Thus,you can let the bean itself supplies default
values ,overriding them only when
the request parameters say to do so.
For e.g.,.the following snippet says"Set the numberOfItems
property to whatever the
value of the numItems request parameter
is,if there is such a request parameter.
Otherwise donot do anything".
<jsp:setProperty name="orderBean" property="numberOfItems"
param = "numItems "/> If you omit both
value and param,it is the same as if you
supplied a param name that matches the
propety name. You can take this idea of
automaticaly using the request property
whose name matches the property one
step further by supplying a property name
of "*" and omitting both value and param.
In this case ,the server iterates through
available properties and request
parameters,matching up ones with
identical names.
30

COMMENTS AND CHARACTER QUOTING


CONVENTIONS

Syntax Description
<%--comment--%> A JSP comment. Ignored by JSP-
to-scriplet translator. Any
embedded JSP scripting
elements ,directives or actions
are ignored.
<!—comment--> An HTML comments. Passed
through to resultant HTML. Any
embedded JSP scripting
elements, directives or actions
are executed normally.
<\% Used in template text (static
HTML) where you really want "<
%".
%\> Used in scripting elements where
31

you really want "%>".


\’ A single quote in an attribute that
uses single quotes. Remember,
however,that you can use either
single or double quotes and other
type of quote will then be a
regular character.
\” A double quote in an attribute that
uses double quotes. Remember,
however,that you can use either
single or double quotes and other
type of quote will then be a
regular character.
%\> %> in an attribute.
<\% <% in an attribute.

AJAX
Ajax stands for Asynchronous JavaScript and XML.  is a group of
interrelated web development techniques used on the client-side to create
interactive web applications. With Ajax, web applications can retrieve data from
the server asynchronously in the background without interfering with the display
and behavior of the existing page. The use of Ajax techniques has led to an
increase in interactive or dynamic interfaces on web pages. Data are usually
retrieved using the XMLHttpRequest object. Despite the name, the use of XML is
not actually required, nor do the requests need to be asynchronous.

Like DHTML, Ajax is not a technology in itself, but a group of technologies. Ajax


uses a combination of HTML and CSS to mark up and style information.
The DOM is accessed with JavaScript to dynamically display, and to allow the
user to interact with, the information presented. JavaScript and the
XMLHttpRequest object provide a method for exchanging data asynchronously
between browser and server to avoid full page reloads.

APACHE TOMCAT 6.04


32

Apache Tomcat (or Jakarta Tomcat or simply Tomcat) is an open source servlet


container developed by the Apache Software Foundation.  Tomcat implements
the Java Servlet and the Java Server Pages (JSP) specifications from Sun
Microsystems, and provides a "pure Java" HTTP web server environment
for Java code to run.
Tomcat should not be confused with the Apache web server, which is
a C implementation of an HTTP web server; these two web servers are not
bundled together. Apache Tomcat includes tools for configuration and
management, but can also be configured by editing XML configuration files.

The goals are of using this is:


 Correctness  Implement the Servlet and JSP specifications as
accurate as possible. Code quality and clarity must match Apache
Standards. We also want a bit more comment and documentation.

 Security  User applications will run in applet like sandboxes, and should
not be able to get out of the box. Servlet API is the only API that can
provide this kind of feature. That means an ISP should be able to let its
users to deploy WARS without having to worry about the system security
or about the possible interference between the users .It also means
companies can use JSPs and applications without having to review them
for security flaws.

 Embedability  The code must be embeddable, acting as a servlet


container for various applications. There are two services Tomcat provides
- servlet services for Web servers and http and servlet services for
standalone applications. Tomcat should be usable as a component
providing Web services for applications, allowing applications to provide
servlet based interfaces. For example it should be possible to create a
Web based configuration for an IDE by just starting Tomcat and using
servlets that access the application’s internal APIs . We also want to
embed Tomcat existing Web servers, providing generic Web programming
using servlets and JSP for Apache,etc.,.

 Performance  As in Apache, the performance is less important than


code quality and must come from using the right algorithms and data
structures ,not by low level hacking. We want to focus on the critical path
and be sure we add the smallest overhead possible, while making sure
that only applications that make use of special features are paying the
price for it.

 Integration with the current Web infrastructure  Web applications will


run on the Web, and we want to make sure we can do work with existing
code and provide a smooth transition. We want to take advantage of the
33

existing optimizations and maturity of web servers like Apache, and make
sure most of the modules and extensions work well with Tomcat.

 Modular Structure  The core should be small and as simple as


possible and most of the functionality must be provided in modules. By
choosing the right modules we can use it in toasters or big servers.
Multiple versions of the same module can be optimized for various VMs or
special environments.

 Reusable components wherever possible  Functionality that is


generic enough should have minimal dependencies on Tomcat core. This
even more visible starting with Tomcat 3.3,where we tried to clearly
identify the “ Modules “and build a collection of general purpose and
independent components that can be used in any other project without
any relation with Tomcat. Having a component that is reviewed , tested
and enhanced in more than one project is worth the price of slightly looser
integration and facade pattern helps integrating independent components
without changing there interfaces.
34

SCOPE OF THE
PROJECT

The JSP based project “Job Management System” is localized, enabling


globalization.

 A logical, 3-tier architecture(Model, View and Controller)

 High level of security using Windows Authentication

 Date grid with custom inline editing, updating and cancellation

 Dynamic report creation enabling faster and efficient retrieval of information


35

 Light weight data classes used for the interface between the business logic
layer and user interface layer.

 User friendly interface

 Efficient updating and retrieval of information

 Cascaded style sheet(CSS) is used to organize styles that will be applied to


other controls.
36

INTRODUCTION TO
SYSTEM DESIGN AND
IMPLEMENTATION

INTRODUCTION TO SYSTEM DESIGN

The most creative and challenging phase of system development life cycle is
system design. The term “design” describes the final system and the process by
which it is developed.
System design is the process by which the detailed design of the system
selected in the study phase is accomplished. The system design goes through
logical and physical state of development. In this phase the user oriented
performance specification is expanded into a design specification. While
37

designing the new system, the developer should have in mind a clear picture of
inputs that may be required in order to achieve the desired outputs.

JOB MANAGEMENT SYSTEM

Job Management System is software which offers a simple, efficient and


consistent user experience in searching and offering jobs. It models the online
job websites. It is of great use and boom to both job seeker and employer.

Through a Job Management System the candidates can post


their profile and can be expected to be noticed by suitable employers. The
employers can search for suitable candidates matching their needs for
qualifications and previous experience.

The project is mainly divided in to three modules

1. Administrator
2. Employees
3. Job Seeker

ADMINISTRATOR:
Administrator has the overall control.
 User Registration Process
 Database Control
 View Details

EMPLOYEE:
The person looking for job. He can perform the following functions

 Post personal details


 Search for companies
 Apply for job

Employers
Job seeker is the person who applies to the company for getting
job. He can perform the following functions.
38

 Search for candidates


 Post their vacancy details

INPUT/OUTPUT DESIGN

Input Design is the process of converting user oriented input into a computer
based format. The goal of designing input date is to make the automation as
easy and free from error as possible. For providing a good input design for the
application easy date input and selection features are adopted.
The presentation layer is responsible for the user interface and communicates
directly with the business logic layer.
A quality output is one that meets the requirement of the end user and presents
the information clearly. In any system results of processing are communicated to
the users and to other systems through outputs. Outputs from computers are
required primarily to communicate the results of processing to the users. They
are also used to provide a permanent copy of these results for future reference.
The main tabs located at the top of each screen are implemented as user control
to take advantage of code reuse. Authorization is enforced by the user control as
it decides whether to display the Administration tad based on the users login.
39

SYSTEM ANALYSIS
40

INTRODUCTION

System Analysis refers to the study of the various operations performed by a


system and their relationship within and outside of the system. System Analysis
is the primary phase of system development. The purpose is to identify the new
system and establish what the new system is to accomplish. Moreover a brief
review of requirement determinations, software enviornments, a report on
feasibility analysis ,system flow diagram is also presented. The proposed system
was subjected thorough analysis and findings are recorded here. System
analysis is an important activity that take place when a new system is being built.
It is the centre of system development it includes gathering necessary data and
developing a plan to the new system. It is not an easy task because many people
need to be satisfied and many conflicts resolved. System Analysis should be
creative and imaginative in producing new solutions to meet the user
requirements.

PROPOSED SYSTEM STUDY

To meet the ever-growing demand of uses and to handle all the processing in
an efficient and faster manner, making the system online is attempted. With the
conversion of the present computerized system to an online system the
organization can achieve better co-ordination among their various reservation
centers and easy access to up-to-date information. There by making profit and
gaining customer satisfaction. Online is economical as it reduces much of the
manual processing, cost and time. The proposed online system is developed in
such a manner that almost all the problems faced by the computerized system
can be easily tackled using it. Most of the user requirements are considered
while developing the proposed system. The provision of timely, accurate and
comprehensive information improves the decisions-making. One important
aspect of the proposed system is that it can easily incorporate changes. The
proposed system is developed using JSP; hence it is user-friendly package, in
Client/Server model and is easily upgradeable.

ADVANTAGES OF THE PROPOSED SYSTEM


The JSP based “Job Management System” is a Web Application that uses a
logical,3-tier architecture. Data access, business logic and user interface logic is
separated into different classes. Data access is provided by Oracle, business
logic and user interface logic are provided by JSP.N-tier architecture has many
advantages including:
 There is a clean separation between the user interface, business logic and
data access layers. this isolation promotes code reuse and makes
maintenance and enhancing the code easier. Development is also easier
because there is a clean decomposition of functionality allowing
41

developers or teams of developers to focus on different parts of the


application during implementation.
 Business rules are centralized into one component that is easy to re-use
and a high level language(like C#) is provided in which to develop the
business rules.
 Data access code is centralized in one place making development
maintenance easier.

Other benefits of proposed system includes

 Up-to-date and user friendly reports can be produced


 High level of date security can be achieved .
 It provides faster and efficient methods of date management and security.
 The developed package is upgradeable.
42

Database Design
43

Once we have our Requirements completed, we can begin modeling our data.


Developing a data model can be a very straightforward task. Somewhat like
programming, database design is “object oriented”. The first step is to define the
entities. Break it down based on how you expect to store information. Anything
that is a noun is likely to be an entity. Everything else will be attributes. Attributes
are the characteristics that define a entity. Attributes will be the field names in
the database. Once you have all the entities defined, we can move onto defining
the relationships between them.

Tables Used
 Address

 Applied jobs

 Employer

 Jobs

 Jobseeker

 Users
44

Schema Description

address Table

Field Name Field Type Description


addressID bigint(20) unique number for each
entry in the table
address varchar(20) Address of the
organization/jobseeker
streetname varchar(20) Street name of the
organization/jobseeker
post varchar(20) post office of the
organization/jobseeker
pincode varchar(20) pin code of the
organization/jobseeker
district varchar(20) district of the
organization/jobseeker
user_id varchar(20) corresponding user id of
the address

appliedjobs Table

Field Name Field Type Description


job_id bigint(20) unique number for each
entry in the table
user_id varchar(20) corresponding user id of
the address
date_applied date date the job was applied

employer Table

Field Name Field Type Description


employer _id bigint(20) unique number for each
entry in the table
company_name varchar(50) company mane
45

company_profile text description about the


company
email varchar(50) email of the company
location varchar(50) location of the company
user_id varchar(50) corresponding user id of
the address

jobs Table

Field Name Field Type Description


job_id bigint(20) unique number for each
entry in the table
job_description varchar(225) description about the job
experience varchar(20) experience required for
the job
location varchar(50) location of the company
date_posted date date the job was posted
status tinyint(4) status of the job
user_id varchar(50) corresponding user id of
the address

jobseeker Table

Field Name Field Type Description


jobseeker_id bigint(20) unique number for each
entry in the table
first_name varchar(30) first name of the
jobseeker
last_name varchar(30) last name of the
jobseeker
email varchar(50) email of the jobseeker
dob varchar(15) date of birth of the
jobseeker
bloodgroup varchar(10) blood group of the
jobseeker
user_id varchar(30) corresponding user id of
the address
46

users table

Field Name Field Type Description


user_id varchar(30) corresponding user id of the
address
password varchar(30) password of a user
role tinyint(4) role of the user
(admin/jobseeker/employer)
status tinyint(4 status(blocked/unblocked/
unapproved/approved)
reg_date date registered date
47

USECASE DIAGRAMS
AND CLASS DIAGRAM
48
49
50
51
52

INTRODUCTION TO
SYSTEM TESTING AND
IMPLEMENTATION
53

INTRODUCTION TO SYSTEM TESTING


System Testing is vital to the success of a system. System Testing can
be looked upon as one among the many processes that an organization
performs. System Testing is actually a series of different tests whose primary
purpose is to fully exercise the computer based system. Although each test has a
different purpose, all these work to verify that all system elements have been
properly integrated and perform allocated functions.
During the testing of “JMS” it was made sure that the software does
exactly what it is suppose to do. Testing is the final verification and validation
activity within the organization itself. In the testing stage of “JMS” the following
goals were aimed :
 To affirm the equality of the application
 To detect and eliminate any residual errors from previous stages
 To validate the software as a solution to the original problem
 To demonstrate the presence of all specified functionality in the
developed application
 Estimate the operational reliability of the syste.
During testing the major activities are concerned on the examination and
modification of the source code.
System Testing is necessary because inadequate testing or non-testing leads to
errors that may not appear until months later. Effective testing early in the
process translated directly into long term cost saving from a reduced number of
errors. Another reason for system testing is its utility as a user oriented vehicle
before implementation.

METHOD OF TESTING
The testing methods used for “JMS” include Unit Testing.
Integration Testing, User Acceptance Testing, Output Testing, and Validation
Testing.

UNIT TESTING
Unit testing or function testing is the basic level of testing where functions
making up a module are tested to ensure that they operate correctly. Unit testing
exercises specific paths in a module’s control structure to ensure complete
coverage and maximum error detection. In JMS application unit testing was
used to test each function. And the output generated by the individual function
agrees with the output generated by the computerized system and manually.
Thus the application proved to satisfy unit testing.
54

INTEGRATION TESTING
Integration Testing addresses the issues associated with the dual
problems for verification and program construction. After the software has been
integrated as set of high order tests are conducted. The main objective in this
testing process is to take unit tested modules and build a program structure that
has been dictated by design. The integration testing has been done in such a
way that all the modules are integrated under a few links like Job search,
Resume Uploading etc.

TOP DOWN INTEGRATION


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. The module subordinates to
the main program module are incorporated into the structure in either a depth
first or breadth first manner.

BOTTOM UP INTEGRATION
This method begins the construction and testing with the modules at the
lowest level in the program structure. Since the modules are integrated from the
bottom up.
It processing required for modules subordinate to a given level is always
available and the need for the stubs is eliminated.

USER ACCEPTANCE TESTING


User Acceptance of a system is the key factor for the success of any
system. In order to achieve the user acceptance in JMS the application is made
according to the users need of the new system. The system under consideration
is tested for user acceptance by constantly getting in touch with prospective
system users at the time of developing or making changes wherever required. It
is done in regard to following points :

INPUT SCREEN DESIGN


Input Screen design was done in a user friendly manner. Only the
necessary options are given on the input screen.

OUTPUT SCREEN DESIGN


The output screens are those, which make the user sensible about the Job
details. Vacancies, Company information. The output screen design too is made
taking into consideration the ease of user.

OUTPUT TESTING
After performing the validation testing the next step is output testing of the
proposed system, as no system could be useful unless it produces the required
output in the specified format. Asking the users about the format required by
them tests the outputs generated or displayed by the system under
consideration. Hence the output format is considered into ways :
55

a. On screen
b. Printed format

TEXT FIELD
The text field can contain only a specified number of character (lesser than
or equal to its size). The text fields are alphanumeric in some cases such as Job
details. Vacancies, city, state, country etc. An incorrect entry always pops up a
dialogue box with the relevant message.

NUMERIC FIELD
The numeric fields can contain only numbers from 0 to 9 and a decimal
point (.). The entry of any character or other symbols leads to the display of
message box with suitable message.

VALIDATION CONTROLS
The following validations controls are also used in the JMS application.

REQUIRED FIELD VALIDATOR CONTROL


The Required Field Validation control validates that the value of another
control something other than its initial value.

RANGE VALIDATOR CONTROL

The Range Validator Control validates that the values of another control
fall within an allowable range, where the minimum and maximum are provided
either directly or by reference to another control.

REGULAR EXPRESSION VALIDATOR CONTROL

The Regular Expression Validator Control validates that the values of


another control match a specified expression.

COMPARE VALIDATOR CONTROL


Compare Validator Control compares one control to another by using a
specified comparison operator.

CUSTOM VALIDATOR CONTROL


The Custom Validator Control allows developers to provide their own
method to validate another controls field.

VALIDATION SUMMARY CONTROL


Validation Summary Control displays a summary of all the validation
errors that occurred during the rendering of a form.
56

PREPARATION OF TEST DATA


The above mentioned testing is done by taking various kinds of test data.
Preparation of test data plays a vital role in system testing. After preparing the
test data the system under study is tested using that test data, errors are again
uncovered and corrected by implementing the above steps and corrections are
noted for future use.

USING LIVE TEST DATA


Live test data are those that are actually extracted from the organization. It
is realistic data that will show how the system will perform for typical processing
requirements, assuming that the live data entered are in fact typical such data
generally will not test all combinations or formats that can enter the system.

USING ARTIFICIAL TEST DATA


Artificial test data are created solely for test purposes, since they can be
generated to test all combinations of formats and values. The most effective test
programs use artificial test data generated by person other than those who wrote
the programs. Often an independent team of testers formulates a testing plan,
using the systems specifications.

QUALITY ASSURANCE
Quality Assurance consists of the auditing and reporting functions of the
newly developed system. The goal of Quality Assurance is to provide the
management with the data necessary to be informed about product quality,
thereby gaining insight and confide that product quality is meeting its goals. This
is an Umbrella activity that is applied through out the engineering process.
Software Quality Assurance encompasses :

 Analysis, design, coding and testing methods and tools.


 Formal technical reviews that are applied during each software
engineering
 Multi tiered testing strategy
 Control of software documentation and the change made to it.
 A procedure to ensure compliance with software development standards
 Measurement and reporting mechanisms

QUALITY FACTORS
The factors that affect the quality can be categorized into two broad groups :
a. Factors that can be directly measured
b. Factors that can be indirectly measured

There are only a few factors that can be measured directly but a lot of factors
that can be measured indirectly. The Quality factors were verified at the time of
testing itself.
57

GENERIC RISKS
A risk is an unwanted event that has negative consequences. Project
managers will engage in risk management to understand and control the risks on
their projects. Risks can be distinguished from other project events by looking for
3 things.

A loss associated with event


The likelihood that the event will occur
The degree to which we can change the outcome.

KEEPING AND REPORTING


The quality begins with asset of technical methods and tools that help the
analyst to achieve high quality specification and the designer to develop high
quality design. The next activity involves assessment of the quality for the design
that is created which is the formal technical review. Software testing combines a
multi step strategy with series of test case design methods that help ensure
effective error detection. It is assumed that testing will uncover most of the errors.
Every change to software has the potential for introducing errors or creating side
effects that propagate errors. The change control process contributes directly to
software quality by formalizing request for change, evaluating the nature of
change and controlling the impact of change.

An important objective of quality assurance is to track the software quality


and assess the impact of methodological and procedural changes on improved
software quality. Record keeping and recording for software quality assurance
provide procedures for the evaluation and separation of software quality
assurance information.

SYSTEM IMPLEMENTATION

Implementation is the stage of the project where the theoretical design is


turned into a working system. At this stage the main work load, the greatest
upheaval and the major impact on the existing system shifts to the user
department. If the implementation is not carefully planned and controlled it can
create chaos and confusion.

Implementation includes all those activities that take place to convert from
the existing system to the new system. The new system may be a totally new,
replacing an existing manual or automated system or it may be a modification to
an existing system. Proper implementation is essential to provide a reliable
system to meet organization requirements. The process of putting the developed
system in actual use is called system implementation. This includes all those
activities that take place to convert from the old system to the new system. The
system can be implemented only after through testing is done and if it is found to
58

be working according to the specifications. The system personnel check the


feasibility of the system. The more complex the system being implemented, the
more involved will be the system analysis and design effort required to implement
the three main aspects :

 Education and training


 System testing
 Changeover

The implementation state involves the following tasks

 Careful planning
 Investigation of system and constraints
 Design of methods to achieve the changeover
 Training of the staff in the changeover phase
 Evaluation of the changeover method

The method of implementation and the time scale to be adopted are found
out initially. Next the system is tested properly and the users are trained in the
new procedures.

IMPLEMENTATION PROCEDURES
Implementation of software refers to the final installation of the package in
its real environment, to the satisfaction of the intended uses and the operation of
the system. In many organizations someone who will not be operating it, will
commission the software development project. In the initial stage people doubt
about the software but we have to ensure that the resistance does not build up,
as one has to make sure that

 The active user must be aware of the benefits of using the new system
 Their confidence in the software is built up
 Proper guidance is imparted to the user so that he is comfortable in using
the application.

Before going ahead and viewing the system, the user must know that for
viewing the result, the server program should be running in the server. If the
server object is not up running on the server, the actual process will not take
place.

USER TRAINING
User training is designed to prepare the user for testing and converting the
system To achieve the objective and benefits expected from computer based
system, it is essential for the people who will be involved to be confident of their
role in the new system. As system becomes more complex, the need for training
is more important. By user training the user comes to know how to enter data,
59

respond to error messages, interrogate the database and call up routine that will
produce reports and perform other necessary functions.

TRAINING ON THE APPLICATION SOFTWARE


After providing the necessary basic training on computer awareness the
user will have to be trained on the new application software. This will give the
underlying philosophy of the use of the new system such as the screen flow,
screen design type of help on the screen, type of errors while entering the data,
the corresponding validation check at each entry and the ways to correct the data
entered. It should then cover information needed by the specific user / group to
use the system or part of the system while imparting the training of the program
on the application. This training may be different across different user groups and
across different levels of hierarchy.

OPERATIONAL DOCUMENT
Once the implementation plans is decided, it is essential that the user of
the system is made familiar and comfortable with the environment. Education
involves right atmosphere and motivating the user. A documentation providing
the whole operations of the system is being developed in such a way that the
user can work with it in well consistent way. The system is developed user
friendly so that the user can work the system from the tips given in the
application itself. Useful tip and guidance is given inside the application itself to
help the user. Users have to be made aware that what can be achieved with the
new system and how it increases the performance of the system. The user of the
system should be given a general idea of the system before he uses the system.

SYSTEM MAINTENANCE
Maintenance is the enigma of system development. The maintenance
phase of the software cycle is the time in which a software product performs
useful work. After a system is successfully implemented, it should be maintained
in a proper manner. System maintenance is an important aspect in the software
development life cycle. The need for system maintenance is for it to make
adaptable to the changes in the system environment. Software maintenance is of
course, far more than Finding Mistakes. Maintenance may be defined by
describing four activities that are undertaken after a program is released for use.

CORRECTIVE MEASURES
This maintenance activity occurs because it is unreasonable to assume
that software testing will uncover all latent errors in a large program, errors will
occur and it will be reported to the developer (s). The process that include the
diagnosis and correction of one or more errors is called corrective maintenance.

ADAPTIVE MAINTENANCE
60

The second activity that contributes to a definition of maintenance occurs


because of the rapid change that is encountered in every aspect of computing.
Therefore, adaptive maintenance – an activity that modifies software to properly
interfere with a changing environment is both necessary and common place.

PERFECTIVE MAINTENANCE
The third activity that may be applied to a definition of maintenance occurs
when a software package is successful. As a software is used, recommendations
for new capabilities, modifications to existing functions and general
enhancements are received from user. To satisfy requests in this category.
Perfective maintenance is performed. This activity accounts for the majority of all
effort expended on software maintenance.

PREVENTIVE MAINTENANCE
The fourth maintenance, activity occurs when software is changed to
improve future maintainability or reliability, or to provide a better basis for future
enhancements. Often called preventive maintenance, this activity is
characterized by reverse engineering and re-engineering techniques.
61

SYSTEM
REQUIREMENTS
62

Hardware Requirements

Processor : Pentium III / AMD Athlone XP

RAM : 128 MB

HDD : 20 GB

FDD : 1.44 MB / 3 ½ inch

Monitor : 15 inch

Mouse : 3 button scroll

CD Drive : 52 X

Keyboard : 108 keys

Software Requirements

Operating System : Windows 2000 / XP/NT / LINUX

Languages : Java 2 (JDBC, JSP), HTML

Front End : JSP

Platform : J2EE

Web Servers : Apache Tomcat

Backend : MYSQL

Browser Program : Internet Explorer / Mozilla Firefox


63

Conclusion
64

Now a days manual process of searching a job of the appropriate choice and
searching the appropriate candidate for a specific job has become a huge task.
So realizing the need of easy management of this process this site has been
developed. Its very easy to update and maintain information through this site.

The main features of this project includes

 Flexibility

 Easy to manipulate information

 Easy access searching

 Storage

 Reduce manual work

 View reports in an efficient manner

 Most economical

The project could very well be enhanced further as per the requirements.
65

REFERENCES
66

1. J2EE and Beyond: Design, Develop, and Deploy World Class Java
Software.
Art Taylor

2. Expert One-on-One J2EE Design and Development


Rod Johnson 

3. Pure JSP: Java Server Pages


James Goodwill 

4. Core Servlet and Java Server Pages (JSP)


Marty Hall

5. Database Programming with JDBC & Java


George Reese

6. The Complete Reference SQl


Publisher: McGraw-Hill Osborne Media
67

You might also like