SOFTWARE ENGINEERING

PROJECT

PROJECT-P1

PAYROLL SYSTEM
GROUP-G8

SUBMITTED BY
Neha Tewari
MCA V Sem
0605414061
 ACKNOWLEDGEMENT

We take this opportunity to express our profound sense of

gratitude and respect to all those who helped us throughout the
duration of this project.
We are also deeply thankful to our teacher whose useful
suggestions, gentle and soothing attitude and right directions
helped us a lot to learn in this project and also for her constant
encouragement and support throughout the project
We are four members in the group.Our group is
G8.Members of the project G8 ,hereby declare that all designing and
documentation are original work produced by the group
members.Except for referencing,no duplication of any other work is
done.

Members name Work assigned

Ashutosh Shukla Logical System Design

Disha Mittal Feasibility Study
Mohit Pratap Singh Requirement Analysis
Neha Tewari Designing and Documentation
 CONTENT

Introduction

Identification of Need

Preliminary Investigation

Problem Statement

Information Collection

Objective

Feasibility Study
• Technical Feasibility
• Economical Feasibility
• Operational Feasibility
• Schedule Feasibility

Overview of the project

Design Phase
• Data Flow Diagram
• Entity Relationship Diagram

Testing of the project

Implementation

Maintenance
 INTRODUCTION

We are here to build a new payroll system to replace the existing

system which is hopelessly out of date.This “Payroll System” is
built for an I.T. company.The Enterprise deal with various
functions and reports provided to the employees.The working at
present is basically manual not computerized.It faces lot of
problems in respect to respect to generate a salary slip,deamess
allowances,loan/advances,provident fund, and insurance
policy.There are various problem at bill generation.The new
system will be state of the art and will have a Web-based interface
that allow employees DA set by employee wise, change employee
preferences (such as payment method), and create various
reports.The system will retain information on all the employees in
the company.The system must pay each employee the correct
amount on time, by the method that they specify.They have an
existing system but that system have a lots of problem and our task
is to develop a new system that fulfills all the requirements needed
by the company.

“Payroll system is concerned with accurate and timely

computation of compensation to each individual employee.In
addition , the payroll system generate relevant information inputs
to budgetary control and financial accounting systems.”
 IDENTIFICATION OF NEED

The Pay Roll departments require a software solution so as to

boost up its operations and minimize the procedural delays. The
ultimate objective of making the project is to increase the
efficiency and to retrieve the data or record of the employee in
least possible time. Computerization of salary details is most
important need as it not only results in rapid access of data but also
saves lot of manual effort and most importantly time and capital.

In this phase, the requirement of the project or the software

are identified completely and if found feasible to be made. For this
the identification of the requirement is very necessary so that the
project is worth making. Here the requirement of the organization
is studied in detail.

The main area of identifying the needs of the organization and

customer are:
 Information about the organization.
 Information about the employees working there.
 Information about the salary details.

After this information is collected, the preliminary investigation

is done, in which the software requirement specification is made.

The main aim of requirement of identifying the needs of the

organization is to get to know if the project or the software is
worth to be made and also to know about the missing links and
faults that may occur in future. It reduces the time that may be
wasted if this investigation is not done.

PRELIMINARY INVESTIGATION
The major steps in the preliminary investigation of
requirements analysis phase are as follows:

(1) Information about the customer’s organization is gathered.

The detailed study of the various processes in the
organization and information flow between the processes is
determined. Special chat sessions or interviews are the
popular ways by which the system analyst gathers
information about the organization. The customer may also
be given a questionnaire to determine his requirement.
(2) Information gathered in the first phase is analyzed to find
any ambiguities. If an ambiguity is found, then a special
interview or questionnaire is prepared. This part is very
important in the sense that if any ambiguity remains
unsolved, it may lead to serious errors at later stages.
Ambiguities and contradiction are to be totally removed at
this stage.
(3) Once the information is available about the organization, a
document called Software Requirement Specification (SRS)
is prepared. The SRS document is most important and it may
be understood as a contract between the customer and
software team. All the software development activities are
done according to the SRS document. An SRS document
must contain following:

 Detailed statement of problem.

 Possible alternative solution to problem.
  Functional requirement of the software system.
 Constraints on the software system.

The SRS document must be precise, consistent and complete.

There is no scope for any ambiguity or contradiction in the SRS
document. A SRS document may be organized as problem
statement, introduction to problem, functional requirement of the
system, non-functional requirement of the system, behavioral
description and criteria.

PROBLEM STATEMENT

The existing system is not so much effective in terms of:

• The dearness allowances master is fixed for all employees.

• Annual increment is automatic.
• Extra allowances adjustment is not there.
• PF management is not there.
• Pay bill report for the month and employee wise annual pay
bill report is not available.
• User/owner cannot handle the system properly.
• Wastage of time and money inconvenient.
• Security and others issue
The main drawback is that it is manual system so it requires
lot of time and money as well as a good amount of
employees for each individual task.
 INFORMATION COLLECTION

