VMV COMMERCE, JMT ARTS & JJP

SCIENCE COLLEGE
(Institute of Computer Studies and Research)
Wardhaman Nagar, Nagpur-08.

MCA Department

A
Project Report
On

“Payroll and Employee Management Web Application”

Submitted to
Rashtrasant Tukadoji Maharaj Nagpur University, Nagpur

In partial fulfillment of the requirement of

Master of Computer Application

M.C.A-II, SEM-II

Developed & Submitted by

Miss. Ayushi S. Jain

Mr. Shyamnarayan H. Pandey

Under the Guidance of

Mrs. A.P Dongaonkar

 2021 – 22

VMV COMMERCE, JMT ARTS & JJP

SCIENCE COLLEGE
(Institute of Computer Studies and Research)
Academic Year 2021 - 22
Wardhaman Nagar, Nagpur-08.

MCA Department

DECLARATION

We here-by declare that the project entitled “Payroll and Employee

Management Web Application’’ has completed by us in partial fulfillment of

M.C.A.-II (Master of Computer Application), Sem.-II degree examination as

prescribed by Rashtrasant Tukadoji Maharaj Nagpur University, Nagpur and had not

been submitted for any other examination and does not form the part of any other

course undergone by us.

Name of Student(s) Student Signature(s)

1. Miss. Ayushi S. Jain

2. Mr. Shyamnarayan H. Pandey

 Place:

Date:

VMV COMMERCE, JMT ARTS & JJP

SCIENCE COLLEGE
(Institute of Computer Studies and Research)
Wardhaman Nagar, Nagpur-08.
Academic Year 2021 - 22
MCA Department

CERTIFICATE

This is to certify that the project entitled “Payroll and Employee Management Web
Application” by “Miss. Ayushi Jain and Mr.Shyamnarayan Pandey” in partial fulfillment of
M.C.A.-II(Master of Computer Application), Sem.-II degree examination, had not
been submitted for any other examination and does not form part of any other
course undergone by the candidate.

It is further certified that they have completed their project as prescribed

by Rashtrasant Tukadoji Maharaj Nagpur University, Nagpur.

Mrs. A.P Dongaonkar Dr. V. R. Bhedi
Guide In-charge

Internal Examiner External Examiner

Place: Nagpur

Date:

ACKNOWLEDGEMENT
With immense pride and sense of gratitude, we take this golden opportunity
to express our sincere regards to the honorable In-charge Dr. V. R. Bhedi of
institute for providing us facilities and inspiration to gather professional
knowledge and material without which it would have been impossible to
complete this hard task.

We are extremely thankful to our Project Guide Mrs. A.P Dongaonkar for his
project guideline throughout the project. Our sincere regards to her for giving
us his outstanding guidance, enthusiastic suggestions and invaluable
encouragement which helped us to complete the project.

We will be failing in our duty if we do not thank the non-teaching staff of the
college for their cooperation.

We would like to thank all who helped us in making this project complete and
successful one.

Miss. Ayushi S.
Jain
Mr. Shyamnarayan H. Pandey
MCA

INDEX

SR.NO CONTENTS PAGE NO.

INTRODUCTION

1.1 EXISTING SYSTEM AND NEED FOR NEW SYSTEM

1.
1.2 PROPOSED SYSTEM
1.3 SCOPE OF WORK

PROBLEM DEFINITION
2.
2.1 REVIEW OF RELATED WORK
2.2 PROBLEM DEFINITION
 ANALYSIS & DESIGN

3.1 USER REQUIREMENTS

3.2 FRONT END & BACK END
3. 3.3 SYSTEM FLOW
3.4 MODULE DESCRIPTION AND FLOW
3.5 DATA FLOW DIAGRAM (DFD)
3.6 ENTITY RELATIONSHIP DIAGRAM (ERD)
3.7 TABLE DESIGN

IMPLEMENTATION & RESULTS

4. 4.1 INPUT FORMS WITH DATA

4.2 OUTPUT REPORTS WITH DATA
4.3 SAMPLE CODE

TESTING AND MAINTENANCE

5. 5.1TESTING
5.2VALIDATION
5.3MAINTENANCE

USER MANUAL
6.
6.1 USER MANUAL

CONCLUSION AND FUTURE SCOPE

7.
7.1 CONCLUSION
7.2 LIMITATIONS AND FUTURE SCOPE

8. REFERENCES

1 Blank Page at the end.

BRIEF Review
Of Project
 Introduction

