Final Project Document

JIMMA UNIVERSITY
JIMMA INSTITUTE OF TECHNOLOGY

FACULTY OF COMPUTING
Information Technology
Web Based Employee Performance Management System for JIT
Group Members
Name ID NO
1. Lencho Yigazu……………………………………...RU0699/08
2. Gadisa Gamachu………………………………….RU0591/08
3. Lami Bulcha…………………………………….……RU2323/07
4. Firomsa Tamiru………………………..………....RU0578/08
Advisors:
Name Signature
1. Mr. Worku Berhanie ……………………..
2. Mrs. Melishew Awoke ……………………...
Submitted to: Faculty of Computing

June, 2019
JIMMA, ETHIOPIA
WEB BASED EMPLOYEE PERFORMANCE MANAGEMENT SYSTEM FOR JIT
Acknowledgement
First of all, we would like to thanks GOD who gave us the ability, patience and strength to
conduct and Complete this Project documentation. Secondly, we would like to acknowledge
and thank our advisors Mr Worku Berhanie and Mrs Melishew Awoke.
i|Page
Abbreviation
UML = unified modeling language
BR = business rule
UC = use case
EPMS = employee performance management system
JIT= Jimma Institute of Technology
HRM = human resource management
ii | P a g e
Contents
CHAPTER ONE ......................................................................................................................... 1
1. INTRODUCTION ........................................................................................................................ 1
1.1 Problem statement ............................................................................................................. 2
1.2 Significant of the project.................................................................................................... 2
1.3 . Proposed system .............................................................................................................. 3
1.4 Objective of the projects ........................................................................................................ 3
1.4.1 General objective ........................................................................................................... 3
1.4.2 Specific Objective .......................................................................................................... 3
1.5 Scope of Project..................................................................................................................... 4
1.6 Methodology......................................................................................................................... 4
1.6.1 Data collection method................................................................................................... 4
1.6.2 System Analysis and Design Methodology ...................................................................... 5
1.6.2.1. Case Tool ................................................................................................................... 5
1.6.2.1.1 Hardware tools: - ................................................................................................. 5
1.6.2.1.2 Software tools: - ..................................................................................................... 5
1.7 .System Development Environment ....................................................................................... 6
1.8 Testing Procedures ................................................................................................................ 6
1.8.1 Unit Testing .................................................................................................................... 6
1.8.2 Integration Test .............................................................................................................. 7
1.8.3 System Testing ................................................................................................................ 7
1.9 Project schedule .................................................................................................................... 8
CHAPTER TWO ........................................................................................................................ 9
2.1 EXISTING SYSTEM ........................................................................................................ 9
Existing system Description .................................................................................................... 9
Introduction ............................................................................................................................ 9
2.1.1 BUSINESS RULE ..................................................................................................... 10
2.1.2 Existing system players ................................................................................................. 10
2.1.3 Functions and Activities in the Existing System ............................................................... 12
2.1.4 Report Process in the Existing System ............................................................................. 12
2.1.5 Bottlenecks of the Existing System ................................................................................. 13
2.1.6. Practices to be preserved .............................................................................................. 14
2.2 New system ...................................................................................................................... 14
2.2.1 Proposed Solution for the new System ....................................................................... 14
2.2.2 Requirements of the Proposed System ....................................................................... 15
iii | P a g e
2.2.3 System Models .............................................................................................................. 17

Use case Diagram ............................................................................................................... 17
Use case documentation ........................................................................................................ 19
2.2.4 Dynamic models ............................................................................................................ 29
2.2.4.1 Sequence diagram ................................................................................................... 29
2.2.4.2 State Chart diagram ................................................................................................. 37
2.2.4.3 Activity Diagram ...................................................................................................... 39
2.2.5 Conceptual Modeling ..................................................................................................... 43
Class Diagram ..................................................................................................................... 43
2.2.6 User interface prototyping ............................................................................................. 45
CHAPTER 3 ................................................................................................................................. 46
SYSTEM DESIGN ..................................................................................................................... 46
3.1 Introduction ..................................................................................................................... 46
3.2. Purpose and goal of design .............................................................................................. 47
3.3. Current software architecture .......................................................................................... 48
3.4. Proposed software Architecture .......................................................................................... 48
3.4.1 Overview ....................................................................................................................... 48
3.4.2 Subsystem Decomposition ............................................................................................. 49
3.4.3 Component diagram ..........................................................................................................
3.4.4 Deployment Diagram ..................................................................................................... 52
3.4.5 Database Design ............................................................................................................ 53
3.4.6 Persistence Model of object oriented Database .................................................................. 54
3.4.6.1 Mapping ..................................................................................................................... 54
CHAPTER FOUR .......................................................................................................................... 57
4 Implementation and testing .................................................................................................... 57
4.1 Introduction ......................................................................................................................... 57
4.2objective and implementation .............................................................................................. 57
4.3Constraints and implementation ........................................................................................... 57
4.4Testing .................................................................................................................................. 57
4.5Testing and requirments........................................................................................................ 58
4.6Testing by scope .................................................................................................................... 58
4.6.1 unit testing ........................................................................................................................ 58
4.6.2 Integration and system testing ........................................................................................... 59
4.7 Sample code and sample output screen ................................................................................ 64
4.8 installation ........................................................................................................................... 71
iv | P a g e
CHAPTER FIVE ............................................................................................................................ 72