Information collection is among one of the major task for the

successful completion of the project. The basic need for
information collection is to know the needs of the customer and to
create a presentable interface so that he can put forward his
requirements. Information collection plays a crucial role to
simulate any project to solve the real world problems.

For the task of information collection we made a number of

surveys of various pay roll systems so as to have an idea about the
requirements of the customer. Information was also collected
through net by visiting websites of various organizations .

Since project is made for employees, we collected their salary

details including loans, deductions, allowances etc. Thus the need
of information collection has been justified by us. Without
information collection it would have been difficult for us to create
the project at par with the current needs of the pay roll department.
 OBJECTIVE

While considering the pitfalls in the existing system ,the new

payroll system has the following objective:

• Enhance details of salary in easy and efficient manner.

• Employee can easily access the salary slip from anywhere.
• Check the details of salary at anytime.
• Multiple allowances option should be there.
• Employee can take multiple loans.
• Improved employee service and support.
• Provide quick access to the details of pay bill and
employee information.
• Pay slips can be configured to include a variety of
information items on any desired format.
• Various reports are generated like annual pay bill
report,employee wise reports.
 FEASIBILITY STUDY

Every project is feasible if given unlimited resources and, infinite

time which is an impractical assumption.Unfortunately, the
development of a computer based system is more likely to be
plagued by a scarcity of resources and difficult delivery dates. It is
both necessary and prudent to evaluate the feasibility of project at
the earliest possible time months or years of effort, thousands or
lakhs of rupees and untold professional embarrassment can be
averted if an ill-conceived system is recognized early in the
definition of the proposed system.
Feasibility study is a test of system proposed regarding its
workability, impact on the organization, ability to meet user needs,
and effective use of resources, The main objective of feasibility
study is to test the technical , operational and economical
feasibility of developing the system. Thus , when a new application
is proposed; it normally goes through a feasibility study before it is
approved for development.
The proposed system must be evaluated from a technical point of
view first , and it technically feasible ,its impact on the
organization and staff must be assessed and compatible social and
technical system can be devised, then it must be tested for
economic feasibility.Thus, during feasibility analysis for the
project the following four areas of interest were considered very
carefully.
Technical Feasibility
A study of resources availability may affect the ability to achieve
an acceptable system. The technical feasibility is frequently the
most difficult area to ensure at these stage.Besides objectives,
function, performance is somewhat hazy,anything seems possible
if the right assumptions are made. It is essential that the process of
analysis and definition be conduced in parallel with an assessment
of technical feasibility.

The technical issues usually raised during the feasibility stage of

the investigation include the following:

• Does the necessary technology exist to do what is suggested(

and can it be acquired)?
• Will the proposed system provide adequate responses to
enquiries, regardless of the number or location of users?
• Can the system be expanded if developed?
• Does this technique guarantee accuracy and ease of access
and data security.
The consideration that is normally associated with technical
feasibility includes resources availability of the organization where
the project is to be developed and implemented. By taking thes
factors into consideration before developing, the resources
availability is adequate. Thus this project is considered technically
feasible for development.

Economical Feasibility
A system that can be developed technically and that will be used if
installed must be a good investment for the organization
Economical feasibility deals with evaluation of development cost
weighted against the ultimate income or bebefit derived from the
developed system. Financial benefits must equal or exceed the
costs. The financial and economic questions raised by analysis
during the preliminary investigation are for the purpose of
estimating the following::
• The cost to conduct a full system investigation. The cost for
hardware and software for the application being considered.
 • The benefits in it the form of reduced costs or fewer costly
errors.
Economical justification is generally the “bottom line”
consideration for the most system. Economic justification includes
a broad range of concerns that include cost benefit analysis .Cost
benefit analysis delineates costs for project.Development and
weight them against tangible and intangible benefits of a system.

Operational Feasibility
Proposed projects are beneficial only if they can be turned into
information systems that will meet the organization operating
requirements. Operational feasibility is a consideration about the
working of the system after installation in the company Simply
stated, this system of feasibility asks if the system will work when
it is developed and installed.

The following are the questions that help test the operational
feasibility of a project:
• Is there sufficient support for the project from management
and users? If the current system is will linked and used to the
extent that person will not be able to see reasons for a
change , there may be resistance.
• Are current business methods acceptable to the users?if they
are not ,users my welcome a change that will bring about
more operational and useful systems.
• Have the users been involvement in the panning and
development of the project? Early involvement reduces the
chances of any resistance to the chances of any resistance to
the system and increase the likelihood of successful project.
• Will the project system can cause any harm? Will it produce
poorer results in any respect of the area? Will accessibility of
the information be lost? Will individual’s performance be
poorer after implementation than before?
 Issues that appear to be relatively minor in the beginning have
