LEAVE MANAGEMENT

SYSTEM
BY AYUSH UPADHYAY,
PRASAD YEOLE
GUIDANCE BY – SEEMA PURANDARE,
ASHWINI WAGHMARE
(BBA-CA, SEM-6)

Modern Education Society’s

NESS WADIA COLLEGE OF COMMERCE

( BBA (CA) Department )

19, Late Prin. V.K Joag Path, Pune - 411001
Tel. 020261670
Fax. No : 26167024
SAVITRIBAI PHULE, PUNE UNIVERCITY,2020-2021
No Title Page No
.

1. Introduction

1.1 Problem Definition

1.2 Need for the New System
1.3
Project Scope

2 Analysis
2.1 Feasibility Study
 Technical Feasibility
 Economical Feasibility
 Operational Feasibility
2.2 Hardware and Software Requirements
3 Design
3.1 ER Diagram
3.2 Database Design / Data Dictionary
3.3 UML Diagram
4 Screenshots
5 Limitations
6 Future Enhancement
7 References and Bibliography

INTRODUCTION
In modern business practice there are many kinds of leave available to
employees; sick, annual, unpaid and compassionate. Tied together with the
different leave structures of companies and the requirements to request and
grant leave we can often allocate too much time and resources to manage it.
With business practise in Durban having to catch up with the fast pace of
Johannesburg and Cape Town, minimal time should be spent on managing
leave. A leave management system, also known as LMS, is a platform that
enables a company to easily and correctly allocate, track and grant leave as well
as allow for employees to request and track their own leave. This is beneficial to
Durban on a whole to allow for more time to streamline all other business
aspects.

Today’s leave management system is more often found in the form of a web
based application due to its easy accessibility and ability to run on almost any
device and operating system that has a web browser. Leave management
systems make it easy for an employee to request leave from their own desk or
even from home if sick. The employee can also attach a doctor’s certificate to
the requested leave application if required.

1.1 Problem Definition :-

Yes, it is true that manual and analog techniques of managing your HR can
include a lot of paper usage. Further, SMEs and other large scale enterprises do
make use of spreadsheets and a lot of papers in order to store employee
documentations. This however, includes a lot of tedious manual efforts which
tend to deteriorate the quality of analysis. Therefore, accurately tracking and
analyzing employee leaves and absenteeism can be a rather tough challenge.
This is when automation comes handy.
1. It helps in streamlining leave procedures.
2. Employee leave information are managed centrally.
3. And consequently, applications and approvals are controlled effectively
online, thereby reducing its dependency on paperwork.

1.2 Need for the New System :-

In order to understand, analyze, interpret and make a decision, the existence of

data is crucial. Further, organizations can accumulate this data manually or with
the help of automated software systems. Making use of these leave management
systems can be one of the best decisions the HR department of an organization
can make. Not only would it be accurate in collecting information but would
play a significant role in effective analysis which would directly enhance the
decision-making efficiency. Moreover, understanding leave patterns could help
resolve queries and problems such as:
1. Reason for absenteeism
2. Perceptual mapping of employees regarding the job they have
The leave management system can be made a lot easier and helpful by
automating the entire thing. Automated and leave management system
online have a set of features that can help accurate interpretations. A few such
features are as follows:
1. Instant leave updates on the system dashboards
2. Moreover, managing leave policies
3. Reduce the usage of papers for leave requests and approvals
4. Further, maintain a holiday calendar for multiple centers across the globe
5. Generate comprehensive reports on employee leave behavior and patterns
6. Plan resources immediately by knowing who have applied for leaves on
specific days.
7. Increase the efficiency and productivity of your teams by avoiding the time
spent for sending email leave applications and approvals.
In other words, the future or scope of effective and efficient employee leave
management lies in the adoption of leave management systems that allow HR
Managers to go ahead with the most suitable decision to a specific problem
statement. Further, it is also important to understand that you can only
improvise those that you can measure and quantify. Therefore, being able to
correctly measure the employee leave patterns and perceptions can help you
work towards making a positive improvement.
.
1.3 Project Scope :-

The primary objective of the proposed Leave Management System is to ensure

the administration of standard leave policies, centralize the collection and
maintenance of leave records, and automate as much of the process as possible.
This system allows creating, monitoring, and routing of the leave applications
from the applicants to the acting supervisors in the department and to the
administrator of the Human Resources Department. The Leave Management
System enables employees with capabilities to submit leave requests online,
check their leave-time balances and view the status of the leave requests via the
World Wide Web (Web), relieving the Human Resources Department from
time-consuming inquiries. The automated leave management ensures that
employees accrue the right amount of "leave" that they are entitled to receive,
and provides a quick and efficient validation method that saves precious time
and eliminates a cumbersome paper process. Also, enabling the supervisor to
approve online requests saves management time. The Leave Management
System calculates and maintains balances of each employee’s vacation, sick and
other benefit time. It gives Human Resource administrators the ability to
review, edit, and approve employee time and leave from any location by using a
standard Web browser.
Thus, the Leave Management System simplifies the leave process, makes it
more maintainable, gives better, clearer and more frequent information to end
users, standardizes the processing of different types of leaves, and lowers the
amount of data entry and verification activities.

