VISVESVARAYA TECHNOLOGICAL UNIVERSITY

"Jnana Sangama", Belagavi - 590 018, Karnataka

A Database Management Systems Mini Project report on

“EMPLOYEE LEAVE MANAGEMENT SYSTEM”

Submitted in partial fulfillment of the requirement for the award of Degree of
Bachelor of Engineering
In
Computer Science & Engineering

Submitted by
MAHESH Y 1AY20CS076
PRADEEP P 1AY20CS106

Under the guidance of

Mrs. Rajani
Assistant Professor
Dept. of CSE

DEPARTMENT OF COMPUTER SCIENCE & ENGINEERING

ACHARYA INSTITUTE OF TECHNOLOGY
(AFFILIATED TO VISVESVARAYA TECHNOLOGICAL UNIVERSITY, BELAGAVI.APPROVED BY AICTE, NEW DELHI, ACCREDITED
BY NAAC, NEW DELHI )
Acharya Dr. Sarvepalli Radhakrishnan Road, Soldevanahalli, Bengaluru-560107

2022-23
 DEPARTMENT OF COMPUTER SCIENCE & ENGINEERING
ACHARYA INSTITUTE OF TECHNOLOGY
(AFFILIATED TO VISVESVARAYA TECHNOLOGICAL UNIVERSITY, BELAGAVI.APPROVED BY AICTE, NEW DELHI, ACCREDITED
BY NAAC, NEW DELHI)
Acharya Dr. Sarvepalli Radhakrishnan Road, Soldevanahalli, Bengaluru-560107

CERTIFICATE

Certified that the Database Management Systems mini project entitled

“ EMPLOYEE LEAVE MANAGEMENT SYSTEM” is a bonafide work carried
out by MAHESH Y (USN-1AY20CS076) & PRADEEP P (USN-1AY20CS106) of
5th semester in partial fulfillment for the award of degree of Bachelor of Engineering
in Computer Science & Engineering of the Visvesvaraya Technological
University, Belagavi, during the year 2022-2023. It is certified that all corrections/
suggestions indicated for internal assessments have been incorporated in the Report
deposited in the departmental library. The Mini Project reporthas been approved as
it satisfies the academic requirements in respect of Mini Project work prescribed for
the Bachelor of Engineering Degree.

Signature of Guide Signature of H.O.D

Mrs. Rajani Dr.Ajith Pandyana

Assistant Professor Associate Professor & Head
Dept. of CSE Dept. of CSE

Name of the Examiners Signature with date

1.

2.
 ACKNOWLEDGEMENT

We express our gratitude to our institution and management for providing us with
good infrastructure, laboratory, facilities and inspiring staff whose gratitude was of immense
help in completion of this mini project successfully.

We express our sincere gratitude to Dr. Rajath Hegde M M, Principal, Acharya

Institute of Technology for providing required environment and valuable support for
developing this mini project.

Our sincere thanks to Dr. Ajith Padyana, Associate Professor & Head , Department
of Computer Science and Engineering, Acharya Institute of Technology for his valuable
support and for rendering us resources for this mini project work.

We express our gratitude to Mrs. Rajani , Assistant Professor, Department of

Computer Science and Engineering, Acharya Institute of Technology who guided us with
valuable suggestions in completing this mini-project at every stage.

Our gratitude should be rendered to many people who helped us in all possible ways.

.
MAHESH Y
(USN-
1AY20CS076)

PRADEEP P
(USN-
1AY20CS106)
 (i)
ABSTRACT

The Employee Leave Management Systems project focuses on integrating various processes
and resolving the two problems encountered in personnel management. This project
addresses the need to automate and simplify employee data, leave applications, and
manage leave benefits. Employees should plan their long holidays in advance, have a
systematic system for managing the holidays and manage work conditions in advance. It
shows a strong work ethic and aids the work process. This is a way to help your employees
reach their full potential and achieve your company goals. As a result, the automated
workplace management system is fast and error-free, requires less paperwork, and is easier
to manage. The system is built using software engineering method to provide automated
system. Both the organization and its employees benefit from an effective leave
management system. It makes it possible to plan early unemployment. Employees can
request leave, view past leave history, the employer may review and approve leave
applications and track current leave for this project
 (ii)

