onlie crporate recruitment system

8/13/2019 Onlie crporate recruitment system

1/118

Corporate Recruitment Management System

ABSTRACT

Corporate Recruitment System (CRS) is web-based tool to reduce communication gap

between Job providers and Job seekers.

Te Main ob!ective o" tis solution is to make easy te recruitment process o"

any organi#ation. Tis CRS is designed by keeping in mind bot parties Job providers

and Job seekers. CRS allows Job seekers to register teir details like skills and

e$perience wit te system% and ten on te oter and even it allows !ob providers to

post teir re&uirements wit te system.

Corporate Recruitment Management system is elp"ul "or te !ob providers i.e.

companies wic are in need o" employees% !ob seekers wo are in need o" !ob% ("or bot

'$p and "resers). Tis portals main aim is to provide te vacancies available "or te !ob

seekers witout taking any carge "rom tem in T tecnologies.CRS will automatically

send mails to all !ob seekers wose skills are matced wit te re&uirement.

Features :

Tis pro!ect can be used very easily in te process o" decision making in new

recruitments.

'""ective way o" providing communication between !ob providers and !ob

seekers.

Reliable and consistent way o" searcing !obs.

Conducting secured and restricted online e$am "or screened employees.

Sending 'mail noti"ication to all !ob seekers.

- -


2/118


CONTENTS

.ntroduction.......................................................................................................*-+

.. ,eneral ntroduction

.. ro!ect /escription

. System 0nalysis.............................................................................................1-2

.. 3b!ectives o" System

.. 4ser Re&uirements

.5. 6ardware 0nd So"tware Re&uirements

5. 7easibility Study.............................................................................................-5

5.. 'conomic 7easibility

5.. 3perational 7easibility

5.5. Tecnical 7easibility

8. So"tware /esign.............................................................................................8-+5

8.. So"tware mplementation

8.. /ata 7low /iagrams

8.5. 0bout 4M9

8.8. 4M9 /iagrams

8.8.. 4se Case /iagrams

8.8.. 0ctivity /iagrams

8.8.5. Class /iagrams

8.8.8. Se&uence /iagrams

*. /atabase /esign.............................................................................................+8-+:

+. nput and 3utput Screens...............................................................................12-22

1. Testing .........................................................................................................2-21

1.. 4nit Testing

- -


3/118


1.. ntegration Testing

1.5. System Testing

1.8. ;alidation Testing

1.*. 3utput Testing

1.+. 0cceptance Testing


4/118


- 8 -


5/118


INTRODUCTION

Te ro!ect titled ?Corporate Recruitment System@ is one wic elps out te

6R ersonal in te recruitment o" new candidates to te company and elps te

recruitment process as a wole.

Corporate recruitment System (CRS) is a part o" te 6uman Resource Management

System tat structures and manages te entire recruitment process. Tis corporate

recruitment service system will primarily "ocus on te posting and management o" !ob

vacancies. 6owever% tis will be te initial step towards acieving te long term goal o"

delivering broader services to support recruitment.

Tis will provide service to te potential !ob applicants to searc "or working

opportunities and i" tey coose tey may be able to make an application online. t is

planned tat ultimately all vacancies will be posted online and tat tis site will o""er

employers te "acilities bot to post teir vacancies online and to review and manage te

resulting applications e""iciently troug te web wit te elp o" te CRS. CRS will

allow !ob provider to establis one to one relationsips wit candidates% by keeping in

close communications wit tem troug out te application% interview% and iring

process. t even allows te candidates to track te progress o" teir application.

n oter words% enables te employer to treat candidates like customers.

- * -


6/118


Features:-

Corporate Recruitment System (CRS) as all te "eatures and "unctions

re&uired "or e$ecuting a success"ul recruitment task% providing e$ceptional case o" use

"or recruitment.

Te 7ollowing are te overview o" te "eatures and bene"its o" CRS.

. /atabase so"tware installed and pre-con"igures "or te immediate use o" te

system e""ectively and e""iciently.

. re-con"igured and ready to run Jobs database wit management module "or

adding and deleting e""iciently.

5. /atabase to store te candidateAs details securely.

8. Customi#able autentication to control access to database "iles using assigned

user login and password control.

*. rovides in"ormation to te managers so tat tey can make !udgment about

particular situations.

+. Reductions in te cost o" iring B tere will be between *2-+2 percent decrease in

te cost o" iring.

1. Reduces te time re&uired to complete te recruitment process o" any

organi#ation.

- + -


7/118


- 1 -


8/118


SYSTEM:

/esigning and implementing te new links.

/esigning and implementing te system "or its users.

0rranging new links as sub!ect wise.

SYSTEM ANALYSIS:

System analysis will be per"ormed to determine i" it is "easible to design

in"ormation based on policies and plans o" te organi#ation and on user re&uirements

and to eliminate te weaknesses o" te present system.

Te new system sould be cost e""ective.

To augment management% improve productivity and services.

To enance user system inter"ace.

To improve in"ormation &uali"y and usability.

To upgrade systems reliability% availability% "le$ibility and growt potential.

Objectives o s!ste":

Te proposed system is an attempt to provide a ric solution to lessen te inconvenience

in andling te cumbersome !ob o" managing and sceduling. Systematic andling o" te

scedules in suc a way is a key to increasing its manageability and its competence.

- < -


9/118


Objective:-

. Tis system provides service to te potential !ob applicants to searc "or working

opportunities.

. Tis system elps te 6R ersonal in te recruitment o" new candidates to te

company.

5. Corporate Recruitment System will allow !ob provider to establis one to one

relationsips wit candidates.

8. Tis corporate recruitment service system will primarily "ocus on te posting and

management o" !ob vacancies.

*. Tis system is designed suc tat ultimately all vacancies will be posted online

and would o""er employers te "acilities to post teir vacancies online.

+. t elps to review and manage te resulting applications e""iciently troug te

web.

1. t even allows te candidates to track te progress o" teir application.


10/118


8. 6elps to provide control access to database "iles using assigned user login and

password control.

%ARD&ARE ' SOFT&ARE S(ECIFICATIONS

)*+ %ARD&ARE RE,UIREMENTS:

rocessor D ntel -; system

rocessor Speed D *2M6# to R0M

6ard /isk D 82,>

)* SOFT&ARE RE,UIREMENTS:

3perating System D Eindows F

/atabase D S&l Server

Server side tecnology D 0S.Get

Server side scripting D 0S

Client side scripting D 6TM9

Eeb-Server D S

- 2 -


11/118


- -


12/118


.* FEASIBILITY STUDY

.*+ Eco$o"ic Feasibi/it!

'conomic "easibility attempts to weig te costs o" developing and

implementing a new system% against te bene"its tat would accrue "rom aving te new

system in place. Tis "easibility study gives te top management te economic

!usti"ication "or te new system.

0 simple economic analysis wic gives te actual comparison o" costs and bene"its are

muc more meaning"ul in tis case. n addition% tis proves to be a use"ul point o"

re"erence to compare actual costs as te pro!ect progresses. Tere could be various types

o" intangible bene"its on account o" automation. Tese could include increased customer

satis"action% improvement in product &uality better decision making timeliness o"

in"ormation% e$pediting activities% improved accuracy o" operations% better

documentation and record keeping% "aster retrieval o" in"ormation% better employee

morale.

.* O0eratio$a/ Feasibi/it!

roposed pro!ect is bene"icial only i" it can be turned into in"ormation

systems tat will meet te organi#ations operating re&uirements. Simply stated% tis test

o" "easibility asks i" te system will work wen it is developed and installed. 0re tere

ma!or barriers to implementationH 6ere are &uestions tat will elp test te operational

"easibility o" a pro!ect

s tere su""icient support "or te pro!ect "rom management and "rom usersH " te

- -


13/118


current system is well liked and used to te e$tent tat persons will not be able to see

reasons "or cange% tere may be resistance. 0re te current business metods acceptable

to te userH " tey are not% 4sers may welcome a cange tat will bring about a more

operational and use"ul systems. 6ave te user been involved in te planning and

development o" te pro!ectH

'arly involvement reduces te cances o" resistance to te system and in general and

increases te likeliood o" success"ul pro!ect.

Since te proposed system was to elp reduce te ardsips encountered. n te e$isting

manual system% te new system was considered to be operational "easible.

.*) Tec1$ica/ Feasibi/it!

'valuating te tecnical "easibility is te trickiest part o" a "easibility

study. Tis is because% at tis point o" time% not too many detailed design o" te system%

making it di""icult to access issues like per"ormance% costs on (on account o" te kind o"

tecnology to be deployed) etc. 0 number o" issues ave to be considered wile doing a

tecnical analysis.

4nderstand te di""erent tecnologies involved in te proposed system be"ore

commencing te pro!ect we ave to be very clear about wat are te tecnologies tat

