EMPLOYEE WELFARE SYSTEM

This project is entitled as” EMPLOYEE WELFARE SYSTEM “is

developing using PHP as front end and SQL Server as back end. This project is based on the

employees and their welfare schemes in a company. These concepts and functionalities are

much applicable for all production and industries. The main objective of this project is to

calculate the salary details, attendance details, perfection of the employee, to enrich the

employee etc. These automatic calculations will reduce the burden of the staffs. Each and

every company will have more schemes for their employee, but there will not be proper

software to maintain all the scheme details and there will not be any centralized data.

Using the data report all the data can be furnished using query

reported. Using the query analysis all data can be downloaded in the excel format. For

manual and automatic data processing. Every  organization, whether big or small, has human

resource challenges to overcome. every organization has different employee management

needs, therefore we design exclusive employee management systems that are adapted to your

managerial requirements. This is designed to assist in strategic planning, and will help you

ensure that your organization is equipped with the right level of human resources for your

future goals. Also, for those busy executive who are always on the go, our systems come with

remote access features, which will allow you to manage your workforce anytime, at all

times.  These systems will ultimately allow you to better manage resources. One of the main

features in employee management system is time tracking for employees. Effective time

tracking mechanism saves both time and money for the organization.
Modules:
Login / Registration / Dashboard  Every employee working on contractual basis will
register and once admin approves it will be able to log in. Once they log in they will be
provided with different options to save their personal details, emergency details, permanent
address, current address etc. They can add experience details related to all previous
companies, add skill sets like proficiency in Java or .net etc.

Attendance &Timesheet This module will allow the employee to select the client, then
select the project he or she is working, task and then provide comments like activity is done
and add no of hours worked for any task. Multiple entries can be posted in a day with
different no of hours. Depending upon no of hours saved, the monthly payment will be
calculated. The option will be provided to mark a day as leave or weekly off. It will have a
view wherein there will be a count, hours, work time and Off time. An employee can also
enter his / her off hours like half n hour for lunch.

Leaves  This module will allow employee to save or request leave type for a day or more. It
will also have leave history grid to check the history of leaves.

Admin Admin will actually manage the admin panel in the back end. Admin will create leave
types. Will add projects. Will have option to approve employees registration. Will add
different skill names, Add company profile with all details including logo, Employer ID,
Address Currency, Owner etc,. Add clients and also add tasks. Admin will approve
timesheets submitted by employees and then come up with pay calculations. Admin will
approve hourly rate submitted by the employee.

Pay module  This module will have a grid wherein it will have the option to pull up
employee working hours details and calculate their pay as per hourly rates approved by
-admin. This module will be accessible to admin only.
 II-SYSTEM STUDY

2.1 Existing System:

System analysis is a detailed study of the various operations performed by a system -and their
relationships within and outside of the system. Analysis begins when a user or manager
begins a study of the program using existing system.
 all the records are not kept perfectly because all the work is done manually, so keeping
up to date details of the vehicles, timings of bookings, seat availability for reservation,
vehicles or rooms/hotels availability is not done. Amount of the overall trips are kept in
documents and the calculations done are manually which made lead to huge mistakes.
 Thus, the existing system is very time consuming and being manual work sometimes
lead to a great loss as well.
System analysis can be categorized into four parts.
 System planning and initial investigation
 Information gathering
 Applying analysis tools for structured analysis
 Feasibility study
 Cost/benefit analysis

Problems With Existing System

 Lack of security of data.
 More man power.
 Time consuming.

 Consumes large volume of pare work.

 Needs manual calculations.
 No direct role for the higher officials.
 Damage of machines due to lack of attention.
