Mareport

Leave Management System
A PROJECT REPORT
Submitted by
Aniket Rajesh Mistry
190860131020
In partial fulfillment for the award of the degree of
BACHELOR OF ENGINEERING
in
Computer Science and Engineering
Laxmi Institute of Technology, Sarigam
Gujarat Technological University,
Ahmedabad May, 2023

Laxmi Institute of Technology-Sarigam
At: Sarigam, P.B. No-15, P.O.: Valsad, Pin: 396155
CERTIFICATE
This is to certify that the project reports, submitted along with the project
entitled Leave Management System has been carried out by Aniket Rajesh
Mistry under my guidance in partial fulfilment for the degree of Bachelor
of Engineering in Computer Science and Engineering, 8th Semester of
Gujarat Technological University, Ahmedabad during the academic year
2022-23.
Mr. Ritesh Chauhan Prof. Pinal M. Hansora

Internal Guide Head of Department
CSE-LIT(086) CSE-LIT(086)
Sarigam,Valsad Sarigam,Valsad
Laxmi Institute of Technology-Sarigam
At: Sarigam, P.B. No-15, P.O.: Valsad, Pin: 396155
DECLARATION
We hereby declare that the Internship/Project report submitted along with

Internship/Project entitled Leave Management System submitted in partial
fulfilment for the degree of Bachelor of Engineering in Computer Science
and Engineering to Gujarat Technological University, Ahmedabad, is a
bonafide record of original project work carried out by me/us at IT Idol
Technologies,Valsad under the supervision of Mr. Darshayu Mapara and
that no part of this report has been directly copied from any students’ report
or taken from any other source, without providing due reference.
Name of the Student Sign of the Student

i
ACKNOWLEDGEMENT
We take this momentous opportunity to express our heartfelt gratitude, ineptness and
regards to vulnerable and highly esteemed HOD, Mr. Pinal Hansora, Head of
Department of computer science & engineering, Laxmi Institute of Technology for
providing us an opportunity to present our Internship project on “Leave Management
System”.
I convey thanks to Our Project guide, Mr.Ritesh Chauhan, Assistant Professor of
Department of computer science & engineering, Laxmi Institute of Technology for
providing encouragement, constant support and guidance which was of a great help to
complete this project work successfully.
I am grateful to my external guide Mr.Darshayu Mapara, for their invaluable advice

and wholehearted cooperation without which this project would not have seen the light of
day.
I would like to thank all the faculty members for their patience, understanding and
guidance that gave me strength and will power to work through the long tedious hours for
developing a project and preparing the report.
Last but not the least, I would also like to thank my colleagues, who have cooperated
during the preparation of our report and without them this project would not have been
possible. Their ideas helped me a lot to improve my project report.
(190860131020)
ii
ABSTRACT
The Leave Management System (LMS) is a comprehensive management

system for a company, consisting of a user side interface & admin side
interface. The user side interface allows the employee to access their
personal information, including applied leaves & its durations, job title,
assigned project, his or her education details and work schedules. They can
also apply for leave and check their leave status whether the leave is
approved, rejected, pending. The admin side interface is only accessed by
administrators who manages employee data, such as approve or rejecting the
applied leave, updating information, approving the projects & adding new
hires. The admin side has functionality to access any employee data or
manage the client, such as adding new clients and tracking interactions. The
backend is built using MongoDB, allowing for efficient handling of requests
and responses between the user sides and admin sides. The website is
designed to be user-friendly, secure & easy to use, with access controls and
permissions to protect sensitive data.
iii
LIST OF FIGURES
Figure No Figure Description Page No
Figure 1.3.1 Organization Chart1 3
Figure 3.7.1 Internship Scheduling Chart Figure 15
Figure 4.5.1 Use Case Diagram 19
Figure 4.6.1 Class Diagram 20
Figure 4.7.1 Entity Relationship (ER) Diagram 21
Figure 4.8.1 Intern Activity Diagram 22
Figure 4.8.2 Team Lead Activity Diagram 23
Figure 4.8.3 Administration Activity Diagram 24
Figure 4.9.1 Mentor Sequential Diagram 25
Figure 4.9.2 Intern Sequential Diagram 25
Figure 5.2.1 User Collection 27
Figure 5.2.2 Leave Collection 27
Figure 5.2.3 Project Collection 28
Figure 5.2.4 Experience Collection 28
Figure 5.2.5 Form No.12BB Collection 29
Figure 5.2.6 Employee Education Collection 29
Figure 5.2.7 Holiday Collection 30
Figure 6.2.1 Login Screen for both Users 31
Figure 6.2.2 Forget Password Screen 32
iv
Figure 6.2.3 Change Password Screen 32
Figure 6.2.4 Intern Dashboard Screen 33
Figure 6.2.5 Intern Profile Screen 33
Figure 6.2.6.1 Intern Leave Apply Screen 34
Figure 6.2.6.2 Intern WFH Apply Screen 35
Figure 6.2.7 Leave Applied Successfully Screen 35
Figure 6.2.8 Intern leave Status Screen 36
Figure 6.2.9 Intern Leave Revocation Screen 36
Figure 6.3.0 Calendar Screen 37
Figure 6.3.1 Daily Task Screen 37
Figure 6.3.2 Daily Task Table 38
Figure 6.3.3 Team View 38
Figure 6.3.4 Leave Policy 39
Figure 6.3.5 Holiday Event 39
Figure 6.3.6 Add Education 40
v
LIST OF TABLE
Table No Table Description Page No

