EMPLOYEE MANAGEMENT SYSTEM

A PROJECT REPORT

Submitted by
MOHANA PRIYA S (1613044)
AJITHA P (1613003)
DINESH KUMAR S (1613017)
DINESH PAUL G (1613019)

in partial fulfillment for the award of the degree

of

BACHELOR OF ENGINEERING

in

COMPUTER SCIENCE ANDENGINEERING

K.S.R. COLLEGE OF ENGINEERING

(An Autonomous Institution, Affiliated to Anna University Chennai and Approved by AICTE)

TIRUCHENGODE-637 215

MARCH-2019

1
 K.S.R. COLLEGE OF ENGINEERING
TIRUCHENGODE – 637215
ANNA UNIVERSITY, CHENNAI-600025
BONAFIDE CERTIFICATE
Certified that this project report “EMPLOYEE MANAGEMENT
SYSTEM” is the bonafide work of “MOHANAPRIYA S
(1613044),AJITHA P (1613003), DINESH KUMAR S(1613017) and
DINESH PAUL G(1613019)”whocarried out the project work under my
supervision.

SIGNATURE SIGNATURE
Dr. A. RAJIV KANNAN M.E., Ph.D., Dr.E. BABY ANITHA,M.E.,Ph.D,
HEAD OF THE DEPARTMENT SUPERVISOR
Professor Professor
Department of CSE Department of CSE
K.S.R College of Engineering, K.S.R College of Engineering,
(Autonomous) (Autonomous)
Tiruchengode - 637215. Tiruchengode - 637215.

-----------------------------------------------------------------------------------------------------
Submitted for Project viva-voce held on ……………

Internal Examiner External Examiner

2
 ACKNOWLEDGEMENT
We feel highly honoured to extend our sincere gratitude to our beloved
Founder cum Chairman, Lion Dr. K.S. RANGASAMY, MJF, K.S.R
Educational Institutions and our Chairman cum Managing Trustee Mr. R.
SRINIVASAN, BBM, MISTE., for providing all facilities to complete this
project work.
We would like to acknowledge the constant and kind support provided
by our Principal Dr. P. SENTHILKUMAR, M.E., Ph.D.(IITM), who
supported us in all the endeavours and been responsible for inculcating us all
through our career.

We feel highly elated to thank our respectable Head of the Department,

Dr. A. RAJIVKANNAN, M.E., Ph.D., MCSI., MISTE., who guided us and
was a pillar of support for the successful completion of the project.
Weare thankful to our Project CoordinatorsDr. N. S. NITHYA M.E.,
Ph.D.,and Mr. C. THIRUMALAI SELVAN M.Tech., Ph.D., of our
department for their valuable suggestions and guidance to our project.

We are the most fortunate in having the opportunity to work under

theguide Mrs. E. BABY ANITHA,M.E.,Ph.D., express our sincere thanks to
her.This project has brought out the hidden talents within us.

It is a pleasure to express our gratefulness to our beloved parents for providing

their support and confidence to us for the completion of the project and our
heartfelt thanks to our entire department faculty members, beloved friends,
directly and indirectly who helped us during the tenure of the project.

3
 ABSTRACT

An Employee management system (EMS)is supported to eliminate

and in some cases reduce the hardships faced by this existing system.
Moreover this system is designed for the particular need of the company to
carry out operations in a smooth and effective manner. No formal
knowledge is needed for the user to use this system. Thus by this all it
proves it is user-friendly. EMS is developed to maintain the details of
employees working in any organisation. It has been developed to override
the problems prevailing in the practising manual system.It maintains the
information about the personal and official details of the employees. In this
project, we have added a special feature called leave management system.
This feature provides both admin login and employee login for applying
leave and giving approval through online.

4
 CONTENTS

SYNOPSIS PAGE NO

1 INTRODUCTION
1.1 PROJECT DESCRIPTION 7

2 SYSTEM ANALYSIS 8
2.1 EXISTING SYSTEM 8
2.2 DRAWBACKS OF EXISTING SYSTEM 8
2.3 PROPOSED SYSTEM 8
2.4 ADVANTAGES OF PROPOSED SYSTEM 8