To avoid all these limitations and make the working more accurately the system needs to be
computerized.
2.2 Proposed System:  
The drawback of the existing system is that it is very difficult to retrieve data
from case files. The propose system is highly automated and makes the travelling
activities much easier and flexible. The user can get the very right information at the very
right time. Customers can get the knowledge of the hotels and vehicles they are going to
use in their trip prior to their starting of trip. This will increase the trust of the customer
into the travel company as well. Once the bookings are confirmed all the travel details,
customer details as well as all the relevant details related to the trip like hotel name, room
number, vehicle number, vehicle owner’s details, date of arriving, date of departure, food
to be served and every single detail will be available to the client. They just need once to
click using mouse and everything is made available to them.

ADVANTAGES OF THE PROPOSED SYSTEM

The system is very simple in design and to implement. The system requires very
low system resources and the system will work in almost all
configurations. It has got following features
 Gives you instant access to a large number of potential customers. It’s a fairly low
cost way to list your property and its rooms.
 Potential reductions in your online marketing spend, as OTAs will invest in marketing
and advertising to attract potential international customers.
 A reduction in your website costs, as OTAs are keen to provide a positive online
experience for customers through good website design and functionality.
 Online travel sites are popular with customers who like to compare accommodation
costs and the services offered by individual providers.
 Impartial reviews on online travel sites may give new customers the confidence to
book.
2.3 SOFTWARE REQUIREMENTS

OS : MS WINDOWS 7

Front End : PHP,HTML,CSS and JavaScript

Back End : MYSQL Server

Framework :Xampp Server.

 2.4 Hardware Requirements
Processor : i3 Processor or above

Clock speed : 500 MHZ

System bus : 32 bits

RAM : 4GB of RAM

HDD : 500 GB or higher

Monitor : LCD Monitor

Keyboard : 108 keys

Mouse : 2 button mouse

2.5 Software Description:

PHP started out as a small open source project that evolved as more and more people found
out how useful it was. Rasmus Lerdorf unleashed the first version of PHP way back in 1994.

 PHP is a recursive acronym for "PHP: Hypertext Preprocessor".

 PHP is a server side scripting language that is embedded in HTML. It is used to
manage dynamic content, databases, session tracking, even build entire e-commerce
sites.
 It is integrated with a number of popular databases, including MySQL, PostgreSQL,
Oracle, Sybase, Informix, and Microsoft SQL Server.
 PHP is pleasingly zippy in its execution, especially when compiled as an Apache
module on the Unix side. The MySQL server, once started, executes even very
complex queries with huge result sets in record-setting time.
 PHP supports a large number of major protocols such as POP3, IMAP, and LDAP.
PHP4 added support for Java and distributed object architectures (COM and
CORBA), making n-tier development a possibility for the first time.
 PHP is forgiving: PHP language tries to be as forgiving as possible.
 PHP Syntax is C-Like.
Common uses of PHP
 PHP performs system functions, i.e. from files on a system it can create, open, read,
write, and close them.
 PHP can handle forms, i.e. gather data from files, save data to a file, through email
you can send data, return data to the user.
 You add, delete, modify elements within your database through PHP.
 Access cookies variables and set cookies.
 Using PHP, you can restrict users to access some pages of your website.
 It can encrypt data.

Characteristics of PHP
Five important characteristics make PHP's practical nature possible −

 Simplicity

 Efficiency

 Security

 Flexibility

 Familiarity

[Link] DESIGN AND DEVELOPMENT

3.1 Data Flow Diagram

Data Flow Diagram (DFD) is a two-dimensional diagram that describes how data is
processed and transmitted in a system. The graphical depiction recognizes each source of data
and how it interacts with other data sources to reach a mutual output. In order to draft a data
flow diagram one must
 Identify external inputs and outputs

 Determine how the inputs and outputs relate to each other

 Explain with graphics how these connections relate and what they result in.

Role of DFD:
 It is a documentation support which is understood by both programmers and non-
programmers. As DFD postulates only what processes are accomplished not how they
are performed.

 A physical DFD postulates where the data flows and who processes the data.

 It permits analyst to isolate areas of interest in the organization and study them by
