ACKNOWLEDGEMENT

On presenting the database management system laboratory mini project report on

“ EMPLOYEE MANAGEMENT SYSTEM”, we feel great to express my
humble feelings of thanks to all of who have helped directly or indirectly in the successful
completion of project work

we would like to thank our respected guide Mr Yathish Aradhya B C and Mr Harish
B M, assistance professor, department of CSE, who has helped us a lot in completing
this task, for his or her continuous encouragement and guidance throughout the project
work.

We would like to thank Mr Santhosh S, associate professor and HOD, department of

CSE , KIT Tiptur and Dr, G D Gurumurthy, the principal KIT Tiptur, for all their
support and encouragement.

We are grateful to department of Computer Science and Engineering and our

institution Kalpataru Institute of Technology for imparting us the knowledge which we
could do our best.

Finally, we also would like to thank the whole teaching and non-teaching staff
of computer science and engineering department.

Thanking You All….!

NAME USN

SANJAY M N 1KI18CS069
SANJAY MURTHY 1KI18CS069

I
 ABSTRACT
Employee Management System is a distributed application, developed to maintain the details of
employees working in any organization. It maintains the information about the personal details of
their employees, also the details about the payroll system which enable to generate the payslip. The
application is actually a suite of applications developed using Java.

It is simple to understand and can be used by anyone who is not even familiar with simple
employees’ system. It is user friendly and just asks the user to follow step by step operations by
giving him few options. It is fast and can perform many operations of a company.

This software package has been developed using the powerful coding tools of JAVA at Front End
and Microsoft sql Server at Back End. The software is very user friendly. The package contains
different modules like Employee details. This version of the software has multi-user approach. For
further enhancement or development of the package, user’s feedback will be considered.
 TABLE OF CONTENTS
SL.NO CHAPTER P.NO

1. “EMPLOYEE MANAGEMENT SYSTEM”

............................................................................................. 1 2. INTRODUCTION
................................................................................................................................ 8 Scope
....................................................................................................................................................... 8
Significance of the Study .........................................................................................................................
8 3. SYSTEM ANALYSIS
............................................................................................................................. 9
Objectives of the proposed system ........................................................................................................ 9
4. HARDWARE AND SOFTWARE REQUIREMENTS
.............................................................................. 10 SYSTEM SPECIFICATIONS
...................................................................................................................... 10 HARDWARE
REQUIREMENTS ................................................................................................................ 10
SOFTWARE REQUIREMENTS
................................................................................................................. 10 5. SYSTEM DESIGN
.............................................................................................................................. 11 DATABASE
DESIGN ................................................................................................................................ 11
ERDiagram ........................................................................................................................................... 13
Data flow -Diagram ...............................................................................................................................
15 6. IMPLEMENTATION MODULES
........................................................................................................ 16 SYSTEM
IMPLEMENTATIONS ................................................................................................................ 16 7.
SOFTWARE TESTING ....................................................................................................................... 26
SYSTEM TESTING
................................................................................................................................... 26
UNIT TESTING ................................................................................................................................
26 INTEGRATION TESTING
................................................................................................................. 27
VALIDATION TESTING
.................................................................................................................... 27
TEST CASES ............................................................................................................................................
27
Test case 1 ..................................................................................................................................... 28
Test case 2 ..................................................................................................................................... 28
Test case 3 ..................................................................................................................................... 29
Test case 4 ..................................................................................................................................... 29
Test case 5 ..................................................................................................................................... 29
8. SCREENSHOTS AND OUTPUT ..........................................................................................................
30
 9. CONCLUSION AND FUTURE ENHANCEMENT
................................................................................. 34
CONCLUSION .........................................................................................................................................
34 FUTURE ENHANCEMENT.
...................................................................................................................... 34 BIBLIOGRAPHY
...................................................................................................................................... 35
 EMPLOYEE MANAGEMENT SYSTEM

