CHAPTER 1

INTRODUCTION
The objective of this project is to automate leave management. With the help of this
application users can apply leave through online, Head of the department can approve or
escalate to higher levels; admin can update leave status online. The user can see the status
of all leave taken and their remaining leave through this application. Head of the department
can view the leave status of all staffs with the help of this application. The work flow is
designed in such a way that the leave system generates notification to the respective users.
Head of the department and principal enable them to act upon. Leave management system
is very simple to understand, easy to use and more convenient for implementation. The major
use of designing such an application is to provide a staff or an employee a better way for
scheduling and calculating their leave details. As the existing system increases the paper
work and record maintenance which is a tedious work, so there is a need of new system
which makes the record maintenance easy that is the common requirement for the
management or an organization. Application development can be generally being thought of
having two major components: analysis and design. In Analysis more emphasis is given to
understanding the details of an existing system or a proposed one and then deciding whether
the proposed system is desirable or not and whether the existing system needs improvement.
Thus, analysis is the process of investigating a system, identifying problems, and using the
information to recommended improvements to the system.

1.1 Purpose of the Project

The Mobile HRM (Human Resource Management) project is aimed at developing an online
leave management system which is important to an organization. It is a new concept that is
been developed for our management to maintain leave record. The Mobile HRM is an
Intranet based application that can be accessed throughout the organization or a specified
Department.

This system can be used to automate the workflow of leave request and their approvals.
There are features like approval of leave, cancellation of leave, report generators in this
system At anytime and anywhere employee or staff can apply their leave using this
application.
There is no necessity for manual filling of leave form and wait to get higher officials’
signature. With the help of this application the staff can also view the previous leave applied
by them. Then the leave request will be forwarded to the higher official of the organization.
In day to day life manual maintenance of leave record became difficult. The advantage of
this application is ease of use. The main aim of this application is used to reduce time.

1.2 Project Objectives

The main objective of leave management system is to manage details of leave staff, Faculty,
Attendance. It manages all the information about leave, leave type, attendance. The project
is totally build at administrative end and thus only the administrator is guaranteed the access.
The purpose of the project is to build an application program to reduce the manual work for
managing the leave. Leave Management System is very convenient to implement, easy to
understand and also easy on implementation. The need of designing such Software is to
provide HR Administration a better way for scheduling balancing work load by maintaining
leave details of the staff. It reduces the human efforts of checking the papers for leave request
manually and maintaining it in folders and files and To automate the existing leave
management in educational institutes.

1.2.1 Scope of the Project

The scope of the project is limited to several processes: handling of employee leave
application, managing leave balances, record management administration and leave
management and It will generate the reports such as leave trends of the company, employee
availability, employee leave balance, leave rejection and leave acceptance The leave
management system is designed in such a way that makes it possible to access it through any
web browser program. The leave management system was designed ,developed and
implemented taking the distinction of the leave of absence policies and types of leaves and
the system is exclusively designed and developed for HR Department in general and the
employees leave records section in particular.

1.2.2 Existing System

 In the Current Leave Record Management System, every College/Department
follows manual procedure in which faculty enters information in a record book.
 At the end of each month/session, Administration Department calculates leave/s
of every member which is a time taking process and there are chances of losing
data or errors in the records.
 This module is a single leave management system that is critical for HR tasks and
keeps the record of vital information regarding working hours and leaves.
1.2.3 Proposed System
In this module, Head of Department (HOD) will have permissions to look after data
of every faculty member of their department. HOD can approve leave through this
application and can view leave information of every individual. This application can
be used in a college to reduce processing work load. This project main idea is to
develop an on line centralized application connected to database which will maintain
faculty leaves, notices information and their replacements (if needed). Leave
management application will reduce paperwork and maintain record in a more
efficient systematic way. This module will also help to calculate the number of leaves
taken monthly/annually and help gather data with respect to number of hours worked,
thereby helping in calculating the work hours by the HR Department.
CHAPTER 2

SOFTWARE REQUIREMENT SPECIFICATION

2.1 Technical Feasibility
The technical feasibility in the proposed system deals with the technology
used in the system. It deals with the hardware and software used in the system
whether they are of latest technology or not. It happens that after a system is
prepared a new technology arises and the user wants the system based on that
technology. This system use Windows platform, HTML, CSS, Bootstrap,
JavaScript, as front end technology, MySQL and PHP as backend technology
and PHP software that running on server. Thus Students Blog is technically
feasible.