TABLE OF CONTENTS
Acknowledgement (i)
Abstract (ii)
Table of contents (iii)
Table of Figure (iv)
CHAPTERS PAGE NO
1: INTRODUCTION......................................................................................................1-6
1.1 Introduction to DBMS
1.1.1 Why DBMS?
1.1.2 Database applications
1.1.3 Advantages of DBMS
1.1.4 Components of DBMS
1.1.5 Three-Schema architecture
1.1.6 Study Of The System
2: SYSTEM REQUIREMENTS...................................................................................07
2.1 Hardware Requirements
2.2 Software Requirements
2.3 Functional Requirements
2.4 Non-Functional Requirements
3: DESIGN......................................................................................................................08-14
3.1 System Design
3.1.1 Introduction
3.1.2 Use case Diagram of Admin
3.1.3 Use case Diagram of Employee
3.2 ER Diagram
3.3 Schema Diagram
4: IMPLEMENTATION................................................................................................15-20
4.1 Tables
4.1.1 Admin Table
 4.1.2 Department Table
4.1.3 Employees Table
4.1.4 Leaves Table
4.1.5 Leave Types Table

4.2 Triggers and routines

4.2.1 Triggers
4.2.2 Routines
4.3 Sql Queries

5: SNAPSHOTS..............................................................................................................21-24

CONCLUSION & FUTURE ENHANCEMENT......................................................... 25-27

BIBLIOGRAPHY................................................................................................................ 28

(iii)
 TABLE OF FIGURES

1.1 Components of Database Management System 3

1.2 Architecture of database system 4
3.1 Use case Diagram and Flow charts 09-12
3.2 Entity Relationship Diagram 13
3.3 Schema Diagram 14
5.1 Snapshot of Employee Login page 24
5.2 Snapshot of Admin Login page 24
5.3 Snapshot of Admin Dashboard 25
5.4 Snapshot of Add Department 25
5.5 Snapshot of Manage Department 26
5.6 Snapshot of Edit Department 26
5.7 Snapshot of Leave Type 27
5.8 Snapshot of Leave Details on Admin page 27
5.9 Snapshot of Employee Profile 28
5.10 Snapshot of Apply for Leave 28

(iv)
Employee Leave Management System DBMS Mini-Project

CHAPTER 1

INTRODUCTION

The Employee Leave Management System (ELMS) is an Intranet based application that can
be accessed throughout the organization or a specified group/Dept. This system can be used to
automate the workflow of leave applications and their approvals.
The project has been planned to be having the view of distributed architecture, with
centralized storage of the database. The application for the storage of the data has been
planned. Using the constructs of MySQL Server and all the user interfaces have been
designed using the PHP technologies. The database connectivity is planned using the
“MySQL Connection” methodology. The standards of security and data protective mechanism
have been given a big choice for proper usage. The application takes care of different modules
and their associated reports, which are produced as per the applicable strategies and standards
that are put forwarded by the administrative staff.

1.1 Introduction to DBMS

DBMS stands for Database Management System. We can break it like this DBMS =
DataBase + Management System. The database is a collection of data and a Management
System is a set of programs to store and retrieve those data. Basically, DBMS is a software
tool to organize (create, retrieve, update and manage) data in a database.

The main aim of a DBMS is to supply a way to store up and retrieve database
information that is both convenient and efficient. By data, we mean known facts that can be
recorded and that have embedded meaning. Normally people use software such as DBASE IV
or V, Microsoft ACCESS, or EXCEL to store data in the form of a database. A datum is a unit
of data. Meaningful data combined to form information. Hence, information is interpreted
data – data provided with semantics. MS. ACCESS is one of the most common examples of
database management software.

Database systems are meant to handle large collections of information. Management

of data involves both defining structures for the storage of information and providing
AIT/CSE/2022-23 1
system must ensure the safety of the information stored, despite system crashes or attempts at
unauthorized access.mechanisms that can do the manipulation of those stored information.
Moreover, the database

1.1.1 Why DBMS?

● To develop software applications in less time.

● Data Independence and efficient use of data.

● For uniform data administration.

● For data integrity and security.

● For concurrent access of data, and data recovery from crashes.

● To use user-friendly declarative query language.

1.1.2 Database applications