Introduction
The purpose of SDSSU Payroll System is mainly to provide automation to the SDSSU
accounting section. The categories of this system where the accountant can calculate the
amount an employee owe based on factors such as the time they worked, their hourly
wages or salaries, and whether they took vacation or holiday time during the pay period.
The system adjusts gross pay by calculating and subtracting taxes and other withholding
amounts. This system was designed for convenience, less time cost. Now days in many
public places such as malls, multiplex system, hospitals, offices, market areas there is a
crucial problem of vehicle parking. The vehicle parking area has many lanes/slots for car
parking. So to park a vehicle one has to look for all the lanes. Moreover this involves a lot of
manual labour and investment. Instead of vehicle caught in towing the vehicle can park on
safe and security with low cost.

Parking control system has been generated in such a way that is filled with many secure
devices such as, parking control gates, toll gates, time and attendance machine, car
counting system etc. these features are hereby very necessary nowadays to secure your car
and also to evaluate the fee structure for every vehicles entry and exit.

The objectives of this project is to build a Vehicle Parking management system that
enables the time management and control of vehicles using number plate recognition. The
system that will track the entry and exit of cars, maintain a listing of the cars with the
parking lot, and determine if the parking lot is full or not. It will determine vehicle according
to their time consumption.

AIMS &OBJECTIVES

The objective of the Payroll System. The payroll management system is a set of
processes that helps you streamline salaries, bonuses, deductions, taxes, and other
necessary aspects of the net pay of all the employees in your organization.

 Ensure employee's are paid on time.

 Ensure the accuracy of the amount employee's are paid.

 Payroll systems are also crucial for companies to ensure that they are following
laws and provide proof of compliance.

 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.
PRELIMINARY
SYSTEM
ANALYSIS
 PRELIMINARY SYSTEM ANALYSIS

 Identification of need:

Identification of needs is generally concerned with the user's requirements and

expectations from the system. Systems can be classified under two categories: Manual
and Computerized. It is obvious that in most cases computerized systems are more
capable and beneficial than manual system due to their faster responses and quick and
fast processing capabilities. Thus in most cases manual systems are concerned with their
transformations into computerized ones. In other cases computerized systems are
concerned with more betterment of their existing system. Whatever may be the reason
there must be some expectation of the users from the new system to be developed. These
expectations are from the identification of needs for the project.

The following are the needs for the development of the proposed system:

 Faster performance of calculations and safe storage of records for later needs.
 Faster Updates and Modifications of the existing records.
 Presentations in ordered and well-structured format.
 Secured storage and retrieval of data.

 Feasibility Study:

Depending on the results of the initial investigation the survey is now expanded to a more
detailed feasibility study. “FEASIBILITY STUDY” is a test of system proposal according to its
workability, impact of the organization, ability to meet needs and effective use of the
resources. It focuses on these major questions:
1. What are the user’s demonstrable needs and how does a candidate system meet
them?
2. What resources are available for given candidate system?
3. What are the likely impacts of the candidate system on the organization?
4. Whether it is worth to solve the problem?
5.During feasibility analysis for this project, following primary areas of interest are to
be considered. Investigation and generating ideas about a new system does this.

Technical Feasibility:
A study of resource availability that may affect the ability to achieve an acceptable system.
This evaluation determines whether the technology needed for the proposed system is
available or not.
• Can the work for the project be done with current equipment existing software
technology & available personal?
• Can the system be upgraded if developed?
• If new technology is needed then what can be developed?
This is concerned with specifying equipment and software that will successfully satisfy the
user requirement. The technical needs of the system may include:

Front-end and back-end selection

An important issue for the development of a project is the selection of suitable front-end
and back-end. When we decided to develop the project we went through an extensive study
to determine the most suitable platform that suits the needs of the organization as well as
helps in development of the project.

Economical Feasibility:

Economic justification is generally the “Bottom Line” consideration for most systems.
Economic justification includes a broad range of concerns that includes cost benefit
analysis. In this we weight the cost and the benefits associated with the candidate system
and if it suits the basic purpose of the organization i.e. profit making, the project is making
to the analysis and design phase.
The financial and the economic questions during the preliminary investigation are verified
to estimate the following:
• The cost to conduct a full system investigation.
• The cost of hardware and software for the class of application being considered.
• The benefits in the form of reduced cost.
• The proposed system will give the minute information, as a result the performance
is improved which in turn may be expected to provide increased profits.
• This feasibility checks whether the system can be developed with the available
funds. The Hospital Management System does not require enormous amount of
money to be developed. This can be done economically if planned judicially, so it is
economically feasible. The cost of project depends upon the number of man-hours
required.
Operational Feasibility
It is mainly related to human organizations and political aspects. The points to be
considered are:
• What changes will be brought with the system?
• What organization structures are disturbed?
• What new skills will be required? Do the existing staff members have these
skills? If not, can they be trained in due course of time?
The system is operationally feasible as it very easy for the End users to operate it. It only
needs basic information about Windows platform

 Need of the system:

A computerized system is needed mainly because of the lack of speed in the manual
system. Computerized system provides speed with accuracy. The new transaction
entries can be made instantly. The modification and deletion of records regarding the
transaction can be done in no time. The new system will not only make modification and
new transaction faster but also speedup the report generation. The generation of
reports will become time effective and the scope of generation will also increase. The
information flow will become faster. The transparency level will also increase. The
coordination between different modules will also increase. The manpower and the paper
work needed for maintaining the operation of the Library will be reduced by the
introduction of the computerized system.

 Flaws of the system:

Every system contains some flaws. In this system, when the user inputs wrong
data the system provides wrong output. The main flaw of the system is it is very expensive.
The estimate of purchase and installation goes very high. Following are the some
Advantages & Disadvantages of the System.

Advantages:

 The system is useful as it calculates an exact cost for all the resources required
during the event.
 The user gets all the resources at a single place instead of wandering around for
these.
 This system is effective and saves time and cost of the users.

Disadvantages:
 Computerized system is very expensive.
 Computerized system is not easy to understand by anyone.
 We have to supply correct data and information. If we supplied wrong data
or information, system cannot correct it and we get wrong output.
 We can delete any record easily.

 There is no human interaction if users have some enquiry.

SYSTEM
SOFTWARE & HARDWARE REQUIREMENTS

 Operating System-Windows 7/8

 Process Dual to core up to i9
 Web Browser- Google Chrome
 Ram 512MB
 Hard Disk-5GB

TOOLS / PLATFORM

Front End-Html(Hyper Text Markup Language), Css/css3,Bootstrap,JavaScript

Back End-Php(PHP: hypertext preprocessor)

LANGUAGE USED
 HTML , CSS/CSS3 , BOOTSTRAP & JAVASCRIPT
 PHP
 JAVA SCRIPT
 DATABASE-PHP MYADMIN
 SERVER- XAMP SERVER

DETAILED
SYSTEM
ANALYSIS
MODULE OF PROJECT

Payroll and Employee Management Web Application

User Login Admin Login Admin_Profile Dashboard

Attendence Employees Deductions Positions

Data Flow Diagram
Entity- relationship diagram
Entity-Relationship database diagram
 INPUT Screens

LOGIN FORM
DASHBOARD:

ADD EMPLOYEE:
EMPLOYEE OVERTIME:(form view)

CASH ADVANCE (Form View):

ADD ATTENDENCE (Form View):
 OUTPUT SCREEN
S

REPORT ATTENDENCE:
EMPLOYEE LIST(DETAIL):
 IMPLEMENTATION

Software testing :
TESTING:-
Testing is a process of executing a program with the indent of finding an error.
Testing is a crucial element of software quality assurance and presents ultimate
review of specification, design and coding.
System Testing is an important phase. Testing represents an interesting
anomaly for the software. Thus a series of testing are performed for the
proposed system before the system is ready for user acceptance testing.
A good test case is one that has a high probability of finding an as
undiscovered error. A successful test is one that uncovers an as
undiscovered error.
Testing Objectives:
1. Testing is a process of executing a program with the intent of finding an
error
2. A good test case is one that has a probability of finding an as yet
undiscovered error
3. Successful test is one that uncovers an undiscovered
errortesting principles:
➢ all tests should be traceable to end user requirements
➢ tests should be planned long before testing begins
➢ testing should begin on a small scale and progress
towards testing in large
➢ exhaustive testing is not possible
➢ to be most effective testing should be conducted by a
independent third party

The primary objective for test case design is to derive a set of tests that
has the highest livelihood for uncovering defects in software. to accomplish
this objective two different categories of test case design techniques are
used. they are
▪ white box testing.
▪ black box
testing.

white-box testing:
White box testing focus on the program control structure. Test
casesare derived to ensure that all statements in the program have been
executed at least once during testing and that all logical conditions have
been executed.
Black-box testing:
Black box testing is designed to validate functional requirements without
regard to the internal workings of a program. Black box testing mainly
focuses on the information domain of the software, deriving test cases by
partitioning input and output in a manner that provides thorough test
coverage. Incorrect and missing functions, interface errors, errors in data
structures, and error in functional logic are the errors falling in this category.

