Project II

"Leave Management System"

Submitted in partial fulfillment of the requirements for the degree of
Bachelor of Engineering

by

Shaikh Naseema Khudbuddin Halima Roll No. 13CO13

Mirza Bushra Riyazuddin Shenaz Roll No. 12CO04
Yadav Pooja Ramavtar Balashree Roll No. 12CO06

Supervisor
Prof. Mukhtar Ansari
Co-Supervisor
Prof.Rehaal Qureshi

Department of Computer Engineering,

School of Engineering and Technology
Anjuman-I-Islam’s Kalsekar Technical Campus
Plot No. 2 3, Sector -16, Near Thana Naka, Khanda Gaon,
New Panvel, Navi Mumbai. 410206

Academic Year : 2016-2017

 CERTIFICATE

Department of Computer Engineering,

School of Engineering and Technology,
Anjuman-I-Islam’s Kalsekar Technical Campus
Khanda Gaon,New Panvel, Navi Mumbai. 410206

This is to certify that the project entitled "Leave Management System" is a bonafide work of
Shaikh Naseema Khudbuddin Halima(13CO13), Mirza Bushra Riyazuddin Shenaz(12CO04)
and Yadav Pooja Ramavtar Balashree(12CO06) submitted to the University of Mumbai in
partial fulfillment of the requirement for the award of the degree of Bachelor of Engineering
in Department of Computer Engineering.

Prof. Mukhtar Ansari Prof. Javed Sheikh

Supervisor Project Co- Coordinator

Prof. Tabrez Khan Dr. Abdul Razak Honnutagi

Head of Department Director

 Project I Approval for Bachelor of Engineering

This project entitled "Leave Management System" by Shaikh Naseema Khudbuddin Halima,
Mirza Bushra Riyazuddin Shenaz and Yadav Pooja Ramavtar Balashree is approved for the
degree of Bachelor of Engineering in Department of Computer Engineering.

Examiners

1. ..............................
2. ..............................

Supervisors

1. ..............................
2. ..............................

Chairman
.............................
 Declaration

We declare that this written submission represents my ideas in my own words and where oth-
ers ideas or words have been included, We have adequately cited and referenced the original
sources. We also declare that We have adhered to all principles of academic honesty and in-
tegrity and have not misrepresented or fabricated or falsified any idea/data/fact/source in my
submission. We understand that any violation of the above will be cause for disciplinary action
by the Institute and can also evoke penal action from the sources which have thus not been
properly cited or from whom proper permission has not been taken when needed.

Shaikh Naseema Khudbuddin Halima

Roll Number:13CO13

Mirza Bushra Riyazuddin Shenaz

Roll Number:12CO04

Yadav Pooja Ramavtar Balashree

Roll Number:12CO06
Abstract

Tittle : Leave Management System

In the existing Leave Record Management System, every College/Department follows manual
procedure in which faculty enters information in a record book. At the end of each month/session,
Administration Department calculates leave/s of every member which is a time taking process
and there are chances of losing data or errors in the records. This module is a single leave man-
agement system that is critical for HR tasks and keeps the record of vital information regarding
working hours and leaves. In this module, Head of Department (HOD) will have permissions
to look after data of every faculty member of their department.HOD can approve leave through
this application and can view leave information of every individual. This application can be
used in a college to reduce processing work load. Leave management application will reduce
paperwork and maintain record in a more efficient systematic way.

Shaikh Naseema Khudbuddin Halima

Roll No: 13CO13

Mirza Bushra Riyazuddin Shenaz

Roll No: 12CO04

Yadav Pooja Ramavtar Balashree

Roll No: 12CO06
B.E. (Computer Engineering)
University of Mumbai.

iv
 Contents

Project I Approval for Bachelor of Engineering . . . . . . . . . . . . . . . . . . . . ii

Declaration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii
Table of Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
List of Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Keywords And Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x

1 Project Overview 1
1.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.1.1 Background Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.1.2 Motivation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.2 Problem Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.3 Current Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.4 The Problems with Current System . . . . . . . . . . . . . . . . . . . . . . . . 3
1.4.1 Advantages Over Current System . . . . . . . . . . . . . . . . . . . . 3
1.5 Goals and Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.6 Scope and Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.7 Report Organization: briefly explains all the chapters and their focus . . . . . . 4

2 Review Of Literature 5
2.1 HR e-Leave Tour Management System at RDCIS, SAIL . . . . . . . . . . . . 5
2.1.1 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.1.2 Pros . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.1.3 Cons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.1.4 How we overcome Those problem in Project . . . . . . . . . . . . . . 6
2.2 E-Notifier: Transport Information Services in Colleges and Exploring Mobile
Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2.2.1 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2.2.2 Pros . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2.2.3 Cons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2.2.4 How we overcome Those problem in Project . . . . . . . . . . . . . . 6
2.3 http://www.timeoffmanager.com . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.3.1 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.3.2 Key Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

v
 2.3.3 Screenshot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.4 http://www.planmyleave.com . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
2.4.1 Key Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
2.4.2 Screenshot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2.5 http://adp.in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.5.1 Key Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.6 Technological Review . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.6.1 Ajax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.6.2 CSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
2.6.3 HTML . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
2.6.4 JavaScript . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
2.6.5 jQuery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
2.6.6 Materialize . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
2.6.7 MySQL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
2.6.8 PHP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

