A

PROJECT REPORT
ON
ONLINE PAYROLL MANAGEMENT
SYSTEM

Submitted to

DEPARTMENT OF MCA (L), IDOL

GAUHATI UNIVERSITY
IN PARTIAL FULFILMENT OF THE DEGREE OF

MASTER OF COMPUTER APPLICATION 2012-2014

Submitted By:
Name: Bishal Baruah
BCA
Roll No: 25120033
 C E R T I F I C A T E

This is to certify that the project entitled “ ONLINE PAYROLL

MANAGEMENT SYSTEM “was performed successfully and sincerely by
Bishal Baruah, student of BCA 6 th Semister, under my guidance in partial
fulfillment of the requirements of the BCA , during the academic session
(2016-2019).

This project report is a bonafide work to the best of my

knowledge and is approved for submission.

Guided By:

BIRINCHI KR MEDHI

ICST

Maligaon, Ghy-12
 ACKNOWLEDGEMENT

We wish to thank those who with their active support and help had
made our project successful. First of all our sincere thanks must particularly
go to Mr Birinchi Kr Medhi, B.E, MD of the ICST Computer Education
Institute, Maligaon,Guwahati for his valuable guidance and all the efforts
he had taken in helping us to carry out our project work.

Last but not least, our many thanks go to our colleagues for his kind
co-operation and help in connection with our project.
 CONTENTS IN DETAILS

CHAPTER 1: INTRODUCTION
1.1 INTRODUCTION

1.2 TITLE OF THE PROJECT

1.3 INTRODUCTION AND OBJECTIVE OF THE PROJECT

CHAPTER 2: PROJECT ANALYSIS

2.1 PROBLEM SOLUTION

2.2 FEASIBILITY STUDY

2.3 SCOPE OF PROPOSE SYSTEM

2.4 HARDWARE AND SOFTWARE USED

CHAPTER 3: STRUCTURED ANALYSIS.

3.1 INTRODUCTION

3.2 CONTEXT DIAGRAM

3.3 DATA FLOW DIAGRM

3.4 ENTITY RELATIONSHIP MODEL.

3.5 DATA DICTIONARY

CHAPTER 4: SYSTEM DESIGN

4.1 INTRODUCTION

4.1.1 LOGICAL DESIGN

4.1.2 PHYSICAL DESIGN

4.2 INPUT DESIGN

4.3 OUTPUT DESIGN

4.4 DATABASE DESIGN

CHAPTER 5: SYSTEM TESTING

 5.1 INTRODUCTION

5.2 TESTING

5.2.1 MODULE TESTING

5.2.2 SYSTEM TESTING

5.2.2.1 PROGRAM TESTING

5.2.2.2 STRING TESTING

5.2.2.3 SYSTEM TESTING

5.2.2.4 USER ACCEPTANCE TESTING

5.2.3 FUNCTIONAL TESTING

5.2.4 STRUCTURAL TESTING

5.2.5 COMBINED STRUCTURAL TESTING AND FUNCTIONAL

5.3 DEBUGGING

CHAPTER 6. SYSTEM SECURITY

7.1 SYSTEM SECURITY MEASURES.

7.2 PREVENTION.

7.3 DETECTION.

7.4 DAMAGE MINIMIZATION.

7.5 PHYSICAL SECURITY.

7.6 ENVIRONMENTAL CONDITION.

7.7 SOFTWARE SECURITY.

7.8 PROTECTION AGAINST VIRUS.

7.9 PASSWORD SECURITY.

CHAPTER 7. CONCLUSION
8.1 SALIENT FEATURES OF THE PROPOSED SYSTEM

8.2 LIMITATIONS OF THE PROJECT

8.3 SCOPE FOR FUTURE WORKS

CHAPTER 8: SCREEN SHOT
CHAPTER 9: CODING
 CHAPTER 1

INTRODUCTION

1.1 TITLE OF THE PROJECT

1.2 INTRODUCTION AND OBJECTIVE OF THE PROJECT

1. “ONLINE PAYROLL MANAGEMENT SYSTEM”

Introduction:

Payroll Management system is to provide an option to generate the salary

automatically every month. This software also equipped with to enter the
attendance of each employee in the organization, it help them to track each
employee attendance, based on this we can generate the salary. The software
built to generate individual pay slip and summary of the payroll. It also has
option to generate the Bank Statement of an Employee. So they can take the
print out of Bank Statement submit to the department. It also provide the
leave details of the Employee.

Objective:
Online payroll Management system is to provide an option to generate the salary
automatically every month. It will provide monthly salary slip of each employee with full
deduction and loan debit. This software also equipped with to enter the attendance of
each employee in the organization, it help them to track each employee attendance, based
on this the system can generate the salary. The software built to generate individual pay
slip and summary of the payroll. It also has option to generate the report for Provident
Fund and ESI. So they can take the print out of Provident Fund and ESI to submit to the
department. So the system will have easy and user friendly interface to provide with the
following online services--
a. New Employee information entry.
b. Attendance registers.
c. Information and update of Basic Pay, Allowances, Deduction etc.
d. Automatic generation of monthly pay slip, salary statement etc.
e. Different report generation regarding employee, attendance etc.
f. Employee can register himself into the system and view the monthly
pay slip, salary statement, Loan premium update etc online