ways of growing into major problems after
implementation.Therefore all operational aspects must be
considered carefully.

Schedule feasibility
Schedule feasibility is an evaluation of time, which is to taken for
the development of the project.Consideration of the time frame for
the completion of the project is important since delays affect costs,
computer time and other development work.

Feasibility Study of the proposed System

Feasibility refers to a process of the evaluating alternative systems
through cost-benefit analysis so that the most feasible and
desirable system can be selected for development a preliminary
investigation was carried out to know more about the problems and
also to examine the usefulness of the system to be developed. The
feasible study of this is undertaken from four angles:
• Technical
• Economic
• Operational
• Schedule

Technical Feasible: The proposed system is easily developed

using the existing software and hardware. The organization has
adequate resources for development of this project.Hence, this
project is considered technically feasible for development.

Economic Feasible:A project is said to be economically

feasible if it can run by using existing resources and doesnot
require any additional software and hardware.The cost of
developing the system includes all phases should be calculated,the
cost of developing the system should be minimized.The proposed
system is economically feasible mainly because it is developed
using existing software and hardware and may be made available
to the clients free of charge.

Operational Feasibility: The proposed system was developed

after discussion with the users of the system .The organization will
use this “Education Player” to play file and various files this player
also has the facility to the shutting down the desired media
system.This is meant to increase the productivity in long run. The
system is underdeveloped with the user’s involvement.

Schedule Feasibility:Schedule feasibility is a consideration of

the time frame for the completion of the project.Planning the
project in terms of time is very important,if the project is not
planned properly it will have a negative impact on the development
of the system.Taking this criterion into consideration, the system is
planned efficiently can be completed in the allotted period which
was about 1 year.

All the above types of feasibility study were conducted and it was
inferred that the system is feasible and was recommended for
development.
 OVERVIEW OF THE PROJECT

The whole project is divided into six modules. The brief

description of each module can be given by:

Employee Module:It consists of the following:

• Employee joining information
• Employee Profile
• Employee Current Position and Job Profile
• Family background details
• Employee qualification and experience details
• Employee Medical History
• Awards given to employee
• Documents submitted by employee
• Employee extra curricular activities
• Employee training details
• Employee appraisals history
• Facility given to employee

Leave Management System:It consists of the following:

• User defined Leave types
• Leave balance details
• Leave application
• Leave approvals
• Leave rules

Time Management System:It consists of the following:

 • Employee shift and shift rotation
• Employee time management, late coming etc
• Attendance data
• Overtime details

Payroll Management System: It consists of the following:

• User defined salary heads
• Salary formula
• Payslip generation
• Professional tax-slab

Employee Transfer, Promotions & Increments:It consists

of the following:
• Promotion details
• Increment details
• Transfer details

HRD Procedures:It consists of the following:

• Final settlement
• Gratuity
• Superannuation
• Tax calculation
 DESIGN PHASE

DFD(Data Flow Diagram):

DFD is one of several notations that are called structured analysis
technique
It is a graphical tool that allows analyst-users to depict the flow of
data in an system.
It concentrates on the movement of data between processes
DFD evolves four symbols for process modelling
• Data flows
• Data stores
• Process
• Source / sink

The components of the system described during requirement

analysis are the focal point in Design of the New System

System Design consists of the following key elements –

 DATA FLOW –

The data flow describes the movement of data into, around

and out of the System. Data is captured in the System using forms
and is stored in the form of tables in the database. After required
processing this data is displayed in the form of Screens, Reports
and print-outs.

 DATA STORES –
 The data stores describe the temporary or permanent collection
of the data. Various tables have been used for the storage of data

 PROCEDURES :

Different Procedures have been used for collecting, transforming

and displaying the data.

 CONTROLS :

Includes Standards and guidelines for determining whether

activities are occurring in anticipated or accepted manner. The
System has various controls which enable it to be under control
and error - free.

Context level DFD:

1-Level DFD:
2- Level DFD
 ENTITY-RELATIONSHIP DIAGRAM
Entity-relationship diagrams (ER-diagrams) support data
modelling by representing the attributes of data objects and the
relationships between different data objects. You should be
familiar with the concept of ER-diagrams from the units
Elements of information and communication technologies
and Computer-based information systems. If you need to
refresh your memory you should refer to the guide for this unit.
Here just a reminder of the notation that is used within ER-
diagrams:

• Data objects are any composite information that must be

understood by the software (e.g. a thing or an event). Data
objects are represented as boxes.

• Attributes define the properties of a data object and are

represented as circles. One or more attributes are defined as the
primary key. The primary key defines an object.

• Relationships connect the data objects and are represented in