3 Requirement Analysis 13
3.1 Platform Requirement : . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
3.1.1 Supportive Operating Systems : . . . . . . . . . . . . . . . . . . . . . 13
3.2 Software Requirement : . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
3.3 Hardware Requirement : . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

4 System Design and Architecture 15

4.1 System Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
4.2 Usecase Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
4.3 Class Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
4.4 Data Flow Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
4.5 Component Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

5 Methodology 20
5.1 Modular Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
5.1.1 Admin Interface Module . . . . . . . . . . . . . . . . . . . . . . . . . 20
5.1.2 Leave Admin Module . . . . . . . . . . . . . . . . . . . . . . . . . . 21
5.1.3 User Interface Module . . . . . . . . . . . . . . . . . . . . . . . . . . 21
5.2 Sequence Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
5.3 Activity Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
5.3.1 Activity For Employee of Leave Management System . . . . . . . . . 23
5.4 Flow-Chart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

6 Implementation Details 27
6.1 Assumptions And Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . 27
6.1.1 Assumptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

vi
 6.1.2 Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
6.2 Implementation Methodologies . . . . . . . . . . . . . . . . . . . . . . . . . . 27

7 Results and Analysis 31

7.1 Test cases and Result . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
7.2 Analytical Discussion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

8 Conclusion and Future Scope 36

8.1 Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
8.2 Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
8.3 Future Enhancement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

References 38

9 Appendix A 39
9.1 Earned Leave or Privilege Leave: . . . . . . . . . . . . . . . . . . . . . . . . . 39
9.2 Casual Leave: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
9.3 Sick Leave or Medical Leave: . . . . . . . . . . . . . . . . . . . . . . . . . . 39
9.4 Maternity Leave: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
9.5 Study Leave or Sabbatical Leave: . . . . . . . . . . . . . . . . . . . . . . . . 40

Acknowledgment 41

vii
 List of Figures

2.1 Time-Off Request Information . . . . . . . . . . . . . . . . . . . . . . . . . . 7

2.2 General Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
2.3 User Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
2.4 Login Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2.5 Search Leave Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2.6 Requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

3.1 XAMPP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
3.2 Web Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

4.1 System Architecture For Leave Management System . . . . . . . . . . . . . . 15

4.2 Usecase diagram For Leave Management System . . . . . . . . . . . . . . . . 16
4.3 Class Diagram For Leave Management System . . . . . . . . . . . . . . . . . 17
4.4 Level 0 Data Flow Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
4.5 Level 1 Data Flow Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
4.6 Component diagram For Leave Management System . . . . . . . . . . . . . . 19

5.1 Application Interface Module . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

5.2 Leave Admin Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
5.3 User Interface Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
5.4 Sequence Diagram for Leave Management System . . . . . . . . . . . . . . . 22
5.5 Activity Diagram for Employee . . . . . . . . . . . . . . . . . . . . . . . . . 23
5.6 Activity Diagram System for Admin . . . . . . . . . . . . . . . . . . . . . . . 24
5.7 Activity Diagram for HOD . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
5.8 Flow Chart For Leave Management System. . . . . . . . . . . . . . . . . . . . 26

6.1 Flow Chart Of User. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

6.2 Flow Chart Of Admin. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
6.3 Flow Chart Of HOD. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

7.1 Home Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

7.2 Login Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
7.3 Forget Password Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
7.4 User Panel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

viii
7.5 Leave History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
7.6 Leave Application Form. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
7.7 Approval/Reject of HOD Panel. . . . . . . . . . . . . . . . . . . . . . . . . . 34
7.8 Leave History of User. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
7.9 Admin Panel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
7.10 Superintendent Panel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

9.1 Types of Leave . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

ix
 Keywords And Glossary

Keywords :
Transparency ,Data Integrity ,Accruals ,Simplicity , E-notifier, Notification Panel, Widget.

Glossary :
C
CIT - Computer Information Technology : use and study of computers, networks, computer
languages and databases .

D
Database - a comprehensive collection of related data organized for convenient access, gener-
ally in a computer.

E
E-notifier - Email Notification : Use email notifications to send selected users email about
specific activities in the system, such as updates to incidents or change requests.

H
HR - Human Resource : a people who make up the workforce of an organization, business
sector or economy.
HRMS - Human Resource Management System : a software application that combines many
human resources functions, including benefits administration and performance analysis.

M
MIS - Management Information System : a computerized database of financial information
organized and programmed.

S
SAIL - Steel Authority of India Limited : a public sector company and is the largest integrated
iron and steel producer in India.
Server - a computer that makes services, as access to data files, programs,and peripheral de-
vices, available to workstations on a network.
SQLite - an in-process library that implements a self-contained, serverless, zero-configuration,
transactional SQL database engine.

x
Wifi - Wireless Internet for Frequent Interface : a brand name certifying that a device or other
product is compatible with a set of broadband wireless networking standards.

Wps - Wi-Fi Protected Setup : feature found on some NETGEAR wireless routers and how
you can use it to connect devices to your wireless network.

xi
 Chapter 1

Project Overview

1.1 Introduction