The two main users involved in this system are

a. Employer
b. Administrator

Employer is a resource of the organization who will register in the Payroll

System, then will be given a user id and Password through the can login to the
system and search for their Pay slip and Bank Statement etc.

Administrator is also a resource of the organization from HR department. He will

generate and put all the reports and information in the system.
 CHAPTER 2

PROJECT ANALYSIS

2.1 PROPOSED SYSTEM

2.2 PROJECT CATEGORY

2.3 FEASIBILITY STUDY

2.4 SCOPE OF PROPOSE SYSTEM

2.5 DRAWBACKS

2.6 SOFTWARE HARDWARE REQUTREMENT

Proposed System:

After studying the existing system conclusion can be drawn that it is

highly beneficial to have a computerized system that ensures accurate
information at right time with less manual effort.

The proposed system is “ONLINE PAYROLL

MANAGEMENT SYSTEM”. The main objective of the proposed system
is to computerize the Employee Management System. The proposed system
which I have developed is a computerized management system which is
intended to keep the log of all activities.

The objective of the system is to overcome the drawbacks of

the existing manual system and make a hassle free computerized system.

 Store the data with minimum redundancy.

 Provide updated information.

 Efficient, easy to use, less error prone, accurate.

Project Category:
The project is based on the concept of RDBMS (i.e. Relational Database Management
System)“A database which store data in the form of tables which has related with each
other in as particular manner”.

Feasibility study:
Whenever we design a new system, normally the management will ask for a feasibility
report of the new system. The management wants to know the technicalities and cost
involved in creation of new system.

- Technical feasibility
- Economic feasibility
- Physical feasibility

Technical feasibility:
Technical feasibility involves study to establish the technical capability of the
system being created to accomplish all requirements to the user. The system should be
capable of handling the proposed volume of data and provide users and operating
environment to increase their efficiency.
For example, system should be capable of handling the proposed volume of data
and provide users.

Economic feasibility:
Economic feasibility involves study to establish the cost benefit analysis. Money
spent on the system must be recorded in the form of benefit from the system. The benefits
are of two types:
Tangible benefits:
- Saving man labor to do tedious tasks saves time.
Intangible benefits:
- Improves the quality of organization.

Physical feasibility:
It involves study to establish the time responses of the new system being created.
For e.g., if the new system takes more than one day to prepare crucial finance statement
for the management, wherever it was required in an hour, the system fails to provide the
same.

It should be clearly establish that the new system requirements in the form of time
responses would be completely met with. It may call for increase in cost. If the required
cost is sacrificed then the purpose of the new system may not be achieved even if it was
found to be technically feasible.
Scope of the Project:
The system under consideration must include all those activities that are necessary for the
smooth functioning of the different process. The system will
 Save time

 Enhance data security

 Easy access of information from wherever required.

 Comfort of data maintained.

Advantages:

 Unauthorized user cannot use the system as it is protected by password.

 Searching will be faster, Navigation will be easier.

 Data inconsistency will be eliminated. Latest can be obtained if the files

updated properly.

 Individual reports can quickly view and printed.

Drawbacks:

 All modules are not considering due to limitation of time.

 Personalized security is not implemented in the system.

 Account module is not implemented, which is one of the most important

part of a business system.

Software Requirements:
Programming language - PHP
Web server - WampServer
Database - MySql
Web technologies - HTML, Java script
Operating system - Windows XP, Windows 7
Hardware Requirements:
Processor: Intel Pentium III or IV or above
Memory: 2 GB RAM or above
Monitor: 15” Color Monitor
Keyboard
Mouse
 CHAPTER 3

STRUCTURED ANALYSIS

3.1 INTRODUCTION.

3.2 CONTEXT DIAGRAM

3.3 DATA FLOW DIAGRAM

3.4 ENTITY RELATIONSHIP MODEL.

3.5 DATA DICTIONARY

3.1 INTRODUCTION

Structured analysis is a set of techniques and graphical tools that allows us to

develop a new kind of system specification that is easily understandable to the
developer. It is the detailed step-by-step investigation of related procedures to see what
must be done and to determine the best way of doing it. The objective is to build a
system specification that provides the basis for design and implementation.

The various tools used in structured analysis are-

 Context diagram.
 Data flow diagram.
 E-R Diagram (Entity Relationship model).
 Data dictionary.

3.2 CONTEXT DIAGRAM

In the initial stage of System Analysis, Context Diagram is constructed to show

the higher-level model of a system. It is used to represent pictorially the boundaries of a
system. Expanding the Context Diagram we get the detailed DFD of the system.
Context Diagram is generally used to show the sources of data and the destination
where the processed data goes. From source data is sent for processing and then the
processed data is sent to the destination. The Context Diagram for my project is as
followed:
Loan Summary
View Attendance

View Loan Details Department Information

View Bank Statement Employee Attendance

View Payslip New Bank Statement

Login Update Payslip

Register Online Payroll Login

User Management System Administrator
User id, Passworsd Confirm

Confirm
Confirm

Confirm Confirm

Confirm Confirm

Confirm Confirm

Confirm Confirm

3.3 DATA FLOW DIAGRAM

