Human Resource Management System For Jju

HUMAN RESOURCE MANAGEMENT SYSTEM FOR JJU
Table of Contents
List of tables..................................................................................................................................IV
Abstract..........................................................................................................................................VI
Acknowledgement........................................................................................................................VII
CHAPTER ONE.............................................................................................................................................1
1. INTRODUCTION.......................................................................................................................................1
1.1 Background.......................................................................................................................................2
1.2 Statement of the problem...................................................................................................................2
1.3 Objectives of the project....................................................................................................................3
1.3.1 General objective........................................................................................................................3
1.3.2 Specific objectives......................................................................................................................3
1.4 Scope of the project...........................................................................................................................3
1.5 Limitation of the Project....................................................................................................................4
1.6 Methodology.....................................................................................................................................4
1.6.1 Data collection............................................................................................................................4
1.6.2 Analysis and design....................................................................................................................5
1.6.3 Development tools......................................................................................................................5
1.7 Significant of the Project...................................................................................................................6
1.8 Risk assessment and management.....................................................................................................6
1.9 Operating Environment.....................................................................................................................7
1.9.1 Hardware Requirement...............................................................................................................7
1.9.2 Software Requirement................................................................................................................7
1.10 Document organization....................................................................................................................7
CHAPTER TWO............................................................................................................................................9
2. DESCRIPTION OF THE EXISTING SYSTEM................................................................................................9
2.1. Introduction......................................................................................................................................9
2.2. The main activities............................................................................................................................9
2.3. The function of the existing system..................................................................................................9
2.4. Players of the existing system.........................................................................................................10
2.5. Report generating in the existing system........................................................................................10
CET DEPARTMENT OF COMPUTER SCIENCE Page 1

2.6. Document used in existing system..................................................................................................10

2.7. Strength of the existing system.......................................................................................................11
2.8. Weaknesses of the existing system.................................................................................................11
2.9. Alternative solutions.......................................................................................................................12
CHAPTER THREE........................................................................................................................................13
3. REQUIREMENTS SPECIFICATION AND ANALYSIS..................................................................................13
3.1. Introduction....................................................................................................................................13
3.1.1 Purpose.....................................................................................................................................13
3.1.2 Intended Audience and Reading Suggestions...........................................................................14
3.1.3 Document convention...............................................................................................................14
3.2. Objective........................................................................................................................................15
3.3. Functional Requirements................................................................................................................15
3.4. Product perspective.........................................................................................................................16
3.5 Product Functions............................................................................................................................16
3.6. Principal Actors..............................................................................................................................16
3.7 User characteristics..........................................................................................................................16
3.8 General Constraints.........................................................................................................................17
3.9. Assumptions and Dependencies.....................................................................................................18
3.10. Non Functional Requirements......................................................................................................18
3.11. System Models.............................................................................................................................19
3.11.1. Use case Models...................................................................................................................19
3.11.2. Use Case Descriptions...........................................................................................................20
3.11.3. Sequence Diagrams................................................................................................................26
3.11.4. Class Diagram........................................................................................................................38
CHAPTER FOUR.........................................................................................................................................39
4. SYSTEM DESIGN....................................................................................................................................39
4.1 Introduction.....................................................................................................................................39
4.2 Design goals....................................................................................................................................39
4.2.1 Performance criteria..................................................................................................................39
4.2.2 Maintenance criteria.................................................................................................................40
4.2.3 End user criteria........................................................................................................................40

4.3 System Architecture.............................................................................................................40

4.4. Subsystem Decomposition..................................................................................................41
4.4.1. Login subsystem...........................................................................................................42
4.2.2. Generate report.............................................................................................................42
4.4.3. Search subsystem.........................................................................................................42
4.4.4. Register subsystem.......................................................................................................42
4.5. Deployment Diagram (hardware/ software mapping)........................................................43
4.6. Persistent Data Management...............................................................................................44
4.7 User interface design............................................................................................................45
CHAPTER FIVE.........................................................................................................................48
IMPLEMENTATION AND TESTING.....................................................................................48
5.1. Introduction.........................................................................................................................48
5.2. Algorithm Design / Coding.................................................................................................48
5.3. Testing.................................................................................................................................70
5.3.1 Unit Testing...................................................................................................................70
5.3.2. Integration Testing.......................................................................................................70
5.3.3. System Testing.............................................................................................................70
5.4.1 Hardware Requirements................................................................................................71
5.4.2. Software Requirements................................................................................................71
5.5 User Manual.........................................................................................................................71
5.6. Installation...........................................................................................................................71
CHAPTER SIX............................................................................................................................72
CONCLUSION AND RECOMMENDATION.........................................................................72
6.1. Conclusion..........................................................................................................................72
6.2. Recommendation................................................................................................................72
REFERENCES:...........................................................................................................................73

List of tables
Table 1 Recorded Data of employees form...................................................................................10
Table 2 Transfer of employee form...............................................................................................11
List of Figures
Figure 1 Use case diagram for Human Resource Management system........................................20
Figure 2 Sequence diagram for login.............................................................................................27
Figure 3 Sequence diagram for register.........................................................................................28
Figure 4 Sequence diagram for update employee information......................................................29
Figure 5 Sequence diagram for view schedule..............................................................................30
Figure 6 Sequence diagram for search employee information......................................................31
Figure 7 Sequence diagram for create employee account.............................................................32
Figure 8 Sequence diagram for post vacancy................................................................................33
Figure 9 Sequence diagram for remove employee account...........................................................34
Figure 10 Sequence diagram for prepare schedule........................................................................35
Figure 11 Sequence diagram for generate report...........................................................................36
Figure 12 Sequence diagram for modifying personal account......................................................37
Figure 13 Class Diagram...............................................................................................................38
Figure 14 System architecture.......................................................................................................41
Figure 15 deployment diagram......................................................................................................43
Figure 16 persistent data management diagram............................................................................44

Figure
17 user interface diagram 45
Figure 18 user interface diagram for Admin page 46
Figure 19 user interface diagram for employee page....................................................................46
Figure 20 user interface diagram for employee page....................................................................47
Figure 21 Sample testing for create account..................................................................................71

Abstract
This Human Resources Management System is a intranet application developed for Jigjiga
University. (The system is designed to computerize the manual process with the use of web
intranet application.) To develop this software the team members (Graduate students of
Computer science) will collect reliable data about the University and conduct the procedures
starting from planning, and justification of the system. This project examines the issues related to
Jigjiga University Human Resource Management system. This project objective is devoted to be
Intranet based Jigjiga university human resource management system and also to keep employee
information in efficient, reliable and secured way, minimize time wasted to get services, get
employee information as quickly as possible from the system. The system would provide basic
set of features to register employees, view schedule, and create account, post vacancy.

