Divya Report
Divya Report
Submitted By
Name: REKHA H
USN: 1OX21MC075
DEPARTMENT OF COMPUTER APPLICATIONS
Bangalore-560068
CERTIFICATE
This is to certify that the Mini Project report on Leave Management System has been
carried out byMs. Rekha HUSN: 1OX21MC075
student of 2th semester MCA, submitted in the partial fulfillment of requirement
prescribed by the V.T.U. for “MASTER OF COMPUTER APPLICATION” for 20MCA29 Web
Technologies Lab with Mini-project course during the year 2021-2022.
Submitted for the VTU Examination held on September 2021 at THE OXFORD COLLEGE OF ENGINEERING,
Bommanahalli, Hosur Road, Bangalore, Karnataka, India.
The Satisfaction and euphoria of the successful completion of any task would be
incomplete without the mention of the people who made it possible. The constant guidance
of these people and encouragement provided by them crowned my efforts with success and
glory. I consider it as a privilege to express my gratitude to all those who led and guided me
in the course of this project.
Finally I thank my parents and the MCA Department staff who have been a constant
source of inspiration for the completion of this project.
Name: REKHA H
USN: 1OX21MC075
CONTENTS
SL.NO PAGE NO.
TITLE
1. ABSTRACT 02
2.
INTRODUCTION
Introduction to the project
Statement of the Problem 03
Technologies used
3.
REQUIRMENTS
Software Requirement 06
Hardware Requirement
4. MODEL 07
5.
ANALYSIS
System Study 09
Feasibility Study
6. IMPLEMENTATION 12
7. CODE 15
8. TESTING 18
9. CONCLUSION 20
10. 20
FUTURE ENHANCEMENT
This is a PHP Project entitled Leave Management System. In this simple project, the main
purpose of this project is to make a faster and reliable web application. At the initial stage of my
study of PHP Programming Language. It is useful for Employers to manage leave of employees.
This project manages aims to manage and track all types of leaves required and granted to an
employee.
This project is aimed at developing an online leave management system that is of importance to
an organization. The Leave Management System (LMS) 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 periodic crediting of leave
is also automated. There are features like email notifications, cancellation of leave, automatic
approval of leave, report generators etc. in this system.
2. INTRODUCTION
PHP
MySQL Database
HTML
HTML (Hypertext Markup Language) is the most basic building block of the Web.
It defines the meaning and structure of web content. Other technologies besides
HTML are generally used to describe a web page's appearance/presentation (CSS)
or functionality/behavior (JavaScript).
CSS
Cascading Style Sheets (CSS) is a simple mechanism for adding style (e.g., fonts,
colors, spacing) to Web documents.
Bootstrap
After studying the problem and its environment, the following requirement
have been identified for developing the system.
RAM : Min 4 GB
Waterfall Model
1. System requirements
2. Software requirements
3. Analysis
4. Program design
5. Coding
6. Testing
7. Operations
1. System requirements
2. Software requirements
Identify, select and document the software features necessary to satisfy the
system requirements.
A deliverable at the end of this stage is the software requirements
document.
Another deliverable is the preliminary design specification.
3. Analysis
4. Program design
5. Coding
6. Testing
7. Operations
5. ANALYSIS
5.1 System Analysis
System analysis is the process of gathering and interpreting facts, diagnosing problems
and using the facts to improve the system. System specifies what system should do. A system is
a set of components that interact to accomplish some purpose.
In the existing system Employees find it difficult to apply for leaves and vacations, especially
Draw backs in existing system: Existing system is human driven (manual), so slow and is also
involving too much of paper work
The feasibility of a project can be ascertained in terms of technical factors, economic factors, or
both. A feasibility study is documented with a report showing all the ramifications of the project
Technical Feasibility.
Technical feasibility
Technical feasibility refers to the ability of the process to take advantage of the current state of
the technology in pursuing further improvement. The technical capability of the personnel as
well as the capability of the available technology should be considered. Technology transfer
between geographical areas and cultures needs to be analyzed to understand productivity loss (or
gain) due to differences (see Cultural Feasibility). so on so technically our project is feasible.
Economic Feasibility
This involves the feasibility of the proposed project to generate economic benefits. A benefit-
cost analysis and a breakeven analysis are important aspects of evaluating the economic
Financial Feasibility
Cultural Feasibility
Cultural feasibility deals with the compatibility of the proposed project with the cultural setup of
the project environment. In labor-intensive projects, planned functions must be integrated with
the local cultural practices and beliefs. For example, religious beliefs may influence what an
individual is willing to do or not do.
Social Feasibility
Social feasibility addresses the influences that a proposed project may have on the social system
in the project environment. The ambient social structure may be such that certain categories of
workers may be in short supply or nonexistent. The effect of the Project on the social status of
the project participants must be assessed to ensure compatibility. It should be recognized that
workers in certain industries may have certain status symbols within the society.
Market Feasibility
6. IMPLEMENTATION
Screenshots:
Employee’s Record Page
Employee Details
<?php
if(!file_exists($page.".php") && !is_dir($page)){
include '404.html';
}else{
if(is_dir($page))
include $page.'/index.php';
else
include $page.'.php';
}
?>
<?php require_once('inc/footer.php') ?>
<div class="modal fade" id="confirm_modal" role='dialog'>
<div class="modal-dialog modal-md modal-dialog-centered"
role="document">
<div class="modal-content">
<div class="modal-header">
<h5 class="modal-title">Confirmation</h5>
</div>
<div class="modal-body">
<div id="delete_content"></div>
</div>
<div class="modal-footer">
<button type="button" class="btn btn-primary" id='confirm'
onclick="">Continue</button>
Dept. of MCA Page: 17
<button type="button" class="btn btn-secondary" data-
dismiss="modal">Close</button>
</div>
</div>
</div>
</div>
<div class="modal fade" id="uni_modal" role='dialog'>
<div class="modal-dialog rounded-0 modal-md modal-dialog-
centered" role="document">
<div class="modal-content rounded-0">
<div class="modal-header">
<h5 class="modal-title"></h5>
</div>
<div class="modal-body">
</div>
<div class="modal-footer">
<button type="button" class="btn btn-primary" id='submit'
onclick="$('#uni_modal form').submit()">Save</button>
<button type="button" class="btn btn-secondary" data-
dismiss="modal">Cancel</button>
</div>
</div>
</div>
</div>
<div class="modal fade" id="uni_modal_right" role='dialog'>
<div class="modal-dialog rounded-0 modal-full-height modal-
md" role="document">
<div class="modal-content rounded-0">
<div class="modal-header">
<h5 class="modal-title"></h5>
<button type="button" class="close" data-dismiss="modal"
aria-label="Close">
<span class="fa fa-arrow-right"></span>
</button>
</div>
Dept. of MCA Page: 18
<div class="modal-body">
</div>
</div>
</div>
</div>
<div class="modal fade" id="viewer_modal" role='dialog'>
<div class="modal-dialog modal-md" role="document">
<div class="modal-content">
<button type="button" class="btn-close" data-
dismiss="modal"><span class="fa fa-times"></span></button>
<img src="" alt="">
</div>
</div>
</div>
</body>
</html>
Software testing is a critical element of software quality assurance and represents the
ultimate review of specification, design and coding. In fact, testing is the one step in the software
engineering process that could be viewed as destructive rather than constructive.
A strategy for software testing integrates software test case design methods into a well-
planned series of steps that result in the successful construction of software.
Testing is the set of activities that can be planned in advance and conducted
systematically. The underlying motivation of program testing is to affirm software quality with
methods that can economically and effectively applied to both strategic to both large and small-
scale systems.
Objective of Testing
A good testing case is one that has high probability of finding as yet undiscovered
errors. Testing is a process of executing a program with the intent of finding errors in it .A
successful test is one that uncovers an as yet undiscovered error .The aim of testing is to
determine that a program works by showing that it has no errors .
Testing is usually relying on to detect the faults on each phase, in addition to the
faults introduced during the coding phase itself. Due to this, different levels of testing are used in
the testing process, each level of testing aims to test different aspect of a system.
Unit Testing will be done to test field validations, navigation, functionality of the
programs and its blocks. These tests are applied on various functions within each program and
other critical program blocks.
Module testing will be done to test the interaction between the various programs
within one module. It checks the functionality of each program with relation to other programs
within the same module. It then tests the overall functionality of each module.
Integration testing is done to test the functionality and interfacing between the
modules. The system is built up of various modules, which work together to automate the
activities of the library management system. These modules should work together in a seamless
way to achieve the desired results. Integration testing will test for this property of the modules.
The modules display a cause and effect relationship, if data in one module is changed, then it
affects the data to change in some other module also. Integration testing needs to check if the
modifications do not adversely affect some other modules.
Acceptance testing was done after the implementation of the system. The acceptance
testing will check if the system works correctly in the user environment and if the entire user
specified functionalities are present. It also tests if the system adheres to the company policies
and quality standard.
The Entire Project has been developed and implemented as per the
requirements, it is found to be bug free as per the testing standard that is
implemented. Any Specification untraced error will be concentrated in the coming
version, which are planned for development in near future.
The System was successful in depicting the aim. As the system developed was
successful in helping patients to easily book appointments, integrated with some
more features.
10 . FUTURE ENHANCEMENT
Currently, this application is only supporting appointment booking for one clinic or
one doctor, Further this can be extended to accompany many doctors and
implement it in a multispecialty hospital.