ANALYSIS
2.1 Feasibility Study :-

After doing the project Leave Management System,study and

analyzing all the existing or required functionalities of the system, the next
task is to do the feasibility study for the project. All the projects are feasible
– given unlimited resourses and infinite time.
Feasibility study includes consideration of all the possible ways to
provide a solution to the given problem. The proposed solution should
satisfy all the user requirements and should be flexible enough so that future
chnages can be easily done based on the future upcoming requirements.

 Technical Feasibility :- This included the study of function, performance

and constraints that may affect the ability to achieve an acceptable system. For
this feasibility study, we studied complete functionality to be provided in the
system, as described in the System Requirement Specification (SRS) and
checked if everything was possible using different type of frontend and backend
platform.
 Economical Feasibility :- This is a very important to be considered
while developing a project. We decided the technology based on minimum
possible cost factor.
o All hardware and software cost has to be born by the
organization.
o Overall we have estimated that the benefits the
organization is going to receive from the proposed
system will surely overcome the initial costs and the
later on running cost for the system.

 Operational Feasibility :- No doubt the proposed system is fully GUI

based that is very user friendly and all inputs to be taken all self-
explanatory even to a layman. Besides, a proper training has been
conducted to let know the essence of the system to the users so that
they feel comfortable with new system. As far our study is concerned
the clients are comfortable and happy as the new system has cut down
their loads and doing.
2.2 Hardware and Software Requirements

Hardware Requirements :-

Name of Component Specification

Processor Intel(R) core(TM) i3-5005U CPU @ 2.00GHz 2.00GHz
HDD 40GB or above
RAM 512GB or above
Keyboard 122 keys

Software Requirements :-

Name of Component Specification

Operating System Windows XP, Windows 10, Linux
Database PHP
Browser Any of Mozilla, Opera, Chrome, etc.
Document MS Word, Excel
Front End HTML, CSS, JavaScript

DESIGN
 This phase of the system development life cycle refines hardware and
software specifications establishes programming plans, trains users and
implements extensive testing procedures, to evaluate design and operating
specifications and/or provide the basis for further modification.

3.1 ER Diagram :-
E-R Model is a popular high level conceptual data model. This model and
its variations are frequently used for the conceptual design of database
application and many database design tools employ its concept
 Attributes
 Relations

o Many-to-many
o Many-to-one
o One-to-many

 Weak entities
 Sub-type and super-type
The entities and their relationships between them are
shown using the following conventions
 An entity is shown in rectangle.
 A diamond represent the relationship among number
of entities.

 The attributes shown as ovals are connected to the

entities or relationship by lines.

 Diamond,oval and relationships are labeled.

 Model is an abstraction process that hides super

details while highlighting details relation to
application at end.
 A data model is a mechanism that provides this
abstraction for database application.

 Data modeling is used for representing entities and

their relationship in the database.

 Entities are the basic units used in modeling database

entities can have concrete existence or constitute
ideas or concepts.

 Entity type or entity set is a group of similar objects

concern to an organization for which it maintain
data.

 Properties are characteristics of an entity also called

as attributes.

 A key is a single attribute or combination of 2 or

more attributes of an entity set is used to identify one
or more instances of the set.
3.2 Database Design :-
Database design is the organization of data according to a database model.
The designer determines what data must be stored and how the data elements
interrelate. ... Database design involves classifying data and identifying
interrelationships. This theoretical representation of the data is called an
ontology.
ADMIN TABLE :

FIELD NAME DATA SIZE CONSTRAINTS

TYPE

ID Varchar 20 Primary Key

USERNAME Varchar 20 Not Null

PASSWORD Varchar 20 Not Null

UPDATION Date 20 Not Null

DATE

DEPARTMENT TABLE :

FIELD NAME DATA SIZE CONSTRAINTS

TYPE

ID VARCHAR 20 Primary Key

DEPARTMEN VARCHAR 20 Not Null

T
NAME

DEPARTMEN VARCHAR 20 Not Null

T SHORT
NAME

CREATION 20 Not Null

DATE
DATE
EMPLOYEE TABLE :

FIELD NAME DATA TYPE SIZE CONSTRAINTS

EMP_ID VARCHAR 10 PRIMARY KEY

FIRST NAME VARCHAR 20 NOT NULL

LAST NAME VARCHAR 20 NOT NULL

