Project Report

On
“Payroll Management System”

GAM-IT-P-2018-0010 Lahiru M Suraweera

 Payroll Management System

Contents

Software Development Life Cycle (SDLC) ......................................................................... 3

Introduction to Project ............................................................................................................. 4
Feasibility Analysis ................................................................................................................... 5
1. Technical Feasibility:..................................................................................................... 5
2. Operational Feasibility:................................................................................................. 5
3. Economic Feasibility: .................................................................................................... 5
4. Scheduled feasibility: .................................................................................................... 5
Development Model .................................................................................................................. 6
Requirement Analysis .............................................................................................................. 8
Functional Requirements: ................................................................................................... 8
 Function 1: Administration of the Application..................................................... 8
 Function 2: Manage Employee Data ....................................................................... 9
 Function 3: Designation History .............................................................................. 9
 Function 4: Increment and Incentive Detail ........................................................ 10
 Function 5: Scale Prediction .................................................................................... 10
Non-Functional Requirements: ........................................................................................ 11
 Hardware Requirements : ........................................................................................ 11
 Software Requirements :.......................................................................................... 11
System Design .......................................................................................................................... 12
Testing ........................................................................................................................................ 13
Implementation ........................................................................................................................ 15

2
GAM-IT-P-2018-0010 Lahiru M Suraweera
 Payroll Management System

Software Development Life Cycle (SDLC)

3
GAM-IT-P-2018-0010 Lahiru M Suraweera
 Payroll Management System

Introduction to Project

Industry employs full-time and casual (contractual) academics. Employees in the

Personnel Department will use the system to maintain employee information, manage
leave, and make payments to the academics every fortnight.

The Payroll system can add new employees and delete employees. It can manage annual
and long-service leave as well as record any sick leave. The system must pay each
academic the correct amount, on time, and by the payment method requested by an
academic.

Employees in the Personnel Department will access system via a Windows-based desktop
interface.

However, the system will also provide a web-based access (called Academic Kiosk) to full-
time academics to view their payment details, leave balances, and personal information.
Some of this information, such as personal details and payment method, can be updated
by academics using the web-based interface.

The Payroll system verifies if the total hours worked so far do not exceed the number of
hours agreed in the contract. The contract information is maintained by another system
called Contracts Management, however the Payroll system stores basic information about
contracts, in particular hourly rate for each contract. The industry deducts standard tax
rates from payments made to full-time academics.

Casual academics can request receiving payment notifications by mail or by email.

Fulltime academics employees do not receive payment notifications but they can use
Academic Kiosk to query the system about fortnightly payments, total salaries received
year-to-date, tax and other deductions, leave balances, etc. As mentioned, Academic
Kiosk can be used to modify personal details and payment method.

4
GAM-IT-P-2018-0010 Lahiru M Suraweera
 Payroll Management System

Feasibility Analysis

We have analyzed the feasibility of the system in terms of following spans:

1. Technical Feasibility
2. Operational Feasibility
3. Economic Feasibility
4. Scheduled Feasibility

1. Technical Feasibility: The development process of Payroll Management System

would be advantageous to the organization because we would make use of only
the currently available resources of the organization. All the tools needed for the
development are already available with the organization and the organization does
not have to acquire any new resources. The technical feasibility is also attributed
to the fact that the system does not make use of any additional or external third
party components which can lead to increased load on the system.

2. Operational Feasibility: The Payroll Management System is intended to provide

a very user-friendly and easy to use interface which is beneficial for both the visitors
as well as the operators who help in providing support for the system. This system
would also be easily acceptable among the visitor and administrator, as there is no
need of any special skill set for using the application. This system also benefits the
users as they do not have to download anything on their terminals increasing their
efficiency and ease of use.

3. Economic Feasibility: The Payroll Management System has a very low

development cost. The low cost is attributed to the usage of the existing resources
of the organization. As the website is very user friendly and easy to use, there is no
need to provide special training to the users of the website, thus saving valuable
time and money.

4. Scheduled feasibility: Projects are always given deadlines. Every project is

completed in a specific duration. I was the only working on the project and I had
the project duration of four months only. So i have tried our level best to fulfill each
and every requirement. I had to complete the project in time and if it is not possible
to complete the software in time then I would try our best to fulfill client
requirements.
5
GAM-IT-P-2018-0010 Lahiru M Suraweera
 Payroll Management System

