new human resource management

8/4/2019 New Human Resource Management

1/29

Vishwas Infosoft Solutions Pvt. Ltd.

HRMS_v_0.11

Human Resource Management

INTRODUCTION.

MODULE DESCRIPTION.

SYSTEM REQUIREMENTS.

SYSTEM ANALYSIS.

FEASIBILITYSTUDY.

PROJECT PLANNING.

DATABASE DESIGN.

DATA DICTIONARY.

DATA FLOW DIAGRAM.

UML DIAGRAMS.

FEATURE ENHANCEMENTS.

BIBLIOGRAPHY.


2/29


HRMS_v_0.12

1.0 Introduction1.1 What is Hrms:

The Human Resource Management System (HRMS) is an on-line computerized system which

stores, processes and reports employment and payroll records.

The functions of HRMS are:

Security (management of on-line view and update capabilities)

Registration process.

Leave application process.

1.2 HRMS SECURITY:

HRMS security is administered by Financial Systems. Operators may have both update and

inquiry or inquiry only privileges to employee data. Access is based on the NMSU

organizational hierarchy, which defines operator access to employees in the same home

department. In addition, operators will have access to departmental employees in

subordinate departments as defined by the universitys hierarchy. Access to employment

records from a department other than an operators home department can be addressed on

a case-by-case basis.

When a logon attempt is made, the system verifies the requested function and logon

information against established security tables and matrices. Access is either allowed or

denied based upon the security clearances for the operator. When an employee record is

requested, the system will verify that the operators home department matches either the

requested employees home department or that a hierarchical relationship exists. If neither

of these conditions exist and the requested employees home department has not been

specifically included in the operators security, access will be denied.


3/29


HRMS_v_0.13

Registration process:

This module provides instruction for completing the new hire process. It is important that

these components accurately reflect an employees history because Human Resources data

is used in both the Universitys management and government reporting for various

purposes.

OBJECTIVES:By the end of this process, you will be able to:

Enter contact information details.

Enter Qualification Information details.

Enter Experience details.

Address Information

Use this page to change existing home or business addresses or to record other addresses.

The system automatically records the home and mailing address here when first entered

under Personal Data. To change one of these addresses, follow the steps below. To enter a

new address type, follow the steps on the next page.

Leave application process:

Provide an understanding of the fundamental workings of the Pay Day Leave Module.

Introduction to Pay Day Leave Module.


4/29


HRMS_v_0.14

Practical use of the different leave types

e.g. Annual, Accumulated, Family Responsibility, Sick, Maternity etc.

The capture of transactions and accessing Leave History.

MODULE DESCRIPTION:

The list of modules incorporated with Human Resource Management System is

Employee Info Module.

Team Leader Module.

HR Module.

Employee Info Module:

This module deals with the management of the employee information such as the

personal details-his name, qualification, skill, experience, login id, password, etc.,

Importance of modules in any software development side is we can easily understand what

the system we are developing and what its main uses are. At the time of project we may

create many modules and finally we combine them to form a system. so that it can be easily

added to the database with any duplication of the data.

TEAM LEADER MODULE:

This module deals with the management of the employee information such as the hiring of

the eligible candidate is to approved to team leader, rejected by team leader. And

employee leave application process is approved or rejected to team leader. When we have


5/29


HRMS_v_0.15

approved process will be forwarded to hr module. Otherwise rejected message will be

forwarded.

HR MODULE:

This module deals with new hire employee based on his profile monitoring and also the

employee leave information details monitoring. When we have team leader approved new

employee information details see hr will be activated or rejected. When we have team

leader approved employee leave information details see hr will be approved or rejected.


6/29


HRMS_v_0.16

SYSTEM REQUIREMENTS :

Software Specification :

Software : Struts.

Middle ware software : JDBC.

Database : My SQL

Operating System : Windows N T / 98/ 2000/XP/7

RAM : 64MB to 256MB.

Hard ware Specification:

Processor : Intel P-III based system

Processor Speed : 250 MHz to 833MHz

Hard Disk : 2GB to 30GB

Key Board : 108 keys


7/29


HRMS_v_0.17

System Analysis:

The HRMS application is based on relational database technology and web

architecture. The application stores information in tables. In this we will discuss the way

HRMS utilizes these tables to enable efficient storage and retrieval of data. We will

discuss the impact of Effective Dates and Actions, as they relate to the business

information you maintain using the HRMS application.

ObjectivesBy the end of this module, you will be able to:

Illustrate effective dating within HRMS.