2.2 Economical Feasibility

Economic analysis is the most frequently used method for evaluating the
effectiveness of a new system. More commonly known as benefit analysis
using HTML, CSS and JavaScript and MySQL easily available in internet.
The economic feasibility study evaluates the cost software development
against the ultimate income or benefits get from the developed system. There
must be scope for profit after the success completion of the project

2.3 Operational Feasibility

The project has been developed in such a way that it becomes very easy even
for a person with little computer knowledge to operate it. This software is
very user friendly and does not require any technical person to operate. Thus
the project is even operationally feasible. Operational feasibility study tests
the operational scope of the software to be developed. The proposed software
must have high operational feasibility. The usability will be high.
2.4 Hardware Requirement

The section of hardware configuration is an important task related to the

software development insufficient random access memory may affect
adversely on the speed and efficiency of the entire system.

The process should be powerful to handle the entire operations .The hard disk
should have sufficient capacity to store the file and application.

 Processor : Intel Pentium Family and above

 RAM : above 712 MB
 Hard Disk : 1.5 GB and above

2.5 Software Requirement

A major element in building a system is the section of compatible software
since the software in the market is experiencing in geometric progression.
Selected software should be acceptable by the firm and one user as well as it
should be feasible for the system.

The document gives a detailed description of the software requirement

specification. The study of requirement specification is focused specially on
the functioning of the system.

It allows the developer or analyst to understand the system function to be

carried out the performance level to the obtained and corresponding
interfaces to be established.

2.6 Tools

HTML, CSS, JavaScript

Hypertext Markup Language (HTML) is the standard markup language

for creating web pages and web applications. With Cascading Style Sheets
(CSS) and JavaScript, it forms a triad of cornerstone technologies for the
World Wide Web.

Web browsers receive HTML documents from a web server or from

local storage and render the documents into multimedia web pages. HTML
describes the structure of a web page semantically and originally included
cues for the appearance of the document.
 HTML elements are the building blocks of HTML pages. With HTML
constructs, images and other objects such as interactive forms may be
embedded into the rendered page. HTML provides a means to create
structured documents by denoting structural semantics for text such as
headings, paragraphs, lists, links, quotes and other items. HTML elements
are delineated by tags, written using angle brackets. Tags such as <img/>
and <input /> directly introduce content into the page. Other tags such as
<p> surround and provide information about document text and may include
other tags as sub-elements. Browsers do not display the HTML tags, but use
them to interpret the content of the page.

Alongside HTML and CSS, JavaScript is one of the three core technologies
of the World Wide Web. JavaScript enables interactive web pages and thus
is an essential part of web applications. The vast majority of websites use it,
and all major web browsers have a dedicated JavaScript engine to execute it.
As a multiparadigm language, JavaScript supports event-driven, functional,
and imperative (including object-oriented and prototype-based)
programming styles. It has an API for working with text, arrays, dates,
regular expressions, and basic manipulation of the DOM, but the language
itself does not include any I/O, such as networking, storage, or graphics
facilities, relying for these upon the host environment in which it is
embedded. JavaScript typically relies on a run-time environment (e.g., a Web
browser) to provide objects and methods by which scripts can interact with
the environment.

MySQL

MySQL is an open source relational database management system

(RDBMS). Its name is a combination of "My", the name of co-founder
Michael Wideness’s daughter, and "SQL", the abbreviation for Structured
Query Language. The MySQL development project has made its source
code available under the terms of the GNU General Public License, as well
as under a variety of proprietary agreements. MySQL was owned and
sponsored by a single for- profit firm, the Swedish company MySQL AB,
now owned by Oracle Corporation. For proprietary use, several paid
[8]

editions are available, and offer additional functionality.

LAMP is an acronym for "Linux, Apache, MySQL, and Perl/PHP/Python”.
Applications that use the MySQL database include:
 TYPO3

 MODx

 Joomla

 WordPress

 Simple Machines Forum

 phpBB

 MyBB and

 Drupal.

MySQL is used in many high-profile. large-scale websites, including

Google, Facebook, Twitter, Flickr, and YouTube. Major features as available
in MySQL 5.6:

 A broad subset of ANSI SQL 99, as well as extensions

 Cross-platform support

 Triggers
CHAPTER 3

ANALYSIS AND DESIGN

3.1 Analyzing the problem