are to be re&uired "or te development o" te new system. 7ind out weter te

organi#ation currently possesses te re&uired tecnologies. s te re&uired tecnology

available wit te organi#ation.

- 5 -


14/118


- 8 -


15/118


2*+ Sot3are I"0/e"e$tatio$

Microsot*NET Fra"e3or4

Te .G'T 7ramework is a new computing plat"orm tat simpli"ies application

development in te igly distributed environment o" te nternet. Te .G'T 7ramework

is designed to "ul"ill te "ollowing ob!ectives.

To provide a consistent ob!ect-oriented programming environment weter

ob!ect code is stored and e$ecuted locally% e$ecuted locally but nternet-

distributed% or e$ecuted remotely.

To provide a code-e$ecution environment tat minimi#es so"tware deployment

and versioning con"licts.

To provide a code-e$ecution environment tat guarantees sa"e e$ecution o" code%

including code created by an unknown or semi-trusted tird party.

To provide a code-e$ecution environment tat eliminates te per"ormance

problems o" scripted or interpreted environments.

To make te developer e$perience consistency across widely varying types o"

applications% suc as Eindows-based applications and Eeb-based applications.

To build all communication on industry standards to ensure tat code based on

te .G'T 7ramework can integrate wit any oter code.

- * -


16/118


Te .G'T 7ramework as two main componentsD te common language runtime and

te .G'T 7ramework class library. Te common language runtime is te "oundation o"

te .G'T 7ramework. Iou can tink o" te runtime as an agent tat manages code at

e$ecution time% providing core services suc as memory management% tread

management% and remoting% wile also en"orcing strict type sa"ety and oter "orms o"

code accuracy tat ensure security and robustness. n "act% te concept o" code

management is a "undamental principle o" te runtime. Code tat targets te runtime is

known as managed code% wile code tat does not target te runtime is known as

unmanaged code. Te class library% te oter main component o" te .G'T 7ramework%

is a compreensive% ob!ect-oriented collection o" reusable types tat you can use to

develop applications ranging "rom traditional command-line or grapical user inter"ace

(,4) applications to applications based on te latest innovations provided by

0S.G'T% suc as Eeb 7orms and FM9 Eeb services.

Te .G'T 7ramework can be osted by unmanaged components tat load te common

language runtime into teir processes and initiate te e$ecution o" managed code%

tereby creating a so"tware environment tat can e$ploit bot managed and unmanaged

"eatures. Te .G'T 7ramework not only provides several runtime osts% but also

supports te development o" tird-party runtime osts.

7or e$ample% 0S.G'T osts te runtime to provide a scalable% server-side environment

"or managed code. 0S.G'T works directly wit te runtime to enable Eeb 7orms

applications and FM9 Eeb services% bot o" wic are discussed later in tis topic.

nternet '$plorer is an e$ample o" an unmanaged application tat osts te runtime (in

te "orm o" a MM' type e$tension). 4sing nternet '$plorer to ost te runtime enables

you to embed managed components or Eindows 7orms controls in 6TM9 documents.

- + -


17/118


6osting te runtime in tis way makes managed mobile code (similar to Microso"t

0ctiveF controls) possible% but wit signi"icant improvements tat only managed code

can o""er% suc as semi-trusted e$ecution and secure isolated "ile storage.

Te "ollowing illustration sows te relationsip o" te common language runtime and

te class library to your applications and to te overall system. Te illustration also

sows ow managed code operates witin a larger arcitecture.

Features o t1e Co""o$ La$5ua5e Ru$ti"e

Te common language runtime manages memory% tread e$ecution% code e$ecution%

code sa"ety veri"ication% compilation% and oter system services. Tese "eatures are

intrinsic to te managed code tat runs on te common language runtime.

Eit regards to security% managed components are awarded varying degrees o" trust%

depending on a number o" "actors tat include teir origin (suc as te nternet%

enterprise network% or local computer). Tis means tat a managed component migt or

migt not be able to per"orm "ile-access operations% registry-access operations% or oter

sensitive "unctions% even i" it is being used in te same active application.

Te runtime en"orces code access security. 7or e$ample% users can trust tat an

e$ecutable embedded in a Eeb page can play an animation on screen or sing a song% but

cannot access teir personal data% "ile system% or network. Te security "eatures o" te

runtime tus enable legitimate nternet-deployed so"tware to be e$ceptionally "eature

ric.

Te runtime also en"orces code robustness by implementing a strict type- and code-

veri"ication in"rastructure called te common type system (CTS). Te CTS ensures tat

- 1 -


18/118


all managed code is sel"-describing. Te various Microso"t and tird-party language

compilers

,enerate managed code tat con"orms to te CTS. Tis means tat managed code can

consume oter managed types and instances% wile strictly en"orcing type "idelity and

type sa"ety.

n addition% te managed environment o" te runtime eliminates many common so"tware

issues. 7or e$ample% te runtime automatically andles ob!ect layout and manages

re"erences to ob!ects% releasing tem wen tey are no longer being used. Tis automatic

memory management resolves te two most common application errors% memory leaks

and invalid memory re"erences.

Te runtime also accelerates developer productivity. 7or e$ample% programmers can

write applications in teir development language o" coice% yet take "ull advantage o" te

runtime% te class library% and components written in oter languages by oter

developers. 0ny compiler vendor wo cooses to target te runtime can do so. 9anguage

compilers tat target te .G'T 7ramework make te "eatures o" te .G'T 7ramework

available to e$isting code written in tat language% greatly easing te migration process

"or e$isting applications.

Eile te runtime is designed "or te so"tware o" te "uture% it also supports so"tware o"

today and yesterday. nteroperability between managed and unmanaged code enables

developers to continue to use necessary C3M components and /99s.

Te runtime is designed to enance per"ormance. 0ltoug te common language

runtime provides many standard runtime services% managed code is never interpreted. 0

"eature called !ust-in-time (JT) compiling enables all managed code to run in te native

- < -


19/118


macine language o" te system on wic it is e$ecuting. Meanwile% te memory

manager removes te possibilities o" "ragmented memory and increases memory

locality-o"-re"erence to "urter increase per"ormance.

7inally% te runtime can be osted by ig-per"ormance% server-side applications% suc as

Microso"t SK9 ServerL and nternet n"ormation Services (S). Tis in"rastructure

enables you to use managed code to write your business logic% wile still en!oying te

superior per"ormance o" te industrys best enterprise servers tat support runtime

osting.

*NET Fra"e3or4 C/ass Librar!

Te .G'T 7ramework class library is a collection o" reusable types tat tigtly integrate

wit te common language runtime. Te class library is ob!ect oriented% providing types

"rom wic your own managed code can derive "unctionality. Tis not only makes

te .G'T 7ramework types easy to use% but also reduces te time associated wit

learning new "eatures o" te .G'T 7ramework. n addition% tird-party components can

integrate seamlessly wit classes in te .G'T 7ramework.

7or e$ample% te .G'T 7ramework collection classes implement a set o" inter"aces tat

you can use to develop your own collection classes. Iour collection classes will blend

seamlessly wit te classes in te .G'T 7ramework.

0s you would e$pect "rom an ob!ect-oriented class library% te .G'T 7ramework types

enable you to accomplis a range o" common programming tasks% including tasks suc

as string management% data collection% database connectivity% and "ile access. n addition

to tese common tasks% te class library includes types tat support a variety o"

- : -


20/118


speciali#ed development scenarios. 7or e$ample% you can use te .G'T 7ramework to

develop te "ollowing types o" applications and servicesD

Console applications.

Scripted or osted applications.

Eindows ,4 applications (Eindows 7orms).

0S.G'T applications.

FM9 Eeb services.

Eindows services.

7or e$ample% te Eindows 7orms classes are a compreensive set o" reusable types tat

vastly simpli"y Eindows ,4 development. " you write an 0S.G'T Eeb 7orm

application% you can use te Eeb 7orms classes.

C/ie$t A00/icatio$ Deve/o0"e$t

Client applications are te closest to a traditional style o" application in Eindows-based

programming. Tese are te types o" applications tat display windows or "orms on te

desktop% enabling a user to per"orm a task. Client applications include applications suc

as word processors and spreadseets% as well as custom business applications suc as

data-entry tools% reporting tools% and so on. Client applications usually employ windows%

menus% buttons% and oter ,4 elements% and tey likely access local resources suc as

te "ile system and periperals suc as printers.

0noter kind o" client application is te traditional 0ctiveF control (now replaced by te

managed Eindows 7orms control) deployed over te nternet as a Eeb page. Tis

- 2 -


21/118


application is muc like oter client applicationsD it is e$ecuted natively% as access to

local resources% and includes grapical elements.

n te past% developers created suc applications using CCNN in con!unction wit te

