09CSA10

Payroll System
Contents
Phase 1

Project Analysis and Planning

1.1.

Study of the Problem

1.2.

Project Scope

1.3.

Objectives

Phase 2

Cost Estimation

Phase 3

Modeling the Requirements

3.1.

Module Description
3.1.1. Login
3.1.2. Employee Details
3.1.3. Salary Details
3.1.4. Modify

3.2.

UML Diagram
3.2.1. Use case Diagram
3.2.2. Class Diagram
3.2.3. Sequence Diagram
3.2.4. Collaboration Diagram

Phase 4

Configuration Management
4.1.

S/W Requirements

4.2.

H/W Requirements

4.3.

Tools

4.4.

Software Development
4.4.1. Form Creation
4.4.2. Script

Phase 5

Software Testing
5.1.

Preparing Test Plan

5.2.

Perform Validation Testing

5.3.

Validation Test Criteria

5.4.

Coverage Analysis

5.5.

Memory Leaks

09CSA10

Synopsis
This is a small scale project for payroll system .The basic idea is
that the manager of the company maintains the details about the
employees, the designation and salary. It consists of employee details,
payroll system, status and exits. The manager can enter the name and
employee ID and get the salary details of that particular employee. In
payroll system we can calculate the net salary of the employee based on
input.
In the Employee details module various details like employee ID,
Name, Designation, Basic pay are obtained from the user.In the Display
module the total database is displayed. In the salary Details module, the
individual database is displayed which shows the PF, DA, HRA and Net
salary of the particular employee. By using the Modify module we can
modify and update the employee personal details on the database stored.

09CSA10

Phase 1 Project Analysis and Planning

1.1.

Study of the Problem

The Payroll processing is critical to businesses and other organizations

because of the significant amounts of money involved in employee remuneration and

the complexity of the legal requirements. This is a small scale project for payroll
processing. The basic idea is that the manager of the company maintains the
information such as companys name, its branches all over. The employee details
maintain the employee ID, Name along with personal information. The total salary
details determine the net pay of the employee. This pay roll processing involves with
two types of users.

USER

ADMINISTRATOR

USERS ROLE:
The users can login/logout the database. He/She can view his/her personal
details, monthly pay details, and company details. The user can just view the
information whereas he/she could not make changes in the database.
ADMINISTRATOR ROLE:
The administrator plays a vital role in the payroll system. The administrator
controls the entire database. The net salary calculations are calculated by the
administrator itself. The main role of the administrator is to safeguard the database.

1.2.

Project Scope
The supplementary specification applies to payroll processing. This
specification defines the non-functional requirement of the system such a

Functionality:
Since it stand alone application, a single user may use it at a time.
Usability:
Desktop interface
Windows 98/2000/Xp
Reliability:
The system is available at 24 hours a day, seven days a week.
Performance:
The performance depends on hardware specification

09CSA10
1.3.

Objectives
The purpose of this document is to define the requirements of payroll

processing. This supplementary specification lists the requirements that are not readily
captured in the use case model. Supplementary specification and the use case model
capture a complete set of requirement of the system.

Phase 2 Cost Estimation

An estimate is a prediction based upon probabilistic assessment. It is the
responsibility of the project manager to make accurate estimations of effort and cost.
This is particularly true for projects subject to competitive bidding where a bid too
high compared with competitors would result in loosing the contract or a bid too low
could result in a loss to the organization. This does not mean that internal projects are
unimportant. From a project leaders estimate the management often decide whether to
proceed with the project. Industry has a need for accurate estimates of effort and size
at a very early stage in a project. However, when software cost estimates are done
early in the software development process the estimate can be based on wrong or
incomplete requirements. A software cost estimate process is the set of techniques and
procedures that organizations use to arrive at an estimate. An important aspect of
software projects is to know the cost, The major contributing factor is effort.
Why SCE is difficult and error prone ?

Software cost estimation requires a significant amount of effort to perform it

correctly.

SCE is often done hurriedly, without an appreciation for the effort required.

You need experience at developing estimates, especially for large projects.

Human bias i.e An Estimator is likely to consider how long a certain portion of
the system would take, and then to merely extrapolate this estimate to the rest of
the system, ignoring the non-linear aspects of software development.

