EMPLOYEE DATABASE AND PAYROLL MANAGEMENT

SYSTEM
Project report submitted
in partial fulfillment of the requirement for the degree of

Bachelor of Technology

By

B.SAI MEGHANA (17UECS0134)

A.S.BINDHU MADHAVI (17UECS0025)
JAYANTI SAWAIYAN (17UECS0271)

Under the guidance of Reshma.K

SCHOOL OF COMPUTING

DEPARTMENT OF COMPUTER SCIENCE & ENGINEERING

VEL TECH RANGARAJAN DR. SAGUNTHALA R & D INSTITUTE

OF SCIENCE AND TECHNOLOGY
CHENNAI 600 062

OCTOBER 2020
 CERTIFICATE

It is certified that the work contained in the project report titled

“EMPLOYEE DATABASE AND PAYROLL MANAGEMENT
SYSTEM” by “B.Sai Meghana, A.S.Bindhu Madhavi and Jayanti
Sawaiyan” has been carried out under our supervision and that this
work has not been submitted elsewhere for a degree.

Signature of Supervisor:
Ms.Reshma.K
Computer Science and Engineering.
Vel Tech Rangarajan Dr.sagunthala
R&D Institue of Science and
Technology.
October,2020.
 Declaration

I declare that this written submission represents my ideas in my own words and
where others' ideas or words have been included, I have adequately cited and
referenced the original sources. I also declare that I have adhered to all
principles of academic honesty and integrity and have not misrepresented or
fabricated or falsified any idea/data/fact/source in my submission. I understand
that any violation of the above will be cause for disciplinary action by the
Institute and can also evoke penal action from the sources which have thus not
been properly cited or from whom proper permission has not been taken when
needed.

(Signature)

(B.SAI MEGHANA)

(17UECS0134)

Date: _____________

(Signature)

(A.S.BINDHU MADHAVI)

(17UECS0025)

Date: _____________

(Signature)

(JAYANTI SAWAIYAN)

(17UECS0271)

Date: ____________
 Approval Sheet

This project report entitled “EMPLOYEE DATA BASE AND PAYROLL

MANAGEMENT SYSTEM” by “B.SAI MEGHANA (17UECS0134),
A.S.BINDHU MADHAVI (17UECS0025) and JAYANTI SAWAIYAN
(17UECS0271)” is approved for the degree of “Bachelor of Technology”.

Examiners

Supervisor

Ms.Reshma. K
Asst.Proffesor
Department of CSE
Vel Tech Rangarajan Dr.Sagunthala
R&D Institute of science and Technology
Avadi, Chennai-600062

Head & Dean, SOC

Dr.Srinivasa Rao,M.Tech.,Ph.D.,
Professor
Department of CSE,
Vel Tech Rangarajan Dr.Sagunthala
R&D Institute of science and Technology
Avadi, Chennai-600062

Date:
Place:
 ABSTRACT
“Employee Database and Payroll Management System” is designed to
make the existing manual system automatic with the help of computerized
equipment and full-edged computer software, fulfilling their requirements,
so that their valuable data and information can be stored for a longer period
with easy access and manipulation of the same. The required software is
easily available and easy to work with. This web application can maintain
and view computerized records without getting redundant entries. The
project describes how to manage user data for good performance and
provide better services for the client.
 LIST OF FIGURES
1. 1 Symbols Used in DFD……………….……….………….07
1.2 Context Level DFD……………….……….……………..08
1.3 DFD At 0 Level………………….……….………………08
1.4 DFD At 1.1 Level …………….……...………………….09
1.5 DFD At 1.2 Level …………….……...………………….09
1.6 DFD At 1.3 Level…………….……….………………….09
2. ER Diagram………………….…………………………….10
3.1 Login Page……………….………………………………15
3.2 Department Form 1…….……………………………...…16
3.3 Department Form 1…….………………………………...16
3.4 Exit Form………….……………………………………..17
3.5 Department Record Adding Page………………………..18
3.5 Designation Form………………………………………..18
3.7 Designation Exit Form…………………………………..19
3.8 Employee Personal Form………………………………..20
3.9 Employee Official Form…………...…………………....20
3.10 Search Form....................................................................21
3.11 Data Base Connection 1………………………………..23
3.12 Data Base Connection 2………………………………..24
3.13 Data Base Connection 1………………………………..24
 TABLE OF CONTENTS