Every organization is information driven and it is the staff who drives and carries out day to
day activities. This Leave Management System can be used throughout the corporate orga-
nization.The staff needs to submit their leaves manually to their respective authorities. This
increases the paperwork maintaining the records becomes tedious.Maintaining notices in the
records also increases the paperwork.This project system can be used to automate the workflow
of leave applications and their approvals in our college.It decreases the paperwork and enables
easier record maintenance . It also reduces chances of Data loss. This system have features like
notification, leave cancellation, automated leave approval and report generation based on the
requested data by the user. This system will help in reducing costs, saving time, integrating and
aligning HR efforts with the rest of organization. Staffs will be empowered and engage with
more input and control over their work life. Through HRMS one can quickly build the work-
flows and processes. The powerful flexibility features keep staffs current and compliant, even
as rules and regulations change. The Leave Management System is an Intranet based website
that can be accessed throughout a college. Since mobile phones are popular and can be used in
all walks of life, we have attempted to create an application that the students can easily access
through their smartphones. Although there are many mobile platforms available in the market
these days, Android OS is the most user-friendly and programmer friendly platform.

1.1.1 Background Introduction

In the existing paper work related to leave management, leaves are maintained using the atten-
dance register for staff.The staff needs to submit their leaves manually to their respective au-
thorities. This increases the paperwork maintaining the records becomes tedious.Maintaining
notices in the records also increases the paperwork. The main objective of the proposed sys-
tem is to decrease the paperwork and help in easier record maintenance by having a particular
centralized Database System, where Leaves and Notice s are maintained.The proposed system
automates the existing system. It decreases the paperwork and enables easier record mainte-

1
 1.2. Problem Definition

nance . It also reduces chances of Data loss.This module intelligently adapts to HR policy of
the management allows employees and their line managers to manage leaves and replacements
for better scheduling of workload.The application basically contains the given modules:Module:
1) Staff Module: It consist of two types of faculties a) Teaching b) Non-teaching 2) HOD Mod-
ule: It consists of Head of the Department/ Manager Body which takes critical decision related
to HR. 3) Administration Module:It calculates leaves maintains records.To provide for an au-
tomated leave management system that intelligently adapts to HR policy of the organization
and allows employees and their line managers to manage leaves and replacements for better
scheduling of work load processes.

1.1.2 Motivation

The leave management system is to decrease the paper work and easier record maintenance by
having a Database for leaves maintenance. The Leave Management System reduces the over
work and time duration. Thus this system maintains the excess leave balance done by college
to maintain the leaves. But in this era of leave application have to suffers lots of problems and
formalities for the approval of leave. It provide a easy, maintained and systematic environment
for the higher panel for the approval of leave.

1.2 Problem Definition

People are constantly in the fight to save their time. The leave management system is a sin-
gle leave management that keeps leave records of all the employees.This system will provide a
connection between the user and the database hence enabling quick retrieval of the information
without any intervention from the human resource manager. In this system employees can apply
for leave online he/she can see his/her balance leave.

The main objective of the system is which shows and helps you to collect most of the infor-
mation about leave details of employees. In this busy world leaves are the day which allow
people to utilize their time at home but leaves are also the days.

1.3 Current Systems

In the Current Leave Record Management System, every College/Department follows manual
procedure in which faculty enters information in a record book. At the end of each month/session,
Administration Department calculates leave/s of every member which is a time taking process
and there are chances of losing data or errors in the records. This module is a single leave man-
agement system that is critical for HR tasks and keeps the record of vital information regarding
working hours and leaves. It intelligently adapts to HR policy of the management and allows
employees and their line managers to manage leaves and replacements.

2
Chapter 1. Project Overview

1.4 The Problems with Current System

At the end of each month/session, Administration Department calculates leave/s of every mem-
ber which is a time taking process and there are chances of losing data or errors in the records.
This module is a single leave management system that is critical for HR tasks and keeps the
record of vital information regarding working hours and leaves. It intelligently adapts to HR
policy of the management and allows employees and their line managers to manage leaves and
replacements (if required).

1.4.1 Advantages Over Current System

In this module, Head of Department (HOD) will have permissions to look after data of ev-
ery faculty member of their department.HOD can approve leave through this application and
can view leave information of every individual. This application can be used in a college to
reduce processing work load.This project main idea is to develop an on line centralized appli-
cation connected to database which will maintain faculty leaves, notices information and their
replacements (if needed). Leave management application will reduce paperwork and maintain
record in a more efficient systematic way. This module will also help to calculate the num-
ber of leaves taken monthly/annually and help gather data with respect to number of hoursâTM
worked, thereby helping in calculating the work hours by the HR Department.

1.5 Goals and Objectives

Leave Management System is very convenient to implement,easy to understand and also easy
on implementation.The need of designing such Software is to provide HR Administration a
better way for scheduling balancing work load by maintaining leave details of the staff. It
reduces the human efforts of checking the papers for leave request manually and maintaining it
in folders and files and To automate the existing leave management in educational institutes.

To decrease the paperwork and enable the process with efficient,reliable record maintenance
by using centralized database, thereby reducing chances of data loss. To provide for an au-
tomated leave management system that intelligently adapts to HR policy of the organization
and allows employees and their line managers to manage leaves and replacements for better
scheduling of work load processes.

1.6 Scope and Applications

The scope of the project is limited to several processes: handling of employee leave application,
manging leave balances, record management administration and leave management and It will
generate the reports such as leave trends of the company, employee availability, employee leave

