final project report for s.e

8/13/2019 Final Project Report for s.e

1/93

SOFTWARE ENGG.

PROJECT ONHUMAN RESOURCE

MANAGEMENTSYSTEM

Submitted by- Submitted to-

Chitransh Saxena Mr. P.K. Maurya

Sakshi Tripathi C.S.E Department

Asha Rani


2/93

Amit Singh

B.Tech(C.S.)

- 2 -


3/93


4/93

ACKNOWLEDGMENT

e express thanks an! gratitu!e t" Mr. #$BA%R K&A'

&..D. (c"mputer science) B.tech %n*ertis $ni*ersity Barei++y

,"r his enc"uraging supp"rt an! gui!ance in carrying "ut the

pr"-ect.

e "u+! +ike t" express gratitu!e an!

in!e/te!ness t" him ,"r his *a+ua/+e a!*ice an! gui!ance ith"ut hich

this pr"-ect "u+! n"t ha*e seen the +ight ", the !ay.

e thank "ur ,acu+ty Mr. P.K. Maurya as "ur

Pr"-ect gui!e ,"r pr"*i!ing us ith an exce++ent pr"-ect an! gui!ing me

in c"mp+eting "ur pr"-ect success,u++y. e "u+! +ike t" thank a++ the

sta,, mem/ers ,"r their kin! c"0"perati"n. e "u+! +ike t" thank my

parents ,"r /eing supp"rti*e a++ the time an! e am *ery much "/+ige!

t" them.

- 4 -


5/93

ABSTRACT The main of the project is to develop a

Human Resource Management system for the Intranet

Automation of HR Software .HR system provides the

information regarding the employees I the company. The

system has been to facilitate good Interaction

communication facilities between the employees and HR

Administration.

The web pages about an employee are created

dynamically based on the user id and password and lin!s

are provided to web pages containing information about

employee "eneral details # $ontact details #s!ill details

etc.# he also has the facility of viewing a summary report of

all the projects done by a particular employee. A list of all

employees is provided along with employee%s &esignationand &epartment.

- 5 -


6/93

CONTENTS

- 6 -


7/93

CONTENTS

Page no!

1Ackn"+e!gement

1A/stract

2. %'TRD$CT%'

2.2 &RMS

3. S4STEM A'A54S%S

3.2 Existing System

3.3 Pr"p"se! System

3.6 7easi/i+ity Stu!y

6. MD$5E DESCR%PT%'

6.2 Emp+"yee %n," M"!u+e

6.3 A!ministrati"n M"!u+e

6.6 Pr"-ect Management M"!u+e

6.8 Training Management M"!u+e

8. S4STEM RE9$%REME'TS

8.2 S",tare Re:uirements

- " -


8/93

8.3 &ar!are Re:uirements

;. 5%TERAT$RE S$R'

=.2 Detai+e! Design

=.2.2 $M5 Diagrams

=.3 Data/ase Design

=.3.2 Data,+" Diagrams

=.3.3 Data/ase Ta/+es

=.3.6 E0R Diagrams

=.3.8 Screens.

?. TEST%'>

@. %MP5EME'TAT%'

. C'C5$S%'

2.B%B5%>RAP&4

- # -


9/93

$NTRODUCT$ON

- % -


10/93

INTRODUCTION

&!2!& $NTRODUCT$ON

To develop a software application that supports the application

specific to the HR automation in an intranet specific to a company

there by allowing the integration of all the employees pertaining to

that organi'ation. To !eep trac! of all the other departments

related to that organi'ation such as mar!eting# development etc.To allow the HR of an organi'ation to update the employee

details when ever there is a change in the employee profile

pertaining to that organi'ation. To bring onto a string the

employee specific suggestions and ma!e them free to post their

re(uirements to the HR thus bringing the organi'ation more

specific regarding the maintenance of the organi'ation.

&!2!2 PURPOSE O' THE PRO(ECT)

The HR center is a powerful application designed to allow

companies to streamline their human resource tas!s and manager

their employees more efficiently

)mployee and $ompany Information

)mployee Time# Attendence# and *eave Re(uest

HR &ocumentation Management +i.e. insurance forms# ,-%s etc./

The HR $enter includes a comprehensive employee information

database# where employers can information# wor! information#

beneficiary information# and more for each employee. It comes

standard with employee self-service access allowing employees to

update their personal information# re(uest time off or input their

daily timesheet entries. It also has role 0based access level control

- &* -


11/93

that is functionally based on whether a user is an employee# a

manager# or an HR admistrators. ,ith HR center managers and