Microso"t 7oundation Classes (M7C) or wit a rapid application development (R0/)

environment suc as Microso"t ;isual >asic. Te .G'T 7ramework incorporates

aspects o" tese e$isting products into a single% consistent development environment tat

drastically simpli"ies te development o" client applications.

Te Eindows 7orms classes contained in te .G'T 7ramework are designed to be used

"or ,4 development. Iou can easily create command windows% buttons% menus%

toolbars% and oter screen elements wit te "le$ibility necessary to accommodate

si"ting business needs.

7or e$ample% te .G'T 7ramework provides simple properties to ad!ust visual attributes

associated wit "orms. n some cases te underlying operating system does not support

canging tese attributes directly% and in tese cases te .G'T 7ramework automatically

recreates te "orms. Tis is one o" many ways in wic te .G'T 7ramework integrates

te developer inter"ace% making coding simpler and more consistent.

4nlike 0ctiveF controls% Eindows 7orms controls ave semi-trusted access to a users

computer. Tis means tat binary or natively e$ecuting code can access some o" te

resources on te users system (suc as ,4 elements and limited "ile access) witout

being able to access or compromise oter resources. >ecause o" code access security%

many applications tat once needed to be installed on a users system can now be sa"ely

deployed troug te Eeb. Iour applications can implement te "eatures o" a local

application wile being deployed like a Eeb page.

- -


22/118


C6*NET

I$tro7uctio$

ACTI8E 9 DATA OBECTS*NET

ADO*NET Overvie3

0/3.G'T is an evolution o" te 0/3 data access model tat directly addresses

user re&uirements "or developing scalable applications. t was designed speci"ically "or

te web wit scalability% statelessness% and FM9 in mind.

0/3.G'T uses some 0/3 ob!ects% suc as te Co$$ectio$and Co""a$7ob!ects% and

also introduces new ob!ects. Oey new 0/3.G'T ob!ects include te DataSet%

DataRea7er% and DataA7a0ter.

Te important distinction between tis evolved stage o" 0/3.G'T and previous data

arcitectures is tat tere e$ists an ob!ect -- te DataSet-- tat is separate and distinct

"rom any data stores. >ecause o" tat% te DataSet"unctions as a standalone entity. Iou

can tink o" te /ataSet as an always disconnected recordset tat knows noting about

te source or destination o" te data it contains. nside a DataSet% muc like in a

database% tere are tables% columns% relationsips% constraints% views% and so "ort.

0 DataA7a0teris te ob!ect tat connects to te database to "ill te DataSet. Ten% it

connects back to te database to update te data tere% based on operations per"ormed

wile te DataSet eld te data. n te past% data processing as been primarily

- -


23/118


connection-based. Gow% in an e""ort to make multi-tiered apps more e""icient% data

processing is turning to a message-based approac tat revolves around cunks o"

in"ormation. 0t te center o" tis approac is te DataA7a0ter% wic provides a bridge

to retrieve and save data between a DataSetand its source data store. t accomplises

tis by means o" re&uests to te appropriate SK9 commands made against te data store.

Te FM9-based DataSetob!ect provides a consistent programming model tat works

wit all models o" data storageD "lat% relational% and ierarcical. t does tis by aving

no knowledge o" te source o" its data% and by representing te data tat it olds as

collections and data types. Go matter wat te source o" te data witin te DataSetis%

it is manipulated troug te same set o" standard 0s e$posed troug te DataSet

and its subordinate ob!ects.

Eile te DataSetas no knowledge o" te source o" its data% te managed provider as

detailed and speci"ic in"ormation. Te role o" te managed provider is to connect% "ill%

and persist te DataSetto and "rom data stores. Te 39' /> and SK9 Server .G'T

/ata roviders (System./ata.3le/b and System./ata.S&lClient) tat are part o" te .Get

7ramework provide "our basic ob!ectsD te Co""a$7% Co$$ectio$% DataRea7er and

DataA7a0ter. n te remaining sections o" tis document% well walk troug eac part

o" te DataSetand te 39' />SK9 Server .G'T /ata roviders e$plaining wat tey

are% and ow to program against tem.

Te "ollowing sections will introduce you to some ob!ects tat ave evolved% and some

tat are new. Tese ob!ects areD

Co$$ectio$s. 7or connection to and managing transactions against a database.

Co""a$7s. 7or issuing SK9 commands against a database.

- 5 -


24/118


DataRea7ers. 7or reading a "orward-only stream o" data records "rom a SK9

Server data source.

DataSets. 7or storing% remoting and programming against "lat data% FM9 data and

relational data.

DataA7a0ters. 7or pusing data into a DataSet% and reconciling data against a

database.

Een dealing wit connections to a database% tere are two di""erent optionsD SK9

Server .G'T /ata rovider (System./ata.S&lClient) and 39' /> .G'T /ata rovider

(System./ata.3le/b). n tese samples we will use te SK9 Server .G'T /ata rovider.

Tese are written to talk directly to Microso"t SK9 Server. Te 39' /> .G'T /ata

rovider is used to talk to any 39' /> provider (as it uses 39' /> underneat).

Co$$ectio$s

Connections are used to talk to databases% and are represented by provider-speci"ic

classes suc as S,LCo$$ectio$. Commands travel over connections and resultsets are

returned in te "orm o" streams wic can be read by a DataRea7erob!ect% or pused

into a DataSetob!ect.

Co""a$7s

Commands contain te in"ormation tat is submitted to a database% and are represented

by provider-speci"ic classes suc as S,LCo""a$7. 0 command can be a stored

procedure call% an 4/0T' statement% or a statement tat returns results. Iou can also

use input and output parameters% and return values as part o" your command synta$. Te

e$ample below sows ow to issue an GS'RT statement against te Nort13i$7

database.

- 8 -


25/118


DataRea7ers

Te DataRea7erob!ect is somewat synonymous wit a read-only"orward-only cursor

over data. Te DataRea7er 0 supports "lat as well as ierarcical data. 0

DataRea7er ob!ect is returned a"ter e$ecuting a command against a database. Te

"ormat o" te returned DataRea7erob!ect is di""erent "rom a recordset. 7or e$ample%

you migt use te DataRea7erto sow te results o" a searc list in a web page.

DataSets a$7 DataA7a0ters

DataSets

Te DataSet ob!ect is similar to te 0/3 Recor7setob!ect% but more power"ul% and

wit one oter important distinctionD te DataSetis always disconnected. Te DataSet

ob!ect represents a cace o" data% wit database-like structures suc as tables% columns%

relationsips% and constraints. 6owever% toug a DataSetcan and does beave muc

like a database% it is important to remember tat DataSetob!ects do not interact directly

wit databases% or oter source data. Tis allows te developer to work wit a

programming model tat is always consistent% regardless o" were te source data

resides. /ata coming "rom a database% an FM9 "ile% "rom code% or user input can all be

placed into DataSet ob!ects. Ten% as canges are made to te DataSet tey can be

tracked and veri"ied be"ore updating te source data. Te ;etC1a$5esmetod o" te

DataSetob!ect

actually creates a second DatSettat contains only te canges to te data. Tis DataSet

is ten used by a DataA7a0ter(or oter ob!ects) to update te original data source.

Te DataSet as many FM9 caracteristics% including te ability to produce and

consume FM9 data and FM9 scemas. FM9 scemas can be used to describe scemas

- * -


26/118


intercanged via EebServices. n "act% a DataSet wit a scema can actually be

compiled "or type sa"ety and statement completion.

DataA7a0ters

Te DataA7a0terob!ect works as a bridge between te DataSetand te source data.

4sing te provider-speci"ic S#/DataA7a0ter (along wit its associated S#/Co""a$7

and S#/Co$$ectio$) can increase overall per"ormance wen working wit a Microso"t

SK9 Server databases. 7or oter 39' />-supported databases% you would use te

O/eDbDataA7a0terob!ect and its associated O/eDbCo""a$7and O/eDbCo$$ectio$

ob!ects.

Te DataA7a0terob!ect uses commands to update te data source a"ter canges ave

been made to te DataSet. 4sing te Fi//metod o" te DataA7a0tercalls te S'9'CT

commandP using te U07ate metod calls te GS'RT% 4/0T' or /'9'T'

command "or eac canged row. Iou can e$plicitly set tese commands in order to

control te statements used at runtime to resolve canges% including te use o" stored

procedures. 7or ad-oc scenarios% a Co""a$7Bui/7erob!ect can generate tese at run-

time based upon a select statement. 6owever% tis run-time generation re&uires an e$tra

round-trip to te server in order to gater re&uired metadata% so e$plicitly providing te

GS'RT% 4/0T'% and /'9'T' commands at design time will result in better run-

time per"ormance.

. 0/3.G'T is te ne$t evolution o" 0/3 "or te .Get 7ramework.

