INTRODUCTION

-1-

INTRODUCTION 1.1. INTRODUCTION TO PROJECT

Job portal is an application developed in order to reduce the gap between Industry and Industry needed resources. If the user selects any date in the job calendar then it displays list of jobs available on that particular date in the same page. This helps for the jobseekers to upload resumes, searches for the jobs based on keywords and finally applies for the suitable jobs. egistered employers can give adds for the jobs and they can take necessary resumes from the portal by performing search.

1.2.

ORGANIZATION PROFILE

SOFTWARE SOLUTIONS
I!"T I# $oftware $olutions is an IT solution provider for a dynamic environment where business and technology strategies converge. Their approach focuses on new ways of business combining IT innovation and adoption while also leveraging an organi%ation&s current IT assets. Their work with large global corporations and new products or services and to implement prudent business and technology strategies in today&s environment.

IMATRIX RANGE OF EXPERTISE INCLUDES:

$oftware 'evelopment $ervices (ngineering $ervices $ystems Integration )ustomer elationship !anagement *roduct 'evelopment (lectronic )ommerce )onsulting

-+-

IT ,utsourcing

-e apply technology with innovation and responsibility to achieve two broad objectives. (ffectively address the business issues our customers face today. /enerate new opportunities that will help them stay ahead in the future.

THIS APPROACH RESTS ON:

" strategy where we architect, integrate and manage technology services and solutions we call it "I! for success. " robust offshore development methodology and reduced demand on customer resources. " focus on the use of reusable frameworks to provide cost and times benefits.

They combine the best people, processes and technology to achieve e0cellent results consistency. -e offer customers the advantages of.

SPEED:
They understand the importance of timing, of getting there before the competition. " rich portfolio of reusable, modular frameworks helps jump-start projects. Tried and tested methodology ensures that we follow a predictable, low - risk path to achieve results. ,ur track record is testimony to comple0 projects delivered within and evens before schedule.

EXPERTISE:
,ur teams combine cutting edge technology skills with rich domain e0pertise. -hat&s e1ually important - they share a strong customer orientation that means they actually start by listening to the customer. They&re focused on coming up with solutions that serve customer re1uirements today and anticipate future needs.

A FULL SERVICE PORTFOLIO:

-2-

They offer customers the advantage of being able to "rchitect, integrate and manage technology services. This means that they can rely on one, fully accountable source instead of trying to integrate disparate multi vendor solutions.

SERVICES:
I!"T I# is providing it&s services to companies which are in the field of production, 1uality control etc -ith their rich e0pertise and e0perience and information technology they are in best position to provide software solutions to distinct business re1uirements.

1.3.

PURPOSE OF THE PROJECT

This application can be mainly intended to create the rich user interface between jobseekers and industries. In this application helps for job seekers to upload resumes, searching for jobs on a particular date. The registered employers can add job fair details can take necessary resumes from the portal by performing search. If the user selects any date in the job calendar then it displays list of jobs available on that particular date.

-3-

PROBLEMS AND SOLUTIONS OF THE PROJECT

-4-

PROBLEMS AND SOLUTIONS OF THE PROJECT 2.1 .PROBLEMS IN EXISTING SYSTEM

The current job sites are very slow and not well organi%ed. There is no well built-in system to check the history or older job postings. These postings might have the last date for many days, but there is no provision to check the job postings day wise.

2.2. SOLUTION OF THESE PROBLEMS

The current project has the following features. 1. $hows the calendar and job postings list on each day. +. The basic features enhanced in "ja0. 2. This system provides useful feature for jobseekers, called job calendar. If the user selects any date in the job calendar then it displays list of jobs available on that particular date in the same page. 3. provide a fle0ible and faster search feature for both employers and Jobseekers

-5-

Fe !"#"$"%& Re'()%

-6-

3. Fe !"#"$"%& Re'()%
*reliminary investigation e0amine project feasibility, the likelihood the system will be useful to the organi%ation. The main objective of the feasibility study is to test the Technical, ,perational and (conomical feasibility for adding new modules and debugging old running system. "ll system is feasible if they are unlimited resources and infinite time. There are aspects in the feasibility study portion of the preliminary investigation. Technical 7easibility ,peration 7easibility (conomical 7easibility

3.1. Te*+,"* $ Fe !"#"$"%&

The technical issue usually raised during the feasibility stage of the investigation includes the following. 'oes the necessary technology e0ist to do what is suggested8 'o the proposed e1uipments have the technical capacity to hold the data re1uired to use the new system8 -ill the proposed system provide ade1uate response to in1uiries, regardless of the number or location of users8 )an the system be upgraded if developed8 -9-

"re there technical guarantees of accuracy, reliability, ease of access and data security8 (arlier no system e0isted to cater to the needs of :$ecure Infrastructure

Implementation $ystem&. The current system developed is technically feasible. It is a web based user interface for audit workflow at ;I)-)$'. Thus it provides an easy access to the users. The database&s purpose is to create, establish and maintain a workflow among various entities in order to facilitate all concerned users in their various capacities or roles. *ermission to the users would be granted based on the roles specified. Therefore, it provides the technical guarantee of accuracy, reliability and security. The software and hard re1uirements for the development of this project are not many and are already available inhouse at ;I) or are available as free as open source. The work for the project is done with the current e1uipment and e0isting software technology. ;ecessary bandwidth e0ists for providing a fast feedback to the users irrespective of the number of users using the system.

3.2. O'e) %"(, $ Fe !"#"$"%&

*roposed projects are beneficial only if they can be turned out into information system. That will meet the organi%ation&s operating re1uirements. ,perational feasibility aspects of the project are to be taken as an important part of the project implementation. $ome of the important issues raised are to test the operational feasibility of a project includes the following. Is there sufficient support for the management from the users8 -ill the system be used and work properly if it is being developed and implemented8 -ill there be any resistance from the user that will undermine the possible application benefits8 This system is targeted to be in accordance with the above-mentioned issues. <eforehand, the management issues and user re1uirements have been taken into consideration. $o there is no 1uestion of resistance from the users that can undermine the possible application benefits. The well-planned design would ensure the optimal utili%ation of the computer resources and would help in the improvement of performance status.

-=-