The causes of poor and inaccurate estimation

New software projects are nearly always different form the last.

Software practitioners don't collect enough information about past

projects.

Estimates are forced to match the resources available.

2.1. Cost and Pricing

09CSA10
Our project is of high range and is highly efficient which can satisfy the payroll
calculation for almost all software companies. The chances of error occurrence is very
limited and so our costs around Rs 10, 00,000(app).

A team of 11 members is required for completing the task.

It takes a time span of 3 weeks to shape the project.

There are no specific environmental constraints.

Phase 3 Modeling the Requirements

3.1.

Module Description

3.1.1. Login
It is the login session for the Administrator, User and Exit.
3.1.2. Employee Details
It is used to add employee details into the database.
3.1.3. Net Salary
It is used to determine the employee net salary.
3.1.4. Modify
It is used to modify and any update in the database.

3.2.

UML Diagram

3.2.1. Use case Diagram

Use Case diagrams show the various activities the users can perform on the
system. The System is something that performs a function. They model the dynamic
aspects of the system. It provides a users perspective of the system.

Actor:
An actor is a user of the system playing a particular role.
Use case:
Use case is a particular activity a user can do on the system.
Relationship:
Relationships are simply illustrated with a line connecting actors to use cases.

09CSA10

Empl oyee Detai ls

Val idity Check

Admi nistrator

System
Payroll Processing
Employee

Database
View and Print the Salary Details

3.2.2. Class Diagram

A class diagram describes the types of objects in the system and the various
kinds of static relationships that exist among them.i.e.,A graphical representation of a
static view on declarative static elements. A class is the description of a set of objects
having similar attributes, operations, relationships and behavior.
employee

database

emp id
name
departm ent
age
designation

empid
name
age
designation

system
show details()
validity check()

view()

administrator

payroll
processing
bas ic pay
HRA
PF
net pay
calculation()

3.2.3. Sequence Diagram

empid
name
departm ent
age
basic pay
HRA
PF
net pay
insert()
delete()
update()

09CSA10
A sequence diagram in Unified Modeling Language (UML) is a kind of
interaction diagram that shows how processes operate with one another and in what
order. It is a construct of a Message Sequence Chart. Sequence diagrams are
sometimes called event diagrams, event scenarios, and timing diagrams
administrator

employee

system

database

payroll
processing

provide ID
Enter ID
Validation check

Provide details
Processing

Send details
Give details
View details

3.2.4. Collaboration Diagram

A Collaboration diagram is very similar to a Sequence diagram in the purpose
it achieves; in other words, it shows the dynamic interaction of the objects in a
system. A distinguishing feature of a Collaboration diagram is that it shows the
objects and their association with other objects in the system apart from how they
interact with each other. The association between objects is not represented in a
Sequence diagram. A Collaboration diagram is easily represented by modeling objects
in a system and representing the associations between the objects as links. The
interaction between the objects is denoted by arrows. To identify the sequence of
invocation of these objects, a number is placed next to each of these arrows.

1: provide ID

administrat
or

employee

2: Enter ID
system
7: Give details

8: View details
6: Send details

5: Processing
3: Validation check
4: Provide details
database

payroll
processing

09CSA10

Phase 4 Configuration Management

Configuration management is also used in software development, where it is
called Unified Configuration Management (UCM). Using UCM, developers can keep
track of the source code, documentation, problems, changes requested, and changes
made. An advantage of a configuration management application is that the entire
collection of systems can be reviewed to make sure any changes made to one system
do not adversely affect any of the other systems

4.1.

S/W Requirements
OS: Windows
Language: Visual Basic

4.2.

H/W Requirements
Intel PII Processor with 300 MHz speed.
64 MB RAM
10MB Hard disk space

4.3.

Tools
Design Tool: Rational Rose suite

4.4.

Software Development

4.4.1. Form Creation

Form1:

09CSA10

Form2:

Form3:

09CSA10

Form4:

09CSA10