CHAPTER 1
INTRODUCTION
Employee Management system is an application that enables users to create and store
Employee Records. The application also provides facilities of a payroll system which
enables user to generate Pay lips too. This application is helpful to department of the
organization which maintains data of employees related to an organization.
Java is a platform independent language. Its created applications can be used on a
standalone machine as well as on distributed network. More over applications
developed in java can be extended to Internet based applications.
Thus java was chosen as background to design this application.

Scope

• Provide employees with a better understanding of their role and responsibilities.

• Increase confidence through recognizing strengths while identifying training
needs to improve weaknesses.
• Improve working relationships and communication between supervisors and
subordinates.
• Increase commitment to organizational goals; develop employees into future
supervisors.
• Assist in personnel decisions such as promotions or allocating rewards.

Significance of the Study

One of its greatest benefits is keeping your team motivated to do their best, and
having an HR management system in place helps achieve that. Employee
management software can be categorized into different groups based on the area of
your business they are specifically designed for.
CHAPTER 2
SYSTEM ANALYSIS

Dept.of.CSE,KIT 8
 EMPLOYEE MANAGEMENT SYSTEM
Page

System analysis is the examination of the business problem that organizations plan to
solve with an information system. The main purpose of the systems analysis stage is to
gather information about the existing system in order to determine the requirements for
an enhanced system or a new system.

Proposed system
The world is advancing day by day new technologies come and go, many new methods
are been introduced almost daily, therefore, the demand of the new systems have been
increased in every organization old system have been replaced by new systems, the
question is why? Its because every organization demands excellent quality work more
profit to be earned in short span of time, to gain as much market trust as they can, and
not to forget as quick they can so they can compete with other organizations. New
systems should be i. User friendly ii. More efficient iii. They should provide security
iv.
Fast
As these four are mentioned, my idea will be based upon these.

Objectives of the proposed system

In this world of growing technologies everything has been computerized. With large
number of work opportunities the Human workforce has increased. Thus there is a need
of a system which can handle the data of such a large number of Employees in an
organization. This project simplifies the task of maintain records because of its user
friendly nature

CHAPTER 3
HARDWARE AND SOFTWARE REQUIREMENTS

Page

Dept.of.CSE,KIT 9
 EMPLOYEE MANAGEMENT SYSTEM
SYSTEM SPECIFICATIONS
Since the Administrator and the user are the main target group of our software, we will
only concern about some important functions for the admin and the user.

HARDWARE REQUIREMENTS

1. Processor: Intel Core i5

2. RAM: 4GB or higher

3. Input Device: Keyboard, Mouse

SOFTWARE REQUIREMENTS
1. Operating System: Windows 10

2. Front End: HTML and CSS

3. Back End: MySQL and PHP

4. Server: Apache

5. Tool: XAMPP

CHAPTER 4
SYSTEM DESIGN
System design is a process of planning a new business system or replacing an
existing system by defining its components or modules to satisfy the specific
requirements. Before planning, you need to understand the old system thoroughly and
determine how computers can best be used in order to operate efficiently. System
design is a very broad topic. Even a software engineer with many years of working
experience at a top IT company may not be an expert on system design. If you want to
become an expert, you need to read many books, articles, and solve real large scale
system design problems.
Dept.of.CSE,KIT Page 10
 EMPLOYEE MANAGEMENT SYSTEM
This repository only teaches you how to handle the system design interview with a
systematic approach in a short time. You can dive into each topic if you have time. Of
course, welcome to add your thoughts.

DATABASE DESIGN
Database design is the organization of data according to the database module that
designer determines what data must be stored and how the data elements interrelate.
With this information, they can begin to fit the data to the database module. Database
management system manages the data accordingly.

Database design involves classifying data and identifying interrelationships. This

theoretical representation of data is called an ontology. The ontology is the theory
behind database’s design.

Dept.of.CSE,KIT Page 11
 EMPLOYEE MANAGEMENT SYSTEM

4.1.1 Schema -Diagram