Testing strategies:
A strategy for software testing must accommodate low-level tests thatare
necessary to verify that all small source code segment has been
correctly implemented as well as high-level tests that validate major system
functions against customer requirements.
Testing fundamentals:
Testing is the 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. If testing is
conducted successfully it uncovers the errors in the software.
Testing cannot show the absence of defects, it can only show
that software defects present.

Testing Information flow:

Information flow for testing flows the pattern. Two class
of input provided to test the process. The software configuration
includes a software requirements specification, a design
specification and source code.
Test configuration includes test plan and test cases
and test tools. Tests are conducted and all the results are
evaluated. That is test results are compared with expected
results. When erroneous data are uncovered, an error is
implied and debugging commences.
Unit testing:
Unit testing is essential for the verification of the code
produced during the coding phase and hence the goal is to
test the internal logic of the modules. Using the detailed
design description as a guide, important paths are tested to
uncover errors with in the boundary of the modules. These
tests were carried out during the programming stage itself. All
units of Vienna SQL were successfully tested.
Integration testing:
Integration testing focuses on unit tested modules and
build the program structure that is dictated by the design phase.
System testing:
System testing tests the integration of each module in
the system. It also tests to find discrepancies between the
system and it’s original objective, current specification and
system documentation. The primary concern is the compatibility
of individual modules. Entire system is working properly or not
will be tested here, and specified path ODBC connection will
correct or not, and giving output or not are tested here these
verifications and validations are done by giving input values to
the system and by comparing with expected output. Top-down
testing implementing here.
Acceptance Testing:
 This testing is done to verify the readiness of the
system for the implementation. Acceptance testing begins when
the system is complete. Its purpose is to provide the end user
with the confidence that the system is ready for use. It involves
planning and execution of functional tests, performance tests
and stress tests in order to demonstrate that the implemented
system satisfies its requirements.
Tools to special importance during acceptance testing include:
Test coverage Analyzer – records the control paths followed
for each test case.
Timing Analyzer – also called a profiler, reports the time spent in
various regions of the code are areas to concentrate on to
improve system performance.
Coding standards – static analyzers and standard checkers are
used to inspect code for deviations from standards and
guidelines.
Test Cases:
Test cases are derived to ensure that all statements in
the program have been executed at least once during testing
and that all logical conditions have been executed.
Using White-Box testing methods, the software engineer can
drive test casesthat
• Guarantee that logical decisions on their true and false sides.
• Exercise all logical decisions on their true and false sides.
• Execute all loops at their boundaries and with in their
operational bounds.
• Exercise internal data structure to assure their validity.
▪
The test case specification for system testing has to be
submitted for reviewbefore system testing commences.
 MAINTENACE

Maintenance and environment:

AS the number of computer based systems, grieve libraries of computer

software began to expand. In house developed projects produced tones of
thousand soft program source statements. Software products purchased
from the outside added hundreds of thousands of new statements. A dark
cloud appeared on the horizon. All of these programs, all of those source
statements-had to be corrected when false were detected, modified as user
requirements changed, or adapted to new hardware that was purchased.
These activities were collectively called software Maintenance.
The maintenance phase focuses on change that is associated with error
correction, adaptations required as the software's environment evolves,
andchanges due to enhancements brought about by changing customer
requirements. Four types of changes are encountered during the
maintenance phase.

➢ CORRECTION
➢ ADAPTATION
➢ ENHANCEMENT
➢ PREVENTION
Correction:

Even with the best quality assurance activities is lightly that the customer will
uncover defects in the software. Corrective maintenance changes the
software to correct defects.

Maintenance is a set of software Engineering activities that occur after

software has been delivered to the customer and put into operation.
Software configuration management is a set of tracking and control
activities that began when a software project begins and terminates only
when the software is taken out of the operation.

We may define maintenance by describing four activities that are

undertaken after a program is released for use:

Corrective
Maintenanc
eAdaptive
 Maintenanc
e
Perfective Maintenance or
Enhancement Preventive
Maintenance or reengineering

Only about 20 percent of all maintenance work is spent "fixing mistakes".

The remaining 80 percent are spent adapting existing systems to changes in
their external environment, making enhancements requested by users,
and reengineering an applicationfor use.

ADAPTION:-
Over time, the original environment (E>G., CPU, operating system,
business rules, external product characteristics) for which the software was
developed is likely to change. Adaptive maintenance results in a modification
to the software to accommodate change to its external environment.