Abstract 1
List Of Figures 1
1.Introduction 2
1.1. Purpose 2
1.2. System overview 3
1.3. Problem statement 3
1.4. DFD modelling of problem 6
1.5. Goal & Vision 12
2. Requirement Specification 13
2.1 Dependencies 13
2.2 Performance Requirement 14
3.Design 15
3.1 Data Base Design 18
4.Coding 20
5.Testing 31
5.1 Testing Technique Used 31
5.2 Features 32
5.3 Future Scope 32
6.Conclusion 34
7.Reference 35
 CHAPTER 1

INTRODUCTION

The proposed project “Employee Database and Payroll

Management System” has been developed to overcome the
problems faced in the practicing of manual system. This software
is built to eliminate and in some cases reduce the hardships faced
by the existing system. Moreover this system is designed for
particular need of the company to carry out its operations in a
smooth and effective manner. This web application is reduced as
much as possible to avoid errors while entering data. It also
Provides error message while entering invalid data. It is user-
friendly as no formal knowledge is required to use the system.
Human resource challenges are faced by every organization which
has to be overcome by the organization. Every organization has
different employee and payroll management needs. Therefore I
have design exclusive Employee and payroll Management System
that are adapted to the organization’s Managerial Requirements.

1.1 PURPOSE

The purpose of this document is to describe the functionality and

specifications of the design of a web application for Managing
Employees and their payroll. The expected audiences of this
document are the developers and the admin of the web application.
Now with the help of this system the admin has the information on
his finger tips and can easily prepare a good record based on their
requirements. Finally, we can say that this system will not only
automate the process but save the valuable time of the manager or
the admin, which can be well utilized buy his institute. This will be
an additional advantage and management of power based on their
free time from his normal duty.

1.2 SYSTEM OVERVIEW

The main concept we cover in our system is manage employee
detail, manage leave, Generate monthly salary, Extra Allowance
and Deduction. Admin is a responsible for operate whole system.
Admin has rights to Add new Employee, Each employee has a
unique username and password to login in to system. After login in
to system all employee can apply for a leave with valid reason. The
admin can check leave and he can approve and reject employee
leave. According to approve leave the leave deduction will be
deducted from salary.

At the time of generate salary we can manually set Travel

Allowance, Medical Allowance, Washing Allowance and Calculate
HR and DA. Admin can generate and view Employee Report,
Leave Report, month wise salary report, year wise salary report,
Employee wise salary report. We have use crystal report for
generate salary slip of employee.

1.3 PROBLEM STATEMENT

Our task is the creation of a new payroll system. The old system is
outdated and no longer adequately manages the payroll process and
the entry of employee time card information. Therefore, manual
Intervention is required to process the payroll. In addition to the
preexisting category of salaried employee, which the current
payroll process does support, our organization now accommodates
two new types of employees: those employees working on
commission, and those employees working on an hourly basis. The
current payroll process doesn't support these two new employee
types, which are described in detail later in this problem statement.
In addition to accommodating all employee types, as well as
ensuring that our system can accommodate newly created
categories of employees in the future, the system must also allow
each of these employees to enter his or her time information via a
corporate intranet using a standard Web browser. Because
Employee can manage only their individual time card information,
a user ID and password is required of each employee prior to
gaining access to this section of the corporate intranet.
The payroll process can process only "signed" time cards, which
are those time cards that the employee has identified as accurate.
Overall, the system will store information about the approximately
2,000 company employees. This data will be stored in the Oracle
payroll database. The payroll process must run on the fifteenth and
Last day of each month at 12:00 a.m. All paychecks must be
accurately calculated and deposited into one or more bank accounts
of the employees' choosing. Employees also should be able to
change personal information, such as names, addresses, and
passwords. Eventually, the system must enable employees to
maintain their direct deposit information via the system as well.
However, this feature is beyond the scope of the initial release.
A human resources representative must be able to initiate the
payroll process on demand based on a selected list of employees.
When doing so, the system should cycle through the list of selected
Employees, running payroll only for those employees. This process
typically will be done by a human resources representative during
normal business hours. As stated earlier, our system must be able
to track information and calculate salaries for the following
Three types of employees:
1. Salaried: These employees are paid a flat salary. However,
they're still required to submit time cards that include the dates
worked and the number of hours worked on those dates.
2. Hourly: These employees are paid based on their hourly rate.
Employees working more than a standard 40-hour work week are
paid 1.5 times their hourly rate.
3. Commission: These employees are paid a commission based on
their total sales. The commission rates for commissioned
employees are 10, 20, or 25 percent. In addition to the percentage
rate, these employees also may receive a base salary. The system
also must allow employees to query the system. Standard queries
will include the ability to view number of hours worked for a
selected pay period and remaining and used vacation time. All
employee information is maintained by a human resources
administrator. The administrator must be able to initiate a payroll
process in a fashion similar to that of the human resources
representative. In addition, the administrator also will be able to
add new employees, remove employees, and change personal
information about employees, including an employee's category
type and an employee's password. The administrator will have
additional reporting capabilities beyond that of an employee,
Which include various administrative reports yet to be identified.

