hrms project peport

8/3/2019 HRMS Project Peport

1/35

Abstract

A Human Resource Management System (HRMS) or Human Resource Information System

(HRIS), refers to the systems and processes at the intersection between human resource

management (HRM) and information technology. It merges HRM as a discipline and in particular its

basic HR activities and processes with the information technology field, whereas the programming of

data processing systems evolved into standardized routines and packages ofenterprise resource

planning (ERP) software. On the whole, these ERP systems have their origin on software that

integrates information from different applications into one universal database. The linkage of its

financial and human resource modules through one database is the most important distinction to the

individually and proprietary developed predecessors, which makes this software application both rigid

and flexible.

1
http://en.wikipedia.org/wiki/Human_resource_managementhttp://en.wikipedia.org/wiki/Human_resource_managementhttp://en.wikipedia.org/wiki/Information_technologyhttp://en.wikipedia.org/wiki/Enterprise_resource_planninghttp://en.wikipedia.org/wiki/Enterprise_resource_planninghttp://en.wikipedia.org/wiki/Human_resource_managementhttp://en.wikipedia.org/wiki/Human_resource_managementhttp://en.wikipedia.org/wiki/Information_technologyhttp://en.wikipedia.org/wiki/Enterprise_resource_planninghttp://en.wikipedia.org/wiki/Enterprise_resource_planning


2/35

Chapter 1

Introduction

2


3/35

Chapter 1 : Introduction

The first view of human resources management, it was a routine active interested in recording,

classifying and saving data related to workers. Those data that will enable them to execute manager

responsibilities in running rules and laws of system and billboards that will organize labor usage and

employment, salaries and wages paymentetc.

However the modern view for Human Resource Management (HRM) was reforming where its one

of the main departments in an organization, which will cooperate in gaining the production efficiency,

plus gaining the main purposes of the organization.

In real life if you want to view or get some services from any organization you must go to that

organization and search through documents to find results and make them manually, this has a big

chance to get loss or

harmed and you may lose your effort and time.

Our system aims to make this operation in computerized form, to insure working in precise and get

employees satisfaction.

We claim this system from scratch and we claim that we included all functionalities to make the

system applicable and easy to use even for non-technical staff.

We start doing our project step by step involving all the phases in system development life cycle,

starting with identification and selection, initiation and planning, analysis, design, and implementation.

3


4/35

1.1. Problem Recognition and Identification

1.1. 1.What problems we face?

The manual work in human resource department in any organization may produce errors, loss

of documents, difficult to determine the wrong and need more time .

1.1.2. What are the undesirable symptoms of the problem?

Spending extra time and effort to produce specific reports, since no ready

templates are available.

The Complexity of maintaining the huge number of paper files used for the

system work.

The probability of losing some information because of the disorganization of paper

files.

1.1.3. What is the solution?

The solution is to develop a nearly full electronic system that will used by the Administrators,

Employees and Data Entry of human resource management system to facilitate its works and

keep track of all necessary management information and reports. The new system will give

control, guarantee accuracy and Save time and effort

1.1.4. The identification

The Human Resource Management System (HRMS) system has been identified by our group,

which hopes that it will be applicable in any Organization.

1.1.5.Selecting IS development project:

We decided to accept this project according to project factors, such as existence and

availability of resources, perceived requirements and real need of this project t

1.1.6.System Overview:

A new system will be constructed in order to allow employee to perform the operation

on documents in their organizations to improve performance, enhance productivity, get

employees satisfaction, and simplify document procedures.

4


5/35

1.2. Project Initiation and Planning

The second phase of the system development life cycle (SDLC) is Project initiation and planning,

which comes after the system on hand being identified and selected, which we will display in this part,

as well as others to recognize the SDLC phases, and the sequence of the tasks involved.

In this phase, we performed a preliminary investigation of the existing system, organizing a system

study team, and developing strategic plans for the remainder of the study.

5


6/35

Chapter 2

Project Planning

6


7/35

Chapter 2 : Project Planning

2.1. Statement of Work:

Project name: Human Resource Management System (HRMS)

Customer: Not Defined .

Project Start -- End: 6-Feb-2011 to 4-May-2011

Project Description:

The Human Resource in Jordan planning to develop a new computerized Employee System, which

will help Organization to get rid of a lot of paper-based files and reports, because all needed

information will be filled and submitted electronically.Goal:

The purpose of this system is to automate the manual process to save employees time, reduce errors,

and have more accurate information.

Objectives:

1. Minimize data-entry errors

2. Provide accurate information.

3. Cost reduction.

4. Increase the flexibility.

5. Increase the speed of performing activities.

6. Improvement of management planning and controls.

Phases of work :

The following tasks and deliverables reflect the current understanding of the project:

Analysis :

1. Determining system requirement.

2. Structuring system requirements (process modeling, logic modeling, Conceptual Data

modeling).

7


8/35

Design :

1. Designing Databases, forms and reports.

2. Designing interfaces and Dialogs.

3. Finalizing Design specifications.

Implementation :

System implementation (coding).

Establishing Project Team :2.2

The necessity of establishing a good development team is equivalent to the necessity ofimplementing a good project, because one of the major factors that determine the success of the

project is how efficient the development team

So, as a first step of initiating our project, we select the team members, such that all expertise

needed to implement the project are available

The team consists of three members:

seinBashar Amin Hus

AbdAlrahman Abu AlKheel

Mohammad Al Hammouri

To guarantee the best communication between the group members, we create a semi-stable

communication plan (changes occurred based on the exams schedules), this plan includes:

- Meeting in university and home

- Mobile phone

- E-mails and messenger

- Team Viewer Application

8


9/35

.Identifying the System development Environment :2.3

We develop this project according to the SDLC and its based software process model such that

waterfall model, evolutionary model and integration from reusable component.

We follow the waterfall model phases to develop our system. The image below is the classic Waterfall

model methodology, which is the first SDLC method and it describes the various phases involved in

development.

Figure Shows the phases waterfall model

9

Feasibility

Analysis

Design

Implementation

Test

Maintenance


10/35

2.4. Project scope :

This project will cover the organization and all corporations that contain department of human

resource and maintain all operations that perform manually.

The main purpose that we will achieve is to make operations performed easily and quickly, and

to save resources.

Actors are interacting and using this system:

1-Administrators: who are responsible to give username and password, and in our system have the

following responsibilities: login to the system, create accounts, change passwords, send messages,

modify databases and get reports.

2-Employee: A person, who uses the system and views some documents.

Receive reports and fill important data, and in our system have the following responsibilities: log in to

the system, modify documents, view states, change passwords, send messages and get reports.

3-Data entry: who is responsible for making some operations and process documents on computers

and complete his work and send the report to system Administrator.

And in our system, he has the following responsibilities: log in to the system, modify documents,

create documents, change passwords, view document states, send messages and get reports.

And for each of them there is a log in screen to allow interacting with the system.

2.5.Feasibility Study:

Feasibility study is a crucial activity that the development team must perform to determine the

practicality of the system and whether it's worth to be developed. Only after this step is completed the

development team can tackle the other steps.

Human resource management system gives the ability to employees to perform their work easily

and quickly, and to avoid chance of losing the document and to improved productivity.

10


11/35

Our team examined some feasibility areas; these areas are as the following:

Tangible benefits:

Error reduction , increase speed of activity and interactions , improve management planning and

control and save resource.

Intangible benefits:

Availability of new , better or more information , improve planning , increase productivity and

efficiency and increase flexibility in doing the jobs , since the process of retrieving documents and

updating them will be faster.

Cost:

Organization cost including Cost for buying software, training employees and pcs and network and

for developer cost maintaining and updating software and adding additional tool.

2.6Risk Management

The situation of facing some problems or threatens by some risks is possible, hence, the need for a

comprehensive risk management plan appears.

In this plan, we identified the major risks categories which might be faced during the project,

these categories are as the following:

1.Project Risk.

2.Product Risk

3.Business Risk.

Risk Identification. Technology risk : The system developed may not integrate efficiently with other

existed human resource management systems (because of technology variations).

People risk: Users may show resistance for adapting the new system or the developing

staff may change at any time

Requirement risk: The required resources may not be available all the time and the

situation of canceling a predefined requirement or the need for stating a new requirement is

possible.

11


12/35

Risk Risk Type Probability Effects Strategy

Requirements change:

There will be a

large number of

changes to the

requirements than

anticipated.

RequirementsHigh Serious

Reviewingrequirements and

update them as they

change.

Inconsistent or

incomplete

requirements.

RequirementsHigh Serious

Review the

requirements

periodically.

Time out: The expected

time may not be enough to

perform each task.

Estimation High SeriousWorking for extra

hours.

Different parts may not

integrate and software

installation may not

succeed.

Tools Moderate Serious

Well defined

interfaces between

the systems parts.

Not enough experience in