Table 7.2.1.1 Test Cases 44
vi
Table of Contents
Declaration……………………………………………………………………………. i
Acknowledgement ........................................................................................................ ii
Abstract.......................................................................................................................... iii
List of Figures................................................................................................................ iv
List of Tables.................................................................................................................. v
Table of Contents............................................................................................................ vi
Chapter 1. Overview of the company………………………………………………. 1
1.1 History………………………………………………………………………. 1
1.2 Different Product / Scope of work…………………………………………. 2
1.3 Organization chart…………………………………………………………. 3
1.4 Capacity of Plant…………………………………………………………… 4
Chapter 2. Overview of different Plant/Unit/Departments in Company………… 5
2.1 Details about work in each department……………………………………… 5
2.2 List the technical specifications used in each department…………………… 8
2.3 Details about task carried out at each department…………………………… 9
Chapter 3. Introduction to Project/Internship Management ……………………. 10
3.1 Project/Internship Summary…………………………………………………. 10
3.2 Purpose………………………………………………………………………. 10
3.3 Objective……………………………………………………………………... 11
3.4 Scope (What it can do and can’t do) ……………………………………....... 12
3.5 Technology and Literature review…………………………………………… 12
3.6 Project / Internship Planning…………………………………………………. 13
3.6.1 Project / Internship Development Approach and Justification………. 13
3.6.2 Project / Internship Effort and Time, Cost Estimation………………. 13
3.6.3 Roles and Responsibilities…………………………………………… 13
3.6.4 Group Dependencies…………………………………………………. 14
3.7 Project / Internship Scheduling (Gantt Chart/PERT/Network Chart)………… 15
Chapter 4. System Analysis…………………………………………………………. 16
4.1 Study of Current System……………………………………………………... 16
4.2 Problem and Weaknesses of Current System………………………………… 16
4.3 Hardware and Software Requirements of new System………………………. 17
4.4 System Feasibility……………………………………………………………. 18
4.4.1 Technical Feasibility…………………………………………………. 18
vii
4.4.2 Economic Feasibility….……………………………………………… 18
4.4.3 Operational Feasibility.……………………………………………… 18
4.4.4 Schedule Feasibility…………………………………………………. 18
4.4.5 Legal Feasibility……………………………………………………… 19
4.5 Use Case Diagram……………………………………………………………. 19
4.6 Class Diagram………………………………………………………………... 20
4.7 E-R Diagram…………………………………………………………………. 21
4.8 Activity Diagram……………………………………………………………. 22
4.8.1 Intern Activity Diagram……………………………………………... 22
4.8.2 Team Lead Activity Diagram ………………………………………. 23
4.8.3 Administrator Activity Diagram…………………………………...... 24
4.9 Sequence Diagram…………………………………………………………… 25
Chapter 5. System …………………………………………………………………… 26
5.1 System Design & Methodology……………………………………………… 26
5.2 Database Design……………………………………………………………... 27
Chapter 6. Implementation…………………………………………………………. 31
6.1 Implementation technology/tool……………………………………………. 31
6.2 Modules implemented………………………………………………………. 31
Chapter 7. Testing…………………………………………………………………… 41
7.1 Testing Plan / Strategy………………………………………………………. 41
7.2 Test Results and Analysis…………………………………………………… 42
7.2.1.1 Test Cases…………………………………………………………… 44
Chapter 8. Conclusion and Discussion……………………………………………. 45
8.1 Overall Analysis of Internship / Project Viabilities………………………… 45
8.2 Dates of Continuous Evaluation (CE-I and CE-II) …………………………. 46
8.3 Problem Encountered and Possible Solutions……………………………… 46
8.4 Summary of Internship / Project work……………………………………… 46
8.5 Limitation and Future Enhancement………………………………………… 47
Chapter 9. References………………………………………………………………. 48
viii
Project ID: 319593 Chapter 1.Overview of the company
CHAPTER 1. OVERVIEW OF THE COMPANY
1.1 HISTORY
IT Idol Technologies is a rapidly expanding technology company that is dedicated to
delivering high-quality IT solutions to its clients. With a proven track record of success,
the company has already serviced over 50 clients and completed over 350 projects. These
numbers are a testament to the company's commitment to providing clients with top-notch
services that meet their specific needs and requirements.
One of the company’s primary goals is build long-term relationships with its clients. This
is achieved by providing exceptional customer services, delivering quality work, and
always striving to exceed expectations. IT Idol Technologies understands that building
strong, long-term relationships with its clients is essential to its success and the success of
its clients. To achieve its goals, the company employs highly skilled developers with
extensive expertise in all major programming languages, including website and mobile
application development. This allows IT Idol Technologies to tackle a wide range of
projects and deliver Comprehensive solutions to its clients.
Overall, IT Idol Technologies is a dynamic and fast-growing technology company that is

dedicated to delivering high-quality IT solutions to its clients. With its proven track record
of success, commitment to customer service, and highly skilled team of developers, the
company is well-positioned to continue growing and expanding its reach in the technology
industry.
Website: https://itidoltechnologies.com/
Industries: IT services and IT Consulting
CEO: Mrs. Deval Rathod
Company size: 120 employees
Headquarters: Valsad India
Type: Self Owned
Specialties: Technical and Time bounded Management, Expertise in dealing with over-
seas clients, Strong Technical Team, Full-stack development, Hybrid App development,
Gujarat Technological University 1 LIT, Sarigam

and Strategic experience for different business Sectors.
1.2 DIFFERENT PRODUCTS/SCOPE OF WORK

Custom mobile application development
● Android
● IOS
● Flutter
● Ionic
● Native Script
Custom web application development
● PHP
● Angular
● WordPress
● Fii
● Api Development
● Html/CSS
● Laravel
● Node Js
● React
● CodeIgniter
● Cake PHP
● UI/UX Design
● Drupal
E-Commerce
● Magento
● WooCommerce
● PrestaShop