examining the data that enter the process and viewing how they are altered when they
leave.

Employee Employee Admin

welfare
System
process

DFD for Employee

 View Employee salary
salary Data table

Employee
Employee welfare View Attendenance
login Process attendenance Datatable
information

View profile profile datatable

information

View employee Task_details

daily Tasks Datatable

View report report datatable

ER Diagram
 -
emp_id emp_im
emp_name

employeeTask emp_descripti
Details
Task_id

emp_name
Emp_dep

emp_img
image Emp
empname
phone
emplyee Employee salary
welfare
process
empid
Emp_id
empaddres Salary date
Emp joindate
amount

attendance
Medical leave
Noofpresen

empid Noofdays

Total noof
working days

3.3 FILE DESIGN:

 One problem that would overcome is how to deal with the relations and searching to
minimize I/O operations. All fields are variable length apart from the id, year & length.
Server should be able to synchronize the database to all clients with minimal operations.
When a client comes online, all changes part the date sync back to the client. Another
way to do this would have a separate table on the server which lists all the operations that
have happened and the date they happened; and sync in a similar happened.
Fast read operations for clients
Some sort of index will have to be stored for each table for where each record starts.
This could be small enough to load into memory and could be stores in files separate to the
actual tables to avoid issues.
Minimise I/O operations
The server will store an “index” of the tracks database in memory with the id and file
name so read operations are kept to a minimum. The main problem will be fragmentation
when a record is deleted. Because of the variable length fields, a new record cannot be added
in that place. So fixed length fields should not be used either (as the filename could be huge
for instance).
3.4 INPUT DESIGN
Input design is one of the most important phases of the system design. Input design is
the process where the input received in the system are planned and designed, so as to get
necessary information from the user, eliminating the information that is not required. The
goal of the input design is to make the data entry logical and free from errors.
Input data are collected and organized into a group of similar data. Once identified
input media are selected for processing. In the software, importance is given to develop
Graphical User Interface (GUI), which is an important factor in developing efficient and user-
friendly software. For inputting user data, attractive forms are designed. User can also select
desired options from the menu, which provides all possible facilities.
Input is any data or instructions entered into the memory of a computer. Two types of
input are data and instructions. Data is a collection of unorganized items that can include

3.5 OUTPUT DESIGN

 Computer output is the most important direct source of information to the user. The
output design refers to the result and information that it’s generated by the system forms
many end users. To produce the output which are displayed in a screen, efficient and
intelligent output design improves the system relationship with the users and help indecision
making. It is designed in a user-friendly way to avoid user burden.
Two of the most output media today are printers and screen. Most customers now
access their reports from a hard copy or screen display. Computer’s output is the most
important and direct source of information to the user, efficient, logical, output design
should improve the systems relations with the user and help in decision-making. As the
outputs are the most important source of information to the user, better design should
improve the system’s relation and also should help in decision-making.
3.6 DATABASE DESIGN
Data base is designed to manage large bodies of information. The management of data
involves both the definitions of structures for the storage of information. In addition the data
base system must provide for the safety of the information solved, despite system crashes or
due to attempts at unauthorized access. For developing an efficient database we have to fulfil
certain conditions such as controlled redundancy.
● Defining the data
● Inputting the data
● Locating the data
● Accessing the data
● Communicating the data
● Revising the data
Objectives of Data base deign
For designing data base design several objectives have to be met as follows:
● Ease of use
● Control of data integrity
● Control of redundancy
● Data independence (logical & physical)

[Link] AND IMPLEMENTATION

 INTRODUCTION:
Testing is the process of detecting errors for which the required open web application
secure employment portal specifications stated. Testing performs a very critical role for
quality assurance and for ensuring the reliability of software. The results of testing are used
later on during the software maintenance. The aim of testing is often used to demonstrate that
a program works by showing that it has no errors. The basic purpose of testing phase is to
detect the errors that may be present in the program. Hence one should not start testing with
the intent of showing that a program works, but the intent should be to show that a program
doesn’t work. The main objective of testing is to uncover an error in systematic way with
minimum effort and time.
TESTING OBJECTIVES
The testing objectives are summarized in the following three steps:
 Testing is process of executing a program with the intent of finding an error.
 A good test case is one that has high probability of finding an undiscovered error.
 A successful test is one that uncovers an as yet undiscovered error.
TESTING TYPES
The different types of testing are:
 Unit testing
 Integration testing
 System testing
 Acceptance testing
Unit Testing:
This test focuses on verification effort on the smallest unit of software module. Using the
detailed design and the process specifications testing is done to uncover errors within the
boundary of the module. All the modules must be successful in the unit test before the start of
the integration testing begins. In this project each service is a module like Login, Forms etc.
Each module has to be tested by giving different sets of inputs. The inputs are validated when
accepting from user.
Integration Testing:
After the unit testing the integration of modules has to be done and then integration
testing can be done. The goal here is to see if modules can be integrated properly, the
emphasis being on testing interfaces between different modules.
System Testing:
In the system testing the entire web portal is tested according the software requirement
specifications document.
Acceptance Testing:
The acceptance testing is performed with realistic data of the client, which focus on
the external behaviour of the system; the internal logic of the program is emphasized.
Software testing is a critical element of software quality assurance and represents the ultimate
review of specification, design and coding. Testing is the exposure of the system to trial input
to see whether it produces correct output.
TESTING PHASES:
Software testing phases include the following:
 Test activities are determined and test data selected.
 The test is conducted and test results are compared with the expected results.

TESTING METHODS:
Testing is a process of executing a program to find out errors. If testing is conducted
successfully, it will uncover all the errors in the software.

Any testing can be done basing on two ways:

 White Box Testing
 Black Box Testing
White Box Testing:
It is a test case design method that uses the control structures of the procedural design
to derive test cases.
Using this testing a software Engineer can derive the following test cases:
 Exercise all the logical decisions on either true or false sides.
 Execute all loops at their boundaries and within their operational boundaries.
 Exercise the internal data structures to assure their validity.
Black Box Testing:
It is a test case design method used on the functional requirements of the software. It will
help a software engineer to derive sets of input conditions that will exercise all the functional
requirements of the program.
Black Box testing attempts to find errors in the following categories:
 Incorrect or missing functions
 Interface errors
 Errors in data structures
 Performance errors
 Initialization and termination errors

By black box testing we derive a set of test cases that satisfy the following criteria:
 Test cases that reduce by a count that is greater than one
 The number of additional test cases that must be designed to achieve reasonable
testing.
TESTING PLANS:
Testing can be done in two ways:
 Bottom up approach
 Top down approach
 SYSTEM IMPLEMENTATION
System implementation is the important stage of project when the theoretical design is
tunes into practical system. The main stages in the implementation are as follows:
● Planning
● Training
● System testing and
● Changeover planning
Planning is the first task in the system implementation. Planning is deciding on the
method and the time scale to be adapted. At the time of implementation of any system people
from different departments and system analysis involve. They are confirmed to practical
problem of controlling various activities of people outside their own data processing
departments.
The line manager controlled through an implementation co-ordinate committee. The
committee consists of idea, problems and complaints of user department. It must also be
consider,
● The implementation of system environment.
● Self-selection and allocation for implementation tasks.
● Consultation with unions and resources available.
● Standby facilities and channels of communication.
 CONCLUSION
While developing the system a conscious effort has been made to create and develop a
software package, making use of available tools, techniques and resources - that would
generate a proper system.
While making the system, an eye has been kept on making it as user-friendly, as cost-
effective and as flexible as possible. As such one may hope that the system will be
acceptable to any user and will adequately meet his or her needs.
As in case of any system development processes where there are a number of
shortcomings, there have been some shortcomings in the development of this system also.
The project is still under modification.