working projects and poor

skills in programming and

little knowledge of database

concepts and development

software.

People High tolerable

Making training

sessions.

Database Creation or

retrieving in an inefficient

way

Technology Moderate tolerable

Learn more about

database conceptsand efficient data

retrieval.

Types of Risk

12


13/35

2.7. Project organization :

2.8.Estimating resources and creating resources plan

Identifying the required resources for each task during the project progress is really a difficult

part of planning ,however , we make an initial estimate for the main resources required, including:

Human resources, Hardware resources ,and Software resources.

Human resources : The needed development team members are including , Project manger ,

Software engineers , System analyst , Designer , Tester and Documenter.

Hardware resources : Pcs , Network (local network) and Printer.

Software resources : Operating system , Windows XP , Microsoft Office , Oracle Developer

10g, SQL Plus and Visual Paradigm

13

HRMS

Services

Administrator Data entry

Employees


14/35

Chapter 3Project Analysis and

Design

14


15/35

Chapter 3 : Project Analysis and Design

3.1. Introduction :

System analysis is a complex process whereby computer-based information systems are developed

and maintained. The most important analytical skills are problem identification, analyzing, and solving

using different analytical tools such as Use Case Diagrams

The main activities involved in analyzing the system are

-Determining system requirements.

-Structuring system requirements.

-Selecting the best alternative design strategy.

.Determining System Requirements: 3.2

1-Requirements elicitation methods:

1.Interviews: the main technique used togather requirements from the users is direct interviews.

2.Web searching: is the second technique which we depend on strongly, to determine and collect

our system requirements.

.Requirement:3.3

3.3.1User requirement:

Functional requirements:

1.The system shall have employee who has account created by administrator.

2.The system shall have manager who has special account with additional privileges.

3.The system shall have administrators with their account who have priority to control the system.

4.The administrators of the system shall be the only ones who are responsible for adding,

modifying, or deleting employees accounts.

5.The administrator shall be able to add news, events, changes depends on manager

recommendation.

6.The employee shall be able to access the system via LAN network only.

7.The data entry shall be only responsible of receiving information to create the document.