ENHANCEMENT: -
As software is used, the customer/user will recognize additional
functions that will provide benefit. Perceptive maintenance extends the
software beyond its original function requirements.

PREVENTION:
Computer software deteriorates due to change, and because
of this, preventive maintenance, often called software re engineering, must
be conducted to enable the software to serve the needs of its end users. In
essence, preventive maintenance makes changes to computer programs
so that they can be more easily corrected, adapted, and enhanced.
Software configuration management (SCM) is an umbrella activity that is
applied throughout the software process.
 2.5 USER MANUAL

The user manual will be provided along with the project so as to help the
user understand the working of the software. It provides detailed information
and allows the user to follow the steps in the user manual.

(i) Assumptions and Dependencies

This software has adependency on the browser that it can be best viewed in any browser.

(ii) System Features

The services provided by this software are:-

➢ THE COMPLAINTS CAN BE REGISTERED.

➢ THE COMPLAINTS CAN BE ATTENDED.

➢ THE STATUS OF THE COMPLAINT CAN BE VIEWED.

➢ REPORTS CAN BE GENERATED AND VIEWED DATE

-WISE AND BRANCH-WISE.
MODE OF OPERATION: -

➢ THE SOFTWARE IS LOGGED IN BY THE LOGIN PAGE. IT

CAN BE LOGGED IN BY ENTERING A USERNAME AND
PASSWORD.

➢ THE USERNAME IS ENTERED AS THE PATIENT ID

CODE AND THE NAME CORRESPONDS TO THE
EMPLOYEE CODE THAT APPEARS IN THE TEXTBOX.
(iii) User Class: -
➢ ADMINISTRATOR

➢ USER (PATIENTS, DOCTOR, RECEPTIONIST ETC.)

(iv) Functional Hierarchy: -

➢ THIS SOFTWARE STATES THE TOP LEVEL IN THE
FUNCTIONAL HIERARCHY AS THEADMINISTRATOR.
CONCLUSION
CONCLUSION:-

“Payroll Management System” software developed for a

company has been designed to achieve maximum efficiency and reduce the time
taken to handle the Payroll activity. It is designed to replace an existing manual
record system thereby reducing time taken for calculations and for storing data. The
system uses Asp .Net as front end and Microsoft SQL as a backend for the database.
The system is strong enough to withstand regressive daily operations under
conditions where the database is maintained and cleared over a certain time of span.
The implementation of the system in the organization will considerably reduce data
entry, time and also provide readily calculated reports.

LIMITATION OF PROJECT:

 Payroll Software Can Be Expensive.

 You May Need to Hire Staff to Process Your Payroll.
 You Must Constantly Backup Your Payroll Data.
 Access to Payroll Software May Be Limited.
 Your Payroll Software May Lead to Withholding Errors.

Scope & FUTURE of PROJECT:

 The future of payroll will become more people focused, those working in the
department will need to be educated, skilled and knowledgeable so that they
can answer queries and support their organizations employees in
understanding their pay and reward.

 This system is effective and saves time and cost of the users.
 BIBLIOGRAPHY

Bibliography:
For the completion of project “Payroll and Employee Management Web Application”,
we have taken reference from variety of book related to HTML, PHP, which helped us
a lot for successful completion of this project. The books referred are as follows:

 AIKEN, T. E. 1957. PROCESSING OUR PAYROLL ON THE UNIVAC. N.A.C.A.

BULLETIN (MAY): 1167-1178.
 ALLEN, L. H. 1914. PAYROLL DISTRIBUTION ON CONSTRUCTION
WORK. JOURNAL OF ACCOUNTANCY (JULY): 38-46.
 AMERICAN PAYROLL ASSOCIATION. 2005. FEDERAL PAYROLL TAX LAWS
AND REGULATIONS. AMERICAN PAYROLL ASSOCIATION.
 ASHER, L. I. 1952. THE PAYROLL METHOD-MANUAL, MACHINE OR
MIXED? N.A.C.A. BULLETIN (MARCH): 864-869.
 BEAUDRY, D. P. JR. 1949. AN ECONOMICAL PAYROLL SYSTEM FEATURING
CENTRALIZED PROCESSING OF EMPLOYEE DEDUCTIONS BY MACHINE
METHODS. N.A.C.A. BULLETIN (SEPTEMBER): 43-58.
 BROWN, C. F. 1927. LABOR CLASSIFICATION AND PAYROLL
ANALYSIS. N.A.C.A. BULLETIN (MAY 1): 789-802.