3.3. E*(,(-"* Fe !"#"$"%&

" system can be developed technically and that will be used if installed must still be a good investment for the organi%ation. In the economical feasibility, the development cost in creating the system is evaluated against the ultimate benefit derived from the new systems. 7inancial benefits must e1ual or e0ceed the costs.

SOFTWARE RE.UIREMENT SPECIFICATION

- 1> -

/. SOFTWARE RE.UIREMENT SPECIFICATION

P0)'(!e:
Job portal is a web based application. This application helps for the jobseekers to upload resumes, searches for the jobs based on keywords and finally applies for the suitable jobs. egistered employers can give adds for the jobs and they can take necessary resumes from the portal by performing search. "dministrator manages the site and he can manipulate all the information in the system. ?e can add job fairs into the system. This system provides useful feature for jobseekers, called job calendar in the same page. This feature completely developed by implementing "ja0 features.

MODULES:
1.

ADMINSTRATOR: The admin acts as a liaison between (mployer and

Jobseeker. ?e collects re1uired information about jobs from the (mployer and provides the same to the Jobseeker and in turn he also collects the information from jobseekers about their e0perience details and contact details and gives to employer. ?e is a single point control. !anages the entire site, *ost Job 7air.

- 11 -

P)(1"!"(,",2. 1. "dmin @ogin.

Aser Id *assword

2. Job fair.
Interview date @ocation 7unctional area

3. egister the employee and job seekers. Job details.

Job id Job code Job description *osted date Interview date 7unctional area Bey skills (0perience )ontact number (mail id @ocation

- 1+ -

)ompany details.
)ompany id )ompany name )ompany website )ompany information )ompany email id )ompany contact number

F0,*%"(, $"%"e!:
"ssociation of (mployer and )ompany. "ssociation of jobseekers and company. $earching resumes by employer uploaded by jobseekers. $ending emails by employer to job seekers.

.0e)"e!:
?ow many resumes are uploaded based on functional area8 ?ow many jobs are available on a particular date8

A$e)%!:
"ll 7ields are !andatory. Asername already e0ists *assword should contain min 1> characters (mail id should be in regular e0pression. Jobseeker registered successfully. (mployer registered successfully.

- 12 -

2. JOBSEE3ERS:
The job seeker has to register in order to login for the first time. Then he can search the jobs ,apply, save the jobs and finally can upload the resumes to a particular job.