3
 1.7. Report Organization: briefly explains all the chapters and their focus

balance, leave rejection and leave acceptance The leave management system is designed in such
a way that makes it possible to access it through any web browser program.

The leave management system was designed ,developed and implemented taking the distinc-
tion of the leave of absence policies and types of leaves and the system is exclusively designed
and developed for HR Department in general and the employees leave records section in partic-
ular. The employee leave section is solely responsible for keeping the leave and related records
of employees and keeping track of their information.

1.7 Report Organization: briefly explains all the chapters

and their focus

The remaining part of the project is organized as follows.

Chapter 2: Describes the literature review of the existing papers and the description about
the system.

Chapter 3: Chapter 3 introduces the Software and Hardware Requirement of the project.

Chapter 4: Consequently, the Project Design of the project is described in the Chapter 4.

Chapter 5: Describes the Methodology of the project.

Chapter 6: Introduces the system model and basic assumption and dependencies of our work.

Chapter 7: Presents the Results and Test cases related work.

Finally, Chapter 8 concludes and describes some future work.

4
 Chapter 2

Review Of Literature

2.1 HR e-Leave Tour Management System at RDCIS, SAIL

2.1.1 Description

Looking at people as assets is part of human resource management and human capital man-
agement. For managing and automating the HR Process to maximize the productivity of the
organization, the organization has to implement HRMS, a Human Resource Management Sys-
tem. HRMS system will help in reducing costs, saving time, integrating and aligning HR efforts
with the rest of the organization. Employees will be empowered and engage with more input
and control over their work life. Through HRMS one can quickly build the workflows and pro-
cesses. The powerful flexibility features keep employees current and compliant, even as rules
and regulations change. For competent management of business process, computerization is
must in today scenario.

2.1.2 Pros

1. To provide faster employee services and online access to various information of the em-
ployees with proper security mechanism.

2. Timely accounting of maintenance activities and availability of on-line information.

2.1.3 Cons

1. In this system they have two login uses.

5
2.2. E-Notifier: Transport Information Services in Colleges and Exploring Mobile Notification

2. The whole process of the system is connected to proper mobile network.

2.1.4 How we overcome Those problem in Project

1. We create only one for all user and admin.

2. As the Internet access should be there in above system which is not possible for all so we
will try that our system should work without the Internet access[1].

2.2 E-Notifier: Transport Information Services in Colleges

and Exploring Mobile Notification

2.2.1 Description

Although there are many mobile platforms available in the market these days, Android OS is
the most user-friendly and programmer friendly platform. Android is an Operating System
supporting a large number of applications in smart phones. These applications make life more
comfortable and advanced for the users.User should know the basic knowledge of internet and
android applications.

2.2.2 Pros

This project is an efficient and user friendly Android mobile application for notifying timetables
and important notices.

2.2.3 Cons

The user of this application will be the employee itself and should have the application installed
on the smart phone/android device.

2.2.4 How we overcome Those problem in Project

This system mainly aims to minimize the difficulties that the employee face in managing and
planning their academic life.

6
Chapter 2. Review Of Literature

2.3 http://www.timeoffmanager.com

2.3.1 Description

TimeoffManager.com offers numerous important features, ranging from ease-of-use and sim-
plicity to scalability. Its ease-of-use makes it easy for anyone to use it, while its scalability lets
companies of every sizes have the peace of mind to know that all their employees’ time-off
requests are being managed efficiently.

2.3.2 Key Features

1. Highly Flexible and Configurable

2. Eliminate Errors and Employee Abuses

2.3.3 Screenshot

Figure 2.1: Time-Off Request Information

7
 2.4. http://www.planmyleave.com

Figure 2.2: General Setting

Figure 2.3: User Setting

2.4 http://www.planmyleave.com

PlanMyLeave is an easy to use and secure online leave management system that calculates
accurate leave balances in real time. It offers visibility into leave entitlements and gives a clear
picture of resource availability to managers. It is Feature rich, automatic and easy to use. It is a
leave management system with powerful functionality and settings that make it very easy to set
up and automate absence management.

2.4.1 Key Features

1. Approval Escalation and auto approve

8
Chapter 2. Review Of Literature

2. HR Information System

3. Access, usage and mobility

4. Leave approval workflow

5. Apply leave for others and View past leave approvals

6. Editing submitted / approved leave requests

7. Auto approvals and Notifications

2.4.2 Screenshot

Figure 2.4: Login Page

Figure 2.5: Search Leave Request

9
 2.5. http://adp.in

Figure 2.6: Requests

2.5 http://adp.in

The ideal leave management tool to support the workforce trends of the present and future.Align
your leave policies with ADP Vista HCMSM and protect your organization from gambits that
result in lost productivity. Automate leave grants, get consolidated reports and improve overall
employee compliance with your leave policies.

2.5.1 Key Features

1. Online Leave Transactions

2. Easy Report Generation

3. Workflow Notification

4. Customizable Leave Policies

2.6 Technological Review

2.6.1 Ajax

AJAX is an acronym for Asynchronous JavaScript and XML. It is a group of inter-related tech-
nologies like JavaScript, DOM, XML, HTML, CSS etc. AJAX is a technique for creating fast
and dynamic web pages. AJAX allows web pages to be updated asynchronously by exchanging
small amounts of data with the server behind the scenes. This means that it is possible to update
parts of a web page, without reloading the whole page.