● Shopify
1.3 ORGANIZATION CHART
Fig 1.3 ORGANIZATION CHART

1.4 CAPACITY OF PLANT
The plant is a single-floor facility, with the HR department office situated on the right side
as one enters. This may indicate that the HR department plays an important role in the
plant’s operations, as it is one of the first areas encountered by employees and visitors.
On the opposite side of the entrance is the employee workspace, which may be designed to
provide a more peaceful and focused environment for workers. The layout of the plant may
have been thoughtfully arranged in order to optimize workflow and minimize distractions,
allowing employees to focus on their work and carry out their responsibilities in a
productive manner.
Beside the HR department office is the office of the CEO, which may also be indicative of
the importance of this area of the plant. This central location may provide the CEO with a
good view of the plant and easy access to both the HR department and the meeting rooms
connected to the office.
The presence of two meeting rooms connected to the CEO's office, as well as washrooms
located throughout the plant, may help to facilitate communication and collaboration
among employees. This could potentially lead to more efficient decision-making and
problem-solving, as well as greater overall productivity within the plant.
Overall, the layout and design of this plant appear to have been thoughtfully arranged in
order to provide employees and interns with the necessary resources and facilities to carry
out their work effectively, while also optimizing workflow and encouraging
communication and collaboration among team members.

Project ID:319593 Chapter 2. Overview of the different
Departments of the Company
CHAPTER 2. OVERVIEW OF THE DIFFERENT

DEPARTMENTS OF THE COMPANY
The company has different departments working on the different technologies, financing,
client handling, planning, infrastructure management, HR department, etc.
2.1 DETAILS WORK IN EACH DEPARTMENT
● Management Department
The management department keeps the check on the process of guiding the development,
maintenance, and allocation of resources to attain organizational goals. Managers are the
people in the organization responsible for developing and carrying out this management
process. Management is dynamic by nature and evolves to meet needs and constraints in
the organization’s internal and external environments. The four primary functions of
managers are planning, organizing, leading, and controlling. By using the four functions,
managers work to increase the efficiency and effectiveness of employees, processes,
projects, and organizations as a whole.
● HR Department
The HR (Human Resources) department is responsible for managing the employee life
cycle (i.e., recruiting, hiring, on boarding, training, and firing employees) and
administering employee benefits. It involves hiring the right kind of people at the right time
in the organization. Under recruitment, the obligations and scope of tasks are formulated
for each employee and a legal contact is signed between the employer and employee has
to follow a definite code of conduct in the organization. It has also the responsibility to
ensure good working environment for the employee. It makes sure that there is no
discrimination on any ground in the organization. In case of any disputes which arise
between the employer and employee, it is HRM’s responsibility to resolve such issues in
an effective manner. It is also responsible for organizing various seminars, meetings,
conferences, etc with other firms to generate healthy relationships with them.

● Infrastructure and Operation Department
Infrastructure Management is responsible for the design, installation, maintenance, and

retirement of the systems and personnel that are at the core of an organization. The services
under the responsibility of the Infrastructure Management are typically the underpinning
(or supporting) services, or infrastructure, that enable the delivery of customer-facing IT
services. It will manage the staff and equipment that handles switching, routing, and in
some cases perimeter devices (firewalls). The operation staff works with external vendors
to support hardware and software. They are also responsible for establishing strong
partnerships with vendors to set clear expectations.
● Frontend Department
The department consists of front-end developers. They are computer programmers who
specialize in website design. Frontend developer’s duties include determining the structure
and design of web pages, striking the balance between the functional and aesthetic design,
and ensuring web design is optimized for smartphones using the different technologies,
frameworks, and libraries. Frontend developers are required to work in teams alongside
backend developers, graphic designers, and user experience designers to ensure all
elements of web creation are consistent. They have proficiency in HTML, CSS, SCSS,
JavaScript, various libraries such as Bootstrap, React, and frameworks like Angular,
Vue.js, etc.
● Backend Department
The department consists of the backend developers. They are the computer programmers
who create, code, and improve the server, server-side applications, and databases that,
when combined with front-end codes, help create a functional, seamless experience for the
end-user. They compile and analyze data, processes, and code to troubleshoot problems
and identify areas for improvements. They collaborate with the frontend developers and
other team members to establish objectives and design more functional, cohesive codes to
enhance the user experience. They have fluency or understanding of specific languages
such as Java, PHP, or python. In the organization, they work on the .NET framework.

● Database Department
The database Department are the database designer. The database designer is in charge of
designing, developing, executing, and preserving a company's data management systems.
One of the most important responsibilities of a database designer is to form relationships
between various elements of data and give it a logical structure. They understand the
organization’s data to skillfully carry out the company’s database design projects. They
design database schema and create databases for varied projects of the company.
● QA (Quality Assurance) Department
The main role of the department is quality assurance. A QA engineer focuses on improving
software development processes and preventing defects in production. They make sure the
software/product development team is doing the right things the right way. They perform
typical tasks such as checking if the product complies with the requirements, assessing
tasks, planning ideas to improve product quality, planning tests, and analyzing the test
results. The main roles are Test Analyst, Test Designer, Test Executer, and Test manager.
● BA Department
The department is consisting of experts in business administration. Their primary

responsibilities include liaising between IT and the executive branch, improving the quality
of IT services, and analyzing business needs. The experts are acting as an information
sources and communicators between business branches.
● Mobile Department
The department consists of mobile developers. They are the developers who are able to
create software for phones and tablets and are familiar with the newest technologies in the
mobile world. They are responsible for developing new features and user interfaces from
wireframe models. By cooperating with the backend team, designers and the other team
deliver well- architected and high-quality solutions and ensure the best performance and
user experience of the application.