3 SYSTEM REQUIREMENTS 9
3.1 HARDWARE REQUIREMENTS 9
3.2 SOFTWARE REQUIREMENTS 9

4 DESIGN 10
4.1USE CASE DIAGRAM 10
4.2REGISTER 11
4.3 ACTIVITY DIAGRAM 12
4.4 INVALID USERNAME/ PASSWORD 13
4.5 REGISTRATION 13
4.6 ADMIN APPROVAL 14
4.7 SOFTWARE REQUIREMENT 15

5
5 TESTING AND IMPLEMENTATION20
5.1 TESTING20
5.1.1 UNIT TESTING 20
5.1.2 INTEGRATION TESTING 21
5.1.3 VALIDATION TESTING 21
5.1.4 RECOVERY TESTING 21
5.1.5 SECURITY TESTING 21
5.1.6 STRESS TESTING 22
5.1.7 WHITE BOX TESTING 22
5.1.8 BLACK BOX TESTING 22
5.2 SYSTEM IMPLEMENTATION 22
6 CONCLUSION 23
7 APPENDICES 24
7.1 SOURCE CODE 21
7.2 SCREENSHOTS 29
8 REFERENCES 32
9 PUBLICATIONS 32

6
LISTOF ABBREVIATIONS AND DEFINITIONS
OS - Operating System
GUI -Graphical User Interface
RAM -Random Access Memory
MB -Mega Bytes
GB -Giga Bytes
HDD -Hard Disk Drive
UML - Uniform Modeling Language
EMS -Employee Management System

1.INTRODUCTION

1.1 PROJECT DESCRIPTION

Employee Management System is a program to automate or computerize all

employee management operations.
Generally, every company has different departments (for example,
Accounts/Admin/Human Resource/Technical/Vendors etc). For our project,
consider the following departments. Due to the limited time, for our project,
we will not be implementing the features of Vendors department.Employee
Management System is open to admins, HRs, Managers, and regular
employees.

Among all users, only the admins have all privileges to access all the
information of EMS. So the admins will insert, update, remove the
employees, departments, generate reports and whereas other users will have
limited roles. Once the user’s login they can perform few tasks specific to
their role. Employee information can be modified by either Admin, Managers
or by the employee himself/herself. Suppose if we want to keep track of a list
of all changes made to an employee profile, we need to maintain logs.

7
 2.SYSTEM ANALYSIS

2.1 EXISTING SYSTEM

 The records are maintained in registers.
 Time consuming process
 Complicated searching, editing and updating.

2.2 DRAWBACKS OF EXISTING SYSTEM

 Takes more time for consuming of managing numerous users and
prevent error from manual method.
 All course registrations are immediately not updated.
 Anyone can view others details. No login is given specifically.

2.3 PROPOSED SYSTEM

In our proposed system we have the provision for adding the details of
the students by themselves. So the overhead of theschool authorities is
become less. Students can study by their own by choosing the course they
want in a secured and easy manner.
2.4 ADVANTAGES OF THE PROPOSED SYSTEM
 Helps in maintaining the computerized employee details.
 Calculate the salary.
 Easy attendance marking.
 Easy calculation of various leave in categories.

8
 3.SYSTEM REQUIREMENTS

3.1 HARDWARE REQUIREMENTS

RAM:
 Maximum : 64 MB
 Hard disk : 20 MB or more
 Recommended : 1GB or more

3.2 SOFTWARE REQUIREMENTS

 Operating System :Windows XP
 Database used :MySQL , Oracle 6
 Environment : Net beans IDE, brackets
 Language Used : PHP

9
 4.DESIGN

4.1.USE CASE DIAGRAM:

10
4.2.REGISTER

4.2.1 Brief Description

 The use case describes how a User registers and logs in into the
Course Registration System.Takes more time for consuming of
managing numerous users and prevent error from manual method.
 All course registrations are immediately not updated.
 Anyone can view others details. No login is given specifically.

11
4.3.ACTIVITY DIAGRAM:

Basic Flow

This use case starts when the actor wishes to Register to the Course
Registration System.
1. The System requests the Student/Staff to give the needed details
for registration.
2. The Student/Staff enters his/her details.
3. The System validates the details to check if all the mandatory
fields are given.

12
Alternative Flows

Mandatory fields not filled

If in the Basic Flow, the Student/Staff doesn’t enter all the required
details then an error message is displayed and at this point the use case ends.

4.4.INVALID USERNAME/ PASSWORD:

If in the Basic Flow, the user enters an invalid id or password, an

error message is displayed and the use case terminates.
Special Requirements
To login the Student/Staff should have already registered.
Pre-Conditions
None
Post-Conditions
If the use case was successful, the Student/Staff registration details
would have been saved in the database and they are successfully logged in
into the System. If not, the System state is unaltered.
Extension Points
None

4.5.REGISTERATION:

Brief Description
This use case allows a Student to register for any one of the courses offered.
The course catalog, that is created and saved in the Database by the
Administrator, provides a list of all the course offered.

Flow of Events

Basic Flow

This use case starts when a Student wishes to register for a course.
1. The System prompts the Student to give an option that he/she
would like to choose from the displayed catalog.
2. Based on the given choice, the Database is checked to see if seats
are available for that course.
3. If it is available then it is displayed to the Student and the course
is reserved.

13
 4. Details regarding the payment is got from the Student and then on
successful registration the Database is updated.
5. A message is displayed to he Student to indicate the successful
registration.
6. If enough seats are not available the secondary choice is offered
to the Student.

Alternate Flow
None
Special Requirements
None
Pre-Conditions
To view the catalogue and register the Student should be logged in
into the System.
Post-Conditions
If the use case was successful, the Student would have registered for
a course. Otherwise, the system state is unchanged.
Extension Points
None

4.6.ADMIN APPROVAL:

Brief Description
This use case describes how a Staff gives his/her preference to teach
a course and how he is able to view the details of all the Students he is
teaching.
Flow of Events

Basic Flow
This use case starts when a Staff who has registered wants to give
his/her preference to teach a course to be taught from the catalog provided by
the Administrator.
1. The System prompts the Staff to give his/her preference details.
2. The Staff enters his/her preference.
3. The preference details given by the Staff is stored in the database.
4. The System then displays the list of Students who have opted for
that course along with their details.
5. The Staff teaches the Student the preferred course.

14
Alternate Flow
None
Special Requirements
None
Pre-Conditions
The Staff should be logged in into the System and a minimum
number of Students should have opted for that course that he prefers to teach.
Post-Conditions
If, there are a minimum of 5 Students opting for the Staff’s preferred
course, he/she starts teaching them. If not, the System state is unchanged.
Extension Points
None

4.7. SOFTWARE REQUIREMENT SPECIFICATION :

OVERVIEW:
The rest of the Software Requirement Specification
documents explains in detail the various software and hardware requirements
and also elaborates on the constraints involved in the system.
OVERALL DESCRIPTION:

4.7.1PRODUCT PERSPECTIVE:

This system is useful to register for the course from the

available courses in the catalogue. It gives an overall description about the
available courses that a student can opt to learn and a professor can prefer to
teach.
 The system provides login facility to the students.
 The system checks whether the users have the required
qualification to register and to view further details on the courses
available.
 The system allows the Administrator to create the catalog and
store it in the database.
 The system updates the payment details as and when the student
reserves a course successfully.
 The course catalog is framed and the decision of offering the
course, based on the preferences given by the staff and based on
the number of students choosing that particular course, is decided
by the administrator.

15
4.7.2 SYSTEM INTERFACE:

This system is an independent application. It does not interface

with any application.

User Interfaces:
A very interactive GUI is provided to the student and the staff. It
prompts the actors to give the required input for each activity of the system.
Operations:
This software is active and can be used to learn as per the staff’s
schedule.

Site Adaption Requirements:

Not applicable.