HR admistrators can manage an trac!

&!2!3 PRO(ECT OB(ECT$+E)

To develop a software application that supports the application

specific to the HR Automation in an intranet specific to a company

there by allowing the interaction of all the employees pertaining to

that organi'ation. To !eep trac! of all the other departments

related to that organi'ation li!e mar!eting# development etc.#

To allow the HR of an organi'ation to update the employee details

when ever there is a change in the employee profile pertaining to

that organi'ation. To bring on to a string the employee

specification suggestions and ma!e them sure to post their

re(uirements to the HR.

&!2!4 PRO(ECT SCOPE)

Allow a for the creation of an application specification to thehuman resource that maintain the intranet automation of the HR

software i.e.# which contains the data related to the employee.

PROJECT OVERVIEW:

This project can be used to identify a employee in the

organi'ation. The project maintains the details of the entire

employee. )ach employee is given with different employee Id.

- && -


12/93

3. S4STEM

A'A'54S%S

- &2 -


13/93

2! SYSTEM ANALYS$S

System ana+ysis ,"cuses "n speci,ying hat the system "r

app+icati"n re:uire! T" !". %t a++"s in!i*i!ua+s see +"gica+e+ements (hat the system sh"u+! !") apart ,r"m the physica+

c"mp"nent it uses (c"mputers termina+s an! st"rage system). %t

is the pr"cess ", gathering an! interpreting ,acts !iagn"sing

pr"/+em an! using the in,"rmati"n t" rec"mmen! impr"*ements

t" the system.

- &3 -


14/93


15/93

2!& E,$ST$NG SYSTEM

The existing system is the manua+ system. The manua+ system

is pr"ne t" err"r. %t is time c"nsuming. %t is *ery !i,,icu+t ,"r a

pers"n t" pr"!uce rep"rt. There are chances ,"r changing the

sa+es rep"rt an! !" ma+practicing. This system in*"+*es a +"t ",

manua+ entries ith the app+icati"ns t" per,"rm the !esire! task.

The !ra/acks ", the existing system are

Data maintenance a!"pte! /y the present system is n"t

accurate

%naccurate resu+t in case ", !up+icating !e+ay an!

inc"nsistency in rep"rting

>enerating c"ns"+i!ate! rep"rts is m"re !i,,icu+t in manua+

system an! it may n"t /e c"nsistent.

The transacti"ns are *ery time c"nsuming There is n" ,aci+ity ,"r the users t" kn" hether the !ata is

entere! is *a+i! "r n"t. This !isa!*antage is the ma-"r cause

", err"rs in transacti"n.

%t is n"t user ,rien!+y

- &5 -


16/93

PROPOSEDSYSTEM

- &6 -


17/93

2!2 PROPOSED SYSTEM

The pr"p"se! system is !esigne! t" e+iminate the !ra/acks ",

the existing system. %t is !esigne! /y keeping in min! a++ the

!ra/acks ", the present system in "r!er t" pr"*i!e a permanent

s"+uti"n t" the pr"/+ems. The primary aim ", the ne system is

t" spee!up transacti"ns. The rep"rt is prepare! ,"r the sa+es

!"ne /y the representati*e an! the !istri/ut"r. The graphs are

a+s" !ran ,"r sh"ing the pict"rai+ representati"n ", sa+es!"ne /y the representati*e an! !istri/ut"r ,"r a m"nth an! year.

The /i++ is ca+cu+ate! at the time ", sa+es an! the

in,"rmati"n ", sa+es is entere! int" the representati*e an!

!istri/ut"r ta/+e simu+tane"us+y. The representati*e c"!e an!

!istri/ut"r c"!e are *a+i!ate! an! the pr"cess is pr"cee!e!.

Accuracy ,"r a++ the !ata entere! is maintaine! in the pr"p"se!

system thr"ugh *a+i!ati"n an! *eri,icati"n ,r"m a++ the ,i+es.


18/93

'EAS$B$L$TY

STUDY

- -


19/93

2!3 'EAS$B$L$TY STUDY

Once the problem is clearly understood, the next

step is to conduct feasibility study, which is

high-level capsule version of the entered

systems and design process. The objective is to

determine whether or not the proposed system

is feasible. The three tests of feasibility have

been carried out.

Technical Feasibility

conomical Feasibility

Operational Feasibility

TECHN$CAL 'EAS$B$L$TY

!n Technical Feasibility study, one has to test

"hether the proposed system can be developed

using existing technology or not. !t is planned to

implement the proposed system using java

technology. !t is evident that the necessary

hardware and software are available for

development and implementation of the proposed

system. #ence, the solution is technically feasible.

- &% -


20/93


21/93

3! MODULE

DESCR$PT$ON

- 2& -


22/93

MODULE DISCRIPTION&

The list of modules incorporated with 'Human Resource

Management System is

mployee !nfo (odule

$dministration (odule

)roject (anagement (odule

Training (anagement (odule

#* *eports

This module deals with the management of the employee

information such as the personal details-his

name,%ualification,s+ill,experience,login id,password,etc.,

!mportance of modules in any software development side is we

can easily understand what the system we are developing and

what its main uses are. $t the time of project we may create

many modules and finally we combine them to form a system.

3!& mployee !nfo (odule

This module deals with the management of

the employee information such as the personal details-his

name,%ualification,s+ill,experience,login id,password,etc.,

!mportance of modules in any software development side is we

can easily understand what the system we are developing and

what its main uses are. $t the time of project we may create

many modules and finally we combine them to form a system.

- 22 -


23/93

person, so that it can be easily added to the database with

any duplication of the data.

3!2 A./n/01a0/on Moe)

This module deals with the management of the employee

information such as the hiring of the eligible candidate,

payments criteria, his personal information maintenance etc.

3!3 Project Management Module

This module deals with the management of the projects

related with the employee li+e-projects that were past

dealt, current projects in his account etc.

3!4 Tra!n!ng Management Module

This module deals with the training of the employee based

on his experience and attendance monitoring. $lso the

information of the projects that need to be trained for the

employees based on their experience and s+ills and the

li+e.

.HR Re"orts ModuleThis module is specified for the purpose of the report

generation for the #* on his desired re%uests.

- 23 -


24/93

SYSTEM

REU$REMENTS

- 24 -


25/93

H#RD$#RE #ND SO%T$#RE

RE&UIREMENTS

Hard 'are S"ec!(!cat!on&

)rocessor above or !ntel )-!!! based

system

)rocessor Speed / (#0 to 1(#0

*$( (inimum 23(4

#ard 5is+ (inimum 64

7ey 4oard 8/3 +eys

So(t'are S"ec!(!cat!on

9anguage :57 8.2

5atabase Oracle )!

Operating System "indows ;)


26/93

*$( & 2(4

L$TERATURE

SUR+EY

- 26 -


27/93

(A+A

:ava was conceived by :ames 6osling, )atric+ >aughton, ?hris

"arth, d Fran+ and (i+e Sheridan at Sun (icrosystems !nc.in

8@@8. !t too+ 81 months to develop the first wor+ing version.

This language was initially called 'Oa+A but was renamed as

':avaA in 8@@. 4etween the initial implementation of Oa+ in

the fall of 8@@ and the public announcement of :ava in the

spring of 8@@, many more people contributed to the design

and evolution of the language.

The main properties of the :ava, which made :ava so popular,

are as follows&

8. Simple

. Secure

. )ortable

3. Object-Oriented

. *obust

2. (ultithreaded

=. $rchitecture->eutral

1. !nterpreted

@. #igh performance

8/.5istributed

88.5ynamic

- 2" -


28/93

THE KEY 'EATURES O' (A+A $S BYTE CODE)

The +ey that allows :ava to solve both the security

and the portability problems just described is that the output

of a :ava compiler is not executable code. *ather, it is 4yte

code. 4yte code is a highly optimi0ed set of instructions

designed to be executed by the :ava runtime systems, which is

called the :ava Birtual (achine C:B(D. That is, in its standard

form, the :B( is an interpreter for 4yte code. This may come

has a bit of surprise.

Translating a :ava program into a byte code helps

and ma+es it much easier to run a program in a wide variety

of environments. The reason is straightforward only the :B(

needs to be implemented for each platform. Once the runtime

pac+age exists for a given system, any :ava program can run

on it. *emember, although the details of the :B( will differ

from platform to platform, all interpret the same :ava 4yte

code.

(A+A EN+$RONMENT)

:ava environment includes a large number of

development tools and hundreds of classes and methods. The

development tools are the part of the system +nown as :ava

5evelopment 7it C:57D and the classes are methods are part

- 2# -


29/93

of the :ava standard library C:S9D, also +nown as the

$pplication )rogramming !nterface C$)!D.

(A+A DE+ELOPMENT K$T)

The :ava development +it comes with a collection of

tools that are used for developing and running :ava programs.

They include&

8.$pplet Biewer Cfor viewing :ava $ppletsD

.:avac C:ava ?ompilerD.:ava C:ava interpreterD

3.:avap C:ava 5isassemblerD

.:avah Cfor ? header filesD

2.:avadoc Cfor creating #T(9 documentsD

=. :db C:ava 5ebuggerD

APPL$CAT$ON PROGRAMM$NG $NTER'ACE)

The :ava standard library includes hundreds of

classes and methods grouped into several functional pac+ages.

(ost commonly used pac+ages are&

9anguage support pac+age& $ collection of classes and

methods re%uired for implementing basic features of

java.

Etilities pac+age& $ collection of classes to provide utility

functions such as date and time functions.

!nput


30/93

>etwor+ing pac+age& $ collection of classes for

communication with other computers via !nternet.

$"T pac+age& The abstract window tool+it pac+age

contains classes that implements platform independent

graphical user interface.

$pplet pac+age& This includes a set of classes that allows

us to create :ava applets.

(A+A DATABASE CONNECT$+$TY (DBC

The :ava database connectivity $pplication

)rogramming !nterface C$)!D is an $)! currently being

designed by Sun (icrosystems that provides a :ava language

interface with SG9 ?all 9evel !nterface standard. This standard

provides a 54(S independent interface to relational databases

that defines a generic SG9 database access framewor+.

The most visible implementation of the SG9 ?9! is

(icrosoftHs O54? COpen 5atabase ?onnectivityD. This $)!

defines a common SG9 syntax and function calls that can be

used by developers to send SG9 commands to and retrieve

data from SG9 databases. O54? - enabled applications ma+e

use of database drivers Csimilar to other device driversD

installed on the system that allows applications to tal+ to a

vendorHs database. Esing this methodology, all of the 54(S

- 3* -


31/93

specific code is placed inside the O54? driver and the

application developer is shielded from implementation specific

problems in theory. )ractically spea+ing, it is sometimes

difficult to completely remove vendorHs specific syntax from all

O54? operations, but in most cases, it is relatively simple tas+

to port O54? to run on a new database server.

O54?Hs primary drawbac+ is that it is written in ?.

4ecause of the limitations inherent in the use of native

methods, the :54? designers have designed the :54?specification to most easily use O54? in short-term, but they

have provided the capability long-term for :54? to be

implemented in other ways.

The :54? $)! is expressed as a series of abstract

:ava interfaces within the java.s%l pac+age. #ere are the most

commonly used interfaces&

java.s%l.5river(anager I manages the loading and

unloading of database drivers from the underlying

systems.

java.s%l.?onnection I #andles the connections to a

specific database.

java.s%l.Statement I contains an SG9 statement to be

passed to the database& two sub-types in this interface

are the )reparedStatement Cfor executing a )re-?ompiled

SG9 statementD and the ?allableStatement Cfor executing

a database stored procedureD.

java.s%l.*esultSet I contains the record result set from

the SG9 statement passed to the database.

- 3& -


32/93

STEPS REU$RED TO ACCESS A (DBC DATABASE

The steps re%uired to access a :54? database

should be familiar. :54? uses the concept of a '?onnectionA

handle to manage a programHs connection to a database.

ESTABL$S$NG A CONNECT$ON

The first thing we need to do is establish a

connection with the 54(S you want to use. This involves two

steps &

*.Load!ng t+e dr!,er!f, we want to use the :54?-O54?

bridge driver, the following code will load it &

?lass.for>ame CJsun.jdbc.odbc.:dbcOdbc5riveAD

Our driver documentation will give us the class name to use.

For instance, if the class name is jdbc.5riverxy0, you would

load the driver with the following line of code&

?lass.for>ame C'jdbc.5riverxy0ADK

-. Ma/!ng t+e connect!on the second step in establishing a

connection is to have the appropriate driver connect to the

54(S. The following line of code illustrates the general

Syntax&

?lass.for>ame CJsun.jdbc.odbc.:dbcOdbc5rive

- 32 -


33/93

?onnection conL5river(anager.get?onnection CJ:dbc& Odbc&

hrmsdsnJDK

CREAT$NG A STATEMENT

$ statement needs to be created so that it can be passed to

the database for processing. This is done by calling the

connection class createStatement CD method.

Syntax&

:ava.s%l.Statement stLconnection.createStatement CDK

RETRE$+$NG +ALUES 'ROM RESULT SET

:54? returns results in a *esultSet object, so we

need to declare in instance of the class *esultSet to hold our

result. The following code demonstrates declaring the

*esultSet object *S and assigning the results to %uery&

*esultSet rsLst.executeGuery CJselect M from ()5$T!9S

where userNnameLJPuserNnamePJJDK

DATABASE

DATABASE

$ database is a set of data, organi0ed for easy

access. The database is an actual dataK it is the database thatyou will be accessing when you need to retrieve data.

DATA D$CT$ONARY

The data dictionary is a set of tables Oracle uses to

maintain information about the database. The data dictionary

contains information about tables, indexes, clusters and so on.

- 33 -


34/93

DBA DATABASE ADM$N$STRATOR

The 54$ is the person responsible for the operation,

configuration and performance of the database. The 54$ is

charged with +eeping the database operating smoothly,

ensuring that bac+ups are done on regular basis Cand that

bac+ups wor+D, and installing new software. Other

responsibilities might include planning for future expansion

and dis+ space needs, creating databases and table spaces,

adding users and maintaining security, and monitoring thedatabase and retuning it as necessary. 9arge installations

might have teams of 54$Hs to +eep the system running

smoothlyK alternatively, the tas+ might be segmented among

the 54$Hs.

OR#CLE

Oracle is a relational database management system, it

provides a platform for client server computing i.e., it supports

distributed database and distributed processing.

- 34 -


35/93

SYSTEM DES$GN

- 35 -


36/93

DETA$LEDDES$GN

- 36 -


37/93

UML

D$AGRAMS

- 3" -


38/93

UN$'$ED MODEL$NG LANGUAGE

E(9 is the international standard notation for object-oriented

analysis and design. The Object (anagement 6roup defines it.

The heart of object-oriented problem solving is the

construction of a model. The model abstracts the essential

details of the underlying problem from its usually complicated

real world. Several modeling tools are wrapped under the

heading of the UMLQ, which stands for Enified (odeling

9anguageQ.

AN O+ER+$EW O' UML)

The E(9 is a language for

Bisuali0ing

Specifying

?onstructing

5ocumenting

These are the artifacts of a software-intensive system. The

three major elements of E(9 are

The E(9Hs basic building bloc+s

The rules that dictate how those building bloc+s may be

put together.

- 3# -


39/93

Some common mechanisms that apply throughout the

E(9.

BAS$C BU$LD$NG BLOCKS O' THE UML)

The vocabulary of E(9 encompasses three +inds of building

bloc+s&

Things

*elationships

5iagrams

TH$NGS $N THE UML)

They are the abstractions that are first-class citi0ens in a

model. There are four +inds of things in the E(9

8. Structural things

. 4ehavioral things.

. 6rouping things.

3. $nnotational things.

These things are the basic object oriented building bloc+s of

the E(9. They are used to write well-formed models.

STRUCTURAL TH$NGS)

- 3% -


40/93

Structural things are the nouns of the E(9 models. These are

mostly static parts of the model, representing elements that

are either conceptual or physical. !n all, there are seven +inds

of Structural things.

Ca)

$ class is a description of a set of objects that share the same

attributes, operations, relationships, and semantics. $ class

implements one or more interfaces. 6raphically a class is

rendered as a rectangle, usually including its name, attributes

and operations, as shown below.

$n0e17a8e)

$n interface is a collection of operations that specify a service

of a class or component.6raphically the interface is rendered as a circle together with

its name.

- 4* -


41/93

ISpelling

Coa9o1a0/on)

?ollaboration defines an interaction and is a society of roles

and other elements that wor+ together to provide some

cooperative behavior thatHs bigger than the sum of all the

elements. 6raphically, collaboration is rendered as an ellipse

with dashed lines, usually including only its name as shown

below.

?hain

Ue Cae)

Ese case is a description of a set of se%uence of actions that a

system performs that yields an observable result of value to a

particular thing in a model. 6raphically, Ese ?ase is rendered

as an ellipse with dashed lines, usually including only its name

as shown below.

A80/:e Ca)

$n active class is a class whose objects own one or more

processes or threads and therefore can initiate control activity.

6raphically, an active class is rendered just li+e a class, but

- 4& -

Chain ofResponsibili

t

P+ace r!er

#*(S

EMP54EE

DEAT%5S

Suspend CDFlush CD


42/93


43/93

server

BEHA+$ORAL TH$NGS)

4ehavioural Things are the dynamic parts of E(9 models.

These are the verbs of a model, representing behaviour over

time and space.

$n0e1a80/on)

$n interaction is a behavior that comprises a set of messages

exchanged among a set of objects within a particular context

to accomplish a specific purpose. 6raphically, a message is

rendered as a direct line, almost always including the name if

its operation, as shown below.

5isplay

S0a0e Ma8


44/93

GROUP$NG TH$NGS

6rouping things are the organi0ational parts of the E(9

models. These are the boxes into which a model can be

decomposed.

RELAT$ONSH$PS $N THE UML)

There are four +inds of relationships in the E(9&

8. 5ependency

. $ssociation

. 6enerali0ation

3. *eali0ation

&!De;enen8=) This is relationship between two classes

whenever one class is completely dependent on the other

class. 6raphically the dashed line represents it with arrow

pointing to the class that it is being depended on.

- 44 -

aiting


45/93

2! Ao8/a0/on) !t is a relationship between instances of

the two classes. There is an association between two

classes if an

instance of one class must +now about the other in order to

perform its wor+. !n a diagram, an association is a lin+

connecting two classes. 6raphically it is represented by line

as shown.

3! Gene1a/>a0/on)$n inheritance is a lin+ indicating one

class is a super class of the other. $ generali0ation has a

triangle pointing to the super class. 6raphically it is

represented by line with a triangle at end as shown.

4! Rea/>a0/on)

D$AGRAMS $N UML)

5iagrams play a very important role in the E(9. There are

nine +ind of modeling diagrams as follows&

Ese ?ase 5iagram

- 45 -


46/93


47/93

that may be dispatched among them. !nteraction diagrams are

used for modeling the dynamic aspects of the system.

$ se%uence diagram is an interaction diagram that emphasi0es

the time ordering of the messages. 6raphically, a se%uence

diagram is a table that shows objects arranged along the ;-

axis and messages, ordered in increasing time, along the R-


axis.

SEUENCE D$AGRAMS

$ se%uence diagram is an interaction diagram that emphasi0es

the time ordering of the messages. 6raphically, a se%uence

diagram is a table that shows objects arranged along the ;-


axis.

Se%uence diagrams have two interesting features&

ACT$+$TY D$AGRAM

$n $ctivity 5iagram is essentially a flow chart showingflow of control from activity to activity. They are used to

model the dynamic aspects of as system. They can also be

used to model the flow of an object as it moves from state

to state at different points in the flow of control.

- 4" -


48/93


49/93


50/93

Training deatils

&ept*ocation

)mp 1ame

S!ill &etails

S!ill $ontent+/

Training Assign+/

&uration+/

$ompensation

$ompensation Amt+/

2ear of wor!+/

S!ill Report+/

)mployee &etails

&ept Assigned+/

&ate of 3oining+/

)mp &etails+/

)mp $omponent+/

HR Administration

Hr 1ame

Hr I&

Add &etails

Add )mp &etails+/

Add Training &etails+/

Add $ompensation+/

)mp login

*ogin+/

$hec! Training &etails+/

$hec! $ompensation+/

$hec! )mployee+/

USE CASE D$AGRAM

- 5* -


51/93

*ogin

*ogout

$hec! )mp &etails

Add )mp details

$hec! Training &etails

Add training details

Administrator

)mployee

$hec! $ompensation

Add $ompensation details

SEUENCE D$AGRAM

- 5& -


52/93

HR Admin )mployeeTraining $ompensation S!ill )mp deatils4lacement

5. login

6. Add emp details

. verify

7. Add s!ills Report

8. Add Training Report

9. Add 4lacement report

:. Add $ompensation Report

;. log out


53/93

)mp login$hec!

Training

Hr Admin

$hec! )mp

&etail $hec!$ompensatiopnAdd

Training

Addcompensation

Add )mp

&etails

ACT$+$TY D$AGRAM

- 53 -


54/93

- 54 -


55/93

Ca D/ag1a.

Training deatils

&ept

*ocation

)mp 1ame