BIBLIOGRAPHY
BOOK REFERENCES
 Doyle, Matt. Beginning PHP 5.3 (Wrox Programmer to Programmer), 2009.
 Lerdorf, Rasmus. PHP Pocket Reference, O'Reilly, 2000.
 Nixon, Robin. Learning PHP, MySQL, JavaScript, and CSS: A Step-by-Step
Guide to Creating Dynamic Websites, O'Reilly, 2012.
 Nixon, Robin. Robin Nixon's PHP Crash Course: Learn PHP in 14 easy lectures,
O'Reilly, 2012.
 Ullman, Larry. PHP Advanced and Object-Oriented Programming: Visual
QuickPro Guide (3rd Edition), 2012.
 Ullman, Larry. PHP for the Web: Visual QuickStart Guide, 2011.
 Welling, Luke and Thomson, Laura. PHP and MySQL Web Development, Third
Edition, Sams, 2008.
 Design and Implementation of the Website Based on PHP & MYSQL
 IntInteraction Methods for Smart Glasses: A Survey
 R. Merchant and S. Saxena,  Engineering. Chicago, IL: Britannica Educational Publishing, 2016.

WEBSITE REFERENCES
● [Link]/learn/PHP
● [Link]/PHP
● [Link]
● [Link]
● [Link]
with-ieee%3F
APPENDICES
A. Screenshots
B. Sample Code:
<!DOCTYPE html>
<!--
To change this license header, choose License Headers in Project Properties.
To change this template file, choose Tools | Templates
and open the template in the editor.
-->
<?php
session_start();
if(isset($_SESSION["aid"])){
header('Location:[Link]');

}
if(isset($_SESSION["uid"])){
header('Location:[Link]');

}
?>

<html>
<head>
<meta charset="UTF-8">

<meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width, initial-scale=1">
<link rel="icon" href="images/homepage/[Link]" type="image/x-icon">
<title> Gas Agency</title>
<meta name="author" content="Audenberg Technologies
([Link])" />
<link href="css/[Link]" rel="stylesheet" type="text/css">
<link href="css/[Link]" rel="stylesheet" type="text/css">
<link href="css/[Link]" rel="stylesheet" type="text/css">
<link rel="stylesheet" href="[Link]
integrity="sha384-
mzrmE5qonljUremFsqc01SB46JvROS7bZs3IO2EmfFsd15uHvIt+Y8vEf7N7fWAU"
crossorigin="anonymous">
<link rel="stylesheet" href="css/[Link]">
<script src="js/[Link]"></script>
<script src="js/[Link]"></script>
<link href="css/[Link]" rel="stylesheet" type="text/css">
<link href="css/[Link]" rel="stylesheet" type="text/css">
<link href="[Link] rel="stylesheet">
</head>
<body>
<?php
// put your code here
include '[Link]';
include '[Link]';
?>

<div class="container-fluid" style="background-image:url(images/[Link]);

height: 100vh; background-size: cover; background-position: center;">

<div id="cd-login" style=" padding: 15% 25% ; height: 100%;">

<!-- log in form -->

<h1 style="color: #fff;">Sign In</h1>
 <form class="cd-form" method="post" action="[Link]">

<p class="fieldset">
<label class="image-replace cd-email"
for="eemail">E-mail</label>
<input class="full-width has-padding has-border"
id="email" name="email" placeholder="E-mail">
<span class="cd-error-message">Error
message here!</span>
</p>

<p class="fieldset">
<label class="image-replace cd-
password" for="epass">Password</label>
<input class="full-width has-padding has-border"
id="password" name="password" type="password" placeholder="Password">
<a href="#0" class="hide-
password">Show</a>
<div id="loginresult"
style="display:none;">Error message here!</div>
- </p>

<input type="hidden" id="currentPage" name="currentPage"