. 0/3.G'T was created wit n-Tier% statelessness and FM9 in te "ore"ront. Two

new ob!ects% te DataSetand DataA7a0ter% are provided "or tese scenarios.

- + -


27/118


5. 0/3.G'T can be used to get data "rom a stream% or to store data in a cace "or

updates.

8. Tere is a lot more in"ormation about 0/3.G'T in te documentation.

*. Remember% you can e$ecute a command directly against te database in order to

do inserts% updates% and deletes. Iou dont need to "irst put data into a DataSetin

order to insert% update% or delete it.

+. 0lso% you can use a DataSetto bind to te data% move troug te data% and

navigate data relationsips

AS(*Net

Server A00/icatio$ Deve/o0"e$t

Server-side applications in te managed world are implemented troug runtime osts.

4nmanaged applications ost te common language runtime% wic allows your custom

managed code to control te beavior o" te server. Tis model provides you wit all te

"eatures o" te common language runtime and class library wile gaining te

per"ormance and scalability o" te ost server.

Te "ollowing illustration sows a basic network scema wit managed code running in

di""erent server environments. Servers suc as S and SK9 Server can per"orm standard

operations wile your application logic e$ecutes troug te managed code.

Server-si7e "a$a5e7 co7e

0S.G'T is te osting environment tat enables developers to use te .G'T

7ramework to target Eeb-based applications. 6owever% 0S.G'T is more tan !ust a

runtime ostP it is a complete arcitecture "or developing Eeb sites and nternet-

- 1 -


28/118


distributed ob!ects using managed code. >ot Eeb 7orms and FM9 Eeb services use

S and 0S.G'T as te publising mecanism "or applications% and bot ave a

collection o" supporting classes in te .G'T 7ramework.

FM9 Eeb services% an important evolution in Eeb-based tecnology% are distributed%

server-side application components similar to common Eeb sites. 6owever% unlike

Eeb-based applications% FM9 Eeb services components ave no 4 and are not

targeted "or browsers suc as nternet '$plorer and Getscape Gavigator. nstead% FM9

Eeb services consist o" reusable so"tware components designed to be consumed by

oter applications% suc as traditional client applications% Eeb-based applications% or

even oter FM9 Eeb services. 0s a result% FM9 Eeb services tecnology is rapidly

moving application development and deployment into te igly distributed

environment o" te nternet.

" you ave used earlier versions o" 0S tecnology% you will immediately notice te

improvements tat 0S.G'T and Eeb 7orms o""ers. 7or e$ample% you can develop Eeb

7orms pages in any language tat supports te .G'T 7ramework. n addition% your code

no longer needs to sare te same "ile wit your 6TT te$t (altoug it can continue to

do so i" you pre"er). Eeb 7orms pages e$ecute in native macine language because% like

any oter managed application% tey take "ull advantage o" te runtime. n contrast%

unmanaged 0S pages are always scripted and interpreted. 0S.G'T pages are "aster%

more "unctional% and easier to develop tan unmanaged 0S pages because tey interact

wit te runtime like any managed application.

Te .G'T 7ramework also provides a collection o" classes and tools to aid in

development and consumption o" FM9 Eeb services applications. FM9 Eeb services