5.1 Conclusion ........................................................................................................................... 72
5.2 Recommendation. ................................................................................................................ 72
5.3 Index.................................................................................................................................... 73
v|Page
List of Figure
Fig1.1. Gant chart ................................................................................................................................. 9
Figure 2.1. use case diagram ............................................................................................................... 19
Figure 2.2. sequence diagram for login............................................................................................... 31
Figure2.3. Sequence diagram for view notification ............................................................................ 32
Figure2.4. Sequence diagram for set examinee/er (examinee and examiner) ..................................... 33
Figure2.5. Sequence diagram for update examinee/er (examinee and examiner)............................... 34
Figure2.6. Sequence diagram for generate report ............................................................................... 35
Figure2.7. Sequence diagram for make evaluation ............................................................................. 36
Figure2.8. Sequence diagram for manage criteria .............................................................................. 37
Figure2.9. state chart diagram for login .............................................................................................. 38
Figure2.10. state chart diagram for manage users............................................................................... 39
Figure2.11. Activity diagram for login ............................................................................................... 40
Figure2.12. Activity diagram for make evaluation ............................................................................. 41
Figure2.13. Activity diagram for manage criteria ............................................................................... 42
Figure2.14. Activity diagram for send notification ............................................................................. 43
Figure2.15. Activity diagram for view notification ............................................................................ 44
Figure 2.16. Class diagram.................................................................................................................. 45
Figure 2.17. User interface prototype ................................................................................................. 46
Figure 3.1. System software architecture ............................................................................................ 49
Figure 3.2. Subsystem decomposition ................................................................................................ 51
Figure 3.3. Domponent diagram ......................................................................................................... 52
Figure 3.4. Deployment diagram ........................................................................................................ 53
Figure 3.5 Database design diagram ................................................................................................... 54
Figure 3.6. Persistent diagram............................................................................................................. 55
Figure 4.1 Home page ......................................................................................................................... 59
Figure 4.2 Login form ......................................................................................................................... 60
Figure 4.3. Boss home page ................................................................................................................ 60
vi | P a g e
List of Tables
Table 2.1. Login use case table ........................................................................................................... 20
Table 2.2. Generate report use case table........................................................................................... 21
Table 2.3: send notification use case table .......................................................................................... 22
Table 2.4: view notification use case table ......................................................................................... 22
Table 2.5: manage users use case table ............................................................................................... 23
Table 2.6: make evaluation use case table .......................................................................................... 24
Table 2.7: logout use case table .......................................................................................................... 25
Table 2.8:- set examinee/er (examinee and examiner) use case table ................................................. 26
Table 2.9:- update examinee/er (examinee and examiner) use case table .......................................... 27
Table 2.10:- manage criteria use case table ........................................................................................ 28
Table 2.11:- view report use case table ............................................................................................... 29
Table 2.12:- view result use case table............................................................................................... 30
Table 3.1. Access control table ........................................................................................................... 56
vii | P a g e
CHAPTER ONE
1. INTRODUCTION
In JIT, employee performance management system is not well-developed in the form web
before to evaluates employee performance, so we want to develop web-based systems that
can increase employee performance among them and increase competency-based system that
measures employee not only on goal attainment but also on the very competencies that are
required for their role. The competency rating value are stored in the database system so that
other processes such as criteria, new criteria, backup search, calculator form and so on, can
arrangement in these databases. Performance management is a system designed to identify
the ways to achieve or fulfill organizational goals through constant assessment and feedback
leading to improvement of employee performance.
1|Page
1.1 Problem statement

The main problem in the existing system faced that, there is no well-organized computerized
system to measure employee performance in JIT. Additionally, the existing performance
management system is implemented ineffectively or the performance measure of the
employee still using the manual appraisal. The main drawback of the current system may: -
 Wastage of time: - supervisor required a lot of time to evaluates each employee with
meeting time.
 The supervisor doesn’t record the performance evaluation at the right time.
 The performance objective and the management system are not proportional: - most
employees perform activities that are not listed or mentioned on the give criteria.
 Data loss and redundancy: - during evaluation information record data can be lost.
 Wastage of resource: - the existing system needs much resource for printing and
writing many documents.
 The existing system is it doesn’t support the feedback system, only examined
employee.
 Lack of security of data.
1.2 Significant of the project

 Increase competitions among each employee
 Focuses employees on self-development
 Minimizing and equalizing of rater bias (unfair)
 More insight for self and managers to plan initiatives and take decisions
 Increases team orientation and communication channels
 Increase productivity and manage problems
 lower cost in completing each process
 Better management and efficient information flow
 Help all the employee can understand their job responsibilities and improve job
performance
Make plan to solve the fetch up problems for future
2|Page
1.3. Proposed system

The new system is designed to solve problems affecting the manual system in use. It is design
to be used online there by relieving the manager or supervisor, employee and any other
workers from much stress as experienced in the manual system. We are going to improve the
drawbacks of the existing system by developing an automated, user friendly and interactive
graphical user interface system which will: -
 Manage time effectively: The proposed system will minimize wastage of time using
computers instead of manual system
 Make the data error free: - helps to avoid data redundancy or duplication.
 Utilize available resource effectively - minimize the usage of any writing material like
paper, pen and any other material that helps to write report document.
 Make the system computerized: - access all the performance management system
using computer system with the aid of the internet connection.
 Give any feedback to the entire employee to correct their weakness.
 Security: since the system requires verification of logon form, sensitive information’s
will not be accessed or modified by unauthorized users.
 Efficient way of data management: -Since the system uses database system there is no
loose of data.
1.4 Objective of the projects

1.4.1 General objective
The general objective of this project is to develop and implement web-based employee
performance management system for JIT.
1.4.2 Specific Objective

 Analyze the limitations of the existing system.
 Analysis and design a system which is secured, efficient and user friendly.
 Design the system that will solve the current problems and provide reliable
functionalities.
 To add and update evaluation criteria
 To design and develop performance ranking system.
 Modeling and developing the new system.
 Implementing the system.
 Testing the system.
 Preparing semester report.
3|Page
1.5 Scope of Project

The scope of this project helps to develop the automate system for employee
performance management system in order to replace the manual paper work. Our
project scope includes the following basic tasks: -
 Manage users: -Add, activate, deactivate and delete system users.

 Our systems support criteria management for users input.
 Supervisor: manages examinee, criteria and generate report for HRM to
evaluate the performance of employee.
 Give feedback /comment...such as warning and appreciation.
 Inform all employees when there is meeting in the form of text message
post on interface.
 Allow users to manage their own profile.
 View result: - only examinee and supervisor can view evaluation result.
 Send report.
 Notification system.
 Generally: On the end the system make evaluation result by producing
result that employees perform in the semester using its own algorithm that
defined in system.
1.6 Methodology
1.6.1 Data collection method
We will try to developing this system obtained data from different sources. Since the data
was the basic component (requirement) to achieve the target aimed by the Project and we will
collect data from different sources to develop our system. Data can be collected:-
A. Interview: -is used to gather required data for the project by contacting directly with
different departments of the JIT administrative staff.
B. Observation: -is used to gather additional data by observing the actual work being
done by the staff and consolidated with what was obtained through Interview.
C. Document Analysis (Document & literature review): -consulted and analyzed
written materials that describe the operations conducted in the station to further
strengthen and support the information that applied the above technique.
4|Page
1.6.2 System Analysis and Design Methodology

To develop a function-able and good quality system, the software development approach that
chosen must be suitable for developing the certain system, it must also provide all the
features that needed for developing the system. In this project, which is to develop an
employee performance management system, the object-oriented approach is chosen.
The object-oriented approach has the ability of encapsulation, inheritance and polymorphism
that provide the facilities of the data hiding and reusability of the code. The objects created in
the program can be reused and the internal structure of the objects it hides using
encapsulation to protect them from corruption. So, it made the system maintenance easier and
shortens the development time. Object-oriented approaches also reduce the complexity of the
system development. This is the reason why object-oriented approach is used in developing
this project.
1.6.2.1. Case Tool

1.6.2.1.1 Hardware tools: -
 Desktop computer/laptop.
 Displaying devices like printer and monitor.
 Storage devices: hard disk, flash disc.
 Internet cable
