Professional Documents
Culture Documents
1 .YitayishAyichle--------------------------2060/08
2. Eriko Bekele-------------------------------1641/09
3. AbiyotEbabu------------------------------1276/09
4. Mitikuwerkineh-------------------------1243/09
5. Chalachewmarew-----------------------1455/09
1|Page
Abstract
This system document is prepared for employee requirement management system of KIOT and
concerned with the description of the existing Human Resource management system and
different types of models used to model the new system under study. Web based human resource
management system mainly provides effective and fast data processing and controlling of
personnel. This web based system of managing human resource in our University setting is
expected to help various services keep an updated data on the status of their employee personal
information. In designing such a system, PHP has been engaged as a development language and
MySQL as a backend database with CSS implemented for the interface. Generally, the main goal
of online human resource management system is to shorten data-processing time, to reduce
errors, to improve the accuracy of input and to provide data reliability of the personnel. Commented [u2]: Now,you can ‘t put here the abstract of your
project.It should be include after completing your project.
2|Page
Table of Contents
Acknowledgment .................................................................................................................................... 1
Abstract................................................................................................................................................... 2
Chapter one ............................................................................................................................................. 8
1.Introduction .......................................................................................... Error! Bookmark not defined.
1. 1. Background of the organization ....................................................................................................... 8
1.2. Background of the project ................................................................................................................. 8
1.3. Statement of problem ........................................................................................................................ 9
1.4Objectives of the Project ..................................................................................................................... 9
1.4.1. General Objectives ..................................................................................................................... 9
1.4.2. Specific Objectives .................................................................................................................. 10
1.5. Feasibility study of the project ........................................................................................................ 10
1.5.1. Economic Feasibility................................................................................................................ 10
1.5.2. Technical Feasibility ................................................................................................................ 12
1.5.3. Operational Feasibilities ........................................................................................................... 13
1.5.4. Schedule Feasibility ................................................................................................................. 13
1.6. Scope of the Proposed System ........................................................................................................ 14
1.7. Significance of the Project .............................................................................................................. 15
1.8. Methodology .................................................................................................................................. 15
1.8.1. Data collection technique ......................................................................................................... 15
1.8.2. System development tools ........................................................................................................ 16
1.8.2.1. Hardware tool.................................................................................................................... 16
1.8.2.2. Software tools ................................................................................................................... 16
1.8.3. System Analysis and Design Approach .................................................................................... 16
1.9 Communication Plan ....................................................................................................................... 17
CHAPTER TWO .................................................................................................................................. 17
2.Description of the existing system and requirement gathering ............................................................. 17
2.1. Introduction of the existing system .................................................................................................. 17
2.3. Major functions of the Existing System ........................................................................................... 19
2.4. Supplementary Requirements.......................................................................................................... 19
2.4.1 Business Rules .......................................................................................................................... 19
2.4.2. Constraints ............................................................................................................................... 20
2.5. Report generating in the existing system ......................................................................................... 20
3|Page
2.6. Bottlenecks of the existing system .................................................................................................. 20
2.6.1. Performance ............................................................................................................................. 20
2.6.2. Input and Output ...................................................................................................................... 21
2.6.3. Security and Control ................................................................................................................ 21
2.6.4. Efficiency ................................................................................................................................ 21
2.7 .proposed solution for the new system .............................................................................................. 21
2.8. System Requirement Specification of Proposed System .................................................................. 21
2.8.1. Functional requirements ........................................................................................................... 21
2.8.2. Non-functional requirements .................................................................................................... 22
2.9. Modeling the existing systems ........................................................................................................ 22
2.9.1. Essential Use case diagram ...................................................................................................... 22
2.9.2. Essential User Interface Prototyping ...................................................................................... 24
2.9.3. Essential User Interface Prototyping flow diagrams ............................................................... 27
2.9.4. Domain modeling with class responsibility collaborator (CRC) ............................................. 29
Chapter Three........................................................................................................................................ 34
3.System Analysis (Modeling the Proposed System) .............................................................................. 34
3.1. Introduction .................................................................................................................................... 34
3.2. Modeling Proposed Systems ........................................................................................................... 34
3.2.1. System use case diagrams ................................................................................................... 34
3.2.2. Use case documentation ........................................................................................................... 37
3.2.3 Sequence diagram ............................................................................................................. 53
3.2.4 Activity Diagram................................................................................................................ 62
3.2.5 Analysis level class diagram (conceptual modeling) ........................................................... 71
3.2.6 User Interface Prototyping .................................................................................................. 72
Reference .............................................................................................................................................. 74
4|Page
List of tables
5|Page
List of figures
6|Page
List of abbreviations
ID: Identifier
7|Page
Chapter one
1. Introduction
8|Page
order to solve this issue; we have developed a web based human resource management system.
The completed project solves the problems that had affected the human resource management
offices. Since it is online it reduces a lot of costs, time to travel to the offices, work over load
and it minimizes the space used to store the data. Online human resource management system
enables to register applicant’s online, online announcement, delete, update employees’ data, and
online registration.
9|Page
1.4.2. Specific Objectives
In order to achieve the general objective of the project the following specific objective are
proposed.
• To create well-organized database that store employees’ information.
• Study and analyse the limitations of the existing system.
• To record and manage large number of employee’s and its details.
• Requirement analysis of the existing system.
• To develop a system that makes retrieval of data in easy way.
• The system has GUI interface and very less user-training is required to learn it.
• This project is economically feasible because its anticipated benefit is greater than
the expected cost.
Tangible costs
A. Miscellaneous cost
This cost contains the various types of costs in which we spent for the development of the project
or the University covers some of the hardware expenses. The following table lists the different
miscellanies costs that we have spend in the process of the development of the system.
10 | P a g e
Table 1.1.Miscellaneous cost
For this particular project we will have use different software but the software is provided by the
university.
11 | P a g e
Table 1.2.Software development cost
Intangible costs
Those are costs which are uncountable .The intangible costs that are acquired in developing the
system are:-
• Our knowledge that we will spent to develop the system may not be measureable in terms
of money.
12 | P a g e
1.5.3. Operational Feasibilities
It determines how the system satisfies the organizations need and it also offers Secure, accurate
and efficient system to the organization.
The system in which we have developed is also compatible to all operating systems and web
browsers.
13 | P a g e
Table 1.3.Time schedule for our project
Oct 2019 Nov 2019 Dec 2019 Jan 2020 Feb 2020 Mar 2020 Apr 2020 May 2020 Jun 2020
ID Task Name Start Finish Duration
10/6 10/13 10/20 10/27 11/3 11/10 11/17 11/24 12/1 12/8 12/15 12/22 12/29 1/5 1/12 1/19 1/26 2/2 2/9 2/16 2/23 3/1 3/8 3/15 3/22 3/29 4/5 4/12 4/19 4/26 5/3 5/10 5/17 5/24 5/31 6/7 6/14 6/21 6/28
• Online announcement process: - the HR admin announces the vacant position to the Commented [u3]: Change it in to ‘online vacancy
announcement.’
applicant.
• Online Registration of Applicants: - the applicant registers on online system. Commented [u4]: Change it in to ‘online Applicant Registration’
• Manage employee profile: - HR manager manage the new employee as well as the
existing ones. Commented [u5]: Change it in to ‘Manage Employee profile’
14 | P a g e
• Managing employee attendance: - it deals a company’s strategic actions to reduce
employee absences so that workers are consistently present to do their jobs, working
productively for the benefit of the organization.
• Report generation: - department can generate reports to human resourceadmin with the
system.
1.8. Methodology
Methodology of a project is a technique of gathering information from the required place to
analysis the current problem of the system.
15 | P a g e
Interview
We have gathered the information from the human resource management officer by asked
questions what and how they work in the human resource office.
Questionnaires
Questionnaires are written set of questions that are given to people in order to collect facts or
opinions about something. We have prepared questioners for the Human Resource Management
System officer to study the existing system and develop the new system.
• Microsoft word: - To publish the proposal and other parts of the project.
• Power Point: -We use it to present our presentation in short and brief way.
• EDRAW Max, enterprise architecture, and viso: - we use those software to draw
UML diagrams like use case diagram, sequence diagram and activity diagram.
• My SQL server: This software will used for designing Database or to create database.
16 | P a g e
It is better way to construct, and manage the objects that are implemented in our
system.
This approach is necessary for reuse concepts of inheritance.
Used to add new feature on the system.
In object oriented analysis phase our team will use case modeling to model the
function of the system, find and identify the business objects, organize the objects and
identify the relation between them and finally model the behavior of the object.
CHAPTER TWO
HR manager:-
• View report
• Generate report
17 | P a g e
• Receive all the attendance forms from every department
• Approve leave
Dean
• View report
• Generate report
Duty scientific director:-
• View report
• Generate report
HR officer
• View report
• Post vacancy announcement on the board
• Generate report.
Department
• Employee requisition
• Recruit applicant based on their CGPA
• Give the exam to recruit applicant
• Select applicants based on their result
• Send report to human resource manager manually
• Take attendance of employees that works only in their office in manual way
except lecturer.
• Manage employee information
• View leave application (Accept or reject leave)
Employee:-
Applicant:-
18 | P a g e
• Search job
Since every organization is made of people, HRM is all about acquiring services of people,
developing their skills, motivating them to the foremost level and making sure that they continue
to maintain their commitment towards the organization.
In short, HRM is concerned with the management of employees from recruitment to retirement.
19 | P a g e
Business rules of post vacancy announcement
2.4.2. Constraints
Constraint means anything that challenges to do our project properly. We expect the following
constraints may encounter while doing the project.
• The unavailability of data source (such as shortages of internet connection) on time may
extend the project completion time.
• Limited Knowledge of the group members.
• Lack of reference books. We can manage this problem by using other methods like
internet.
• Shortage of Time. We managed such problem by using additional time from our rest time.
2.6.1. Performance
The existing system’s performance is slow. Since the existing system is manual, the time
required to perform the activities is too much. The existing system’s response time is very slow
and it processes activities slowly.
20 | P a g e
2.6.2. Input and Output
In the existing system, the input of information is redundant, inaccurate, not well organized and
inflexible and these inputs may lead to create confusion and work load on employees and
produce inaccurate output since the information is written by pen and on paper.
2.6.4. Efficiency
Due to the manual operation most of the activities are prone to wastage of resources like papers,
man power, time etc. to produce the corresponding outputs. This makes the current system
inefficient while utilizing resources.
• Posting announcements: the system post vacancy announcements and notice for the
applicants in order to make them informed.
21 | P a g e
• Online Registration of Applicants: The system registers applicants’ who wants to be
hired in the institution with appropriate information. Without coming to the office they
can be able to register online by using the system.
• Managing employee attendance: The system manages the attendance of employees.
• Manage employee profile: The system is able to search, delete and update the hired
employee information when it is needed.
• Report generation: the system is able to generate a report for each employee based on
the information in the database.
• the system is responsibly fast in order to access the required crime information’s
22 | P a g e
Commented [u6]: Is there any existing system we are using in
kIoT?If your answer is no,How you dvelopusecase diagram for the
Usecase diagram of existing system manual system?and what is the benefit to design for that?
Receive
attendance
Dean
Approve leave
Manager
approve selected
applicant
View report
Duty
Generate report scientific
director
HR officer
Sign attendance
Post vacancy
announcement
Apply for leave
Employee requisition
Employee
select applicant
Recruit applicant
Take attendance
23 | P a g e
2.9.2. Essential User Interface Prototyping
A technology-independent prototype created using paper that can be used to identify UI
requirements.
Figure 2.2.Essential User Interface Prototyping for post vacancy announcement form
24 | P a g e
Figure 2.3..Essential User Interface Prototyping for applicant register form
25 | P a g e
Figure 2.4.Essential User Interface Prototyping for employee attendance
26 | P a g e
2.9.3. Essential User Interface Prototyping flow diagrams
27 | P a g e
Human resource management
HR Duty scientific
HR officer Dean Department employee
manager director applicant
generate
approved report
selected
applicant
take
attendance
manage
employee
accept or reject
leave
28 | P a g e
2.9.4. Domain modeling with class responsibility collaborator (CRC)
CRC modeling is a collection of standard index card that have been divided into three sections:
• The CRC table is provided from essential use case diagram. We take the actors as a class
When we draw CRC modeling, we identify the class Such as: HR manager, Employee, HR
officer, Applicant, Dean, Duty scientific director and department.
29 | P a g e
Table 2.1.class responsibility collaborator for manager
HR manager
Name Employee
Duty scientific director
Age
Department
Sex HR officer
Applicant
Phone number
Address
View report()
Generate report()
Table 2.2.class responsibility collaborator for HR
Receive attendance() officer
Approve leave()
Approve selected
applicant()
HR officer
Name HR manager
Applicant
Age
Sex
Phone number
Address
View report()
Generate report()
30 | P a g e
Table 2.3.class responsibility collaborator for Applicant
Name HR officer
Department
Age
HR manager
Sex Dean
Phone number Name Department
Address Duty scientific director
Age
CPGA Sex
Department Phone number
Search job() Address
View available vacancy View report()
announcement() Generate report()
Register to the open position()
View the screening info()
31 | P a g e
Table 2.5.class responsibility collaborator for Department
Department
Name Dean
HR manager
Age
Applicant
Sex Employee
Phone number
Address
Employee requisition ()
Recruit applicants based on
their CGPA()
Give exam()
Select applicants based on their
result()
Generate report()
Take attendance()
Manage employee
information()
View leave application()
32 | P a g e
Table 2.6.class responsibility collaborator for Duty scientific director
Name Dean
HR manager
Age
Sex
Phone number
Address
View report()
Generate report()
Employee
Name Department
Age HR manager
Sex
Phone number
Address
Education level
Id
Department
Sign attendance()
View leave approval ()
Apply for leave()
33 | P a g e
Chapter Three
3.1. Introduction
This chapter deals with analyzing the proposed system by using different UML analysis
modeling techniques. Such as: use case diagrams, use case descriptions (scenarios), sequence
diagrams, activity diagrams, analysis class diagram, and user interface prototype.
After identifying the actors and use cases, the use cases are developed and textual descriptions
(scenarios) are stated. The sequence diagram depicted based on the use cases which are
developed for the proposed system. Activities will be represented by the activity diagrams.
In the proposed system, the use case describes a sequence of action that provides a measurable
value to an actor and draw as a horizontal ellipse. An actor is a person that places a role in one or
more interaction with the system.
The major actors that are involved in the proposed system are the following:
HR admin:-
• View report
• Leave approval
• Send notification
• Manage account
HR manager:-
34 | P a g e
• Manage employee profile
Department:-
• Generate report
Employee:-
• Sign attendance
Applicant:-
• Online register
35 | P a g e
Table 3.1.use case identifier
Login UC-1
Logout UC-17
36 | P a g e
Use case diagram of proposed system
Manage <<inherit>> Create
account View leave
<<inherit>> application
<<inherit>> Accept
Delete <<inherit>>
<<inherit>>
Post vacancy
Reject
announcement Send employee
<<include>> <<include>> leave Departm
Update
ent
<<include>> <<include>>
Generate report
<<include>>
Approve leave <<include>>
Admin Login
View available
<<include>> <<include>>
vacancy
announcement
Send notification
<<include>>
<<include>>
<<include>>
<<extend>>
<<include>>
View report Register Applican
<<include>>
t
<<include>> <<include>>
Logout
Sign attendance Manage
attendance
Register
Update
Search <<inherit>>
37 | P a g e
Table 3.2.Use case documentation for Login
38 | P a g e
Table 3.3.use case documentation for manage account
Use case Name Manage account
39 | P a g e
Table 3.4.use case documentation for send notification
Use case Name Send Notification
40 | P a g e
Table 3.5.use case documentation for view report
41 | P a g e
Table 3.6.use case documentation for leave approval
Actors Admin
Basic course of action Step1: click view leave application page from
menu.
42 | P a g e
Table 3.7.use case documentation for manage employee profile
43 | P a g e
Table 3.8.use case documentation for post vacancy announcement
Admin
Basic course of action Step1: click post announcement page from menu.
Alternative course of action If the user does not select the file to be post the
system display error message. And go to step3.
44 | P a g e
Table 3.9.use case documentation for manage generate report
45 | P a g e
Table 3.10.use case documentation for apply for leave
46 | P a g e
Table 3.11.use case documentation for online register
47 | P a g e
Table 3.12.use case documentation for view vacancy announcement
48 | P a g e
Table 3.13.use case documentation for sign attendance
49 | P a g e
Table 3.14.use case documentation for send employee leave
50 | P a g e
Table 3.15.use case documentation for view leave approval
51 | P a g e
Table 3.16.use case documentation for view leave application
52 | P a g e
3.2.3 Sequence diagram
The sequence diagram is used primarily to show the interaction between objects in the sequential
order that interaction occur. The main purpose of sequence diagram is to define event sequence
that result in some desire outcome. The sequence diagram is draw from the use case description
especially from basic course of action and alternative course of action of use case.
53 | P a g e
Login form Validator() Database
User Home page Login page
6.Validate()
7.If(incorrect)try again()
9.If(correct)submit successfully
10.Check()
54 | P a g e
Admin
Admin page Create account form Validator() Database
8.If(valid)submit succesfully()
9.Check()
55 | P a g e
Admin page Delete account form Validator() Database
::Admin
1.Select delete account link()
8.If(valid)submit succesfully()
9.Check()
56 | P a g e
Admin
Admin page Post announcement form Validator() Database
«requirement»
Post announcement 1.Select post announcement link()
1.Select post announcement link()
2.Display form() 2.Display form()
3.Select the file to post()
4.Submit()
5.Validate()
6.If(empty)try again() 3.Select the file to post()
7.Repeat step 2 &3()
8.If(!empty)submit succesfully()
9.Posted succesfully() 4.Submit()
5.Validate()
6.If(empty)try again()
8.If(!empty)submit succesfully()
9.Posted succesfully()
57 | P a g e
Figure 3.5.Sequence diagram for post vacancy announcement
«requirement»
Leave application Departm
ent
1.Leave application link() Employee page Leave application form Validator() Database
2.Display form()
3.Fill the form()
4.Submit() 1.Leave application link()
5.Validate()
6.If(empty)try again() 2.Display form()
7.Repeat step 2 &3()
8.If(!empty)submit succesfully()
9.Leave application submitted succesfully()
3.Fill the form()
4.Submit()
5.Validate()
6.If(empty)try again()
8.If(!empty)submit succesfully()
58 | P a g e
Admin page Send notification form Validator() Database
Admin
5.Validate()
6.If(empty)try again()
8.If(!empty)submit successfully
59 | P a g e
Department Department page Generate report form Validator() Database
5.Validate()
6.If(empty)try again()
8.If(!empty)generate successfully
60 | P a g e
«requirement»
Register
1.Click home page()
2.Display registration form()
3.Fill the form()
4.Submit()
Applicant
5.Validate() Home page Registeration form Validator() Database
6.If( inccorect) try again()
7.Repeat step 2&3() 1.Click home page()
8.If(correct) submit successfully()
9.registersd successfully()
2.Display registration form
4.Submit()
5.Validate()
6.If(incorrect)try again()
8.If(correct)submit successfully()
9.Registered succsssfully()
61 | P a g e
3.2.4 Activity Diagram
Activity diagram is another important diagram in UML to describe dynamic aspect of the
system. Activity diagram is basically a flow chart to represent the flow of information one
activity to another activity.
62 | P a g e
act Use Case Model
No
is correct
Yes
63 | P a g e
act Use Case Model
Admin page
click create
account link
display create
account form
click submit
button
No
is correct
Yes
create account
successfully
64 | P a g e
act Use Case Model
Admin page
click on
announcement link
select browse
click submit
button
Yes
is empty
No
announcement
posted
successfully
65 | P a g e
act Use Case Model
Employee page
click leave
application page
display leave
application form
click submit
button
No
is correct
Yes
display
successfully
message
66 | P a g e
act Use Case Model
applicant browse
the system
click vacancy
announcement link
display the
vacancy
information
view vacancy
announcement
successfully
67 | P a g e
act Use Case Model
select applicant
registration page
display regitration
form
click submit
button
No
is correct
Yes
display register
successfully
68 | P a g e
act use case model
Admin page
Click notification
link
Display
notification form
click submit
button
No
is correct
Yes
Notification send
successfully
69 | P a g e
act use case modl
Manager page
Click registration
link
Display
registration form
No is correct
Yes
Registered
successfull
70 | P a g e
3.2.5 Analysis level class diagram (conceptual modeling)
It Shows the class, interrelationship (including inheritance, aggregation and association), and the
operations and attributes of the classes.
Adimin Report
View
1 *
Name Report_type
Id 1 Manage Report_date
Sex
Address
Phone number
Generate report()
View report() view report()
Post vacancy announcement()
Leave approval() *
Send notification()
Manage account() * Generate
1 *
Account
Department
Post 1 1
User name Has
* User Id Name
Password Id
Vacancy announcement User type Sex
Address
Announcement type Create account() Phone number
Registration_start_date Delete account() Generate report()
Registration_ end_ date Update account() View report()
1 1
post()
view()
*
Has Has
Post 1
1
Manager
Emloyee
Name
* Name
Id Manage 1 Id
Applicant Sex
Sex
Address
Name Address
Phone number
Sex Phone
Manage number
employee profile()
Department
Age Manage attendance()
CGPA Sign attendance()
Department Apply for leave()
Qualification
*
View vacancy announcement()
Register() Sign
1 1
Attendance
Attendance_date
Attendance_ time
Sign attendance()
Manage attendance()
71 | P a g e
Figure 3.18.Analysis level class diagram
72 | P a g e
Figure 3.20.User Interface Prototyping for applicant registration
73 | P a g e
Figure 3.21.User Interface Prototyping for employee attendance
Reference
[3].Jeffery A.Hoffe, Joey F.George, Joseph S.Valacich, Modern System Analysis And Design,
4th edition
[4].David Jung, Pierre Boutquin, John D.Conly III, Loren Eidani, Lowell Maller, Jack Purdum,
The White Group’s Visual Basics 6 Super Bible, Fourth edition.
74 | P a g e