Development Model

The Payroll Management System is a database software application which is developed

using a waterfall software developing model.

The waterfall model is a popular version of the systems development life cycle model for
software engineering. Often considered the classic approach to the systems development
life cycle, the waterfall model describes a development method that is linear and
sequential. Waterfall development has distinct goals for each phase of development.
Imagine a waterfall on the cliff of a steep mountain. Once the water has flowed over the
edge of the cliff and has begun its journey down the side of the mountain, it cannot turn
back. It is the same with waterfall development. Once a phase of development is
completed, the development proceeds to the next phase and there is no turning back.

The advantage of waterfall development is that it allows for departmentalization and

managerial control. A schedule can be set with deadlines for each stage of development
and a product can proceed through the development process like a car in a carwash, and
theoretically, be delivered on time. Development moves from concept, through design,
implementation, testing, installation, troubleshooting, and ends up at operation and
maintenance. Each phase of development proceeds in strict order, without any
overlapping or iterative steps.

The disadvantage of waterfall development is that it does not allow for much reflection
or revision. Once an application is in the testing stage, it is very difficult to go back and
change something that was not well-thought out in the concept stage. Alternatives to the
waterfall model include joint application development (JAD), rapid application
development (RAD), synch and stabilize, build and fix, and the spiral model.

To follow the waterfall model, one proceeds from one phase to the next in a purely
sequential manner. For example, one first completes requirements specification, which are
set in stone. When the requirements are fully completed, one proceeds to design. The
software in question is designed and a blueprint is drawn for implementers (coders) to
follow — this design should be a plan for implementing the requirements given. When
the design is fully completed, an implementation of that design is made by coders.
Towards the later stages of this implementation phase, separate software components
produced are combined to introduce new functionality and remove errors.

6
GAM-IT-P-2018-0010 Lahiru M Suraweera
 Payroll Management System