Acknowledgement
The first and for most thanks will be for our advisors dr. Francis and Mr. Hashim for their
valuable supportive ideas to develop this project. And also the effective continuation support.
In addition, we would like to forward our special words of gratitude to Jigjiga University Human
Resource Management employees who helped us by providing information and giving useful
documents that are appropriate for our project.

CHAPTER ONE
1. INTRODUCTION
Today most applications are changed in to online. This helps to
 Increase the qualities of the work
 Reduces the complexities of tasks
 Keeps the security of data in most advantageous condition
 Data transfer makes more easily, and others.
Human resource management (HRM or simply HR) is a function in an organization designed to

maximize employee performance in service of their employer’s strategic objectives. The main
function of Human resource management system is
 Registering new employee
 Post vacancy
 Sending to scholarship
 Resignation of employee by any means
 Conducting interview for the new employee.
A Human Resources Management System (HRMS) or Human Resources Information System
(HRIS) refers to the systems and processes at the intersection between human resource
management (HRM) and information technology. It merges Human Resources Management as
a discipline and in particular it’s basic Human Resource activities and processes with the
information technology field. The HRMS proposed here is developed to work in an intranet.
An intranet is a computer network that uses Internet Protocol technology to
 Share information
 Operational systems or computing services within an organization.
This term is used in contrast to extranet, a network between organizations, and instead refers to
a network within an organization. An intranet may host multiple private websites and constitute
an important component and focal point of internal communication and collaboration. Any of
the well known Internet protocols may be found in an intranet, such as
 HTTP (web services)
 SMTP (e-mail)
 FTP (file transfer protocol).

1.1 Background
Jigjiga University is among one of the universities in Ethiopia. It is located at jigjiga town in
east of Ethiopia 628 kilo meters far away from Addis Ababa about 2 kilo meters from the city of
jigjiga. The university was started giving service in 1999E.C.The university was branch of
Haramaya university. After two years the university became independent just like other
university. This university gives service for the member of it. This university contains only one
main campus. It has hierarchal management style. From the hierarchal management human
resource management is located at the fourth level. In this university there are a number of
employees that are located based on their qualification in order to achieve university’s desire and
give service for the society of the university.
1.2 Statement of the problem

The existing system of Human Resource Management System activities is manual, so it is
difficult to manage all employee details. This manual System has the following problems:
 Wastage of time
As a result of employee information are not arranged in a defined manner, it is much difficult to
find a record associated with specific employee. Beside the time wasted workers assigned to
these offices may get Bored, giving not suitable service to the employee.
 Low Performance
The current system has working low level of data organized because the system works all things
in manually documented. Also, the response time to the employee is very slow; because they use
manual system.
 Control and Security

 Since the existing system is manual it is difficult to maintain the employee data.
 Unauthorized person can modify employee information .Because the employee data
are simply stored on the shelf (hardcopy) where anybody can change the status of
the employee record.
 Poor file keeping system

Because of employee information are being written on paper, they may be damaged or someone
may pick them out from the shelf intentionally or unintentionally.
 Low Efficiency
Recording all information by manually takes a lot of time and it may be confusing.
 Poor collection of Information and Data

 Data is not accurately captured, it may contain errors.
 Data may be redundant.
 It is difficult to produce the required information from the manually document file.
 Since the data of the employees are not maintained in a database it may be lost.
1.3 Objectives of the project
1.3.1 General objective

The general objective of this project is to develop a dynamic human resource management
system of Jigjiga University in intranet.
1.3.2 Specific objectives

The project is expected to fulfill the following specific objectives..
 Study and analyse the current system
 Perform the modeling activities
 Design the proposed system
 Developing and testing the proposed system
1.4 Scope of the project

The Human Resource Management System of Jigjiga University is expected to provide service
for all employees in suitable manner to the human resource management of the University.
The project has the following scopes:
 Employee registration
 Updating employee account
 Search employee information

 Sending Feedback
 Deleting Employee information
 Generating report
 Posting Vacancy
1.5 Limitation of the Project

Even though, this project focuses on Human Resource Management System for Jigjiga
University, it doesn’t handle pay roll system, new recruitment training exit interview etc..
1.6 Methodology
1.6.1 Data collection

Observation
Enables us to list out the existing system problems, as it is what we see or observe in reality.
Interview
We will gather the information by interviewing the human resource management employees
about the existing Human resource management system. The questions we prepare will be open
ended. We choose this type because we can get detailed information about the current system
and also not to limit the available responses for the question.
Document analysis
Documents are one of the basic sources for the project development. Relevant documents and
techniques help to improve the proposed system. To have detailed awareness about the related
project we will use documents such as
 Books
 e-books
 Websites to develop the project.
During the analysis of documents, we will consider those documents that can bring more
features to the system.

Questionnaires
We will prepare questioners for the Human Resource Management System to study the existing
system and develop the new system.
1.6.2 Analysis and design
To understand and express the essential and interesting feature of an application in the complex
real world, an object oriented model is built around objects. We will use the unified modeling
language (UML) for designing of this project. The unified modeling language (UML) is an
object oriented language for
 Specifying
 Visualizing
 Constructing
 Documenting the artifacts of software systems.
Because UML uses simple intuitive notation, nonprogrammers can also understand UML
models. The UML notation is useful for graphically depicting object oriented analysis and
design models.
1.6.3 Development tools
Hardware:
 Desktop computer
 RAM 4GB
 467GB hard disk
 Laptop
 Flash
 CD-ROM
Software:
 Microsoft Office Word 2007

 Operating System: Window 7
 Microsoft office Visio 2003
 Php, Mysql

 Java script,Css
 Google chrome
 Dreamweaver
1.7 Significant of the Project

The new system is expected to bring visible changes in the Human Resource Management
system. It will document the employee information in an organized manner.
The project will have the following significant:-
Beneficiaries for the campus:
 In order to minimize number of workers
 Reduces data loss.
 Make the system secure from unauthorized user
 It reduces the wastage of time during searching and modifying employee information
Beneficiaries for the users:
 Satisfy employee needs
 Avoid load of work of the employee
 Very fast and accurate.
Beneficiaries for the group:
 To get experience and knowledge to solve problems
 Technological advancement
1.8 Risk assessment and management

In the development of our project there may be problems that may affect the project progress.
Such as:
 Virus attack in the computer:

 Computer failure-hardware
 Shortage of Electric power
 Shortage of Internet access
We will minimize these problems by the following methods:

 For virus infection we will duplicate files in more than two computers, backup files on
CD-RW and external devices in order to resist problem.
 By updating the antivirus software.
 We can minimize problem of Internet access by using internet cafes.
1.9 Operating Environment

An operating environment is the area where a program is capable of being run.
1.9.1 Hardware Requirement

Client side:
 Any computer
Server side:
 Processor- 64-bit, four-core, 2.5 GHz minimum per core
 RAM- 16 GB for production use
 Hard disk-80GB
1.9.2 Software Requirement

Client side:
 Operating System: any
 Browser software