DFD is a pictorial representation which depicts the different processes at work

within a system. It is used to show the information flow from process to process,
process to store, or store to process. The DFD of the individual processes may be
broken down into forms which may be shown level wise.

The context diagram is the starting point of the DFD. A DFD is a series of
bubbles joined by lines-which represents the data transformations and the lines
represent the data flows in the system. So it is also known as “BUBBLE CHART”.
There are various symbols used to draw a DFD, like-

SQUARE: - A square defines a source (originator) or destination of system

data.
 ARROW: - An arrow indicates data flow- data in motion. It is a pipeline for
flow of information.

CIRCLE: - A circle or bubble represents a process that transforms incoming

data in to outgoing data.

OPEN RECTANGLE: - An open rectangle is a data store- data at rest, or

temporary repository of data.

The first Level DFD of project for Administrator is the following:

 User id, Password 1.1 User id, Password
Administrator Login Process Registration
Confirm User id, Password

New Employee Data 1.2 New Employee Data

Employee Employee
Confirm Confirm

New Department Data 1.3 New Department Data

Confirm Department Department

Department id

Monthly Attendance 1.4 New Attendance Data

Employee Attendance
Confirm Attendance Last Attendance Data

Monthly New Payslip 1.5 Payment Data

Confirm Payslip Payslip

Employee id

Employee
Employee id

Loan Information 1.6 Loan Statement

Loan Loan
Confirm Summery Loan Account

Employee id, Account No 1.7 Employee id, Account No

Bank Bank
Confirm Statement EmployeeAccount Statement
The first Level DFD of project for User is the following:

User id, Password 1.1 User id, Password

User Registration Registration
Confirm User id, Password

User id, Password 1.2 User id, Password

Login Process Login
Confirm Confirm

Month and Year 1.3 Employee id

Confirm Payslip Payslip
Payment Information

View Loan Summary 1.4 Employee id

Loan Loan
Confirm Summary Loan Account

Leave Application 1.5 Leave Details

Confirm Leave Leave

Confirm

1.6

1.7

The Second Level DFD of my project for Administrator is the following:

 User id, Password 2.1 User id, Password
Administrator Cha nge Admin Login
P ass w o r d User id, Password
User id
2.1.1
Confirm Update
Update Password
Password

Employee id 2.2 Employee id

Search Employee
Employee
Employee id
2.2.1
Update
Confirm Employee Update Employee

2.3 Department Data

Department Data Sear ch Department
D epar tm ent
Department Data
2.3.1
U p d a te
Confirm D ep a rtm en t Department Data

Monthly Attendance 2.4 New Attendance Data

Search Attendance
Employee Attendance
New Attendance Data
2.4.1
Update
Confirm Atten dance Update Attendance

2.5
New Payslip Search Payslip Data
Payslip
Payslip
Payslip Data
2.5.1
Update
Confirm Update Payslip
Payslip

2.6
Loan Information New Loan Summary
Search Loan
LoanSummary
New Loan Summary
2.6.1
Update
Confirm Update Loan Data
Loan Data
 3.4 E-R DIAGRAM (ENTITY RELATIONSHIP DIAGRAM)

Entity Relationship Diagram represents the relationship between various entities

and their attributes. Relationship between entities makes up a data structure. There are
three type of relationship we can find in an ERD,

 One to one.
 One to many
 Many to many.

Symbols used in ER diagram are as follows:

1. Entity: An entity is collected of sets of attributes in a data model. We can represent

it by a rectangle box. However there is a weak entity also we can find.

2. Attributes: Attributes are the fields of database we can represent it by an oval.

3. Relationship: Relationship represents various relations between the entities.

Relationships Identifying relationship

4. Lines: Line is nothing but it connects the relationships, attributes and entities.

E-R DIAGRAM FOR

STUDENT INFORMATION MANAGEMENT SYSTEM

The ER Diagram of my project is the following:
 Year
Month
Absent

Emp id

1
For Attendance
M
n
ti o
gna

Process
e si
p. D
Em

Dep
t. Id

1
e

1
Em p. Na m

M N Dep
t. N
Employee am e
Work Department
1
M 1 De
pt.
Ad
dr
s

e ss
Id

ddres

E-
p.

m ail
Em

A
Em p.

In Receive Process
Em p. Id

Mo
nth
Bank Name

1 1 M

Bank To Payslip
Ye

1 1
ar
Bran

Em

Em
p
p.

. Id
ch

Cu

Co
Ac

rre

nt
co

Em
ac
nt

Ba
u

p
t

sic .N
nt

N
Ba

am
o
No

la n

e
ce
 3.5 DATA DICTIONARY:

Data Dictionary is a structured repository of data, which provides detailed

information about the data flowing among functions and to or from data stores. It is
a set of rigorous definitions of all DFD data elements and data structures used to
develop the application. It serves as a valuable document to the organization for
future enhancement. Centralizing all definitions in the dictionary removes the
danger to duplications and inconsistencies. During implementation, it serves as a
common base against which programmers who are working on the system compare
their data descriptions. Also control information maintained for each data element
is cross-referenced in the Data Dictionary.

Most database management system has a Data Dictionary as a standard feature.

