Professional Documents
Culture Documents
Payroll Management System: A Project Report ON
Payroll Management System: A Project Report ON
PROJECT REPORT
ON
Submitted by
degree of
DIPLOMA IN ENGINEERING
in
Information Technology
CERTIFICATE
This is to certify that the project report, submitted along with the project
entitled Payroll Management System has been carried out by Vrushika H.
Ruwala, Monika D. Tiwari, Devanshi V. Trivedi under my guidance in
partial fulfillment for the degree of Diploma in Information Technology 5th
Semester of Gujarat Technological University, Ahmedabad during the
academic year 2018-19. These students have successfully completed project
activity under my guidance.
External Examiner:
The satisfaction that accompanies that the successful completion of any task would be
incomplete without the mention of people whose ceaseless cooperation made it possible,
whose constant guidance and encouragement crown all efforts with success.
We are grateful to our project guide Mr. Pragnesh A. Patel for the guidance, inspiration
and constructive suggestions that helpful us in the preparation of this project.
We also thank our colleagues who have helped in successful completion of the project.
I
ABSTRACT
In our institute process of salary slip generation done manually by an admin. Admin uses
Microsoft excel for maintaining all information related to faculties salary and salary slip
generation. But using Microsoft excel for such task makes overall process more time
consuming and error prone as lots of manual work has to be done by admin. Payroll
management system will be used for maintaining and monitoring salary slip generation
process of faculties within institute. The primary objective of system is to maintain details
of various allowances, tax, deductions and increments that need to be given to the
faculties of the organization. System enables faculties to view or print their salary slip of
particular month or year. Using this system admin can generate salary slip and perform
pay bill calculation according to the salary structure assigned to individual faculty
efficiently and timely manner. If faculties have any query related to salary slip or have
any other queries, they can ask to admin about query and admin resolve query.
II
Table of Contents
Table of Contents...........................................................................................................................III
Chapter 1: Introduction...................................................................................................................1
1.1 Project Summary........................................................................................................1
1.2 Purpose.......................................................................................................................2
1.3 Scope..........................................................................................................................3
1.4 Report Outline......................................................................................................................4
Chapter 2: Literature Review..........................................................................................................5
2.1 Existing System..........................................................................................................5
2.2 Problems in existing system.......................................................................................5
2.3 Problem Solution:.................................................................................................................6
Chapter 3: Project Management.....................................................................................................7
3.1 Project Planning and scheduling................................................................................7
3.1.1 Project Development Approach..........................................................................7
3.1.2 Project Plan..........................................................................................................9
3.1.3 Schedule Representation...................................................................................10
Chapter 4: System Requirements Specification............................................................................11
4.1 functional Requirement............................................................................................11
4.2 Non-functional requirements....................................................................................13
4.3 Hardware and Software Requirement................................................................................14
Chapter 5: System Analysis...........................................................................................................15
5.1 Feasibility Study.....................................................................................................15
5.1.1 Technical Feasibility.........................................................................................15
5.1.2 Economical Feasibility......................................................................................16
5.1.3 Operational Feasibility...................................................................................16
5.2 Function of System.............................................................................................................17
5.2.1 Use Case Diagram..............................................................................................17
5.3 Data Modeling....................................................................................................................18
5.3.1 Class Diagram.....................................................................................................18
IV
List of Figures
List of Tables
V
166150316049 PAYROLL MANAGEMENT SYSTEM
166150316058
166150316059
Chapter 1: Introduction
Payroll management system deals with the maintenance of salary slip generation
.faculties do registration. In registration process faculties add their personal and bank
account related details. Faculties can update their profile. For administration login,
separate username and password will be provided. Admin will add salary details of each
faculties and system will calculate salary based on increments, deduction and other salary
details. Salary slip will be generated month wise by system. Faculties will view their
salary slip of particular month or year with login into their account and also can print their
salary slip. At the end of the year salary report will be generated for specific criteria. If
faculties have any query related to salary slip or have any other queries, they can ask to
admin about query and admin resolve query.
It is show the comparison between existing system and our system and also shows what is
drawback of existing system and how we overcome that drawbacks by making our
project.
Project management includes project planning and scheduling and it divided into subparts
such as project development approach, project plan &schedule representation. Project
development approach tells about the model which we are going to use in our project.
Project plan represent the time duration of different task of project and schedule represent
shows the graphical representation of project.
This chapter gives the idea about functional and non-functional requirements of system
and requirement of software and hardware tools.
This chapter contains information such as feasibility study, functions of system, data
Modeling and functional and behavioral modeling.
Data base design shows the tables of data dictionary of each table.
The iterative waterfall model provides feedback paths from every phase to its preceding
phases, which is the main difference from the classical waterfall model.
Feedback paths introduced by the iterative waterfall model are shown in the figure below.
₋ Major requirements must be defined; however, some details can evolve with time
₋ In iterative model we are building and improving the software step by step.
₋ In iterative waterfall model feedback path from one phase to its preceding phase
allows correcting the errors that are committed and these changes are reflected in
the later phases.
166150316049 PAYROLL MANAGEMENT SYSTEM
166150316058
166150316059
Work task Jul Aug Sep Oct Jan Feb March April
Find definition ,
analyzing definition
Abstract generation,
analysis of system
Development approach
Work division
Functionalities and
characteristics of
system
Diagrams
Documentation
Testing
Chapter 4: System Requirements Specification
4.1 Functional Requirement
The functional requirements discuss the functionalities expected from the system. These
are statements of services that provide how the system should react to particular inputs
and how the system should behave in particular situation. It describes relationship
between inputs and outputs.
Administrative module.
Efficiency: Our payroll management system reduces time spent on processing employee
information, salaries, tax and other information. The efficiency of this system realised
when salaries related or other information is sought and need not be found manually in a
separate or paper based system. It takes less time to generate payslip.
Data Security: Our system does not allow data unauthorized person access to data that
includes their personal and banking details. Our system provide a password protected
environment by which only authorized person can view their personal and other
information related detail.
Accuracy: as the number of faculties rises, so will the paper work need to be done .The
higher the quantity the higher the risk of human error. Payroll system provides
automation of entire process. It provides accurate salary calculation and other
information.
Reduce complexity: process of salary slip generation is done manually and maintaining
all these information on paper that increases complexity. Due this complexities errors also
increases. The use of MS excel to process payroll will result in the quick accumulation of
multiple sheets and files as we need different document for faculties information and
other data that also increases complexity. Using our system salary slip generates
automatically and all other information stores at one place so there is no possibility to
increases any complexity.
GPG (IT) P a g e 13
4.3 Hardware and Software Requirement
The Feasibility analysis is designed to determine whether or not, given the project
environment, a project will be successful. A feasibility analysis may be conducted for a
project with emphasis on financial viability, environmental integrity, cultural
acceptability, or political practicability. It is determination of a success and a description
of how that determination should be achieved.
It makes analysis of different aspects like cost required for developing and executing the
system, the required for each phase of the system and so on. It helps identifying the risk
factors involved in developing and deploying the system and helps in planning for risk
analysis. If these important factors are not analyzed then definitely it would have impact
on the organization and the development and the system would be a total fail.
Technical feasibility is center around the computer system such as hardware, software etc.
this is determining whether the available technical system is feasible to run our project or
no? Suppose current computer is operating at 80% load then additional hardware. And it
affects financial consideration to enhance this system .if budget is available then you can
enhance it. It is determining whether the current hardware and software is sufficient to
complete project work or not.
5.1.2 Economical Feasibility
Economic analysis is most used method for evaluating the effectiveness of system .this is
commonly known as cost/benefit analysis. The procedure is to determine the benefit and
compare them with cost, whether it is economically feasible or not? If yes, then the
decision is made to design and implement the system. It is determining whether software
is in budget to develop or not.
The System Working is quite easy to use and learn due to its simple but attractive
interface. User requires no special training for operating the system. Technical
performance include issues such as determining whether the system can provide the right
information for the Department personal faculty details, and whether the system can be
organized so that it always delivers this information at the right place and on time using
internet services. Acceptance revolves around the current system and its personnel.
5.2 Function of System
5.2.1Use Case Diagram
The requirements of a system can be captured by use case diagrams. They are modeled to
capture the intended behavior of the system. Use cases interact with human or actors that
use the system to accomplish some work. They define a set of sequence of actions that a
system performs to yield an observable result of value to an actor. An actor represents a
role that a human, a hardware device or another system plays with the system.
Use cases are used to a common understanding with the systems end users and the
domain experts. The purpose of use case diagram is to Captured the dynamic aspect of a
system. The use cases do not mention any specific algorithm to be used or the internal
data representation, internal structure of the software etc.
A class diagram in is a type of static structure diagram that describes the structure of a
system by showing the system's classes, their attributes, operations (or methods), and
the relationships among objects. A class is a set of objects that share a common structure
and common behavior. A class is an abstraction of real world items. When these items
exist in the real world they are instances of the class and are referred to as objects the
attribute and operation sections of the class box can be suppressed to reduce detail in an
overview. Suppressing a section makes no statement. Absence of attributes or operations,
but drawing an empty section explicitly states that there is no element in that part.
Classes:
Active Classes:
Active classes initiate and control the flow of activity, while passive classes stores
data and serve other classes.
Visibility:
Use visibility markers to signify who can access the information contained within
class.
Association:
An entity relationship diagram shows the relationships of entity sets stored in a database.
An entity in this context is a component of data. In other words, ER diagrams illustrate
the logical structure of database.
When documenting a system or process, looking at system in multiple ways increases the
understanding of that system. ERD diagram are commonly used in conjunction with a
data flow diagram to display the contents of data store. They help us to visualize how data
is connected in a general way, and are the particularly useful for constructing a relational
database. In the context of structured analysis, the ERD defines all data that are entered,
stored, transferred, and produced within an application.
ERD is detailed logical representation of the data of any system has three main element:
Object, Attribute, and their Relationship.
Figure 4 : ER Diagram
5.3.3 Activity diagram
Arrows run from start towards the end and represent the order in which activities happen.
A data flow diagram illustrates how data is processed by a system in terms of input and
outputs. As its name indicates its focus is on the flow of information, where data comes
from, where it goes and how it gets stored.
DFD Layers:
Draw data flow diagrams can be made in several nested layers. A single process node on
high level diagram can expanded to show a more detailed data flow diagram. Draw the
context diagram first, followed by various layers of data flow diagrams.
DFD Levels:
The first level DFD shows the main processes within the system. Each of these processes
can be broken into further processes until you reach pseudo code.
0- Level:
Faculty:
Column Name Data Type Constraints Description
f_id Varchar(50) Primary Key Faculty id
Username Varchar(50) - User Name
f_name Varchar(30) - Faculty Name
Department Varchar(30) - Department Name
Address Varchar(50) - Address
f_Type Varchar(20) - Faculty Type
date_of_Joining Date - Date Of Joining
Registration
Column Name Data Type Constraints Description
Id Int(11) Private key Id
Username Varchar(30) - User name
Email Varchar(30) - Email address
Password Varchar(100) - Password
Account:
Column Name Data Type Constraints Description
GPG (IT) P a g e 25
bank_name Varchar(30) - Bank Name
Salary Slip:
Column Name Data Type Constraints Description
Deducation:
Column Name Data Type Constraints Description
scooter_advance - Scooter/Cycle
Int(10) Advance
Earning:
Column Name Data Type Constraints Description
Query:
Column Name Data Type Constraints Description
Chapter 7: Implementation
7.1 Implementation
GPG (IT) P a g e 29
Figure 7.3 : Faculty Login Form
The above figure shows the faculty login form. Here faculty can add his/her valid
username and password then press the submit button.
Software testing is defined as an activity to check whether the actual results match
the expected results and to ensure that the software system isDefect free. It involves
execution of a software component or system component to evaluate one or more
properties of interest.software testing is an investigation conduct to provide
stackholders with information about the quality of the software product or service
under test. software testing can also provide an objective, independent view of the
software to allow the business to appreciate and understand the risks of software
implementation.
white box testing(also known as clear box testing, glass box testing, and transparent box
testing and structural testing, by seeing the source code) tests internal structures or
workings of a program, as opposed to the functionality exposed to the end-user. In white-
box testing, as internal perspective of the system, as well as programming skills, are used
to design test cases. The tester chooses inputs to exercise path through the code and
determine the appropriate outputs. This is analogous to testing nodes in a circuit, e.g.in-
circuit testing(ICT).
While white-box testing can be applied at the unit, integration and system levels of the
software testing process, it is usually done at the unit level. It can test paths within a
unit,
paths between units during integration, and between subsystems during a system-level
test.
The above Black-Box can be any software system you want to test. For Example, an
operating system like Windows, a website like Google, a database like Oracle or even
your own custom application. Under Black Box Testing, you can test these
applications by just focusing on the inputs and outputs without knowing their internal
code implementation.
This method is named so because the software program, in the eyes of the tester, is
like a black box; inside which one cannot see. This method attempts to find errors in
the following categories:
GPG (IT) P a g e 36
166150316049 PAYROLL MANAGEMENT SYSTEM
166150316058
166150316059
Conclusion
Payroll management system project develop for an organization has been design
to achieve maximum efficiency and reduce the time taken to handle payroll activity. It is
design to replace an existing manual record system thereby reducing time taken for
calculation and for storing data. The system uses PHP as a front end and MySQL as back-
end for the database. The system is strong enough to withstand regressive daily operation
under conditions where database is maintain and cleared over certain time of span. The
implementation of system in the organization will considerably reduce the data entry time
and also provide readily calculated reports.
Future-Work
In payroll management system we can include tax calculation module for
faculties. So that faculties can add their proposed tax deduction details at the start of year.
Based on these details income tax value automatically calculated for every month
deduction in salary slip generation. In payroll management system we can also take into
consideration an important factor no of leaves for the calculation of salary by adding
module related to leave management.
GPG (IT) P a g e 37
REFERENCES
1) https://www.geeksforgeeks.org/software-engineering-iterative-waterfall-model
2) www.creately.com
3) www.quora.com
4) www.coursehero.com
5) https://bootsnipp.com/snippets/2REg
6) Fundamentals of software development, Madhav Ajvalia
7) Fundamentals of software Engineering, Rajib Mall