form of arrows or diamonds. Object-relationship pairs are bi-
directional. We can distinguish between 1:1, 1:N and M:N
relationships
 id condition
name value
company value
Emp_code
condition
Policy no DA
id
premium DEDUCTION

Maturity date
Adds_in

INSURANCE/POLICY Minus in
ALLOWANCE

insurance Gross
salary Deduct
Emp_code
year month date
add
adds
da EMI in
PAY BILL id
LOAN/ADV
loan
loan
Emp_code allowance Basic salary
s
premium duration

Net salary

telephone name OTHER

gets ALLOW
Basic pay

Date of joining
value
name
id
EMPLOYEE MASTER
condition
id
Depends
address on
designation Pay group category
Pay id

title
PAY SCALE

paymax

designation
depends

Pay min

Pay
increment

DEPENDENTS
name

number
age
relation
 TESTING OF SOFTWARE
Once the code for a module or function has been written, it is
tested under several conditions. Testing of the code is done to
observe whether it behaves as per the expectation. For testing a
module or function, several test cases are generated and the
behavior of the program is observed. If the output at any test case
is different than expected, then its code could have to be corrected
or it may have to be rewritten. The exhaustive testing of the
program is very difficult and might take a lot of time. The test
cases are so developed that they cover almost every condition .The
testing of software may be categorized as follows:

 Unit testing
 Integration testing
 System testing

UNIT TESTING

The module or function is first unit tested upon

completion of code writing .In unit testing, a module is tested in
isolation. Therefore unit testing is also called isolation .the module
is tested against several test conditions. There are two ways of
code check called Code Walkthrough and Code inspection. Code
Walkthrough is an informal technique for analyzing the quality of
code.
Code inspection is a formal process where the code for a module is
checked in terms of the commonly made errors.
The unit is carried out in two ways:

 Black box testing

  White box testing

BLACK BOX TESTING

Black box testing of a module is done without

bothering the internal architecture of the module. The test cases
developed in the line of SRS document and the behavior of the
module is observed

WHITE BOX TESTING

White box testing mainly focuses on the internal

architecture of the module .The test cases are developed to find
the bugs and errors in the code in the module.

INTEGRATION TESTING

After the unit testing of modules, the module developed

undergoes integration testing. Various modules developed are
integrated according to a certain plan and the test cases are
executed to check whether the various modules work as a single
entity. It is not necessary to put all the modules together to perform
integration testing.

SYSTEM TESTING

The final test is performed after developing all the

modules according to the requirement. The objective of the system
testing is to determine whether the software system performs as per
the requirements mentioned in SRS document. This testing is
known is system testing. A fully developed software product is
system tested. The system testing is done in three phases called
Alpha, Beta and Acceptance Testing.

 The software development team at the developer site

conducts Alpha Testing. The software product containing
all the modules are intermarried and test cases are executed.
If the product is successful, then the next phase called Beta
testing is performed.
 Beta Testing is performed by a group of friendly customers
in the presence of the software development team. The
problem noted and the suggestions made by the customer are
considered. Once the product is successful in Beta testing, it
undergoes Acceptance Testing.
 The customers themselves perform Acceptance Testing. If
the software is successful in acceptance testing, the product is
installed at the customer’s site.

IMPLEMENTATION
The implementation phase is less creative phase than system
design. It is primarily concerned with user training, site preparation
, and file conversion. When the candidate system is linked to
terminals or remote size, the telecommunication network and test
of the network along with the system are also included under
implementation.
 MAINTENANCE

Once the software is delivered and deployed, it enters

the maintenance phase. All systems need maintenance, but for
other system it is largely due to problems that are introduced due to
aging. Why is maintenance needed for software, when software
does not age? Software needs to be maintained not because some
of its components wear out and need to be replaced, but because
there are often some residual errors in the system that must be
removed as they are discovered. It is commonly believed that the
state of the art today is such that almost all software that is
developed has residual errors, or bugs, in them. Many of these
surfaces only after the system have been in operation, sometimes
for a long time. These errors, once discovered, need to be removed,
leading to the software getting changed. This is sometimes called
corrective maintenance.

Even without bugs, software frequently undergoes

change. The main reason is that software often must be upgraded
and enhanced to include more features and provide more services.
This also requires modification of the software. It has been argued
that once a software system is deployed, the environment in which
it operates changes. Hence, the needs that initiated the software
developed also change to reflect the needs of the new environment.
Hence the software must adapt to the needs of the changed
environment. The changed software then changes the environment,
which in turn requires further change. This phenomenon is
sometimes called the law of software evolution. Maintenance due
to this phenomenon is sometimes called adaptive maintenance.

Thus, maintenance involves understanding the existing

software (code and related documents), understanding the effects
of change, making the change—to both the code and the
documents—testing the new parts (changes), and retesting the old
parts that were not changed.