2.2 LIST OF TECHNICAL SPECIFICATIONS USED IN EACH

DEPARTMENT
1) Frontend Department
● Html
● SCSS
● Bootstrap
● Material UI
● JQuery
● Angular
● React
● Kotlin
● Figma
● Android Native
● Flutter
● IOS Native
● Sketch
● Adobe XD
2) Backend Department
● Java
● C#
● C++
● Python
● Laravel
● Core PHP
● Express Js
● ASP .Net
● Node Js
3) Database Department
● Mysql
● MongoDB
4) Mobile Department

● Xamarin
● Kotlin
● Ionic
● Flutter
2.3 DETAILS ABOUT TASK CARRIED OUT AT EACH
DEPARTMENT
● First of all Business Analytics team makes the Documentation on the Project, in which
this team specifies the all requirement of the Project, Elaborate the project abstract,
describe the Functional and Non-functional requirements and show how the Project
will be look like.
● Then UI/UX team creates user flows, wireframes, prototypes and mockups for the
project.
They translate requirements into style guides, design systems, design patterns and
attractive user interfaces.
● After that all developers (Frontend, Backend and Database) understand the project
requirement by the documentation and Mockups.
● Then Database developer design stable, reliable and effective databases, then optimize
and maintain legacy systems.
● Also Modify databases according to requests and perform test and database usage
issues and malfunctions.
● Back-end developers are responsible for creating, maintaining, testing, and debugging
the entire backend of a website. This includes the core application logic, databases, data
and application integration, API, and other backend processes.
● Front-end developers focus on the visual layout, user interface/interaction, and user
experience. They create components and features that are directly accessed by a user
through the front-end of a website.
● In their work, they translate wireframes from designers into fully realized user
interfaces by creating the buttons, images, links, and pages that all need to function
efficiently, accurately, and quickly in order for the user to carry out a particular task.
interfaces by creating the buttons, images, links and pages that all need to function

Project ID:319593 Chapter 3. Introduction to Project/
Internship Management
CHAPTER 3. INTRODUCTION TO INTERNSHIP
3.1 INTERNSHIP SUMMARY

As an intern at IT Idol Technologies, I worked as a Frontend Developer and was
responsible for the Integrating an api and Frontend designing of Leave Management
System. I was assigned to make Leave Management System in React js.
The Leave Management System (LMS) is a comprehensive management system for a

company, consisting of a user side interface & admin side interface. The user side interface
allows the employee to access their personal information, including applied leaves & its
durations, job title, assigned project, his or her education details and work schedules. They
can also apply for leave and check their leave status whether the leave is approved, rejected,
pending. The admin side interface is only accessed by administrators who manages
employee data, such as approve or rejecting the applied leave, updating information,
approving the projects & adding new hires. The admin side has functionality to access any
employee data or manage the client, such as adding new clients and tracking interactions.
The backend is built using MongoDB, allowing for efficient handling of requests and
responses between the user sides and admin sides. The website is designed to be user-
friendly, secure & easy to use, with access controls and permissions to protect sensitive
data.
During this period of the internship I learn a lot about React js like how to design or create,
a components of website & also learn about how to integrate an api with front-end. We had
a short training period of around one month where we learned basics of front end as well
as backend, I was given many basic tasks to perform and that was the performance
evaluation through assessments. After the completion of the basic training period, I was
assigned to the project of Leave Management System as a front-end developer.
3.2 PURPOSE
The goal of this project is to deliver a Web-Application for It Idol Technologies where the
Mentor’s profile, as well as the intern’s profile, will be managed, Interns will be able to
request for a leave from its Mentor and Mentor can Accept or Reject leaves, updating

information and processing terminations all this can be managed in this website.
3.3 OBJECTIVE
The main objective of the Project Leave Management System is to manage the details of
the interns as well as their Mentors, Leave, Leave Durations & Types. It manages all the
information about Interns and Employees.
The purpose of the project is to build an application program to reduce the manual work
for managing the Leave, Leave Durations, Leave Type, and Company intern’s details. It
tracks all the details about the Interns and their Leave.
Functionalities provided by Leave Management System are as follows:
● User Side Interface: This side of the system is designed for employees to access their
personal information and request leaves. The following are the key functionalities of
this side:
Access personal information: Employees can view and update their personal details,
including contact details, job title, previous job experience, education detail, assigned
task, department, and work schedules.
Leave request: Employees can request for leave through the system, which will be sent
to the admin side for approval only admin has rights to approve leaves.
Leave status: Employees can view their current leave status.

● Admin side Interface: This side of the system is designed for administrators to manage
employee data approve leave requests. This following are the key functionalities of this
side: Employee data management: Admin can add new hires, update information,
process terminations, and view employee information. Leave approval: Admin can
approve or reject leave requests. Client data management: Admin can manage client
data by adding new clients and tracking interactions.

3.4 SCOPE
The Leave management will be the web application where interns will be able to request a
leave from the mentors and HRS.
The admins can manage employee data, such as adding new hires, updating information,
processing terminations, and approving leave requests. This side may also include
functions for client data management, such as adding new clients and tracking interactions.
This will computer computerize various process of the Leave Management System.
● It satisfies the user requirement.
● Be easy to understand by the user and operator.
● Be easy to operate.
● User Friendly interface.
● Be expandable.
3.5 TECHNOLOGY AND LITERATURE REVIEW
During my internship, I had the opportunity to acquire knowledge and skills in the field of
web Development and Frontend Development. Throughout the internship, I was taken the
entire process of building a web application from the basics to the advanced level.
At the beginning of the internship, I started with the basics of Web Development. This
involved understanding the various components of a web page, how they work together,
and how to structure them using HTML and CSS. Additionally, I also learnt about
responsive design, which is the process of building web pages that can adapt to different
screen sizes and devices.
Following that, I developed into Frontend Development using React.js. I learnt how to
design frontend and integrate with api that can communicate with the backend. This
involved understanding how to create user side interface, and connect with the server side.
Overall, my internship experience was highly informative and very helpful, as I gained
practical experience in Web Development and Frontend Development. I was able to learn
from Industry experts and develop the necessary skills to build robust and efficient web
applications.