Describe the four Actions and their purpose when accessing a page.

EXISTING SYSTEM :

The HR Administration falls short of controlling the employees activities in analyzing his/her

strengths and weakness. The decision for appraisal of assigning next project to the

employee or to train him/her to enhance the skills where lies with proper projection. He is

not provided with the detailed project information done or to be assigned based on

Application / Verticals.

DRAWBACKS IN EXISTINGSYSTEM: Need of extra manual effort.

It used to take much time to find any employee.


8/29


HRMS_v_0.18

Not very much accurate.

Danger of losing the files in some cases.

PROPOSED SYSTEM:

Decision in assigning proper skillful hands for the project is an important issue in HR

Module. The HR Administrator should report with the personal holding the necessary skills

required for the project assignment. The decision in making analysis about the employees

skills is a prime important before booting in. The proposed system of HR Module is the right

software to be incorporated into the Automation of HR Software for helping the organization

needs with respect to skilful Human Resource.

The proposed system provides detail general information about the employee along with

Educational, Certification, Skill and Project details. It enhances the HR Management in

adding, viewing and updating employees details and generates various reports regarding

employees skill and experience. Suggestions and Grievances posted by the employees are

upheld for taking care of the necessary steps in forwarding companys obligation.

ADVANTAGES OF PROPOSED SYSTEM:

Very fast and accurate.

No need of any extra manual effort.

No fever of data loss.

Just need a little knowledge to operate the system.

Doesnt require any extra hardware device.


9/29


HRMS_v_0.19

At last very easy to find the employees.

FEASIBILITY 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

Economical Feasibility

Operational Feasibility

TECHNICAL FEASIBILITY:

In Technical Feasibility study, one has to test Whether the proposed system can be

developed using existing technology or not. It is planned to implement the proposed system

using java technology. It is evident that the necessary hardware and software are available

for development and implementation of the proposed system. Hence, the solution is

technically feasible.

ECONOMICAL FEASIBILITY :

As part of this, the costs and benefits associated With the proposed system compared

and the project is economically feasible only if tangible or intangible benefits outweigh


10/29


HRMS_v_0.110

costs. The system development costs will be significant. So the proposed system is

economically feasible.

OPERATION FEASIBILITY :

It is a standard that ensures interoperability Without stifling competition and

innovation among users, to the benefit of the public both in terms of cost and service

quality. The proposed system is acceptable to users. So the proposed system is

operationally feasible.

PROJECT PLANNING

The material covered so far has addressed the concepts, tools, and technology for

building systems. Developing a system requires planning and coordinating resources within

a given time. More important, effective project management is needed to organize the

available resources, schedule the events, and establish standards. A project manager is

expected to have managerial and technical skills along with management support for

system success.

The process of planning, designing, and implementing computer system is called a

project. A project manager who uses available resources to produce systems for the

organization directs it. In large firms, installing a system may take years and involve

hundreds of people. Planning and installing smaller projects on schedule also take time to

and require control and coordination of resources. It takes an effective manager to organize

the available resources, schedule the events, and establish standards. A project manager is

expected to have managerial and technical skills along with management support for

system success.

Time Scheduling:


11/29


HRMS_v_0.111

Project planning involves plotting project activities against a time frame. We

exercised a lot to plan project according OO project metrics.

There are two popular tools to plot the project planning: Gantt chart and PERT chart.

Gantt chart:

The following chart shows our typical plan of the time scheduling in the form of Gantt

chart. A Gantt chart is a horizontal bar chart developed as a production control tool in 1917

by Henry L. Gantt, an American engineer and social scientist.

Week

Activity 0 2 4 6 8 10 12 14 16 18 20

Preliminary

Analysis

Design

Coding

Testing

Documentation

PERT Chart:

Gantt chart has one drawback: They do not show precedence relationships among the

tasks and the milestones of a project. PERT charts have overcome this. The following chart

shows our typical plan of the time scheduling in the form of PERT chart.

Task ID:


12/29


HRMS_v_0.112

1. Preliminary Investigation

2. Analysis

3. Design

4. Coding

5. Testing and Debugging

6. Documentation

Precedence relationships:

Part of the process of building a project schedule involves breaking down the work into

smaller activities (the Work Breakdown Structure) and then sequencing the activities. When

you sequence the activities you should make sure that every activity is related to at least

one other activity. In many cases, the relationships will involve two or more activities.

There are a couple of ways to represent these relationships. Perhaps the most common

technique is called Precedence Diagramming Method (PDM). (This technique is sometimes

called Activity on Node (AON).) In the PDM technique, the activities themselves are placed

