There were three actors, namely employees, head
of division and administrator. Actors are connected
with multiple use cases i.e. user authentication,
submitting a leave that must check the remaining
leave from the user. Status of leave, approve leave,
manage master data, and archive submission report.
All of the use cases are functional requirement that
will be implemented in the system.
2.4 Entity Relationship Diagram
Entity Relationship Diagram is a network model that
uses the data arrangement that is stored in the system
in an abstract model (Larman, 2007). In Figure 4,
there are 7 entities and 6 relationships. The 7 entities
are users, leave, study programs, units, types, HR, and
email. Each entity has attribute, and relationships
with another entities. Like user entity that has a
relationship with leave entity, Prodi, and unit. While
the leave entity has a relationship with personnel
entities, HR department, email, and users.
2.5 Class Diagram
Class diagram shows relationship between the classes
and the detailed explanation of each classes in design
mode of a system (Ladjamudin, 2013). Class diagram
design for the system is depict in Figure 5. There were
17 classes in the system. These classes have a
relationship according to their function, such as user
class that corresponds to user controller, and leave is
associated with submission controller. The class
design is based on model view controller where there
are view class that act as user interface, control class
that has function and procedure, and the model class
that connect to the data.
3 IMPLEMENTATION AND
TESTING
The system was built by using Yii2 framework with
PHP 5.6.40 version, and MySQL database. Yii2 is a
PHP-based open source framework. It has adopted
MVC concept or model, view and controller. MySQL
is the popular open source database software.
3.1 Database Implementation
The database implementation is based on the ER
Diagram design in the Figure 4. There were seven
tables for database, namely users, leave, units, study
programs, supervisor, types and e-mail. We also
integrate the leave management system
authentication with single sign on system that exist in
Polibatam. With this integration, the system doesn’t
need to store the information about authentication.
User can use one identity to authenticate into the
leave management system.
3.2 Interface Implementation
Interface implementation implements the user
interface that user can use to interact with the system.
1. Leave Application Page
In this page, there is an application form.
This form filled by employee to apply for
leave. The employee needs to state the leave
type, start date, number of working days and
reason of leave, the page is depicted in
Figure 3.
2. Application Status Page
This page shows the status of requested
leave for employee. As in the Figure 6,
employee can monitor whether the leave
application has been approved.
3. Lists of request application page
This page in Figure 7 shows annual leave
information that has been requested and will
be verified by supervisor. This page used by
HR department to get all leave data for all
employee.
4. HR Page
It is page that contain master data of
employee and leave regulation.
5. Report Page
This page shows a report related to staff’s
leave application as an archive.
Figure 3: Leave application page.