EMAIL ID 20 NOT NULL

VARCHAR

PASSWORD NOT NULL

VARCHAR 20

GENDER 20 NOT NULL

VARCHAR

DOB DATE 20 NOT NULL

DEPARTMENT VARCHAR 20 NOT NULL

ADDRESS VARCHAR 20 NOT NULL

AV_LEAVE 20 NOT NULL

INT
PHONE 20 NOT NULL
NUMBER
INT

STATUS VARCHAR 20 NOT NULL

REG DATE DATE 20 NOT NULL

ROLE VARCHAR 20 NOT NULL

LOCATION VARCHAR 20 NOT NULL

LEAVE TYPE TABLE :

FIELD DATE TYPE SIZE CONSTRAINTS
NAME

ID VARCHAR 20 PRIMARY KEY

LEAVE TYPE VARCHAR 10 NOT NULL

DESCRIPTION VARCHAR 10 NOT NULL

FROM_DATE DATE 10 NOT NULL

TO_DATE DATE 10 NOT NULL

CREATION DATE 10 NOT NULL

DATE
3.3 UML Diagram
UML is an acronym that stands for Unified Modelling Language.
Simply put, UML is a modern approach to modelling and documenting
software. In fact, it’s one of the most popular business process modelling
techniques.

It is based on diagrammatic representations of software components. As the

old proverb says:“a picture is worth a thousand words”. By using visual
representations, we are able to better understand possible flaws or errors in
software or business processes.

UML was created as a result of the chaos revolving around software

development and documentation. In the 1990s, there were several different
ways to represent and document software systems. The need arose for a more
unified way to visually represent those systems and as a result, in 1994-1996,
the UML was developed by three software engineers working at Rational
Software. It was later adopted as the standard in 1997 and has remained the
standard ever since, receiving only a few updates.
 Start
Login to the Leave
Management System

Check Check Check Check

Check
Permis Permis Permiss Permis
Permiss
sion sion ion sion
ion

Manage Manage Approve Manage Cancel Manage

Manage Leaves Leaves Company
Notification Leaves

Logout From the System

End

Activity Diagram for Leave Management System

 SCREENSHOTS

Screenshots of Leave Management system :-

 LIMITATIONS

Although I have put my best efforts to make the software flexible, easy to
operate but limitations can not be ruled out even by me. Though the software
presents a broad range of options to its users some intricate options could not be
covered into it; partly because of logistics and partly because of sophistication.
Paucity of time was also major constraint, thus it was not possible to make the
software fool proof and dynamic. Lack of time also compelled me to ignore
some part such as storing old entries of the user etc.
Considerable efforts have made the software easy to operate even for
the people not related to the field of computers but it is acknowledged that a
layman may find it a bit problematic at the first instance. The user is provided
help at each step for his convenience in working with the software.

List of Limitations which is available in the Leave Management System

 Security is one of the biggest concerns. Systems must be designed to

prevent unauthorized access to sensitive and confidential data, as well as
inadvertent disclosure. This generally required many “departments” and access
authorizations, all of which had to be monitored and maintained.

 For a limited number of employees, the installation process is quite short.

However, if the number is huge, the cost of hiring an IT specialist to manage the
system is likely..

 Small businesses tend to move away from the status quo and expand over
time. For example, they first chose a simple vacation management system for
their limited number of employees. As they grow, the system should be able to
evolve with them. It is not logical for companies to change systems every time
they increase their workforce.
 FUTURE ENHANCEMENT

In a nutshell, it can be summarized that the future scope of the

project circles around maintaining information regarding :-

 We can add printer in future.

 We can give more advance Software for Online Ticket Booking of
Amusement Park including more facilities.
 We will host the platform on online servers to make it accessible
worldwide.
 Integrate multiple load balancers to disturb the loads of the System.
 Create the master and slave database structure to reduce the overload of
the database queries

The above mentioned points are the enhancements which can be

done to increase the applicability and usage of this project. Here we can
maintain the records of Ticket Booking and Category. Also as it can be
seen that now-a-days the players are versatile, i.e. so there is a scope for
introducing a method to maintain the Online Ticket Booking System.
Enhancements can be done to maintain all the Ticket Bookings, History,
Customer, Order, Confirm Order.
We have left all the options open so that if there’s any other future
requirement in the system by the user for the enhancement of the system then it
is possible to implement them. In thelast we would like to thanks all the persons
involved in the development of the System directly or indirectly. We hope that
the project will serve its purpose for which it is develop there by understanding
success of process.
 REFERENCES & BIBLIOGRAPHY

 Google for problem solving

 https://www.tutorialspoint.com
 https://www.youtube.com
 https://developer.mozilla.org/en-US/docs/Web/CSS/Reference
 https://www.w3schools.com/php/
 http://www.wikipedia.org