Thus the waterfall model maintains that one should move to a phase only when its
preceding phase is completed and perfected. However, there are various modified
waterfall models (including Royce's final model) that may include slight or major
variations upon this process.

System
Engineering Analysis
Design
Code
Testing
Maintenance

7
GAM-IT-P-2018-0010 Lahiru M Suraweera
 Payroll Management System

Requirement Analysis

Nowadays, the world is moving at a lightening swiftness and so is computer field. It is

advancing each and every day.

Initially the work of project management was done manually and the data was kept in
files but now the technology is such that each employee who is part of project
management team has all the projects, their phases, reports all at hand.

Due to which user can quickly know regarding the status of any project and its progress.
Such is the technology which is increasing at a very fast pace. This system has been made
so, that user can work faster and in a much better environment.

Functional Requirements:

 Function 1: Administration of the Application

Function Purpose and Priority

Administrator can create new roles/rights/users and edit the existing

roles/rights/users.

Function Inputs

Create User : - User name, Full Name, Password.

Create Rights : - Give rights to the user

Function Operations

Create User : - The admin fills the information about the user and selects rights
to be given to the user clicks on the “Save” button.

Function Outputs

Create User : - New user is created and assigned to the selected rights and then
added in the database.

Edit User : - Changes made to the user information are saved.

8
GAM-IT-P-2018-0010 Lahiru M Suraweera
 Payroll Management System

 Function 2: Manage Employee Data

Function Purpose and Priority

It stores detailed employee profile including his/her personal information,

qualification profile, experience profile and basic salary information.

Function Inputs

Personal Details : Name, Address, Contact, Date of Birth, Sex etc.

Qualification Profile : Qualification, Grade, Passing Year, Institute.

Experience Profile : Worked As, Nos. Working Years, Working Category

Basic Salary Information : Designation, Department, Scale, Date of Joining,

Applicable allowances and deduction and bank information etc.

Function Operations

The employee details can be added, edited and deleted by the users who have
enough authority for the functions.

Function Outputs

The user authentication is checked against the operation used by the user. If user
is not allowed to access the asked operation he/she is reported by the application.

 Function 3: Designation History

Function Purpose and Priority

The past data of the employee designation and his/her progress throughout career
is maintained.

Function Inputs

Designation, Type, Date of Joining, Reason for new designation etc.

Function Operations

The user fills the input details save.

Function Outputs

The current designation is upgraded. New scale is assigned and joining date,
month of increment is changed.
9
GAM-IT-P-2018-0010 Lahiru M Suraweera
 Payroll Management System

 Function 4: Increment and Incentive Detail

Function Purpose and Priority

The functions allows to keep track of the increments/incentives given to the

employee.

Function Inputs

Date, Nos of increment/incentives, Reason.

Function Operations

The user can add increment/incentives records.

Function Outputs

The current basic is upgraded according to the given increment/incentives based

on the employee’s scales.

 Function 5: Scale Prediction

Function Purpose and Priority

This is the analytical tool which allows to generated data showing the normal
progress of any employee in future

Function Inputs

Selects employee, Starting Date (Joining date, Current date), Ending date, and the
years after which the scales should be upgraded.

Function Operations

Generates the data including year and basic of the employee according to the
given inputs.

Function Outputs

Shows graphical view of the generated prediction.

10
GAM-IT-P-2018-0010 Lahiru M Suraweera
 Payroll Management System

Non-Functional Requirements:

 Hardware Requirements :
233 MHz Pentium processor or other compatible

Intel Chipset Motherboard

512 MB SD-RAM

4 GB hard disk

 Software Requirements :
Operating System -Windows 98 onwards

Application Software –Microsoft Visual Basic 6.0

Database Tool – Oracle

11
GAM-IT-P-2018-0010 Lahiru M Suraweera
 Payroll Management System

System Design

Main Flow Diagram

Login

Member? No

Yes

Authenticate No Error Message

User Valid??

Yes

Display Menu
According to user
Rights

12
GAM-IT-P-2018-0010 Lahiru M Suraweera
 Payroll Management System

Testing

Testing plan is one of the modules of the system analysis and the design, which has
greater importance. After system is ready it should go for testing. Testing is one of the
critical phases. The system Developer has to undergo and which one should not avoid
before final system implementation.

If testing is conducted successfully, it will never cover errors in the software. Secondly,
testing demonstrates that software functions appear to be working according to
specification and that performance requirements appear to have been met. In addition,
data collected as testing is conducted provides a good indication of software reliability
and some indication of software quality as a whole. But there is one thing that testing
cannot do:

Testing cannot show the absence of defects, it can only show that software errors are
present. Testing should be planned before testing begins. Test planning can begin as soon
as the coding phase is complete.

During system testing the system is used experimentally to ensure that software does not
fail special test data are input and result examined and likewise corrections are done.

VARIOUS TESTING METHODS ARE:

 Unit Testing

 Integration Testing
 System Testing

 Acceptance Testing

13
GAM-IT-P-2018-0010 Lahiru M Suraweera
 Payroll Management System

Unit Testing

Integration
Testing

System Testing

Acceptance
Testing

 In Unit Testing, we tested individual components like each controls for their validations
to ensure that they operate correctly.
 The next level is called Integration Testing. In this many unit tested modules are
combined into subsystems, which are then tested. The goal here is to see if the
modules can be integrated properly. This testing activity can be considered testing the
design.
 In System Testing, we tested whether system elements have been properly integrated
and perform allocated functions to detect the errors that may result from
unanticipated interactions between sub-system and system components.
 Finally, in Acceptance Testing, we tested whether the system is accepted for
operational use or not.

In this employee management system I have used unit testing & integration testing.

14
GAM-IT-P-2018-0010 Lahiru M Suraweera
 Payroll Management System

Implementation

When a new system needs to be implemented in an organization, there are three different
ways to adopt this new system: The big bang adoption, phased adoption and parallel
adoption.

 Parallel adoption: The old and the new system are running parallel, so all the users

can get used to the new system, and meanwhile do their work using the old system.
 Phased adoption: The adoption will happen in several phases, so after each phase

the system is a little nearer to be fully adopted.

 Big bang adoption: The switch between using the old system and using the new

system happens at one single date, the so called instant changeover of the system.

 Everybody starts to use the new system at the same date and the old system will
not be used anymore from that moment on.

Since our system is completely independent from the existing system and makes no use
of the existing system, the implementation method used is the Big Bang Adoption. User
documentation does not need to be updated during the implementation process,
because it happens in such a short period. There are no special interfaces needed to be
able to get used to the new system, because the new system is all there is.

15
GAM-IT-P-2018-0010 Lahiru M Suraweera
 Payroll Management System

Thank You

16
GAM-IT-P-2018-0010 Lahiru M Suraweera