8.The system shall allow the employee to change his profiles (Like change the account password.(

15


16/35

3.3.2System requirements:

Functional requirements:

1. The system shall be able to deal with four types of users: system administrators,

employees, and Data Entry.

2. The system shall provide good authentication subsystem that allows each user to enter

his account and give permission for the authorized users.

3. The system shall include resources such as: hardware, operating system and basic

computer application.

4. The managers should be able to view the state of the document.

5. The mangers shall be able to view the employees state.

Non-Functional requirements:

1- Security issue : the system must be secured that forbid unauthorized people or staff cant

gain access to the system . Every subsystem shouldnt allow staff from other subsystem to

modify its data .

2- User friendly: the system must be simple and clear for the users to help them do what they

want.

3- Effectiveness: we must keep a backup for all the information in the server .

4- The quick access and Provision of the required services.

5- Reliability: The application must validate user entries in order to ensure that no errors are

encountered. If a certain error shows up, the error must be displayed in a well structured way in

order to allow the users to easily understand it.

6- Evolution: The application must be designed and constructed in a way which makes it open to

expansion.

16


17/35

Chapter 4Process Modeling

(DFD)

17


18/35

Chapter 4 : Process Modeling (DFD):

Context diagram.

Level 0:

18

System

administrator

Human resource

system

EmployeeData entry

0.1

Log in

0.1

Log in

0.1

Log in

Human

resource

Employee Data Entry

Adminstrato


19/35

Level 1:

19


20/35

Level 2 :

20

0.3.0

Display page

0.3.2

Changing

password

0.3.4

Get report

0.3.5

Sending

message

0.3.6

Crating new

document

System Database

Employee Database

System user

D2

D1

0.3.3

Viewing

document

0.3.7

Modify

document

Employee Database

0.3.1

Create event

Data Entry


21/35

Level 3:

21

0.4.0

Display page

0.4.1

Modify

document0.4.3

View state

0.4.5

Changing

password

Employee DatabaseD2

0.4.4

Send

message

0.4.2

Get report

Employee


22/35

4.1.Requirements Model:

-Identification of actors whos interacting with our system:

System administrator:

-Login to the system.

-Change password.

-Send message.

-Modify database.

-Create account.

-Get report.

Employee:


-Modify document.

-View status.

-Change password.

-Send message.

-Get report.

Data entry


-Modify document.

-Get report.

-Change password.

-View document status.

-Send message.

-Create event.

22


23/35

4.2. System Models :

4.2.1. UML Diagram Model:

4.2.1.1 Use case Diagrams:

Use Case Diagram: A view of a system that emphasizes the behavior as it appears to outside

users. A use case diagram partitions system functionality into transactions (use cases) that are

meaningful to users.

In this part of the HRMS design we will show the general event that done by users of theHRMS system.

user name user password

employee

systemadministrator

log in

end user

Figure (4.1): shows Use case diagram for login procedure

23


24/35

l o g i n

g e t re p o r t

m o d i fy d a t a b a s e

c r e a t a c c o u n t

c h a n g e p a s s w o r d

s e n d m e s s a g e

s y s te m a d m i n i s t r s to r

Figure (4.2): shows Use case diagram for system administrator

24


25/35

l o g i n

c h a n g e p a s s w o r dm o d i f y d o c u m e n t

s e n d m e s s a g e

< < i n c l u d e > >< < i n c l u d e > >< < i n c l u d e > >

g e t r e p o r t

e m p l o y e e

v i e w s t s t u s

Figure (4.3): shows Use case diagram for employee

25


26/35

\

26


27/35

27

log in

Send message

View document state

Get reportCreate eventChangePassword

Modify document

Data Entry


28/35

Figure (4.4): shows Use case diagram for Data Entry

log in

employeeend user

adminstrstor

processing document

28


29/35

Figure (4.5): shows Use case for modifying document for all actors

4.2.1.2. Sequence Diagrams :

Sequence Diagrams: An interaction diagrams shows an interaction, consisting of a set of objects and

their relationships, including the messages that may be exchanged between them.

Sequence diagrams: show the messages objects send to each other in a timely manner.

In this part we will illustrate how the HRMS users interact with each other and with system

component.

29


30/35

systemadministrator

systemadministrator

human resourssystem

human resourssystem

system adminpage

system adminpage

creat anewaccount

creat anewaccount

user databaseuser database broadcastingevent

broadcastingevent

systememployeesystem

employee

1.viewing

2.login

3.username&pass

4.verfiying

5.success

6.viewing

7.display

8.select crate event

9.fill the form

10.add new user

11.success message

12.select broadcasting event

13.select event

14.broadcast

15.success message

Figure (4.6): shows Sequence diagram for some actions that are performed by system administrator

30


31/35

employeeemployee human resours

system

human resours

system

creating new

account

creating new

account

viewing

document

viewing

document

process

document

process

document

document

database

document

database

1.viewing

2.login

3.username&pass

4.verfiying

5.success

6.creating new document

7.add new document

8.success message

9.view document

10.info request

11.info

12.process

13.info reques

14.success message

Figure (4.7): shows Sequence diagram for some actions that are performed by employee

31


32/35

Figure (4.8): shows Sequence diagram for some actions that are performed by data entry

4.3. Entity Relation Diagram (ER)

32

enduserenduser human resourse

system

human resourse

system

enduser pageenduser page processingprocessing document

database

document

database

1.viewing

2.login

3.username&pass

4.verfiying

5.success

6.viewing

7.display

8.modifying document

9.requested document

10.view document

11.processing

12.update document

13.success message


33/35

Figure (4.8): shows Entity Relation Diagram

Conclusion and Further Work

33


34/35

This Project is intended to convert all paper based companies to computer based ones , and do some

jobs that are more accurate and more reliable by computers than hand job .

There is a lot of modification can be done on this system like

1- Adding a hardware to register attendance of employees .

2- Connect this system to the internet and allow it to send emails to employees that alert them

about their leaves and vacations .

3- Develop a web application and connect it with this system to allow all employees to explore

their salaries , leaves , attendance ,etc

34


35/35

References :

1- Gennick Jonathan, Oracle SQL Plus; The Definitive guide , OReilly , 2006 .

2- Kevin Loney, Bob Bryla , Oracle Database 10g Handbook , McGraw-Hill , 2005 .

3- Curtis HK Tsang , Clarence SW Lau , Ying K Leung , Object-Oriented Technology , McGraw-

Hill , 2005.

4- Ian Sommerville , Software Engineering , Pearson, 2010 , Edition 9th .

5- Wikipedia , http://en.wikipedia.org/wiki/Wikipedia.
http://en.wikipedia.org/wiki/Wikipediahttp://en.wikipedia.org/wiki/Wikipediahttp://en.wikipedia.org/wiki/Wikipedia

hrms project peport

Documents