Product Functions:
The major functions include:
 Entering the student details into the database.

 Offering the chosen (if available) course to the student.

 Receiving payment from the student.

 Getting the staff’s preference to teach a course.

User Characteristics:

The software product developed has a simple interface that all

students can use and work on. The student requires no technical expertise to
handle the product.
Constraints:
 Hardware limitations-there must be 64 MB on-based memory

 Product limitation- a course is offered only when a minimum

number of students have opted it and also the number of
students who have opted a particular course does not exceed a
maximum limit.

 Control function-in case of errors and services problems, proper

error handling and data recovery mechanism must be included.

16
  Interface to other application-not applicable.

 Parallel operation not applicable.

 Reliability requirements- data redundancy and use of

special/blank characters must be avoided during registration
.
 Safety/ security consideration-the application must be exited
always normally.

 Higher order language requirements – not applicable.

Assumptions and Dependencies:

The data provided by both the student and the staff is assumed to be
valid and true.

4.7.3 External Interface Requirements:

User Interfaces:

The user interfaces is a typical form which includes text boxes, command
buttons and label boxes that are appropriate. During any illegal access an
error message appears using a message box on the screen. The user interface
is designed using MS-Access.

Screen formats/ organizations:

The introductory screen will ask if the user is a student or a staff with
the registration screen to follow. Once the registration is successful, login
screen is provided followed by the course selection, reservation and payment.

Windows format/organizations:

Each function will lead to another window. The user can switch to
the previous window whenever required.

Data format:

The data entered by the users will be alphanumeric.

17
End message:

When there are some errors on entering invalid data, correct data is
asked via the error message else leads to termination of the software.

4.7.4 PERFORMANCE REQUIREMENTS:

Multiple users can accesses the software at any given time.

DESIGN CONSTRAINTS:

The software requires 1 GB RAM. It is based completely on

Windows functionality platform. The software is portable and inaccessible to
users with no valid id or to users who lack the basic qualifying criteria.

SOFTWARE SYSTEM ATTRIBUTES:

RELIABILITY:

The factors establishing the software’s reliability are:

 The user cannot use the software with no valid id.
 The staff’s qualifications are tested and hence a reliable
service is offered.

SECURITY:
 Payment transactions made are highly secure.

PORTABILITY:
 It can operate on all operating systems.

4.7.5. MANTAINABILITY:

Having implemented the concept of modularity it reduces the

complexity involved in maintaining the software.

LOGICAL DATABASE:
The system requires the use of Oracle database
table to hold the details of all the students and staffs.

18
ACTIVITYDIAGRAM :

19
 5. TESTING AND IMPLEMENTATION
5.1 TESTING
 Testing is a process of executing a program with the inent of
finding an error.
 A good test case is one that has a probability of finding an as yet
undiscovered error.
 A successful test is that uncovers as an yet undiscovered error.

TESTING PRINCIPLE
 All tests should be traceable to customer requirement.
 Tests should be planned long before testing begins.
 The Pareto principle applies to software testing.
 Exhaustive testing is not possible.
 To be most effective,an independent third party should conduct
testing.

Software testing involves executing an implementation of the

softwarewith test data and to examine the outputs of the software and its
operational behaviour to check that it is performing as required. Testing is a
dynamic technique of verification and validation because it works with an
executable representation of the system.

5.1.1UNIT TESTING
Unittesting focuses verification effort on the smallest unit of software
design-the software component or module. Using the component-level design
description as a guide, important control paths are tested to uncover errors
within the boundary of the module. The relative complexity of tests and
uncovered errors is limited by the constrained scope established foe unit

20
testing. The unit test is white- box oriented and the step can be conducted in
parallel for multiple components.

5.1.2 INTEGRATION TESTING

Integration testing is a level of software testing where individual units
are combined and tested as a group. The purpose of this level of testing is to
expose faults in the interaction between integrated units. Test drivers and test
stubs are used to assist in Integration Testing. It also involves testing the
integration of systems and packages, testing interfaces to external
organizations. It is the second level of testing done after Unit testing and
before System testing.

5.1.3 SYSTEM TESTING