Server side:
 Server operating system

 Mysql
 Php
1.10 Document organization

The project organization involves five chapters. Among them chapter one is proposal of the
project that includes:-
 Introduction and Background
 Statement of problem

 Objectives and Methodology
 project scope and Limitation
Analysis phase is the second chapter that includes:-

 Description of Existing system
 Document used
 Activities and functions

The third chapter is design of the project which contains
 Class diagram
 Deployment diagram
The forth chapter is design of the project which contains

 Purpose and goals of design
 System Architecture
 Deployment diagram
The final chapter includes

 implementation and testing

CHAPTER TWO
2. DESCRIPTION OF THE EXISTING SYSTEM
2.1. Introduction
This chapter deals with analyzing
 The purpose
 Goals
 Objectives and Function of the existing system.
It produces a broad outline of the proposed system that identifies the function to be performed
and the technical aspects that the system must fulfill and briefly describe the existing system
functionality, problem of the existing system. The Human Resource staff store their document in
manual system. Even though the Human Resource Recorder has no enough facilities, it is
providing service with the high effort of the workers.
2.2. The main activities

 Promotion of employee due to their qualification and the service they gave
 Test the new employees due to the qualification that needed
 Giving orientation for the new employees that pass the test
 After registering agree with new employees in personally and organizational issues
 Evaluate employee every six months to increase their efficiency
2.3. The function of the existing system

 Registering new employee
 Post vacancy
 Generate required report

 Updating registered employee profiles

 Higher education
 Promotion
 Transfer employees
 Deleting of employees
 Resignation
 Terminated
2.4. Players of the existing system

 Recorder (clerk)
 Human information system expert
 Human resource personnel officer
 Employee
2.5. Report generating in the existing system

In the existing system the report is generated as the requirement of the organization department.
The organization asks the responsible worker to provide report. As we observed and also
interview the human resource management department the report generating mechanism is
manual, that is any kind of report is delivered by worker and then it will be transformed to whom
it may concerns. It provides in week, month and year.
2.6. Document used in existing system

Ethiopian Academic Staff Data Collection sheet (on duty in 2007)
University JIG-JIGA University
School/college/Faculty /institute College of Engineering & Technology
Education Department
/program Teaching
Field of /unit service Semester
Level study /school/subject Year at credit

S.No. Sex He(E.C) hours
he
(she)Teaches

Full Aca
Name demi
c
Ran
k
1
2
3
4
Table 1 Recorded Data of employees form
S.No. Name Sex Field of Program University Department

study Ta
ble 1 2
2
3
4
Transfer of employee form
2.7. Strength of the existing system

Even if the human resource management has no capacity to fulfill all of its requirements
alongside this the human resource management has the following strength:-
 The human resource management arranges the employee information by their

qualification and authority which makes somewhat easier to search for a employee
 Uniquely specify employee’s status by their id
 assign id for employees

2.8. Weaknesses of the existing system

The existing system of human resource management system activities is difficult for manager to
manage all employee details since it is done manually. This manual human resource management
has many drawbacks:-
 Wastage of time and cost.

 Errors occurred due to carelessness.
 The details information of the employee is traditionally paper based and maintained
on paper.
 Need of extra manual effort to manage employee.
 It used to take much time to find any employee information.
 Not accurate.
 Danger of losing the files in some cases.
 Mostly the data of the employee are stored on excel sheet.
2.9. Alternative solutions

To overcome the problems of the current system that exists in the operation of the HRM, our
project group members have put down alternative solution. These are:
 Changing the whole current system in to computerized system without affecting the
structure of the existing system. Developing the human resource management system
for the university on intranet. We choose this one because it has the following
advantages:
 Accessible anytime
 Platform independent: it is accessible in any operating system.

CHAPTER THREE
3. REQUIREMENTS SPECIFICATION AND ANALYSIS
3.1. Introduction
Requirement gathering is a way of collecting information to improve or change the existing
system by the new system. Requirement is a major base for better solution or for solving
problem which exists in the current system by gathering requirement.
The new system is based on the interest and understanding of the users. The sequence of
activities which are performed in the current system also impacts the development of new
system. To work in accordance with the interest of users and working process of current system
there must be a clear understanding of the following:
 How activities are performed?
 What current system requires?
 What are the problems that the current system faces?
 What improvement should be done to make it a better system?
Having such kind of understanding helps us to distinguish modules which are going to be
changed in the new system and to determine how proposed system can solve the current
problems and also able to design other new features which are user interactive.
To gather the information we used interviews and reviewing document (forms, reports). In
addition to the above two methods we observed how they perform their activities in the current
system.
3.1.1 Purpose
Analyzing the current system and making requirement determination helps to develop a system
which includes necessary information and source for different activities. Some of the purposes of
analyzing manual system are:-
 To distinguish current problems in different categories based on the case and to find
solution to each. In case of finding solution we analyzed which part of the existing manual
system has to be converted into new computerized system.
 To design and develop different type of files, forms and report generating system based on
manual activity.
3.1.2 Intended Audience and Reading Suggestions

Since we are developing Human Resource Management System, more concern is given for the
users that are employees of the Jigjiga University. So that we have prepared and presented the
existing system work flow and the optional analysis of our proposed system and we have got the
following suggestions from the employees:
The proposed system is:-
 More easily understandable and also reliable
 Decreases wastage of time that have been faced waiting for register
 Introduce to the new technology
 It is sophisticated
Beside employees we have also given our proposed system for the HRM staff since they are also
part that will be affected by the system. After analyzing our proposed system they have given the
following suggestions:-
The proposed system is:
 Efficient because the proposed system eliminate redundancy
 Easy to learn and work with
3.1.3 Document convention

HRMS……………………….Human Resource Management System
JJU……………………………Jigjiga University
SRS……..……….Software Requirement Specification
UML……………………………………Unified Modeling Language
UC………………………………………Use Case
DB……………………………………...Database
EMP…………………………….Employee
Info………………………………………Information
UI…………………………………………User Interface

PHP……………………………………… Hypertext Preprocessor
Vaca………………………………………Vacancy
Num………………………………………Number
SQL………………………………………Structured Query Language
HTTP……………………………………Hyper Text Transfer Protocol
HTML……………………………………….Hyper Text Markup Language
HRM……………………….Human Resource Management
HR Recorder……………………….Human Resource Recorder
3.2. Objective
The objective of this phase is to develop the requirement specification and analysis as it started
from last section by using the information planned. The requirement specification is the phase
that leads to the designing and implementation; that the correct and accurate designing has a
great role to the system implementation. Based on this designing our target, providing the
automated system to the Human Resource Management, be attained with the rapidly developing
technologies. The system is to be beneficiary of this by applying the possible technology results
as much as possible.
3.3. Functional Requirements

Functional requirements are the intended behaviors of the system. This behavior may be
expressed as services, tasks or functions that the system is required to perform.
 Registration of employees: register new employees to the system
 Generate report: The system support registrar officer to generate report about detail of
