Professional Documents
Culture Documents
TRAINING INSTITUTE
Prepared By:
No Name………………………………………………………………………ID
1. Beniyam Abdulmged……………………………………………………R/951/10
2. Yohnnes Adane……………………………………………………..……R/959/10
Junary, 2021
FEDERAL TECHNICAL, VOCATIONAL, EDUCATION AND TRAINING INSTITUTE
PREPARED BY:
No. Name………………………………………………………………………ID
1. BENIYAM ABDULMGED………………………………………………R/0011/07
2. YOHNNES ADANE………………………………………………………R/0120/07
EXAMINING BOARD:
ii
ACKNOWLEDGMENTS
The success of this Project would have not been possible without the guidance and
assistance of some individuals to whom we give our deepest and profound gratitude.
First of all, we thank our almighty God, whom all the blessings and knowledge come from,
thank you our advisor Mr. Abay G. for assisting and providing us the support and the
knowledge we might needed to write this document. Secondly we would like to express our
group member to integrate different idea to do our document in different side by merging
different ability to each other and for contribution of each of them in many times.
Our parents, for their continuous support and understanding, to my friends, for their moral
support and encouragement, And to all the people who in one way or another have
contributed to make this project possible.
iii
ACRONYMS AND ABBREVIATIONS
iv
ABSTRACT
Human Resource Management System is a process of managing the overall activity of the
Employees of a certain company and it is the process of identifying the information that
needed to that organization.
Ethio-Italy Poly Technic Collage Human Resource Information Management System is
software that can be able to solve the problem that occurs in manual system by managing the
overall employee activities in the Collage. The proposed system mainly have the
significances of reducing man power, time and cost and wastage of resource.
In order to achieve the computerized system we used UML (Unified Modeling Language)
and object oriented approach to design our system and used Iterative testing methodology to
test the system. The data gathering methods which are used are interview, document analysis
and observation. We used various hardware and software technologies in order to develop
our system.
This project aims to develop a new system by fulfilling all necessary requirements that are
needed by users. The motivation of this document is to make the management of all Human
Resource activity starting from employee, applicant, manager and the activity of the admin
system process clear to understand and to create well designed system that can make the
management process more efficient and effective.
Table of Contents
CHAPTER ONE ...................................................................................................................... 1
INTRODUCTION ................................................................................................................... 1
1.1 Background ............................................................................................................... 1
1.2 Statement of the problem .......................................................................................... 2
1.3 Objectives.................................................................................................................. 2
1.3.1 General Objective .................................................................................................. 2
1.3.2 Specific Objectives ................................................................................................ 2
1.4 Scope and Limitations ............................................................................................... 3
1.5 Significance of the project ........................................................................................ 3
1.6 Beneficiary of the project .......................................................................................... 3
1.7 Methodology ............................................................................................................. 4
1.7.1 Data gathering methodology ................................................................................... 4
1.7.2 Development methodology ..................................................................................... 4
1.7.3 Development approaches ........................................................................................ 5
1.7.4 Development Tools ................................................................................................. 6
1.7.8 Testing methodology................................................................................................... 7
1.8 Feasibility study ........................................................................................................ 8
1.9 Project plan ............................................................................................................. 10
1.9.1 Project Time Schedule......................................................................................... 10
1.9.2 Project Cost ......................................................................................................... 10
CHAPTER TWO ................................................................................................................... 11
REQUIREMENT ELICITATION......................................................................................... 11
2.1 Introduction ............................................................................................................. 11
2.2 Overview of the existing system ............................................................................. 11
2.3 Existing System Business Rule ............................................................................... 11
2.4 Advantage of Existing System ................................................................................ 12
2.5 Disadvantage of Existing System ........................................................................... 12
2.6 Proposed Solution ................................................................................................... 13
2.7 Preferred Solution ................................................................................................... 13
2.8 Domain Modeling with CRC Card ......................................................................... 14
i
2.9 Essential Use Case of Existing System ........................................................................ 15
2.10 Essential Use Case Documentation............................................................................ 16
2.11 Essential User Interface Prototype ............................................................................. 18
3.1 Introduction ............................................................................................................. 20
3.2 Overview of New System ....................................................................................... 20
3.3 System Requirements .............................................................................................. 20
3.3.1 Functional Requirement................................................................................... 20
3.3.2 Non Functional Requirement ........................................................................... 21
3.4 System Modeling .................................................................................................... 21
3.4.1 System Use Case Diagram............................................................................... 22
3.4.2 Use case Documentation.................................................................................. 23
3.4.6 Use case documentation of vacancy announcement. ............................................ 26
3.4.3 System Activity Diagram ................................................................................ 32
3.4.4 System Sequence Diagram .............................................................................. 35
3.4.5 Conceptual Class Diagram .................................................................................... 36
CHAPTER FOUR ................................................................................................................. 39
SYSTEM DESIGN ................................................................................................................ 39
4.1 Introduction ............................................................................................................. 39
4.2 Proposed Software Architecture ............................................................................. 39
4.3 Subsystem Decomposition ...................................................................................... 39
4.4 System Class Diagram ............................................................................................ 40
4.5 Stat Chart Diagram.................................................................................................. 41
4.6 Collaboration Diagram ............................................................................................ 42
4.7 Persistent Data management ................................................................................... 43
4.8 Component Diagram ............................................................................................... 46
4.9 Deployment Diagram .............................................................................................. 47
CHAPTER FIVE ................................................................................................................... 50
CONCLUSION AND RECOMMENDATIONS .................................................................. 50
5.1 Conclusion .............................................................................................................. 50
5.2 Recommendations ................................................................................................... 50
REFERENCES ...................................................................................................................... 51
ii
List of Tables
TABLE 2.10.1 EXISTING ESSENTIAL USE CASE DOCUMANTATION OF REGISTER EMPLOYEE .............................................. 16
TABLE 2.10.2 EXISTING ESSENTIAL USE CASE DOCUMANTATION OF ANNOUNCE VACANCY ............................................. 16
TABLE 2.10.3 EXISTING ESSENTIAL USE CASE DOCUMANTATION OF POST EXAM SCHEDULE ............................................ 17
TABLE 2.10.4 EXISTING ESSENTIAL USE CASE DOCUMANTATION OF PLACE EMPLOYEE .................................................. 17
TABLE 2.10.5 EXISTING ESSENTIAL USE CASE DOCUMANTATION OF MANAGE DATA. .................................................... 17
TABLE 2.10.7 EXISTING ESSENTIAL USE CASE DOCUMANTATION OF TAKE EXAM. ........................................................ 18
TABLE 2.10.9 EXISTTING ESSENTIAL USE CASE DOCUMANTATION OF VIEW PLACEMENT. ............................................... 18
iii
TABLE 3.4.14USE CASE DOCUMENTATION OF APPROVE LEAVE. .......................................................................... 30
iv
List of Figures
v
CHAPTER ONE
INTRODUCTION
1.1 Background
Ethio-Italy Poly Technic Collage is a young public institution which was established by the federal
republic government of Ethiopia in 2001 E.C. Ethio-Italy Poly Technic Collage is located in the industrial
and commercial city called Ethio-Italy Poly Technic Collage located 515km east of Addis Ababa, the
capital city of Ethiopia. The Collage has opened various faculties in 2001 E.C. but in this year the faculties
has been turned to schools. The Collage has its first graduate batch in year 2003, and keeps graduating
more students in the years after. There are up to eight different faculties currently in the academic system
of the Collage. The Collage’s strategic vision of achieving to be a reputable Polytechnique College and its
mission of producing competent and well prepared graduates displaces the Collage’s focus on the Ethio-
Itally Polytechnique College which currently incorporates about ten departments
The organization has planned to provide highly accurate and fast services to the Collage community. From
those health’s care center, registrar, store, finance, compound service and so on. It is a new Collage
relatively with the old ones, however, it being new doesn’t stopped it from achieving its goal and
competing with the old ones, in such a short time it has shown a significant change both on physical growth
and organizational growth. After some years it is expected to be a high technologically best Collage if it
changes its manual system with highly accurate and fast efficient computerized system.
Mission: To produce competent graduates, demand driven innovative research and technology outputs
and community service through providing quality education, training and consultancy, conducting research
by promoting effective entrepreneurship and democratic attitude to foster socio-cultural, economic and
political transformation of the nation
Vision: Ethio-Italy Poly Technic Collage strives to be premium choice in the nation, competent in Africa
and internationally accredited Polytechnique Collage the near future.
Core values: Equality and equity, academic freedom corporate social responsibility trusted partnership,
participatory team work, client satisfactions, efficiency and effectiveness, credibility, competence,
professional integrity, trusted partnership, self-initiation and commitment to excellence.
Technology is spreading its wing in almost every walks of human life activities. Now a day it is better if
every activity is done using new technology in order to fulfill the need of human being and organization.
To use this new technology the roll of IT knowledge is very important.
The aim of this project is to develop human resource information management system that will generally
enhance the organization’s employee management system and other related information by making a new
and computerized system to improve the current system.
1
Many developing countries are in a good position to exploit the opportunity of technological revolution and
advance human development. However countries like Ethiopia are deprived of the benefits of the IT
knowledge is in its early stage.
Currently the organization is using half automated computer based system that means by word and excels
application. Human resource is a function in organizations design to maximize employee performance in
service of an employee’s strategic objectives. HRMS is primary concerned with the management of people
within organizations, focusing on systems and policies, HRMS departments and units in organization
typically undertake a number of activities, including employee’s benefits design Employee recruitment,
“training and development”, Performance appraisal, and rewarding.
1.3 Objectives
1.3.1 General Objective
The general objective of this project is to develop the web-based human resource information management
system for Ethio-Italy Poly Technic Collage.
3
temporarily register to the organization using the form on the web. Any applicant (user) that fulfills the
requirement in anywhere can participate within the system without any geographical limitation. And also
they can not to be expected in the place of the organization to see whether they are selected to be employee
of the organization or not, simply searching on the web the system.
1.7 Methodology
The appropriate methods that will be used to develop this project are data gathering, development
methodology, development approach, development tools and testing methodology in proper manner in
order to have sufficient information about the existing system and its weakness.
5
By comparing the above model our team selects iterative model, because iterative model have the
following advantages:-
In iterative model we can only create a high-level design of the application before we actually begin
to build the product and define the design solution for the entire product. Later on we can design
and built a skeleton version of that, and then evolved the design based on what had been built.
In iterative model we are building and improving the product step by step. Hence we can track the
defects at early stages. This avoids the downward flow of the defects.
In iterative model we can get the reliable user feedback. When presenting sketches and blueprints of
the product to users for their feedback, we are effectively asking them to imagine how the product
will work.
In iterative model less time is spent on documenting and more time is given for designing.
Combines benefit of prototyping and waterfall
Flexibility and re-incorporate additional requirements.
This methodology keeps the project development in track to its objectives.
Develop and deliver software in increments, in which Each increment is complete in itself
Feedback from one iteration is used in the future iterations
2.dreamweaver It’s an editor software used as a tool or environment for writing and designing html, php
and other codes
7.notepad Its text editor used to write PHP, HTML and JavaScript Programming commands and
syntaxes.
MYSQL data To store and retrieve data from the server
base
Window 7 and It is the operating system used to run the application on the server.
10
7
1.8 Feasibility study
Feasibility study is an important phase in the software development process. It enables the developer to
have an assessment of the product being developed it refers to the study of the product in terms of
outcomes of the product, operational use and technical Support required for implementing it. Feasibility
study should be performed on the basis of various criteria and parameters.
The various feasibility studies are
Economic Feasibility
Operational Feasibility
Technical Feasibility
Economic Feasibility: Economic feasibility determines whether the required software is capable of
generating financial gains for an organization. It involves the cost incurred on the software development
team, estimated cost of hardware and software, cost of performing feasibility study, and so on. For this, it is
essential to consider expenses made on purchases (such as hardware purchase) and activities required to
carry out software development.
In addition, it is necessary to consider the benefits that can be achieved by developing the software for
Human resource information management system for Ethio-Italy Poly Technic Collage. When the system
is automated it does not be require much more cost beyond the capacity of the organization by automating
the system. This is one advantage of solving problems with Human resource information management
system for Ethio-Italy Poly Technic Collage so it is economically feasible because:-The system provide
fast and efficient automated environment. 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. The
costs that the new system expenditure is as follows:-
Hardware Cost: The organization required small amount of hardware and software for the system, so no
much more cost has been incurred in implementing the system.
Manpower Cost: The proposed system is user friendly and does not require much knowledge of
computers. Thus there is no requirement of highly qualified staff in computers requiring big amounts of
salaries. Thus no extra expenditure is required for manpower. Therefore the system is financially feasible.
Maintenance Cost: The campus has their own employees that are working in the maintenance field and
they have their own monthly salary so the system does not have much more expenditure in maintaining the
resources of the system.
The benefits or outcomes we are deriving from the product compared to the total cost we are spending for
developing the product is greater. The benefits are more than the older system provides. In the present
system, the development of the new product greatly enhances the accuracy of the system.
Operational Feasibility: Operational feasibility assesses the extent to which the required software
performs a series of steps to solve business problems and user requirements. This feasibility is dependent
on human resources (software development team) and involves visualizing whether the software will
operate after it is developed and be operative once it is installed. It determines how the system satisfies the
8
organizations need and it also offers secure, accurate and efficient system to the organization. The system
in which we will have developed is also compatible to all operating systems. Operational feasibility also
performs the following tasks:-
Determines whether the problems anticipated in user requirements are of high priority.
Determines whether the solution suggested by the software development team is acceptable.
Analyzes whether users will adapt to new software.
Determines whether the organization is satisfied by the alternative solutions proposed by the
software development team.
Our project is operationally feasible because:
The HRMS workers support this project.
The system will reduce the needed time and manpower to give service.
Manager of the HRMS satisfied for this project.
Able to use and do according to the graphical user interface on the dynamic website.
The user (Applicant), employee, and administrator can operate the system easily.
The system solves the problems of the existing system.
The product is feasible in operational manner. The products work well at design, implementation and also
functional in the real time environment. The system takes consideration of the study of additional human
resource required and their technical expertise, in the present system, all the operations can be performed
easily compared to existing system and supports
Technical Feasibility: Technical feasibility assesses the current resources (such as hardware and software)
and technology, which are required to accomplish user requirements in the software within the allocated
time and budget. For this, the software development team ascertains whether the current resources and
technology can be upgraded or added in the software to accomplish specified user requirements. Technical
feasibility also performs the following tasks.
Analyzes the technical skills and capabilities of the software development team members, and determines
whether the relevant technology is stable and established.
The technical requirement for human resource management in order to do their operation by the new
computerized system is:-Training on the new system to know how it operates and how to use the
computerized system.
If the system is available in the market it fully supports users in technical manner. It provides additional
training needed to be given to the people to make the system work. In the proposed system, the user
interface is user friendly and does not require much expertise and training. This is achieved through
integration of web server and database server in the same environment.
The proposed system is technically feasible as:
This project is practically applicable with in the current technology.
The software used to implement the system is well understood by the group members.
We have technical knowledge about:
PHP used as an interface with XAMPP or WAMP.
Notepad/Notepad++ to write and edit the code.
MYSQL to build the database for storing the data.
9
Unified Modeling Language (UML) model to do analyzing and designing in good manner.
10
CHAPTER TWO
REQUIREMENT ELICITATION
a. Introduction
Describing and modeling the major functions of the existing system to identify problems in the existing
system, to provide alternative solutions for the problem identified, to select the feasible solution among the
alternative solution and finally to decide the functional requirements of the proposed new system. This
chapter presents the description of the existing employee record system of Ethio-Italy Poly Technic
Collage Human Resource Management. It presents the major functions of the existing system, documents,
forms and business rules used and reports generated by the current employee record. In addition, it presents
problems faced in the existing system, good practices to be preserved and the players in the existing
system. Alternative solutions to address the problem in the existing system, with options analysis, are also
part of the things discussed in this chapter.
11
BR2: Each Employee must have a unique ID.
BR3: When employees are leaving the Human Resource Management by any means, they have to
handover resources or duties the respond the resource in proper manner.
BR4: Reports must be prepared and generated within a specified schedule.
BR5: Whenever the employee is absent from his/her job his/her compensation must be reduced, if he/she
have no permission from department head.
BR6: When employees are reregistered again by any means, the staff must fill employee description in the
employee registration form and update the employee data.
BR7: Whenever new employee category is received, a new Registration form must be prepared.
BR8: Every department requesting employee must be eligible (legal) known in the Collage.
f. Proposed Solution
The proposed solutions that will be used to solve the problems of the existing system are:-
Desktop Application
Networked System
Web based System
Android Application
Networked System:-Networked System use a client-server architecture, where the client and server are
two computers connected to the network. The server is programmed to provide some service to the client.
we don’t use this system because system is not only applicable to DDU and the system does need to be
accessed outside DDU during the applicant view the.
Web-based System:-Web based system is client-server software in which the client runs in web browser.
Users access the application from any computer connected to the internet. It is easy to install and maintain,
because once the version is upgrade it is installed on host server, all users can access it straight away.
Develop desktop application: - It is application use to solve the problem that exists on the current system
by storing all the data of the organization in a well manner and it will also retrieve without much effort.
This application does not need any connection on the internet.
Develop Mobile Application: - Another alternative way of solving the existing system problems is by
creating a software application that can be run on mobile devices such as smart phones and tablet
computers. This application use for storing large amount of data and exchange notification between each
actor of the system in a fast way than websites can.
g. Preferred Solution
Our team investigates the alternative solutions that can solve the problem and after detail discussion, we
select web-based system for the new system because of the following reasons:
The preferred solution of the project is web based because
It meets our knowledge qualification.
It meets our specification.
It is easy to use.
Web based application enables the users to access the services 24/7.
The preferred solution also durable and accessible make it cost effective
The preferred solution can deliver information extremely effective
13
h. Domain Modeling with CRC Card
A Class Responsibility Collaborator (CRC) Model is a collection of standard index cards that have been
divided in to three sections. A class represents a collection of similar objects, a responsibility is something
that a class knows or does, and a collaborator is another class that a class interacts with to full fill its
responsibility. CRC models are a brainstorming tool used in the design of object oriented software and
typically used when first determining which classes are needed and how they will interact.
Responsibilities: Collaboration:
Full Name MANAGER
Age
Sex
Job position
Apply to vacancy
Take exam
View placement
Table 2.8 CRC card of applicant
14
Class name: EMPLOYEE
Responsivities: Collaboration:
SSN MANAGER
Full name
Age
Sex
Job position
Generate report
15
2.10 Essential Use Case Documentation
Use case name Register employee
Identifier UC-1
Actor HRM manager
Discription The hrm manager can register each of the
employee and can be update and delete
each of the data.
Pre condition The manager should be know the over all
information of each employee befor
registering the employee.
Flow of event The employee can be finish the over all
process of the employty the hrm activity.
Post condition The emplyee registered to the existing
data of the other employee.
17
Actors Applicant
Description The applicant take the exam after
applying to the vacancy.
Pre condition The applicant should be apply to the
position fullfill the criteria.
Flow of event The applicant view the position and apply
to that positon and take the exam.
Post condition Applicant take exam.
18
User interface prototyping an iterative analysis technique which user are actively involved in the mocking
up of the user interface of a system
In our case the following is the essential user interface prototyping of the existing system.
Employee Registration form:
19
CHAPTER THREE
SYSTEM ANALYSIS
3.1 Introduction
Studying the existing system is possible to understand that how the proposed system can solve the existing
system problems. This helps to determine both functional and non-functional requirements. The boundary
and the actors who are involved in Ethio-Italy Poly Technical Collage human resource management system
by using use case diagram along with the written use case scenarios that can be described.
Reviewing the existing system brings about an important contribution to the entire development process.
On doing this phase we can realize what is going wrong, what to change, what activity or practice to
encourage, and what alternative solution to propose.
20
Leave management: - The system allows to the employee able to fill in leave application form in
the appropriate fields and the human resource manager allow leaving approval application based on
the reason what the employee can be illustrated.
Message or notification:-The system is able to communicate the employee by sending the message
to the other employee or to the manager.
In shortly the functional requirement of our system is:-
Login
Logout
Messaging system(send, receive, reply)
Employee registration
Vacancy announce
Manage account (create, activate and deactivate, update).
Place employee
Leave request
Approve leave
View approved leave
Post exam schedule
Applicant registration
Approve applicant.
22
3.4.2 Use case Documentation
Use case name Login
Identifiers UC -1
Description The user login to the system to navigate the system
Actors Admin, HR manager, Employee
Pre-condition The user must have user name and password.
Basic course of action 1. The user browses the system
2. The user clicks login link
3. The system displays the login page
4. The user enters the username and password
5. The user clicks on login button
6. The system takes the user to the page.
7.The use case end
Alternative course of action A. If the user name and password is not correct
A5. The system displays user name or password wrong
A6. The use case goes to step 4 in the basic course of action
A7. The use case ends
Post condition The user logged to the system.
Table 3.4 .1use case documentation of the login page.
Use case name Logout
Identifiers Uc-2
Description The user logout the system.
Actors Admin, HR manager, Employee, applicant
Pre-condition The user must logout the system after navigate the system.
Basic course of action 1. he user browses the system
2. The user login to the system
3. The system authenticates the user
4. The user do what he/she want
5. The user clicks on logout button
6. The system takes the user out of the page.
7. The use case end
Alternative course of action A. If the identification is not correct
A3. The system displays identification wrong
A4. The use case goes to step 2 in the basic course of action
A5. The use case ends
Post condition The system was logged out.
Table 3.4.2 use case documentation of new system logout.
23
Use case name Manage account
Identifiers Uc-3
Description The administrator manages account.
Actors Admin
Pre-condition The admin should login to the system using Uc-1
Basic course of action 1. The user browse the system
2. The user login to the system having user name and password
3. The system authenticates the user inputs
4. User selects create account
5. The user fill the form
6. The user click create account
7. The system save the new account
8. The system display message successfully crate the account
Use case is ends
Alternative course of action A. If user enters wrong information
A3. System displays information is wrong message
A4. The use case goes to step 2 in the basic course of action
A5. The use case end
Post condition The account is managed.
Table 3.4.3 use case documentation of create account.
Use case name update account
Identifiers Uc-4
Description The admin update account
Actors Admin
Pre-condition The account must create.
Basic course of action 1. HR officer browse system
2. The user login to the system having user name and password
3. The system authenticates the user inputs
4. Click update account
5. HR officer fill required information.
6. Click update account
7. Search found from database.
8. Display searched result.
9. Click update account button.
10. Update account form database.
11. Update account notification.
The use case ends
Alternative course of action A. If user enters wrong information
A3. System displays information is wrong message
24
A4. The use case goes to step 2 in the basic course of action
A5. The use case end
B. If account does not exist
B6. System displays message account does not found
B7. The use case goes to step 5 in the basic course of action
B8. The use case end
Post condition Account is updated.
i. Table 3.4.4 use case documentation of update account
Use case name Delete account
Identifiers Uc-5
Description The admin can delete account
Actors Admin
Pre-condition User must login and account is must be exist.
Basic course of action 1. The user browses the system
2. The user login to the system having user name and password
3. The system authenticates the user inputs
4. Officer click delete account button,
5. HR officer fill required information.
6. Click delete account
7. Search found from database.
8. Display searched result.
9. Click confirm delete account button.
10. Delete account form database.
11. Delete account notification.
12.The use case ends
Alternative course of action A. If user enters wrong information
A3.System displays information is wrong message
A4.The use case goes to step 2 in the basic course of action
A5.The use case end
B. If account does not exist
B6. System displays message account does not found
B7.The use case goes to step 5 in the basic course of action
B8. The use case end
Post condition Account is deactivated.
Table 3.4.5 use case documentation of deactivate account.
Use case name Vacancy announce
Identifiers Uc-6
Description The HR manager announces the vacancy position.
Actors HR manager.
Pre-condition The user must login to the system.
25
Basic course of action 1. The user browses the home page
2. HR officer login to the system by inserting the user name and
password
3. The system authenticates user information
4. While the user select approve, vacancy announcement form will
display
5. The user fills the information
6. The user click on post button
7. The use case ends
Alternative course of A. If the user doesn’t have access privilege to use the system
action A3. The system informs the user to fill the correct information
A4. The use case goes to step 2 in basic course of action
A5. The use case ends
B. If the vacancy file is not correctly filled
B6. The system informs the user to fill correctly
B7. The use case goes to step 5 in basic course of action
Post condition Vacancy is announced.
3.4.6 Use case documentation of vacancy announcement.
Use case name View vacant position
Identifiers Uc-7
Description The applicant can view the vacant position.
Actors Applicant
Pre-condition The user want to see
Basic course of action 1. The user browses the system
2. The user click on vacant menu
3. The user select from list of options
4. The system displays vacant
5. The user view the vacant
6. The use case ends
Alternative course of action A. If there is no vacant position
A4. The system displays 'no vacant position' message
A5. Then use case ends
Post condition If there is a vacant position see the position.
Table 3.4.7use case documentation of view vacancy position
Use case name Applicant registration
Identifiers Uc-8
Descriptions The applicant want to registered on position
Actors Applicant
Pre-condition Vacancy must be announced
Basic course of action 1. The user browses the home page
26
2. The applicant clicks on apply button
3. The applicant fills the form
4. The applicant clicks submit button
5. The applicant submits the filled information to HR office
DB
6. The use case ends.
Alternative course of action A. If the applicant does not fill the form correctly
A4.the system informs the applicant to fill correct input
A5. Use case goes to step 3 in basic course of action
A6. The use case ends
Post condition Applicant is successfully registered.
Table 3.4.8 use case documentation of applicant registration.
Use case name Applicant approval
Identifiers Uc-9
Description Used to approve the registered applicant based on the given announced
criteria
Actors HR manager
Precondition The applicant must be registered to the position.
Basic course of action 1. The user browses the system
2. The user login in to the system
3. The system validates the inputs
4. The system displays the home page
5. The user selects applicant detail
6. The system displays applicants detail information
7. The user checks the applicant information with the posted one
8. The user clicks on approve button
9. The system displays successfully approved message
10. The use case ends
27
Identifiers Uc-10
Description The appropriate actor can post exam schedule.
Actors Admin
Pre-condition Applicant must be approved.
Basic course of action 1. The user browse the system
2. The user login in to the system
3. The system validates the inputs
4. The user selects view register
5. The user selects applicant detail
6. The system displays applicants detail form
7. The user select exam schedule
8. The system displays schedule form
9. The user fills the schedule
10. The user select post button
11. The system displays schedule posted message 12.Use case ends
28
A5. The use case ends
B. If the applicant enters incorrect input
B7. The system informs the user to fill correctly
B8. The use case goes to step 6 in basic course of action
B9. The use case ends
Post condition Pre employment successfully registered.
Table 3.4.11 use case documentation of pre-employment registration
Use case name Placement
Identifiers Uc-102
Description HR Officer place competent applicants as employee
Actors HR manager
Pre-condition Pre-employment registration
Basic course of action 1. The user browses the system
2. The user login to the system having user name and password
3. The system authenticates the user inputs
4. The user select view register
5. The user select employee detail and click on placement
6. The system displays placement form
7. The user fills the form
8. The user click on place button
9. The system informs the user “placed successfully” and employee
information is recorded in the database
29
5. The system displays leave application form
6. The user fill the form
7. The user clicks on Submit button
8. Use case ends
30
4. The system displays approved leave employee
5. The user can see approved leaves
7.Use case ends
Alternative course of action A. User is not privilege to the system
A2. The system informs the user to input correct information
A3. The use case goes to step 1 in the basic course of action
A4. The use case ends
Post condition The employee views the approved leave.
Table 3.4.15 use case documentation of view approved leave.
Use case name Send message
Identifiers Uc-16
Description To send message notification from one user to another for any purpose.
Actors Any user
Pre-condition User want to send message for one purpose.
Basic course of action 1. The user login in to the system
2. The system validates the inputs
3. The user select message menu
4. The system displays message form
5. The user write the message
6. The user enter the destination address
7. The user click on the send button
8. The system displays 'message is successfully' send message
9. Use case ends
33
Figure 3.5.2 activity diagram for create account.
34
3.4.4 System Sequence Diagram
Sequence diagrams are an interaction diagrams that shows how processes operate with one another and in
what order. It shows interaction of objects and classes involved in the scenario and the sequence of
messages exchanged between the objects needed to carry out the functionality of use case scenarios. The
sequence diagram of our system is the following:
Figure 3.6.1
sequence diagram of login page.
35
Figure 3.6.2 sequence diagram of create account.
36
Figure 3.4.5.1 conceptual class diagram
37
Actors Rule description
HR Should have user account to login to the system. And should have announce vacancy to
manager applicant page when applicant fulfill the criteria it approve the request.
Applicant Should read the vacancy and when they fulfill the criteria they register to the position and
should take exam by going to the officer.
Employee Should have user account to login and navigate the system and when they request leave form
they should write the evidence reason to the manager unless and otherwise they can’t get
approved.
38
CHAPTER FOUR
SYSTEM DESIGN
4.1 Introduction
Systems design is multi-step process that focuses on data structure software architecture, procedural
details, (algorithms etc.) and interface between modules. The design process also translates the
requirements into the presentation of software that can be accessed for quality before coding begins. It 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 chapter focuses on transforming
the analysis model into the design model that takes into account the non-functional requirements and
constraints described in the problem of the statement and requirement analysis sections discussed earlier.
This document describes the requirements for developing the human resource information management
system for Ethio-Italy Poly Technic Collage.
40
HR MANAGER
APPLICANT ADMIN
EMPLOYEE Fname=varchar
Sex=varchar +admin
1.1 +fname=varchar +fname=varchar
SSN=int name=varchar
+age=int -cgpa=int
M.* manage() -ID=int
-CGPA=int +sex=char
-ac.type=char()
+sex=varchar -SSn=int Login()
+jop positionvarchar 1.* create() 1.*
request()
update()
register() request() Login
view()
activate/deactivate() Manage()
type user=varchar
1.* username=char account
View()
password=char
Request login() -Ac.type=char
view vacancy cancel() #username=char
+start date=int +fname=varchar forgotpassword() #password=char
+end date=int +position=varchar
1.* create()
+position=varchar +Case=varchar
+type of request update()
+requirement=varchar announce vacancy post activate/deactivate()
leave=varchar
apply()
+start date=int generate report
submit() +end date=int
registration cancel() +position=varchar +type=varchar
view() +requirement=varchar -memberName
+fname=varchar +ammount=varchar
view approved send()
-cgpa=int post()
+email=char +fname=varchar 1.*
Fill() +sex=int +date=int
+position=varchar post exam schedule Post()
view()
register()
+date of exam=int
+requirement=varchar
post()
1.* 1.*
placement approve
+fname=varchar +registered info=varchar
+position=varchar
approve()
Figure 4.4 system class diagrams.
4.5 Stat Chart Diagram
State chart diagram shows the different states of an object during its life and the motivations that cause the
object to change its state and view objects as machines or finite mechanisms. This diagram shows the
sequence of activities of the HRMS what action will be performed first and which will be the coming.
41
applicant view vacancy register registration form fill fill form
view summit
exit
no submitt
yes
Created successfully
42
Figure 4.6 collaboration diagram of login
43
User name varchar(20) - primary Not Null
Admin
EMPLOYEE
Vacancy
44
Field Names Type Visibility Key Description
Message
Login
45
Table 4.7 persistent data management of login
Applicant
46
4.9 Deployment Diagram
Deployment model is a model the configuration of the run time elements. It provides necessary
environment in which system components are to be executed in. This model will be used to show how the
hardware in the organization will be connected and which component of the software will be deployed in
hardware.
47
Figure 4.10 User Interface
48
Figure 4.10 Login Page
49
CHAPTER FIVE
CONCLUSION AND RECOMMENDATIONS
5.1 Conclusion
Ethio-Italy Poly Technic Collage Human Resource Information Management System is software that can
be able to solve the problem that occurs in manual system.
An effort has been made to study HRMSof Ethio-Italy Poly Technic Collage as partial fulfillment of BSc
degree in Information Technology. 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 HRMS models have been designed to reflect the
new system that is supposed to solve problems. Designing computerized HRMS of Ethio-Italy Poly
Technic Collagehelps to maintain a computer based HRMS.
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. We believe that
different tools and techniques has helped us a lot in capturing real user requirements and model the right
system for the users for their day to day transactions. Thus it should have the precedence in know-how and
experience in collecting, processing and utilizing information.
Ethio-Italy Poly Technic Collage Human Resource Information Management System is a web based
application to serve the whole employee in the Ethio-Italy Poly Technic Collage . This system is to serve
Human Resource Manager, Administrator to reduce work load and save time.
Through various challenging, now the team is coming to the end of this project. Those different challenges
made possible by the cooperation of all the group members.
5.2 Recommendations
As our system means Ethio-Italy Poly Technic Collage Human Resource Information Management System
we recommend that all activity that is done by our system is efficient, effectively and secured in all side.
For Ethio-Italy Poly Technic Collage Human Resource Information Management, we would like to
recommend that, this system is very essential and the office must use the system effectively by running the
system in all functional side. The entire employee in the HRMS must use the system in similar manner to
increase employee performance and to control over all activities in.
50
REFERENCES
[1] www.eipc.com)“ history of the Collage”
[2] J.Jones. (2001,May 15).difference between constraint and limitation(3rd
ed.)[online].online.Available:https://www.Quara.com
[3] Dianll Arthur. Managing human resource in small and midsized companies.1986, 2nd edition, amacom.
[4] William p.anthony, k.michelekacmarpamal. l.perrewe’tohumanResource management a strategic
Approach, 4th edition.
[5] Trevor Bolton, An introduction to human Resource Management, 2002 3rd edition.
51