176330307110

PROJECT REPORT

ON

PAYROLL MANAGEMENT SYSTEM

By

JAYDEV SOLANKI (176330307110)

DEV SHAH (176330307096)
ABHISHEK PATEL (176330307060)

DEPARTMENT OF COMPUTER ENGINEERING

L.J. POLYTECHNIC, AHMEDABAD

2018-2019
 176330307110

DEPARTMENT OF COMPUTER ENGINEERING

L.J. POLYTECHNIC, AHMEDABAD
2018-2019

CERTIFICATE

Date: ___/___/____

This is to certify that Mr. JAYDEV PAYROLL SOLANKI, Mr. DEV SHAH, Mr.
ABHISHEK PATEL from LJ POLYTECHNIC having 176330307110,
176330307096, 176330307060 have completed project documentation on the
problem definition of semester IV during the academic year 2018-19 having Title
MANAGEMEMT SYSTEM in a group consisting of 3 persons.

Institute Guide Head of the Department

 176330307110

ACKNOWLEDGEMENT

The final outcome of this report took a lot of help and dedication from our
colleagues. I would like to sincerely thank them for their efforts. We would also like
to extend our gratitude towards our mentor MS. DHARA SHARMA who have
helped us throughout this report and through the junctures.

We are incredibly thankful for our College and the Computer Department for
providing us with all the helpful materials.

We enjoyed and learnt a lot by creating this report and hope that the same will be
felt from the reader.

JAYDEV SOLANKI (176330307110)

DEV SHAH (176330307096)
ABHISHEK PATEL (176330307060)
 176330307110

INDEX

Sr. Practical Starting Report Sign

no. Date Date
Discuss about software definition and select
1. one.

Create an abstract for selected software

2. definition.

Introduction about the software to be

3. developed.

4. Software Analysis for chosen topic.

5. Case study of Data Dictionary.

6. Case study of E-R Diagram.

7. Case Study of Data Flow Diagram.

8. Study about last phase of SDLC (Testing).

9. Conclusion

10. Bibliography
 176330307110

Table of Contents
ABSTRACT ..............................................................................................................................
Chapter 1 Introduction.......................................................................................................... 1
1.1 Need for the New system ................................................................................................................ 9

1.2 Detailed Problem Definition ........................................................................................................... 9

1.3 Viability of the System ................................................................................................................... 10

1.4 Presently Available Systems for the same ...................................................................................... 10

1.5 Future Prospects .............................................................................................................................. 10

Chapter 2 Analysis .............................................................................................................. 11

2.1 Requirement Analysis ..................................................................................................................... 11

2.2 Project Model .................................................................................................................................. 11

2.3 Schedule Representation ................................................................................................................. 14

2.4 Feasibility Study ............................................................................................................................. 15

Chapter 3 Design ................................................................................................................. 18

3.1 Data Flow Diagram ....................................................................................................................... 18

3.2 ER-Diagram .................................................................................................................................. 20

Chapter 4 System Modelling ................................................................................................ 22
4.1 Database Design............................................................................................................................ 22
Chapter 5 Technical Specification...................................................................................... 25
5.1 Hardware Specification ................................................................................................................. 25

5.1.1 RAM ............................................................................................................................ 25

5.1.2 Hard Drive Storage needed ........................................................................................... 25

5.1.3 Other Hardware requirement ....................................................................................... 25

5.2 Platform ........................................................................................................................................ 25

5.2.1 Supported Operating System ........................................................................................ 25

5.2.2 Programming Server ..................................................................................................... 25

5.2.3 Framework (if any) ....................................................................................................... 25

I
 176330307110

5.3 Programming Languages used ...................................................................................................... 25

5.3.1 Markup Language ......................................................................................................... 25

5.3.2 Programming Language ................................................................................................ 25

5.3.3 Scripting Language (If any) .......................................................................................... 25

5.4 Technical Specification ................................................................................................................. 25

5.4.1 Front-End ..................................................................................................................... 25

5.4.2 Back-End ...................................................................................................................... 25
5.4.3 IDE ................................................................................................................................ 25
5.4.4 UML Tools .................................................................................................................. 25
5.4.5 SRS Tools ..................................................................................................................... 25
Chapter 6 Testing................................................................................................................. 26
6.1 Testing Methods............................................................................................................................ 26
6.1.1 Black Box Testing......................................................................................................... 26
6.1.2 White Box Testing ........................................................................................................ 27
Conclusion ............................................................................................................................ 29
Bibliography ......................................................................................................................... 30

II
 176330307110

Table INDEX

1 Table 1:Schedule Representation ......................................................................................5

2 Table 2:ER-Diagram Symbols ...........................................................................................8
3 Table 3:Data Flow Diagram Symbols .............................................................................11
4 Table 4:Data Dictionary ....................................................................................................14