Three classes are to be defined in a data dictionary. They are:

 Data elements: It is the smallest unit of data that provide for no further
decomposition.
 Data structure: It is a group of data element handled as a unit.
 Data flows & data stores: They are data structures in motion and data structures
at rest respectively.

In constructing the Data Dictionary the analyst have to consider several

points:

 Each data flow in the DFD has one Data Dictionary entry.
 Definitions must be readily accessible by name.
 There should not be data redundancy in the data definition.
 The procedures for writing definition should be precise.

The Data Dictionary of the proposed “ONLINE PAYROLL MANAGEMENT

SYSTEM” is as follows:
SI NO FIELDNAME DATA TYPE WIDTH CONSTRAINT TABLE

1 Employee_id Varchar 10 Primary Key Employee

2 Employee Name Varchar 20 Non key Employee

3 Department id Varchar 10 Primary Key Employee

4 Department Name Varchar 30 Non key Employee

5 Designation Varchar 10 Non key Employee

6 Date of Joining Date Non key Employee

7 Sex Varchar 10 Non key Employee

8 Address Varchar 40 Non Key Employee

9 Contact No Varchar 20 Non key Employee

10 E-mail Varchar 30 Non key Employee

11 Account No Varchar 20 Primary key Bank

12 Bank Name Varchar 20 Non key Bank

13 Branch Varchar 20 Non key Bank

14 Current Balance Int 11 Non key Bank

15 Employee Address Varchar 40 Non key Bank

16 Loan Name Varchar 30 Non key Bank

17 Loan Amount Int 11 Non key Bank

18 EMI Float Non key Bank

19 Month Varchar 10 Non key Attendance

20 Year Int 11 Non key Attendance

21 CL Int 11 Non key Attendance

22 ML Int 11 Non key Attendance

23 EL Int 11 Non key Attendance

24 Absent Int 11 Non key Attendance

25 Basic Pay Int 11 Non key Pay slip

26 TA Float Non key Pay slip

27 DA Float Non key Pay slip

28 HRA Float Non key Pay slip

29 MA Float Non key Pay slip

30 LIC Float Non Key Pay slip

31 Tax Float Non Key Pay slip

32 GPF Advance Float Non Key Pay slip

33 GPF Closing Balance Float Non Key Pay slip

34 Total deduction Float Non Key Pay slip

35 Gross Pay Float Non key

36 Loan EMI Float Non Key Pay slip

37 Net Float Non Key Pay slip

38 User Name Varchar 20 Primary Key Registration

39 Password Varchar 10 Non Key Registration

40 DOB Date Non Key Registration

41 Posting Varchar 20 Non Key Registration

 CHAPTER 4

SYSTEM DESIGN

4.1 INTRODUCTION

4.1.1 LOGICAL DESIGN

4.1.2 PHYSICAL DESIGN

4.2 INPUT DESIGN

4.3 OUTPUT DESIGN

4.4 DATABASE DESIGN

4.1 SYSTEM DESIGN:

System design is a solution a “how to approach the creation of a new system”. This
important phase is composed of several steps. It provides the understanding and
Procedural details necessary for implementing in the system recommended in the
feasibility study. Emphasis is on translating the performance requirement into design
specification

Design goes through logical and physical stages of development. Logical

design review the present physical system, prepares input and output specification
details the implementation plan and prepares a logical design walkthrough. The
physical design maps out details of the physical system, plans the system
implementation, devices a test and implementation plan and specifies any new
hardware and software.

System design goes through two phases of developments:-

a. Logical Design
b. Physical Design
4.1.1 LOGICAL DESIGN:

We know that the data flow diagram shows the logical flow of the system and defines
the boundaries of the system. A logical design specifies the user needs at the level of
detail that virtually determines the information flow into and out of the system and the
required data resources. Logical design describes the inputs, outputs, databases and
procedures all in a format that meets the user requirements.

4.1.2 PHYSICAL DESIGN:

It provides the working system by defying the design specification that tells the
programmers exactly what the candidate system must do. In short it can state that
physical design is the implementation of the logical design.

Physical system design consists of the following steps:-

1. Design the physical system.

 Specify input/output media
 Design the database and specify backup procedures.
 Design physical information flow through the system and a physical design
walkthrough.
2. Planned system implementation.
 Prepare a conversion schedule and a target date.
 Determining training procedure, course and timetable.
 Device a test and implementation plan and specify any new hardware
/software

 Update benefits costs, conversion date and system constraints (legal, financial,
hardware etc)

System design involves the following design:-

 Input Design
 Output Design
 Database Design
MENU DESIGN:

In any computer system, a user first interact with its menus, therefore it should be
good enough such that the user can feel comfortable while using it.

Like most of the system, the format will be shown along with a list of number, and
users are expected to choose appropriate option by positioning the cursor or keying the
appropriate number. A series of menus allow the user to step through a series of
hierarchical levels of increasing specificity.

The advantage of the well designed menu is that it provides a familiar format and
clear set of choice which were well understood by the user. Menus therefore require
less training than common languages. One important feature of a menu structure is the
capability of back tracking to a higher or returning to the higher level and starting ones.
An ideal interface should have shortcut. Example of a shortcut are menu of menu name
so that a user may immediately specify a lower level menu and a feature to permit
direct writing of a complex command that by passes the menu displays.

