Payroll Management System
Payroll Management System
CONTENTS
LIST OF FIGURES ……………………………………………………………………………………….
ABSTRACT ………………………………………………………………………………………………
CHAPTER 1: INTRODUCTION............................................................................................................01
1.1 OBJECTIVE….....................................................................................................................02
1.2 PROPOSAL….....................................................................................................................02
1.3 MODULE.............................................................................................................................02
1.4 APPLICATIONS.................................................................................................................03
1.5 FEATURES..........................................................................................................................05
1.6 TRADITIONAL SYSTEM…...............................................................................................06
1.6.1 PROS AND CONS OF TRADITIONAL SYSTEM…..................................06
1.7 INTRODUCTION TO DBMS.............................................................................................07
1.7.1 ADVANTAGES OF DBMS..........................................................................08
1.7.2 COMPONENTS OF DBMS...........................................................................09
CHAPTER 2: SYSTEM REQUIREMENTS...........................................................................................11
2.1 SOFTWARE REQUIREMENTS..........................................................................................11
2.2 HARDWARE REQUIREMENTS........................................................................................11
2.3 SYSTEM TOOLS.................................................................................................................11
2.4 TRIGGER............................................................................................................................13
CHAPTER 3: SYSTEM DESIGN..........................................................................................................15
3.1 REQUIREMENTS AND CONSTRAINTS.........................................................................15
3.1.1 FUNCTIONAL CONSTRAINTS...............................................................................15
3.1.2 CONSTRAINTS.........................................................................................................16
3.2 ENTITIES AND ATTRIBUTES.........................................................................................17
3.3 ENTITY RELATIONSHIP DIAGRAM…..........................................................................20
3.4 SCHEMA DIAGRAM….....................................................................................................21
CHAPTER 4: TESTING.........................................................................................................................24
4.1 INTRODUCTION TO TESTING........................................................................................24
4.1.1 TESTING PROCESS....................................................................................................24
4.1.2 UNIT TESTING............................................................................................................25
4.1.3 INTEGRATED TESTING............................................................................................25
4.1.4 SYSTEM TESTING......................................................................................................25
CHAPTER 5: ANALYSIS AND RESULT..............................................................................................27
5.1 ANALYSIS OF PAYROLL MANAGEMENT.....................................................................27
5.2 WEBSITE SNAPSHOTS........................................................................................................28
5.3 DATABASE SNAPSHOTS....................................................................................................36
CONCLUSION…………………………………………………………………………………………….
BIBLIOGRAPHY.......................................................................................................................................
TABLE OF
CONTENTS
LIST OF
CHAPTER 1
INTRODUCTION
A Database Management System serves as the backbone of the Payroll Management System,
offering a secure and centralized platform for data storage and retrieval. It allows for the
efficient organization of employee information, salary structures, tax records, and other
pertinent data points. Through the implementation of a DBMS, organizations can achieve real-
time access to accurate and up-to-date payroll information, facilitating quick decision-making
processes and ensuring data integrity.
This integration of a Payroll Management System with a DBMS not only minimizes the risk
of errors associated with manual data handling but also enhances data security and
confidentiality. With user-friendly interfaces and advanced reporting capabilities,
organizations can effortlessly manage payroll tasks, generate comprehensive reports, and
ensure compliance with regulatory standards.
1.1 OBJECTIVE
The primary objective of implementing a Payroll Management System integrated with
a Database Management System (DBMS) is to automate and optimize payroll processes,
ensuring accuracy, efficiency, and compliance. This system aims to centralize payroll data,
enhance data security, provide real-time access to information, and streamline reporting,
ultimately contributing to cost reduction and improved overall operational effectiveness.
1.2 PROPOSAL
Problem Statement: Payroll is usually the most expensive part of a business.
Employee attendance systems that use paper sheets are inefficient and make it very easy for
employees to cheat the system by entering incorrect data on the sheet. To avoid the
aforementioned issues, an automatic and flexible system should be implemented, of which
the suggested system is one.
Scope: This project's scope comprises solutions for handling employee personal data,
leave management, personnel actions, calculating payroll, accurately registering employee
attendance using a Biometric Fingerprint Attendance Device, and system authentication and
authorization for software users. Furthermore, the program will generate various reports for
the bureau's senior management in order to aid them in their decision-making process.
Specific users with distinct role kinds, such as manager, administrator, human resource
people, and finance, will be able to change the system database based on their assigned
access capabilities. This software will provide a system for authentication and authorization.
Every user with a specified role type can log in with their username and password and gain
access to the system to which they have been granted access.
1.3 MODULES
The payroll system modules manage an employee's financial records, such as salary,
bonuses, deductions, benefits, and costs, among other things. Payroll administration is one
of the most important tasks that any organization undertakes, but it is also one of the most
complicated and time-consuming.
1.4 APPLICATIONS
A payroll management system can be used across various industries and fields
where there is a need to manage employee compensation and related processes. Here
are some examples:
1. Retail: Retail businesses with both full-time and part-time employees can benefit
from payroll management systems to handle complex pay structures, track hours
worked, and manage employee compensation effectively.
2. Hospitality: Hotels, restaurants, and other hospitality businesses often have a large
and diverse workforce with varying pay rates, shift differentials, and tip allocations. A
payroll management system can help streamline payroll processing and ensure
compliance with labor laws in this industry.
7. Government Agencies: Government agencies at the local, state, and federal levels
have complex payroll requirements due to civil service regulations, union contracts,
and other factors. A payroll management system can help automate payroll processing
and ensure compliance with government regulations.
1. Professional Services: Law firms, accounting firms, consulting firms, and other
professional service providers often bill clients based on employee hours worked. A
payroll management system can help track billable hours, allocate expenses, and
generate accurate invoices for clients.
Overall, a payroll management system can be used in any industry or field where there
is a need to manage employee compensation, track hours worked, and ensure
compliance with labor laws and regulations.
1.5 FEATURES
These are the important features of the project Payroll Management System:
Login Page: The page where the admin users will log in their system credentials
to access the system.
Home Page; The page where the admin will be redirected by default after logging
into the payroll management system.
Department List Page: The page where the admin can admin/staff will manage the
list of their company's departments.
Position List Page: The page where the admin/staff will manage the list of their
company's positions per department.
Allowance List Page: The page where the admin/staff will manage the list
of allowances.
Deduction List Page: The page where the admin/staff will manage the list
of deductions.
Employee List Page: The page where the admin will manage the list of the
employees. This also the page where the admin will manage the employees'
allowances and deductions.
Attendance List Page: The page where the admin will encode and manage the
employees' daily time records.
Payroll List Page: The page where all payroll cut-offs are listed and can be
managed. This also the page where can admin calculate the payroll of employees.
Cut-off Payroll Page: The page where the employees' payroll is listed.
Employee's Pay slip Model: The popup modal that displays the employee's pay slip.
Programs that use these files depend on knowledge about that format.
In earlier days, database applications were built on top of file systems. Basically, it
is a collection of application programs that performs services for end users such asproduction
of reports. Each file defines and manages its own data.
File Processing design approach was well suited to mainframe hardware and
batch input.
Companies mainly use file processing to handle large volumes of structured
data on a regular basis.
It can be more efficient and cost effective in many cases.
Design is simple.
Customization is easy.
Cons
Integrity problems
Databases and database technology have had a major impact on the growing use of computers.
A database is a collection of related data. By data, we mean known facts that can be recorded
and that have implicit meaning. For example, consider the names, telephone numbers, and
addresses of the people you know. Nowadays, this data is typically stored in mobile phones,
which have their own simple database software. In other words, a database has some source
from which data is derived, some degree of interaction with events in the real world, and an
audience that is actively interested in its contents. A database can be of any size and
complexity. For example, the list of names and addresses referred to earlier may consist of
only a few hundred records, each with a simple structure. On the other hand, the computerized
catalogue of a large library may contain half a million entries organized under different
categories.
A database is designed, built, and populated with data for a specific purpose. It has
an intended group of users and some preconceived applications in which these
users are interested.
A database management system (DBMS) is a computerized system that enables users to create
and maintain a database. The DBMS is a general-purpose software system that facilitates the
processes of defining, constructing, manipulating, and sharing databases among various users
and applications. Defining a database involves specifying the data types, structures, and
constraints of the data to be stored in the database. The database definition or descriptive
information is also stored by the DBMS in the form of a database catalogue or dictionary; it is
called meta-data. Constructing the database is the process of storing the data on some storage
medium that is controlled by the DBMS. Manipulating a database includes functions such as
querying the database to retrieve specific data, updating the database to reflect changes in the
mini world, and generating reports from the data. Sharing a database allows multiple users and
programs to access the database simultaneously.
2. Data Integrity
Data integrity means that the data is accurate and consistent in the database. Data
Integrity is very important as there are multiple databases in a DBMS. All of these
databases contain data that is visible to multiple users. So, it is necessary to ensure that
the data is correct and consistent in all the databases and for all the users.
1. Data Security
Data Security is vital concept in a database. Only authorized users should be allowed to
access the database and their identity should be authenticated using a username and
password. Unauthorized users should not be allowed to access the database under any
circumstances as it violates the integrity constraints.
2. Privacy
The privacy rule in a database means only the authorized users can access a database
according to its privacy constraints. There are levels of database access and a user can
only view the data he is allowed to. For example - In social networking sites, access
constraints are different for different accounts a user may want to access.
Database Management System automatically takes care of backup and recovery. The
users don't need to backup data periodically because this is taken care of by the DBMS.
Moreover, it also restores the database after a crash or system failure to its previous
condition.
4. Data Consistency
Data consistency is ensured in a database because there is no data redundancy. All data
appears consistently across the database and the data is same for all the users viewing
the database. Moreover, any changes made to the database are immediately reflected to
all the users and there is no data inconsistency.
DBMS: Software that allows users to create and manipulate database access.
CHAPTER 2
SYSTEM REQUIREMENTS
This section describes the software and hardware requirements of the system.
RAM: At least 4GB RAM for development; more may be needed for production
depending on project complexity and traffic.
Storage: Enough storage space for project files, database files, and XAMPP installation.
Network: Stable internet connection for downloading XAMPP and additional tools.
The various system tools that have been used in developing both the front end and the back end
Front end
JavaScript (JS)
It is a dynamic computer programming language. It is most commonly used as part of web
browsers, whose implementations allow client-side scripts to interact with the user, control the
browser communication asynchronously, and alter the document content that is displayed.
JavaScript is used to create pop-up windows displaying different alerts in the system like “User
registered successfully”, “Product added to cart” etc.
Backend
PHP
PHP is a server-side scripting language that is embedded in HTML. It is used to manage
dynamic content, databases, session tracking, and even build entire e-commerce sites. It is
integrated with a number of popular databases, including MySQL, PostgreSQL, Oracle,
Sybase, Informix, and Microsoft SQL Server.
XAMPP
XAMPP is an abbreviation where X stands for Cross-Platform, A stands for Apache, M stands
for MYSQL, and the Ps stand for PHP and Perl, respectively. It is an open-source package of
web solutions that includes Apache distribution for many servers and command-line
executables along with modules such as Apache server, MariaDB, PHP, and Perl. XAMPP
helps a local host or server to test its website and clients via computers and laptops before
releasing it to the main server. It is a platform that furnishes a suitable environment to test and
verify the working of projects based on Apache, Perl, MySQL database, and PHP through the
system of the host itself.
2.4 TRIGGER
A trigger is a special type of stored procedure that automatically runs when an event occurs in
the database server. DML triggers run when a user tries to modify data through a data
manipulation language (DML) event. DML events are INSERT, UPDATE, or DELETE
statements on a table or view. The trigger used in our database is used to convert the length of
the song, which is entered in the form of minutes, into seconds and then store the value of the
second in the database under the length attribute of the track table. DML triggers are commonly
used to enforce data integrity constraints, audit changes to the database, or automate certain
tasks based on data modifications.
They can be used to enforce complex business rules that cannot be easily implemented
using constraints or to maintain derived data or computed columns in the database.
3. DML Triggers: DML triggers are special stored procedures in a database that are
automatically executed when certain data manipulation language (DML) events occur,
such as INSERT, UPDATE, or DELETE statements on a table or view.
1. Functionality: Upon triggering, the trigger calculates the length of the song from
minutes to seconds. This involves converting the length value entered in minutes into
seconds and then storing the calculated value in the database under the "length"
attribute of the "track" table.
CHAPTER 3
SYSTEM DESIGN
● Logical design
● Physical design
During the logical design phase, the analyst describes inputs (sources), outputs(destinations),
databases (data sores) and procedures (data flows) all in a format that meets the user requirements.
The analyst also specifies the needs of the user at a level that virtually determines the information
flow in and out of the system and the data resources. Here the logical design is done through data
flow diagrams and database design. The physical design is followed by physical design or coding.
Physical design produces the working system by defining the design specifications, which specify
exactly what the candidate system must do. The programmers write the necessary programs that
accept input from the user, perform on necessary processing of accepted data and produce the
required report on a hard copy or display it on the screen. Database Databases are the storehouses
of data used in the software systems. The data is stored in tables inside the database. Several
tables are created for the manipulation of the data for the system. Two essential settings fora
database are Normalization is a technique to avoid redundancy in the tables.
Distributed Database: Distributed Database implies that a single application should be able
to operate transparently on data that is spread across a variety of different databases and
connected by a Communication Network.
Client/Server System
The term client/server refers primarily to an architecture or logical division of
responsibilities, the client is the application (also known as the front-end), and the server is
the DBMS (also known as the back-end).
A client/server system is a distributed system in which,
Some sites are client sites and others are server sites.
All the data resides at the server sites.
All applications execute at the client sites.
User Interfaces
Front-End Software: HTML, CSS, JAVASCRIPT, BOOTSTRAP.
Back-End Software: MySQL
Hardware Interfaces
Windows.
A browser which supports php and html
Security Requirements
Security systems need database storage just like many other applications. However, the
special requirements of the security market mean that vendors must choose their
database partner carefully.
3.1.2 CONSTRAINTS
Constraints on The Relational Database Are Of 4 Types:
Domain Constraints
Key Constraints
Entity Integrity Constraints
Referential Integrity Constraints
1. Domain Constraints:
Every domain must contain atomic values (smallest indivisible units) it means
composite and multi-valued attributes are not allowed.
We perform datatype check here, which means when we assign a data type to
a column, we limit the values that it can contain.
E.g., If we assign the datatype of attribute age as int, we can’t give it values
other than int datatype.
These are called uniqueness constraints since it ensures that every tuple in the
relation should be unique.
A relation can have multiple keys or candidate keys(minimal super key), out of
which we choose one of the keys as primary key, we don’t have any restriction
on choosing the primary key out of candidate keys, but it is suggested to go with
the candidate key with less number of attributes.
Null values are not allowed in the primary key, hence not null constraint is also
a part of key constraint.
o Employee_id
o Log_type
o Datatime_log
o Date_updated
DEDUCTIONS
o Id
o Deduction
o Description
DEPARTMENT
o Id
o Name
EMPLOYEE
o Id
o Employee_no
o Firstname
o Middlename
o Lastname
o Department_id
o Position_id
o Salary
EMPLOYEE_ALLOWANCES
o Id
o Employee_id
o Allowance_id
o Type
o Amount
o Effective_date
o Date_created
EMPLOYEE_DEDUCTIONS
o Id
o Employee_id
o Deduction_id
o Type
o Amount
o Effective_date
o Date_created
PAYROLL
o Id
o Ref_no
o Date_from
o Date_to
o Type
o Status
o Date_created
PAYROLL_ITEMS
o Id
o Payroll_id
o Employee_id
o Present
o Absent
o Late
o Salary
o Allowance_amount
o Allowances
o Deduction_amount
o Deductions
o Net
o Date_created
POSITION
o Id
o Department_id
o Name
USERS
o Id
o Doctor_id
o Name
o Address
o Contact
o Username
o Password
o Type
An ER diagram shows the relationship among entity sets. An entity set is a group of similar
entities and these entities can have attributes. In terms of DBMS, an entity is a table or
attribute of a table in database, so by showing relationship among tables and their attributes,
ER diagram shows the complete logical structure of a database.
The geometric shapes and their meaning in an E-R Diagram. We will discuss these terms in
detail in the next section (Components of a ER Diagram) of this guide so don’t worry too
much about these terms now, just go through them once.
Ellipses: Attributes.
Lines: They link attributes to Entity Sets and Entity sets to Relationship Set
Entity
The entity is the central concept of the Entity-Relationship model. An entity represents a
description of the common features a of the set of objects in the real world. Examples of
entities are Person, Car, Artist, and Album.
Attribute
An Attribute represents the properties of real-world objects that are relevant for the
application purposes. Attributes are associated with the concept of Entity, with the meaning
that all the instances of the entity are characterized by the same set of attributes. In other
words, the entity is a descriptor of the common properties of a set of objects, and such
properties are expressed as attributes.
Relationship
A Relationship represents semantic connections between entities, like the association between
an artist and his/her album, or between an artist and his/her reviews.
The possible values are one and many. Based on their maximum cardinality constraints,
relationships are called
DATAFLOW
The data flow shows the flow of information from a source to its destination. Data flow
is represented by a line, with arrowheads showing the direction of flow. Information always
flows to or from a process and may be written, verbal or electronic. Each data flow may be
referenced by the processes or data stores at its head and tail, or by a description of its contents
DATA STORE
A data store is a holding place for information within the system: It is represented by
an open-ended narrow rectangle. Data stores may be long-term files such as sales ledgers or
may be short-term accumulations: for example, batches of documents that are waiting to be
processed. Each data store should be given a reference followed by an arbitrary number.
CHAPTER 4
TESTING
This includes executing the program with the intent of finding errors. It is important to
distinguish between faults and failures. Software testing can provide objective, independent
information about the quality of software and risk of its failure to users or sponsors. It can be
conducted as soon as executable software (even if partially complete) exists.
Most testing occurs after system requirements have been defined and then implemented in
testable programs. System testing falls within the scope of black-box testing, and as such,
should require no knowledge of the inner design of the code or logic.
In system testing, integration testing passed components are taken as input. The goal of
integration testing is to detect any irregularity between the units that are integrated together.
System testing detects defects within both the integrated units and the whole system.
The result of system testing is the observed behavior of a component or a system when it is
tested. System Testing is a black-box testing. System testing is performed after the integration
testing and before the acceptance testing.
Testing performs a very crucial role in quality assurance and ensuring the reliability of the
software. During testing, the program to be tested is executed as a set of test cases and the
output is performed as expected. The service of testing for errors in a program depends
critically on the test cases.
Unit testing.
Integration Testing
System Testing.
Each module was tested to ensure that the information flows properly into
and out ofthe program unit under test.
Each unit was tested to ensure its proper functioning. Different modules are
testedindependently to ensure that the desired output is obtained by each
module.
The components at the bottom level which have no subordinates are tested.
After combining, different components are linked together to the main menu to
ensure
Testing the fully integrated applications including external peripherals in order to check
how components interact with one another and with the system as a whole. This is also
called the End-to-End testing scenario.
Verify thorough testing of every input in the application to check for desired
outputs. Testing of the user's experience with the application.
CHAPTER 5
ANALYSIS AND RESULTS
5.1 ANALYSIS OF PAYROLL MANAGEMENT
Security is paramount, with robust measures in place to safeguard sensitive payroll data
from unauthorized access or modification. Only authorized personnel can access and
modify information, ensuring data integrity and confidentiality. In essence, a well-
implemented payroll management system optimizes payroll operations, fosters
compliance, enhances employee satisfaction, and bolsters organizational effectiveness.
HOME PAGE
Feedback Form
ATTENDANCE LIST
ATTENDANCE UPDATION
PAYROLL LIST
REPORT GENERATION
TRIGGER IN PAYROLL
EMPLOYEE LIST
DEPARTMENT LIST
JOB LIST
ALLOWANCE LIST
DEDUCTION LIST
USERS
PAYROLL TABLE
USERS TABLE