III
 176330307110

Figure INDEX
1 Figure 1:Iterative Waterfall Model .......................................................................................3
2 Figure 2:Black Box Testing ...................................................................................................14
3 Figure 3:White Box Testing .................................................................................................16

IV
 176330307110

ABSTRACT

In earlier days when the managers and owners have to spent their most of the precious time in the
month end to calculate salary of each employee working in that corresponding company. Today
to overcome this headache and problem we introduce you a system named payroll management
system.

Payroll management system is a system which provides an option to generate salary of each
employee automatically every month. It is the administration of the financial record of employees'
salaries, wages, bonuses, net pay, and deductions per month.

Payroll management system is used to manage and streamline the process of making payments to
employees. Companies use Payroll System to automate such things as calculating payments,
withholding tax and depositing monthly payments into the designated bank account of employees.
This system helps to generate or to track every employee and base on that attendance help to
generate the salary of the employee. This system is made or built for the easy to work in the salary
management system. It best because of the no one kind of mistakes in salary payroll process.
Payroll system is automatic it will help users for the payment to pay the employee Maintain about
the employees when enter in and on about the data of the employee attendance fetchers of the
payroll management team when the month will be finish at that time. It deals with the financial
aspects of employee's salary, allowances, deductions, gross pay, net pay etc. and generation of
pay-slips for a specific period.

V
 176330307110

CHAPTER-1
INTRODUCTION

1.1 Need of the new system

 Managers and owners have to spent their most of the precious time
in the month end to calculate salary of each employee working in that
corresponding company.
 It is also highly prone to human error that can create untimely or
incorrect payments.
 Managing and calculating leaves manually every month for each and
every employee is a part of payroll. This is prone to large errors and
takes up a lot of time.

1.2 Detailed problem definition

 A manual payroll processing system overburdens HR and Finance
teams with mundane activities like documentation and repetitive
cross checking. This system is made to overcome this type of human
errors by providing a clear view to all the employee’s data in a
document format.
 Companies use Payroll System to automate such things as
calculating payments, withholding tax and depositing monthly
payments into the designated bank account of employees.

1.3 Viability of the system

 It deals with the financial aspects of employee's salary, allowances,
deductions, gross pay, net pay etc. and generation of pay-slips for a
specific period.

1
 176330307110

 Payroll software keeps calculations consistent and accurate. It

automatically factors in key items like salary grade, benefits,
expenses, allowances and deductions when processing wages.
 Payroll automation centralizes employment data, such as, contracts,
CBAs, performance records, leaves, timesheets and conversations.
Users with system permission can quickly access the related data
from various devices or platforms.

1.4 Presently available system for the same

 https://factohr.com
A software offering all the modules to cover a user’s entire payroll
process.
 https://kredily.com
An HRMS platform that helps organizations manage the dynamic and
ever connected human resources.
 http://hrone.cloud
Best payroll management software in Delhi NCR. provides services like
automate payroll inputs and F&F settlement.

1.5 Future prospects

 As technology advances, payroll is becoming more seamless process.
 After the software’s growth this system can expand its use of cloud
services as needed without extra hardware purchases and with little
or no software.
 When freelance work on the rise the system will provide option of
instant payments for hourly workers which will be paid immediately
or nearly immediately after they have worked

2
 176330307110

CHAPTER – 2
ANALYSIS

2.1 Requirement Analysis

 After the software’s growth this system can expand its use of cloud
services as needed without extra hardware purchases and with little
or no software.
 When freelance work on the rise the system will provide option of
instant payments for hourly workers which will be paid immediately
or nearly immediately after they have worked.
2.2 Project Model

Feasibility study

Requirement Analysis &

Specification

Design

Coding & Unit Testing

Integration & System

Testing

Maintenance

(Iterative Waterfall Model)

3
 176330307110

 Classical waterfall model is idealistic, it assumes that no defect is

introduced during any development activity.
 But in practice, defects do get introduced in almost every phase of
the life cycle. Even defects may get at much later stage of the life
cycle.
 So, solution of this problem is Iterative Waterfall Model.
 Iterative Waterfall Model is by far the most widely used model.
Almost every other model is derived from the waterfall model.
 The principle of detecting errors as close to its point of introduction
as possible is known as phase containment of errors.

1. Advantages

 Some working functionality can be developed and early in the

software development life cycle (SDLC).

 It is easily adaptable to the ever-changing needs of the project as

well as the client.

 It is best suited for agile organisations.

 It is more cost effective to change the scope or requirements in

Iterative model.

 Parallel development can be planned.

 Testing and debugging during smaller iteration is easy.

4
 176330307110

 Risks are identified and resolved during iteration, and each

iteration is an easily managed.