employee profile.
 Prepare schedule: the system should Prepare Schedule.
 Login: for validating users

 Search information: retrieving information from the database

 display Information: show information from the database
 Comment: The system accepts comment from user.

 Create Account: The system able to create account users.
3.4. Product perspective

The proposed Human Resource Management system which will be developed by the project
team member is intranet application. This system will provide registration of employees to users
of the Human Resource Management system. Furth+er the HRM can perform update, delete, and
insert employee information as needed. Lastly the system has report generating mechanisms for
operations performed in the registration.
3.5 Product Functions

The new system is expected to have the following functionalities:
 Make search for a specific employee.
 Accept feedback
 Create users and grant their functions based on their privileged level in the system.
 delete the information of employees from the database
3.6. Principal Actors

An actor represents anything or anyone that interfaces with your system. This may include
people, external systems, and other organizations. An actor initiates a use case and receives
something of value from the use case. Actors are always external to the system being modeled
Those are:
 Administrator
 HR Recorder
 Employee
3.7 User characteristics

User characteristics are about people who are going to use the system. Users are classified based
on their skill in to Naive and sophisticated users. Naive users are users who have little
knowledge about the functionalities of the systems. Sophisticated users are users who have

enough knowledge about the functionalities of the system, they even write their own queries and
programs. In our case most of the users are inexperienced.
 Educational level: Users should be comfortable with the English language.
 Experience: Users should have prior information regarding the online registration and
view grade report.
 Skills: Users should have basic knowledge and should be comfortable using general
purpose applications on computers.
 Beside these we have also made aware of the technology that we are using for
developing the system. So that now at this moment there is no any kind of being strange
problem faced.
3.8 General Constraints

The constraints that fetches for the proposed system are:
 All operations are in English so user must have basic knowledge of English.
 Employees cannot delete or update any records from the database.
 Age of employee must be positive integer.
 The system must give and assign each user a unique user ID and password
 Every user must be comfortable using computer.
 The system must validate every process such as: id, name, age, phone number and other
records.
 Normally a Jigjiga University use manual process and activity. Automating this all with
short period of time seems to be difficult. So, it takes more time to be automated
 The other risk is the price of materials may arise and fall. Therefore budget may modify
in negotiation. In addition after implementation, if the software fails to run how to fix is
negotiable.
The main risk that should be taken in to consideration, during the development of the project, is
securing the project from unauthorized access (user). To overcome such risks we are going to
develop a password protection method that gives access to authorized person only. The other is
data loss which is caused by virus infection. To prevent this problem, virus and worms infection,
we will install a current updated antivirus. In addition to installing the updated antivirus, we will
take back up of our documents.

3.9. Assumptions and Dependencies

 The users have LAN connection whenever they want to use the product.
 The employees have some minimal knowledge Of the English language.
 Administrator has full privilege on the system.
 The employees have a valid his/her ID number and his/her password.
3.10. Non Functional Requirements

This requirement does not directly affect the system but their presence is useful for the system. A
non-functional requirement relates to the technical aspects of system must fulfill, such as
performance, security, user interface and reliability issues.
Some of the non-functional requirements are: -
Security issues:-The system must be protected from unauthorized users. To protect employees’
data and system misuse, the system should provide restriction in using system functionality and
information access by its user.
Robustness: The system shall validate data entry and prompt the user when the invalid data is
entered
Computer viruses: since the system will be using in every computer of authorized person
viruses can be carried internally and externally to our system. Possible measures that can be
taken include:
 Scanning all external storage media for viruses before use.

 Installing and using the latest antivirus and providing regular update to the software.
 HRM system checking and updating virus definitions.
 Use password to login to the system.
Maintenance: the parts of the system answer the question that raised due to some kinds of the
problem.
Availability: - The system should easily be available to authorized users at any desired time.
Performance: - The system should be well fit to perform operations clearly without any
problem or the system should be avoiding bottle neck situations.

User friendly/ system interface: the system interface that will be developed must be
interactive and easily understandable.
3.11. System Models
3.11.1. Use case Models

A use case model is one of the Unified modeling language that indicates an interaction between
users and a system. It captures the goal of the users and the responsibility the system to its users.
It is the functionality of the system or the service provided by the new system. The main purpose
of a use case model is to show what system functions are performed for which actor.

Figure 1 Use case diagram for Human Resource Management system.
3.11.2. Use Case Descriptions

Use case documentation includes text descriptions of processes with sections like Actors,
Precondition, post Condition, flow event and alternative action.
1. Use case name: Login

Use case Number:-UC-01
Actors:-Admin, HR Recorder, Employee
Description: - validates the users to enter into the system.
Precondition:-the user must have valid user name and password.

Post condition: The users logs in to the system.

Basic course of action:-
1. The user browse home page.
2. The system displays the login form to the user.
3. The user fills user name and password.
4. The user submits to the system.
5. The system checks the login information whether it is valid or not.
6. The user gets user profile.
7. Use case ends.
Alternate course of actions A: invalid username and password
A.5.The system validates user name and password.
A.6.The system informs the invalidity to the user.
A.7.The user restarts from step 3.
2. Use case name: register

Actors:-HR Recorder
Description: - register new employees
Precondition:-the user must have valid user name and password.
Post condition: The user registers the employees
1. A valid user selects new employee registration form from main menus.
2. The system displays the Registration Form.
3. The user fills the form
4. The system validates filled data.
5. The user saves to the data base
Alternate course of actions A: invalid employee data is blocked.
3. Use case name: update employee information

Actors:-HR Recorder, Admin
Description: - changing employee information

Precondition: - the employee record must be exist.

Post condition: The user changes the employee information
1. The valid user selects employee update form from main menus.
2. The system displays the update Form.
5. The user saves changes to the data base
Alternate course of actions:
A.4.The system validates filled data.
A.5.The system informs invalidity to the user.
A.6 The use case restarts from step 3.
4. Use case name: view schedule

Actors:-Employee
Description: - allow the user to view the schedule
Precondition: - the schedule must be posted
Post condition: the system display the schedule
1. The valid user selects view schedule form from main menus.
2. The system displays the view schedule Form.
3. Use case ends
Alternate course of actions
A.1. the system checks the privilege of the user, whether it is valid or not.
A.3.The use case restart from step login.
5. Use case name: search employee information

Actors:-HR Recorder, Admin, employee
Description: - retrieving employee information

Precondition: - the employee record must be exist.

Post condition: display the employee information
1. The user selects employee search form from main menus.
2. The system displays the search Form.
3. The user enters id number or name of employees the form
4. The system validates the employee id or name
5. The system displays the employee information.
6. Use case ends
A.4. the system validates the employee id or name
A.5.The use case restart from step 3
6. Use case name: create employee account