in boxes and the boxes are connected with arrows that show the precedence relationship.

The most common precedence relationship is when one activity cannot start until another

activity has finished. In most schedules this is the relationship that exists in almost all (if

not all) cases. This is referred to as a Finish-to-Start relationship. However, there are three

721

21

28

4914

1

2

3

4

5

6

7


13/29


HRMS_v_0.113

other ways that one or more activities can be related to another one. All four are described

below.

First, let's assume we have two activities--"A" and "B". It does not matter what the exact

activities are. It only matters that there is a relationship between them. There are four

possible relationships.

Finish-to-Start :

This means that Activity B cannot start until Activity A has completed. This is by far the

most common relationship between multiple activities. In most schedules, all relationships

will be finish-to-start.

Example:

Activity A is "Create the Project Charter."

Activity B is "Obtain Project Charter approval from the Project Sponsor."

This finish-to-start relationship would say that we must create the Project Charter

before we obtain Project Charter approval from the Project Sponsor.

Start-to-Finish:

Start-to-finish means that Activity A must start before Activity B can finish. This is a very

rare relationship.

Example: Let's assume that you want to fertilize your garden, but the plants must all be wet

when the fertilizer is applied.

Activity A is to "fertilize the garden."

Activity B is to "water the garden."


14/29


HRMS_v_0.114

The start-to-finish relationship says we need to start watering the garden (activity B)

first to get the plants wet. This activity must continue until the fertilizing starts (activity

A). This will ensure the plants remain wet until the fertilizer is ready to be applied. Note

that you can start watering at any time and you can finish fertilizing at any time. The

relationship only ties the start of activity A to the completion of activity B.

Start-to-Start:

This means Activity A must start before Activity B can start.

Example: Assume that you are having your walls painted in one room and wallpaper is

being hung in another room. You want to minimize the total disruption and so you want to

make sure both activities happen at the same time.

Activity A is "Paint the walls."

Activity B is "Hang the wallpaper."

The wallpaper hangers may be ready to go (activity B). However, the start-to-start

relationship says that they cannot start until the painting starts (activity A). This

relationship is based on the activity start times. The end times of each activity are not

related and, in fact, one activity could end at a much later time than the other.

Finish-to-Finish:

This means Activity A must finish before Activity B can finish.

Example: Assume you're cooking dinner and you want the turkey to finish cooking before

the potatoes.

Activity A is "Cook turkey."

Activity B is "Cook potatoes."


15/29


HRMS_v_0.115

The finish-to-finish relationship says that the turkey must finish cooking (activity A)

before the potatoes finish cooking (activity B). This relationship is based on the end

times. They can each start whenever they need to, as long as they finish in this

order.

Database Design:Database design is the process of developing database structures to hold data to

cater to user requirements. The final design must satisfy user needs in terms of

completeness, integrity, performance and other factors. For a large enterprise, the database

design will turn out to be an extremely complex task leaving a lot to the skill and experience

of the designer. A number of tools and techniques, including computer-assisted techniques,

are available to facilitate database design.

The primary input to the database design process is the organizations statement of

requirements. Poor definition of these requirements is a major cause of poor database

design, resulting in databases of limited scope and utilities which are unable to adopt to

changes.

The major step in database design is to identify the entities and relationships that

reflect the organizations data, naturally. The objective of this step is to specify conceptual

structure of the data and is often referred to as data modeling.

There are several methodologies to model the data logically. We adopted ER

modeling as our data modeling technique. ER model is technique for analysis and logical


16/29


HRMS_v_0.116

modeling of systems data requirements. It uses three basic concepts: entities, attributes

and relations.

Entity:

Entity is a distinguishable object. These entities are classified into regular entities

and weak entities. A weak entity is an entity that is existence dependent on some other

entity i.e. it does not exist if that other entity does not exist. A regular entity is that it is not

weak. The graphical notation of entity is shown below.

Attribute:

Entities have properties known as attributes. All entities of a given type have certain

kinds of properties in common. Each kind of property draws its value from a corresponding

value set. Properties can be of various types: Simple or composite, key, single or multi,

missing, and base or derived. Attributes are graphically represented as shown below.

Relation:

Relationship defines an association among entities. The entities involved in a given

relationship are said to be participants in tat relationship. The number of participants in a

given relationship is called the degree of that relationship. An ER relationship can be one

one, one many, and many - many. Cardinality of a relationship refers to representing the

number of occurrences of entities in a given relationship. The graphical notation of relation