3.6 INTERNSHIP PLANNING

3.6.1 Internship Development Approach and Justification
The internship program at IT Idol Technologies is of 6 months duration. I joined here for
an internship as an Intern.
There were the basic training session in the 1st month of Internship.
In training the all different topics of Web Development from its basics were taught and
after that there were different task given on the basis of learning.
I have developed my skills during this Internship and learn a lot of technical part of any
language.
From the given task, I learnt to understand the flow of a project, how it start from the
Requirement gathering to Deployment.
3.6.2 Internship Effort and Time, Cost Estimation
For this Project completion, 4 months of duration given in which 1 month was all about
training and sessions.
After one month the training continued with project and my internship was started from 30
January 2023.
In this Project, there were different team who was going to put efforts to complete this
Project. Business Analytics, Database, Frontend, Backend, QA these all teams were in the
project completion.
We all team make the efforts for Requirement Gathering, Analysis, Designing,
Implementation, Testing & Integration and Maintenance.and the all tasks were assigned to
us by the Mentors weekly.
3.6.3 Roles and Responsibilities
My Role at IT Idol Technologies was as a Frontend developer in React js.

Responsibilities:
1) To create the frontend part of this project.

2) To integrate front end with api.
3) Make the interface as much as interactive to user.
4) Make Ui As much as clean as possible.

3.6.4 Group Dependencies

● In It Idol Technologies all the Projects works are performed in a Team.
● First of all Business Analytics team makes the Documentation on the Project, in which
this team specifies the all requirement of the Project, Elaborate the project abstract,
describe the Functional and Non-functional requirements and show how the Project
will be look like.
● Then UI/UX team creates user flows, wireframes, prototypes and mockups for the
Project.
● They translate requirements into style guides, design systems, design patterns and
attractive user interfaces.
● After that all developers (Frontend, Backend and Database) understand the project
requirement by the documentation and Mockups.
● Then Database developer design stable, reliable and effective databases, then optimize
and maintain legacy systems.
● Also Modify databases according to requests and perform tests and database usage
issues and malfunctions
● Back-end developers are responsible for creating, maintaining, testing, and debugging
the entire back end of a website. This includes the core application logic, databases,
data and application integration, API, and other back end processes.
● Front-end developers focus on the visual layout, user interface/interaction, and user
experience. They create components and features that are directly accessed by a user
through the front-end of a website.
interfaces by creating the buttons, images, links, and pages that all need to function
● This is how these all teams (BA, Database, Front end, Back end, QA) depends on each
other’s.

3.7 INTERNSHIP SCHEDULING (GANTT CHART/PERT/NETWORK CHART)
Fig 3.7.1 Internship Scheduling Chart

Project ID: 319593 Chapter 4. System Analysis
CHAPTER 4. SYSTEM ANALYSIS
4.1 STUDY OF CURRENT SYSTEM
Currently, the system in place for requesting leaves by employees involves sending written
emails to the HR department. This means that for every leave request, employees have to
go through the trouble of composing an email and sending it to HR. This process can be
quite cumbersome and time-consuming for most employees, which can affect their
productivity and overall job satisfaction.
Moreover, the existing system has several weaknesses and limitations. For instance, if the
HR department has not reviewed an employee's leave request email, the employee might
not be able to take the leave as planned. This can cause unnecessary stress and frustration
for employees who need to take time off from work for various reasons.
Additionally, managing and keeping track of employees' leave records on the HR end can
be challenging, especially in today's era where there are several automated tools and
software that can help streamline such processes. As a result, the current system might not
be the most efficient and effective way to manage employee leaves.
In conclusion, the manual efforts required to manage employee leaves in the existing
system can be quite tedious, time-consuming, and error-prone. Therefore, it might be
worthwhile for the organization to explore more automated and streamlined approaches to
managing employee leaves, which can improve the overall efficiency and productivity of
the workforce.
4.2 PROBLEM AND WEAKNESS OF CURRENT SYSTEM
The current system for managing intern leave requests is disorganized, with no proper way
to maintain records or track the status of requests. Interns are unable to view the status of
their leave requests, and someone has to manually keep track of the list of interns and their
number of leave.
Mentors are also unable to accurately determine the number of remaining leaves for the
specific intern they are supervising, which can lead to confusion and misunderstandings.
Furthermore, there is no efficient way to know if another mentor has already approved or

rejected an intern's leave request, causing delays and potential scheduling conflicts.
In summary, the lack of an organized system for managing intern leave requests can lead
to inefficiencies, confusion, and potential conflicts. Implementing a streamlined approach
that enables interns to track the status of their leave requests and mentors to accurately
monitor their intern's leave balance can improve the overall productivity and effectiveness
of the intern program.
4.3 HARDWARE AND SOFTWARE REQUIREMENTS OF NEW

SYSTEM
Hardware Requirements
Memory Space:
Minimum – 32 MB
Recommended – 64 MB
HDD – To install the software at least 2 GB and the data storage is depending upon the
organization setup.
PROCESSOR – Intel Pentium IV, 1GHZ or above
RAM – 256MB or above
VIDEO – 1024×768, 24-bit colors
KEYBOARD – Standard 104 Keys(QWERTY)
Software Requirements
Operating System – Windows Vista or higher
Supported browser versions
Chrome latest
Firefox - latest and extended support release (ESR)
Edge - 2 most recent major version
Microsoft SQL Server SSMS - 2 most recent major version
Visual Studio - most recent major versions