Actors:-Admin
Description: - adding new employee account
Precondition: - the user must have administrative privilege
Post condition: The user adds new account
1. The user selects create account form from main menus.
2. The system displays the create account Form.
3. The user enters required information
5. The user saves to the database
6. Use case ends
A.4. the system validates filled data.
A.6.The use case restart from step 3.
7. Use case name: post vacancy


Actors:-Admin
Description: - posting a vacancy to employees
Precondition: - the user must have administrative privilege
Post condition: The user posts the vacancy
1. The user selects post vacancy form from main menus.
2. The system displays the post vacancy Form.
3. The user enters required vacancy want to post
5. The user saves to the database
8. Remove employee account

Actor(s): Administrator
Precondition: user should have administrative privilege
Description: Allow user to remove employee account
Post Condition: employee account removed
Basic course of actions
1. User clicks on remove form from the main menu
2. The user type employee ID and submit to system.
3. The system validates employee id.
4. The system removed employees account.
5. Use case end.
Alternative course of action: If user enters invalid username and password then the system
display error message. The user can choose to return to the beginning.
9. Use case name: prepare schedule


Actor(s): Registrar officer

Description: allow the user to prepare the schedule
Precondition: The user must be logged onto the system before this use case begins
Basic course of action
1. The user selects prepare schedule form
2. The user fills the information
3. The system validates the entered data
4. The user saves the data to data base
5. The use case ends
Alternative course of action:

10. Use case name: Generate report

Actor(s): Registrar officer
Precondition: If the manager wants any report or request for report.
Description: Allow user to generate report
Post Condition: report will be generated
Basic course of actions
1. The system display report type to the user.
2. The user clicks on the report type and submits to the system.
3. The system prepares the report and displays to the user.
4. Use-case ends.
Alternative course of action: If user enters invalid username and password then the system
display error message. The user can choose to return to the beginning
11. Use case name: modify personal account

Actors:-HR Recorder, Admin, Employee
Description: - modifying user name and password

Precondition: - the personal account record must be exist.

Post condition: The user changes the personal account
1. The valid user selects modify account form from main menus.
2. The system displays the modify account Form.
5. The user saves changes to the data base
Alternate course of actions:
A.4.The system validates filled data.
A.6 The use case restarts from step 3.
3.11.3. Sequence Diagrams

A sequence diagram in a Unified Modeling Language (UML) is a kind of interaction diagram
that shows how processes operate with one another and in what order. A sequence diagram
shows object interactions arranged in time sequence. It shows the objects and classes involved in
the scenario and the sequence of messages exchanged between the objects needed to carry out
the functionality of the scenario.

Figure 2 Sequence diagram for login.

Figure 3 Sequence diagram for register

Figure 4 Sequence diagram for update employee information

Figure 5 Sequence diagram for view schedule

Figure 6 Sequence diagram for search employee information

Figure 7 Sequence diagram for create employee account

Figure 8 Sequence diagram for post vacancy

Figure 9 Sequence diagram for remove employee account

Figure 10 Sequence diagram for prepare schedule

Figure 11 Sequence diagram for generate report

Figure 12 Sequence diagram for modifying personal account

3.11.4. Class Diagram
Figure 13 Class Diagram

CHAPTER FOUR
4. SYSTEM DESIGN
4.1 Introduction
Systems design is the process of defining and developing a system to satisfy specified
requirements of the user. Designers in all disciplines draw on fundamental design concepts and
principles. This document describes the requirements for developing the Human Resource
Management System for the Jigjiga University.
4.2 Design goals

The goal of this project is to develop Human Resource Management System for the University,
based on the input about employee registration, view the schedule. Different conditions have to
be satisfied by the final System and which have been specified in the SRS. This document
specifies the final system design for the system.
The overall system design goal is to provide an efficient, modular design that will reduce the
system’s complexity, facilitate change and result in an easy implementation. This will be
accomplished by designing strongly cohesion system with minimal coupling. In addition, this
document will provide interface design models that are consistent user friendly and will provide
straight forward transition through the various system functions.
4.2.1 Performance criteria

Performance, dependability, and end user criteria are usually specified in the requirements or
inferred from the application domain. The customer and the supplier (developer) dictate cost and
maintenance criteria.
Performance criteria: - performance criteria include:
 Response time, the speed imposed on the system. The system should responsive
maximum number of tasks with minimum times.
 Number of tasks accomplished in a fixed period of times.
 Memory space available for speed optimizations should be used efficiently.

4.2.2 Maintenance criteria

When we say the system is maintainable, we mean it can be maintained easily when changes
arise from the user and designer/developers it is not only when changes arise but also when we
consider the non-functional requirement. We prepare full maintenance document and attach with
the web content then the end user can maintain the fall of the system easily by using the
maintenance manual or document. And also by using online help or contact us end user can
communicate with the maintenance group of the system and can get any help that able him to
maintain the failure.
4.2.3 End user criteria

This is to mean the users of the system after the completion of the system, how the system is
used in friendly manner for both the experienced and inexperienced users using the user interface
and this is clearly stated in the users’ documentation. For example if the employee wants to view
his/her schedule and familiar with computer first he must get account from administrator and
then simply he /she logged in to our system and then select view schedule then the schedule will
be displayed. But if the user doesn’t have any experience on how to use the system then he/she
can use the contact us/Help link. Then he can get full information about use of the system in
order to perform the required activity/operation.
4.3 System Architecture

The Human Resource Management System is a system which contains major part which includes
employee Detail. The user selects one of the available options as an input to the system.
According to the input by the user the system acts and the rest of the functions are performed
accordingly. The administrator can operate on any employee details. But the normal employee or
users can only access their details of all the functionalities.

Figure 14 System architecture
4.4. Subsystem Decomposition

These are the working area of the project after the completion of total process. In the sub system
decomposition we can see the different components emanated from system architecture that
collaborate to handle single application at a time.
When the operator runs the intranet application, the user interface appears by preceding login
screen. Next to login screen is the main page that supports other operational directories. The
different subsystems have a coupling to complete entire process.

4.4.1. Login subsystem

This subsystem checks whether the user is valid or not. It consist of the authentication,
authorization, and password functionalities of the system.
4.2.2. Generate report

The report subsystem consists of all functionalities of the system that produce report concerning
employee information. The reports might be in a paper form or data grid depending on the type
of report.
4.4.3. Search subsystem

Search subsystem assists all subsystems whenever identification and allocation are needed by the
subsystems.
4.4.4. Register subsystem

The registration subsystem consists of the functionalities of registering or Data Entry in to the
system, insert employee information and Update employee information.

4.5. Deployment Diagram (hardware/ software mapping)
Figure 15 deployment diagram

4.6. Persistent Data Management
Figure 16 persistent data management diagram

4.7 User interface design