S!ill &etails

S!ill $ontent+/

Training Assign+/

&uration+/

$ompensation

$ompensation Amt+/

2ear of wor!+/

S!ill Report+/

)mployee &etails

&ept Assigned+/

&ate of 3oining+/

)mp &etails+/

)mp $omponent+/

HR Administration

Hr 1ame

Hr I&

Add &etails

Add )mp &etails+/

Add Training &etails+/

Add $ompensation+/

)mp login

*ogin+/

$hec! Training &etails+/

$hec! $ompensation+/

$hec! )mployee+/

- 55 -


56/93


57/93

DATA 'LOW

D$AGRAMS

- 5" -


58/93

DATA 'LOW D$AGRAMS

DATA 'LOW D$AGRAMS)

$ graphical tool used to describe and analy0e the moment of

data through a system manual or automated including the

process, stores of data, and delays in the system. 5ata Flow

5iagrams are the central tool and the basis from which other

components are developed. The transformation of data from

input to output, through processes, may be described logically

and independently of the physical components associated with

the system. The 5F5 is also +now as a data flow graph or a

bubble chart.

CONTE,T D$AGRAM)

The top-level diagram is often called a 'context diagram. !t

contains a single process, but it plays a very important role in

studying the current system. The context diagram defines the

system that will be studied in the sense that it determines the