Dept.of.CSE,KIT Page 12
 EMPLOYEE MANAGEMENT SYSTEM
ER-Diagram

ENTITY-RELATIONAL DIAGRAM
Entity relationship model is a popular high level conceptual model. The ER model
describes data as entries, relationship and attributes.
Entities and attributes
The basic object that the ER model represent is an entity, which is a thing in the real
world with an independent existence. An entity may be an object with physical
existence, like a car or may be an object with conceptual existence, like company, a job
etc.
Each entity has a particular property called attribute that describes it.

Several different types of attributes in ER model:

Simple verses composite.
Single verses multivalued.
Stores verses derived

Entity types, value sets and key attributes:

A database usually contains group of entities that are similar. An entity type defines a
set of entities that have same set of attributes. An entity type is represented in ER
diagram as a rectangular box enclosing the entity type name.
An important constituent on the entities is the key or uniqueness. An entity type usually
has an attribute whose values are distinct for each individual entity. Such an attribute is
called as key attribute and its value can be used to identify each entity uniquely. In ER
diagram notation, each key attribute Hs its name underlined inside oval. Each simple
attribute of an entity type is associated with a value set, which specifies the set of value
that may be assigned to that attribute for undivided entity.

Dept.of.CSE,KIT Page 13
 EMPLOYEE MANAGEMENT SYSTEM

ER-Diagram

Dept.of.CSE,KIT Page 14
 EMPLOYEE MANAGEMENT SYSTEM
Data flow -Diagram
The data flow diagram shows the flow of data between different process in business. It is a simple
intuitive method for describing business process without focusing in the detail of computer. The data
flow diagram basically contains the four primary symbols. The process that is any function being
performed which is generally shown by oval in the diagram. The data flow is shown by the element
movement. It is generally represented by the arrow. The data store is the place where the data is being
stored is generally represented by the two parallel lines. Then there is something called as the external
entity which is given by the rectangular box.

4.1.3 Data flow -Diagram

IMPLEMENTATION MODULES
SYSTEM IMPLEMENTATIONS
System implementation is the process of bringing the developed system and
turning it over to user. It can be the most crucial stage in achieving a successful new
system and in giving the users confidence that the new system will work and be
effective.

Dept.of.CSE,KIT Page 15
 EMPLOYEE MANAGEMENT SYSTEM
For successful implementations of the system, implementation plan is necessary. Its
major elements include test plan, training plans, an equipment installation plan and a
conversion plan. The test plan provides for the preparations of the test ad for testing the
system in a planned, structured manner. Training plan is necessary to ensure that all
people who are associated with the computer related information system have the
necessary knowledge and skills. The important activities are preparations ,equipment
installation and hardware –software checkout.
Conversion is the process if initiating and performing all the physical operations
that result directly in the turnover of the new system to the user. There are two parts of
conversion .The conversion plan is implemented throughout the development phase
into the operational phase. The conversion plan includes procedural conversion,
program conversion and the file conversion. The changeover plan also specifies the
method of change from old to new system. Choices of changeover methods include
parallel operations, immediate replacement and physical changeover.

Implementation is divided into one module:

ADMIN LOGIN MODULE: This module provides administrator related functionality

like from this module use can add seat, games, information. From this module Admin
can view daily, weekly and monthly report. This module is developed for admin of the
website and admin can add, delete, edit and view the data related to information of
users in this module.

-- phpMyAdmin SQL Dump

-- version 4.8.4
-- https://www.phpmyadmin.net/
--
-- Host: 127.0.0.1
-- Generation Time: Apr 06, 2019 at 08:34 PM --
Server version: 10.1.37-MariaDB -- PHP Version:
7.3.1
SET SQL_MODE = "NO_AUTO_VALUE_ON_ZERO";

Dept.of.CSE,KIT Page 16
 EMPLOYEE MANAGEMENT SYSTEM
SET AUTOCOMMIT = 0;
START TRANSACTION;
SET time_zone = "+00:00";