User interface design is the design of computers, appliances, machines, mobile communication
devices, software applications, and websites with the focus on the user's experience and
interaction. The goal of user interface design is to make the user's interaction as simple and
efficient as possible, in terms of accomplishing user goals.
The user interface of the Human Resource Management is representing the way in which the
users of the system interact with the system.
Sample user interface for home page
Figure 17 user interface diagram

Sample user interface for Administrator page
Figure 18 user interface diagram for Admin page
Sample user interface for employee page
Figure 19 user interface diagram for employee page

Sample user interface for hr recorder page
Figure 20 user interface diagram for hr recorder page

CHAPTER FIVE
IMPLEMENTATION AND TESTING
5.1. Introduction
The Implementation phase in the software life-cycle is where the actual software is implemented.
The result of this phase consists of source code, together with documentation to make the code
more readable. This is what we call software implementation. The purpose of these activities is
to convert the final physical system specification into working model with reliable software and
hardware, document the work that has been done, and provide help for current and future users
and take care of the system.
5.2. Algorithm Design / Coding

For controller class member function algorithm are designed. This design enables to see every
steps and flow of logic in each function. This design part is important in the coding part of
implementation. Some of the algorithms are:
Algorithm for deleting schedule
updatevac : is used to update vacancy.
Precondition: vacancy data should be selected.
Post condition: vacancy data will be updated.
BEGIN
Login as admin
Search the vacancy from database
If the vacancy is available in the database
SEECT the authorization table
DISPLAY the vacancy data

Select the schedule to UPDATE
UPDATE vacancy data
Else
Display Error No such record exists
Algorithm for login
Go to home page
Fill user name and password and select the role in the login page
If the filled input is valid
Display User main page
Else
Display Error Message and return to the login page
Sample coding
<?php
error_reporting(0);
require_once 'header.php'?>
<div class="bdy g-100 pg-warp">
<div class="g-100 pg-title">

<p> </p>
<div class="main">Update Vacancy</div>
<div class="sub bold">| </div>
</div>
<div> <p> </p>
<form method="post" action="updatevac.php" class="frm">
<b>Enter Vacancy No or Job Type : <input type="text" name='ss' title="Please Enter

Vacancy No or Job Type">
<input class="s-g-100 btn other" type="submit" name="search" value="search">


<form>
<b/>
<?php
function search()
mysql_connect('localhost','root','');
mysql_select_db('jjuhrm');
@$ele=$_POST['ele'];
$q = "select * from vacancy where no='".$_POST['ss']."' or emptype='".$_POST['ss']."'";

$r=mysql_query($q);
//echo "r=".$r;
$nr=mysql_num_rows($r);
if($nr==0)
{echo"<br />No such record exists"; require_once 'footer.php';exit();}
else echo "


    <br />Total no. of records: ". $nr;
?>
<table class="g-100">
<thead>
<tr>
<th></th>
<th>No</th>
<th>Employment Type</th>
<th>Job Type</th>
<th>Exprience Required</th>
<th>Qualification</th>
<th>Starting</th>
<th>Ending</th>

</tr>
</thead>
<tbody>
<?php
for ($i = 0; $i < mysql_num_rows($r); $i++)
$row= mysql_fetch_row($r);
//print_r($row);
echo "<tr><td><a
href=\"updatevac.php?updatevacedit=1&no='$row[0]'\">UPDATE</a></td><td>$row[0]</
td><td>$row[1]</td><td> $row[2]
</td><td>$row[3]</td><td>$row[4]</td><td>$row[5]</td><td>$row[6]</td></tr>";
?>
</table>
<?php

?>
<?php
function updatevacform()
@$no=$_GET['no'];
mysql_connect('localhost','root','');
$sql="SELECT * FROM vacancy WHERE no=$no order by no";
$result = mysql_query($sql)or die(mysql_error());
$row = mysql_fetch_array($result);
?>
<div style=" font:Geneva, Arial, Helvetica, sans-serif;margin-left:10px; margin-

right:10px; border:1px;box-shadow: 3px 3px 10px 2px #888888; border- ridge; padding:15px
15px 2px 5px; border-radius:7px; margin-top:5px; text-align:justify; background-
color:#ECF1EF">
<form method="post" action="updatevac.php" class="frm">
Vacancy NO.= <?php echo $row[0] ?>
<input type="hidden" name="no" value="<?php echo $row[0]?>" />

<div class="g-100 g-parent">
<label class="g-15 s-g-100">Employment Type :</label> <input

class="g-40 s-g-100"
type="text" name="emptype" value="<?php echo

$row[1]?>" title="Please Enter only Letters" pattern="[A-Za-z\\]+"/>
</div>
<label class="g-15 s-g-

100">            &
nbsp;  Job Type :</label> <input
class="g-40 s-g-100" type="text" name="jobtype"

title="Please Enter only Letters" pattern="[A-Za-z\\]+"
value="<?php echo $row[2]?>"/>
</div>
<label class="g-15 s-g-100">Exprience Required :</label> <input

class="g-40 s-g-100"
type="text" name="exp" value="<?php echo $row[3]?

>" />

</div> <div class="g-100 g-parent">

100">          Qualification
:</label> <input
class="g-40 s-g-100" type="text" name="qual"
value="<?php echo $row[4]?>" />
</div>

100">          Starting Date
:</label><br /> <input class="g-40 s-g-100"
type="date" name="start" value="<?php echo $row[5]?

>" />
</div>

100">          Ending Date :</label>
<br /><input class="g-40 s-g-100"
type="date" name="end" value="<?php echo $row[6]?>"/>

</div>
<div class="g-100 g-parent btn-cnt">
<label class="g-15 s-hdn s-g-100"></label>
<div class="g-40 s-g-100 g-parent">
<input type="submit" class="s-g-100 btn primary"

value="Update" name="update"/>
<input type="reset" class="s-g-100 btn other"

value="Cancel"/>
</div>
</div>
</form>
<?php
?>