is represented as shown below.

Regular Entity Weak Entity

Attribute


17/29


HRMS_v_0.117

In our project we have identified entities, attributes for those entities, and relationships

between those entities from data collected at analysis phase. These are listed below:

Entities:

Registration

Registration Status

Registration Experience

Employee

Department.

Department Details

Employee Leave Details.

Employee Utilities.

Attributes:

Relationshi

p


18/29


HRMS_v_0.118

EntityAttributes

Registration REGISTRATION_ID,FIRSTNAME ,LASTNAME,DOB, AGE, SEX,

CONTACT NUMBER, ALTERNATIVE NUMBER , EMAIL_ID,

ADDRESS,

SCHOOL_DETAILS,INTERMEDIATE_DETAILS,GRADUATION_

DETAILS, POSTGRADUATION_DETAILS, DEPARTMENT,

REGISTRATIONSTATUS , TYPEOFREGISTRATION,

SOFTSKILLS, TECHNICALSKILLS, REGISTERED

DATE,APPROVEDDATE,ACTIVATIONDATE.

Registration Status EMPLOYEE_ID,DEPARTMENT_ID,FIRSTNAME,LASTNAME,DO

CUMENTS_SUBMITTED,OFFERLETTER_CREATED,OPPOINTM

ENT_CREATED,EMPLOYEE_ID_CREATED,ACCESSCARD_ISS

USED.

Registration Experience REGISTRATION_ID,ORGANIZATIONNAME,TOTAL_EXPERIEN

CE (In Months) ,DESIGNATION, REFFERAL_NAME,

REFFERAL_NUMBER,REFFERAL _DESIGNATION.

Employee EMPLOYEE_ID,FIRSTNAME,LASTNAME,DOB,AGE,CONTACT

NUMBER,ALTERNATIVENUMBER,EMAIL_ID,ADDERSS,

SCHOOL_DETAILS,INTERMEDATE_DETAILS,

GRADUTION_DETAILS,POSTGRADUTION_DETAILS,SKILLS,S

EX,LANGUAGEKNOWN,PASSWORD,STATUS,DATEOFJOININ

G.

Department DEPARTMENT_ID,DEPARTMENTNAME,LOCATION,DOMAIN.

Department Details EMPLOYEE_ID,DESIGNATION,SALARY,ROLE,DESCRIPTION,

DEPARTMENT_ID,IDCARD_NO,GRADE,TEAMLEADER,MANAG

ER,ANNUAL_LEAVES.

Employee Leave Details LEAVE_ID,EMPLOYEE_ID,EMPLOYEENAME,SUBJECT,

LEAVE_FROMDATE,LEAVE_TODATE, DESCRIPTION,

LEAVESTATUS,LEAVEREQUESTEDDATE,LEAVEAPPROVEDDA

TE,TL_LEAVEAPPROVEDDATE,HR_LEAVEACTIVEDATE.

Employee Utilities EMPLOYEE_ID,FIRSTNAME,LASTNAME,EMPLOYEE_DESK,

PERIPHERLS,DESCRIPTION,IPADDRESS,ASSESSCARDNO,

DATEOFJOINING,


19/29


HRMS_v_0.119

Data Dictionary:

A data dictionary is a catalogue a repository of the elements in a system. As the

name suggests, these elements center around data the way they are structured to meet

user requirements and organization needs. In a data dictionary you will find a list of all the

elements composing the data flow through a system.

REGISTRATION:

Name Type Constraints Description

REGISTRATION_ID Varchar(20) Primary key REGISTRATION_ID

FIRSTNAME Varchar (45) Not null FIRSTNAME

LASTNAME Varchar (45) Not null LASTNAME

DOB Varchar (32) Not null DOB

AGE INT(6) Not null AGE

SEX Varchar(20) Not null SEX MALE/FEMALE

CONTACTNUMBER Varchar(12) Not null CONTACTNUMBER

ALTERNATIVE

NUMBER

Varchar(12) ALTERNATIVE

NUMBER

EMAIL_ID Varchar(50) EMAIL_ID

ADDRESS Varchar(150) Not null ADDRESS

SCHOOL_DETAILS Varchar(150) SCHOOL_DETAILS

INTERMEDIATE_DET

AILS

Varchar(150) INTERMEDIATE_DET

AILS

GRADUTION_DETAIL

S

Varchar(150) GRADUTION_DETAIL

S

POSTGRADUATION_

DETAILS

Varchar(150) POSTGRADUATION_

DETAILS

DEPARTMENT Varchar(32) Not null DEPARTMENT