1.4 DFD MODELLING OF PROBLEM

DFD:

DFD provides a logical method of the system and shows the flow
of data and the flow of logic involved.

SYMBOLS USED IN DFD:

Four symbols are used in drawing data flow diagrams,

These are:
Fig 1.1 Symbols used in DFD
CONTEXT LEVEL DFD:

The CFD shows the external entity action on the software is shown
here in CFD as a single process.

Fig 1.2 CFD

DFD AT 0 LEVEL:

Fig 1.3 DFD at Level 0

DFD AT 1.1 LEVEL:

 Fig 1.4 DFD at Level 1.1

DFD AT 1.2 LEVEL:

Fig 1.5 DFD at level 1.2

DFD AT 1.3 LEVEL:

Fig 1.6 DFD at Level 1.3

ER DIAGRAM:

ER diagram allows us to sketch database design. ERD is a

graphical tool for modeling data. It is a graphical representation of
the logical structure of the database.

Fig 2. ER Diagram

1.5 GOAL & VISION

Compensation is one of the most important motivators for an
employee. A company that pays its employees the correct wage on
time engenders loyalty from them, because they know they can
count on their firm to deliver as promised. Moreover, it makes the
financial operations of the organization more efficient. Thus, the
goals of a payroll system are to simplify this administrative duty to
free up company resources for more important tasks, like growing
the business.

Cost-Saving Efficiency

The first and most important goal of any payroll system is

efficiency. Efficient payroll systems save time and money by
ensuring that paychecks go out on time in the correct amounts each
pay period. Once the system is set up, many parts can be
automated, to reduce errors and delays. Moreover, such systems
record data, so if there is a discrepancy, it is quick and easy to
pinpoint.

Compliance

Payroll systems are also crucial for companies to ensure that they
are following laws and provide proof of compliance. For example,
at the end of the year a company will have to include payroll costs
in its taxes, and prove that it has made all the proper deductions
from employees' pay. Moreover, in the U.S. where health insurance
is often tied to employment, payroll systems can prove that an
employee has been contributing to his or her health plan and is
eligible for coverage.
Growth

Helping a company grow is an indirect, but nonetheless important

goal of payroll. Payroll systems take care of what is basically an
administrative chore. By doing this cheaply and effectively, it frees
up entrepreneurs and other employees to focus on growing a
business' footprint and profitability. It gives them the freedom and
peace of mind to focus on such big-picture planning, and if a
problem does arise, the systematic record-keeping allows it to be
resolved quickly without taking up too many resources.

Running Payroll Systems

In large companies, a number of workers will likely work in the

payroll department keeping in close contact with human resources
and the accounting department simply because of the volume and
complexity of the work. In medium and small businesses, a payroll
department may simply be a few workers or a single person, who
may also have other duties as well. Many bookkeeping services
also cater to small businesses and entrepreneurs who don't have the
time or man power to run their own payroll system.
 CHAPTER 2

REQUIREMENTS SPECIFICATION

Specific Requirements:
External interface requirements
User interfaces
The software provides good graphical interface to the user.
Hardware interfaces
Mouse
Keyboard
Printer
Hard disk- Ram with memory 256 MB or more
Software interfaces
Operating system: Windows XP/Vista or any main stream OS

Functional requirements
Languages: HTML, PHP, JavaScript
RDBMS: Online MySQL
Web Server: WAMP server
Development Platform: Adobe Dreamweaver

TOOLS USED:
Editor Used: Dreamweaver for PHP, WAMP, Server for MySQL
Operating System: Windows10