4.4.2. Script
Coding for form1:
Private Sub Command1_Click()
End
End Sub
Private Sub Command2_Click()
If Text1.Text = "manimaran" And Text2.Text = "welcome" Then
Text1.Text = ""
Text2.Text = ""
Form2.Visible = True
Else
MsgBox "invalid username and password"
Text1.Text = ""
Text2.Text = ""
Text1.SetFocus
End If
End Sub
Coding for form2:
Private Sub Command1_Click()
Form3.Show
End Sub
Private Sub Command2_Click()
Form4.Show
End Sub
Private Sub Command3_Click()
Unload Me
End Sub
Private Sub Command4_Click()
End
End Sub
Coding for form3:
Dim db As Database
Dim rs As Recordset
Private Sub Command1_Click()
Text9.Text = ((Val(Text5.Text) + Val(Text6.Text) + Val(Text7.Text)) (Val(Text8.Text)))
End Sub
Private Sub Command2_Click()
Form4.Show
End Sub

09CSA10

Private Sub Command3_Click()

Unload Me
Unload Form2
End Sub
Private Sub Command4_Click()
End
End Sub
Private Sub Command5_Click()
rs.MoveFirst
Text1.Text = rs(0)
Text2.Text = rs(1)
Text3.Text = rs(2)
Text4.Text = rs(3)
Text5.Text = rs(4)
Text6.Text = rs(5)
Text7.Text = rs(6)
Text8.Text = rs(7)
End Sub
Private Sub Command6_Click()
rs.MovePrevious
Text1.Text = rs(0)
Text2.Text = rs(1)
Text3.Text = rs(2)
Text4.Text = rs(3)
Text5.Text = rs(4)
Text6.Text = rs(5)
Text7.Text = rs(6)
Text8.Text = rs(7)
End Sub
Private Sub Command7_Click()
rs.MoveNext
Text1.Text = rs(0)
Text2.Text = rs(1)
Text3.Text = rs(2)
Text4.Text = rs(3)
Text5.Text = rs(4)
Text6.Text = rs(5)
Text7.Text = rs(6)
Text8.Text = rs(7)
End Sub
Private Sub Command8_Click()
rs.MoveLast
Text1.Text = rs(0)

09CSA10
Text2.Text = rs(1)
Text3.Text = rs(2)
Text4.Text = rs(3)
Text5.Text = rs(4)
Text6.Text = rs(5)
Text7.Text = rs(6)
Text8.Text = rs(7)
End Sub
Private Sub Form_Load()
Set db = OpenDatabase("z:\mani.mdb")
Set rs = db.OpenRecordset("table")
End Sub
Coding for form4:
Dim db As Database
Dim rs As Recordset
Private Sub Command6_Click()
Unload Me
Unload Form3
Unload Form2
End Sub
Private Sub Command7_Click()
End
End Sub
Private Sub Command3_Click()
rs.AddNew
rs(0) = Text1.Text
rs(1) = Text2.Text
rs(2) = Text3.Text
rs(3) = Text4.Text
rs(4) = Text5.Text
rs(5) = Text6.Text
rs(6) = Text7.Text
rs(7) = Text8.Text
rs.Update
MsgBox "record inserted"
End Sub
Private Sub Command4_Click()
Text1.Text = ""
Text2.Text = ""
Text3.Text = ""
Text4.Text = ""
Text5.Text = ""
Text6.Text = ""
Text7.Text = ""

09CSA10
Text8.Text = ""
End Sub
Private Sub Command5_Click()
Unload Me
Form2.Show
End Sub
Private Sub Form_Load()
Set db = OpenDatabase("z:\mani.mdb")
Set rs = db.OpenRecordset("table")
End Sub

Phase 5 Software Testing

5.1.

Preparing Test Plan

Preparing test plan is the first step in the last phase of software development

cycle .The test plan consists of all the activities that had to be done in the software
testing phase. This test plan has been documented using the rational test manager
software.
5.2.

Perform Validation Testing

Software is completely assembled as a package interfacing errors have been

uncovered and a final series of software test validation testing may begin. Validation
successive when the customer is satisfied.
5.3.

Validation Test Criteria

Software validation is achieved through a series of black box test that

demonstrates conformity with requirements.

5.4.

Coverage Analysis
Coverage analysis is used to identify untested code. Using rational pure

coverage, untested code can easily be identified.

09CSA10
5.5.

Memory Leaks
Memory leak testing has been done using rational purity software.

Result:
Based on the system requirements specification PAYROLL INFORMATION
SYSTEM has been designed and implemented.