2. Disadvantage

 More resources may be required.

 Although cost of change is lesser, but it is not very suitable for

changing requirements.

 More management attention is required.

 It is not suitable for smaller projects.

 Highly skilled resources are required for skill analysis.

2.3 Schedule Representation

Generalized project scheduling tools and technique can be applied with

little modification to software projects.
Program evolution and review techniques (PERT) and critical path
method (CPM) are two project scheduling method that can be applied to
software development. Both techniques are driven by information already
developed in earlier project planning activities:

 Estimate of effort.
 A decomposition of the product function.
 The selection of appropriate process model and task set.

5
 176330307110

 Decomposition of tasks.

ACTIVITY START FINISH

DATE DATE

Requirement
Analysis

System Analysis

System Design

System Coding

Testing and
Integration

2.4 Feasibility study

 Operational Feasibility:

Feasibility of the working of the system after the installation in the

organization as mentioned in the feasibility analysis.

 Technical Feasibility:

Technical feasibility is frequently the most difficult area to ensure

at this stage. It is essential that the process of analysis and
definition to be conducted parallel to an assessment of the technical
feasibility.

6
 176330307110

 Economic Feasibility:

An evaluation of development cost is weighted against the ultimate

income or benefits derived from the developed system. There was
no need of extra hardware and software for development of this
project.

 Motivational Feasibility:

An evaluation of the probability that the organization is sufficient

motivation to support the development and implementation of
the application with necessary user participation, resources,
training etc.

 Schedule Feasibility:
An evaluation of the time needed for the development of
this project. The time schedule required for the development of this
project is very important, since more development time effects
machine time, costs and delays in the development of the
other systems.

7
 176330307110

CHAPTER-3

DESIGN

3.1 ER-Diagram
An Entity Relationship (ER) Diagram is a type of flowchart
that illustrates how “entities” such as people, objects or
concepts relate to each other within a system. ER Diagrams are
most often used to design or debug relational databases in the
fields of software engineering, business information systems,
education and research. Also known as ERDs or ER Models,
they use a defined set of symbols such as rectangles, diamonds,
ovals and connecting lines to depict the interconnectedness of
entities, relationships and their attributes. They mirror
grammatical structure, with entities as nouns and relationships
as verbs.

[Table 3.1.1: ER-Diagram Symbols]

Symbols Description
Entity: Data object is real world entity
or thing.

Attributes: An attribute is property of

characteristic of an entity.

8
 176330307110

Relationship: Entity are connected

each other via relations. Generally,
relationships in binary because there are
two entities are related to each other.

Cardinality (One to One): An instance

of entity A can relate to one only
instance of B and vice versa.

Cardinality (One to Many): An

instance of entity A can relate to one or

many instances of B but be can only
relate one instance of A.

Cardinality (Many to One): Many

instances of entity A can relate to one
instances of entity B and vice versa.

9
 176330307110

Cardinality (Many to Many): One or

more instances of entity A can relate to
one more instance of entity B and vice
versa.

3.2 Data Flow Diagram

DFD (data flow diagram) is also known as bubble chart or data
flow graph.
DFD’s are very useful in understanding the system and can be
effectively used during analysis. It shows flow of data through
a system visually. The DFD is a hierarchical graphical model
of a system the different processing activities or functions that
the system performs and the data interchange among these
functions.

10
 176330307110

It views a system as a function that transforms the inputs into

desired output.
Each function is considered as a process that consumes some
input data and produces some output data.
Function model can be represented using DFD.

[Table 3.2.1: Data Flow Diagram Symbols]

Symbols Description
Entity: Entities are external to the
system which interacts by inputting the
data.

System: It shows the system name.

Process: It shows the part of the system

that transforms into outputs.

Data Flow: It passes the data from one

part to another.

11
 176330307110

Data Store: Data store is represented by two

parallel lines. It is generally logical file or
database.

12
 176330307110

CHAPTER-4

SYSTEM MODELING

4.1 Data Dictionary

A data dictionary is a collection of descriptions of the data objects or

items in a data model for the benefit of programmers and others who
need to refer to them. A first step in analyzing a system of objects
with which users interact is to identify each object and its
relationship to other objects. This process is called data modeling
and results in a picture of object relationships. After each data object
or item is given a descriptive name, its relationship is described (or it
becomes part of some structure that implicitly describes
relationship), the type of data (such as text or image or binary value)
is described, possible predefined values are listed, and a brief textual
description is provided. This collection can be organized for
reference into a book called a data dictionary.

When developing programs that use the data model, a data dictionary
can be consulted to understand where a data item fits in the structure,
what values it may contain, and basically what the data item means in
real-world terms. For example, a bank or group of banks could model
the data objects involved in consumer banking. They could then
provide a data dictionary for a bank's programmers. The data
dictionary would describe each of the data items in its data model for