<?php
function updatevacedit()
mysql_connect('localhost', 'root','');
$sql="
UPDATE `vacancy`
SET
èmptype` = '".$_POST['emptype']."',
`jobtype` = '".$_POST['jobtype']."',
èxprequired` = '".$_POST['exp']."',
`qual` = '".$_POST['qual']."',
`start` = '".$_POST['start']."',
ènd` = '".$_POST['end']."'
WHERE `no` = '".$_POST['no']."';
";
//echo "\$sql = '$sql'<br>\n";
mysql_query($sql) or die(mysql_error());

?>
<?php
function message()
echo
"





   ";
echo "

            Update
Success";
?>
<?php

function main()
require_once ("../../config.php");
// check the user based on his role to access this page
if ($_SESSION ['role'] != "admin") {
header("location:../../index.php");exit();}
if(@$_POST['search']) {search();require_once 'footer.php';exit();}
if(@$_GET['updatevacedit']==1) {updatevacform();require_once 'footer.php'; exit();}
if(@$_POST['update']) {updatevacedit();message();require_once 'footer.php'; exit(); }
main();require_once 'footer.php';
?>
///////
<?php

require_once ("config.php");
$_SESSION['role']="";
?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"

"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
<meta http-equiv="content-type" content="text/html; charset=iso-8859-1" />
<meta name="description" content="your description goes here" />
<meta name="keywords" content="your,keywords,goes,here" />
<meta name="author" content="Your Name / Original design by Andreas Viklund -

http://andreasviklund.com/" />
<link rel="stylesheet" type="text/css" href="style.css" media="screen,projection"

title="style (screen)" />
<link rel="stylesheet" type="text/css" href="print.css" media="print" />
<title>JJU HRM</title>
<link rel="icon" type="image/png" href="image/logo.png"/>
<style type="text/css">

</style>
</head>
<body>
<div id="container">
<div id="desc"></div>
<div id="navitabs">
<h2 class="hide">Site menu:</h2>
<a class="activenavitab" href="index.php">Home</a><span class="hide"> | </span>
<a class="navitab" href="Vacancy.php">Vacancy</a><span class="hide"> | </span>
<a class="navitab" href="Feedback.php">Feedback</a><span class="hide"> | </span>
<a class="navitab" href="About us.php">About us</a><span class="hide"> | </span>

<a class="navitab" href="login.php">Login</a><span class="hide"> | </span>
<a class="navitab" href="help.php">Help</a>
</div>
<div id="main">
<h2 align="center"> </h2>
<h2 align="center" class="style3">Welcome to JJU HRM </h2>
<p></p>
<div style=" font:Geneva, Arial, Helvetica, sans-serif;margin-left:90px; margin-

right:60px; border:1px;box-shadow: 3px 3px 10px 2px ; border- ridge; padding:15px 15px 2px
25px; border-radius:5px; margin-top:5px; text-align:justify; background-color:#858585">
<form name="myform" action="<?php echo

PATH?>php/login.php" method="post" class="frm" >
<div class="g-100 <?php echo

isset($_SESSION['error'])? 'rl':''?> mrgn10-t pdng10 bold">
<?php echo isset($_SESSION['error'])?

$_SESSION['error']:''?>
<h4>Login</h4>
</div>

<label ><b>User name</label>

<input style="margin-left:20px display:inherit; border:1px solid grey;
border-radius: 5px;width:180px; height:25px; background-color:#FFFFFF;" class="g-

100"
type="text" name="uname"
required="required" title="Enter User Name"
placeholder="User name">
<br/>
<br/>
<label > Pass word </label> <input

style="margin-left:20px display:inherit; border:1px solid grey;
border-radius: 5px;width:180px; height:25px; background-color:#FFFFFF; class="g-100"
type="password"
required="required" name="pass" class="g-100" placeholder="Pass word" title="Enter Pass
Word">
<br/><br/>
<label >
   <b>Role</b> </label>      <select
required="required" name="role"class="g-100" style="margin-left:20px display:inherit;
border:1px solid grey;

border-radius: 5px;width:180px; height:25px; background-color:#FFFFFF;" title="Select

the role" >
<option value=""> Select

Role</option>
<option
value="admin">Admin</option>
<option
value="employee">employee</option>
<option value="hrrec">hr
recorder</option>
</select>
<p> </p>
<br/> <br/>
<div class="g-100 s-g-100 g-

parent">

     <input type="submit" value="Login" style="margin-
left:20px display:inherit; border:1px solid grey;
border-radius: 5px;width:80px; height:25px; background-color:lightgrey;" name="login"

class="s-g-100 fright btn primary" />

<input type="reset" class="style4"

style="margin-left:20px display:inherit; border:1px solid grey;
border-radius: 5px;width:80px; height:25px; background-color:lightgrey;"

value="Clear"/>
</div>
</form>
<p> </p>
</div>
</div>
<div id="sidebar">
<h3> </h3>
<h3>Main Menu:</h3>
<p>
<a class="sidelink" href="index.php">Home</a><span class="hide"> | </span>
<a class="sidelink" href="Vacancy.php">Vacancy</a><span class="hide"> | </span>
<a class="sidelink" href="Feedback.php">Feedback</a>
<a class="sidelink" href="About us.php">About us</a><span class="hide"> | </span>
<a class="sidelink" href="login.php">Login</a>
<a class="sidelink" href="help.php">Help</a>
</p>
<h3>Navigations:</h3>

<p><a href="https://www.facebook.com/pages/JJUhrms/445990882234144?ref=hl"
target="_blank"><img class="photo" src="images/facebook.jpg" height="26" width="156"
alt="facebook" /></a></br><a href="https://twitter.com/jjuhrms1" target="_blank"><img
class="photo" src="images/twitter.jpg" height="29" width="156" alt="twitter" /></a></p>
<h3>Contact Info:</h3>
<p><img class="photo" src="images/test.jpg" height="51" width="156" alt="" /></p>
<p>Location: JIGJIGA</p>
<p>
<p1>Email:jjuhrm@gmail.com</p1>
</p>
<p>
<p1>Phone:+251-920-55-7994</p1>
</p>
<p>
<p1>Website:<a href="https://www.jju.edu.et">www.jju.edu.et</a><br />
<br />
</p1>
<p1>Fax: +251-920-55-79-94</p1>
<br />
</p>
</div>
<div id="footer">

<p>Copyright © 2015. All Right Reserved by JJU HRM.</p>
</div>
</div>
</body>
</html>
<?php
require_once ("../config.php");
if (isset ( $_POST ['login'] )) {
$uname = $_POST ['uname'];
$password = $_POST ['pass'];
$role = $_POST ['role'];
var_dump ( $_POST );
$conn = mysql_connect ( DB_SERVER, DB_USER, DB_PASS );
if (! $conn) {
die ( "Could not connect: " . mysql_error () );
mysql_select_db ( DB_NAME );

$sql = "SELECT * ";
$sql .= "FROM user ";
$sql .= "WHERE uname = '" . $uname . "' ";
$sql .= "AND password = '" . $password . "' ";
$sql .= "AND role = '" . $role . "' ";
$sql .= "LIMIT 1";
var_dump($sql);
$result_set = mysql_query ( $sql, $conn );
$userinfo = mysql_fetch_array ( $result_set );
if (isset($userinfo ['ID'])) {
$_SESSION['error']='';
$_SESSION['userID']=$userinfo ['ID'];
$_SESSION['name']=$userinfo ['firstName'];
$_SESSION['fullName']=$userinfo ['firstName'].' '.$userinfo ['lastName'];
$_SESSION['role']=$userinfo ['role'];
var_dump ( session_id() );
var_dump ( $_SESSION);
if ($role == 'admin') {

header ( 'Location:'.PATH.'user/admin/' );
} elseif ($role == 'employee') {
header ( 'Location:'.PATH.'user/employee/' );
} elseif ($role == 'hrrec') {
header ( 'Location:'.PATH.'user/hrrecorder/' );
}else{
header ( 'Location:'.PATH.'login.php' );
} else {
$_SESSION['error']='incorrect User Name, Pass Word or Role Please try

again';
header ( 'Location:'.PATH.'login.php' );
var_dump ( $sql );
var_dump ( $userinfo );

5.3. Testing
5.3.1 Unit Testing
All forms are separately tested means that add some data to the form and check all validity or
functionality of the system. Through this mechanism every system gets tested. If the error
occurs, correction will be taken without affecting another module.
5.3.2. Integration Testing

In this testing part, all the modules will be combined together and tested it for its fitness with
each other and with the systems functionality. If error occurs in combining them, the module
with problem will be identified and recombined. Both units testing and integrated testing are
performed by all team members at the work place.
5.3.3. System Testing

In this testing, the team performs over all functional testing by checking whether it meets the
required target or not. In this phase, we are simply trying to show a sample test case where admin
crates account on the form shown and also the database where the user information is stored also
shown.

Figure 21 Sample testing for create account

Figure 18 1 Sample testing for create account
5.4 Hardware and Software Requirements

The hardware and software we used for running this project are listed below.
5.4.1 Hardware Requirements

Computers with the following specifications
 4 GB RAM and 10GB hard disk
5.4.2. Software Requirements

The different kinds of software we used in the development of the website are:
 Wamp server
5.5 User Manual

The website developing group will give training to the administrator how to use the system and
give training for how to retrieve and check the Registered employees and how to updates data
and others. And give training for employees how to use the system.
5.6. Installation
Since the project is web application. We only need to host it on the intranet server and
give it public IP address so that it can be access by any Employee who of JJU which has web
browser and intranet connection.
CHAPTER SIX
CONCLUSION AND RECOMMENDATION
6.1. Conclusion
This chapter discusses the conclusion of the entire proposed study where in the researchers have
recommendation according to their findings. The main purpose of this project is to give online
service of viewing schedule, posting vacancy preparing schedule..
An effort has been made to study how to manage human resource management system as partial
fulfillment of BSC degree in computer science. In doing the study the team has tried to follow
object oriented system analysis and design methodology.
Since the success and failure of any system depends on gathering the right information through
different fact-finding techniques and user involvements, the team has made the best effort to
gather requirements. After a detail review and study of the existing system of human resource

system models have been designed to reflect the new system that are suppose to solve problems.
Designing computerized management system helps to maintain a computer based applications.
In order to solve different problems existed the team has tried to propose a solution that at least
reduce the existed problems and model the proposed system using different tools and
methodologies. Thus it should have the precedence in know-how and experience in collecting,
processing and utilizing information.
6.2. Recommendation
Since we are now living in a world that is led by technology and technology results, we need
more and more applications to familiarize ourselves and also come up with the fast advancing
technology. Thus, as we are beginner website developers, we recommend that other website
designers, beginners or professionals, to create more dynamic pages that are very user friendly,
more secure and also introduce the community as a whole to be familiar with the current
technology. We hope that this project will create some initiation for those people who want to
develop human resource management system.
REFERENCES:
 Jigjiga University, http://www.jju.edu.et/index.php/aboutus/baground, accessed on
11/22/14.
 Coad, Peter. Nicola, Jill. Object oriented programming. New York: McGraw-Hill (1993).
 KatipoCommunicationsLtd.[PDFdocument].Availableat:
http://www.parliaments.info/downloads/16%20KOHA%20-%20Presentation.pdf.
 Use case and functional requirements http://www.bredemeyer.com/usecases.htm
 Printed document of Jigjiga university human resource management system department

Human Resource Management System For Jju

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Human Resource Management System For Jju

Uploaded by

Copyright:

Available Formats

HUMAN RESOURCE MANAGEMENT SYSTEM FOR JJU

CET DEPARTMENT OF COMPUTER SCIENCE Page 1

2.6. Document used in existing system..................................................................................................10

CET DEPARTMENT OF COMPUTER SCIENCE Page 2

4.3 System Architecture.............................................................................................................40

CET DEPARTMENT OF COMPUTER SCIENCE Page 3

Table 1 Recorded Data of employees form...................................................................................10

Table 2 Transfer of employee form...............................................................................................11

Figure 1 Use case diagram for Human Resource Management system........................................20

Figure 2 Sequence diagram for login.............................................................................................27

Figure 3 Sequence diagram for register.........................................................................................28

Figure 4 Sequence diagram for update employee information......................................................29

Figure 5 Sequence diagram for view schedule..............................................................................30

Figure 6 Sequence diagram for search employee information......................................................31

Figure 7 Sequence diagram for create employee account.............................................................32

Figure 8 Sequence diagram for post vacancy................................................................................33

Figure 9 Sequence diagram for remove employee account...........................................................34

Figure 10 Sequence diagram for prepare schedule........................................................................35

Figure 11 Sequence diagram for generate report...........................................................................36

Figure 12 Sequence diagram for modifying personal account......................................................37

Figure 13 Class Diagram...............................................................................................................38

Figure 14 System architecture.......................................................................................................41

Figure 15 deployment diagram......................................................................................................43

Figure 16 persistent data management diagram............................................................................44

CET DEPARTMENT OF COMPUTER SCIENCE Page 4

Figure 18 user interface diagram for Admin page 46

Figure 19 user interface diagram for employee page....................................................................46

Figure 20 user interface diagram for employee page....................................................................47

Figure 21 Sample testing for create account..................................................................................71

CET DEPARTMENT OF COMPUTER SCIENCE Page 5

CET DEPARTMENT OF COMPUTER SCIENCE Page 6

CET DEPARTMENT OF COMPUTER SCIENCE Page 7

Human resource management (HRM or simply HR) is a function in an organization designed to

CET DEPARTMENT OF COMPUTER SCIENCE Page 8

1.2 Statement of the problem

 Control and Security

CET DEPARTMENT OF COMPUTER SCIENCE Page 9

 Poor collection of Information and Data

1.3 Objectives of the project

1.3.1 General objective

1.3.2 Specific objectives

1.4 Scope of the project

CET DEPARTMENT OF COMPUTER SCIENCE Page 10

1.5 Limitation of the Project

1.6.1 Data collection

CET DEPARTMENT OF COMPUTER SCIENCE Page 11

1.6.2 Analysis and design

1.6.3 Development tools

 Microsoft Office Word 2007

CET DEPARTMENT OF COMPUTER SCIENCE Page 12

1.7 Significant of the Project

1.8 Risk assessment and management

 Virus attack in the computer:

We will minimize these problems by the following methods:

CET DEPARTMENT OF COMPUTER SCIENCE Page 13

1.9 Operating Environment

1.9.1 Hardware Requirement

1.9.2 Software Requirement

 Server operating system

1.10 Document organization

 Introduction and Background

CET DEPARTMENT OF COMPUTER SCIENCE Page 14

 Objectives and Methodology