HARDWARE USED:
Processor: Intel Core i3
RAM: 2GB
Hard Disk: 1TB
2.1 DEPENDENCIES
All necessary hardware and software are available for
implementing and use of the tool. The proposed system would be
designed, developed and implemented based on the software
requirements specifications document. End users should have basic
knowledge of computer and we also assure that the users will be
given software training documentation and reference material.
The system is not required to save generated reports.

2.2 PERFORMANCE REQUIREMENTS

1) The overall system should be fast and error free.
2) It should have built in error checking and correction facilities.
3) The system should be able to handle large amount of data
comfortably.
 CHAPTER 3
DESIGN

Fig 3.1 Login page

This is login page in which User selects his category (Admin,
Account manager etc.).

Fig 3.2 Department form 1

In this Department form user has to enter their department code
and department name. This will have two options like add and
close.
 Fig 3.3 Department form 2
In the above form if a new user tries to add again then this pop will
appear showing message “RECORD ADDED”.

Fig 3.4 Exit form

After getting added we can exit from the application by simply
clicking on close button which displays exit page.
 Fig 3.5 Department record adding page
We can check whether a record was added or not. This was
verified by performing SQL queries on our database.

Fig 3.6 Designation form

This is designation form in which we can add designation Code
and designation Name along with the department code.

Fig 3.7 Designation exit form

Once we are done with filling form we can exit from the form by
hitting yes button on this page.
 Fig 3.8 Employee personal form
This is the employee personal registration form which will have
many fields like name, qualification, DOB etc.

Fig 3.9 Employee official form

This is the template of an Employee’s official form which requires
sensible information like PF_Account.No and ESI_Account.No
etc.

Fig 3.10 Search form

In this page we can search for a particular employee by entering
Empid in the provided text box and after clicking show button if
the record exists it will be displayed.

3.1 DATABASE DESIGN

Database design involves the production of a model of the data to
be stored in the database. A data model is a diagram of the
database design that documents and communicates how the
database is structured. The design process is divided into three
main stages conceptual, logical and physical database design. The
purpose of the conceptual database design is to decompose the
design into more manageable tasks, by examining user
perspectives of the system. That is, local conceptual data models
are created that are a complete and accurate representation of the
enterprise as seen by different users. Each local conceptual data
model is made up of entity types, relationship types, attributes and
their domains, primary keys and integrity constraints. For each user
view identified a local conceptual data model would be built. In
building the conceptual data model, a data dictionary is built to
identify the major entities in the system. An entity relationship
(ER) diagram is used to visualize the system and represent the
user’s requirements. The ER diagram is used to represent entities
and how they relate to one another. The ER diagram also shows the
relationships between the entities, their occurrence (multiplicities)
and attributes.
Data dictionary
Entity Name Description
Department
Different disciplines from The People’s University of Bangladesh
(PUB)Employee All employees of PUB Designation Designations
of the employees Pay Head The categories under which the
employees are paid Deduction Head The categories under which
the salary of the employees are deducted Overload Payment Extra
payments to the employees for engaging with extra hours of duty
Advance Payment which is paid to the employees in advance
Conveyance Allowance Payment which is paid for transport cost
by the employees Festival Allowance Bonus payment which is
paid to the employees for festival Payroll Monthly payment and
increment details of the employees
Fig 3.11 Database connection 1

Fig 3.12 Database connection 2

 Fig 3.13 Database connection 3

CHAPTER 4

CODING
Index.php:

<?php
session_start();
?>
<!DOCTYPE html>
<html>
<head>
<meta name="viewport" content="width=device-width, initial-
scale=1">
<style>
body {font-family: Arial, Helvetica, sans-serif;}
/* Full-width input fields */
input[type=text], input[type=password] {
width: 100%;
padding: 12px 20px;
margin: 8px 0;
display: inline-block;
border: 1px solid #ccc;
box-sizing: border-box;
}
/* Set a style for all buttons */
button {
background-color: #4CAF50;
color: white;
padding: 14px 20px;
margin: 8px 0;
border: none;
cursor: pointer;
width: 100%;
}
button:hover {
opacity: 0.8;
}
/* Extra styles for the cancel button */
.cancelbtn {
width: auto;
padding: 10px 18px;
background-color: #f44336;
}
/* Center the image and position the close button */
.imgcontainer {
text-align: center;
margin: 24px 0 12px 0;
 position: relative;
}
img.avatar {
width: 40%;
border-radius: 50%;
}
.container {
padding: 16px;
}
span.psw {
float: right;
padding-top: 16px;
}
/* The Modal (background) */
.modal {
display: none; /* Hidden by default */
position: fixed; /* Stay in place */
z-index: 1; /* Sit on top */
left: 0;
top: 0;
width: 100%; /* Full width */
height: 100%; /* Full height */
overflow: auto; /* Enable scroll if needed */
background-color: rgb(0,0,0); /* Fallback color */
background-color: rgba(0,0,0,0.4); /* Black w/ opacity */
padding-top: 60px;
}
/* Modal Content/Box */
.modal-content {
background-color: #fefefe;
margin: 2% auto 10% auto; /* 5% from the top, 15% from the
bottom and centered */
border: 1px solid #888;
 width: 40%; /* Could be more or less, depending on screen size */
}
/* The Close Button (x) */
.close {
position: absolute;
right: 25px;
top: 0;
color: #000;
font-size: 35px;
font-weight: bold;
}
.close:hover,
.close:focus {
color: red;
cursor: pointer;
}
/* Add Zoom Animation */
.animate {
-webkit-animation: animatezoom 0.6s;
animation: animatezoom 0.6s
}
@-webkit-keyframes animatezoom {
from {-webkit-transform: scale(0)}
to {-webkit-transform: scale(1)}
}
@keyframes animatezoom {
from {transform: scale(0)}
to {transform: scale(1)}
}
/* Change styles for span and cancel button on extra small screens
*/
@media screen and (max-width: 300px) {
span.psw {
 display: block;
float: none;
}
.cancelbtn {
width: 100%;
}
}
.button {
background-color: #000000;
color: #FFFFFF;
padding: 10px;
border-radius: 10px;
-moz-border-radius: 10px;
-webkit-border-radius: 10px;
margin:10px
}
.small-btn {
width: 50px;
height: 25px;
}
.medium-btn {
width: 70px;
height: 30px;
}
.big-btn {
width: 180px;
height: 40px;
}
</style>
<?php
include("header12.php");
include("dbconnect.php");
extract($_POST);
if(isset($submit))
{
$rs=mysql_query("select * from users where
username='$username' and password= MD5('$password')");
if(mysql_num_rows($rs)<1)
{
$found="N";
}
else
{
$_SESSION[login]=$username;
header("Location: welcome.php");
}
}
?>
</head>
<body>
<center>
</br></br></br>
<h1><strong>MY EMPLOYEE MANAGER</strong></h1>
<br>
<h1><STRONG>ADMINISTRATOR &nbsp;
LOGIN</STRONG></h1>
<button
onclick="document.getElementById('id01').style.display='block'"
class="button big-btn" style="width:10%; font-size :
20px;"><strong>Login</strong></button>
</center>
<div id="id01" class="modal">
<form class="modal-content animate" name="form1"
method="post" action="">
<div class="imgcontainer">
<span
onclick="document.getElementById('id01').style.display='none'"
class="close" title="Close Modal">&times;</span>
<img src="admin.png" alt="Avatar" class="avatar">
</div>
<div class="container">
<label for="uname"><b>Username</b></label>
<input type="text" placeholder="Enter Username"
name="username" id="username" required>
<label for="psw"><b>Password</b></label>
<input type="password" placeholder="Enter Password"
name="password" id="password" required>
<button type="submit" name="submit" id="submit"
value="Login">Login</button>
<!-- <label>
<input type="checkbox" checked="checked" name="remember">
Remember me
</label>-->
</div>
<div class="container" style="background-color:#f1f1f1">
<button type="button"
onclick="document.getElementById('id01').style.display='none'"
class="cancelbtn">Cancel</button>
<!--
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&nbsp;&nbsp;&nbsp; <button
onclick="document.getElementById('id02').style.display='block'"
class="button big-btn" style="width:50%; font-size :
20px;"><strong>Forget Password</strong></button> -->
</div>
</form>
</div>
<div id="id02" class="modal">
<form class="modal-content animate" method="post" action="">
<div class="imgcontainer">
<span
onclick="document.getElementById('id02').style.display='none'"
class="close" title="Close Modal">&times;</span>
</div>
<div class="container">
<label for="uname"><b>Enter Your Email id</b></label>
<input type="text" placeholder="Enter Username"
name="username" id="username" required>
<input type="submit" name="submi" value="Submit">
</div>
</form>
</div>
<script>
// Get the modal
var modal = document.getElementById('id01');
var modal = document.getElementById('id02');
// When the user clicks anywhere outside of the modal, close it
window.onclick = function(event) {
if (event.target == modal) {
modal.style.display = "none";
}
}
</script>
Welcome.php
<?php
session_start();
include "header.php";
?>
<!doctype html>
<html>
<head>
<style>
.button {
background-color: #000000;
color: #FFFFFF;
padding: 10px;
border-radius: 10px;
-moz-border-radius: 10px;
-webkit-border-radius: 10px;
margin:10px
}
.small-btn {
width: 50px;
height: 25px;
}
.medium-btn {
width: 70px;
height: 30px;
}
.big-btn {
width: 250px;
height: 40px;
}
</style>
<meta charset="utf-8">
<title>Untitled Document</title>
</head>
<body class="bg">
<center>
<br>
<form action="emp_master.php" align= "center">
<!--<div class="button big-btn">This is a big button</div>-->
<button type="submit" class="button big-btn"
value="emp_master" name="add" ><font size="3"><strong>Add
New
Employee</strong></font></button>
</form>
<br>
<form action="dep_master.php">
<button type="submit" class="button big-btn" value=""
name="add" ><font size="3"><strong>Add New
Department</strong></font></button>
</form>
<br>
<form action="grad_master.php">
<button type="submit" class="button big-btn" value="#"
name="add" ><font size="3"><strong>Add New
Grade</strong></font></button>
</form>
<br>
<form action="emp_grad_detail.php">
<button type="submit" class="button big-btn" value="#"
name="add" ><font size="3"><strong>Employee Grade
Details</strong></font></button>
</form>
<br>
<form action="salary_detail.php">
<button type="submit" class="button big-btn" value="#"
name="add" ><font size="3"><strong>Prepare Monthly
Salary</strong></font></button>
</form>
<br>
<form action="report.php">
<button type="submit" class="button big-btn" value="#"
name="add" ><font size="3"><strong>Generate
Report</strong></font></button>
</form>
</table>
</form>
</center>
</body>
</html>
emp_master.php
<?php
session_start();
include_once "header.php";
?>
<?php
include_once 'dbconnnect.php';
if(isset($_POST['submit']))
{
$file = rand(1000,100000)."-".$_FILES['file']['name'];
$file_loc = $_FILES['file']['tmp_name'];
$file_size = $_FILES['file']['size'];
//echo $file_size;
$file_type = $_FILES['file']['type']
$folder="uploads/";
// new file size in KB
$new_size = $file_size/1024;
echo $new_size;
// new file size in KB
// make file name in lower case
$new_file_name = strtolower($file);
// make file name in lower case
$final_file=str_replace(' ','-',$new_file_name);
if(move_uploaded_file($file_loc,$folder.$final_file))
{
$sql="INSERT INTO tbl_uploads(file,type,size)
VALUES('$final_file','$file_type','$new_size')";
$_SESSION['final_file']=$final_file;
mysqli_query($connection,$sql);
?>
<script>
alert('successfully uploaded');
window.location.href='emp_master.php?success';
</script>
<?php
}
else
{
?>
 CHAPTER 5

TESTING
Software testing is a critical phase of software quality assurance. It
Indicates the ultimate review of specification, design and code
generation. Once source code has been generated, software must be
tested to uncover and correct maximum possible errors, before
being delivered. Testing emphasizes on a set of methods for the
creation of test cases that fulfill overall testing objectives.
The primary objectives of software testing are as follows:
1. Testing is a process of executing a program to find an error in it.
2. A good test case should have a high probability of finding an as
yet undiscovered error.
3. A test case will be considered successful if it uncovers an as-yet-
Undiscovered error.

5.1 TESTING TECHNIQUE USED

1. UNIT TESTING:

Unit testing aims the verification effort on the smallest unit of soft-
ware design i.e., a software component or module. It uses
procedural design as a guide to test major control paths and
uncover errors within the module boundary. It is a White box
oriented and the step can be conducted in parallel for multiple
components. Unit testing is a dynamic method for verification,
where the program is actually compiled and executed. It is one of
the most widely used methods, and the coding phase is sometimes
called “coding and unit testing phase”. The goal of unit testing is to
test modules or “units”, not the whole software system. Unit testing
is most often done by the programmer himself/herself. The goal of
Unit testing is to isolate each part of the program and show that the
individual parts are correct. A unit test provides a strict, written
contract that the piece of code must satisfy. As a result, it affords
several benefits.
2. INTEGRATION TESTING:

Integration testing is a phase of software testing in which

individual software modules are combined and tested as a group. It
follows snit testing and precedes system testing. The major
objective of integration testing is to tackle the problem of
integration i.e. putting all the modules together. One module can
have an inadvertent, adverse effect on another, sub functions, when
combined, may not be magnified to unacceptable levels; global
data structure can cause problems and to truncate this list of
problems we use integration testing. Integration testing strategy
used is Bottom-Up Integration Testing. In it all the bottom or low
level modules, procedures or functions are integrated and then
tested. After the integration testing of lower level integration
modules, the next level of modules will be formed and can
be used for integration testing. This approach is helpful only when
all or most of the modules of the same development level are
ready. This method helps to determine the levels of software
development and makes easier to report testing progress in the
form of a percentage.

3. VALIDATION TESTING:

At the climax of integration testing, software is developed as a

package having all the errors uncovered and corrected. At this
time, a final series of software test May being. It is called
validation testing. Validation succeeds when software function in a
reasonably executable manner. Validation attempts to uncover
errors, but the emphasis is on the requirements level i.e. the things
that will be immediately apparent to the customer.

5.2 FEATURES

Features of Employee database and payroll Management system:

Easy to use.
It is completely secure.
It is completely controlled by admin.
This system is easily compatible with most of the web browsers.
It is very interactive and saves time.
Reduces paper works.
Calculations are automated so it is highly accurate.
Admin can view all the records whenever necessary with ease.

5.3 Future scope:

The option to print the records In future. The system can be
developed in such a way that its existing features can be modified
to better versions. This system is very flexible so that the
maintenance and further amendments based on the changing
environment and requirements can be made easily. Any changes
that may lead to system failures are prevented with security
measures. The project will support a multi-user environment,
which is more than one user can access simultaneously. It can be
further developed to include more operations and analysis, as
changes are required in the system to adapt to the external
developments. Further enhancements can be made to the system at
any later point in time. Coding procedures can be modified
according to the needs of the user. The system code is also well
designed that it will form the basis for further enhancement and
also new operations can be included in the system. The reports can
be represented in all necessary protection. Added options can be
designed in reports.

CHAPTER 6

Conclusion
This project is built keeping in mind that it is to be used by only
one user that is the admin. It is built for use in small scale
organization where the number of employees is limited. According
to the requested requirement the admin can add, manipulate,
update and delete all employee data in his organization. The admin
can add new departments and delete them. The Admin can also add
predefined pay grades for the employees. The required records can
be easily viewed by the admin anytime time he wants in an instant.
The payment of the employee is based on monthly basis.
Numerous validations implemented would enable the admin to
enter accurate data. The main objective of this framework is to
save time, make the system cost effective and management records
efficiently.
 CHAPTER 7

REFERENCES:
[1].http//www.ijetae.com/files/Volume4Issue4/IJETAE_0414_140.
[2]. Schmitt, Bob (10 October 2014). & quot; Collection
Management Systems&quot;. Retrieved 15 November 2015.
[3]. Carpinone, Elana C. (May 2010), Museum Collection
Management systems: One Size Does NOT Fit All, p. 26.Retrieved
5 December 2015.
[4]. http://www.tangedco.gov.in/linkpdf/Agri%20For m.pdf:The
pdf is a form to apply for agricultural loan. This gives us the idea
about attributes required in database“Agricultural loans”.
[5]. http://ceoharyana.nic.in/?module=pages&amp;pageid=42: The
link tells us about the requirements for Voter ID Generation. This
information can be used to maintain the database.
[6]. A Java API for the description of large complex networks
under the object-oriented paradigm A. Ni~no1;y, C.Mu~noz-
Caro1, S. Reyes1 and M. Castillo1 1 SciCom Research Group.
Escuela Superior de Inform_atica de Ciudad Real,Universidad de
Castilla-La Mancha. Paseo de la Universidad 4. 13004 Ciudad
Real, Spain.
[7]. Compiling and Optimizing Java 8 Programs for GPUExecution
Kazuaki Ishizaki IBM Research– Tokyo,Akihiro Hayashi Rice
University ,Gita Koblents IBM Canada, Vivek Sarkar Rice
University.