13
 176330307110

consumer banking (for example, "Account holder" and ""Available

credit").

[Table no 4: Data Dictionary]

Primary key:
Foreign key:

Field name Data Size Constraints Description

type
field _name Integer 10 Primary key It specifies field_name.

field Varchar 13 Not null It specifies field name_title.

name_title

14
 176330307110

CHAPTER-5

TECHNICAL SPECIFICATION

5.1 Hardware Specification

• 5.1.1 RAM: 4GB

• 5.1.2 Hard Drive Storage needed: 500GB

• 5.1.3 Other Hardware requirements: No

5.2 Platform

• 5.2.1 Supported Operating System: Window XP,7,8,10 and

MacOS and Linux

• 5.2.2 Programming Server: XAMPP Server 7.2.10

5.3 Framework

• 5.3.1 Markup Language: HTML 5

• 5.3.2 Programming Language: PHP 7.2

• 5.3.3 Scripting Language: Java Script, jQuery

5.4 Technical Specification

• 5.4.1Front-End: HTML 5, CSS4, Java Script, jQuery,

BootStrap4

15
 176330307110

• 5.4.2 Back-End: PHP7.2, MySQL 5.7.23

• 5.4.3 IDE: Sublime Text 3, Eclipse Oxygen 2018-2019 Edition

• 5.4.4 UML Tools: RFF Flow

• 5.4.5 SRS Tools: Microsoft Office 365

16
 176330307110

CHAPTER-6

TESTING

6.1 Testing Methods

6.1.1 Black Box Testing

Black Box Testing is also known as Behavioral Testing or Functional

Testing. It is a technique of testing without having any knowledge of
the internal working of the application.
Black Box Testing treats the software as a “Black Box”- without any

knowledge of internal working and it only examines the fundamental

aspects of the system. This method of test can be applied to each and
every level of software testing such as unit, integration, system and
acceptance testing.

17
 176330307110

[Figure 2: Black Box Testing]

This method attempts to find errors in the following cases:

• Incorrect or missing functions

• Interface Errors

• Errors in structures or external database access

• Behavior or performance errors

• Initialization and termination errors

Advantages:

• Unbiased tests because the designer and tester work independently.

• Tester is free from any pressure of knowledge of specific

programming languages to test the reliability and functionality of an

application / software.
• Test is performed from a user’s point-of-view and not of the designers.

• Test cases can be designed immediately after the completion

of specifications.

Disadvantages:

• Testing every possible input stream is not possible because it is time-

consuming and this would eventually leave many program paths
untested.

18
 176330307110

• Test cases are extremely difficult to be designed without clear and

concise specifications.
• Results might be overestimated at time.

• Cannot be used for testing complex segments of code.

6.1.2 White Box Testing

White Box Testing is a software testing method in which the

internal structure/design/implementation of the item being tested is

known to the tester. The tester chooses inputs to exercise paths through
the code and determines the appropriate outputs. This method is named
so because the software program, in the eyes of the tester, is like a
white/transparent box; inside which one clearly sees.

[Figure 3: White Box Testing]

The aim of this testing is to investigate the internal logic and structure of
the code. That is why white box testing is also known as Structural Testing.

19
 176330307110

Test Cases generated using White Box Testing can:

• Guarantee that all independent paths within a module have been exercised
at least once.
• Exercise all decisions whether they are true or false.

• Exercise external data structure of the program.

Advantages:

• Code optimization by revealing hidden errors.

• Transparency of the internal coding structure which is helpful in deriving

the type of input data needed to test an application effectively.
• Covers all possible paths of a code thereby, empowering a software
engineering team to conduct thorough application testing.
• Enables programmer to introspect because developers can carefully
describe any new implementation.
• Gives engineering-based rules to stop testing an application.

Disadvantages:

• Since tests can be very complex, highly skilled resources are required with
a thorough knowledge of programming and implementation.
• Test script maintenance can be a burden if the implementation changes
too frequently.
• Necessity to create full range of inputs to test each path and condition
make the white box testing method time-consuming.

20
 176330307110

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. 12.Future Application of the Project This project has
many future applications like it can be used in any of the Retail Outlet of Any Type
companies. This project was build keeping in mind all the requirements of these
outlets and they can be implemented in any such type of organization with very few
modifications.

21
 176330307110

BIBLIOGRAPHY

• BOOK REFRENCE

[1] Andrew Hunt, David Hunt, “The Pragmatic Programmer: From

Journeyman to Master”, Addison-Wesley Professional

[2] Robert C. Martin, “Clean Code: A Handbook of Agile Software

Craftmanship”, Prentice Hall

• WEB REFRENCE

[1] https://www.tutorialspoint.com

[2] https://www.w3scools.com

22