1.6.2.1.2 Software tools: -

 Microsoft word 2016: - to prepare documentation.
 Microsoft PowerPoint: - to prepare slide shows.
 Apache server: - to facilitate works as local server.
 MYSQL: - to store user’s information.
 Notepad++: - to write different codes (PHP, CSS, JavaScript)
 Redraw max: - to Design UML diagrams.
5|Page
1.7 .System Development Environment

Operating environment is the environment that is responsible for operating or applying the
product of software. The operating environment of this product use different hardware
platforms like computer using PHP language.
PHP programming language: - the implementation or code part of this system is developed on
the area of this language. It is used to develop computer programs for Microsoft Windows, as
well as web sites, web applications and web services.
Microsoft office 2016: The team use Microsoft office word during prepares planning and
writing documentation.
UML Diagramming: The application design using different UML diagram for the application.
The team proposes to use Edraw max in order to support those diagrams. Since Edraw max
facilitates object-oriented analysis and design the great thing about Edraw max is that it
allows analysts, engineers, writers, and project managers to create, view, manipulate, and
modify elements in a Unified Modeling Language (UML) across the entire enterprise, using
one tool and one language.
1.8 Testing Procedures

Testing is a trial experience in which the deliverables of the project are checked with
acceptable standards in the project. We used unit testing, and system testing to test the
correctness of each module and the compiled program.
1.8.1 Unit Testing

In this type of testing, components are tested individually. In case of our system, all
components have been tested to maximum satisfaction. The components that will be tested
are listed below: -
 Calculate evaluation result.
 Add and update evaluation criteria.
 Notification system between them.
 Supervisor manages examinee/er (examinee and examiner): -set examinee/er
(examinee and examiner) and examinee/er (examinee and examiner).
 Make evaluation
6|Page
1.8.2 Integration Test

When a number of components are complete; it will test to ensure that they integrate well
with each other, the operating system, and other components.
1.8.3 System Testing

For verifying the whole system is functioning in the integrated manner and helping in striving
or try to achieve planned goal. System testing is comparing Function of the system developed
in relation with expected function of the system.
7|Page
1.9 Project schedule
Tasks Start Finish Duration

Title submission Nov1 Nov8 8 days
Title proposal Nov 17 Nov 25 8 days
Analysis Nov 29 Dec 9 10 days
Design Dec 10 Jan15 35 days
Implementation Mar 1 May 25 85 days
Final defense Jun 25(?) Jun 26(?) 1 day
Task name Nov 1-8 Nov 17-25 Nov 29- Dec 10- Mar 1- Jun 25-
Dec 9 Jan 15 May 25 (?)
Title
submission
Title proposal
Analysis
Design
Implementation
Final defense
Fig 1: Gant Chart
8|Page
CHAPTER TWO
2.1 EXISTING SYSTEM
Existing system Description
Introduction
This chapter produces a broad outline of the proposed system that identifies the function to be
performed and the technical aspect that the system must fulfill and briefly describes the
existing system functionality, problem of the existing system. It also deals the functional and
nonfunctional requirements of the proposed system.
It is necessary to know the existing system of a given organization to develop a better system.
The existing system of JIT EPMS follows working manual system; this type of system is very
tedious or bulky for each employee. Each and every employee has its own individual
evaluation criteria within their department which is give or prepared by their supervisor. The
target area of this web based employee performance management system currently performs
different activities including calculating the evaluation result, adding evaluation criteria,
update evaluation criteria, set examinee/er (examinee and examiner) and update examinee/er
(examinee and examiner) and then like. In addition to the above explanation the existing
system is not secured since; it is manual based and the documents which stored in each
individual department can be easily steal by someone and throwaway the paper. so this
manual system is not reliable in case of such problems.
9|Page
2.1.1 BUSINESS RULE

A business rule is effectively an operating principle or polices that we try to specify for both
the traditional existing system and the new system must satisfy. It is a principle or a policy in
which the proposed system operates accordingly. It deals with access control issues. It often
pertains to access control issues, operating policies and principles of the organization.
 The existing system includes the following operating principles or rules:
BR1. Colleague & supervisors should be participate in evaluation

BR2. Employee evaluated in semester.
BR3. Criteria preparation
 The main business rules or principles of the proposed system are: -
BR1. . Employee evaluated in a semester.

BR2.Colleague & supervisors should be participate in evaluation
BR3. Criteria preparation
BR5. Only authorized user should evaluate
BR6. The employee must be evaluated only once by giving take care b/c system doesn’t
allow after evaluation
2.1.2 Existing system players

Player represents external entities that interact with the system. They manage and perform the
system functionally. These players are participating both in the administrative and
academicals staff or both the two staff has the same number of players.
 In the administrative staff there are different departments. Which includes:-

 Finance: - which includes
 Main finance officer
 Finance officer
 Budget officer
 Type writer
 Project finance officer
 Messenger
 Clinic
 Surgery
 Pharmacy
 Laboratory
10 | P a g e
 Diagnosis
 Main Cash holder
 Supporter Cash holder
 Library
 Librarian
 Library attendant
 Library auditor
 dormitory
 human resource management
 main record
 human resource study
 type writer
 lecturer id card preparation
 empty vacancy space
 perquisite motivation rather regular payment
 discipline
 In the academicals staff there is two different departments. Which includes:-
 Lecture
 Lecturer
 Assistant lecturer
 Assistant
 Lab Assistant
 Lab attendants
 In the technician staff there are five major activities or sub staffs. Which includes:-
 Electricity
 Water(drain pipe)
 Construction and color plated
 Wood maintenance
 Metal welding
 In JIT as we have gathered information all staff (administrative, academicals and
technician) the employee performance can be measure or evaluated by three evaluation
types or methods. These evaluation types are:-
11 | P a g e
 Supervisor evaluation types: - the supervisor must be evaluates all the employees
which are participating in his or her staff and finally sent their result to the HRM.
 Colleague evaluation types: - in this evaluation type all the colleague can be evaluate
their work friend or their colleague and send to the supervisor.
 Student evaluation types:- evaluation type in which university lecturers evaluates
according to criteria given by supervisor
2.1.3 Functions and Activities in the Existing System

The major activities in the existing system are activities that have been accomplishes in
existing system.
 Distributing the evaluation criteria to the individual employee with their department.
 Evaluate the entire employee within the organization.
 Give the reward to the employee that has a good participation on their work.
 Give warnings to the employee when he or she can’t surmount the responsibility.
 Give the extension time for correcting his or her performance.
 Record the employee information in documented form.
 Make confirmation between the employee and supervisor in the given plan.
 Divide the employee into groups used for easy manage by the supervisor.
 Each employee processes the report to the supervisor and supervisor pass into the HR
2.1.4 Report Process in the Existing System