● Telecom: There is a database to keep track of the information regarding calls made,
network usage, customer details, etc. Without the database systems, it is hard to
maintain that huge amount of data that keeps updating every millisecond.
● Industry: Where it is a manufacturing unit, warehouse, or distribution center, each
one needs a database to keep the records of ins and outs. For example, distribution
centers should keep a track of the product units that are supplied into the centre as well
as the products that got delivered out from the distribution centre on each day; this is
where DBMS comes into the picture.
● Education sector: Database systems are frequently used in schools and colleges to
store and retrieve the data regarding student details, staff details, course details, exam
details, payroll data, attendance details, fees details etc. There is a hell lot of
interrelated data that needs to be stored and retrieved efficiently.
● Online shopping: You must be aware of the online shopping websites such as
Amazon, Flipkart etc. These sites store the product information, your addresses and
preferences, credit details and provide you the relevant list of products based on your
query. All this involves a Database management system.
 ● Banking system: For storing customer info, tracking day to day credit and debit
transactions, generating bank statements etc. All this work has been done with the help
of Database management systems.

1.1.3 Advantages of DBMS

A DBMS manages data and has many advantages.

● Data Independence: Application programs should be as free or independent as

possible from details of data representation and storage. DBMS can supply an abstract
view of the data for insulating application code from such facts.
● Efficient data access: DBMS utilizes a mixture of sophisticated concepts and
techniques for storing and retrieving data competently and this feature becomes
important in cases where the data is stored on external storage devices.
● Data integrity and security: If data is accessed through the DBMS, the DBMS can
enforce integrity constraints on the data.
● Data administration: When several users share the data, integrating the
administration of data can offer major improvements. Experienced professionals
understand the nature of the data being managed and can be responsible for organizing
the data representation to reduce redundancy and make the data to retrieve efficiently.
● Providing backup and recovery: A DBMS must provide facilities for recovering
from hardware or software failures. The backup and recovery subsystem of the DBMS
is responsible for recovery.
● Permitting inferencing and actions using rules: Some database systems provide
capabilities for defining deduction rules for inferencing new information from the
stored database facts.
1.1.4 Components of DBMS

Fig-1.1: Components of a Database Management System

● Users: Users may be of any kind such as DB administrator, System developer or
database users.
● Database application: Database application may be Departmental, Personal,
organization’s and / or Internal.
● DBMS: Software that allows users to create and manipulate database access.
● Database: Collection of logical data as a single unit.
● Database access language: This is used to access the data to and from the database,
to enter new data, update existing data, or retrieve required data from databases. The
user writes a set of appropriate commands in a database access language, submits
these to the DBMS, which then processes the data and generates and displays a set of
results into a user readable form.
1.1.5 Three-Schema architecture

Fig-1.2: Architecture of database system

The levels form a three-level architecture that includes an external, a conceptual, and an
internal level. The way users recognize the data is called the external level. The way the
DBMS and the operating system distinguish the data is the internal level, where the data is
actually stored using the data structures and file. The conceptual level offers both the mapping
and the desired independence between the external and internal levels.

1.1.6 STUDY OF THE SYSTEM

GUI’S
In the flexibility of the uses the interface has been developed a graphics concept in mind,
associated through a browses interface. The GUI’S at the top level have been categorized as
1. Administrative user interface
2. The operational or generic user interface
The administrative user interface concentrates on the consistent information that is practically,
part of the organizational activities and which needs proper authentication for the data
collection. The interfaces help the administrations with all the transactional states like Data
insertion, Data deletion and Date updation along with the extensive data search capabilities.
The operational or generic user interface helps the users upon the system in transactions
through the existing data and required services. The operational user interface also helps the
ordinary users in managing their own information helps the ordinary users in managing their
own information in a customized manner as per the assisted flexibilities.

NUMBER OF MODULES
The system after careful analysis has been identified to be presented with the following
modules:
The modules involved are:
 Administration
 Employee
 Authentication
Administrator:-
In this module the Administrator has the privileges to add all the Employees and register them
in the organization and check the information of the Employee and check the status of the
leave when they have taken and what type of leave they have taken and search is done based
on the employee and report is generated based on employee.

Employee:-
In this module employee has the privileges to use his username and password for login and
he/ she can apply for the leave and he/ she can check the status of leave (approved or not
approved).

Authentication:-
This module contains all the information about the authenticated user. User without his
username and password can’t enter into the login if he is only the authenticated user then he
can enter to his login.
CHAPTER 2