value="<?php echo $_SERVER['PHP_SELF']; ?>"
<p class="fieldset">
<input id="loginsubmit" class="full-width" type="submit"
name="loginsubmit" id="login" value="Login">
</p>

</form>
<p class="pull-right">
 <button id="regNowBtn" class="btn btn-default" data-toggle="modal"
data-target="#empsignup" style="color: brown;" >
Register Now</button></p>

<button id="regEmpModalBtn" style="display:none;" data-toggle="modal" data-

target="#empsignup" >
</button>
<!-- <a href="#0" class="cd-close-form">Close</a> -->
</div>

</div>

</body>
</html>

<?php
session_start();
require_once "./functions/[Link]";
$title = "Edit book";
require_once "./template/[Link]";
require_once "./functions/database_functions.php";
$conn = db_connect();

if(isset($_GET['bookisbn'])){
$book_isbn = $_GET['bookisbn'];
} else {
echo "Empty query!";
exit;
 }

if(!isset($book_isbn)){
echo "Empty isbn! check again!";
exit;
}

// get book data

$query = "SELECT * FROM books WHERE book_isbn = '$book_isbn'";
$result = mysqli_query($conn, $query);
if(!$result){
echo "Can't retrieve data " . mysqli_error($conn);
exit;
}
$row = mysqli_fetch_assoc($result);
?>
<form method="post" action="edit_book.php" enctype="multipart/form-
data">
<table class="table">
<tr>
<th>ISBN</th>
<td><input type="text" name="isbn" value="<?php
echo $row['book_isbn'];?>" readOnly="true"></td>
</tr>
<tr>
<th>Title</th>
<td><input type="text" name="title" value="<?php
echo $row['book_title'];?>" required></td>
</tr>
<tr>
<th>Author</th>
<td><input type="text" name="author" value="<?php
echo $row['book_author'];?>" required></td>
</tr>
 <tr>
<th>Image</th>
<td><input type="file" name="image"></td>
</tr>
<tr>
<th>Description</th>
<td><textarea name="descr" cols="40" rows="5"><?
php echo $row['book_descr'];?></textarea>
</tr>
<tr>
<th>Price</th>
<td><input type="text" name="price" value="<?php
echo $row['book_price'];?>" required></td>
</tr>
<tr>
<th>Publisher</th>
<td><input type="text" name="publisher" value="<?
php echo getPubName($conn, $row['publisherid']); ?>" required></td>
</tr>
</table>
<input type="submit" name="save_change" value="Change"
class="btn btn-primary">
<input type="reset" value="cancel" class="btn btn-default">
</form>
<br/>
<a href="admin_book.php" class="btn btn-success">Confirm</a>
<?php
if(isset($conn)) {mysqli_close($conn);}
require "./template/[Link]"
?>

<?php
$book_isbn = $_GET['bookisbn'];
 require_once "./functions/database_functions.php";
$conn = db_connect();

$query = "DELETE FROM books WHERE book_isbn = '$book_isbn'";

$result = mysqli_query($conn, $query);
if(!$result){
echo "delete data unsuccessfully " . mysqli_error($conn);
exit;
}
header("Location: admin_book.php");
?>
[Link] Design:

Table Design:

Table Design:

Table name: Login_details

Field name Data type Size Constraints Description

Uname Text 15 Primary key Employee/admin name

Pword Varchar 15 Not null Password

Table name: employee_details

Field name Data type Size Constraints Description

empid Number 6 Primary key empid

empname Varchar 20 Not null empname

empphone Varchar 15 Not null empphone

empeaddress Varchar 15 Not null empeaddress

empjoindate date 8 Not null empjoindate

Table name: salary_details

Field name Data type Size Constraints Description

empid Number 6 Primary key empid

Salary details Varchar 20 Not null Salary details

salarydate Varchar 20 Not null salarydate

empdepartment Varchar 30 Not null empdepartment