4.2 INPUT DESIGN:

Input design is a circle part of any system design. Inaccurate input data are the
most important cause of error in data processing. Data entry can be controlled by input
design. Input design is the process of converting user oriented inputs to computer based
format. The goal of designing input data is to make data entry as easy, logical and free
from errors can possible.

While entering the data the operator needs to know the following:-

 The allocated field for each field.

 Fields sequence which most match that in the source document.
 The format in which data field is entered.

Keeping in view the users requirements, the input screens have been designed
and developed for easy and error free data entry. Based on the various types of inputs to
be fed to the computer in using the proposed system, all input screens are designed in
real mode and help are given in the form of guide the data entry operators step by step.

The Input Form design of the proposed system is given as below:

4.3 OUTPUT DESIGN:

Computer output is the most important and direct source information to the users.
Efficient intelligible output design should improve the system relationship with the user
and help in design making. A major form of the output is a hardcopy from the printer.

In the system, under consideration printout are designed around the output
requirement of the user. The output design can be classified into two groups:

1. Form Design.

2. Report Design.

4.4 DATABASE DESIGN

Usually, a collection of interrelated data is as database. The database contains

information about one particular enterprise. Database system is to stair and manages large
volume of information. The management of data involves both the definition structure of the
storage of information and provision for manipulation of information. In addition the database
system must provide for safety of the information stored in the database, despite system crashes
or unauthorized access.

The lists of tables of the proposed system are given below:

Table name: ADMINISTRATOR LOGIN

 SI FIELD DATA TYPE WIDTH CONSTRAINT
NO

1 Username Varchar 10 Primary Key

2 Password Varchar 10 Non Key

Table name: Employee

SI FIELD DATA TYPE WIDTH CONSTRAINT

NO

1 Employee_id Varchar 10 Primary key

2 Employee_name Varchar 20 Non key

3 Department Id Varchar 10 Foreign Key

4 Department Name Varchar 30 Non key

5 Designation Varchar 10 Non key

6 Sex Varchar 10 Non key

7 Address Varchar 40 Non key

8 Contact No Varchar 20 Non key

9 E-mail Varchar 30 Non key

Table name: DEPARTMENT

SI FIELD DATA TYPE WIDTH CONSTRAINT

NO

1 Department_id Varchar 10 Primary key

2 Department _name Varchar 20 Non key

3 Address Varchar 50 Non key

4 Contact No Varchar 20 Non key

 5 E-mail Varchar 20 Non key

Table name: BANK

SI FIELD DATA TYPE WIDTH CONSTRAINT

NO

1 Employee_id Varchar 10 Foreign key

2 Employee_name Varchar 30 Non key

3 Account_no Varchar 20 Primary Key

4 Bank_name Varchar 20 Non key

5 Employee_address Varchar 40 Non key

6 Contact_no Varchar 20 Non key

7 Loan_name Varchar 30 Non key

8 Loan_amount Varchar 30 Non key

9 E-mail Float Non key

Table name: ATTENDANCE

I FIELD DATA TYPE WIDTH CONSTRAINT

NO

1 Employee_id Varchar 10 Foreign key

2 Employee_name Varchar 20 Non key

 3 Designation Varchar 20 Non key

4 Department Varchar 20 Non key

5 Month Varchar 10 Non key

6 Year Int 11 Non key

7 CL Int 11 Non key

8 ML Int 11 Non key

9 EL Int 11 Non key

10 Absent Int 11 Non key

Table name: LEAVE

I FIELD DATA TYPE WIDTH CONSTRAINT

NO

1 Employee_id Varchar 10 Foreign key

2 CL Int 11 Non key

3 ML Int 11 Non key

4 EL int 11 Non key

Table name: PAY SLIP

SI FIELD DATA TYPE WIDTH CONSTRAINT
NO

1 Employee_id Varchar 10 Foreign key

2 Employee_name Varchar 30 Non key

3 Month Varchar 10 Non key

4 Year Int 11 Non key

5 Basic_pay Int 11 Non key

 6 TA Float Non key

7 DA Float Non key

8 HRA Float Non key

9 MA Float Non key

10 LIC Float Non key

11 Tax Float Non key

12 GPF_advance Float Non key

13 GPF_closing_balnce Float Non key

14 Total_deduction Float Non key

15 Gross_pay Float Non key

16 Loan_emi Float Non key

17 Net Float Non key

Table name: REGISTRATION

SI FIELD DATA TYPE WIDTH CONSTRAINT

NO

1 User_name Varchar 20 Primary Key

2 Password Varchar 10 Non key

3 Employee_name Varchar 20 Non key

4 Employee_id Varchar 20 Foreign Key

5 Date of Birth Date Non key

6 Department Varchar 20 Non key

7 Designation Varchar 20 Non key

8 Posting Varchar 20 Non key

9 Address Varchar 40 Non key

10 Contact_no Varchar 20 Non key

11 E-mail Varchar 20 Non key

 CHAPTER 5

SYSTEM TESTING

5.1 INTRODUCTION

5.2 TESTING

5.2.1 MODULE TESTING

5.2.2 SYSTEM TESTING