10
Chapter 2. Review Of Literature

2.6.2 CSS

Cascading Style Sheets (CSS) is a style sheet language used for describing the presentation
of a document written in a markup language."Cascading" means that styles can fall (or cas-
cade) from one style sheet to another, enabling multiple style sheets to be used on one HTML
document. It brings a lot of long-awaited novelties, like rounded corners, shadows, gradients,
transitions or animations, as well as new layouts like multi-columns, flexible box or grid lay-
outs.

2.6.3 HTML

HyperText Markup Language(HTML) is a computer devised which allow website creation. It

is the HTML code that provides an overall framework of how the site will look. These websites
can then be viewed by anyone else connected to the Internet.HTML is used to create electronic
documents (called pages) that are displayed on the World Wide Web.

2.6.4 JavaScript

JavaScript is prototype-based with first-class functions, making it a multi-paradigm language,

supporting object-oriented, imperative, and functional programming styles.JavaScript is a pro-
gramming language that is run by most modern browsers. It supports object-oriented program-
ming and procedural programming. It can be used to control web pages on the client side of the
browser, server-side programs, and even mobile applications.

2.6.5 jQuery

jQuery is a JavaScript Library.jQuery greatly simplifies JavaScript programming.jQuery is a

fast, small, and feature-rich JavaScript library. It makes things like HTML document traversal
and manipulation, event handling, animation, and Ajax much simpler with an easy-to-use API
that works across a multitude of browsers.

2.6.6 Materialize

Materialize is a UI component library created with CSS, JavaScript, and HTML. Materialize UI
components helps in constructing attractive, consistent, and functional web pages and web apps
while adhering to modern web design principles like browser portability, device independence,
and graceful degradation. It helps in creating faster, beautiful, and responsive websites. It is
inspired from Google Material Design.

11
 2.6. Technological Review

2.6.7 MySQL

MySQL is the most popular Open Source Relational SQL database management system. MySQL
is one of the best RDBMS being used for developing web-based software applications. MySQL
is a very powerful program in its own right. It handles a large subset of the functionality of
the most expensive and powerful database packages. MySQL is very friendly to PHP, the most
appreciated language for web development.

2.6.8 PHP

The PHP Hypertext Preprocessor (PHP) is a programming language that allows web developers
to create dynamic content that interacts with databases. PHP is basically used for developing
web based software applications. PHP is a server side scripting language that is embedded in
HTML. It is used to manage dynamic content, databases, session tracking, even build entire
e-commerce sites. It is integrated with a number of popular databases, including MySQL,
PostgreSQL, Oracle, Sybase, Informix, and Microsoft SQL Server.

12
 Chapter 3

Requirement Analysis

3.1 Platform Requirement :

3.1.1 Supportive Operating Systems :

The supported Operating Systems for client include:

- Linux Operating System (Ubuntu Server OS 14.04) our.

Linux is the operating system that will support comparative website. since Linux is an open
source operating system. The project we implemented is developed n Linux platform. The
comparative website is tested on the same Linux OS.

Ubuntu 14.10 is used as server operating system. Apache 2.4 is used as Web server and for
database server Mysql server is used.

3.2 Software Requirement :

The Software Requirements in this project include:

- XAMPP

- Web Brower : Internet Explorer, Mozilla Firefox, Google Chrome etc.

XAMPP stands for Cross-Platform (X), Apache (A), MariaDB (M), PHP (P) and Perl (P). It is
a simple, lightweight Apache distribution that makes it extremely easy for developers to create

13
 3.3. Hardware Requirement :

a local web server for testing and deployment purposes. XAMPP is a free and open source
cross-platform web server solution stack package developed by Apache Friends.

Figure 3.1: XAMPP

A web browser is a software application for retrieving, presenting and traversing information
resources on the World Wide Web. An information resource is identified by a Uniform Resource
Identifier that may be a web page, image, video or other piece of content. Hyperlinks present in
resources enable users easily to navigate their browsers to related resources.The most popular
web browsers are Google Chrome, Microsoft Edge (preceded by Internet Explorer), Safari,
Opera and Firefox.

Figure 3.2: Web Server

3.3 Hardware Requirement :

3.3.0.1 Hardware Requirements For Deployment

- Processor : Intel Pentium Family and above

- RAM : above 712 MB

- Hard Disk : 1.5 GB and above

14
 Chapter 4

System Design and Architecture

4.1 System Architecture

In our System there will be employee who is working in organisation to hold those employee
there will be particular HOD of a particular department. Director is assign to check the leave
record of a particular department. Admin has all records of all employees. Employee will first
apply for a leave then leave form will sanctioned from a particular department HOD.Then it
will submitted to a department register,Then further submitted to the Admin leave register they
enter into staff attendance register,They will upload it into E-Time software.

Figure 4.1: System Architecture For Leave Management System

15
 4.2. Usecase Diagram

4.2 Usecase Diagram

In our System there will be employee who is working in organisation to hold those employee
there will be particular HOD of a particular department. Director is assign to check the leave
record of a particular department. Admin has all records of all employees. Employee will first
apply for a leave then leave form will sanctioned from a particular department HOD.Then it
will submitted to a department register,Then further submitted to the Admin leave register they
enter into staff attendance register,They will upload it into E-Time software.