In our system employee performance management system report is not generate but; can
create or process from the individual examinee in the form of notification system and the
supervisor submits it to the HRM. The Employee processes report in the six month or
semester which uses manual System, it takes time to write and submit to the supervisor. All
the departments of each staff process reports in manual system in the existing system. As we
have listed in the above in both the administrative and academicals staff the entire employee
can be evaluated by the three examiners. But each of the examiners gives different value
based on the given criteria to the examinee. The evaluation form is filled with each examiner
as he or she assumes to give the result for examinees surmount of responsibility.
12 | P a g e
 In all staff’s employee can be examined by: -

 Colleague evaluation
 Supervisor evaluation
 Student evaluation
1. Colleague: - they must evaluate the examinee out of some given rule based on the
given criteria which is given to him or her.
2. Supervisors: -can also evaluate the examinee out of some given rule in which they can
base on their agreement.
3. Students :- can evaluate university lecturers according to criteria stored on database by
supervisor
2.1.5 Bottlenecks of the Existing System

 Performance
 The current system is still working at low level of data organized, because the system
works all things in manual form. The current system doesn’t give fast response time to
manage and evaluate the employee performance.
 Security and control
 Every record of the existing system is paper based so, it is difficult to control and secure
these manual records, since it doesn’t have any authentication and authorization system.
 Resource consumption
 Due to the manual operation most of the activities are easy to wastage of resources like
stationary materials, manpower, time and the resource utilization of the current system
very extravagant; because use much resource for writing any documented formats.
 Efficiency
 The workers or the employee can waste time and materials that may happen by the
peoples and data is redundantly processed or redundantly copied. The materials required
for tasks are expensive.
 Service
 The existing system gives very tedious service in processing the report for the
HRM. Because it is difficult to manage and controlling the employee
performance manually
13 | P a g e
2.1.6. Practices to be preserved

The main activities that are performed in the manual system will be transfer by designing the
web based activities. That of each activity is transfers to the new system are designed and
automated to achieve the best functionality.
 In the existing system it increases a good relationship between each employee in

meetings.
 Make performance evaluation computerized to minimize resource usage.
 The proposed system helps to exchange the experience by giving any feedback.
 The proposed system helps minimize access time.
2.2 New system

2.2.1 Proposed Solution for the new System
The new system is designed to solve problems affecting the manual system in use. It is design
to be used web there by relieving the manager or supervisor, employee and any other workers
from much stress as experienced in the manual system. We are going to improve the
drawbacks of the existing system which is manual by developing an automated, user friendly
and interactive graphical user interface system which will:-
 Manage time effectively:-in the proposed system make it reducing the wastage of time
during evaluation with the aid of computer system.
 Make the data error free: - helps to avoid data redundancy or duplication.
 Utilize available resource effectively - minimize the usage of any writing material like
paper, pen and any other material that helps to write report document.
 Make the system computerized: - access all the performance management system
using computer system with the aid of the internet connection.
 Give any feedback to the entire employee to correct their weakness.
 Security: since the system requires verification of logon form, sensitive information’s
will not be accessed or modified by unauthorized users.
 Efficient way of data management: -Since the system uses database system there is no
loose of data.
14 | P a g e
2.2.2 Requirements of the Proposed System

2.2.2.1 Non-Functional Requirement
 Performance: The system provides fast access to user according to their request.
Navigation requires very little Computation and the response time of the system is short.
 Usability: The system interface that we are developing to be interactive and easily
understandable. Employees can easily interact with the system from outside using internet
since it is web based and easy to use it.
 Reliability: The data or information which is retrieved from the system is accurate
(required) in deserved time and easy to load data.
 Availability: Our system is available in everywhere in a JIT; every time and system user
can access who wants to evaluate employee performance using internet access.
 Security: Our system can be accessed only for the authorized user by creating account.
 Portability: our system supports every operating system.
 Error handling: It can tolerate to wrong inputs and prompts the users to correct the inputs.
It guides the users to properly utilize it. It displays a message when the user tries to access
the data that are not available in the data base or make a mistake on the system.
 Extensibility: The system should enable the addition of new functionality or feature
without any restriction.
 Maintainability: The system that we are developing will be easily maintainable and
modifiable for new features.
 User interface requirement
 The User interface of the homepage use attractive color: -the user interface of this
software includes button or link lists in the home page and as well as in the
individual user pages and make it use more appropriate color.
 The interface should be user friendly: - the interface is not ambiguous for any
system user to use it.
15 | P a g e
2.2.2.2 Functional Requirement

Functional requirements which are observable tasks or processes that must be performed by
the system.
The following are the functional requirements of the system.
 Manage users: - the system admin can manage users in case of Add, activate, deactivate
and delete them.
 Manage criteria: - the supervisors manage criteria in case of adding and updating the
criteria that were added before as needed.
 Manage examinee/er (examinee and examiner): - the supervisor can set and update the
examinee/er (examinee and examiner) for different time schedule.
 Make evaluation: - all the examiners can evaluate or examine the examinee how he or
she performs his or her work efficiently and effectively.
 View result: -only the examinee and supervisor can see the evaluation results how much
he or she can got out of one hundred.
 Generate report: - system generates the report that result of each examinee or employee
must be submitted to the supervisor and HRM.
 View report: - the HRM view or read all the prepared report that were send from
supervisor.
 Send notification:-all the system users can send any notification in the form of message
between them except the system admin.
 View notification: - all the system- users can view or read the notifications that were
send by the other users except the system admin.
16 | P a g e
2.2.3 System Models

Use case Diagram
Relationship between actors and use cases exists whenever an actor is involved with an
interaction described by a use case and modeled as a line connecting use cases and actors. In
order to create relevant use cases for the system, we used the following actors for the system
has been identified:
 Colleague: - Colleague is one of the participators in the evaluation system can which
evaluate the examinee and notify.
 Student evaluation:- participants who evaluates university lecturers according to
criteria stored on database by supervisor
 Supervisor: -the supervisor sets the examinee/er (examinee and examiner), update
examinee/er (examinee and examiner), add and update criteria and make the
evaluation. .
 HRM: -who can view the report and exchange notification system.
 Admin: - control the overall of the system by creating, activate, deactivating and
deleting system users.
17 | P a g e
Figure 2.1 use case Diagram
18 | P a g e
Use case documentation

Use case name Login
UC_ID UC_01
Actors All actor of the system
Description All are enters authorized username and
password to access the system.
Precondition Any user who wants to access the system’s
functionality should able to login and have
an account.
Basic course of action 1. The user opens the login page
2. The system displays login form that
accepts username and password from
user
3. The users enter their username and
password
4. The user clicks on login button
5. The system searches username from
data base and match it with password.
6. If the entry is correct, the system take
the user into his/her page
7. End of case
Alternative course of action 6A The system display error message

6B. The system let user to enter again or
takes steps of 2,3,4 and 5 basic flow events
6C.End of case
Post condition The users are reached to the official page.
Table 2.1 Login Use case Table
19 | P a g e
Use case name generate report