5.2.2.1 PROGRAM TESTING

5.2.2.2 STRING TESTING

5.2.2.3 SYSTEM TESTING

5.2.2.4 USER ACCEPTANCE TESTING

5.2.3 FUNCTIONAL TESTING

5.2.4 STRUCTURAL TESTING

5.2.5 COMBINED STRUCTURAL TESTING

5.3 DEBUGGING

5.1 INTRODUCTION

A system should always be tested thoroughly before implementing it, as regards its
individual programs, the system as a whole user acceptance etc. This is because
implementing a new system is a major job, which requires a lot of man, hours and a lot
of other resources, so an error not detected before implementation may cost a lot.
Effective testing early in the process translates directly into long term cost savings from
reduced number of errors. This is also necessary because in some cases, a small error
not detected and corrected before installation may explode into much larger problem.

Testing is done based on the following principles:

1. All tests should be traceable to customer requirement. The objectives of system testing
are to uncover errors.
2. Tests should be planned long before testing begins. Test planning can begin as soon as
requirement model is complete. Therefore, all tests can be planned and designed before
any code has been generated.
3. Testing should begin “in the small” and progress towards testing “in the large”. The
first tests planned and executed generally focus on individual program modules. As
testing progresses, testing shifts focus in an attempt to find errors in integrated clusters
of modules and ultimately in the entire system.
4. Exhaustive testing is not possible. The number of path permutations for even a
moderately sized program is exceptionally large.

For this reason, it is impossible to execute every combinations of path during testing. It
is possible however, to adequately cover program logic and ensure that all conditions in
the procedural design have been exercised.

Programming and testing is followed by the stage of installing the new computer based
system. Actual implementation of the system can begin at this point using either a
parallel or direct change over plan, or some blend of two. The testing and
implementation of the system “ONLINE PAYROLL MANAGEMENT SYSTEM” was
carried out as described below:

5.2 TESTING

5.2.1 MODULE TESTING

The testing of individual modules was completed during the development itself. Some
real data entered manually and necessary testing was completed for each module.
Necessary changes were made there to make sure that the module is working
satisfactorily.

5.2.2 SYSTEM TESTING

The System Testing consists of the following things:

5.2.2.1 PROGRAM TESTING

A program represents the logical elements of a system. For a program to

run satisfactorily, it must compile and test data correctly and tie in properly with other
programs. When a program is tested, the actual output is compared with the expected
output. If there is a discrepancy, the sequences of instructions are tested to determine
the problem. In this system testing is carried out and it showed positive results.

5.2.2.2 STRING TESTING

Programs are invariably related to one another and interact in a total system.
Each portion of the system is tested against the entire module with both test and live
data before the entire system is ready to be tested.

5.2.2.3 SYSTEM TESTING

System testing is designed to uncover weaknesses that were not found in earlier
tests. This includes forced system failure and validation of the total system.

5.2.2.4 USER ACCEPTANCE TESTING

An acceptance test has the objective of selling the user on the validity and reliability of
the system. It verifies the system’s procedures operate to system specification and that
the integrity of vital data is maintained.
5.2.3 FUNCTIONAL TESTING

The functional testing specifies the operating conditions, input values and expected
results. The functional testing in this project results in positive. All the various
operating conditions and expected are accurate. When this test is carried out it does not
arise any situation it is able to take care of all the situations.

5.2.4 STRUCTURAL TESTING

The structural testing is concerned with examining the internal processing logic of a
software system. In the project this test is carried out to make sure that while in the
calculation of excise and invoice, various taxes and total amounts are calculated with
accuracy. In this test all the logical parts are tested very carefully and it resulted in
positive.

5.2.5 COMBINED STRUCTURAL TESTING AND FUNCTIONAL

TESTING

The combining structural and functional testing of all the operating conditions,
input values, expected results along with the internal processing logic of the software
system, which means these combined effort is through the study of the whole system.
The combination of these two testing is also called as the Unit Testing. In this unit
testing the system results is almost accurate in the operating conditions, expected
results along with the internal processing logic of the system.
5.3 DEBUGGING

Debugging occurs as a consequence of successful testing. That is, when a test

case uncovers an error, debugging can and should be an orderly process that
results in removal of the error.

The debugging process will always have one of two outcomes:

1. The cause will be found, corrected and removed.

2. The cause will not be found.

The software was tested vigorously before implementation and when errors were
found they were corrected and removed.
 CHAPTER 6

SYSTEM SECURITY

6.1 SYSTEM SECURITY MEASURES.

6.2 PREVENTION.

6.3 DETECTION.

6.4 DAMAGE MINIMIZATION.

6.5 PHYSICAL SECURITY.

6.6 ENVIRONMENTAL CONDITION.

6.7 SOFTWARE SECURITY.

6.8 PROTECTION AGAINST VIRUS.

6.9 PASSWORD SECURITY.

6.1 SYSTEM SECURITY:

The measures for data protection taken by an organization reflect its awareness
and attitude towards Information Technology. If top management treats computers as a
de-humanized, intangible, but integrity would, at best, be lackadaisical. On the other
hand, if the management considers information as an important recourse and computers
as an aid in decision making one would find a positive approach and involvement by
the management towards security of information. This attitude naturally percolates
down to the lower levels and the workers consider the computer correspondingly as an
enemy.