are built on standards suc as S30 (a remote procedure-call protocol)% FM9 (an

- < -


29/118


e$tensible data "ormat)% and ES/9 (te Eeb Services /escription 9anguage). Te

.G'T 7ramework is built on tese standards to promote interoperability wit non-

Microso"t solutions.

7or e$ample% te Eeb Services /escription 9anguage tool included wit te .G'T

7ramework S/O can &uery an FM9 Eeb service publised on te Eeb% parse its

ES/9 description% and produce CQ or ;isual >asic source code tat your application

can use to become a client o" te FM9 Eeb service. Te source code can create classes

derived "rom classes in te class library tat andle all te underlying communication

using S30 and FM9 parsing. 0ltoug you can use te class library to consume FM9

Eeb services directly% te Eeb Services /escription 9anguage tool and te oter tools

contained in te S/O "acilitate your development e""orts wit te .G'T 7ramework.

" you develop and publis your own FM9 Eeb service% te .G'T 7ramework provides

a set o" classes tat con"orm to all te underlying communication standards% suc as

S30% ES/9% and FM9. 4sing tose classes enables you to "ocus on te logic o" your

service% witout concerning yoursel" wit te communications in"rastructure re&uired by

distributed so"tware development.

7inally% like Eeb 7orms pages in te managed environment% your FM9 Eeb service

will run wit te speed o" native macine language using te scalable communication o"

S.

Active Server (a5es*NET

0S.G'T is a programming "ramework built on te common language runtime

tat can be used on a server to build power"ul Eeb applications. 0S.G'T o""ers several

important advantages over previous Eeb development modelsD

- : -


30/118


E$1a$ce7 (eror"a$ce*0S.G'T is compiled common language runtime code

running on te server. 4nlike its interpreted predecessors% 0S.G'T can take

advantage o" early binding% !ust-in-time compilation% native optimi#ation% and

cacing services rigt out o" te bo$. Tis amounts to dramatically better

per"ormance be"ore you ever write a line o" code.

&or/7-C/ass Too/ Su00ort*Te 0S.G'T "ramework is complemented by a ric

toolbo$ and designer in te ;isual Studio integrated development environment.

EISEI, editing% drag-and-drop server controls% and automatic deployment are

!ust a "ew o" te "eatures tis power"ul tool provides.

(o3er a$7 F/e?ibi/it!*>ecause 0S.G'T is based on te common language

runtime% te power and "le$ibility o" tat entire plat"orm is available to Eeb

application developers. Te .G'T 7ramework class library% Messaging% and /ata

0ccess solutions are all seamlessly accessible "rom te Eeb. 0S.G'T is also

language-independent% so you can coose te language tat best applies to your

application or partition your application across many languages. 7urter% common

language runtime interoperability guarantees tat your e$isting investment in

C3M-based development is preserved wen migrating to 0S.G'T.

Si"0/icit!*0S.G'T makes it easy to per"orm common tasks% "rom simple "orm

submission and client autentication to deployment and site con"iguration. 7or

e$ample% te 0S.G'T page "ramework allows you to build user inter"aces tat

cleanly separate application logic "rom presentation code and to andle events in a

simple% ;isual >asic - like "orms processing model. 0dditionally% te common

language runtime simpli"ies development% wit managed code services suc as

automatic re"erence counting and garbage collection.

- 52 -


31/118


Ma$a5eabi/it!* 0S.G'T employs a te$t-based% ierarcical con"iguration

system% wic simpli"ies applying settings to your server environment and Eeb

applications. >ecause con"iguration in"ormation is stored as plain te$t% new settings

may be applied witout te aid o" local administration tools. Tis #ero local

administration pilosopy e$tends to deploying 0S.G'T 7ramework

applications as well. 0n 0S.G'T 7ramework application is deployed to a server

simply by copying te necessary "iles to te server. Go server restart is re&uired%

even to deploy or replace running compiled code.

Sca/abi/it! a$7 Avai/abi/it!* 0S.G'T as been designed wit scalability in

mind% wit "eatures speci"ically tailored to improve per"ormance in clustered and

multiprocessor environments. 7urter% processes are closely monitored and

managed by te 0S.G'T runtime% so tat i" one misbeaves (leaks% deadlocks)% a

new process can be created in its place% wic elps keep your application

constantly available to andle re&uests.

Custo"i@abi/it! a$7 E?te$sibi/it!* 0S.G'T delivers a well-"actored

arcitecture tat allows developers to plug-in teir code at te appropriate level.

n "act% it is possible to e$tend or replace any subcomponent o" te 0S.G'T

runtime wit your own custom-written component. mplementing custom

autentication or state services as never been easier.

Securit!*Eit built in Eindows autentication and per-application con"iguration%

you can be assured tat your applications are secure.

La$5ua5e Su00ort

Te Microso"t .G'T lat"orm currently o""ers built-in support "or tree

languagesD CQ% ;isual >asic% and JScript.

- 5 -


32/118


- 5 -


33/118


&1at is AS(*NET &eb For"s

Te 0S.G'T Eeb 7orms page "ramework is a scalable common language

runtime programming model tat can be used on te server to dynamically generate Eeb

pages.

ntended as a logical evolution o" 0S (0S.G'T provides synta$ compatibility

wit e$isting pages)% te 0S.G'T Eeb 7orms "ramework as been speci"ically

designed to address a number o" key de"iciencies in te previous model. n particular% it

providesD

Te ability to create and use reusable 4 controls tat can encapsulate common

"unctionality and tus reduce te amount o" code tat a page developer as to

write.

Te ability "or developers to cleanly structure teir page logic in an orderly "asion

(not spagetti code).

Te ability "or development tools to provide strong EISEI, design support "or

pages (e$isting 0S code is opa&ue to tools).

0S.G'T Eeb 7orms pages are te$t "iles wit an .asp$ "ile name e$tension.

Tey can be deployed trougout an S virtual root directory tree. Een a browser

client re&uests .asp$ resources% te 0S.G'T runtime parses and compiles te target "ile

into a .G'T 7ramework class. Tis class can ten be used to dynamically process

incoming re&uests. (Gote tat te .asp$ "ile is compiled only te "irst time it is accessedP

te compiled type instance is ten reused across multiple re&uests).

0n 0S.G'T page can be created simply by taking an e$isting 6TM9 "ile and

canging its "ile name e$tension to .asp$ (no modi"ication o" code is re&uired). 7or

- 55 -


34/118


e$ample% te "ollowing sample demonstrates a simple 6TM9 page tat collects a users

name and category pre"erence and ten per"orms a "orm postback to te originating page

wen a button is clicked.

0S.G'T provides synta$ compatibility wit e$isting 0S pages. Tis includes

support "or U code render blocks tat can be intermi$ed wit 6TM9 content

witin an .asp$ "ile. Tese code blocks e$ecute in a top-down manner at page render

time.

Co7e-Be1i$7 &eb For"s

0S.G'T supports two metods o" autoring dynamic pages. Te "irst is te

metod sown in te preceding samples% were te page code is pysically declared

witin te originating .asp$ "ile. 0n alternative approac--known as te code-beind

metod--enables te page code to be more cleanly separated "rom te 6TM9 content

into an entirely separate "ile.

I$tro7uctio$ to AS(*NET Server Co$tro/s

n addition to (or instead o") using U code blocks to program dynamic

content% 0S.G'T page developers can use 0S.G'T server controls to program Eeb

pages. Server controls are declared witin an .asp$ "ile using custom tags or intrinsic

6TM9 tags tat contain a ru$atserver attribute value. ntrinsic 6TM9 tags are

andled by one o" te controls in te S!ste"*&eb*UI*%t"/Co$tro/snamespace. 0ny

tag tat doesnt e$plicitly map to one o" te controls is assigned te type o"

S!ste"*&eb*UI*%t"/Co$tro/s*%t"/;e$ericCo$tro/.

- 58 -


35/118


Server controls automatically maintain any client-entered values between round

trips to te server. Tis control state is not stored on te server (it is instead stored witin

an i$0ut t!0e1i77e$ "orm "ield tat is round-tripped between re&uests). Gote

also tat no client-side script is re&uired.

n addition to supporting standard 6TM9 input controls% 0S.G'T enables

developers to utili#e ricer custom controls on teir pages. 7or e$ample% te "ollowing

sample demonstrates ow te as0:a7rotator control can be used to dynamically

display rotating ads on a page.

. 0S.G'T Eeb 7orms provide an easy and power"ul way to build

dynamic Eeb 4.

. 0S.G'T Eeb 7orms pages can target any browser client (tere are no

script library or cookie re&uirements).

5. 0S.G'T Eeb 7orms pages provide synta$ compatibility wit e$isting

0S pages.

8. 0S.G'T server controls provide an easy way to encapsulate common

"unctionality.

*. 0S.G'T sips wit 8* built-in server controls. /evelopers can also use

controls built by tird parties.

+. 0S.G'T server controls can automatically pro!ect bot uplevel and

down level 6TM9.

1. 0S.G'T templates provide an easy way to customi#e te look and "eel

o" list server controls.


36/118


- 5+ -


37/118


S,L SER8ER

DATABASE

0 database management% or />MS% gives te user access to teir data and elps

tem trans"orm te data into in"ormation. Suc database management systems include

d>ase% parado$% MS% S&l Server and SK9 Server. Tese systems allow users to create%

update and e$tract in"ormation "rom teir database.

0 database is a structured collection o" data. /ata re"ers to te caracteristics o"

people% tings and events. SK9 Server stores eac data item in its own "ields. n SK9

Server% te "ields relating to a particular person% ting or event are bundled togeter to

"orm a single complete unit o" data% called a record (it can also be re"erred to as raw or

an occurrence). 'ac record is made up o" a number o" "ields. Go two "ields in a record

can ave te same "ield name.

/uring an SK9 Server /atabase design pro!ect% te analysis o" your business

needs identi"ies all te "ields or attributes o" interest. " your business needs cange over

time% you de"ine any additional "ields or cange te de"inition o" e$isting "ields.

S,L Server Tab/es

SK9 Server stores records relating to eac oter in a table. /i""erent tables are

created "or te various groups o" in"ormation. Related tables are grouped togeter to

"orm a database.

(ri"ar! e!

'very table in SK9 Server as a "ield or a combination o" "ields tat uni&uely

identi"ies eac record in te table. Te 4ni&ue identi"ier is called te rimary Oey% or

- 51 -


38/118


simply te Oey. Te primary key provides te means to distinguis one record "rom all

oter in a table. t allows te user and te database system to identi"y% locate and re"er to

one particular record in te database.

Re/atio$a/ Database

Sometimes all te in"ormation o" interest to a business operation can be stored in

one table. SK9 Server makes it very easy to link te data in multiple tables. Matcing

an employee to te department in wic tey work is one e$ample. Tis is wat makes

SK9 Server a relational database management system% or R/>MS. t stores data in two

or more tables and enables you to de"ine relationsips between te table and enables you

to de"ine relationsips between te tables.

Forei5$ e!

Een a "ield is one table matces te primary key o" anoter "ield is re"erred to

as a "oreign key. 0 "oreign key is a "ield or a group o" "ields in one table wose values

matc tose o" te primary key o" anoter table.

Reere$tia/ I$te5rit!

Got only does SK9 Server allow you to link multiple tables% it also maintains

consistency between tem. 'nsuring tat te data among related tables is correctly

matced is re"erred to as maintaining re"erential integrity.

- 5< -


39/118


Data Abstractio$

0 ma!or purpose o" a database system is to provide users wit an abstract view o"

te data. Tis system ides certain details o" ow te data is stored and maintained.

/ata abstraction is divided into tree levels.

(1!sica/ /eve/D Tis is te lowest level o" abstraction at wic one describes ow te

data are actually stored.

Co$ce0tua/ Leve/D 0t tis level o" database abstraction all te attributed and wat data

are actually stored is described and entries and relationsip among tem.

8ie3 /eve/D Tis is te igest level o" abstraction at wic one describes only part o"

te database.

A7va$ta5es o RDBMS

Redundancy can be avoided

nconsistency can be eliminated

/ata can be Sared

Standards can be en"orced

Security restrictions ca be applied

ntegrity can be maintained

Con"licting re&uirements can be balanced

/ata independence can be acieved.

Disa7va$ta5es o DBMS

0 signi"icant disadvantage o" te />MS system is cost. n addition to te cost o"

purcasing o" developing te so"tware% te ardware as to be upgraded to allow "or te

e$tensive programs and te workspace re&uired "or teir e$ecution and storage. Eile

- 5: -


40/118


centrali#ation reduces duplication% te lack o" duplication re&uires tat te database be

ade&uately backed up so tat in case o" "ailure te data can be recovered.

FEATURES OF S,L SER8ER MS tat delivers unmatced

per"ormance% continuous operation and support "or every database.

SK9 S'R;'R R/>MS is ig per"ormance "ault tolerant />MS wic is specially

designed "or online transactions processing and "or andling large database application.

SK9 S'R;'R wit transactions processing option o""ers two "eatures wic contribute

to very ig level o" transaction processing trougput% wic are

Te row level lock manager

E$ter0rise 3i7e Data S1ari$5

Te unrivaled portability and connectivity o" te SK9 S'R;'R />MS enables

all te systems in te organi#ation to be linked into a singular% integrated computing

resource.

(ortabi/it!

SK9 S'R;'R is "ully portable to more tan


41/118


O0e$ S!ste"s

SK9 S'R;'R o""ers a leading implementation o" industry Bstandard SK9. SK9

ServerAs open arcitecture integrates SK9 S'R;'R and non BSK9 S'R;'R />MS

wit industries most compreensive collection o" tools% application% and tird party

so"tware products SK9 ServerAs 3pen arcitecture provides transparent access to data

"rom oter relational database and even non-relational database.

Distribute7 Data S1ari$5

SK9 ServerAs networking and distributed database capabilities to access data

stored on remote server wit te same ease as i" te in"ormation was stored on a single

local computer. 0 single SK9 statement can access data at multiple sites. Iou can store

data were system re&uirements suc as per"ormance% security or availability dictate.

U$"atc1e7 (eror"a$ce

Te most advanced arcitecture in te industry allows te SK9 S'R;'R />MS

to deliver unmatced per"ormance.

So01isticate7 Co$curre$c! Co$tro/

Real Eorld applications demand access to critical data. Eit most database

Systems application becomes ?contention bound@ B wic per"ormance is limited not by

te C4 power or by disk 3% but user waiting on one anoter "or data access . SK9

Server employs "ull% unrestricted row-level locking and contention "ree &ueries to

minimi#e and in many cases entirely eliminates contention wait times.

No I=O Bott/e$ec4s

SK9 ServerAs "ast commit groups commit and de"erred write tecnologies

dramatically reduce disk 3 bottlenecks. Eile some database write wole data block to

disk at commit time% SK9 Server commits transactions wit at most se&uential log "ile

on disk at commit time% 3n ig trougput systems% one se&uential writes typically

- 8 -


42/118


group commit multiple transactions. /ata read by te transaction remains as sared

memory so tat oter transactions may access tat data witout reading it again "rom

disk. Since "ast commits write all data necessary to te recovery to te log "ile% modi"ied

blocks are written back to te database independently o" te transaction commit% wen

written "rom memory to disk.

2*)* About UML:

U$iie7 Mo7e/i$5 La$5ua5e:

Te 4ni"ied Modeling 9anguage allows te so"tware engineer to e$press an analysis

model using te modeling notation tat is governed by a set o" syntactic semantic and

pragmatic rules.

0 4M9 system is represented using "ive di""erent views tat describe te system "rom

distinctly di""erent perspective. 'ac view is de"ined by a set o" diagram% wic is as

"ollows.

4ser Model ;iew

i. Tis view represents te system "rom te usersA perspective.

ii. Te analysis representation describes a usage scenario "rom te

end-users perspective.

Structural model view

i. n tis model te data and "unctionality are arrived "rom inside te

system.

ii. Tis model view models te static structures.

>eavioral Model ;iew

t represents te dynamic o" beavioral as parts o" te system% depicting

te interactions o" collection between various structural elements

described in te user model and structural model view.

- 8 -


43/118


mplementation Model ;iew

n tis te structural and beavioral as parts o" te system are represented

as tey are to be built.

'nvironmental Model ;iew

n tis te structural and beavioral aspects o" te environment in wic

te system is to be implemented are represented.

4M9 is speci"ically constructed troug two di""erent domains tey areD

4M9 0nalysis modeling% tis "ocuses on te user model and structural model

views o" te system.

4M9 design modeling% wic "ocuses on te beavioral modeling%

implementation modeling and environmental model views.

4se case /iagrams represent te "unctionality o" te system "rom a userAs point o" view.

4se cases are used during re&uirements elicitation and analysis to represent te

"unctionality o" te system. 4se cases "ocus on te beavior o" te system "rom e$ternal

point o" view.

0ctors are e$ternal entities tat interact wit te system. '$amples o" actors include

users like administrator% bank customer =etc.% or anoter system like central database.

- 85 -


44/118


DATA FLO& DIA;RAMS:

T1ere are t1ree t!0es o DFDGs t1e! are+* Co$te?t Leve/ DFD

* To0 Leve/ DFD a$7

Co$te?t Leve/ DFD:

n te Conte$t 9evel te wole system is sown as a single process.

Go data stores are sown.

nputs to te overall system are sown togeter wit data sources (as '$ternalentities).

3utputs "rom te overall system are sown togeter wit teir destinations

(as '$ternal entities).

- 88 -


45/118


To0 Leve/ DFD:

Te Top 9evel /7/ gives te overview o" te wole system identi"ying te ma!or

system processes and data "low. Tis level "ocuses on te single process tat is drawn in

te conte$t diagram by VWooming inA on its contents and illustrates wat it does in more

detail.

- 8* -


46/118


Detailed Level DFD:

n /etailed /.7./s te main process is divided into sub processes and we try to "ind out

te "low "rom one process to anoter process. Ee "ind te interaction among '$ternal

entities% processes% sub processes and database.

- 8+ -


47/118


UML Dia5ra"s

USE CASE DIA;RAM

0 use case diagram is a diagram tat sows a set o" use cases and actors and

relationsips.

Co$te$ts

4se case commonly contain

4se cases

0ctors

/ependency% generali#ation and association relationsips

- 81 -


48/118


Over a// Use Case

Administrator

IT Non-IT

Validation

Login

Online Test

Requirement

Shortlist

Interview

Result

o! See"er

Recruiter

Resume

#R$

- 8< -


49/118


A7"i$istrator Use Case

Administrator

Login

%reate Recruiter

%reate o! See"er

Resume

Requirement

Shortlist

Online Test

Interview

Result

Logout

&ermission

#R$

- 8: -


50/118


Recruiter Use Case

IT Non-IT

Register

Login

Sends Requirements

Shortlist

Interview

Result

Logout

Recruiter

Resume

- *2 -


51/118


ob See4er Use Case

Register

Login

Interview

Result

Logout

Online Testo! See"er

Resume

- * -


52/118


C/ass Dia5ra"

o! See"ers

code ' string

name ' string

do( ' date

t)*e ' stringtas" ' string

email ' string

clear+,

view+,

close+,

Registration

ITs Non-ITs

Recruiters

R.name ' string

R.id ' string

t) *e ' string

/RL ' string

email ' string

add ' stringdate ' string

geto*enings+,

getresults+,

create+,

u*date+,

delete+,

close+,

view+,

ITsNon-ITs

Login

/sername ' string

*assword ' string

change*assword ' v oid

save+,

cancel+,

close+,

validation+,

#R$ 0anager

name ' string

t) *e ' string

*ermission ' string

create+,

getid+,

getresult+,

getshortlist+,

getresume+,

u*date+,

delete+,

close+,

v iew+,

v alidation+,

Admin

OnlineTest

id ' stringt)*e ' string

testdate ' date

testtime ' time

getid+,

getresult+,

create+,

u*date+,

delete+,

close+,

view+,

1221

122n122n 1221

122n

1221

Shortlist

code ' string

com*an)name ' string

t)*e ' string

s"ill ' string

result ' string

date ' date

getid+,

getresult+,

getlist+,

create+,u*date+,

delete+,

close+,

view+,

122n

122n

Resume

o!id ' string

t)*e ' string

name ' string

do! ' date

quali3ication ' string

s"ill ' string

e4*erience ' num!er

create+,

u*date+,

delete+,

close+,

view+,

122n

1221122n

122n

122n

1221

Interview

I$ ' string

com*an)name ' string

interviewdate ' date

address ' string

(o!id ' s tring

*lace ' string

create+,getresume+,

u*date+,

delete+,

close+,

v iew+,

Non-ITsITs

122n1221

122n

1221

122n

122n

1221

1221

1221122n

1221

122n

1221

122n

- * -


53/118


ACTI8ITY DIA;RAM:

0n activity diagram sows te "low "rom activity to activity. 0n activity is an ongoing non-

atomic e$ecution witin a state macine.

0ctivities ultimately result in some action% wic is made up o" e$ecutable atomic

computations tat result in a cange in state o" te system or te return o" a value.

0ctivity diagrams commonly contain

0ctivity states and action states

Transitions

3b!ects

9ike all oter diagrams% activity diagrams may contain notes and

constrains.

Lo5i$ (rocess

&roviding

%redentials

Validation

Retr)

Services

- *5 -


54/118


Re5istratio$ (rocess

&rovidinge4amination

admin validation

Invalidate

details

&rovide

%redentials

A7"i$istrator (rocess

Login

&ermissions

Recruitero!see"er Online Test Results

Logout

Shortlist Interview

validation

%reate7/*d

ate7$elete

#R$0anager7Administrator

View

Resume Requireme

nts

- *8 -


55/118


Recruiter (rocess

Login

validation

%reate7/*d

ate7$elete

View

Requireme

nts

Interview Resume Shortlist Results

Logout

- ** -


56/118


ob See4er (rocess

Login

validation

%reate7/*d

ate7$elete

View

Resume Online Test Results Interview

Logout

SE,UENCE DIA;RAM

0n interaction diagram sows an interaction% consisting o" a set o" ob!ects and

teir relationsips% including te messages tat may be dispatced among tem.

0 se&uence diagram is an interaction diagram tat empasi#es te time ordering

o" messages.

,rapically% a se&uence diagram is a table tat sows ob!ects arranged along $-

a$is and messages% ordered in increasing time% along te y-a$is.

- *+ -


57/118


Co$te$ts

Se&uence diagrams commonly contain te "ollowingD

3b!ects 9inks Messages

9ike all oter diagrams% se&uence diagrams may contain notes and constrains.

A7"i$istrator Se#ue$ce

' #R$Login &ermission Recruiter o! See"er Resume Requirement Online Test Shortlist InterviewResult

1' Login Request+,

res*onse+,valid+,

8'create+,9' create+,

:'create+,

;' view+,

' cr eate7view+,

res*onse+,

=' create+,

res*onse+,

' create+,

res*onse+,

?' create according to the result+,

res*onse+,

1@' create+,

res*onse+,

- *1 -


58/118


Recruiter Se#ue$ce

' Recruiter Register Login Requirement InterviewResumeResultShortlist

1' ill the 3orm

8' su!mit+,ver3ication+,

con3irmation

9' login request+,

re*onse+,

Valid+,

:' sends+,

res*onse+,

;' view+,

'view+,=' view+,

select (o!see"er res*onse+,

' send+,

res*onse+,

- *< -


59/118


ob See4er Se#ue$ce

' o! See"erRegister Login Resume Online Test Result Interview

1' ill u* the details

8' su!mit+,ver3ication+,

con3irmation

9' generate resume+,

res*onse+,

:' login request+,

validation+,

res*onse+,

;' view+,

' write+,

res*onse+,

=' view+,

res*onse+,

' view+,valid+,

res*onse+,

?' attend+,

res*onse+,

COLLABORATION DIA;RAM

- Collaboration is a society o" classes% inter"aces% and oter elements tat work

togeter to provide some cooperative beavior tatAs bigger tan te sum o" all its parts.

- Collaboration is also te speci"ication o" ow an element% suc as a classi"ier or an

operation% is reali#ed by a set o" classi"iers and associations playing speci"ic roles used in

a speci"ic way

- *: -


60/118


Co$te$ts

Collaboration diagrams commonly contain te "ollowingD

3b!ects

9inks

Messages

9ike all oter diagrams% se&uence diagrams may contain notes and constrains.

A7"i$istrator Co//aboratio$

' #R$

Login

&ermissio

n

Recruiter

o!See"er

ResumeRequireme

nt

Online

Test

Shortlist

Interview

Result

8' valid+,

1' 1' Login Request+,

9' res*onse+,

:' 8'create+,

;' 9' create+,

' ' create+,

19' res*onse+,

1


61/118


Recruiter Co//aboratio$

' Recruiter

Register

Login

Requireme

nt

Interview

Resume

Shortlist

Result

9' ver3ication+,

' Valid+,

1' 1' ill the 3orm8' 8' su!mit+,

:' con3irmation

;' 9' login request+,

=' re*onse+,

' :' sends+,?' res*onse+,

1@' ;' view+,

1:' ' send+,

1;' res*onse+,

19' select (o!see"er res*onse+,

11' 'view+,

18' =' view+,

- + -


62/118


ob See4er Co//aboratio$

' o! See"er

RegisterLogin

Resume

Online

Test Result

Interview

9' ver3ication+,>' validation+,

1' ?' attend+,

1=' res*onse+,1?' res*onse+,

;' 9' generate resume+,


63/118


64/118


/S6R

Ce!

Browser

ServletsA**lication

A**lication Server

8S6

Server

$ata!ase Server

0)SDL Server

- +8 -


65/118


ER-Dia5ra"

Inter.Scedule

0ail.Id' VAR%#AR+,

rom' VAR%#AR+:;,

ToChom' VAR%#AR+:;,

Su!(ect' VAR%#AR+:;,

Bod)' VAR%#AR+:;,

/ser.Regestration

/ser.Id' INT6E6R

/ser.Name' VAR%#AR+:;,

&wd' VAR%#AR+:;,

Se4' VAR%#AR+:;,

#omeNum!er' INT6E6R

0o!ile' INT6E6R

60ail' VAR%#AR+:;,

&&honeNum!er' INT6E6R

%#ouseNum!er' INT6E6R

%StreetName' VAR%#AR+:;,

%%it)' VAR%#AR+:;,

%State' VAR%#AR+:;,

%ountr)' VAR%#AR+:;,

%&inNum!er' INT6E6R

ouseNum!er' VAR%#AR+:;,

&StreetName' VAR%#AR+:;,

&%it)' VAR%#AR+:;,

&State' VAR%#AR+:;,

&%ountr)' VAR%#AR+:;,

&&inNum!er' INT6E6R

Duali3ication' VAR%#AR+:;,

o!.$etails

o!.%ode' INT6E6R

o!.Name' VAR%#AR+:;,


Required.S"ills' VAR%#AR+:;,

Required.64*erience' VAR%#AR+:;,

Res*onsi!ilities' VAR%#AR+:;,

Vacancies' VAR%#AR+:;,

%reated.On' VAR%#AR+:;,

%reated.B)' VAR%#AR+:;,

Login.$etails

/ser.Id' INT6E6R

/ser.Name'' VAR%#AR+:;,

&assword' VAR%#AR+:;,

Role'' VAR%#AR+:;,

&hoto./*load

/ser.Id' INT6E6R

&hoto.Id' VAR%#AR+:;,

&hoto.Name' LONE BINAR5

Recruiter.$etails

/ser.Id' INT6E6R

/ser.Name' VAR%#AR+:;,

&assword' VAR%#AR+:;,

Se4' VAR%#AR+:;,

#ouse.Num!er' VAR%#AR+:;,

0o!ile' VAR%#AR+:;,

60ail' VAR%#AR+:;,

&ass*ort.Num!er' VAR%#AR+:;,

%#ouse.Num!er' VAR%#AR+:;,

%Street.Name' VAR%#AR+:;,

%%it)' VAR%#AR+:;,

%State' VAR%#AR+:;,

%ountr)' VAR%#AR+:;,

%&in.Num!er' VAR%#AR+:;,ouse.Num!er' VAR%#AR+:;,

&Street.Name' VAR%#AR+:;,

&%it)' VAR%#AR+:;,

&STate' VAR%#AR+:;,

&%ountr)' VAR%#AR+:;,

&&in.Num!er' VAR%#AR+:;,


Duestion.$etails

Duestion.Num!er' INT6E6R

Duestion' VAR%#AR+1;@,

Duestion.O*tion1' VAR%#AR+1@@,



Duestion.O*tion:'' VAR%#AR+1@@,

Answer' VAR%#AR+:;,

- +* -


66/118


- ++ -


67/118


ob Detai/s

- +1 -


68/118


(rovi7er Detai/s

- +< -


69/118


,uestio$ Detai/s

Resu"e Detai/s

- +: -


70/118


- 12 -


71/118


See4er Re5istratio$

- 1 -


72/118


- 1 -


73/118


- 15 -


74/118


ob See4er Lo5i$ (a5e

- 18 -


75/118


ob See4er Re5istratio$ (a5e

- 1* -


76/118


ob See4er %o"e (a5e:

- 1+ -


77/118


ob Searc1:

- 11 -


78/118


C/ic4 A00/! To Sub"it*

- 1< -


79/118


8ie3 A00/ie7 obs:

- 1: -


80/118


E7it (roi/e

-


81/118


C1a$5e 0ass3or7

-


82/118


Resu"e U0/oa7

-


83/118


O$/i$e Test For A00/ie7 Ca$7i7ates O$/!

-


84/118


-


85/118


Lo5out

-


86/118


Recruiter Re5istratio$

-


87/118


Recruiter %o"e (a5e:

-


88/118


A77i$5 Ne3 ob

-


89/118


E7it A ob:

-


90/118


8ie3 List O obs:

- :2 -


91/118


A77 a ,uestio$ or O$/i$e Test:

- : -


92/118


E7it A ,uestio$:

- : -


93/118


8ie3 A// ,uestio$s

- :5 -


94/118


De/ete a ,uestio$

- :8 -


95/118


C1a$5e (ass3or7

- :* -


96/118


E7it (roi/e

- :+ -


97/118


C1a$5e 0ass3or7

- :1 -


98/118


A7"i$ %o"e (a5e

- :< -


99/118


Recruiter List

- :: -


100/118


See4ers List

- 22 -


101/118


Se/ecte7 Ca$7i7ates List:

- 2 -


102/118


Lo5out

- 2 -


103/118


- 25 -


104/118


H* Testi$5

Testing is te process o" detecting errors. Testing per"orms a very critical role "or

&uality assurance and "or ensuring te reliability o" so"tware. Te results o" testing are

used later on during maintenance also.

(s!c1o/o5! o Testi$5

Te aim o" testing is o"ten to demonstrate tat a program works by sowing tat

it as no errors. Te basic purpose o" testing pase is to detect te errors tat may be

present in te program. 6ence one sould not start testing wit te intent o" sowing tat

a program works% but te intent sould be to sow tat a program doesnAt work. Testing

is te process o" e$ecuting a program wit te intent o" "inding errors.

Testi$5 ObjectivesD

Te main ob!ective o" testing is to uncover a ost o" errors% systematically and wit

minimum e""ort and time. Stating "ormally% we can say%

Testing is a process o" e$ecuting a program wit te intent o" "inding an error.

0 success"ul test is one tat uncovers an as yet undiscovered error.

0 good test case is one tat as a ig probability o" "inding error% i" it e$ists.

Te tests are inade&uate to detect possibly present errors.

Te so"tware more or less con"irms to te &uality and reliable standards.

- 28 -


105/118


LE8ELS OF TESTIN;

n order to uncover te errors present in di""erent pases we ave te concept o" levels o"

testing. Te basic levels o" testing are

Client Geeds 0cceptance Testing

Re&uirements System Testing

/esign ntegration Testing

Code 4nit Testing

0 series o" testing is done "or te proposed system be"ore te system is ready

"or te user acceptance testing.

Te steps involved in Testing are.

H*+ U$it Testi$5:

4nit testing "ocuses veri"ication e""orts on te smallest unit o" te so"tware

design te module*Tis is also known as ?Module Testing@ *Te modules are tested

separately*Tis testing carried out during programming stage itsel"*n tis testing eac

module is "ound to be working satis"actorily as regards to te e$pected output "rom te

module*

H* I$te5ratio$ Testi$5:

/ata can be grossed across an inter"aceJone module can ave adverse e""orts on

anoter*ntegration testing is systematic testing "or construction te program structure

- 2* -


106/118


wile at te same time conducting tests to uncover errors associated wit in te inter"ace.

Te ob!ective is to take unit tested modules and build a program structure * 0ll te

modules are combined and tested as a wole* 6ere correction is di""icult because te

isolation o" cause is complicate by te vast e$pense o" te entire program. Tus in te

integration testing stop all te errors uncovered are corrected "or te te$t testing steps*

H*) S!ste" testi$5:

System testing is te stage o" implementation tat is aimed at ensuring tat te

system works accurately and e""iciently "or live operation commences. Testing is vital to

te success o" te system. System testing makes a logical assumption tat i" all te parts

o" te system are correct% ten goal will be success"ully acieved.

T1e our "ajor s!ste" testi$5 are

i.Recovery Testing

ii. Security Testing

iii.Stress Testing

iv. er"ormance Testing

RECO8ERY TESTIN;

Recovery testing is a system test tat "orces te so"tware to "ail in a variety o"

ways and veri"ies tat recovery is properly per"ormed. " recovery is automatic% re-

initiali#ation% ceckpoint mecanisms% data recovery% and restart are eac evaluated "or

correctness. " recovery re&uires uman intervention% te mean time to repair is

evaluated to determine weter it is witin acceptable limits*

- 2+ -


107/118


SECURITY TESTIN;

Security testing attempts to veri"y tat protection mecanisms built into a system

will% in "act% protect it "rom improper penetration. /uring security testing% te tester

plays te role o" te individual wo desire to penetrate te system. ,iven enoug time

and resources% good security testing will ultimately penetrate a system. Te role o" te

system designer is to make penetration cost more tan te value o" te in"ormation tat

will be obtained.

STRESS TESTIN;

/uring earlier so"tware testing steps% wite bo$ and black bo$ tecni&ues

resulted in a toroug evaluation o" normal program "unctions and per"ormance. Stress

tests are designed to con"ront programs wit abnormal situations*

(ERFORMANCE TESTIN;

7or real-time and embedded systems% so"tware tat provides re&uired "unction

but does not con"irm to per"ormance re&uirements is unacceptable. er"ormance testing

is designed to test te run-time per"ormance o" so"tware witin te conte$t o" an

integrated system. er"ormance testing occurs trougout all steps in te testing

process.

er"ormance tests are sometimes coupled wit stress testing and o"ten re&uire

bot ardware and so"tware instrumentation. Tat is% it is o"ten necessary to measure

resource utili#ation. >y instrumenting a system% te tester can uncover situations tat

lead to degradation and possible system "ailure.

H*. 8a/i7atio$ Testi$5:

- 21 -


108/118


0t te conclusion o" integration testing so"tware is completely assembled as a

package% inter"acing errors ave been uncovered and corrected and a "inal series o"

so"tware tests begins validation test begins* ;alidation test can be de"ined in many

ways* >ut te simple de"inition is tat validation succeeds wen te so"tware "unction in

a manner tat can reasonably e$pected by te customer. 0"ter validation test as been

conducted one o" two possible conditions e$ists.

3ne is te "unction or per"ormance caracteristics con"irm to speci"ications

and are accepted and te oter is deviation "rom speci"ication is uncovered and a

de"iciency list is created. roposed system under consideration as been tested by using

validation testing and "ound to be working satis"actorily.

H*2 Out0ut Testi$5:

0"ter per"orming validation testing% te ne$t step is output testing o" te proposed

system since no system could be use"ul i" it does not produce te re&uired output in te

speci"ied "ormat. 0sking te users about te "ormat re&uired by tem tests te outputs

generated by te system under consideration. 6ere te output "ormat is considered in

two ways% one is on te screen and oter is te printed "ormat. Te output "ormat on te

screen is "ound to be correct as te "ormat was designed in te system designed pase

according to te user needs. 7or te ard copy also te output comes as te speci"ied

re&uirements by te users. 6ence output testing does not result any corrections in te

system.

H*K User Acce0ta$ce Testi$5:

4ser acceptance o" a system is te key "actor o" te success o" any system.

Te system under study is tested "or te user acceptance by constantly keeping in touc

wit te prospective system users at te time o" developing and making canges

werever re&uired.

- 2< -


109/118


Test Data:

Taking various kinds o" test data does te above testing. reparation o" test

data plays a vital role in te system testing a"ter preparing te test data te system under

study is tested using te test data. Eile testing te system by using te test data errors

are again uncovered and corrected by using above testing steps and corrections are also

noted "rom te "uture use.

Testi$5:

Te testing done ere was System TestingBcecking weter te user

re&uirements were satis"ied. Te code "or te new system as been written completely

using JS as te coding language% 6TM9 as te inter"ace "or "ront-end designing and

Java Script "or validating te client-side applications. Te new system as been tested

well wit te elp o" te users and all te applications ave been veri"ied "rom every

nook and corner o" te user.

0ltoug some applications were "ound to be erroneous tese applications ave

been corrected be"ore being implemented. Te "low o" te "orms as been "ound to be

very muc in accordance wit te actual "low o" data.

- 2: -


110/118


- 2 -


111/118


usingSystem;usingSystem.Data;usingSystem.Configuration;usingSystem.Collections;usingSystem.Web;usingSystem.Web.Security;usingSystem.Web.UI;usingSystem.Web.UI.WebControls;usingSystem.Web.UI.WebControls.WebParts;usingSystem.Web.UI.HtmlControls;

usingSystem.Data.SqlClient;usingSystem.Windows.Forms;

ublicartialclass!obPro"ider#$dd!ob% System.Web.UI.Page& SqlConnection con; SqlCommand cmd;

rotected"oidPage#'oad(ob)ectsender* +"ent$rgse, & con - newSqlConnection(Configurationanager.ConnectionStrings/0crms01.ConnectionString,; Calendar2.3isible - false; if(4IsPost5ac6,

&

'oadPro)ectId(,; 7 Createdby.8e9t - Session/0CurrentUser01.8oString(,; 7 ri"ate"oid'oadPro)ectId(, & cmd - newSqlCommand(0select ma9(!obCode, from !ob#Details0* con,; con.:en(,; strings - cmd.+9ecuteScalar(,.8oString(,; if(s -- 00, &

!obCode.8e9t - 0!ob20; 7 else & strings2 - s.Substring(*


112/118


& cmd - newSqlCommand(0insert into !:b#Details "alues(?0> !obCode.8e9t > 0?*?0> [email protected] > 0?*?0> Aualifi.8e9t > 0?*?0> BS6ills.8e9t > 0?*?0> B+9.8e9t > 0?*?0>Besoons.8e9t > 0?*?0> 3acancies.8e9t > 0?*?0> Createdon.8e9t > 0?*?0> Createdby.8e9t> 0?*?0> DroDown'ist2.SelectedItem.8e9t > 0?,0* con,; con.:en(,;

cmd.+9ecute@onAuery(,; con.Close(,;

essage5o9.Sow(0Successfully added0* 0Success essage0*essage5o95uttons.:* essage5o9Icon.Information,;

7 catc(+9cetione2, & essage5o9.Sow(e2.essage* 0+rror essage0* essage5o95uttons.:*essage5o9Icon.Information,; 7 7

rotected"oidImage5utton2#Clic6(ob)ectsender* ImageClic6+"ent$rgs e, & Calendar2.3isible - true; 7 rotected"oidCalendar2#SelectionCanged(ob)ectsender* +"ent$rgse, & Createdon.8e9t - Calendar2.SelectedDate.8oString(,; 7 rotected"oidCalendar2#DayBender(ob)

onlie crporate recruitment system

Documents