UC_ID UC_02
Actor Supervisor
Description Organize and send employee evaluation result reports to the HRM.
Precondition UC_01, prepare their own report.
Basic course of action 1. User opens their own homepage.
2. The user clicks the report link.
3. System displays the report form.
4. The users write the report.
5. User clicks the send button.
6. System Save reports in to database.
7. The system displays successfully send message.
8. Use case end
Alternative course of 5A. blank or empty space.
action 5B.system displays message “ fill space before sending”
5C .user back to step 4.
6A. use case end.
Post condition The report is generated and The system displays successfully send
message.
Table 2.2 generate report use case table
20 | P a g e
Use case name Notify

UC_ID UC_03
Actor HRM, Supervisor, Examinee/er and colleague
Description UC_01, All the users of the system can send notification between
them.
Pre-condition User must have some feed backs or messages to be send.
Basic course of action 1. User click on send notification link on their individual page.
2. The system displays the notification page.
3. User writes message in the form of notification.
4. User clicks the send link.
5. System display successfully send notification message.
6. Use case end
Alternative course of action 4A. empty space or not write notification.
4B. system display message “fill the space before click button ”
4C. User back to step 3
5A. use case end.
Post condition Users send notification to the appropriate person.
Table 2.3 Send notification use case table
Use case name View notification

Actors HRM, Supervisor, Examinee and colleague
UC_ID UC_04
Description Each user views the notification that sent between them.
Pre-condition UC_01, other users must have send some messages.
Basic course of action 1. .The system gives notification on notification panel.
2. The user clicks on notification to browse information.
3. Visit information.
4. Use case end
Post condition Read or view all the notifications and reply it.
Table 2.4. View notification Use case Table
21 | P a g e
Use case name Manage users
UC_ID UC_05
Actor Admin
Description The admin of the system can Add, activate, deactivate and delete
any user of the system.
Pre-condition Admin must be login to system.
Basic course of action 1. System displays Admin page.
2. Admin clicks manage users link.
3. Admin Select an option from the lists.
4. Admin edit the necessary profile.
5. Click Save button.
6. Use case end
Post condition Employee changes the necessary information.
Table 2.5. Manage users use case table
22 | P a g e
Use case name Make evaluation

UC_ID UC_06
Actors Examiner(colleague, supervisor, students)
Description Evaluation of employee performance is the major activities for
knowing the work level of the employee.
Pre-condition UC_01, know the assigned examinee and read the criteria.
Basic course of action 1. Examiner Open users’ homepage.
2. Examiner Click evaluation link.
3. System displays all the necessary evaluation criteria were with
its provided filling space.
4. User fills the points to each criterion.
5. User clicks submit button.
6. A system calculates and stores the result into database.
7. System display messages “evaluation successfully”.
8. Use case end
Alternative course of 5A. User inserts incorrect value (letter).
action 6A. system display message “field accepts only number”.
7A. empty space.
8A. use case end
Post condition Examiners logout from the system.
Table 2.6. Make Evaluation Use Case table
23 | P a g e
Use case name Logout

UC_ID UC_07
Actors All users or actors of the system.
Description The user logouts when he/she wants to

back home page or exit from the system
Precondition UC_01, Users finish their activities.
Basic course of action 1. user clicks the log out button
2. The system responds to the requested action.
3. System returns the users to the home page.
4. Use case end.
Post condition User logs out or sign out.
Table 2.7. Logout use case Table
24 | P a g e
Use case name set examinee/er (examinee and examiner)

UC_ID UC_08
Actors Supervisor
Description The supervisor set the examinee/er (examinee and examiner) to
make the evaluation.
Precondition UC_01, need have examinee/er (examinee and examiner) in
database.
Basic course of action 1. Supervisor clicks the examinee/er (examinee and examiner)
link.
2. System displays page contains list of the examinee/er
(examinee and examiner).
3. Supervisor writes the examinee/er (examinee and examiner)
on displayed page.
4. Supervisor submitted it.
5. System Save in to the database.
6. Message from system successfully set examinee/er
(examinee and examiner).
7. Use case end.
Alternative course of action 4A. empty space.
5A.repetitions of examinee/er (examinee and examiner) list or
IDNO.
6A. incorrect IDNO.
7A. use case end.
Post condition Supervisor logout from the system.
Table 2.8. Set examinee/er (examinee or examiner) use case Table
25 | P a g e
Use case name Update examinee/er (examinee and examiner)

UC_ID UC_09
Actor Supervisor
Description The supervisor updates the examinee/er (examinee and examiner) if it
needs change.
Pre-condition UC_01, Set the examinee/er (examinee and examiner) first to be
updated.
Basic course of action 1. Supervisor opens his or her home page.
2. Supervisor Clicks examinee/er (examinee and examiner) link.
3. Supervisor Updates examinee/er (examinee and examiner) from
the given examinee/er (examinee and examiner) option.
4. System display updated form.
5. User search or retrieve from database by using IDNO.
6. System display list of examinee/er (examinee and examiner).
7. Supervisor Select submit button.
8. System Save and change in database.
9. System display “Successfully updated examinee/er (examinee
and examiner).”
10. Use case end.
Alternative course of action 4A. incorrect IDNO.
Post condition User closes it and logs out from the system.
Table 2.9. Update Examinee/er use case table
26 | P a g e
Use case name Manage criteria

UC_ID UC_010
Actor Supervisor
Description Criteria are managed with in specific period of time for success.
Pre-condition UC_01, evidence for managed.
Basic course of action 1. Supervisors open the page.
2. Supervisor clicks the criteria option link.
3. System displays criteria page.
4. Supervisor Select criteria.
5. Supervisors add or update the criteria.
6. System retrieves from database or file document.
7. Supervisor Save in to database.
8. Supervisor Send to users.
9. System displays success fully send message.
10. Use case end
Alternative course of action 4A.empty selection.
4B. back to step 4
5A. use case end.
5B. incorrect selection (IDNO).
6B. use case end.
Post condition The supervisor Logs out from the system.
Table 2.10. Manage Criteria use case table
27 | P a g e
Use case name View report

UC_ID UC_011
Actor HRM
Description The HRM read the reported result of the employee about their
performance.
Pre-condition Report must be submitted from the supervisor.
Basic course of action 1. User opens his or her home page.
2. User Clicks report link.
3. System retrieves report from database.
4. System displays the reported information.
5. User view or read the report.
6. Use case end
Alternative course of action 3A. empty report.
4A.use case end.
Table 2.11. View Report use case table
28 | P a g e
Use case name View result

UC_ID UC_012
Actor Examinee and supervisor
Description The examinee can view the final result which is given by all the
examiners additionally by supervisor calculates and send to him or her.
Pre-condition UC_01, Examinee must be evaluated by the entire examiner.
Basic course of action 1. Examinee/supervisor opens his or her home page.
2. Examinee/supervisor clicks result link.
3. System retrieves result from database.
4. Examinee/supervisor view or read the result.
5. Use case end
Alternative course of action 3A. empty result in database.
3B. use case end.
Table 2.12. View Result use case table
2.2.4 Dynamic models