boundaries. $nything that is not inside the process identified

in the context diagram will not be part of the system study. !t

represents the entire software element as a single bubble with

input and output data indicated by incoming and outgoing

arrows respectively.

- 5# -


59/93

TYPES O' DATA 'LOW D$AGRAMS)

5ata Flow 5iagrams are of two types as follows&

CaD )hysical 5F5

CbD 9ogical 5F5

2.PHYS$CAL D'D)

Structured analysis states that the current system

should be first understand correctly. The physical 5F5 is the

model of the current system and is used to ensure that the

current system has been clearly understood. )hysical 5F5s

shows actual devices, departments, and people etc., involved

in the current system

2! LOG$CAL D'D)

9ogical 5F5s are the model of the proposed system.

They clearly should show the re%uirements on which the new

system should be built. 9ater during design activity this is

ta+en as the basis for drawing the systemHs structure charts.

BAS$C NOTAT$ON

- 5% -


60/93

The 4asic >otation used to create a 5F5Hs are as follows&

DATA'LOW)5ata move in a specific direction from an origin

to a destination.

PROCESS))eople, procedures, or devices that use or produce

CTransformD 5ata. The physical component is not

identified.

SOURCE) xternal sources or destination of data, which may

be )eople, programs, organi0ations or other

entities.