Figure 4.2: Usecase diagram For Leave Management System

4.3 Class Diagram

In class diagram of our system there where different panels such as department,working staff,etc.They
have there leave register carried by admin panel for records of all employees and there request
where sanctioned or rejected by there particular department HOD or Director sir.

16
Chapter 4. System Design and Architecture

Figure 4.3: Class Diagram For Leave Management System

4.4 Data Flow Diagrams

4.4.0.1 Level 0 of Leave Management System

In Level 0 of Leave Management System there will one employee panel who will apply for a
leave.There is one admin panel who will validate the request and gives the notification to the
employee.HOD will accept or reject the request of employee.

17
 4.5. Component Diagram

Figure 4.4: Level 0 Data Flow Diagram

4.4.0.2 Level 1 of Leave Management System

In Level 1 of Leave Management System in employee panel he/she will login for leave applica-
tion then they will check the type of leave fills the form and then update the documents.In HOD
panel he will grant the permission whether the application is accepted or rejected he will check
the request and then take the decision.In Admin panel they will be able to check the details of
all the employees he also has the power of accepting or rejecting the request after that they will
upload the records and provide the notification to the employee.

Figure 4.5: Level 1 Data Flow Diagram

4.5 Component Diagram

The Component diagram consists of Employee, HOD, Director Sir, Superintendent and Ad-
min.The employee will send his leave request to hod if hod accepted then further updated by

18
Chapter 4. System Design and Architecture

admin and else rejected then reverse send to employee.The hod and office superintendent will
send there request to director sir and same process will carried on.Admin Staff will send there
request office superintendent and follow as above and all the data is store in database server.

Figure 4.6: Component diagram For Leave Management System

19
 Chapter 5

Methodology

5.1 Modular Description

The methodology will be prototype model of system development life cycle which iterative and
will involve the following stages of system analysis, system design, implementation/development,
testing and validation. In the analysis phase, existing system will be evaluated.

Problems with the current system will be identified. This will be done by interviewing users of
the system and consulting with human resource. The new system requirements are defined. In
particular, the deficiencies in the existing system must be addressed with specific proposals for
improvement.

The proposed system will be designed with the help of DFDâTM s and ERDâTM s in order to
identify the relationship between the different entities in the system. The new system will be
implemented using tools such as flow charts, data flow diagrams, and design manipulation lan-
guages such as PHP to design the user interface and enable connection to the database and SQL
to design the relational tables in the database.

When the new system is up it will be tested and validated in order to find out whether it is
doing what it was meant for. Maintenance will be kept up rigorously at all times. Users of the
system will be kept up-to-date concerning the latest modifications and procedures

5.1.1 Admin Interface Module

In this module depending upon on going and future activities of college admin can update the
calender, they can add the new employee and delete old employees. Admin can also view the
request of staff members and on the basis of eligibility. They can reject or forward the request
to the higher authority for the approval.

20
Chapter 5. Methodology

Figure 5.1: Application Interface Module

5.1.2 Leave Admin Module

In this module admin can add the type of leaves like different institutions have there own leave
types and policies. They can also modify leave. Admin update the data of employee after
approval of request.

Figure 5.2: Leave Admin Module

5.1.3 User Interface Module

In this module employee can apply for a leave. They can also attach the supported documents[In
case of Medical Leave]. They can also view the balance leaves and history of leaves. After
sending of application employee can also see the status of their application. User will also see
the calender in the institution department holidays will be highlighted.

21
 5.2. Sequence Diagrams

Figure 5.3: User Interface Module

5.2 Sequence Diagrams

The sequence diagram consists of Employee,HOD,Director Sir,Office Superintendent and Ad-

min.The employee will send his leave request to hod if hod accepted then further updated by
admin and else rejected then reverse send to employee.The hod and office superintendent will
send there request to director sir and same process will carried on.Admin Staff will send there
request office superintendent and follow as above.

Figure 5.4: Sequence Diagram for Leave Management System

22
Chapter 5. Methodology

5.3 Activity Diagram

5.3.1 Activity For Employee of Leave Management System

In our system there will be employee who is working in an organization.If he/she wants to apply
for a leave first he/she will login then punch-in after that they will view the leaves.Then after
checking the leaves they will apply for a leave further they punch-out then logout of the system.

Figure 5.5: Activity Diagram for Employee

5.3.1.1 Activity For Admin of Leave Management System

In our system there will be employee who is working in an organization.If he/she wants to apply
for a leave first he/she will login then View the leave after that they punches-in then they will
create the leave.They will now add the employee,generates the report then punch-out.After this
Sanctioned/Rejection will take place then atlast they will log-out.

23
 5.3. Activity Diagram

Figure 5.6: Activity Diagram System for Admin

5.3.1.2 Activity For HOD of Leave Management System

In our system there will be employee who is working in an organization.If he/she wants to apply
for a leave first he/she will login then punch-in after that they will view the leaves then they will
view the status generate the report then they will punch-out.After the above steps the request
will either accepted or rejected then apply leave then they logout.

24
Chapter 5. Methodology

Figure 5.7: Activity Diagram for HOD

5.4 Flow-Chart