2.2.4.1 Sequence diagram
A sequence diagram shows object interactions arranged in time sequence. It is dynamic
model of use cases, showing the interaction among classes during a specified time
period. A sequence modeling in our system is used to formalize the behavior of the
system and to visualize the communication among objects. It helped us to identify
additional objects and participate in the use case. This phase of the document ties uses cases
with objects and shows the behavior of a use case is distributed among its participating
objects.
29 | P a g e
Figure 2.2 Sequence Diagram for Login
30 | P a g e
Figure2.3.Sequence diagram for view notification
31 | P a g e
Figure2.4.Sequence diagram for set examinee/er
32 | P a g e
Figure 2.5. Sequence diagram for update examinee/er
33 | P a g e
Figure 2.6. Sequence diagram for generate Report
34 | P a g e
Figure 2.7. Sequence diagram for Make evaluation
35 | P a g e
Figure 2.8. Sequence diagram for Manage criteria
36 | P a g e
2.2.4.2 State Chart diagram

State chart diagram shows the states the object (class) passes through in its life. This model
guide how objects in our system change from one state to another and when the change
happens.
Figure 2.9. State chart diagram for Login
37 | P a g e
Figure 2.10. State chart diagram for Manage users
38 | P a g e
2.2.4.3 Activity Diagram

We use activity diagrams to show the operations/activities performed by use cases to achieve
their functionality. Activity diagrams are drawn for each use case of the system
Figure 2.11. Activity diagram for Login
39 | P a g e
Figure 2.12. Activity diagram Make evaluation
40 | P a g e
Figure 2.13. Activity diagram for Manage criteria
41 | P a g e
Figure 2.14. Activity diagram for send notification
42 | P a g e
Figure 2.15. Activity diagram for View Notification
2.2.5 Conceptual Modeling

Class Modeling in the Unified Modeling Language (UML) is a type of static
structure Modeling that describes the structure of a system by showing the
system's classes, their attributes, operations (or methods), and the relationships
among objects.
Class Diagram
Create a class diagram is diagram that we will use to build block the system we
will develop. Our Class diagrams should show the objects and how they are
interrelated.
43 | P a g e
Figure 2.16. Class Diagram
44 | P a g e
2.2.6 User interface prototyping
Figure 2.17 interface prototype
45 | P a g e
CHAPTER 3
SYSTEM DESIGN
3.1 Introduction
System Design phase is process of describing, organizing, and structuring system
components at architectural design level and detailed design level. Build a system Design
converts functional models from analysis into models that helps to represent the solution for
the problem.
The analysis model describes the system completely from the actors’ point of view and serves
as the basis of communication between the client and the developers. The analysis model,
however, does not contain information about the internal structure of the system, its
hardware configuration, or, more generally, how the system should be realized. And System
design is the transformation of the analysis model into a system design model.
In this chapter, we define the design goals of our project and decompose the system into
smaller subsystems that it can be understandable. We also select strategies for building the
system, such as the hardware/software platform on which the system will run the persistent
data management strategy and the access control policy. The result of this chapter is a model
that includes a clear description of each of these strategies, a subsystem decomposition,
and a UML deployment diagram representing the hardware or software mapping of the
system.
46 | P a g e
3.2. Purpose and goal of design

The purpose of the proposed system design part is very important so as to make the
implementation of the proposed system very easy. The different types of the system modeling
techniques that are used to make easy the implementation of the system such as deployment
and component modeling are show in detail
The design goals are to describe the structure of the system, including any subprograms to be
used along with the packaging of the system. Design goals describe the qualities of the
system that developers should achieve. Such goals are normally derived from the
nonfunctional requirements of the system described earlier.
 User Interface: The user interface of the system should be easy to use by each user of the
system with little training. Our interface contains different buttons which guide the Users
what to click and fill to enter to their page to do what they want. So the user interface is
easy to use. We also use different icons, buttons, frames and light colors to make
attractive interface. We also do our system clear which means the interface shows where
to go in the system.
 Security: user’s account is created by the system administrator, so, no one can’t create an
account by themselves and use the system. But person who has an account can login to
the system using his/her username and password and use the system.
 Fault Tolerance: The system should be able to give response (error message) when the
user enter incorrect input. If users enter incorrect data like username, password and
invalid fields the system displays an error message which informs the user to enter the
correct information. To do this, we apply validation using java script.
 Extensibility: The system should enable the addition of new functionality without any
restriction.
 Portability: The system should work in different platforms, for there could be platform
shifting in the future and the work to have the acceptance of different institutes having the
different platforms.
47 | P a g e
3.3. Current software architecture

JIT employee performance management system uses manual system for recording any
employee performance evaluation result as well as any employee information. The
current employee performance management system in JIT, there is no the software
architecture.
3.4. Proposed software Architecture

3.4.1 Overview
For JIT employee performance Management System or for the proposed system we used the
three tier architecture.
 The presentation layer (UI):- occupies the top level part and displays information
related to services available on website.
 The Service/application tier: - is the middle tier which is pulled from the user interface. It
performs controlling the application functionalities by performing detailed processing.
 The data tier (DB):- is a house for database servers where information is stored and
retrieved.
The server will give response based on the user request. From this description the architecture
of the system is depicted diagrammatically.
Figure3.1. system software architecture
48 | P a g e
3.4.2 Subsystem Decomposition

Subsystem decomposition is the process by which a complex problem or system is broken
down into modules that are easier to conceive, understand, program, and maintain. It
breaks a large system down into progressively smaller classes or objects that are
responsible for some part of the problem domain.
 criteria subsystem: -
 add new criteria
 update existing criteria
 examinee/er(examinee and examiner) subsystem: -
 set examinee/er(examinee and examiner)
 set examinee
 set examiner
 update examinee
 update examiner
 update examiner
 evaluation subsystem: -
 make evaluation
 users subsystem: -
 add users
 Activate users
 deactivate users
 Delete users account
 Report subsystem: -
 send report
 View report
 Notification sub system:-
 Send notification
 View notification
49 | P a g e
Fig 3.2.Subsystem Decomposition
50 | P a g e
3.4.3 Component diagram

Components of the system will be wired this shows that there is relation among components;
management of the system, database and operations performed on databases such security
issues.
Fig 3.3.Component diagram
51 | P a g e
3.4.4 Deployment Diagram

Deployment diagrams models the physical architecture of a system, and it shows the
relationships between the software and hardware components in the system and the physical
distribution of the process
Fig 3.4 Deployment diagram
52 | P a g e
3.4.5 Database Design
Fig 3.5. Database design diagram
53 | P a g e
3.4.6 Persistence Model of object oriented Database

3.4.6.1 Mapping
54 | P a g e
Fig 3.6. Persistent Diagram
55 | P a g e
3.4.7 Access control and database