DATA STORE) #ere data are stored or referenced by a process

in

theSystem

- 6* -


61/93


62/93


63/93

Con0e?0 'o@ D/ag1a.

De81/;0/on)?ontext Flow 5iagram gives us the complete

details about the inputs and outputs for a given system. !n the

above system the main tas+ is to identify a criminal face. So,

the operator and eyewitness are the inputs to our system and

criminal face is desired output.

LOG$N PROCESS

Use! "#

Pass$o!#

ERRR %' %'P$T

Le:e-&

De81/;0/on) The inputs to the process are Eser !d and

)assword given by the developer to allow the software

available for the $dmin environment. $fter giving the inputs

the details, chec+s whether the entered ones are valid are not.

!t displays screen if match occurs otherwise error message if

they are not matched.

- 63 -

5>%' PROCESS SCREE'


64/93

MA$N SCREEN PROCESS

Le:e -2

De81/;0/on) This process mainly explains the differentscreens that are available for the admin. #ere the selection of

the screen depends on the admin and he can select whatever

screen he wants. The different screens that are available are

$dd mp details, $dd s+ill *eport, $dd placement report, $dd

Training *eport, $dd ?ompensation *eport.

- 64 -

MA%'

SCREE'ADM%' A!! Emp

A!! Ski++

Rep"rts