Tools and Platforms Used
Frontend: Angular, HTML, CSS, Bootstrap, React js, Material Ui, tailwind.
Database: MongoDB & Microsoft SQL Server
4.4 SYSTEM FEASIBILITY
The 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 changes can be easily done based on the future
upcoming requirements.
4.4.1 Technical Feasibility
In Technical Feasibility study, one has to check whether the current requirements for
building the app is feasible with the available Hardware capabilities. In this application,
our backend needs MongoDB and our frontend needs React js. So, it is evident that the
necessary hardware and software are available for development and implementation of the
proposed system. Hence, the solution is technically feasible.
4.4.2 Economic Feasibility
The purpose of an implementation feasibility study is to verify that the system can be
properly implemented in any environment. So, the current proposed system uses React js
for frontend, which is used to handle all the API requests coming from MongoDB Backend.
So, the proposed system can be easily implemented and hence implementation feasibility
is achieved.
4.4.3 Operation Feasibility
-It is a measure of how well a proposed system solves the problems, and takes advantage
of the opportunities identified during scope definition and how it satisfies the requirements
identified in the requirements analysis phase of system development. The proposed system
is user-friendly and adheres to the requirements, thus acceptable to the users. Hence the
system is operationally feasible.

4.4.4 Schedule Feasibility
The main goal regarding the development of the System is well known, well understood
and can be easily completed in the allocated time. So, respecting the tight schedule and
considering the fixed objectives of the project it is expected to be a feasible system
regarding the schedule concerned.
4.4.5 Legal Feasibility
Legal feasibility is a measure of how well a solution/ proposed system can be implemented
within the existing legal and organization’s policy. It determines whether the proposed
system conflicts with the legal requirement. As there the solution was accepted by the
company management team and had the approval of both the user and developer there
were no such legal conflicts, has the proposed system pass the legal feasibility.
4.5 USE CASE DIAGRAM
Fig 4.5.1 Use Case Diagram

4.6 CLASS DIAGRAM
Fig 4.6.1 Class Diagram

4.7 ER DIAGRAM
Fig 4.7.1 Entity Relationship (ER) Diagram

4.8 ACTIVITY DIAGRAM
Fig 4.8.1 Intern Activity Diagram

Fig 4.8.2 Team Lead Activity Diagram

Fig 4.8.3 Administrator Activity Diagram

4.9 SEQUENCE DIAGRAM
Fig 4.9.1 Mentor Sequential Diagram
Fig 4.9.2 Intern Sequential Diagram

Project ID: 319593 Chapter 5. System Design
CHAPTER 5. SYSTEM DESIGN
5.1 SYSTEM DESIGN & METHODOLOGY
Systems design is the process of defining the architecture, components, modules,

interfaces, and data for a system to satisfy specified requirements.
The System Design Description report provides summary or detailed information about a
system design represented by a model.
Systems design is therefore the process of defining and developing systems to satisfy
specified requirements of the user.
5.2 DATABASE DESIGN
Database designs provide the blueprints of how the data is going to be stored in a system.
A proper design of a database highly affects the overall performance of any application.
The designing principles defined for a database give a clear idea of the behavior of any
application and how the requests are processed.

Data Dictionary
1) User Collection
Table 5.2.1 User Collection
2) Leave Collection
Table 5.2.2 Leave Collection

3) Project Collection
Table 5.2.3 Project Collection
4) Experience Collection
Table 5.2.4 Experience Collection

5) Form no 12B Collection
Table 5.2.5 Form No 12B collection
6) Employee Education Collection
Table 5.2.6 Employee Education Collection

7) Holidays Collection
Table 5.2.7 Holidays Collection

Project ID: 319593 Chapter 6. Implementation
CHAPTER 6. IMPLEMENTATION
6.1 IMPLEMENTATION TECHNOLOGY/TOOL
Supported browser versions

Chrome latest
MongoDB
Visual Studio - most recent major versions
Tools and Platforms Used
Frontend: React js, HTML, CSS, Bootstrap, Material UI
Backend: MongoDB
Database: Mongo Atlas
6.2 MODULES IMPLEMENTED

1) Login Screen
Tam Lead and Intern can login into their individual profiles by providing Email and
password.
Fig 6.2.1 Login Screen for both Users

2) Forgot Password Screen
If Intern or Team Lead as an user forget their password while signing into the web
application, then they can click on forget password link and change the password and go to
login again
Fig 6.2.2 Forget Password Screen
3) Change Password Screen:

Here, Users can change their passwords.
Fig 6.2.3 Change Password Screen

4) User Dashboard Screen:

This is the screen of User Dashboard.
Fig 6.2.4 Intern Dashboard Screen
5) User Profile Screen:

Here user can see his/her details like username, Designation, Department etc and in this
page he can also add his past Company Experience and Education Details.
Fig 6.2.5 Intern Profile Screen
6) User Apply Leave Screen:

This is the Screen for user to apply for the leave. user can apply for 4 types of leave

application:
1) Leave
(i) 1st half day
(ii) 2nd half day
(iii) Single Day
(iv) Multiple Days
Fig 6.2.6.1 Intern Leave Apply Screen

7) Leave Apply Successfully Screen:
Fig 6.2.7 Leave Applied Successfully Screen

8) User leave Status Screen:

User can see all its previous Pending, accepted, rejected or revoked Leave application
here.
Fig 6.2.8 Intern leave Status Screen
9) User Leave Cancel Screen:

User can also apply for Canceling of leave application.
Fig 6.2.9 Intern Leave Revocation Screen