This flow chart shows the proper function on leave taken by the employees of our college for
all teaching and non-teaching staff with approval of there heads and then updated by the admin
department.

STEPS:

1. Here first Employee will Register there details.

2. After that login and can apply for leave.

3. His request will be send to the HOD.

4. HOD will approved/reject and then further send it to admin for updation.

5. After complition of all the above steps employee will recieve the message on his mobile.

25
 5.4. Flow-Chart

Figure 5.8: Flow Chart For Leave Management System.

26
 Chapter 6

Implementation Details

6.1 Assumptions And Dependencies

6.1.1 Assumptions

The following Assumption was taken into consideration:

- Assume that all the information entered by the user will be correct. If any wrong infor-
mation found then system will notify an alert. The system is required to save generated
reports.

6.1.2 Dependencies

- Applying for leave registration is compulsory without registration user cannot apply for
the leave.Every user can only login by there Unique Id.

6.2 Implementation Methodologies

Based on the availability of leave, employee can apply for leave online. Casual leave ,Privilege
leave ,Sick leave ,Compensatory off. Same process followed by the staff of School Of Phar-
macy and Architecture as well.All teaching and non-teaching staff can apply for requisitions
with their held department and even they can see total request in there panel and also they can
see the status of their request.

In Our School Of Engineering, it has five departments such as:

27
 6.2. Implementation Methodologies

1. Computer Engineering

2. Mechanical Engineering

3. Civil Engineering

4. Electrical Engineering

5. Electronic And Telecommunication Engineering.

For User:

Every department has its own HOD. For example, If Computer department staff wants to apply
for the leave then it will accepted or rejected by only there department HOD and then further
updation process carried by admin.
If leave accepted SMS for User will be delivered to the user.

Figure 6.1: Flow Chart Of User.

28
Chapter 6. Implementation Details

For Admin:

In case of admin they can also apply for leave and there leave can be accepted or rejected
by there office Superintendent. Superintendent can also apply for leave and his leave approval
or disapproval done by the Director sir.If leave accepted SMS will be delivered to the user.

Figure 6.2: Flow Chart Of Admin.

For HOD:

This module is having the power of leave verification of the students or employees. HOD is
able to see the leave record of employees. HOD can verify the leave on the basis of the leave
availability of the employee
After the leave verification leave is transferred to the principal for the approval. HOD is having
authority of approval or disapproval of leave and remark on that. .HOD leave will be accepted
or rejected by the Director sir. If leave accepted SMS will be delivered to the user.

29
 6.2. Implementation Methodologies

Figure 6.3: Flow Chart Of HOD.

30
 Chapter 7

Results and Analysis

7.1 Test cases and Result

Registration Page Test: Registration tested successfully.

Log-in Page Test: User log-in by there Unique Id is successful.
User Panel Test: Working is successful with no errors.
HOD Panel Test: Working is successful with no errors.
Superintendent Panel Test: Working is successful with no errors.
Director Panel Test: Working is successful with no errors.
Log-out Page Test: Working is successful with no errors.

7.2 Analytical Discussion

In the below figure,it is main page/home page. In that we have two option available one will
take to log-in page and other to registration page. In registration page,user can Register with
there corresponding details.

Figure 7.1: Home Page

31
 7.2. Analytical Discussion

In the below figure user can log-in with there unique Id and password and redirect to the user
panel.

Figure 7.2: Login Page.

We have a password recovery option... If someone forget the password then you have to click
in forget password link given in the log-in page...when user click on that link, it will ask you a
question that u had answered during registration, write the correct answer and click, then change
password option will come and there you can change your password and confirm it and submit
it!!

Figure 7.3: Forget Password Page.

In the below figure user can see total types of leave and also can see the total number for leaves
of every type as well as how many leave taken from the total leave in the panel.In the above
figure user can see all leave history about the leave such as type of leave,number of days,date
when leave taken etc.

32
Chapter 7. Results and Analysis

Figure 7.4: User Panel.

Figure 7.5: Leave History

This is the leave form where user details where already fetched from the registration form where
unique id plays an important role and the leave details have to provide with themself as there
requirement.

33
 7.2. Analytical Discussion

Figure 7.6: Leave Application Form.

This is the HOD Panel where he can see all staff request in the form of card wheather to accept
to reject the request of user depends on HOD and see all the user having which leave taken on
which date and number of dates.

Figure 7.7: Approval/Reject of HOD Panel.

34
Chapter 7. Results and Analysis

Figure 7.8: Leave History of User.

The below figure is of admin panel where if higher authorities accepted the request then it will
further proceed to the admin panel for the updation of the request.

Figure 7.9: Admin Panel.

The Superintendent Panel where he can see all admin staff request in the form of card wheather
to accept to reject the request of staff depends on leave and see all the user having which leave
taken on which date and number of dates.

Figure 7.10: Superintendent Panel.

35
 Chapter 8

Conclusion and Future Scope

8.1 Conclusion

• Leave Management System is very useful for college to maintain the leave records of the
staff and it also maintains the leave applications of the staff.

• This system is to decrease the paper work and easier record maintenance by having a
particular website for leaves maintenance.

• This approach basically deals with the record of leaves taken by faculty members in the
organization and the higher authorities may accept or reject the leave applications re-
quested by the staff.