SYSTEM REQUIREMENTS
2.1 Hardware Requirements
 Processor: Intel Core2 Quad @ 2.4Ghz on Windows® Vista 64-Bit / Windows® 7
64-Bit / Windows® 8 64-Bit / Windows® 8.1 64-Bit.
 RAM: 2GB of RAM

 Memory: 256GB Hard drive

 Keyboard: MS-compatible keyboard

 Mouse: MS-compatible mouse

2.2 Software Requirements

 Operating system: Windows® Vista 64-Bit / Windows® 7 64-Bit / Windows® 8 64-
Bit / Windows® 8.1 64-Bit / Windows® 10
 Front end: HTML, BOOTSTRAP,CSS, JAVASCRIPT

 Back end: MySQL and PHP

 IDE:VS Code

 Text Editor: VS Code

 Database: MySQL
 Server: XAMPP enabled with Apache and MySQL

 Browser: Chrome etc.

2.3 Functional Requirements

 New Employee Registration: The system should allow a new employee to added by
filling the required details.
 Admin Login: The admin can login to his/her account and view the details of every
employee and also the Leaves of the employee and Approval of leave.
 Automatic update to database once a new Employee registered. Also, if a
employee requests permission of leave , it gets automatically updated to the
database.
2.4 Non-functional Requirements

 Performance Requirements: Performance of the system should be fast and

 accurate. System shall handle expected and unexpected errors. Should be able
 to handle large amount of data.
 Safety Requirements: Must be two servers, one main server and one backup server.
 Security Requirements: Admin authentication and validation of employees using their
password. Proper accountability which includes not allowing a employee to see other
employee’s account. Only admin will see and manage all user’s account. Proper user
authentication should be provided.
CHAPTER 3

DESIGN
3.1 System Design

3.1.1 INTRODUCTION

Software design sits at the technical kernel of the software engineering process and is applied
regardless of the development paradigm and area of application. Design is the first step in the
development phase for any engineered product or system. The designer’s goal is to produce a
model or representation of an entity that will later be built. Beginning, once system
requirement have been specified and analyzed, system design is the first of the three technical
activities -design, code and test that is required to build and verify software.
The importance can be stated with a single word “Quality”. Design is the place where quality
is fostered in software development. Design provides us with representations of software that
can assess for quality. Design is the only way that we can accurately translate a customer’s
view into a finished software product or system. Software design serves as a foundation for all
the software engineering steps that follow. Without a strong design we risk building an
unstable system – one that will be difficult to test, one whose quality cannot be assessed until
the last stage.
During design, progressive refinement of data structure, program structure, and procedural
details are developed reviewed and documented. System design can be viewed from either
technical or project management perspective. From the technical point of view, design is
comprised of four activities – architectural design, data structure design, interface design and
procedural design.
3.1.2 Use Case Diagram of Admin

Admin Dashboard

Manage Department
(Add / update / delete)

Manage Leave
type(Add/update/delete

Manage Employees
(Add /update /Delete)
Admin

Manage Leave
requests(Approve/not
approve)

Change

Fig-3.1.2: Use Case Diagram of Admin

3.1.2 Use Case Diagram of Employee

Employee Profile

(Update)

Change Password

Apply for Leave

Employee

View leave History

Fig : 3.1.2 Use Case Diagram of Employee

3.1.3 FLOW CHART

3.1.3.1 User flow chart

Fig: 3.1.3.1 User Flow Chart

3.1.3.2 User Admin chart

Fig:3.1.3.2 Admin Flow chart

3.2 E – R DIAGRAMS

Fig:3.2.1 Entity Relationship Diagram

1

N
1

N
N

N 1
N
N
M N
N:M
 Any number of users can renew any number of books in the library. (N:M).
 Any number of books can be returned by any number of users(N:M).
1:N
 One user can receive any number of messages.
 One user can give N number of recommendations.
 One book can be associated with N number of records
 One book can be written by N number of authors.
 One user can create N number of records.

3.3 Schema Diagram

Fig: 3.3.1 Schema Diagram

Chapter 4

IMPLEMENTATION

4.1 Tables

SYNTAX: Create table table_name (attribute_1 data_type_1,attribute_2 data_type_2,

attribute_n data_type_n, primary key(attribute), foreign key(attribute) references
parent_table(attribute) on delete cascade);

4.1.1 Admin Table:

CREATE TABLE admin ( id int(11) NOT NULL, UserName varchar(100) NOT NULL,
Password varchar(100) NOT NULL, updationDate timestamp NOT NULL DEFAULT
'0000- 00-00 00:00:00' ON UPDATE current_timestamp)))