System testing is the testing of a complete and fully integrated
software product. Usually software is only one element of a larger computer
based system. Software is interfaced with other software/hardware systems.
This testing is actually a series of different tests to exercise full system.

5.1.4 VALIDATION TESTING

Validation testing ensures that the product actually meets the client’s
needs. It can also be defined as to demonstrate that the product fulfils its
intended use when deployed on appropriate environment.

5.1.5 RECOVERY TESTING

Recovery testing is a type of non-functional testing technique
performed in order to determine how quickly the system can recover after it
has gone through system crash or hardware failure. Recovery testing is the
focused failure of the software to verify if the recovery is successful. It is

21
categorized under performance testing and sometimes also carried out with
load testing.

5.1.6 SECURITY TESTING

Security testing is a variant of software testing which ensures, that
system and applications in an organization, are free from loopholes that may
cause a big loss. Security testing of any system is about finding all possible
loopholes and weaknesses of the system which might result into loss of
information at the hands of the employees or outsiders of the organization
5.1.7 STRESS TESTING
Stress testing is used to test the stability and reliability of the system.
This test mainly determines the system on its robustness and error handling
under extremely heavy load conditions. It even tests beyond the normal
operating point and evaluates how the system works under those extreme
conditions. It is done to make sure that the system would not crash under
crunch situations.

5.2 SYSTEM IMPLEMENTATION

According to the system design mentioned earlier, the online
registration system has two major components: back end and front end
system, was successfully implemented and loaded on the Internet. At the
developing stage, after undergoing research and experiment on choices of
programs and databases, My SQL and Java were the major software and
database used for developing the entire website Furthermore, NETBEANS is
an effective platform and stable plus easy to manage, was chosen as a web
server of the website.

22
6.CONCLUSION

Thus, by using this Online Course Reservation System application, a

student can register for a course by providing valid credentials. Once login
successful, student can view the available courses and register for selected
course. They can also make use of video conferencing. This application
provides automated system between Student and Registrar.

6.1 SCOPE
The Scope of the software product developed involves paid service to the
students to select and learn a restricted number of courses that are being
offered. It involves a very simple registration procedure to be done by the
student while being guided by a mentor through the course. The course is
not offered until a minimum number of students opt for it.

7. APPENDICES

23
7.1 SOURCE CODE

<?php
session_start();
error_reporting(0);
include('includes/config.php');
if(isset($_POST['signin']))
{
$uname=$_POST['username'];
$password=md5($_POST['password']);
$sql ="SELECT EmailId,Password,Status,id FROM tblemployees WHERE
EmailId=:uname and Password=:password";
$query= $dbh -> prepare($sql);
$query->bindParam(':uname', $uname, PDO::PARAM_STR);
$query->bindParam(':password', $password, PDO::PARAM_STR);
$query->execute();
$results=$query->fetchAll(PDO::FETCH_OBJ);
if($query->rowCount() > 0)
{
foreach ($results as $result) {
$status=$result->Status;
$_SESSION['eid']=$result->id;
}
if($status==0)
{
$msg="Your account is Inactive. Please contact admin";
} else{
$_SESSION['emplogin']=$_POST['username'];
echo "<script type='text/javascript'>document.location = 'emp-
changepassword.php'; </script>";
}}
else{
echo "<script>alert('Invalid Details');</script>";
}
}
?>
<!DOCTYPE html>
<html lang="en">
<head>
<!-- Title -->
<title>ELMS | Home Page</title>

24
<!-- Styles -->
<link type="text/css" rel="stylesheet"
href="assets/plugins/materialize/css/materialize.min.css"/>
<link href="assets/css/materialdesign.css" rel="stylesheet">
<link href="assets/plugins/material-preloader/css/materialPreloader.min.css"
rel="stylesheet">
<!-- Theme Styles -->
<link href="assets/css/alpha.min.css" rel="stylesheet" type="text/css"/>
<link href="assets/css/custom.css" rel="stylesheet" type="text/css"/>