• This system also approach to reduce the formalities and time delay facing by faculty
members for the approval of leave.

• Further upgradation of the Leave Management System for various type of organisation
with multiple hierarchies can help in reducing paperwork and help achieve error free
tabulation of leaves.

8.2 Limitations

• The leave status cannot be cleared until and unless the HOD approves/ rejects the appli-
cation and the staff cannot cancel the leave application once made.

• The system will not function properly with multiple computers in the network and the
system will fail if the server fails, but the data will remain stored in the database.

36
Chapter 8. Conclusion and Future Scope

8.3 Future Enhancement

• The leaves that have not been availed by the staff in the given session can be automat-
ically carried forward to the next working session depending on the HR policy of the
organisation.

• Every employees individual leave record can be tabulated in a pie chart format to ascertain
his/her performance during the working session for HR approval activity.

• The summarised data generated by this system can be further provided to different de-
partments, for example, Finance, Accounts for direct calculation of salaries.

• If personal data is fed into the system while creating employee profiles, a single interface
to ascertain information such as no. of years worked,birthdays, notice period, promotions,
can be availed at a single point by the HOD.

37
 References

[1] S Selvi, Manas Rath, N K Sinha, S P Singh, N N J Hemrom, A Bhattacharya, A K Biswal

HR e-Leave Tour Management System at RDCIS, SAIL International Conference on Information
Technology, June-2014 .

[2] Pandore Yogesh Bandopant E-Notifier: Transport Information Services in Colleges and Ex-
ploring Mobile Notification International Journal of Advanced Research in Computer and Com-
munication Engineering Vol. 5, Issue 4, April 2016.

[3] Rehman S.U Smart agent for automated E-commerce UK IEEE pp.124-128, 7-10 7-10
Nov.2011, School of information System, Computer. Math, Brunel Univ, Uxbridge.

[4] Richard Barker, Tasks and Deliverables, Addison Wesley.

[5] Bell, Charles, Expert MySQL, Apress, 2012.

[6] http://www.timeoffmanager.com.

[7] http://www.planmyleave.com.

[8] http://adp.in.

38
 Chapter 9

Appendix A

9.1 Earned Leave or Privilege Leave:

The type of leave which the employees earn as they work for an organisation for a specified
number of days.The privilege leave is sanctioned to the employees without any salary deduc-
tions. This type of leave requires prior approval from the employer except in cases of emer-
gency.

9.2 Casual Leave:

The type of leave that is granted for short durations and can ordinarily be taken with prior
information to the employer except in cases when informing the employer is not possible.As a
rule, official holidays are not counted when calculating the number of casual leaves if they fall
during the period of casual leave.

9.3 Sick Leave or Medical Leave:

An employee can call in sick if he is not in a state to come to office for work. Usually, an
employee is entitled to sick leave only after a stipulated period of employment in an organiza-
tion. The number of sick leaves permissible may vary from organization to organization and
as a matter of fact, no prior intimation is required for availing this type of leave. A medical
certificate from a registered medical practitioner may be required to testify the sickness if the
sick leave is being extended for a long period of time.

39
 9.4. Maternity Leave:

9.4 Maternity Leave:

This provision is especially available for those women employees who plan to have a baby. The
duration of paid maternity leave is 26 months and this can be further extended with 16 months
of unpaid leave. No deductions can be made from the leave account of the female employee.
This type of leave can also be taken in case of miscarriage or abortion but the leave limit in such
cases is shorter.

9.5 Study Leave or Sabbatical Leave:

An employee may be granted a study or sabbatical leave to enable him to update his knowledge
and experience in a way that he will be of greater use to the Institute after re-joining.

Figure 9.1: Types of Leave

Apart from the various leaves mentioned above, certain sectors and industries also have provi-
sions for commuted leave, leave not due, paternity leave, extraordinary leave, childcare leave,
hospital leave, special disability leave and child adoption leave.

40
 ACKNOWLEDGMENT

We would like to take the opportunity to express our sincere thanks to our guide Mukhtar
Ansari, Assistant Professor, Department of Computer Engineering, AIKTC, School of Engi-
neering, Panvel for his invaluable support and guidance throughout our project research work.
Without his kind guidance support this was not possible.

We are grateful to him for his timely feedback which helped us track and schedule the process
effectively.His time, ideas and encouragement that he gave helped us to complete our project
efficiently.

We would also like to thank Dr. Abdul Razak Honnutagi, AIKTC, Panvel, for his encourage-
ment and for providing an outstanding academic environment, also for providing the adequate
facilities.

We are thankful to Prof. Tabrez Khan, HOD, Department of Computer Engineering, AIKTC,
School of Engineering, Panvel and all my B.E. teachers for providing advice and valuable guid-
ance.

We also extend our sincere thanks to all the faculty members and the non-teaching staff and
friends for their cooperation.

Last but not the least, We are thankful to all our family members whose constant support and
encouragement in every aspect helped me to complete my project.

Shaikh Naseema Khudbuddin Halima

Roll No. 13CO13

Mirza Bushra Riyazuddin Shenaz

Roll No. 12CO04

Yadav Pooja Ramavtar Balashree

Roll No. 12CO06
(Department of Computer Engineering)
University of Mumbai.

41
 9.5. Study Leave or Sabbatical Leave:

42
Chapter 9. Appendix A

43