4.1.2 Department Table:

CREATE TABLE tbldepartments (

id int(11) NOT NULL,
DepartmentName varchar(150) DEFAULT NULL,
DepartmentShortName varchar(100) DEFAULT
NULL,
DepartmentCode varchar(50) DEFAULT NULL, CreationDate timestamp NULL
DEFAULT current_timestamp())
4.1.3 Employees Table:

CREATE TABLE tblemployees(id int(11) NOT NULL,EmpId varchar(100) NOT NULL,

FirstName varchar(150) DEFAULT NULL,LastName varchar(150) DEFAULT NULL,

EmailId varchar(200) DEFAULT NULL,Password varchar(180) DEFAULT NULL,

Gender varchar(100) DEFAULT NULL, Dob varchar(100) DEFAULT NULL,

Department varchar(255) DEFAULT NULL,Address varchar(255) DEFAULT NULL,

City varchar(200) DEFAULT NULL,Country varchar(150) DEFAULT NULL,

Phonenumber char(11) DEFAULT NULL,Status int(1) DEFAULT NULL,

RegDate timestamp NULL DEFAULT current_timestamp() )

4.1.4 Leaves Table:

CREATE TABLE tblleaves (id int(11) NOT NULL, LeaveType varchar(110) DEFAULT
NULL,ToDate varchar(120) DEFAULT NULL,FromDate varchar(120) DEFAULT
NULL,Description mediumtext DEFAULT NULL,PostingDate timestamp NULL DEFAULT
current_timestamp(),AdminRemark mediumtext DEFAULT NULL, AdminRemarkDate
varchar(120) DEFAULT NULL, Status int(1) DEFAULT NULL,IsRead int(1) DEFAULT
NULL, empid int(11) DEFAULT NULL)
4.1.5 Leave types Table:

CREATE TABLE tblleavetype ( id int(11) NOT NULL,

LeaveType varchar(200) DEFAULT NULL,

Description mediumtext DEFAULT NULL,

CreationDate timestamp NOT NULL DEFAULT current_timestamp()

4.2 TRIGGERS AND ROUTINES

4.2.1 TRIGGERS
Trigger to update purchase status of the customer when he place an order
 CREATE TRIGGER
`chng_status` AFTER INSERT ON `orders`
FOR EACH ROW UPDATE customer set purchase='ordered' WHERE cid=new.cid;
Trigger to update purchase status of the customer when he place a return order
 CREATE TRIGGER
`ret_status` AFTER INSERT ON `return_order`
FOR EACH ROW UPDATE customer set purchase='returned' WHERE cid=new.cid;
4.2.2 ROUTINES
Routine to retrieve data of customer who placed atleast one order.
CREATE DEFINER=`root`@`localhost` PROCEDURE ‘ordered customer details’()
Select c.*,o.oid from customer c ,orders o where c.cid=o.oid.

Routine to retrieve data of product which has been orderes.

CREATE DEFINER=`root`@`localhost` PROCEDURE ‘ordered customer details’()
Select p.*,o.oid from products p,orders o where p.cid=o.oid.

4.3 Queries
Indexes for table `admin`
--
ALTER TABLE `admin`
ADD PRIMARY KEY (`id`);
Indexes for table `tbldepartments`
--
ALTER TABLE `tbldepartments`
ADD PRIMARY KEY (`id`);

--
-- Indexes for table `tblemployees`
--
ALTER TABLE `tblemployees`
ADD PRIMARY KEY (`id`);

--
-- Indexes for table `tblleaves`
--
ALTER TABLE `tblleaves`
ADD PRIMARY KEY (`id`),
ADD KEY `UserEmail` (`empid`);

--
-- Indexes for table `tblleavetype`
--
ALTER TABLE `tblleavetype`
ADD PRIMARY KEY (`id`);

--
-- AUTO_INCREMENT for dumped tables
--

--
-- AUTO_INCREMENT for table `admin`
--
ALTER TABLE `admin`
MODIFY `id` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=2;

--
-- AUTO_INCREMENT for table `tbldepartments`
--
ALTER TABLE `tbldepartments`
MODIFY `id` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=5;

--
-- AUTO_INCREMENT for table `tblemployees`
--
ALTER TABLE `tblemployees`
MODIFY `id` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=3;

--
-- AUTO_INCREMENT for table `tblleaves`
--
ALTER TABLE `tblleaves`
MODIFY `id` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=11;

--
-- AUTO_INCREMENT for table `tblleavetype`
--
ALTER TABLE `tblleavetype`
MODIFY `id` int(11) NOT NULL AUTO_INCREMENT, AUTO_INCREMENT=4;
COMMIT;
CHAPTER 5

SNAPSHOTS
The following snapshot contains the login page
 In Employee login page. Employee can login by using Employee Email.
 By using the Password employee can Login into his account

Fig: 5.1 Snapshot of Employee Login Page

The following snapshot contains admin page

 In Admin Login Page. Admin can login by using Username and
 Password.

Fig: 5.2 Snapshot of Admin Login Page

The following snapshot contains Admin Dashboard

 From Admin Dashboard. Admin see all the details of employees, departments
 Admin can Approve the leaves

Fig: 5.3 Snapshot of Admin Dasnboard Page

The following snapshot contains Add Department

 From Admin page. Admin can add the department based on reuirements.
 Admin can add the department details like Department code.

Fig: 5.4 Snapshot of Admin of Add department Page

The following snapshot contains Manage Department

 In admin page admin he can manages the Departments.

 He can see the details of Department like Department name, Date of creation etc

Fig: 5.5 Snapshot of Admin of Manage department Page

The following snapshot contains Edit Department

 Admin can update the department.

 He can also update details of the department code.

Fig: 5.6 Snapshot of Admin of Edit department Page

The following snapshot contains Leave Type on Admin Page

 Admin can add leave type.

 And also he can add the description for the leave type.

Fig: 5.7 Snapshot of Leave Type Page

The following snapshot contains Leave Details on Admin Page

 Admin can also see the Leave Details of the Employee

 He can sees the leave status, leave type etc.

Fig: 5.8 Snapshot of Leave Details on Admin Page

The following snapshot contains Employee Profile

 In this employee profile page. Employee can update the details of the employee.
 He can change his password in employee profile page.

Fig: 5.9 Snapshot of Employee Profile Page

The following snapshot contains Employee Apply for Leave

 In employee profile page. He can apply leave from this page.

 Employee can choose the leave type from which date to which date and writing
reason for leave

Fig: 5.10 Snapshot of Employee Apply for Leave Page

 CONCLUSION & FUTURE ENHANCEMENT

Conclusion:
Our project is only a humble venture to satisfy the needs to manage their project work.
Several user friendly coding have also adopted. This package shall prove to be a powerful
package in satisfying all the requirements of the school. The objective of software
planning is to provide a frame work that enables the manger to make reasonable
estimates made within a limited time frame at the beginning of the software project and
should be updated regularly as the project progresses.
At the end it is concluded that we have made effort on following points… :
 A description of the background and context of the project and its relation to work already
done in the area.
 Made statement of the aims and objectives of the project.
 The description of Purpose, Scope, and applicability.
 We define the problem on which we are working in the project.
 We describe the requirement Specifications of the system and the actions that can be done
on these things.
 We understand the problem domain and produce a model of the system, which describes
operations that can be performed on the system.
 We included features and operations in detail, including screen layouts.
 We designed user interface and security issues related to system.
 Finally the system is implemented and tested according to test cases.

FUTURE ENHANCEMENTS
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 Employee Leave Management System including
With more facilities.
 We will host the platform on online servers to make it accessible worldwide
 Integrate multiple load balancers to distribute the loads of the system

 Create the master and slave database structure to reduce the overload of the database
queries
 Implement the backup mechanism for taking backup of codebase and database on regular
basis on different servers

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 Employee and
Leave. 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 Employee Leave Management System.
Enhancements can be done to maintain all the Employee, Leave, Company, Payroll, Salary.

We have left all the options open so that if there is any other future requirement in the system
by the user for the enhancement of the system then it is possible to implement them.In the last
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
underlining success of process.
 BIBLIOGRAPHY

For PHP
 https://www.w3schools.com/php/default.asp
 https://www.sitepoint.com/php/
 https://www.php.net/

For MySQL
 https://www.mysql.com/
 http://www.mysqltutorial.org

For XAMPP
 https://www.apachefriends.org/download.html