A!!

P+acement

A!! Training

Rep"rt

A!!

C"mpensati"n


65/93


66/93

A S/ Re;o10

Le:e-4

De81/;0/on)This process clearly illustrates adding the details

of the mployees s+ill *eport such as name, %ualification,experience, department, projects handled, current projects

and s+ills along with his () !d. These details are being added

to the database, if any error is generated then it will be

prompted to the admin otherwise we get message data is

successfully added.

- 66 -

ADD Ski++

Rep"rtA!min

DATABASE

DATA %S

ADDED


67/93

#dd Placement Re"ort

Le:e-5

De81/;0/on)This process clearly illustrates adding the detailsof the mployees placement *eport such as name, employee

status, reporting date, regulatory region, country, company

control unit, department, supervisor id, location and along with

his () !d. These details are being added to the database, if

any error is generated then it will be prompted to the admin

otherwise we get message data is successfully added.

- 6" -

A!minA!!

P+acement

Rep"rt

DATA

$PDATED

DATABASE


68/93

TRA$N$NG REPORTS

Le:e-6


of the mployees Training *eport such as name, project name,

training department, s+ill report, start date, end date,

department, and remar+s and along with his () !d. These

details are being added to the database, if any error is

generated then it will be prompted to the admin otherwise we

get message data is successfully added.