</head>
<body>
<div class="loader-bg"></div>
<div class="loader">
<div class="preloader-wrapper big active">
<div class="spinner-layer spinner-blue">
<div class="circle-clipper left">
<div class="circle"></div>
</div><div class="gap-patch">
<div class="circle"></div>
</div><div class="circle-clipper right">
<div class="circle"></div>
</div>
</div>
<div class="spinner-layer spinner-spinner-teal lighten-1">
<div class="circle-clipper left">
<div class="circle"></div>
</div><div class="gap-patch">
<div class="circle"></div>
</div><div class="circle-clipper right">
<div class="circle"></div>
</div>
</div>
<div class="spinner-layer spinner-yellow">
<div class="circle-clipper left">
<div class="circle"></div>
</div><div class="gap-patch">
<div class="circle"></div>
</div><div class="circle-clipper right">
<div class="circle"></div>
</div>
</div>

25
<div class="spinner-layer spinner-green">
<div class="circle-clipper left">
<div class="circle"></div>
</div><div class="gap-patch">
<div class="circle"></div>
</div><div class="circle-clipper right">
<div class="circle"></div>
</div>
</div>
</div>
</div>
<div class="mn-content fixed-sidebar">
<header class="mn-header navbar-fixed">
<nav class="cyan darken-1">
<div class="nav-wrapper row">
<section class="material-design-hamburger navigation-toggle">
<a href="#" data-activates="slide-out" class="button-collapse show-on-large
material-design-hamburger__icon">
<span class="material-design-hamburger__layer"></span>
</a>
</section>
<div class="header-title col s3">
<span class="chapter-title">ELMS | Employee Leave Management
System</span>
</div>
</form>
</div>
</nav>
</header>
<aside id="slide-out" class="side-nav white fixed">
<div class="side-nav-wrapper">
<ul class="sidebar-menu collapsible collapsible-accordion" data-
collapsible="accordion" style="">
<li>&nbsp;</li>
<li class="no-padding"><a class="waves-effect waves-grey"
href="index.php"><i class="material-icons"></i>Employe Login</a></li>
<li class="no-padding"><a class="waves-effect waves-grey" href="forgot-
password.php"><i class="material-icons"></i>Emp Password
Recovery</a></li>

<li class="no-padding"><a class="waves-effect waves-grey"

href="admin/"><i class="material-icons"></i>Admin Login</a></li>

26
</ul>
<div class="footer">
<p class="copyright">BATCH 6 ©</p>

</div>
</div>
</aside>
<main class="mn-inner">
<div class="row">
<div class="col s12">
<div class="page-title"><h4>Welcome to Employee Leave Management
System</h4></div>
<div class="col s12 m6 l8 offset-l2 offset-m3">
<div class="card white darken-1">
<div class="card-content ">
<span class="card-title" style="font-size:20px;">Employee 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="signin" 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="signin" value="Sign in" class="waves-effect

waves-light btn teal">
</div>
</form>
</div>
</div>
</div>
</div>
</div>

27
</div>
</main>
</div>
<div class="left-sidebar-hover"></div>

JAVASCRIPT:
<script src="assets/plugins/jquery/jquery-2.2.0.min.js"></script>
<script src="assets/plugins/materialize/js/materialize.min.js"></script>
<script src="assets/plugins/material-
preloader/js/materialPreloader.min.js"></script>
<script src="assets/plugins/jquery-blockui/jquery.blockui.js"></script>
<script src="assets/js/alpha.min.js"></script>

</body>
</html>

7.2 SCREENSHOTS
Home Page:
WELCOME TO EMPLOYEE MANAGEMENT SYSTEM

28
ADMIN LOGIN:

EMPLOYEE PASSWORD RECOVERY:

29
CHANGE PASSWORD:

ADD EMPLOYEE:

30
ADMIN APPROVAL:

UPDATE EMPLOYEE:

31
REFERENCES:
The books referred during predevelopment stages of
project include:
 Software Engineering by Roger S.Pressman.
 Introduction to Object Oriented Analysis And Design
by Craig Larman.
 www.wikepedia.com

PUBLICATIONS

Oriented Journal of Computer Science and Technology

32