One of the best and first steps in ensuring data security is to create awareness
and develop a culture within the organization towards the ways in which information
can be lost/alter and what would be the consequences, of such an occurrence, to the
organization and individuals.

All other steps that can be taken are:

 IT ‘Planning: The organization must decide on a policy for introduction of IT.

This must be done at the highest level and should address issues such as levels of
protection for various aspects of information relating to the organization.
 Selection of technology, keeping in mind obsolesces due to new innovations and
necessity for keeping in step;
 Identification of points of exposure of weak links to device means to plug them;
 Physical protection of machine and media.
Control and monitoring the access to data, its usage, by persons and its integrity
must be early defined and responsibility for ensuring these must test on persons
designed for these tasks; an audit procedure would go a long way in ensuring adherence
to laid down guidelines.

While the above are relevant for any computer based MIS implementation, in case
of PCs, the rules acquisition and use must be unambiguously stated. Additional points
to be looked into are:

 Information classification;
 Responsibility for security;
 User training to increase security awareness and propagation of do’s and do not’s.
 Guidelines for creation and changes to passwords etc.
There are four time-honored principles for ensuring security and recovery in
case of breaches of security:

6.2 PREVENTION:

The best method is of course stopping all breaches of security before they occur. ‘Need-
to knows’ policy is an offshoot of the principle of prevention.

6.3 DETECTION:

However one may try to ensure it, total security is almost impossible. The next
principle, therefore, is that one must be able to detect breaches to security, whenever
they occur, within the shortest possible time. This helps in damage assessment and,
also, in devising further preventive measures.

6.4 DAMAGE MINIMIZATION:

 There must be enough resilience in the system to recoup the losses, damage and
become functional, by reinstating the status, at the earliest.

6.5 PHYSICAL SECURITY:

These measures are for PCs being used by us. The measures available are:

 Physically bolt down the PC to a table so that it can’t be casually lifted and taken
away.
 Locate the PC in such a way that it is conveniently accessible to the user, but
hidden from casual passes-by.
 Have likeable cupboards for floppies and keep them locked at all times, except
when used.
 Keyboard and PC locking devices can be fitted so that the PC can’t be operated
unless these locks are opened.
 Keep a record of all floppies in use; don’t permit alien floppies into the
organization.
 Use lockable rooms for PCs, specially those handling sensitive data. Make it a
practice to lock the room when leaving it for even a short time.
 Time above apply to server, gateways and the like.

6.6 ENVIRONMENTAL CONDITIONS:

The PCs are fairly rugged and can tolerate wide ranges of temperatures,
humidity, and voltages. To ensure trouble free and prolonged life, consider the
following measures:

 Have temperature and humidity gauge placed in the close proximity of PC and
keep a casual watch to ensure that condition are within limits. Switch off if the
limits are exceeded.
 If the normal electrical supply is subject to large variations of voltage and
frequency or spikes, it is prudent to have voltage and frequency stabilizers for the
PC.
 Ensure that excessive dust or paper scrap does not accumulate near the PC.
 The plug sockets should fit snugly and cables leading to terminals and printers
should be secured properly and not left hanging.
 We may consider putting a thin transparent plastic cover on the keyboard if it
does not hamper to handling the keyboard.
 The most important is the use of a vacuum cleaner at regular intervals.
6.7 SOFTWARE SECURITY:

There are some measures we can take to ensure that that is not corrupted or
modified by unauthorized users and to reinitiate the database to its known status
in case this happens and these are:

 Use original software for Operating System, Compilers or software packages. We

have to pay for it, but we can then be sure that it would be bug-free, known also
as “licensed” software.
 Use correct procedures for shutting down the PC so that all files etc. would be
properly closed.
 If we develop our own applications, introduce passwords to access our
application; these passwords should not be visible on the screen when keyed-in.
 Keep back-ups of all our files. Whenever we operate on any file, (especially in
update/append/alter mode), if we have our own programs they should include a
“copy” procedure; this ensures that a back up of our data files would always be
automatically taken.

6.8 PROTECTION AGAINST VIRUS:

A number of measures are available for reducing the risk of being attacked by
computer viruses:

-> Build employee awareness of the risk.

-> Don’t allow the use of outside programs for company PCs or networks;

-> Do not interface company networks to out side “Bulletin Boards”

->Make system/server files “Read only”.

-> Try and obtain source code for important software in use and compile it in-
house.

->Check executable code, using “debug” or separate utilities to study code

structure and check spaces for viruses.

6.9 PASSWORD SECURITY:

6.9.1 IDENTIFICATION:
The password only indicates an object with a unique identity is assigned to it. Thus it
should not become authorization to access data without further checks, if some measure
of security is desired.

6.9.2 AUTHENTICATION:

This process verifies that a person or object is who he/she or it claims to be. This
could be achieved by asking some standard questions and getting answers to them; if
the answers match with those held on the systems, the person or object is authenticated.

6.9.3 AUTHORIZATION:

This is the last step in the process; through this, we can ensure that only a given
user, terminal or other resource, can access data to which permission has been
guaranteed to read, write or alter; thus a matrix can be created to indicate which users
have access to which files, records or fields. If the user request passes the matrix he is
allowed to access, otherwise he is denied access to some part of the database.
 CHAPTER 7

CONCLUSION

7.1 SALIENT FEATURES OF THE PROPOSED SYSTEM

7.2 LIMITATIONS OF THE PROJECT

7.3 SCOPE FOR FUTURE WORKS

7.1 SALIENT FEATURES OF THE PROPOSED SYSTEM

There are some silent features of the proposed system:-

 Reduce paper work.

 Easy to operate.
 Reduce man power.
 Maintain quality.
 Easy linking of the various files.

7.2 LIMITATIONS OF THE PROJECT

I have collected the information necessary for the system as much as possible and I have tried
my level best to develop user-friendly software but due to my inexperience and lack of time
there are also some limitations in the system. These are: -

1. Not any special error handling procedure has been used.

2. Although the system is password protected, there is no administrative and operating

system level security.
 7.3 SCOPE FOR FUTURE WORK

Software development is never ending process and continues throughout the life of the
software. The software has been developed keeping in mind easy modification and
enhancement that may be required from time to time.

The software can be effectively used as a Online Payroll Management System to generate
the reports. But some scopes for further enhancement are still left in the system. The system
provides scope for further enhancement depending upon requirements. Even though the system
satisfies user requirements, still more and more additional work can be carried out.
 CHAPTER 8

SCREEN SHOT

Some of the Screen Shot of my Project are the Following:

Screen Shot of the Home/Index Page:

Screen Shot for Admin Login Form:

Screen shot for creating new Employee by Admin:
Screen shot for new Applied Leave Entry by Admin:

Screen shot for processing new Pay slip by Admin:

Screen shot for New Registration by Employee:

Screen shot for User Login by Employee:
Screen shot for searching Pay slip by Employee:

Screen shot for Pay Slip print form by Employee:

 CHAPTER 9
CODING

The following is the for Data Base Connectivity for my Project:

$con=mysql_connect("localhost","root","");

if($con)
{
$dbstatus=mysql_select_db("payroll");
$rs=mysql_query("insert into attendence
values('$empid','$ename','$designation','$department','$month','$year','$cl','$ml','
$el','$absent')");
if($rs)
{
echo "<script>Alert.render('Record inserted
successfully')</script>";
}
else
{
echo "<script>Alert.render('Record not inserted
successfully')</script>";
}
}

else
{
echo "<script>Alert.render('Connection not
successfully')</script>";
}
}*/
?>
The following is the coding for Pay slip Processing:
<?php
session_start();

$empid=$_POST['empid'];
$ename=$_POST['ename'];
$month=$_POST['month'];
$year=$_POST['year'];
$basicpay=$_POST['basicpay'];
$ta=$_POST['ta'];
$lic=$_POST['lic'];
$tax=$_POST['tax'];
$gpfadvance=$_POST['gpfadvance'];
$gpf=$_POST['gpf'];

$con=mysql_connect("localhost","root","");
mysql_select_db('payroll');

if($con)
{
$rs1=mysql_query("select * from attendence where
empid='".$empid."' and month='".$month."'");
if($row=mysql_fetch_array($rs1))
{
$count_absent=$row['absent'];
}

if($count_absent>0)
$absentd=$count_absent*500;
else
$absentd=0;

$rs2=mysql_query("select * from bank where empid='".$empid."'");

if(mysql_num_rows($rs2)<1)
{
echo "<script>alert('No bank record enter for this
employee.')</script>";
}
 else if($row=mysql_fetch_array($rs2))
{
$loan_emi=$row['emi'];
}

$rs3=mysql_query("select Max(gpf_closing_balance) from payslip

where empid='".$empid."'");
if(mysql_num_rows($rs3)<1)
{
$gpfbalance=0;

}
else if($row=mysql_fetch_array($rs3))
{
$gpfbalance=$row['gpf_closing_balance'];
}

$DA=$basicpay*50/100;
$MA=$basicpay*20/100;
$HRA=$basicpay*20/100;
$GP=$basicpay+$ta+$DA+$HRA+$MA;
$total_deduction=$lic+$tax+$gpf+$loan_emi+$absentd;
$net=$GP-$total_deduction;

$gpfbalance=$gpfbalance+$gpf-$gpfadvance;

$rs=mysql_query("insert into payslip

values('$empid','$ename','$month','$year','$basicpay','$ta','$DA','$HRA','$MA','$l
ic','$tax','$gpfadvance','$gpfbalance','$total_deduction','$GP','$loan_emi','$net')");
if($rs)
{
echo "<script>alert('Record inserted successfully')</script>";
header("location:payslip_calculate.php?eid=$empid&en=$ename&month=$month
&year=$year&bp=$basicpay&ta=$ta&da=$DA&hra=$HRA&ma=$MA&lic=$lic&t
ax=$tax&gpfa=$gpfadvance&gpfcb=$gpfbalance&td=$total_deduction&gp=$GP&
emi=$loan_emi&net=$net");
}
else
{
echo "<script>alert('Record not inserted
successfully')</script>";
}
}
else
{
echo "<script>alert('Record not inserted successfully')</script>";
}

?>