- 6# -

A!minA!!

Training

Rep"rt

DATA

$PDATED

DATABASE


69/93

COMPAR$SON PROCESS

Le:e-"


of the mployees ?ompensation *eport such as name, salary

range, and annual income, tax of income, loans, present

annual income, facilities, and insurance and along with his ()

name. These details are being added to the database, if any

error is generated then it will be prompted to the admin

otherwise we get message data is successfully added.

- 6% -

A!minA!!

C"mpensati"

n Rep"rt

DATA

$PDATED

DATABASE


70/93

DATABASE

TABLES

DATABASE TABLES

9ogin Table

- "* -


71/93

$dd mployee 5etails

add_emp

user_name password id first_name last_name ualifi!ation department date_ of"irt#

a$e se% address

!ishore !ishore 5==7 !ishore !umar M>A ?I1A1$) 5;-April 5 male yousfguda

sree sree 5==5 sree !umar mca computers =5=5.Tech computers 59=65.Tech computers ==95


72/93

s'ill_report()

user_name fname ua dept pro*_#and !urr_#and e%p s'il

sree sree mca computers I4MS hrms 3ava#3sp

vamsi vamsi >.Tech IT $RS ?inger 4rint I& java#jsp#jdbc

!ishore !ishore M>A ?I1A1$) Tally Accounts 9 $A