In this system, there are multiple actors which have access to different functionality and data.
Access control and security specifies what the user can access or what cannot perform by
some users. The following table shows access control of our system.
Operator Actors
Head HRM Examinee Examiner Admin

Login     
Make
evaluation()   

Manage users()
Notify()    
View
notification()    
View result()   
Table 3.1. Access control table
56 | P a g e
CHAPTER FOUR
4. IMPLEMENTATION AND TESTING

4.1 Introduction
The main purpose of this phase of documentation is to see issue related with the
transformation of design phase to implementations phase. Design phase which is considered
as input for implementation phase. The functional requirement of the system from the design
phase above is the key input to the implementation phase. This to put the overall system into
real working system by identifying other technical problem on the system. In this phase the
tools and language that we use to develop the system is HTML and PHP. Our system
contains front end and back end as every system. The front end is implemented using HTML
and the back end is developed using PHP. This system is tested using different system testing
method and integrated to gather.
4.2 Objective of Implementation

The main objective of the implementation is to transform the design into actual system. Using
HTML and PHP the functional requirement which is clearly mentioned in previous phase is
implemented. The resource management system for JIT implementation is the Specific
objective of this implementation. Implementation is the process of ensuring that the
information system is operational and used. It also ensures that the information system meets
the quality standard (quality assurance of the system).
4.3 Constraints on Implementation

The constraints are some kind of requirement that can impose to our system from
environment. It can be considered as restriction that show the project's limitations the three
most significant project constraints are schedule, cost and scope are sometime known as the
triple constraint or project management. The schedule (sometimes stated more broadly as
time) specifies the timeline according to which those components will be delivered, including
the final deadline for completion. Cost (sometimes stated more broadly as resources)
involves the financial limitation of resources input to the project and also the overall limit for
the total amount that can be spent. Project constraints are also considered to be somewhat
mutually exclusive. In the project management triangle, it is assumed that making a change to
one constraint will affect one or both of the others. For example, increasing the scope of the
project is likely to require more time and money. That reality is also expressed as the pick
two principle, which maintains that for any given set of three desired qualities or expectations
such as "good, fast and cheap" it is likely that only two can coexist: A given product might
57 | P a g e
be delivered quickly and inexpensively, for example, but the quality will suffer. It can be
considered as restriction that show the project's limitations.
4.4 Testing
Testing is a trial experience in which the deliverables of the project are checked with acceptable
stands in project. There are three types of testing used in many testing endeavors.
4.5 Testing by requirement

Requirements-based testing is a testing approach in which condition and data are derived the
requirements. These requirement are functional and non-functional requirement of the system .The
requirement of the system is what the system do while no requirement of system are the requirement
that add the quality of system to make functional requirement of system to be fulfilled .These non-
functional requirement includes attributes such as performance, reliability or usability. Once source
code has been generated, system must be tested to uncover (and correct) as many errors as possible
before delivery to user. This by Exercising the input and output of the program to cover errors in
program function, behavior and performance. Our system handles error by displaying the error
message when the user enters wrong input/data. For instance when user enter password if old
password and new password doesn't much it tell to user that mismatch problem. For security purpose
the next is MD5 (message digesting algorithm) which is one part of hashing function whose main
purpose is to verify that a file is unaltered.
4.6 Testing by Scope

4.6.1 Unit Testing
The unit testing is types of testing which use to verify the functionality of the specific section
of code at functional level. In this type of testing, components are tested individually. The
goal of unit testing is to isolate each part of the program and show that the individual parts
are correctly programmed or not. Each unit test is tested separately before integrating them
into modules to test the interfaces between modules. While implementing the code all
small components such as functions, conditional statements, loops and others were tested.
For instance while employee registration, using system the account created for employee. If
password not much system display that password is not match. This unit testing which check
using loops whether the two are equal.
58 | P a g e
4.6.2 Integration and System Testing

After unit testing, our system is also tested whether every unit is integrated to every other
unit. The integration testing identifies the problems that occur when the units are combined.
Integration testing tests the interface between modules of the software application. The
different modules are first tested individually and then combined to make a system. Testing
the interface between the small units or modules is integration testing.
System testing is testing of software application as a whole to check if the system is

complaint with the user requirements. It is end to end user perspective testing intended to find
defects of the software system. System testing is kinds of black box testing technique thus the
knowledge of internal code is not required. It is high level testing that is always performed
after integration testing. JIT Employee performance management system which we have
developed is tested to check if all modules or the whole system is working properly as
intended.
59 | P a g e
Figure 4.1 Home page
60 | P a g e
Figure 4.1 Login Form
Figure 4.3 Boss home page
61 | P a g e
62 | P a g e
Fig : Teacher result
Fig Hrm total result
63 | P a g e
4.7 Sample Code and Sample output Screen
<?php
session_start();
require('dbconfig.php'); ?>
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width, initial-scale=1">
<meta name="description" content="">
<meta name="author" content="">
<title>JIT</title>

<link href="css/bootstrap.min.css" rel="stylesheet">

<link href="css/modern-business.css" rel="stylesheet">

<link href="font-awesome/css/font-awesome.min.css" rel="stylesheet" type="text/css">
</head>
<body>

<nav class="navbar navbar-default navbar-fixed-top" role="navigation"

style="background:#66CCFF">
<div class="container" >

64 | P a g e

<div class="navbar-header">
<button type="button" class="navbar-toggle" data-toggle="collapse" data-

target="#bs-example-navbar-collapse-1">
<span class="sr-only">Toggle navigation</span>
<span class="icon-bar"></span>
</button>
<a class="navbar-brand" href="index.php" style="color:#FFFFFF" >JIT Web

Based Employee Performance Management System</a>
</div>

<div class="collapse navbar-collapse" id="bs-example-navbar-collapse-1">
<ul class="nav navbar-nav navbar-right">
<li style="color:#FFFFFF">
<a style="color:#FFFFFF" href="index.php"><i class="fa fa-home fa-

fw"></i>Home</a>
</li>
<li style="color:#FFFFFF">
<a style="color:#FFFFFF" href="index.php?info=about"><i class="fa fa-

home fa-fw"></i>About</a>
</li>
<li class="dropdown">
<a style="color:#FFFFFF" href="#" class="dropdown-toggle" data-toggle="dropdown"

href="#"><i class="fa fa-sign-in fa-fw"></i>Login
65 | P a g e
<span class="caret"></span></a>
<ul class="dropdown-menu">
<li><a href="index.php?info=login">Student</a></li>
<li><a href="index.php?info=boss_login">boss</a></li>
<li><a href="index.php?info=faculty_login">Faculty</a></li>
<li><a href="index.php?info=hrm_login">Hrm</a></li>
<li><a href="admin">Admin</a></li>
</ul>
</li>
<li>
<a style="color:#FFFFFF" href="index.php?info=contact"><i class="fa fa-