/*!40101 SET
@OLD_CHARACTER_SET_CLIENT=@@CHARACTER_SET_CLIENT */;
/*!40101 SET
@OLD_CHARACTER_SET_RESULTS=@@CHARACTER_SET_RESULTS */;
/*!40101 SET
@OLD_COLLATION_CONNECTION=@@COLLATION_CONNECTION */;
/*!40101 SET NAMES utf8mb4 */;

--
-- Database: `370project`
--

-- -------------------------------------------------------
-

--
-- Table structure for table `alogin` --

CREATE TABLE `alogin` (

`id` int(11) NOT NULL,
`email` tinytext NOT NULL,
`password` longtext NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1;

--
-- Dumping data for table `alogin` --
INSERT INTO `alogin` (`id`, `email`, `password`) VALUES (1,
'admin', 'admin');

-- -------------------------------------------------------
-

--
-- Table structure for table `employee` --
CREATE TABLE `employee` (

Dept.of.CSE,KIT Page 17
 EMPLOYEE MANAGEMENT SYSTEM
`id` int(11) NOT NULL,
`firstName` varchar(100) NOT NULL,
`lastName` varchar(100) NOT NULL,
`email` varchar(100) NOT NULL,
`password` text NOT NULL,
`birthday` date NOT NULL,
`gender` varchar(10) NOT NULL,
`contact` varchar(20) NOT NULL,
`nid` int(20) NOT NULL,
`address` varchar(100) DEFAULT NULL,
`dept` varchar(100) NOT NULL,
`degree` varchar(100) NOT NULL,
`pic` text NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1;

--
-- Dumping data for table `employee`
--

INSERT INTO `employee` (`id`, `firstName`, `lastName`,

`email`, `password`, `birthday`, `gender`, `contact`,
`nid`, `address`, `dept`, `degree`, `pic`) VALUES
(101, 'Mehadi', 'Hassan', '[email protected]', '1234',
'1997-08-13', 'Male', '01919', 12121, 'Razarbagh', 'IT',
'Head', 'images/me.png'),
(102, 'Test', 'Pilot', '[email protected]', '1234',
'2018-01-01', 'Male', '0202', 303, 'Ad_______', 'CSE',
'CSE', 'images/no.jpg'),
(103, 'Steven', 'Wilson', '[email protected]', '1234',
'1990-02-02', 'Male', '5252', 6262, 'Thames, UK',
'Creative', 'MSc', 'images/sw-google.png'),
(104, 'Guthrie', 'Govan', '[email protected]', '1234',
'1971-12-01', 'Male', '9595', 5959, 'Chemsford, USA',
'Creative', 'MSc', 'images/test.jpg'),
(105, 'Elon', 'Musk', '[email protected]', '1234', '1971-06- 28',
'Male', '8585', 5858, 'LA, USA', 'SpaceTech', 'BSc',
'images/330px-Elon_Musk_Royal_Society.jpg'),

Dept.of.CSE,KIT Page 18
 EMPLOYEE MANAGEMENT SYSTEM
(106, 'Hacker', 'Man', '[email protected]', '1234', '1990-02-02', 'Male', '7575', 5757,
'Underground, Dhaka', 'NetworkSecurity', 'MSc', 'images/hacker.png'),
(107, 'Wonder ', 'Woman', '[email protected]', '1234', '1993-
03-03', 'Female', '4545', 5454, 'USA', 'Defense ', 'MS', 'images/no.jpg'),
(108, 'Andrew', ' Ng', '[email protected]', '1234', '1976- 04-16',
'Male', '758758', 857857, 'USA', 'AI', 'PhD',
'images/download.jpeg'),
(109, 'Ian ', 'Goodfellow', '[email protected]', '1234', '1985-
01-01', 'Male', '852852', 258258, 'USA', 'AI', 'PhD',
'images/1-5.jpg'),
(110, 'Christopher ', 'Manning', '[email protected]',
'1234', '1965-09-18', 'Male', '147147', 741741, 'USA',
'NLP', 'PhD', 'images/download (1).jpeg'),
(111, 'Jon', 'Snow', '[email protected]', '1234', '2011-02-
01', 'Male', '0187282', 112233, 'Winterfell',
'Management', 'BSc.', 'images/jon-snow.jpg');

-- -------------------------------------------------------
-

--
-- Table structure for table `employee_leave` --

CREATE TABLE `employee_leave` (

`id` int(11) DEFAULT NULL, `token` int(11)
NOT NULL,
`start` date DEFAULT NULL,
`end` date DEFAULT NULL,
`reason` char(100) DEFAULT NULL,
`status` char(50) DEFAULT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1;

--
-- Dumping data for table `employee_leave`
--

INSERT INTO `employee_leave` (`id`, `token`, `start`,

`end`, `reason`, `status`) VALUES
(101, 301, '2019-04-07', '2019-04-08', 'Sick Leave',

Dept.of.CSE,KIT Page 19
 EMPLOYEE MANAGEMENT SYSTEM
'Approved'),
(102, 305, '2019-04-07', '2019-04-08', 'Urgent Family
Cause', 'Approved'),
(103, 306, '2019-04-08', '2019-04-08', 'Concert Tour', 'Approved'),
(101, 307, '2019-04-14', '2019-04-30', 'Want to see GOT',
'Pending'),
(105, 308, '2019-04-26', '2019-04-30', 'Launching Tesla
Model Y', 'Pending'),
(111, 309, '2019-04-09', '2019-04-13', 'Visit to Kings
Landing', 'Pending'),
(104, 310, '2019-04-08', '2019-04-09', 'Emergency Leave', 'Pending');

-- -------------------------------------------------------
-

--
-- Table structure for table `project` --

CREATE TABLE `project` (

`pid` int(11) NOT NULL,
`eid` int(11) DEFAULT NULL,
`pname` varchar(100) DEFAULT NULL,
`duedate` date DEFAULT NULL,
`subdate` date DEFAULT '0000-00-00',
`mark` int(11) NOT NULL,
`status` varchar(50) DEFAULT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1;

--
-- Dumping data for table `project` --

INSERT INTO `project` (`pid`, `eid`, `pname`, `duedate`,

`subdate`, `mark`, `status`) VALUES
(213, 101, 'Database', '2019-04-07', '2019-04-04', 10,
'Submitted'),
(214, 102, 'Test', '2019-04-10', '0000-00-00', 0, 'Due'),
(215, 105, 'Tesla Model Y', '2019-04-19', '2019-04-06',
10, 'Submitted'),
(216, 106, 'Hack', '2019-05-04', '2019-04-05', 5,

Dept.of.CSE,KIT Page 20
 EMPLOYEE MANAGEMENT SYSTEM
'Submitted'),
(217, 111, 'Do Nothing', '2019-04-02', '2019-04-01', 8, 'Submitted'),
(218, 105, 'Tesla Model X', '2019-04-03', '2019-04-03',
10, 'Submitted'),
(219, 101, 'PHP', '2019-04-07', '0000-00-00', 0, 'Due'),
(220, 110, 'Data Analysis', '2019-04-16', '2019-04-04', 8, 'Submitted'),
(221, 110, 'Data Analysis', '2019-04-16', '2019-04-04', 7,
'Submitted'),
(222, 103, 'Statistical', '2019-04-19', '2019-04-04', 6, 'Submitted'),
(223, 108, 'Software Scema', '2019-04-09', '2019-04-02', 3, 'Submitted'),
(224, 107, 'Security Check', '2019-04-26', '2019-04-05',
9, 'Submitted'),
(225, 109, 'ML', '2019-04-03', '2019-04-04', 6, 'Submitted');

-- -------------------------------------------------------
-

--
-- Table structure for table `rank` --

CREATE TABLE `rank` (

`eid` int(11) NOT NULL,
`points` int(11) DEFAULT '0'
) ENGINE=InnoDB DEFAULT CHARSET=latin1;

--
-- Dumping data for table `rank`
--

INSERT INTO `rank` (`eid`, `points`) VALUES

(101, 10),
(102, 0),
(103, 6),
(104, 0),
(105, 20),
(106, 5),
(107, 9),
(108, 3),
(109, 6),

Dept.of.CSE,KIT Page 21
 EMPLOYEE MANAGEMENT SYSTEM
(110, 15),
(111, 8);

-- -------------------------------------------------------
-

--
-- Table structure for table `salary`
--

CREATE TABLE `salary` (

`id` int(11) NOT NULL,
`base` int(11) NOT NULL,
`bonus` int(11) DEFAULT NULL,
`total` int(11) DEFAULT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1;

--
-- Dumping data for table `salary` --

INSERT INTO `salary` (`id`, `base`, `bonus`, `total`)

VALUES
(101, 55000, 10, 60500),
(102, 16500, 0, 16500),
(103, 65000, 6, 68900),
(104, 78000, 0, 78000),
(105, 105000, 20, 126000),
(106, 60000, 5, 63000),
(107, 77000, 9, 83930),
(108, 50000, 3, 51500),
(109, 85000, 6, 90100),
(110, 47000, 15, 54050),
(111, 45000, 8, 48600);
--
-- Indexes for dumped tables
--

--

Dept.of.CSE,KIT Page 22
 EMPLOYEE MANAGEMENT SYSTEM
--
--
Indexes for table `alogin`

ALTER TABLE `alogin`

ADD PRIMARY KEY (`id`);

--
-- Indexes for table `employee`
--
ALTER TABLE `employee`
ADD PRIMARY KEY (`id`),
ADD UNIQUE KEY `email` (`email`);

--
-- Indexes for table `employee_leave`
--
ALTER TABLE `employee_leave` ADD
PRIMARY KEY (`token`),
ADD KEY `employee_leave_ibfk_1` (`id`);

--
-- Indexes for table `project`
--
ALTER TABLE `project`
ADD PRIMARY KEY (`pid`),
ADD KEY `project_ibfk_1` (`eid`);

--
-- Indexes for table `rank`
--
ALTER TABLE `rank`
ADD PRIMARY KEY (`eid`);

--
-- Indexes for table `salary`
--

--

Dept.of.CSE,KIT Page 23
 EMPLOYEE MANAGEMENT SYSTEM
--
ALTER TABLE `salary`
ADD PRIMARY KEY (`id`);
--
-- AUTO_INCREMENT for dumped tables

-- AUTO_INCREMENT for table `alogin`

--
ALTER TABLE `alogin`
MODIFY `id` int(11) NOT NULL AUTO_INCREMENT,
AUTO_INCREMENT=2;

--
-- AUTO_INCREMENT for table `employee`
--
ALTER TABLE `employee`
MODIFY `id` int(11) NOT NULL AUTO_INCREMENT,
AUTO_INCREMENT=112;

--
-- AUTO_INCREMENT for table `employee_leave`
--
ALTER TABLE `employee_leave`
MODIFY `token` int(11) NOT NULL AUTO_INCREMENT,
AUTO_INCREMENT=311;

--
-- AUTO_INCREMENT for table `project`
--
ALTER TABLE `project`
MODIFY `pid` int(11) NOT NULL AUTO_INCREMENT,
AUTO_INCREMENT=226;

--
-- Constraints for dumped tables
--
--

Dept.of.CSE,KIT Page 24
 EMPLOYEE MANAGEMENT SYSTEM
--
--
-- Constraints for table `employee_leave`
--
ALTER TABLE `employee_leave`
ADD CONSTRAINT `employee_leave_ibfk_1` FOREIGN KEY
(`id`) REFERENCES `employee` (`id`) ON DELETE CASCADE ON UPDATE
CASCADE;

--

Dept.of.CSE,KIT Page 25
 EMPLOYEE MANAGEMENT SYSTEM
--
Constraints for table `project`
--
ALTER TABLE `project`
ADD CONSTRAINT `project_ibfk_1` FOREIGN KEY (`eid`)
REFERENCES `employee` (`id`) ON DELETE CASCADE ON UPDATE CASCADE;

--
-- Constraints for table `rank`
--
ALTER TABLE `rank`
ADD CONSTRAINT `rank_ibfk_1` FOREIGN KEY (`eid`)
REFERENCES `employee` (`id`) ON DELETE CASCADE ON UPDATE CASCADE;

--
-- Constraints for table `salary`
--
ALTER TABLE `salary`
ADD CONSTRAINT `salary_ibfk_1` FOREIGN KEY (`id`)
REFERENCES `employee` (`id`) ON DELETE CASCADE ON UPDATE CASCADE;
COMMIT;

/*!40101 SET
CHARACTER_SET_CLIENT=@OLD_CHARACTER_SET_CLIENT */;
/*!40101 SET
CHARACTER_SET_RESULTS=@OLD_CHARACTER_SET_RESULTS */;
/*!40101 SET
COLLATION_CONNECTION=@OLD_COLLATION_CONNECTION */;
CHAPTER 5
SOFTWARE TESTING
SYSTEM TESTING
The testing phase is an important part of software development. It is the processes of
finding errors and missing operations and also a complete verifications to determine
whether the objectives , requirements are satisfied. Software testing is carried out in
three steps,

Dept.of.CSE,KIT Page 26
 EMPLOYEE MANAGEMENT SYSTEM
Levels in testing:
1) Unit testing
2) Integration testing
3) Validation testing
The first step includes unit testing where each module is tested to provide its
correctness to determine any missing operations and to verify whether the objectives
have been met. Errors are noted down and corrected immediately. Unit testing is the
important and major part of the project. So errors are rectified easily in particular
modules and program quality is increased. In this project, entire system is divided into
several modules.
Second step include integration testing. If we need not to be the case that
software whose modules when run individually and showing perfect result with also
show perfect result as whole .The individual modules are clipped under this major
module and tested again and verified the results. A module can have inadvertent,
adverse effect on any other on the global data structure causing serious problems.

UNIT TESTING

It is the process of taking each program modules and runs in isolation from the rest of
the modules, by using prepared inputs and comparing the results with the results
predicted by the specifications and design of modules .This enables the tester to detect
errors in coding and logic that are contained within that module one.

INTEGRATION TESTING

Integration testing is a systematic technique for constructing tests to uncover errors

associated within the interfaces. In this testing , all the modules are combined , and then
the entire program is tested as a whole.

VALIDATION TESTING

Dept.of.CSE,KIT Page 27
 EMPLOYEE MANAGEMENT SYSTEM
At the culmination of integration testing, software is completely assembled as a
package; interfacing errors have been recovered and corrected and a final series of a
software testsvalidation tests begin. Validation testing can be defined in many ways but
a simple definition is that validation succeeds when the software functions in a manner
that can be reasonably expected by the customer.
In validation testing if user wants to enter the numeric value he can only enter
the numeric value not the text value. For e.g.: in phone number field user can only enter
numeric value to it. The system is user friendly with user guide and messages to explain
further procedures. An attempt has been made to perfect the process by incorporating
validation at each level.

TEST CASES
During Test Cases that are good at revealing the presence of faults is central to
successful testing. The reason for this is that if there is a fault in the program, the
program can still provide the expected behaviour on the certain inputs. Only for the set
of inputs the faults that exercise the fault in the program will the output of the program
devise from the expected behaviour. Hence, it is fair to say that testing is as good as its
test case.
number of test cases used to determine errors in the program should be
minimum. There are two fundamental goals of a practical testing activity:-

• maximize the number of errors detected and. minimize the number of test cases.

As these two goals are contradictory so the problem of selecting test cases is a
complex one. While selecting the test cases the primary objective is to ensure that if
there is an error or fault in the program, it is exercised by one of its test cases. An ideal
test case is one which succeeds (meaning that there are no errors, revealed in its
execution) only it there are no errors in the program one possible set of ideal test cases is
one which includes all the possible inputs to the program. This is often called
"exhaustive testing", however it is impractical and infeasible as even a small program
can have an infinite input domain.

Dept.of.CSE,KIT Page 28
 EMPLOYEE MANAGEMENT SYSTEM
So to avoid this problem we use "test criteria" in selection of the test cases. There are
two aspects of the test case selection:-
• specifying a criteria for evaluating the test cases
• generating the set of cases that satisfy a given criteria.

The fully automated process of generating test criteria has not been yet found rather
guidelines are only the automated tool available to us previously. The two fundamental
properties for a testing criterion are:-
• Reliability: a criterion is reliable if all the sets that satisfy the criteria detect the same
error. .
• Validity: a criterion is valid if for any error in the program there is some set satisfying
the criteria that will reveal the error.

The fundamental theorem of testing is that if a testing criterion is valid and reliable, if a
set satisfying criteria succeeds then the program contains no errors. Test case 1

Case : Testing the domain login.

Result : All the operations work successfully.
Test case 2
Case : Testing the basic module.
Result : System is not able to detect and generate correct information and
exception
Reason : This occurred because query is not proper format, script problem.
Solution : After giving the proper function and query, we can able to get correct
result.

Test case 3
Case : Testing of the generated report.
Result : System is not able to generate correct output.
Reason : His occurred because database was not normalized.
Solution : After marketing proper normalized we can able to get correct result.

Test case 4

Case : Testing of the generated report.

Result : System is not able to generate correct output.
Reason : His occurred because query is not properly fired.

Dept.of.CSE,KIT Page 29
 EMPLOYEE MANAGEMENT SYSTEM
Solution : After giving the proper query, we can able to get correct result.

Test case 5

Case : Testing of the admin(master) module (employee rights) Result

: All the operation works successfully.

Dept.of.CSE,KIT Page 30
 EMPLOYEE MANAGEMENT SYSTEM

CHAPTER 6
SCREENSHOTS AND OUTPUT

ADMIN LOGIN

Fig 5.2: Admin Page

Dept.of.CSE,KIT Page 31
 EMPLOYEE MANAGEMENT SYSTEM
EMPLOYEE LOGIN PAGE

EMPLOYEE REGISTERATION FORM

Fig 5.4: Employee register form

Dept.of.CSE,KIT Page 32
 EMPLOYEE MANAGEMENT SYSTEM
EMPLOYEE DATA VEIW

PROJECT ASSIGN FOR EMPLOYEE

Dept.of.CSE,KIT Page 33
 EMPLOYEE MANAGEMENT SYSTEM
LEAVE FORM

SALARAY VIEW

Fig 5.8: Salary view

CHAPTER 7
CONCLUSION AND FUTURE ENHANCEMENT

Dept.of.CSE,KIT Page 34
 EMPLOYEE MANAGEMENT SYSTEM
CONCLUSION

• The aim of the project is to automate a (your project), which has been
successfully performed.
• The package is very user friendly one, which helps the administrator to manage
the users and also the database itself efficiently with effective use of minimum
number of buttons. The user or administrator is not expected to know completely
about the software.
• This reduces manual and enormous amount of paperwork involved.

FUTURE ENHANCEMENT.

Currently the system supports in desktop pc and in future we can make mobile browser
compatible site.

BIBLIOGRAPHY

• Elmasri & Navathe; Fundamentals of Database Systems Third Edition,

AddisonWesley,1999.
• Raghu Ramakrishnan; Database Management Systems, Second Edition, McGraw
Hill, 2000
• Visua,l basic 6.0 Rajendra Prasad

REFERENCES
https://learndigital.withgoogle.com/digitalgarage-au https://www.w3schools.com/

https://www.tutorialspoint.com/index.html

Dept.of.CSE,KIT Page 35