$dd )lacement *eport

p+,CE-ENT)(

username emp_stat effe_dat re$ion !oun !omp !ont_unit dept lo! super_id

sree Active =5-march-==9

Maharastra ABSTRA*IA >.H.).* production 4roduction $ampus employee

vamsi Active feb Maharastra ")RMA12 ") IT 1etwor!ing $ampus employee

!ishore Active 58 june &elhi BSA bre!ely ?I1A1$) ?inancing $ampus employee

- "2 -


73/93


74/93

SCREENS

- "4 -


75/93

LOG$N SCREEN

5>%' PRCESS

$SER %D

PASSRD

Submit Reset

- "5 -


76/93

MA$N SCREEN


77/93


78/93


79/93


80/93


81/93

Emp+"yee +"g"ut page

- #& -


82/93

- #2 -


83/93

TEST$NG

TEST$NG PHASE

The completion of a system is achieved only after it

has been thoroughly tested. Though this gives a feel the

project is completed, there cannot be any project without

going though this stage. #ence in this stage it is decided

whether the project can under go the real time environment

execution without any brea+ downs, therefore a pac+age can

be rejected even at this stage.

- #3 -


84/93


85/93

ACCEPTANCE TEST$NG

The software has been tested with the realistic data

given by the client and produced fruitful results. The client

satisfying all the re%uirements specified by them has also

developed the software within the time limitation specified. $

demonstration has been given to the client and the end-user

giving all the operational features.

- #5 -


86/93

$MPLEMENTAT$ON

$MPLEMENTAT$ON PHASE

The implementation is the final and important phase.

!t involves Eser training, system testing and successful

running of the developed system. The users test the developed

system when changes are made according to the needs. The

testing phase involves the testing of the developed system

using various +inds of data. $n elaborate testing of data is

prepared and system is tested using the tests data.

- #6 -


87/93

!mplementation is the stage where theoretical design

turned into a wor+ing system. !mplementation is planed

carefully to propose system to avoid unanticipated problems.

(any preparations involved before and during the

implementation of proposed system. The system needed to be

plugged in to the organi0ationHs networ+ then it could be

accessed from anywhere, after a user logins into the portal.

The tas+s that had to be done to implement the system were

to create the database tables in the organi0ation database

domain. Then the administrator was granted his role so thatthe system could be accessed.

The next phase in the implementation was to educate

the system. $ demonstration of all the functions that can be

carried out by the system was given to examination

department person, who will ma+e extensive use of the

system.

- #" -


88/93

CONCLUS$ON

The conclusion we getfrom our software is that

we have made highly

efficient and helpful

- ## -


89/93

software i.e. HUMANRESUR!E MANA"EMENT

S#STEM.which is anApplication software has

$een developed usingoracle and %ava data$ase

programmingconnectivity via oracledriver so as to meet the

re&uirements of anorgani'ation( there$y

ensuring &ualityperformance .The data

can $e accessed(manipulated and

retrieved very easily. Toconclude this softwarehas proved to $e a user

friendly interface.

- #% -


90/93


91/93

B$BL$OGRAPHY

- %& -


92/93


93/93

WEBS$TES RE'ERRED

The following lin+s were searched and exploited extensively for

the project development and implementation.

8. http&

final project report for s.e

Documents