REGISTRATIONSTAT

US

Varchar(32) REGISTRATIONSTAT

US

TYPEOFREGISTRATI Varchar(32) Not null TYPEOFREGISTRATI


20/29


HRMS_v_0.120

ON ON

SOFTSKILLS Varchar(32) Not null SOFTSKILLS

TECHNICALSKILLS Varchar(32) TECHNICALSKILLS

REGISTERED_DATE Varchar(32) Not null REGISTERED_DATE

APPROVED_DATE Varchar(32) Not null APPROVED_DATE

ACTIVATION_DATE Varchar(32) Not null ACTIVATION_DATE

REGISTRATION_STATUS:


EMPLOYEE_ID Varchar(20) Primary key EMPLOYEE_ID

DEPARTMENT_ID INT(11) NOTNULL DEPARTMENT_ID



DOCUMENTS_SUBMITTED Varchar (45) DOCUMENTS_SUBMITTED

OFFERLETTER_CREATED Varchar (45) OFFERLETTER_CREATED

OPPOINTMENT_CREATED Varchar (45) OPPOINTMENT_CREATED

EMPLOYEE_ID_CREATED Varchar (45) EMPLOYEE_ID_CREATED

ACCESSCARD_ISSUSED Varchar (45) ACCESSCARD_ISSUSED

REGISTRATION_EXPERIENCE:


REGISTRATION_ID Varchar(20) Not null EMPLOYEE_ID

ORGANIZATIONNAME Varchar(45) Not null ORGANIZATIONNAME

TOTAL_EXPERIENCE (In Varchar (45) Not null TOTAL_EXPERIENCE (In


21/29


HRMS_v_0.121

Months) Months)

DESIGNATION Varchar (45) Not null DESIGNATION

REFFERAL_NAME Varchar (45) REFFERAL_NAME

REFFERAL_NUMBER Varchar (45) REFFERAL_NUMBER

REFFERAL _DESIGNATION Varchar (45) REFFERAL _DESIGNATION

EMPLOYEE:


EMPLOYEE_ID Varchar(20) Primary key EMPLOYEE_ID



DOB Varchar (32) Not null DOB

AGE INT(6) Not null AGE

SEX Varchar(20) Not null SEX MALE/FEMALE

CONTACTNUMBER Varchar(12) Not null CONTACTNUMBER

ALTERNATIVE

NUMBER

Varchar(12) ALTERNATIVE

NUMBER

EMAIL_ID Varchar(50) EMAIL_ID

ADDRESS Varchar(150) Not null ADDRESS

SCHOOL_DETAILS Varchar(150) SCHOOL_DETAILS

INTERMEDIATE_DET

AILS

Varchar(150) INTERMEDIATE_DET

AILS

GRADUTION_DETAIL

S

Varchar(150) GRADUTION_DETAIL

S


22/29


HRMS_v_0.122

POSTGRADUATION_

DETAILS

Varchar(150) POSTGRADUATION_

DETAILS

SKILLS Varchar(32) Not null SKILLS

LANGUAGEKNOWN Varchar(32) LANGUAGEKNOWN

PASSWORD Varchar(32) Not null PASSWORD

STATUS Varchar(32) Not null STATUS

DATEOFJOINING Varchar(32) DATEOFJOINING

ER Diagram:


23/29


HRMS_v_0.123

DATA FLOW DIAGRAM:


24/29


HRMS_v_0.124

UML Diagrams:


25/29


HRMS_v_0.125

Use case Diagram:

Sequence Diagram:


26/29


HRMS_v_0.126

Collaboration Diagram:


27/29


HRMS_v_0.127

FEATURE ENHANCEMENTS:


28/29


HRMS_v_0.128

Software Specification :

Software : Struts.

Middle ware software : Hibernate.

Database : My SQL .

Bibliography


29/29


HRMS_v_0.129

SOFTWARES REFERENCES

HTML:HTML In a Nut Shell ORielly

Using HTML 4.0 Joseph Weber

Java:

Java In a Nut Shell ORielly

Using Java 2 Platform Joseph Weber

The Complete Reference Java 1.2 Herbert Schildt

Core Java Kenneth Paul

Introduction To Java Servlets James Good Will

Java Servlet Programming ORielly

Java Database Programming Matthew Siple

System Development:

Fundamentals Of System Concepts Jerry Fitz Gerald

System Analysis And Design Elias M. Awad

Software Engineering: Roger P Pressman

Uml References:

Learning Uml ORielly

new human resource management

Documents