10) User Calendar Screen:
Fig 6.3.0 Calendar Screen
11) Task List:
Fig 6.3.1 Daily Task Screen

Fig 6.3.2 Daily Task Table
12) Team View:
Fig6.3.3 Team View

13) Leave policy:
Fig6.3.4 Leave Policy
14) Holiday Events:
Fig 6.3.5 Holiday Events

15) Add Education:
Fig 6.3.6 Add Education

Project ID:319593 Chapter 7. Testing
CHAPTER 7 TESTING
7.1 TESTING PLAN/STRATEGY
Testing plan
The objective of system testing is to make sure that the whole software production works
according to the requirements, and no significant errors appear in the application. System
testing is the most substantial part of software testing. It involves checking of different
aspects of the system. A software product must pass all the planned tests. Only in this case
its quality can be assured.
We went through several different tests, at the different phases. The tests should validate
from both the requirements perspective and business perspective. At the conclusion of
testing, one should have a high level of confidence that the system will work according to
user requirements and will meet business needs.
Testing strategy
The development process repeats this testing sub-process a number of times for the
following phases:
1) Unit Testing.
Unit Testing tests a unit of code (module or program) after coding of that unit is
completed.
2) Integration Testing
Integration Testing tests whether the various programs that make up a system,
interface with each other as desired, fit together and whether the interfaces between
the programs are correct.
Testing is carried out in such a hierarchical manner to ensure that each component is
correct and the assembly/combination of components is correct. Merely testing a
whole system at the
end would most likely throw up errors in components that would be very costly to
trace and fix.

7.2 TEST RESULTS AND ANALYSIS
Testing methods
Black box and White box testing:

In black-box testing a software item is viewed as a black box, without knowledge of its
internal structure or behavior. Possible input conditions, based on the specifications (and
possible sequences of input conditions), are presented as test cases. In white-box testing
knowledge of internal structure and logic is exploited. Test cases are presented such that
possible paths of control flow through the software item are traced. Hence more defects
than black-box testing is likely to be found. The disadvantages are that exhaustive path
testing is infeasible and the logic might not conform to specification. Instrumentation
techniques can be used to determine the structural system coverage in white box testing.
For this purpose, tools or compilers that can insert test probes into the programs can be
used.
7.2.1 Test Cases

Table 7.2.1.1 Test Case
Test Title Test Steps Expected Result TEST RESULT

Validate Email field Keep the Email field Validation message PASS
as blank must be displayed
using invalid inputs
as “Please enter
Email”
Enter invalid email Validation message PASS

format must be displayed
as “Please enter
Valid Email”
Enter special Validation message PASS

characters in Email must be displayed
field. as “Please enter
Valid Email”
Validate Pass field Keep the Password Validation message PASS

field as blank must be displayed
as “Please enter
Password”

Enter Less than 8 Validation message PASS

characters in must be displayed
Password field. as “Password must
be at least 8
characters”
Enter a Password in Validation message PASS

invalid format. must be displayed
as “Password must
contain at least one
uppercase letter, one
lowercase letter and
one number”
Validate Phone No Keep the Phone No Validation message PASS

field as blank must be displayed
field using invalid
as “Please enter
inputs Phone Number.”
Enter Less than 10 Validation message PASS

characters in Phone must be displayed
No field. as “Please Enter
Valid Phone
Number.”
Enter letters in Phone Validation message PASS

No field. must be displayed
as “Please Enter
Valid Phone
Number.”
Enter More than 10 Validation message PASS

Valid Phone
Number.”

Valid Phone
Number.”
Validate Name field Keep the Name field Validation message PASS
as blank must be displayed
as “Please enter
Name”


characters in Name must be displayed
field. as “Please enter
Valid Name”
Enter numbers in Validation message PASS

Name filed. must be displayed
as “Please enter
Valid Name”

Project ID:319593 Chapter 8. Conclusion and Discussion
CHAPTER 8. CONCLUSION AND DISCUSSION
8.1 OVERALL ANALYSIS OF INTERNSHIP / PROJECT VIABILITIES
Feasibility Study:
● Technical Feasibility:
In Technical Feasibility study, one has to check whether the current requirements
for building the app is feasible with the available Hardware capabilities. In this
application, our backend needs MongoDB and our frontend needs React js. So, it is
evident that the necessary hardware and software are available for development and
implementation of the proposed system. Hence, the solution is technically feasible.
● Operational Feasibility:
Operational feasibility is dependent on human resources available for the project and
involves projecting whether the system will be used if it is developed and
implemented. It is a measure of how well a proposed system solves the problems, and
takes advantage of the opportunities identified during scope definition and how it
satisfies the requirements identified in the requirements analysis phase of system
development. The proposed system is user-friendly and adheres to the requirements,
thus acceptable to the users. Hence the system is operationally feasible.
● Economical Feasibility:
The purpose of an implementation feasibility study is to verify that the system can
be properly implemented in any environment. So, the current proposed system uses
React js for frontend, which is used to handle all the API requests coming from
MongoDB Backend. So, the proposed system can be easily implemented and hence
implementation feasibility is achieved.
The main goal regarding the development of the System is well known, well
understood and can be easily completed in the allocated time. So, respecting the tight
schedule and considering the fixed objectives of the project it is expected to be a
feasible system regarding the schedule concerned.