There will be a System home page where there will be a login screen is
available. There are three types of users in the system:

 Staff
 HOD
 Principal

3.1.1 Personal Staff

The staff members logs into his/her interface windows where he can check:
 leave details
 Status of leave application
 Place new request for leave

3.1.2 HOD

HOD logs into his/her interface window to

 Check new leave request

 Check employee leave details

 Check person on leave on particular given dates

 Accept/Rejects leave application

 Manage Employee details

 3.1.3 Principal

Principal logs into his/her interface window to

 Check new leave request

 Check employee leave details

 Check person on leave on particular given dates

 Accept/Rejects leave application

3.2 Design of project

The design specifies the design of various aspects and different stages of the
project. Design is the ultimate framework of the project. In the sense, the
design is a plan or a mindful blueprint of the project to be developed. The
following diagrams shows the flow of the output window.

User case Diagram

Fig:3.1 Use Case Diagram For Leave Management

The above Use case diagram shows how the Staff, HOD and Principal access the
leave management system.
Data Flow diagram

Fig 3.2 Data Flow Diagram For Leave Management

In Level 0 of Leave Management System there will one Staff panel who
will apply for a leave. There is one Principal panel who will validate the
request and gives the notification to the Staff. HOD will accept or reject
the request of Staff.
CHAPTER 4
IMPLEMENTATION
Implementation is the stage where all planned activities are put into action.
Before the implementation of a project, the implementers (spearheaded by the
project committee or executive) should identify their strength and weaknesses
(internal forces), opportunities and threats (external forces).

4.1 Pseudocode for Home page

<link href="https://fonts.googleapis.com/css?family=Merriweather+Sans:400,700"
rel="stylesheet">

<link
href='https://fonts.googleapis.com/css?family=Merriweather:400,300,300italic,400itali
c,700,700italic' rel='stylesheet' type='text/css'>

<header class="masthead">

<div class="container h-100">

<div class="row h-100 align-items-center justify-content-center text-center">

<div class="col-lg-10 align-self-end">

<h1 class="text-uppercase text-white font-weight-bold">

VIVEKANADA INSTITUTE OF TECHNOLOGY</h1>

<hr class="divider my-4">

</div>

<div class="col-lg-8 align-self-baseline">

<p class="text-white-75 font-weight-light mb-5">

WELLCOME TO LEAVE MANAGEMENT SYSTEM</p>

<a class="btn btn-primary btn-xl js-scroll-trigger" href="web">CLICK HERE</a>

</header>
4.2 Pseudocode for Login
<div class="card-content ">

<span class="card-title" style="font-size:20px;">Staff Login</span>

<?php if($msg){?><div class="errorWrap"><strong>Error</strong> : <?php echo

htmlentities($msg); ?>

</div><?php }?>

<div class="row">

<form class="col s12" name="signing" method="post">

<div class="input-field col s12">

<input id="username" type="text" name="username" class="validate"

autocomplete="off" required >

<label for="email">Email Id</label>

</div>

<div class="input-field col s12

<input id="password" type="password" class="validate" name="password"

autocomplete="off" required>

<label for="password">Password</label>

</div>

<div class="col s12 right-align m-t-sm">

<input type="submit" name="signing" value="Sign in" class="waves-effect waves-light

btn teal">
CHAPTER 5
TESTING
The purpose of testing is to discover errors. Testing is the process of trying to
discover every conceivable fault or weakness in a work product. It provides a
way to check the functionality of components, sub-assemblies, assemblies and/or
a finished product. It is a process of exercising software with the intent of
ensuring that the Software system meets its requirements and user expectations
and does not fail in an unacceptable manner. There are various types of test. Each
test type addresses a specific testing requirement

Types of Testing Techniques

5.1 White box testing

White Box Testing is a testing in which the software tester has knowledge of
the inner workings, structure and language of the software, or at least its
purpose. It is used to test areas that cannot be reached from a black box level.

5.2 Black box testing

Black Box Testing is testing software without any knowledge of the inner
workings, structure or language of the module being tested. It is a testing in
which the software under test is treated, as a black box you cannot “see” into
it. The test provides inputs and responds to outputs without considering how
the software works.
5.3 Grey box testing
This involves having knowledge of internal data structures and algorithms
for purpose of designing tests, while executing those tests at the user, or
black-box level. Manipulating input data and formatting output do not
qualify as grey box, because the input and output are clearly outside of the
“black box” that we are calling the system under test.