phone fa-fw"></i>Contact</a>
</li>
</ul>
</div>

</div>

</nav>
<?php
@$info=$_GET['info'];
if($info!="")
if($info=="about")
66 | P a g e
include('about.php');
else if($info=="contact")
include('contact.php');
else if($info=="login")
include('login.php');
else if($info=="boss_login")
include('boss_login.php');
else if($info=="hrm_login")
include('hrm_login.php');
else if($info=="faculty_login")
include('faculty_login.php');
// else if($info=="registration")
67 | P a g e
//include('registration.php');
else
?>

<header id="myCarousel" class="carousel slide">

<ol class="carousel-indicators">
<li data-target="#myCarousel" data-slide-to="0" class="active"></li>
<li data-target="#myCarousel" data-slide-to="1"></li>
<li data-target="#myCarousel" data-slide-to="2"></li>
</ol>

<div class="carousel-inner">
<div class="item active">
<div class="fill" style="background-image:url('images/logo.jpg');"></div>
<div class="carousel-caption">
</div>
</div>
<div class="item">
<div class="fill" style="background-image:url('images/11.jpg');"></div>
68 | P a g e
</div>
</div>
<div class="item">
</div>
</div>
<div class="item">
</div>
</div>
<div class="item">
<div class="fill" style="background-image:url('images/jit.png');"></div>
</div>
</div>

69 | P a g e
<a class="left carousel-control" href="#myCarousel" data-slide="prev">
<span class="icon-prev"></span>
</a>
<a class="right carousel-control" href="#myCarousel" data-slide="next">
<span class="icon-next"></span>
</a>
</header>


<div class="container">
<div class="row">
<div class="col-lg-12">
<div class="col-sm-10" style="size:3 margin-top:60px;margin-bottom:80px">
<h2><marque>JIT employee performance Evaluation and

management System</marque></h2>
</div>
<?php } ?>
</div>
</div>

<div class="navbar-fixed-bottom nav navbar-inverse text-center"

style="padding:15px;height:40px; background:#66CCFF">
<span style="color:#FFFFFF">Developed By ....... 2019 IT graduated student

</span>
70 | P a g e
</div>

<script src="css/jquery.js"></script>

<script src="css/bootstrap.min.js"></script>

<script>
$('.carousel').carousel({
interval: 5000 //changes the speed
})
</script>
</body>
</html>
4.8 Installation
The installation process is the method of converting the run code to actual use by users. After
code is written and run the following are required for installation of system.
Web Server with PHP: This is the software server that controls the web communication between
the Web Host Server (Hardware Web Server) and each Web Client (user browser).
Database Server: We used MySQL for the backend database server which uses to store each and
every table of the system for permanent storage. Information stored in database is accessed using Ip
address of the host or using local host if on one machine.
User Browser: This is the application that user used to browse the server in order to get the service
from server. This application is Firefox, internete explorer, opera and safari.
71 | P a g e
CHAPTER FIVE
CONCLUSIONS AND RECOMMENDATIONS

5.1 Conclusions
Implementing the analyzed and designed web based performance management system might
be the best solution to the current major JIT employee performance management problem, as
it will provide web based performance evaluation result so, every legal employee who uses
the system can evaluate his or her colleague and the system displays result for Examinees.
Accordingly hrm visit or read all given result for each employees and give some conclusions
based on the evaluation result of each employee how they perform their tasks to achieve the
goal of the organization.
5.2 Recommendations
The system that we have developed involves web based employee performance management system
for JIT, which means it’s a huge system. So it is very difficult to include all functionality of the
performance management systems in each and every staffs and departments so we only concerned the
online performance evaluation system for Academic staffs. Therefore, we recommend the following
features need to be included in any further revision and extension attempt.
1. Integrate with the bank system for salary payment.

2. We recommend that the systems give the motivational activity like reward.
3. The system it could be integrated with android based application by which each employee
using their own smart phone.
4. We recommend that to include the entire organization employee performance measurement.
72 | P a g e
5.3 APPENDIX
Questions asked during requirement gathering using interview
What are the objectives of your organization?
What is the mission of your organization?
How many staffs do you have?
How does your current system work?
Is it manual?
Is it computerized?
Is it semi-automated?
If your answer for question number 4 is choice “b” or “c” what computer applications do you
use?
How the employee can be evaluated?
What are the procedures or steps when the employee is evaluated?
What qualifications are expected from employee?
How do you store employee and other information’s?
What are the problem that you get when the organization use the existed system?
What are the employees that included within the system?
73 | P a g e

Final Project Document

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

Final Project Document

Uploaded by

Copyright:

Available Formats

JIMMA UNIVERSITY

JIMMA INSTITUTE OF TECHNOLOGY

Submitted to: Faculty of Computing

2.2.3 System Models .............................................................................................................. 17

CHAPTER FIVE ............................................................................................................................ 72

1.1 Problem statement

1.2 Significant of the project

 Focuses employees on self-development

 Minimizing and equalizing of rater bias (unfair)

 Increases team orientation and communication channels

 Increase productivity and manage problems

 lower cost in completing each process

 Better management and efficient information flow

1.3. Proposed system

1.4 Objective of the projects

1.4.2 Specific Objective

1.5 Scope of Project

 Manage users: -Add, activate, deactivate and delete system users.

1.6.2 System Analysis and Design Methodology

1.6.2.1. Case Tool

1.6.2.1.2 Software tools: -

1.7 .System Development Environment

1.8 Testing Procedures

1.8.1 Unit Testing

1.8.2 Integration Test

1.8.3 System Testing

1.9 Project schedule

Tasks Start Finish Duration

Fig 1: Gant Chart

2.1.1 BUSINESS RULE

 The existing system includes the following operating principles or rules:

BR1. Colleague & supervisors should be participate in evaluation

BR1. . Employee evaluated in a semester.

2.1.2 Existing system players

 In the administrative staff there are different departments. Which includes:-

2.1.3 Functions and Activities in the Existing System

2.1.4 Report Process in the Existing System

 In all staff’s employee can be examined by: -

2.1.5 Bottlenecks of the Existing System

2.1.6. Practices to be preserved

 In the existing system it increases a good relationship between each employee in

2.2 New system

2.2.2 Requirements of the Proposed System

2.2.2.2 Functional Requirement

2.2.3 System Models

Figure 2.1 use case Diagram

Use case documentation

Alternative course of action 6A The system display error message

Post condition The users are reached to the official page.

Table 2.1 Login Use case Table

Use case name generate report

Table 2.2 generate report use case table

Use case name Notify

Table 2.3 Send notification use case table

Use case name View notification

Table 2.4. View notification Use case Table

Use case name Manage users

Table 2.5. Manage users use case table

Use case name Make evaluation

Table 2.6. Make Evaluation Use Case table

Use case name Logout

Description The user logouts when he/she wants to

Table 2.7. Logout use case Table