8.2 DATES OF CONTINUOUS EVALUATION
Date of CE-I: 06-03-2023
Date of CE-II: 11-05-2023
8.3 PROBLEM ENCOUNTERED AND POSSIBLE SOLUTION
In existing System, there are some difficulties to manage the leave applications of Interns
for respective department’s Team Leads. They faces difficulties to track the leave history
of a particular Intern.
This leave management system helps to manage the Profile of each Team Leads, employees
and interns.
And this system also help to keep the track of every leave of each interns and also track the
response of Team Leads and admin (Accept / Reject / Revoke) for those leaves.
8.4 SUMMARY OF INTERNSHIP / PROJECT WORK
During my internship, I worked on the Leave Management System (LMS) project, which
is a comprehensive web application that provides management solutions for a company.
My primary responsibility was to develop the Frontend of the LMS using React js, which
involved Designing of interface and integrating an api between user-side interface.
In addition to frontend development, I also worked on various aspects of the project,

including ensuring the security of the website by implementing Validation and regex code
to protect sensitive data. I also contributed to the development of the user-side interface,
which enables employees to access their personal information and request leave.
Working on the LMS project was a valuable learning experience, as I gained practical
experience in web development and learned to work effectively in a team environment.
Overall, my internship was a great opportunity to apply my technical skills and contribute
to the development of a real-world project.

8.5 LIMITATION AND FUTURE ENHANCEMENT
Limitation
1) Limited Customization Options: The LMS is a pre-built system, which may have
limited customization options. This means that some companies may have specific
requirements that are not accommodated by the system, and it may be challenging to
customize the system to meet those requirements.
2) Limited Mobile Accessibility: The LMS may have limited accessibility on mobile
devices. As the system is primarily designed for desktop users, employees who need
to access the system on their mobile devices may find it challenging to navigate or use
the system effectively.
Future Enhancement
1) Next goal will be to overcome these limitations.
2) Add some extra functionalities like start working on Admin side where I can add
progress chart, chat board, each employee progress bar, etc.
3) If intern will have some query, then he can directly ask in chat to all the Team Leads
together

Project ID:319593 Chapter 9. References
CHAPTER 9. REFERENCES
[1] https://www.w3schools.com/
[2] https://legacy.reactjs.org/docs/getting-started.html
[3] https://www.google.com/search?q=mongodb+atlas&rlz=1C1CHBF_enIN1026IN102
6&oq=Mongo&aqs=chrome.0.69i59l2j69i57j69i64j0i131i433i512j46i131i340i433i
512j69i60l2.4718j0j7&sourceid=chrome&ie=UTF-8
[4] https://code.visualstudio.com/docs
[5] https://www.postman.com/company/about-postman/
[6] https://www.tutorialspoint.com/index.htm
[7] https://stackoverflow.com/

Mareport

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Mareport

Uploaded by

Copyright:

Available Formats

Leave Management System

Aniket Rajesh Mistry

In partial fulfillment for the award of the degree of

Laxmi Institute of Technology, Sarigam

Gujarat Technological University,

Ahmedabad May, 2023

Mr. Ritesh Chauhan Prof. Pinal M. Hansora

We hereby declare that the Internship/Project report submitted along with

Name of the Student Sign of the Student

I am grateful to my external guide Mr.Darshayu Mapara, for their invaluable advice

Aniket Rajesh Mistry

The Leave Management System (LMS) is a comprehensive management

Figure No Figure Description Page No

Figure 1.3.1 Organization Chart1 3

Figure 3.7.1 Internship Scheduling Chart Figure 15

Figure 4.5.1 Use Case Diagram 19

Figure 4.6.1 Class Diagram 20

Figure 4.7.1 Entity Relationship (ER) Diagram 21

Figure 4.8.1 Intern Activity Diagram 22

Figure 4.8.2 Team Lead Activity Diagram 23

Figure 4.8.3 Administration Activity Diagram 24

Figure 4.9.1 Mentor Sequential Diagram 25

Figure 4.9.2 Intern Sequential Diagram 25

Figure 5.2.1 User Collection 27

Figure 5.2.2 Leave Collection 27

Figure 5.2.3 Project Collection 28

Figure 5.2.4 Experience Collection 28

Figure 5.2.5 Form No.12BB Collection 29

Figure 5.2.6 Employee Education Collection 29

Figure 5.2.7 Holiday Collection 30

Figure 6.2.1 Login Screen for both Users 31

Figure 6.2.2 Forget Password Screen 32

Figure 6.2.4 Intern Dashboard Screen 33

Figure 6.2.5 Intern Profile Screen 33

Figure 6.2.6.1 Intern Leave Apply Screen 34

Figure 6.2.6.2 Intern WFH Apply Screen 35

Figure 6.2.7 Leave Applied Successfully Screen 35

Figure 6.2.8 Intern leave Status Screen 36

Figure 6.2.9 Intern Leave Revocation Screen 36

Figure 6.3.0 Calendar Screen 37

Figure 6.3.1 Daily Task Screen 37

Figure 6.3.2 Daily Task Table 38

Figure 6.3.3 Team View 38

Figure 6.3.4 Leave Policy 39

Figure 6.3.5 Holiday Event 39

Figure 6.3.6 Add Education 40

Table No Table Description Page No

CHAPTER 1. OVERVIEW OF THE COMPANY

Overall, IT Idol Technologies is a dynamic and fast-growing technology company that is

Gujarat Technological University 1 LIT, Sarigam

and Strategic experience for different business Sectors.

1.2 DIFFERENT PRODUCTS/SCOPE OF WORK

Gujarat Technological University 2 LIT, Sarigam

1.3 ORGANIZATION CHART

Fig 1.3 ORGANIZATION CHART

Gujarat Technological University 3 LIT, Sarigam

1.4 CAPACITY OF PLANT

Gujarat Technological University 4 LIT, Sarigam

CHAPTER 2. OVERVIEW OF THE DIFFERENT

client handling, planning, infrastructure management, HR department, etc.

2.1 DETAILS WORK IN EACH DEPARTMENT

Gujarat Technological University 5 LIT, Sarigam

● Infrastructure and Operation Department