P)(1"!"(,",2: $eeker details.

$eeker id *assword 7irst name @ast name (mail id $ecurity 1uestion $ecurity answer )ontact number

$eeker job details.

$eeker id Job id $tatus

*ost

esume:

7irst name @ast name (mail id 7unctional area (0perience

- 13 -

 "nnual salary Bey skills esume path esume headline

<asic 1ualification

F0,*%"(, $"%"e!:
"ssociation of admin and job seekers. "ssociation of $eeker details and $eeker job details. $earching for jobs. Apload resumes.

.0e)"e!:

?ow many jobs are there based on functional area8 @ast date for recruitment8 @ocation for job fair8

A$e)%!:
"ll 7ields are !andatory. Asername already e0ists *assword should contain min 1> characters (mail id should be in regular e0pression.

- 14 -

 Jobseeker registered successfully.

3. EMPLOYER:
The job seeker has to register in order to login for the first time. ?e can give adds for the jobs and he can take necessary resumes from the portal by performing search.

P)(1"!"(,",2: (mployer details.

(mployer id *assword 7irst name @ast name (mail id @ocation )ompany id $tatus

F0,*%"(, $"%"e!:
"ssociation of admin and employer. Ciew job seekers resumes. $ending emails by employer to job seekers. .0e)"e!: ?ow many resumes are uploaded based on functional area8 ?ow many job seekers are registered8 -hich jobs are suitable for which resumes. - 15 -

A$e)%!:
"ll 7ields are !andatory. Asername already e0ists *assword should contain min 1> characters (mail id should be in regular e0pression.

Fe %0)e! (4 T+"! P)(5e*%:

1. Se )*+ E,2",e:
It is a tool used to provide the search option to the job seekers like based on the functional area and location. If the job seekers select any location it shows list of all available jobs on that place.

2. J(# C $e,6 ):
If the user selects any date in the job calendar then it displays list of jobs available on that particular date in the same page. This feature completely developed by implementing "ja0 features.

/.2. HARDWARE RE.UIREMENTS:

*3 +.9/< processor and above. am 41+ !< and above.

?'' +> /< ?ard 'isk and above.

/.3. S(4%7 )e )e80")e-e,%!:

o !icrosoft .;et framework 3.>.

- 16 -

o !icrosoft "$*.;et. o "J"# Tool kit. o !icrosoft )D.;et language. o !icrosoft $E@ $erver +>>9 o ?T!@.

SYSTEM DESIGN
- 19 -

- 1= -

9. SYSTEM DESIGN
9.1. M(60$e 6e!"2,:
$oftware design sits at the technical kernel of the software engineering process and is applied regardless of the development paradigm and area of application. 'esign is the first step in the development phase for any engineered product or system. The designer&s goal is to produce a model or representation of an entity that will later be built. <eginning, once system re1uirement have been specified and analy%ed, system design is the first of the three technical activities -design, code and test that is re1uired to build and verify software. The importance can be stated with a single word FEualityG. 'esign is the place where 1uality is fostered in software development. 'esign provides us with representations of software that can assess for 1uality. 'esign is the only way that we can accurately translate a customer&s view into a finished software product or system. $oftware design serves as a foundation for all the software engineering steps that follow. -ithout a strong design we risk building an unstable system H one that will be difficult to test, one whose 1uality cannot be assessed until the last stage. 'uring design, progressive refinement of data structure, program structure, and procedural details are developed reviewed and documented. $ystem design can be viewed from either technical or project management perspective. 7rom the technical point of view, design is comprised of four activities H architectural design, data structure design, interface design and procedural design.

9.2. DATA FLOW DIAGRAMS

" data flow diagram is graphical tool used to describe and analy%e movement of data through a system. These are the central tool and the basis from which the other components are developed. The transformation of data from input to output, through processed, may be described logically and independently of physical components associated with the system. These are known as the logical data flow diagrams. The physical data

- +> -

flow diagrams show the actual implements and movement of data between people, departments and workstations. " full description of a system actually consists of a set of data flow diagrams. Asing two familiar notations Iourdon, /ane and $arson notation develops the data flow diagrams. (ach component in a '7' is labeled with a descriptive name. *rocess is further identified with a number that will be used for identification purpose. The development of '7'&$ is done in several levels. (ach process in lower level diagrams can be broken down into a more detailed '7' in the ne0t level. The lop-level diagram is often called conte0t diagram. It consists a single process bit, which plays vital role in studying the current system. The process in the conte0t level diagram is e0ploded into other process at the first level '7'. The idea behind the e0plosion of a process into more process is that understanding at one level of detail is e0ploded into greater detail at the ne0t level. This is done until further e0plosion is necessary and an ade1uate amount of detail is described for analyst to understand the process. @arry )onstantine first developed the '7' as a way of e0pressing system re1uirements in a graphical from, this lead to the modular design. " '7' is also known as a Fbubble )hartG has the purpose of clarifying system re1uirements and identifying major transformations that will become programs in system design. $o it is the starting point of the design to the lowest level of detail. " '7' consists of a series of bubbles joined by data flows in the system.

DFD SYMBOLS:
In the '7', there are four symbols 1. " s1uare defines a sourceJoriginatorK or destination of system data +. "n arrow identifies data flow. It is the pipeline through which the information flows 2. " circle or a bubble represents a process that transforms incoming data flow into outgoing data flows. 3. "n open rectangle is a data store, data at rest or a temporary repository of data

- +1 -

*rocess that transforms data flow.

$ource or 'estination of data 'ata flow 'ata $tore

CONSTRUCTING A DFD: $everal rules of thumb are used in drawing '7'&$. 1. *rocess should be named and numbered for an easy reference. (ach name should be representative of the process. +. The direction of flow is from top to bottom and from left to right. 'ata traditionally flow from source to the destination although they may flow back to the source. ,ne way to indicate this is to draw long flow line back to a source. "n alternative way is to repeat the source symbol as a destination. $ince it is used more than once in the '7' it is marked with a short diagonal. 2. -hen a process is e0ploded into lower level details, they are numbered. 3. The names of data stores and destinations are written in capital letters. *rocess and dataflow names have the first letter of each work capitali%ed

- ++ -

Le1e$ : D" 2) - 4() J(# P()% $

Job seeker

Job *ortal

(mployer

"dministrator

- +2 -

Le1e$ 1 D" 2) - 4() A6-",:

Seekers

VIEW

Employers

VIEW

Admin

Id&password Invalid Id& password

Valid ID & Password

ADD &VIEW VIEW SIGNOUT

Job Fair

Company Details

Logout D

- +3 -

Le1e$ 1 D" 2) - 4() J(# !ee;e):

$egistration

View Jobs Sear!" Jobs

INPUT

VIEW ViIEW

Job Seekers

Id&password Invalid Id& password

Valid ID & Password

VIEW View & Update SIGNOUT

Job#airs

A!!ount

Logout D

- +4 -

Le1e$ 1 D" 2) - 4() E-'$(&e):

$egistration

A!!ount

Input

Sear!" $esumes
Search

Employer

Id&password Invalid Id& password

Valid ID & Password

VIEW

Post Jobs

Logout D

- +5 -

Le1e$ 2 D" 2) - 4() A6-",:

SAVE TO D

Seekers

SU""ESS O# $AI!U#E

Seeker Details

View Employer Employers

VIEW VIEW & DE!ETE

SAVE TO D

SU""ESS O# $AI!U#E

Delete Employer

Employer Details
SAVE TO D SU""ESS O# $AI!U#E

Admin
ADD

Job Fair

Date

SU""ESS O# $AI!U#E SAVE TO D SAVE TO D

Lo!ation
VIEW SU""ESS O# $AI!U#E SAVE TO D

Job Fair Details

Fun!tional area

SU""ESS O# $AI!U#E

Company Details

SAVE TO D SU""ESS O# $AI!U#E

Company Details

- +6 -

Le1e$ 2 D" 2) - 4() E-'$(&e)

SAVE TO D

$egistration

SU""ESS O# $AI!U#E

Employer Details

Input

SAVE TO D

A!!ount SU""ESS O# $AI!U#E

View Update

A!!ount Details

Employer

search

Search

Fun!tional Area
SU""ESS O# NOT SU""ESS O# NOT

SAVE TO D

$esumes Search
Postin%

Seeker $esume Details

E%perien!e Post
Company 'ame SAVE TO D

SU""ESS O# NOT

SAVE SAVE

P(sting )ob Details

Inter&iew date

SU""ESS O# NOT

- +9 -

Le1e$ 2 D" 2) - 4() J(# !ee;e)

SAVE TO D

$egistration

SU""ESS O# $AI!U#E

Seeker Details
Sa&ed Jobs

SAVE TO D

Input
View

View Jobs

SAVE TO D

Applied Jobs

Job Details

Jobs Job Seeker

Search

Sear!" Jobs
View

Area
SAVE TO D SAVE TO D

E%perien!e
SAVE TO D

Job Fiar
Update sends

SU""ESS O# $AI!U#E

Job Fair Details

A!!ount

SAVE TO D SU""ESS O# $AI!U#E

Seeker Details

Post $esume

SAVE TO D

SU""ESS O# $AI!U#E

$esume Details

- += -

UML D" 2) -!

- 2> -

*SECASE DIA+$A,

Open the site

#e%istration

&o'see(er

!o%in

Search )or *o's

Upload resu+es

Select resu+e

Ad+in E+plo,er
Send +ails

Activate & Deactivate e+plo,er&&o'see(ers

- 21 -

#e%istration Int-./ UserID Varchar-01/ Password Varchar-01/ Una+e #e%istration-/

Interview

&o'calender

Search *o's ', see(er

Date&ti+e Interviewdate Date&ti+e Interview Int-./ &o'id varc har2-31/ Address Varchar2-31/ Address varchar *o'code Interview-/ &o'id-/ &o'code-/ View*o's-/ Appl,*o's-/ Save*o's-/

Search*o'see(ers ',E+plo,er

Int-./ *o'Id Varchar *o'code Upload co+pan,details-/ Post*o's-/ Search *o'see(ers-/

&o'see(ers Int-./ userid Varchar-01/ Passowrd Varchar-31/ Una+e View*o's-/ Appl,-/ Save-/

E+plo,er Int-./ us erid Varchar-01/ Password Varchar-31/ Una+e View reu+es-/ Send +ails-/

CLASS DIA+$A,

- 2+ -

Admin &o' see(er

#e%ister

Employers

#e%ister success)ull, !o%in Search *o's upload resu+es Send +ails to *o'see(ers Send #esu+es

SE-*E'CE DIA+$A,

- 22 -

!o%in

Search resu+es and send to e+plo,ers

Activate&Deactivate E+plo,ers&&o'see(ers

A!ti&ity Diagram For Admin

- 23 -

#e%istration

!o%in

NO 4es

Search resu+es

Send 5ails to *o'see(ers

A!ti&ity Diagram For Employer

- 24 -

AC.IVI./ DIA+$A, F($ J( SEE0E$

#e%istration

!o%in

NO 4es

Search &o's

Upload resu+es

- 25 -

123 D DESI+'
Entities4
06 Ad+in 26 &o' )air 76 &o' details .6 "o+pan, Details 36 See(er Details 86 Post #esu+e 96 E+plo,er Details

Entities wit" Attributes4

52 Admin 4 User Id Password 62Job #air4 Interview date !ocation $unctional area 72Job details4 &o' id &o' code &o' description Posted date Interview date $unctional area :e, s(ills E;perience

- 26 -

 "ontact nu+'er E+ail id !ocation 32Company details4 "o+pan, id "o+pan, na+e "o+pan, we'site "o+pan, in)or+ation "o+pan, e+ail id "o+pan, contact nu+'er "o+pan, Address 12Seeker details4 See(er id Password $irst na+e !ast na+e E+ail id Securit, <uestion Securit, answer "ontact nu+'er &o' id Status 82 Post $esume4 $irst na+e !ast na+e E+ail id

- 29 -

 $unctional area E;perience Annual salar, :e, s(ills #esu+e path #esu+e headline asic <uali)ication

92Employer details4 E+plo,er id Password $irst na+e !ast na+e E+ail id !ocation "o+pan, id Status

"dmin

?as

(mployer

- 2= -

Ad+in ID -P:/ Password

E+plo,erID-P:/ Password $irstNa+e !astNa+e E+ailID !ocation "o+pan,ID-$:/ Status

"dmin

?as

)ompany

- 3> -

"o+pan,ID-P:/ "o+pan,Na+e "o+pan,We'site "o+pan,In)or+ation "o+pan,E+ailID "ontactNo "o+pan,Address Ad+in ID -P:/ Password

$eeker'etails ?as

Job'etails

See(erID See(erNa+e &o'ID-P:/ See(erE+ailID "ontactNo6 - 31 -

*o'ID-$:/ &o'Details :e,S(ills See(erE+ailID "ontactNo6 InterviewDate $unctionalArea

)ompany ?a s

(mployer

E+plo,erID-P:/ Password $irstNa+e !astNa+e E+ailID !ocation "o+pan,ID-$:/ Status - 3+ -

"o+pan,ID-P:/ "o+pan,Na+e "o+pan,We'site "o+pan,In)or+ation "o+pan,E+ailID "ontactNo "o+pan,Address

(mployers

? as

Job$eekers

- 32 -

See(erID See(erNa+e &o'ID-P:/ See(erE+ailID "ontactNo6 E+plo,erID-$:/ E+plo,erID-P:/ Password $irstNa+e !astNa+e E+ailID !ocation "o+pan,ID-$:/ Status

- 33 -

9.9
Admin4

DB T #$e!:

SNO 1

COLUMN NAME "'!I;I' *"$$-, '

DATA TYPE <SIZE= C" )?" J14K C" )?" J14K

CONSTRAINTS <3EY= * I!" I B(I ;,T;A@@

REFERENCES FROM

- 34 -

Job Seekers4
SNO 1 + 2. 3. 4. 5. 6. 9. =. 1> 11 COLUMN NAME $((B( LI' A$( ;"!( *"$$-, ' 7I $T;"!( @"$T;"!( (!"I@I' $()A ITILEA($TI,; $()A ITIL";$-( ),A;T I @,)"TI,; ),;T")TL;A! DATA TYPE <SIZE= I;TJ1>K C" )?" J14K C" )?" J14K C" )?" J14K C" )?" J14K C" )?" J14K C" )?" J14K C" )?" J14K C" )?" J14K C" )?" J14K C" )?" J14K CONSTRAINTS <3EY= * I!" I B(I ;,T;A@@ ;,T;A@@ ;,T;A@@ ;A@@ ;,T;A@@ ;,T;A@@ ;,T;A@@ ;,T;A@@ ;,T;A@@ ;,T;A@@ REFERENCES FROM

- 35 -

E-'$(&e) De% "$!:

SNO 1

COLUMN NAME (!*@,I( LI' A$( ;"!(

DATA TYPE <SIZE= I;TJ1>K C" )?" J14K C" )?" J14K C" )?" J14K C" )?" J14K C" )?" J14K C" )?" J14K C" )?" J14K C" )?" J14K C" )?" J14K C" )?" J14K C" )?" J14K C" )?" J14K C" )?" J14K

CONSTRAINTS <3EY= * I!" I B(I ;,T;A@@ ;,T;A@@ ;,T;A@@ ;A@@ ;,T;A@@ ;,T;A@@ ;,T;A@@ ;,T;A@@ ;,T;A@@ ;,T;A@@ ;,T;A@@ ;,T;A@@ ;,T;A@@

REFERENCES FROM

+ 2. 3. 4. 5. 6. 9. =. 1> 11 1+ 12 13 *"$$-, ' 7I $T;"!( @"$T;"!( (!"I@I' $()A ITILEA($TI,; $()A ITIL";$-( ),;T")TL;A! !,<I@(L;A! ),;T")TL;A! "'' ($$ ),!*";I;"!( $T"TA$

),!*";I '(T"I@$

J(# De% "$!:

- 36 -

SNO 1

COLUMN NAME J,<LI' J,<L),'(

DATA TYPE <SIZE= I;TJ1>K C" )?" J14K C" )?" J14K C" )?" J14K '"T(J1+K '"T(J1+K C" )?" J14K C" )?" J14K C" )?" J14K I;TJ3K C" )?" J14K C" )?" J14K

CONSTRAINTS <3EY= * I!" I B(I ;,T;A@@ ;,T;A@@ ;,T;A@@ ;,T;A@@ ;,T;A@@ ;,T;A@@ ;,T;A@@ ;,T;A@@ ;,T;A@@ ;,T;A@@ ;,T;A@@

REFERENCES FROM

+ 2. 3. 4. 5. 6. 9. =. 1> 11 1+

J,<L;"!( J,<L'($) I*TI,; *,$T('L'"T( I;T( CI(-L'"T( 7A;)TI,;"@L" (" B(I-$BI@@$ ),!*";IL;"!( (#*( I(;)( (!"I@-I' @,)"TI,;

),!*";I '(T"I@$

Emp resume details4

SNO 1

COLUMN NAME (!*@,I( LI'

DATA TYPE <SIZE= I;TJ1>K

CONSTRAINTS <3EY= 7, (I/; B(I

REFERENCES FROM (!*@,I( T"<@( J,< $((B( T"<@(

$((B( LI'

I;TJ1>K

7, (I/; B(I

C(-' ,& 6e% "$!:

- 39 -

S'(
0 2 7 . 3 8 9

C(L*,' 'A,E
"O5PAN4=ID "O5PAN4=NA5E "O5PAN4=WE SITE "O5PAN4=E5AI!ID "O5PAN4=IN$O "O5PAN4=ADD#ESS "O5PAN4="ONTA"T

DA.E ./PE :SI;E<

I;TJ1>K C" )?" J14K C" )?" J14K C" )?" J14K C" )?" J14K C" )?" J14K INT-01/

C('S.$AI'.S :0E/<
P#I5A#4:E4 ;,T;A@@ ;,T;A@@ ;,T;A@@ ;,T;A@@ ;,T;A@@ ;,T;A@@

$EFE$E'CES F$(,

J(# F ") De% "$!:

S'(
0 2 7

C(L*,' 'A,E
INTE#VIEWDATE !O"ATION $UN"TIONA!=A#EA

DA.E ./PE :SI;E<

DATETI5E-02/ C" )?" J14K C" )?" J14K

C('S.$AI'.S :0E/<
;,T;A@@ ;,T;A@@ ;,T;A@@

$EFE$E'CES F$(,

See;e)>'(!%>)e!0-e De% "$!:

- 3= -

S'( 1 + 2 3 4 5 6 9 = 1 > 1 1 1 + 1 2 1 3 1 4 1 5 1 6

C(L*,' 'A,E 7I $T;"!( @"$T;"!( (!"I@I' @,)"TI,; $()A ITIL";$-( ),A;T I *?,; L;A! !,<I@(L;A! (#*( I(;)( ";;;A"@L$"@" I 7A;)TI,;"@L" (" ),!*";IL;"!( $((B( LI' B(IL$BI@@$ ($A!(L*"T? ($A!(-?("'@I;( <"$I)LEA"@I7I)"TI,;

DA.E ./PE :SI;E< C" )?" J14K C" )?" J14K C" )?" J14K C" )?" J14K C" )?" J14K C" )?" J14K I;TJ1>K I;TJ1>K I;TJ1>K I;TJ1>K C" )?" J14K C" )?" J14K C" )?" J14K C" )?" J14K C" )?" J14K C" )?" J14K C" )?" J14K

C('S.$AI'.S :0E/< ;,T;A@@ ;A@@ ;,T;A@@ ;,T;A@@ ;,T;A@@ ;,T;A@@ ;,T;A@@ ;,T;A@@ ;,T;A@@ ;,T;A@@ ;,T;A@@ ;,T;A@@ ;,T;A@@ ;,T;A@@ ;,T;A@@ ;,T;A@@ ;,T;A@@

$EFE$E'CES F$(,

J,<$((B( J,<$((B(

- 4> -

De!*)"'%"(, (4 Te*+,($(2& U!e6 ", P)(5e*%

?. De!*)"'%"(, (4 Te*+,($(2& U!e6 ", P)(5e*%.

- 41 -

?.1. INTRODUCTION TO .NET F) -e7();

The .;(T 7ramework is a new computing platform that simplifies application development in the highly distributed environment of the Internet. The .;(T 7ramework is designed to fulfill the following objectives.

To provide a consistent object-oriented programming environment whether object code is stored and e0ecuted locally, e0ecuted locally but Internet-distributed, or e0ecuted remotely.

To provide a code-e0ecution environment that minimi%es software deployment and versioning conflicts. To provide a code-e0ecution environment that guarantees safe e0ecution of code, including code created by an unknown or semi-trusted third party. To provide a code-e0ecution environment that eliminates the performance problems of scripted or interpreted environments. To make the developer e0perience consistent across widely varying types of applications, such as -indows-based applications and -eb-based applications. To build all communication on industry standards to ensure that code based on the .;(T 7ramework can integrate with any other code.

The .;(T 7ramework has two main components. the common language runtime and the .;(T 7ramework class library. The common language runtime is the foundation of the .;(T 7ramework. Iou can think of the runtime as an agent that manages code at e0ecution time, providing core services such as memory management, thread management, and emoting, while also enforcing strict type safety and other forms of code accuracy that ensure security and robustness. In fact, the concept of code management is a fundamental principle of the runtime. )ode that targets the runtime is known as managed code, while code that does not target the runtime is known as unmanaged code. The class library, the other main component of the .;(T 7ramework, is a comprehensive, object-oriented collection of reusable types that you can use to develop applications ranging from traditional command-line or graphical user interface J/AIK applications to applications

- 4+ -

based on the latest innovations provided by "$*.;(T, such as -eb 7orms and #!@ -eb services. The .;(T 7ramework can be hosted by unmanaged components that load the common language runtime into their processes and initiate the e0ecution of managed code, thereby creating a software environment that can e0ploit both managed and unmanaged features. The .;(T 7ramework not only provides several runtime hosts, but also supports the development of third-party runtime hosts. 7or e0ample, "$*.;(T hosts the runtime to provide a scalable, server-side environment for managed code. "$*.;(T works directly with the runtime to enable -eb 7orms applications and #!@ -eb services, both of which are discussed later in this topic. Internet (0plorer is an e0ample of an unmanaged application that hosts the runtime Jin the form of a !I!( type e0tensionK. Asing Internet (0plorer to host the runtime enables you to embed managed components or -indows 7orms controls in ?T!@ documents. ?osting the runtime in this way makes managed mobile code Jsimilar to !icrosoftM "ctive#M controlsK possible, but with significant improvements that only managed code can offer, such as semi-trusted e0ecution and secure isolated file storage. The following illustration shows the relationship of the common language runtime and the class library to your applications and to the overall system. The illustration also shows how managed code operates within a larger architecture.

FEATURES OF THE COMMON LANGUAGE RUNTIME

The common language runtime manages memory, thread e0ecution, code e0ecution, code safety verification, compilation, and other system services. These features are intrinsic to the managed code that runs on the common language runtime. -ith regards to security, managed components are awarded varying degrees of trust, depending on a number of factors that include their origin Jsuch as the Internet, enterprise network, or local computerK. This means that a managed component might or might not be

- 42 -

able to perform file-access operations, registry-access operations, or other sensitive functions, even if it is being used in the same active application. The runtime enforces code access security. 7or e0ample, users can trust that an e0ecutable embedded in a -eb page can play an animation on screen or sing a song, but cannot access their personal data, file system, or network. The security features of the runtime thus enable legitimate Internet-deployed software to be e0ceptionally featuring rich. The runtime also enforces code robustness by implementing a strict type- and codeverification infrastructure called the common type system J)T$K. The )T$ ensures that all managed code is self-describing. The various !icrosoft and third-party language compilers /enerate managed code that conforms to the )T$. This means that managed code can consume other managed types and instances, while strictly enforcing type fidelity and type safety. In addition, the managed environment of the runtime eliminates many common software issues. 7or e0ample, the runtime automatically handles object layout and manages references to objects, releasing them when they are no longer being used. This automatic memory management resolves the two most common application errors, memory leaks and invalid memory references. The runtime also accelerates developer productivity. 7or e0ample, programmers can write applications in their development language of choice, yet take full advantage of the runtime, the class library, and components written in other languages by other developers. "ny compiler vendor who chooses to target the runtime can do so. @anguage compilers that target the .;(T 7ramework make the features of the .;(T 7ramework available to e0isting code written in that language, greatly easing the migration process for e0isting applications. -hile the runtime is designed for the software of the future, it also supports software of today and yesterday. Interoperability between managed and unmanaged code enables developers to continue to use necessary ),! components and '@@s. The runtime is designed to enhance performance. "lthough the common language runtime provides many standard runtime services, managed code is never interpreted. " feature called just-in-time JJITK compiling enables all managed code to run in the native machine language of the system on which it is e0ecuting. !eanwhile, the memory manager

- 43 -

removes the possibilities of fragmented memory and increases memory locality-ofreference to further increase performance. 7inally, the runtime can be hosted by high-performance, server-side applications, such as !icrosoftM $E@ $erverN and Internet Information $ervices JII$K. This infrastructure enables you to use managed code to write your business logic, while still enjoying the superior performance of the industryOs best enterprise servers that support runtime hosting.

.NET FRAMEWOR3 CLASS LIBRARY

The .;(T 7ramework class library is a collection of reusable types that tightly integrate with the common language runtime. The class library is object oriented, providing types from which your own managed code can derive functionality. This not only makes the .;(T 7ramework types easy to use, but also reduces the time associated with learning new features of the .;(T 7ramework. In addition, third-party components can integrate seamlessly with classes in the .;(T 7ramework. 7or e0ample, the .;(T 7ramework collection classes implement a set of interfaces that you can use to develop your own collection classes. Iour collection classes will blend seamlessly with the classes in the .;(T 7ramework. "s you would e0pect from an object-oriented class library, the .;(T 7ramework types enable you to accomplish a range of common programming tasks, including tasks such as string management, data collection, database connectivity, and file access. In addition to these common tasks, the class library includes types that support a variety of speciali%ed development scenarios. 7or e0ample, you can use the .;(T 7ramework to develop the following types of applications and services.

)onsole applications. $cripted or hosted applications. -indows /AI applications J-indows 7ormsK. "$*.;(T applications. #!@ -eb services. -indows services.

- 44 -

7or e0ample, the -indows 7orms classes are a comprehensive set of reusable types that vastly simplify -indows /AI development. If you write an "$*.;(T -eb 7orm application, you can use the -eb 7orms classes.

?.2

ASP.NET

Se)1e) A''$"* %"(, De1e$('-e,%

$erver-side applications in the managed world are implemented through runtime hosts. Anmanaged applications host the common language runtime, which allows your custom managed code to control the behavior of the server. This model provides you with all the features of the common language runtime and class library while gaining the performance and scalability of the host server. The following illustration shows a basic network schema with managed code running in different server environments. $ervers such as II$ and $E@ $erver can perform standard operations while your application logic e0ecutes through the managed code.

SERVER@SIDE MANAGED CODE

"$*.;(T is the hosting environment that enables developers to use the .;(T 7ramework to target -eb-based applications. ?owever, "$*.;(T is more than just a runtime hostP it is a complete architecture for developing -eb sites and Internet-distributed objects using managed code. <oth -eb 7orms and #!@ -eb services use II$ and "$*.;(T as the publishing mechanism for applications, and both have a collection of supporting classes in the .;(T 7ramework. #!@ -eb services, an important evolution in -eb-based technology, are distributed, server-side application components similar to common -eb sites. ?owever, unlike -eb-based applications, #!@ -eb services components have no AI and are not targeted for browsers such as Internet (0plorer and ;etscape ;avigator. Instead, #!@ -eb services consist of reusable software components designed to be consumed by other applications, such as traditional client applications, -eb-based applications, or even other

- 45 -

#!@ -eb services. "s a result, #!@ -eb services technology is rapidly moving application development and deployment into the highly distributed environment of the Internet. If you have used earlier versions of "$* technology, you will immediately notice the improvements that "$*.;(T and -eb 7orms offers. 7or e0ample, you can develop -eb 7orms pages in any language that supports the .;(T 7ramework. In addition, your code no longer needs to share the same file with your ?TT* te0t Jalthough it can continue to do so if you preferK. -eb 7orms pages e0ecute in native machine language because, like any other managed application, they take full advantage of the runtime. In contrast, unmanaged "$* pages are always scripted and interpreted. "$*.;(T pages are faster, more functional, and easier to develop than unmanaged "$* pages because they interact with the runtime like any managed application. The .;(T 7ramework also provides a collection of classes and tools to aid in development and consumption of #!@ -eb services applications. #!@ -eb services are built on standards such as $,"* Ja remote procedure-call protocolK, #!@ Jan e0tensible data formatK, and -$'@ J the -eb $ervices 'escription @anguageK. The .;(T 7ramework is built on these standards to promote interoperability with non-!icrosoft solutions. 7or e0ample, the -eb $ervices 'escription @anguage tool included with the .;(T 7ramework $'B can 1uery an #!@ -eb service published on the -eb, parse its -$'@ description, and produce )D or Cisual <asic source code that your application can use to become a client of the #!@ -eb service. The source code can create classes derived from classes in the class library that handle all the underlying communication using $,"* and #!@ parsing. "lthough you can use the class library to consume #!@ -eb services directly, the -eb $ervices 'escription @anguage tool and the other tools contained in the $'B facilitate your development efforts with the .;(T 7ramework. If you develop and publish your own #!@ -eb service, the .;(T 7ramework provides a set of classes that conform to all the underlying communication standards, such as $,"*, -$'@, and #!@. Asing those classes enables you to focus on the logic of your service, without concerning yourself with the communications infrastructure re1uired by distributed software development.

- 46 -

7inally, like -eb 7orms pages in the managed environment, your #!@ -eb service will run with the speed of native machine language using the scalable communication of II$.

ACTIVE SERVER PAGES.NET

"$*.;(T is a programming framework built on the common language runtime that can be used on a server to build powerful -eb applications. "$*.;(T offers several important advantages over previous -eb development models. E,+ ,*e6 Pe)4()- ,*e. "$*.;(T is compiled common language runtime code running on the server. Anlike its interpreted predecessors, "$*.;(T can take advantage of early binding, just-in-time compilation, native optimi%ation, and caching services right out of the bo0. This amounts to dramatically better performance before you ever write a line of code. W()$6@C$ !! T(($ S0''()%. The "$*.;(T framework is complemented by a rich toolbo0 and designer in the Cisual $tudio integrated development environment. -I$I-I/ editing, drag-and-drop server controls, and automatic deployment are just a few of the features this powerful tool provides. P(7e) ,6 F$eA"#"$"%&. <ecause "$*.;(T is based on the common language runtime, the power and fle0ibility of that entire platform is available to -eb application developers. The .;(T 7ramework class library, !essaging, and 'ata "ccess solutions are all seamlessly accessible from the -eb. "$*.;(T is also language-independent, so you can choose the language that best applies to your application or partition your application across many languages. 7urther, common language runtime interoperability guarantees that your e0isting investment in ),!-based development is preserved when migrating to "$*.;(T. S"-'$"*"%&. "$*.;(T makes it easy to perform common tasks, from simple form submission and client authentication to deployment and site configuration. 7or e0ample, the "$*.;(T page framework allows you to build user interfaces that cleanly separate application logic from presentation code and to handle events in a simple, Cisual <asic like forms processing model. "dditionally, the common language runtime simplifies

- 49 -

development, with managed code services such as automatic reference counting and garbage collection. M , 2e #"$"%&. "$*.;(T employs a te0t-based, hierarchical configuration system, which simplifies applying settings to your server environment and -eb applications. <ecause configuration information is stored as plain te0t, new settings may be applied without the aid of local administration tools. This Q%ero local administrationQ philosophy e0tends to deploying "$*.;(T 7ramework applications as well. "n "$*.;(T 7ramework application is deployed to a server simply by copying the necessary files to the server. ;o server restart is re1uired, even to deploy or replace running compiled code. S* $ #"$"%& ,6 A1 "$ #"$"%&. "$*.;(T has been designed with scalability in mind, with features specifically tailored to improve performance in clustered and multiprocessor environments. 7urther, processes are closely monitored and managed by the "$*.;(T runtime, so that if one misbehaves Jleaks, deadlocksK, a new process can be created in its place, which helps keep your application constantly available to handle re1uests. C0!%(-"B #"$"%& ,6 EA%e,!"#"$"%&. "$*.;(T delivers a well-factored architecture that allows developers to Qplug-inQ their code at the appropriate level. In fact, it is possible to e0tend or replace any subcomponent of the "$*.;(T runtime with your own custom-written component. Implementing custom authentication or state services has never been easier. Se*0)"%&. -ith built in -indows authentication and per-application configuration, you can be assured that your applications are secure.

?.3

S.L SERVER
" database management, or '<!$, gives the user access to their data and helps

them transform the data into information. $uch database management systems include d<ase, parado0, I!$, $E@ $erver and $E@ $erver. These systems allow users to create, update and e0tract information from their database.

- 4= -

" database is a structured collection of data. 'ata refers to the characteristics of people, things and events. $E@ $erver stores each data item in its own fields. In $E@ $erver, the fields relating to a particular person, thing or event are bundled together to form a single complete unit of data, called a record Jit can also be referred to as raw or an occurrenceK. (ach record is made up of a number of fields. ;o two fields in a record can have the same field name. 'uring an $E@ $erver 'atabase design project, the analysis of your business needs identifies all the fields or attributes of interest. If your business needs change over time, you define any additional fields or change the definition of e0isting fields.

S.L SERVER TABLES

$E@ $erver stores records relating to each other in a table. 'ifferent tables are created for the various groups of information. elated tables are grouped together to form a database.

PRIMARY 3EY
(very table in $E@ $erver has a field or a combination of fields that uni1uely identifies each record in the table. The Ani1ue identifier is called the *rimary Bey, or simply the Bey. The primary key provides the means to distinguish one record from all other in a table. It allows the user and the database system to identify, locate and refer to one particular record in the database.

RELATIONAL DATABASE
$ometimes all the information of interest to a business operation can be stored in one table. $E@ $erver makes it very easy to link the data in multiple tables. !atching an employee to the department in which they work is one e0ample. This is what makes $E@ $erver a relational database management system, or '<!$. It stores data in two or more tables and enables you to define relationships between the table and enables you to define relationships between the tables.

- 5> -

FOREIGN 3EY
-hen a field is one table matches the primary key of another field is referred to as a foreign key. " foreign key is a field or a group of fields in one table whose values match those of the primary key of another table.

REFERENTIAL INTEGRITY
;ot only does $E@ $erver allow you to link multiple tables, it also maintains consistency between them. (nsuring that the data among related tables is correctly matched is referred to as maintaining referential integrity.

- 51 -

SYSTEM TESTING AND IMPLEMENTATION

- 5+ -

C. SYSTEM TESTING AND IMPLEMENTATION

C.1. INTRODUCTION
$oftware testing is a critical element of software 1uality assurance and represents the ultimate review of specification, design and coding. In fact, testing is the one step in the software engineering process that could be viewed as destructive rather than constructive. " strategy for software testing integrates software test case design methods into a well-planned series of steps that result in the successful construction of software. Testing is the set of activities that can be planned in advance and conducted systematically. The underlying motivation of program testing is to affirm software 1uality with methods that can economically and effectively apply to both strategic to both large and small-scale systems.

C.2. SOFTWARE TESTING

The software engineering process can be viewed as a spiral. Initially system engineering defines the role of software and leads to software re1uirement analysis where the information domain, functions, behavior, performance, constraints and validation criteria for software are established. !oving inward along the spiral, we come to design and finally to coding. To develop computer software we spiral in along streamlines that decrease the level of abstraction on each turn. " strategy for software testing may also be viewed in the conte0t of the spiral. Anit testing begins at the verte0 of the spiral and concentrates on each unit of the software as implemented in source code. Testing progress by moving outward along the spiral to integration testing, where the focus is on the design and the construction of the software architecture. Talking another turn on outward on the spiral we encounter validation testing where re1uirements established as part of software re1uirements analysis are validated against the software that has been constructed. 7inally we arrive at system testing, where the software and other system elements are tested as a whole.

- 52 -

A;IT T($TI;/

!,'A@( T($TI;/

"o+ponent Testin%

$A<-$I$T(! T($I;/

$I$T(! T($TI;/

Inte%ration Testin%

User Testin%

"))(*T";)( T($TI;/

C.3. U,"% Te!%",2

Anit testing focuses verification effort on the smallest unit of software design, the module. The unit testing we have is white bo0 oriented and some modules the steps are conducted in parallel.

1. WHITE BOX TESTING

This type of testing ensures that "ll independent paths have been e0ercised at least once "ll logical decisions have been e0ercised on their true and false sides

- 53 -

"ll loops are e0ecuted at their boundaries and within their operational bounds "ll internal data structures have been e0ercised to assure their validity.

To follow the concept of white bo0 testing we have tested each form .we have created independently to verify that 'ata flow is correct, "ll conditions are e0ercised to check their validity, "ll loops are e0ecuted on their boundaries.

2. BASIC PATH TESTING

(stablished techni1ue of flow graph with )yclomatic comple0ity was used to derive test cases for all the functions. The main steps in deriving test cases were. Ase the design of the code and draw correspondent flow graph. 'etermine the )yclomatic comple0ity of resultant flow graph, using formula. CJ/KR(-;S+ or CJ/KR*S1 or CJ/KR;umber ,f egions -here CJ/K is )yclomatic comple0ity, ( is the number of edges, ; is the number of flow graph nodes, * is the number of predicate nodes. 'etermine the basis of set of linearly independent paths.

3. CONDITIONAL TESTING
In this part of the testing each of the conditions were tested to both true and false aspects. "nd all the resulting paths were tested. $o that each path that may be generate on particular condition is traced to uncover any possible errors.

/. DATA FLOW TESTING

- 54 -

This type of testing selects the path of the program according to the location of definition and use of variables. This kind of testing was used only when some local variable were declared. The definition-use chain method was used in this type of testing. These were particularly useful in nested statements.

9. LOOP TESTING
In this type of testing all the loops are tested to all the limits possible. The following e0ercise was adopted for all loops. "ll the loops were tested at their limits, just above them and just below them. "ll the loops were skipped at least once. 7or nested loops test the inner most loop first and then work outwards. 7or concatenated loops the values of dependent loops were set with the help of connected loop. Anstructured loops were resolved into nested loops or concatenated loops and tested as above. (ach unit has been separately tested by the development team itself and all the input have been validated.

- 55 -

OUTPUT SCREENS

- 56 -

HOME PAGE

- 59 -

ADMIN LOGIN PAGE

- 5= -

ADMIN FUNCTIONALITY FORM

- 6> -

VIEWING THE EMPLOYER DETAILS BY ADMIN:

- 61 -

DELETE THE EMPLOYER DETAILS BY ADMIN:

- 6+ -

ADDING JOBFAIRS BY ADMIN:

- 62 -

(!*@,I( @,/I;

- 63 -

SUBMIT THE JOB FAIR DETAILS BY ADMIN:

- 64 -

VIEWING THE COMPANY DETAILS BY ADMIN:

- 65 -

LOGOUT PAGE OF ADMIN:

- 66 -

EMPLOYER REGISTRATION FORM FOR NEW USER

PASSWORD RECOVERY FOR EMPLOYERS:

- 69 -

- 6= -

RETRIEVING PASSWORD:

- 9> -

FUNCTIONALITY OF EMPLOYER:

- 91 -

UPDATE EMPLOYER DETAILS BY EMPLOYER:

- 9+ -

UPDATING EMPLOYER DETAILS:

- 92 -

SEARCHING THE RESUMES BY EMPLOYER:

- 93 -

DISPLAYING JOB SEE3ERS DETAILS:

- 94 -

JOB POSTING BY EMPLOYER:

- 95 -

LOGOUT FORM FOR EMPLOYER:

D JOB SEE3ERS REGISTRATION FORM FOR NEW JOB SEE3ERS:

- 96 -

FORGOT PASSWORD FORM FOR JOB SEE3ERS:

- 99 -

- 9= -

RETRIEVING PASSWORD FOR JOB SEE3ERS:

- => -

FUNCTIONALITY FORM FOR JOB SEE3ERS:

- =1 -

VIEWING THE JOBS BY JOB SEE3ERS:

- =+ -

- =2 -

SEARCHING JOBS BY JOB SEE3ERS:

- =3 -

DISPLAYS JOB DETAILS:

DISPLAYING APPLIED JOB DETAILS:

- =4 -

UPDATE SEE3ER ACCOUNT:

- =5 -

POSTING RESUME FOR APPLIED JOBS:

- =6 -

- =9 -

- == -

UPDATING JOB SEE3ER DETAILS:

VIEWING JOB FAIR DETAILS BY JOB SEE3ERS:

- 1>> -

DISPLAYING JOB DETAILS ON PARTICULAR DATE:

- 1>1 -

- 1>+ -

NO JOBS FOUND ON PARTICULAR DATE SELECTED:

- 1>2 -

ABOUT US:

- 1>3 -

S&!%e- Se*0)"%&

- 1>4 -

E.S&!%e- Se*0)"%&
E.1. I,%)(60*%"(,
The protection of computer based resources that includes hardware, software, data, procedures and people against unauthori%ed use or natural 'isaster is known as $ystem $ecurity. $ystem $ecurity can be divided into four related issues. $ecurity Integrity *rivacy )onfidentiality

SYSTEM SECURITY refers to the technical innovations and procedures applied to the hardware and operation systems to protect against deliberate or accidental damage from a defined threat. DATA SECURITY is the protection of data from loss, disclosure, modification and destruction. SYSTEM INTEGRITY refers to the power functioning of hardware and programs, appropriate physical security and safety against e0ternal threats such as eavesdropping and wiretapping. - 1>5 -

PRIVACY defines the rights of the user or organi%ations to determine what information they are willing to share with or accept from others and how the organi%ation can be protected against unwelcome, unfair or e0cessive dissemination of information about it. CONFIDENTIALITY is a special status given to sensitive information in a database to minimi%e the possible invasion of privacy. It is an attribute of information that characteri%es its need for protection.

E.2. SECURITY IN SOFTWARE

$ystem security refers to various validations on data in form of checks and controls to avoid the system from failing. It is always important to ensure that only valid data is entered and only valid operations are performed on the system. The system employees two types of checks and controls.

CLIENT SIDE VALIDATION

Carious client side validations are used to ensure on the client side that only valid data is entered. )lient side validation saves server time and load to handle invalid data. $ome checks imposed are. C<$cript in used to ensure those re1uired fields are filled with suitable data only. !a0imum lengths of the fields of the forms are appropriately defined. 7orms cannot be submitted without filling up the mandatory data so that manual mistakes of submitting empty fields that are mandatory can be sorted out at the client side to save the server time and load. Tab-inde0es are set according to the need and taking into account the ease of user while working with the system.

SERVER SIDE VALIDATION

$ome checks cannot be applied at client side. $erver side checks are necessary to save the system from failing and intimating the user that some invalid operation has been performed or the performed operation is restricted. $ome of the server side checks imposed is.

- 1>6 -

$erver side constraint has been imposed to check for the validity of primary key and foreign key. " primary key value cannot be duplicated. "ny attempt to duplicate the primary value results into a message intimating the user about those values through the forms using foreign key can be updated only of the e0isting foreign key values.

Aser is intimating through appropriate messages about the successful operations or e0ceptions occurring at server side. Carious "ccess )ontrol !echanisms have been built so that one user may not agitate upon another. "ccess permissions to various types of users are controlled according to the organi%ational structure. ,nly permitted users can log on to the system and can have access according to their category. Aser- name, passwords and permissions are controlled o the server side.

- 1>9 -

CONCLUSION

- 1>= -

1:. CONCLUSION
In this paper, we have presented a portal service techni1ue in order to reduce the gap between Industry and Industry needed resources. This helps for the jobseekers to upload resumes, searches for the jobs based on keywords and finally applies for the suitable jobs. This system provides useful feature for jobseekers, called job calendar. If the user selects any date in the job calendar then it displays list of jobs available on that particular date in the same page. This feature completely developed by implementing "ja0 features. Job )alendar feature was employed to solve the proposed optimi%ation problem. 7urthermore, we presented a $earch (ngine which is used to provide the search option to the job seekers like based on the functional area and location. If the jobseekers selects any location it shows list of all available jobs on that place. -e developed an efficient "ja0 feature for this portal which speeds up the page and increase more efficiency of the page. " proof of concept implementation of our portal techni1ue was used to conduct e0periments using both synthetic and real-world data. . " comparison our portal techni1ue with previously posed techni1ues shows the superiority of our techni1ue to deletion, alteration, and insertion attacks.

- 11> -

BIBLIOGRAPHY

- 111 -

11.BIBLIOGRAPHY
FOR .NET INSTALLATION
www.support.mircosoft.com

FOR DEPLOYMENT AND PAC3ING ON SERVER

www.developer.com www.14seconds.com

FOR S.L
www.msdn.microsoft.com

FOR ASP.NET
www.msdn.microsoft.comTnetT1uickstartTaspplusTdefault.com www.asp.net www.fme0pense.comT1uickstartTaspplusTdefault.com www.asptoday.com www.aspfree.com www.3guysfromrolla.comTinde0.asp0

- 11+ -