Вы находитесь на странице: 1из 74

Automated Payroll Processing in an Organization

ABSTRACT

Automated Payroll Processing is a web application based on Client


Server and Electronic payment technology, which is aimed at developing a System that
manages the payment of monthly wages of employees in an organization.

This application is supported by a database consisting of employee’s


salary details and their leave allowances. Based on these details at the end of every month
the application automatically credits the employee’s bank account with their salary. The
amount of salary credited into employees account is a variant of their leave allowances.

This Payroll Processing application also considers employee’s


income tax regulations and loan payment details. Based on these considerations the salary
of each employee is deducted at the source. Taking into account all these aspects the
appropriate accounts of each employee are credited. This application also includes
generation of salary slips to every employee.

Finally our project facilitates the activity of crediting the employee’s


account with their salaries integrated with deductions based on leave allowances, loan
payments and updating of income tax regulations giving a holistic solution to the
Organization.

There are two modules in our project, They are


1. Administrator
2. Employee.

Requirements:
Hardware Requirements:
• Windows Desktop PC’s
• Window Server
Software Requirements:
Server Details:
Operating System :Windows 98/2000/XP
Database (Backend):
MS-SQL server / Oracle, ODBC for Oracle Connectivity.
Front end:
Web browser to run Front end programs developed using HTML,
Java script, Servlets, JSP
Client Details:
Any web browser compatible to run Front end programs.
LBRCE - JKC

Automated Payroll Processing


Release No. 1

User Requirements Document


Version No. 1.0

Institute For Electronic Governance


______________________________________________________________
___
Automated Payroll Processing
Release No. 1

User Requirements Document


Version No.1.0

Prepared By Inspected/Reviewed By Approved By

NAME: Nalini.Y,
Naresh.Ch,
Nishitha.A,
Priyanka.G,
Poornima lavanya.M.

TITLE: Automated Payroll Processing.

SIGNATURE:

DATE: 30-03-07

VERSION HISTORY

Version Date Changed By: Changes Made:


No.
1.0 30-03-07
Automated Payroll Processing

User Requirements Document

Table of Contents

OVERVIEW....................................................................................................................................................................6
CUSTOMER:......................................................................................................................................................................6
PURPOSE:.........................................................................................................................................................................6
SCOPE:............................................................................................................................................................................6
REFERENCES:....................................................................................................................................................................6
GENERAL REQUIREMENTS ....................................................................................................................................7
SYSTEM IN CONTEXT:........................................................................................................................................................7
USER CHARACTERISTICS: ..................................................................................................................................................7
CONSTRAINTS:..................................................................................................................................................................7
SYSTEM-WIDE REQUIREMENTS (RECEIVED):.........................................................................................................................7
SYSTEM-WIDE REQUIREMENTS (DERIVED):........................................................................................................................7
DETAILED REQUIREMENTS....................................................................................................................................8
FUNCTIONAL REQUIREMENTS..............................................................................................................................................8
Use-Case Overview .................................................................................................................................................8
Use-Cases Specifications.......................................................................................................................................10
TECHNICAL REQUIREMENTS..............................................................................................................................................15
Operational Environment:.....................................................................................................................................15
Development Environment:....................................................................................................................................15
........................................................................................................................................................................................18
OVERVIEW..................................................................................................................................................................20
PROBLEM FRAME............................................................................................................................................................20
REFERENCES...................................................................................................................................................................20
INTERFACE REQUIREMENTS ..............................................................................................................................20
USER INTERFACES...........................................................................................................................................................20
HARDWARE INTERFACES...................................................................................................................................................20
SOFTWARE INTERFACES....................................................................................................................................................20
COMMUNICATIONS INTERFACES..........................................................................................................................................20
FUNCTIONAL REQUIREMENTS............................................................................................................................20
FEATURE ANALYSIS.........................................................................................................................................................21
OBJECT ANALYSIS...........................................................................................................................................................25
STATE ANALYSIS.............................................................................................................................................................26
NONFUNCTIONAL REQUIREMENTS...................................................................................................................28
PERFORMANCE REQUIREMENTS..........................................................................................................................................29
SAFETY & RELIABILITY REQUIREMENTS ............................................................................................................................29
SECURITY REQUIREMENTS ...............................................................................................................................................29
SOFTWARE QUALITY ATTRIBUTES......................................................................................................................................29
INTRODUCTION ........................................................................................................................................................34
SCOPE:..........................................................................................................................................................................34
REFERENCES:..................................................................................................................................................................34
GENERAL CONSIDERATIONS................................................................................................................................34
DECISIONS:....................................................................................................................................................................35
DEPENDENCIES:..............................................................................................................................................................35
CONVENTIONS:...............................................................................................................................................................35
DETAILED DESIGN....................................................................................................................................................35
INTRODUCTION.........................................................................................................................................................43
THE “AUTOMATED PAYROLL PROCESSING” HELPS ADMINISTRATOR HONOR THEIR PROFESSIONAL COMMITMENTS BY
FOLLOWING A TAILORED VERSION OF THE ORGANIZATION’S STANDARD PROCESS. .......................................................................43
CONTEXT DIAGRAM........................................................................................................................................................43
REFERENCES...................................................................................................................................................................43
SYSTEM DESCRIPTION...........................................................................................................................................43
SCOPE...........................................................................................................................................................................43
SUCCESS CRITERIA..........................................................................................................................................................44
CONSTRAINTS............................................................................................................................................................44
TECHNICAL CONSTRAINTS................................................................................................................................................44
ARCHITECTURAL REQUIREMENTS...................................................................................................................44
SYSTEM ARCHITECTURE.......................................................................................................................................45
LOGICAL VIEW...............................................................................................................................................................45
USE-CASE SUMMARY......................................................................................................................................................46
ARCHITECTURAL ANALYSIS
.........................................................................................................................................................................................47
AS MVC ARCHITECTURE IS USED FOR THE SYSTEM IT IS EASY TO MAINTAIN QUALITY AND BUSINESS REQUIREMENTS OF THE USER. 47
UTILITY TREE................................................................................................................................................................47
Issue/Decision ....................................................................................................................................................47
........................................................................................................................................................................................51
OVERVIEW..................................................................................................................................................................53
SCOPE:..........................................................................................................................................................................53
REFERENCES:..................................................................................................................................................................53
DOMAIN DEFINITIONS:...........................................................................................................................................54
TABLE DEFINITIONS: ..............................................................................................................................................54
ADMIN..........................................................................................................................................................................54
EMPLOYEE.....................................................................................................................................................................54
DESIGNATION .................................................................................................................................................................55
LEAVE ..........................................................................................................................................................................55
LOAN ...........................................................................................................................................................................56
BANK............................................................................................................................................................................56
SAL SLIP........................................................................................................................................................................57
PURPOSE .....................................................................................................................................................................62
SOFTWARE LIFECYCLE..........................................................................................................................................62
SCHEDULE AND RESPONSIBILITIES ..................................................................................................................63
INTRODUCTION:.......................................................................................................................................................69
........................................................................................................................................................................................70
SCOPE...........................................................................................................................................................................70
REFERENCES...................................................................................................................................................................70
TESTING OBJECTIVE:.............................................................................................................................................70
The objective of the URD is to obtain agreement with the customer regarding
the specifics of the product. Therefore, the URD avoids technical language and notations as
much as possible. The URD provides an overall description of the product, as well as
detailed descriptions of its intended functionality and the desired operational and
development environments.

Overview
The purpose of this section is to obtain agreement regarding the objectives the system must meet.
Ultimately, this segment defines the boundaries of the effort.

Customer: The Automated Payroll Processing System is an application of LBRCE –


JKC. Its target user group consists of Admin, Employees.

Purpose: The Purpose of the project is to maintain the information regarding the
employee and generates the pay slip.

Scope: Generating ID’s and payslips for the employees

References: LBRCE –JKC. User Requirements Document v.1.0.1


LBRCE – JKC High-Level Design v.1.0.1
LBRCE – JKC Software Requirments Specifications v.1.0.1
General Requirements
The purpose of this section is to obtain agreement regarding the characteristics that the system as
a whole must take into account.

System in Context: The “Automated Payroll processing” is an independent system. It is a


web based application.
• Administrator and employee can view the details
through the Login form.
• Administrator undergoes through series of activities and
generates a pay slip for employee.
• Employee can view the salary slip.
User Characteristics:The users are Admin and Employee.
• The Admin will be having the authority for assigning particular
ID to all the employee’s and updates the information of an
employee like Salary details, Loan details, Leave details, Tax
details and generates salary slip for an employee.
• The Employee can enter by using his ID and update his profile,
view earnings, view deductions, view salary slip.
Constraints:
The system displays the entire information of an employee.
The information will be updated by the admin.

RULES:
• The Administrator can only update the information. The updation
of the loan, leave, tax details will be done by administrator only.
• The employee can only update the personal profile. And view the
salary slip.
System-Wide
Requirements • The system generates the pay slip for an employee.
(Received): • The pay slip includes entire information about the earnings,
deductions.
• The employee can view the pay slip.

System-Wide • The employee can update his personal profile.


Requirements • The employee can change password.
(Derived): • The employee can view the salary slip.
Detailed Requirements

Functional Requirements
The purpose of this section is to obtain agreement regarding what the system
will need to do when interacting with outside parties, such as users or other systems.

Use-Case Overview

Use case diagram:


Login

Add New Employee

View Salary details

Administrator

View Loan details


Employee

View Leave details

View Income Tax rules

Credit Employee Account

Generate Salary Slip

Update Profile

View Deductions

View Earnings

Log Out

The table below offers a consolidated view of the Use-Cases. Detailed descriptions of the use
cases are given in the Use-Case Specification section following this table.

Use-Case ID Use-Case Name Priority Stability Verifiability

US_APP_ADM_01 Login High Stable Verifiable


US_APP_ADM_02 Add new employee High Stable Verifiable
US_APP_ADM_03 View Salary details High Stable Verifiable
Use-Case ID Use-Case Name Priority Stability Verifiability

US_APP_ADM_04 View Loan details High Stable Verifiable


US_APP_ADM_05 View Leave details High Stable Verifiable
US_APP_ADM_06 View Tax details High Stable Verifiable
US_APP_ADM_07 Credit employee High Stable Verifiable
acc
US_APP_ADM_08 Generate salary slip High Stable Verifiable
US_APP_ADM_09 Logout High Stable Verifiable

Use-Case ID Use-Case Name Priority Stability Verifiability

US_APP_EMP_01 Login High Stable verifiable


US_APP_EMP_02 Update profile High Stable Verifiable
US_APP_EMP_03 View Earnings High Stable Verifiable
US_APP_EMP_04 View Deductions High Stable Verifiable
US_APP_EMP_05 View salary slip High Stable Verifiable
US_APP_EMP_06 Logout High Stable Verifiable

Use-Cases Specifications

Use-Case ID: US_APP_ADM_01 Use Case Name: Login

Description: The Administrator enters the site through this usecase. This use
case provided with ability to view, update and generate salary slip for an
employee.
Preconditions: Identification of login
Postconditions: Updates leave, loan and tax details and generates pay slip for an
employee
Frequency of Use: Low
Normal Course of Admin logins the system
Events: Checks the details of an employee and generate salary slip
Alternative Courses: Administrator has all rights to view and modify or update the all details
of an employee.

Use-Case ID: US_APP_ADM_02 Use Case Name: Add new employee

Description: The administrator enters the details of new employee. Each employee is
provided id and designation.
Preconditions: The login id of admin is checked and verified. If it was correct then
admin is able to login else rejected.
Postconditions: Updates the employee details.
Frequency of Use: High
Normal Course of The new employee registration will be done.
Events:

Use-Case ID: US_APP_ADM_03 Use Case Name: View salary details

Description: The Administrator view and update the salary details of an


employee.
Preconditions: The administrator enters the particular employee id, month and
year to view the details of an employee.
Postconditions: Updates leave, loan and tax details and generates pay slip for an
employee
Frequency of Use: High
Normal Course of Checks the details of an employee and update salary details.
Events:

Use-Case ID: US_APP_ADM_04 Use Case Name: View Loan details

Description: The Administrator updates the loan details. Based on this details
his salary will be credited.
Preconditions: If the employee id is a valid one. he admin will update the loan
details of corresponding employee.
Postconditions: Updates leave, tax details and generates pay slip for an employee
Frequency of Use: High
Normal Course of The loan details includes EMI, repaid amount, balance amount.
Events:
Use-Case ID: US_APP_ADM_05 Use Case Name: View Leave details

Description: The Administrator updates the leave details. Based on this details
his salary will be credited.
Preconditions: If the employee id is a valid one. The admin will update the leave details
of corresponding employee.
Postconditions: Updates tax details and generates pay slip for an employee
Frequency of Use: High
Normal Course of Based on the type of a leave and number of days the salary will be
Events: credited.

Use-Case ID: US_APP_ADM_06 Use Case Name: View Tax details

Description: The Administrator updates the Tax details. Based on this details
his salary will be credited.
Preconditions: If the employee id is a valid one. The admin will update the tax details of
corresponding employee.
Postconditions: Generates pay slip for an employee
Frequency of Use: High
Normal Course of Based on the tax details his salary is given.
Events:

Use-Case ID: US_APP_ADM_07 Use Case Name: Credit employee account

Description: The salary of an employee is credited into his account.

Preconditions: The entire details of an employee will be updated by the administrator.


Postconditions: Employee can view his salary slip
Frequency of Use: High
Normal Course of The employee salary will be credited in to his bank account.
Events:

Use-Case ID: US_APP_ADM_08 Use Case Name: Generate salary slip

Description: The administrator will update the details of an employee and salary slip
will be generated.
Preconditions: The employee details include loan, leave, tax will be updated.
Postconditions: The employee can view the salary slip.
Frequency of Use: High
Normal Course of The salary slip will be generated.
Events:
Use-Case ID: US_APP_ADM_09 Use Case Name: Logout

Description: After completion of updating employee details administrator exit


from the system.
Preconditions: Employee salary slip is generated
Postconditions: The administrator can update other employee details.
Frequency of Use: High
Normal Course of Administrator exits from this session.
Events:

Use-Case ID: US_APP_EMP_01 Use Case Name: Login

Description: The employee enters the site through this usecase. This use case
provided with update profile, view earnings, view deductions, view
salary slip.
Preconditions: Identification of login.
Postconditions: Employee can update profile
Frequency of Use: High
Normal Course of Employee can update profile and view his earnings, deductions and
Events: salary slip.

Use-Case ID: US_APP_EMP_02 Use Case Name: Update profile

Description: The employee can update his information.The information


include
id, designation, email-id, phone number etc.
Preconditions: The login id of employee is checked and verified. If it was correct then
employee is able to login otherwise rejected.
Postconditions: View earnings, deductions and salary slip.
Frequency of Use: High
Normal Course of Employee can update his information.
Events:

Use-Case ID: US_APP_EMP_03 Use Case Name: View earnings

Description: The employee can view his earnings that are based on his loan,
leave, tax details.
Preconditions: The login id of employee is checked and verified. If it was
correct then employee is able to login otherwise rejected.
Postconditions: Employee views deductions and salary slip.
Frequency of Use: High
Normal Course of Employee can view earnings, deductions and salary slip.
Events:

Use-Case ID: US_APP_EMP_04 Use Case Name: View deductions

Description: The employee can view deductions that are based on his loan,
leave details.
Preconditions: The login id of employee is checked and verified. If it was correct
then employee is able to login otherwise rejected.
Postconditions: Employee can view his salary slip.
Frequency of Use: High
Normal Course of Employee can view deductions.
Events:

Use-Case ID: US_APP_EMP_05 Use Case Name: View salary slip

Description: Employee can view his salary slip

Preconditions: The entire details of an employee will be updated by the administrator.


Postconditions: Employee can view his salary slip
Frequency of Use: High
Normal Course of Employee salary slip can be viewed.
Events:

Use-Case ID: US_APP_EMP_06 Use Case Name: Logout

Description: After completion of viewing employee details employee


exit from the system.
Preconditions: Employee can view his salary slip.
Postconditions: Logout from the system
Frequency of Use: High
Normal Course of Employee exits from this session.
Events:

Technical Requirements
The purpose of this section is to obtain agreement regarding the platforms to be used for
deploying the working systems and for developing the working system. This is input to assist
managerial decisions (i.e., purchasing) as well as technical analysis (i.e., constraints imposed by
the platform).

Operational To run the project in the production mode, one web server and database
Environment: server is needed and one operating system.

Development Requires JSP and remaining same as Operational Environment


Environment:
LBRCE - JKC

Automated Payroll Processing


Release No. 1

Software Requirements Specification


Version No. 1.0

Institute For Electronic Governance


_________________________________________________________________
Automated Payroll Processing
Release No. 1

Software Requirements Specification


Version No. 1.0

Prepared By: Inspected/Reviewed By: Approved By:

NAME: Nalini.Y,
Naresh.Ch,
Nishitha.A,
Priyanka.G,
Poornima lavanya.M.

TITLE: Automated Payroll Processing

SIGNATURE:

DATE: 29-03-07

VERSION HISTORY

Version Date Changed By: Changes Made:


No.
1.0 29-03-
07
Automated Payroll Processing

Software Requirements Specification

Table of Contents

OVERVIEW....................................................................................................................................................................6
CUSTOMER:......................................................................................................................................................................6
PURPOSE:.........................................................................................................................................................................6
SCOPE:............................................................................................................................................................................6
REFERENCES:....................................................................................................................................................................6
GENERAL REQUIREMENTS ....................................................................................................................................7
SYSTEM IN CONTEXT:........................................................................................................................................................7
USER CHARACTERISTICS: ..................................................................................................................................................7
CONSTRAINTS:..................................................................................................................................................................7
SYSTEM-WIDE REQUIREMENTS (RECEIVED):.........................................................................................................................7
SYSTEM-WIDE REQUIREMENTS (DERIVED):........................................................................................................................7
DETAILED REQUIREMENTS....................................................................................................................................8
FUNCTIONAL REQUIREMENTS..............................................................................................................................................8
Use-Case Overview .................................................................................................................................................8
Use-Cases Specifications.......................................................................................................................................10
TECHNICAL REQUIREMENTS..............................................................................................................................................15
Operational Environment:.....................................................................................................................................15
Development Environment:....................................................................................................................................15
........................................................................................................................................................................................18
OVERVIEW..................................................................................................................................................................20
PROBLEM FRAME............................................................................................................................................................20
REFERENCES...................................................................................................................................................................20
INTERFACE REQUIREMENTS ..............................................................................................................................20
USER INTERFACES...........................................................................................................................................................20
HARDWARE INTERFACES...................................................................................................................................................20
SOFTWARE INTERFACES....................................................................................................................................................20
COMMUNICATIONS INTERFACES..........................................................................................................................................20
FUNCTIONAL REQUIREMENTS............................................................................................................................20
FEATURE ANALYSIS.........................................................................................................................................................21
OBJECT ANALYSIS...........................................................................................................................................................25
STATE ANALYSIS.............................................................................................................................................................26
NONFUNCTIONAL REQUIREMENTS...................................................................................................................28
PERFORMANCE REQUIREMENTS..........................................................................................................................................29
SAFETY & RELIABILITY REQUIREMENTS ............................................................................................................................29
SECURITY REQUIREMENTS ...............................................................................................................................................29
SOFTWARE QUALITY ATTRIBUTES......................................................................................................................................29
INTRODUCTION ........................................................................................................................................................34
SCOPE:..........................................................................................................................................................................34
REFERENCES:..................................................................................................................................................................34
GENERAL CONSIDERATIONS................................................................................................................................34
DECISIONS:....................................................................................................................................................................35
DEPENDENCIES:..............................................................................................................................................................35
CONVENTIONS:...............................................................................................................................................................35
DETAILED DESIGN....................................................................................................................................................35
INTRODUCTION.........................................................................................................................................................43
THE “AUTOMATED PAYROLL PROCESSING” HELPS ADMINISTRATOR HONOR THEIR PROFESSIONAL COMMITMENTS BY
FOLLOWING A TAILORED VERSION OF THE ORGANIZATION’S STANDARD PROCESS. .......................................................................43
CONTEXT DIAGRAM........................................................................................................................................................43
REFERENCES...................................................................................................................................................................43
SYSTEM DESCRIPTION...........................................................................................................................................43
SCOPE...........................................................................................................................................................................43
SUCCESS CRITERIA..........................................................................................................................................................44
CONSTRAINTS............................................................................................................................................................44
TECHNICAL CONSTRAINTS................................................................................................................................................44
ARCHITECTURAL REQUIREMENTS...................................................................................................................44
SYSTEM ARCHITECTURE.......................................................................................................................................45
LOGICAL VIEW...............................................................................................................................................................45
USE-CASE SUMMARY......................................................................................................................................................46
ARCHITECTURAL ANALYSIS
.........................................................................................................................................................................................47
AS MVC ARCHITECTURE IS USED FOR THE SYSTEM IT IS EASY TO MAINTAIN QUALITY AND BUSINESS REQUIREMENTS OF THE USER. 47
UTILITY TREE................................................................................................................................................................47
Issue/Decision ....................................................................................................................................................47
........................................................................................................................................................................................51
OVERVIEW..................................................................................................................................................................53
SCOPE:..........................................................................................................................................................................53
REFERENCES:..................................................................................................................................................................53
DOMAIN DEFINITIONS:...........................................................................................................................................54
TABLE DEFINITIONS: ..............................................................................................................................................54
ADMIN..........................................................................................................................................................................54
EMPLOYEE.....................................................................................................................................................................54
DESIGNATION .................................................................................................................................................................55
LEAVE ..........................................................................................................................................................................55
LOAN ...........................................................................................................................................................................56
BANK............................................................................................................................................................................56
SAL SLIP........................................................................................................................................................................57
PURPOSE .....................................................................................................................................................................62
SOFTWARE LIFECYCLE..........................................................................................................................................62
SCHEDULE AND RESPONSIBILITIES ..................................................................................................................63
INTRODUCTION:.......................................................................................................................................................69
........................................................................................................................................................................................70
SCOPE...........................................................................................................................................................................70
REFERENCES...................................................................................................................................................................70
TESTING OBJECTIVE:.............................................................................................................................................70
Overview
The Software Requirements Specification (SRS) begins the translation process that converts the
software requirements into the language the developers will use. The SRS draws on the use-
cases from the User Requirement Document (URD) and analyzes the situations from a number
of perspectives to discover and eliminate inconsistencies, ambiguities, and omissions before
development progresses significantly under mistaken assumptions.
Problem Frame Machine Domain --- Automated Payroll Processing
Problem Domain --- Maintaining employee records, updating
profiles,
. updating loans
References LBRCE –JKC. User Requirements Document v.1.0.1
LBRCE – JKC High-Level Design v.1.0.1
LBRCE – JKC Software Requirments Specifications v.1.0.1
Interface Requirements
This section defines the parameters that the software product must follow while interacting with
the outside world.
User Interfaces 1. Login Screen
2. Menu selection Screen
3. Employee Salary Details
4. Employee Loan Details
5. Employee Leave Details
6. Employee Tax Details
7. Generate Salary Slip
8. Employee Bank Details
Hardware Interfaces
Server Configuration:
Minimum 2GB Hard Disk
P-III processor or equivalent
Ram 512 MB
Windows with Apache preloaded.

Client Configuration:
A terminal with Internet Explorer and Printer.
Software Interfaces Operating system – WindowsXP/2000
Language -- JSP
Database – Oracle
Network -- LAN
Communications Communications interfaces can be provided through e-mail, web browser,
Interfaces network server communications protocols, electronic forms, and so on.
For this we can use communication standards such as FTP or HTTP to
provide security using encryption algorithms and synchronization
mechanisms

Functional Requirements
This section analyzes various angles of the functionality to be developed. You do not need to
use each type of analysis for the entire system. Select only those analyses that best allow you
to complete your understanding of the requirements.
Feature Analysis The Automated Payroll Processing system consists of following modules.
Admin : In this module admin is provided with many services such as
assigning roles, Add new employee, Update Salary Details, Update Loan
Details, Update Leave Details, Update Tax Details, Generate Salary Slip,
View employee account.
Employee: In this module employee is provided with the services such as
Update personal profile, Change Password, View earnings, View
Deductions, View Salary Slip.

Sequence Diagram :

For Admin:

Administrator Add new Enter employee Salary details Loan details Leave details Tax details Salary slip Bank
employee id
Verifies and adds

logout

Gives id View salary details update loan details update leave details
perform tax calculations Generate salary slip
verify employee account

Logout

For Employee:
Employee Update profile Change Earnings Deductions salary slip
password

view earnings View deductions


View salary slip

Logout

Logout

Logout

Logout

Logout

Activity Diagram :
Login

Employee
Administrator

Update
Add new profile
employee

Salary Change
details password

Loan Earnings
details

Leave Deductions
details

Tax details
View
salary slip

Enter No Update salary


employee id Salary credited details

Yes
Update Loan
details
view salary
slip

Update Leave
details

Update Tax
details

Generate
salary slip

View the
employ...

Logout

Class Diagram :
Update profile
login status='e' Employee
status='a' id
username id name
pasword password email id
qualification
key skills
Bank details address
Add new id
employee Account number update()
Administrator
id can verifies Balance amount
id
name
password salary slip change password
designation
date of joining generates salary month id
salary year password
date
updates total earnings change password()
updates total deductions
net pay
update salary view earnings
netamount()
details
id
id update loan details month
leave details Tax details
name id year
designation loan number id id
basic salary loan amount earned leaves basic salary earnings()
DA repaid amount privileged leaves tax percentage
HRA balance amount unpaid leaves tax amount
PF EMI total leave days
balance duration leave allowance taxdeduction() view
calculate() leave deductions deductions
id
Deduction() month
year

deductions()

System Feature ID: System Feature Name:

SRS_APP_ADM_01 Admin Services

Description: Admin module generates the salary slip from the leave
details, loan details, tax details he filled for an employee and
also on the data given by the employee. The feature stores the
data in a database and retrieve using employee ID. Updates
employee’s information whenever necessary.
Activity Diagrams, List the graphical models used to analyze the features and to
Sequence Diagrams, Class better understand what needs to happen in the system. This
Diagrams:
can help identify issues such as omissions in the
requirements. Remember that this is an analysis activity and
not yet a design activity. Proceed only to a level of detail that
allows you to understand the problem domain.
The diagrams are defined as delineated in the Unified
Modeling Language (UML):
• Activity diagrams that show the user-system
interactions: Use this type of diagram to better
understand the flow of the work, and, in particular,
the branching.
• Sequence diagrams that show object interactions:
Use this type of diagram to identify the key concepts
of the domain, i.e., the objects that will implement the
behavior.
• Class diagrams that summarize the classes of objects
that appear in the sequence diagram: Use this type of
diagram as a complement to the previous diagram.
Operations: 1. Add new employee
2. Update Salary details
3. Update Loan details
4. Update Leave details
5. Update Tax details
6. Generate Salary Slip
7. Verify Employee’s Account

System Feature ID: System Feature Name:

SRS_APP_EMP_01 Employee Services

Description: This module enable to maintain information so that burden


on the admin will be reduced. Here employee is provided to
update his personal profile, View his earnings, View
deductions, View profile, View salary slip
Activity Diagrams, List the graphical models used to analyze the features and to
Sequence Diagrams, Class better understand what needs to happen in the system. This
Diagrams:
can help identify issues such as omissions in the
requirements. Remember that this is an analysis activity and
not yet a design activity. Proceed only to a level of detail that
allows you to understand the problem domain.
The diagrams are defined as delineated in the Unified
Modeling Language (UML):
• Activity diagrams that show the user-system
interactions: Use this type of diagram to better
understand the flow of the work, and, in particular,
the branching.
• Sequence diagrams that show object interactions:
Use this type of diagram to identify the key concepts
of the domain, i.e., the objects that will implement the
behavior.
• Class diagrams that summarize the classes of objects
that appear in the sequence diagram: Use this type of
diagram as a complement to the previous diagram.

Operations: 1. Update Profile


2. Change password
3. View earnings
4. view deductions
5. view salary slip

Object Analysis 1. Admin


2. Employee
S. No. Class Name Responsibility Persistent (Y / N)
S1 Admin The admin must assign id’s to Permanent
all employees and assign a role Database
to them

S. No. Class Name Responsibility Persistent (Y / N)


S2 Employee Employee updates his profile Permanent
and checks his salary slip. Database

State Analysis Each user will be provided with a login name and password. When a
valid user enters the system, a list of services will be displayed as hyper
links. User can select any option and perform desired operations like
Update profile, Change password, Update salary, Update Leave, Update
Loan, Generate Salary Slip etc. Data updation service will be provided to
only designated user. User can select logout option and exit from the
system.

State Diagram:
For admin:

Login Role Administrator

Add new
employee

Update salary
details

Update Loan
details

Update Leave
details

Update Tax
details

Generate
salary slip

Verify bank
details

Logout

For Employee:
Login Role

Earnings Employee Deductions

Update
profile

view salary
slip

Logout

Nonfunctional Requirements
Performance System can withstand even though many number of users requested
Requirements the desired service. As we are keeping office level server of the
automated payroll system. And access is given to the only registered
users of office who requires the services of viewing, Updating etc. It
can withstand the load
Safety & Reliability By incorporating a robust and proven SQL into the system, reliable
Requirements performance and integrity of data is ensured. There must be a power
backup for server system.

Security Sensitive data is protected from unwanted access by users appropriate


Requirements technology and implementing strict user- access criteria.

Software Quality Menu-driven programs with user friendly interface with simply hyper
Attributes links. It is very easy to use. Backup mechanisms are considered for
maintainability of software as well as database. As it is object oriented
reusability exists. As project is based on MVC architecture, testability
exists.
LBRCE - JKC

Automated Payroll Processing


Release No.1

Detailed Design
Version No.1.0

ND System Solutions

_________________________________________________________________
Automated Payroll Processing
Release No.1

Detailed Design
Version No.1.0

Prepared By: Inspected/Reviewed By: Approved By:

NAME : Nalini.Y,
Naresh.Ch,
Nishitha.A,
Priyanka.G,
Poornima lavanya.M.

TITLE : Automated Payroll Processing

SIGNATURE :

DATE : 06-03-07

VERSION HISTORY

Version Date Changed Changes Made:


No. By:
1.0 06-03-07
Automated Payroll Processing

Detailed Design

Table of Contents

OVERVIEW........................................................................................................................................................................6
CUSTOMER:..........................................................................................................................................................................6
PURPOSE:.............................................................................................................................................................................6
SCOPE:................................................................................................................................................................................6
REFERENCES:.......................................................................................................................................................................6
GENERAL REQUIREMENTS ........................................................................................................................................7
SYSTEM IN CONTEXT:............................................................................................................................................................7
USER CHARACTERISTICS: ......................................................................................................................................................7
CONSTRAINTS:......................................................................................................................................................................7
SYSTEM-WIDE REQUIREMENTS (RECEIVED):............................................................................................................................7
SYSTEM-WIDE REQUIREMENTS (DERIVED):............................................................................................................................7
DETAILED REQUIREMENTS........................................................................................................................................8
FUNCTIONAL REQUIREMENTS..................................................................................................................................................8
Use-Case Overview ....................................................................................................................................................8
Use-Cases Specifications...........................................................................................................................................10
TECHNICAL REQUIREMENTS..................................................................................................................................................15
Operational Environment:.........................................................................................................................................15
Development Environment:.......................................................................................................................................15
...........................................................................................................................................................................................18
OVERVIEW......................................................................................................................................................................20
PROBLEM FRAME................................................................................................................................................................20
REFERENCES.......................................................................................................................................................................20
INTERFACE REQUIREMENTS ..................................................................................................................................20
USER INTERFACES...............................................................................................................................................................20
HARDWARE INTERFACES.......................................................................................................................................................20
SOFTWARE INTERFACES........................................................................................................................................................20
COMMUNICATIONS INTERFACES..............................................................................................................................................20
FUNCTIONAL REQUIREMENTS................................................................................................................................20
FEATURE ANALYSIS.............................................................................................................................................................21
OBJECT ANALYSIS...............................................................................................................................................................25
STATE ANALYSIS.................................................................................................................................................................26
NONFUNCTIONAL REQUIREMENTS.......................................................................................................................28
PERFORMANCE REQUIREMENTS..............................................................................................................................................29
SAFETY & RELIABILITY REQUIREMENTS ................................................................................................................................29
SECURITY REQUIREMENTS ...................................................................................................................................................29
SOFTWARE QUALITY ATTRIBUTES..........................................................................................................................................29
INTRODUCTION ...........................................................................................................................................................34
SCOPE:..............................................................................................................................................................................34
REFERENCES:.....................................................................................................................................................................34
GENERAL CONSIDERATIONS....................................................................................................................................34
DECISIONS:........................................................................................................................................................................35
DEPENDENCIES:..................................................................................................................................................................35
CONVENTIONS:...................................................................................................................................................................35
DETAILED DESIGN........................................................................................................................................................35
INTRODUCTION............................................................................................................................................................43
THE “AUTOMATED PAYROLL PROCESSING” HELPS ADMINISTRATOR HONOR THEIR PROFESSIONAL COMMITMENTS BY
FOLLOWING A TAILORED VERSION OF THE ORGANIZATION’S STANDARD PROCESS. ...........................................................................43
CONTEXT DIAGRAM............................................................................................................................................................43
REFERENCES.......................................................................................................................................................................43
SYSTEM DESCRIPTION...............................................................................................................................................43
SCOPE...............................................................................................................................................................................43
SUCCESS CRITERIA..............................................................................................................................................................44
CONSTRAINTS................................................................................................................................................................44
TECHNICAL CONSTRAINTS....................................................................................................................................................44
ARCHITECTURAL REQUIREMENTS.......................................................................................................................44
SYSTEM ARCHITECTURE...........................................................................................................................................45
LOGICAL VIEW...................................................................................................................................................................45
USE-CASE SUMMARY..........................................................................................................................................................46
ARCHITECTURAL ANALYSIS
............................................................................................................................................................................................47
AS MVC ARCHITECTURE IS USED FOR THE SYSTEM IT IS EASY TO MAINTAIN QUALITY AND BUSINESS REQUIREMENTS OF THE USER.....47
UTILITY TREE....................................................................................................................................................................47
Issue/Decision ........................................................................................................................................................47
...........................................................................................................................................................................................51
OVERVIEW......................................................................................................................................................................53
SCOPE:..............................................................................................................................................................................53
REFERENCES:.....................................................................................................................................................................53
DOMAIN DEFINITIONS:...............................................................................................................................................54
TABLE DEFINITIONS: .................................................................................................................................................54
ADMIN.............................................................................................................................................................................54
EMPLOYEE.........................................................................................................................................................................54
DESIGNATION ....................................................................................................................................................................55
LEAVE ..............................................................................................................................................................................55
LOAN ...............................................................................................................................................................................56
BANK................................................................................................................................................................................56
SAL SLIP............................................................................................................................................................................57
PURPOSE .........................................................................................................................................................................62
SOFTWARE LIFECYCLE..............................................................................................................................................62
SCHEDULE AND RESPONSIBILITIES .....................................................................................................................63
INTRODUCTION:...........................................................................................................................................................69
...........................................................................................................................................................................................70
SCOPE...............................................................................................................................................................................70
REFERENCES.......................................................................................................................................................................70
TESTING OBJECTIVE:.................................................................................................................................................70

Introduction
Scope: The Scope of this document is to maintain list of employee ids and
related information.

References: • LBRCE –JKC. User Requirements Document v.1.0.1


• LBRCE – JKC High-Level Design v.1.0.1
• LBRCE – JKC Software Requirments Specifications v.1.0.1

General Considerations
Decisions: • MVC is used in this project. It mainly deals with 3 interfaces,
namely model, view, Controller.
• Model :-
A model represents an application data and contains the
logic for accessing and manipulating the data. Any data i.e. part of
the persistent state of the application should reside in the model
objects. A model groups related data and operations for providing a
specific service; In these group of operations wrap and abstract the
functionality of the business process being modeled.
A model’s interface exposes methods for accessing and
updating the state of the model and for executing the complex
processes encapsulated inside the model. Model services are accessed
by the controller for either querying or effectively change in the
model state.
• View :-
The View is responsible for sending the state of the
model. The presentation semantics are encapsulated with in the view,
therefore model data can be adopted for several different kinds of
clients. The view modifies itself when the change in the model is
communicated to the view. A view forwards user input to the
controller.
• Controller :-
The Controller is responsible for intercepting and
translating user input in to sections to be performed by the model.
The controller is responsible for selecting the next view based on user
input and the outcome of model operations.
Dependencies: The Automated Payroll system details the module uses PHP parser.
Conventions: • Structures appear in the class diagrams.
• Sequence Of calls that appear at the beginning of many sequence
diagrams are fully represented only once.
• Database operations common to all sequence diagrams are fully
represented only once.

Detailed Design

Class Design:
The Purpose of Class Design is to depict the
classes with in a model. In an object oriented application, Classes have attributes, operations and
relationships.
The attributes are stored the data about an object and the operations are giving the
responsibilities for an object.
In this Document the Classes are Administrator and Employee. The following relation
is existed in between the two classes.

Update profile
login status='e' Employee
status='a' id
username id name
pasword password email id
qualification
key skills
Bank details address
Add new id
employee Account number update()
Administrator
id can verifies Balance amount
id
name
password salary slip change password
designation
date of joining generates salary month id
salary year password
date
updates total earnings change password()
updates total deductions
net pay
update salary view earnings
netamount()
details
id
id update loan details month
leave details Tax details
name id year
designation loan number id id
basic salary loan amount earned leaves basic salary earnings()
DA repaid amount privileged leaves tax percentage
HRA balance amount unpaid leaves tax amount
PF EMI total leave days
balance duration leave allowance taxdeduction() view
calculate() leave deductions deductions
id
Deduction() month
year

deductions()
USECASE DESIGN

Use case diagrams depict:

• Use cases: A use case describes a sequence of actions that provide something of
measurable value to an actor and is drawn as a horizontal ellipse.
• Actors: An actor is a person, organization, or external system that plays a role in one or
more interactions with your system. Actors are drawn as stick figures.
• Associations: Associations between actors and use cases are indicated in use case
diagrams by solid lines. An association exists whenever an actor is involved with an
interaction described by a use case. Associations are modeled as lines connecting use cases
and actors to one another, with an optional arrowhead on one end of the line. The arrowhead
is often used to indicating the direction of the initial invocation of the relationship or to
indicate the primary actor within the use case. The arrowheads are typically confused with
data flow and as a result I avoid their use
Login

Add New Employee

View Salary details

Administrator

View Loan details


Employee

View Leave details

View Income Tax rules

Credit Employee Account

Generate Salary Slip

Update Profile

View Deductions

View Earnings

Log Out
LBRCE - JKC

AUTOMATED PAYROLL PROCESSING

Release No. 1.0

High Level Design Document


Version No. 1.0

Institute For Electronic Governance


_________________________________________________________________
AUTOMATED PAYROLL PROCESSING
Release No.1.0

High Level Design Document


Version No1.0.

Prepared By: Inspected By: Approved By:

NAME: Nalini.Y,
Naresh.Ch,
Nishitha.A,
Priyanka.G,
Poornima lavanya.M.

TITLE: Automated Payroll Processing

SIGNATURE:

DATE: 23-02-2007

VERSION HISTORY

Version Date Changed Changes Made:


No. By:
1 23-02-2007
REPOSITORY SEARCH ENGINE FOR ALUMNI OF COLLEGE

High Level Design Document

Table of Contents

OVERVIEW....................................................................................................................................................................6
CUSTOMER:......................................................................................................................................................................6
PURPOSE:.........................................................................................................................................................................6
SCOPE:............................................................................................................................................................................6
REFERENCES:....................................................................................................................................................................6
GENERAL REQUIREMENTS ....................................................................................................................................7
SYSTEM IN CONTEXT:........................................................................................................................................................7
USER CHARACTERISTICS: ..................................................................................................................................................7
CONSTRAINTS:..................................................................................................................................................................7
SYSTEM-WIDE REQUIREMENTS (RECEIVED):.........................................................................................................................7
SYSTEM-WIDE REQUIREMENTS (DERIVED):........................................................................................................................7
DETAILED REQUIREMENTS....................................................................................................................................8
FUNCTIONAL REQUIREMENTS..............................................................................................................................................8
Use-Case Overview .................................................................................................................................................8
Use-Cases Specifications.......................................................................................................................................10
TECHNICAL REQUIREMENTS..............................................................................................................................................15
Operational Environment:.....................................................................................................................................15
Development Environment:....................................................................................................................................15
........................................................................................................................................................................................18
OVERVIEW..................................................................................................................................................................20
PROBLEM FRAME............................................................................................................................................................20
REFERENCES...................................................................................................................................................................20
INTERFACE REQUIREMENTS ..............................................................................................................................20
USER INTERFACES...........................................................................................................................................................20
HARDWARE INTERFACES...................................................................................................................................................20
SOFTWARE INTERFACES....................................................................................................................................................20
COMMUNICATIONS INTERFACES..........................................................................................................................................20
FUNCTIONAL REQUIREMENTS............................................................................................................................20
FEATURE ANALYSIS.........................................................................................................................................................21
OBJECT ANALYSIS...........................................................................................................................................................25
STATE ANALYSIS.............................................................................................................................................................26
NONFUNCTIONAL REQUIREMENTS...................................................................................................................28
PERFORMANCE REQUIREMENTS..........................................................................................................................................29
SAFETY & RELIABILITY REQUIREMENTS ............................................................................................................................29
SECURITY REQUIREMENTS ...............................................................................................................................................29
SOFTWARE QUALITY ATTRIBUTES......................................................................................................................................29
INTRODUCTION ........................................................................................................................................................34
SCOPE:..........................................................................................................................................................................34
REFERENCES:..................................................................................................................................................................34
GENERAL CONSIDERATIONS................................................................................................................................34
DECISIONS:....................................................................................................................................................................35
DEPENDENCIES:..............................................................................................................................................................35
CONVENTIONS:...............................................................................................................................................................35
DETAILED DESIGN....................................................................................................................................................35
INTRODUCTION.........................................................................................................................................................43
THE “AUTOMATED PAYROLL PROCESSING” HELPS ADMINISTRATOR HONOR THEIR PROFESSIONAL COMMITMENTS BY
FOLLOWING A TAILORED VERSION OF THE ORGANIZATION’S STANDARD PROCESS. .......................................................................43
CONTEXT DIAGRAM........................................................................................................................................................43
REFERENCES...................................................................................................................................................................43
SYSTEM DESCRIPTION...........................................................................................................................................43
SCOPE...........................................................................................................................................................................43
SUCCESS CRITERIA..........................................................................................................................................................44
CONSTRAINTS............................................................................................................................................................44
TECHNICAL CONSTRAINTS................................................................................................................................................44
ARCHITECTURAL REQUIREMENTS...................................................................................................................44
SYSTEM ARCHITECTURE.......................................................................................................................................45
LOGICAL VIEW...............................................................................................................................................................45
USE-CASE SUMMARY......................................................................................................................................................46
ARCHITECTURAL ANALYSIS
.........................................................................................................................................................................................47
AS MVC ARCHITECTURE IS USED FOR THE SYSTEM IT IS EASY TO MAINTAIN QUALITY AND BUSINESS REQUIREMENTS OF THE USER. 47
UTILITY TREE................................................................................................................................................................47
Issue/Decision ....................................................................................................................................................47
........................................................................................................................................................................................51
OVERVIEW..................................................................................................................................................................53
SCOPE:..........................................................................................................................................................................53
REFERENCES:..................................................................................................................................................................53
DOMAIN DEFINITIONS:...........................................................................................................................................54
TABLE DEFINITIONS: ..............................................................................................................................................54
ADMIN..........................................................................................................................................................................54
EMPLOYEE.....................................................................................................................................................................54
DESIGNATION .................................................................................................................................................................55
LEAVE ..........................................................................................................................................................................55
LOAN ...........................................................................................................................................................................56
BANK............................................................................................................................................................................56
SAL SLIP........................................................................................................................................................................57
PURPOSE .....................................................................................................................................................................62
SOFTWARE LIFECYCLE..........................................................................................................................................62
SCHEDULE AND RESPONSIBILITIES ..................................................................................................................63
INTRODUCTION:.......................................................................................................................................................69
........................................................................................................................................................................................70
SCOPE...........................................................................................................................................................................70
REFERENCES...................................................................................................................................................................70
TESTING OBJECTIVE:.............................................................................................................................................70
Introduction
The “Automated Payroll Processing” helps administrator honor their professional
commitments by following a tailored version of the organization’s standard process.
This application is supported by a database consisting of employee’s salary details
and their leave allowances. Based on these details at the end of every month the application
automatically credits the employee’s bank account with their salary. The amount of salary credited
into employees account is a variant of their leave allowances.
This Payroll Processing application also considers employee’s income tax
regulations and loan payment details. Based on these considerations the salary of each employee
is deducted at the source. Taking into account all these aspects the appropriate accounts of each
employee are credited. This application also includes generation of salary slips to every employee.

Context Diagram

Event Driven
Web based
System

PPS System
Business Logic
Storage
Subsystem

Data Access Application Layer Interface

Application Layer

Personal
Persistent
Data Repository

References
• LBRCE-JKC. Business Case and Vision Document v.1.0.1
• LBRCE-JKC.Features List v.1.0.1

System Description
Scope
This project is a distributed endeavor that strives to employ languages that promote platform
independence and make it possible to support desktop and laptop systems in traditional and
wireless networking infrastructures .Efforts must be focused on business logic issues rather than
needlessly duplicating user interface software, database software, etc. Its main focus is on the
generation of reports at any time.
Success Criteria
This system automates the managerial functions of Automated payroll processing with its
various features with-in less time and effective manner. This system will be successful if it
delivers accurate documentation of existing payroll appointment types and processes , identifies
both technical and policy issues, and recommends a stream lined future process that both meets
company payroll requirements and is technically feasible. We believe that once any
organizations choose to use this system it will eventually recognize the value and necessity of
this system. Naturally, this system will be successful.

Constraints
There must be high end system to load software and to maintain database. A minimal
terminal is required with printer for reports which are to be connected in the network.

Technical Constraints

Windows system with Apache server configured for execution of JSP coding, SQL database is
required

Architectural Requirements
1. Portability— The system must be easily portable to a wide variety of platforms using various
operating systems. Porting the software from one operating system to another should not
require more than 5% of the code to be changed .Similarly changing the backend database
should not require more than 5% of the code to change.
2. Extensibilty/Reuse— The software should be extensible in order to add new features without
affecting base modules. The new releases of the system should maximize the reuse of
solutions developed in earlier releases.
3. Ease of use— The system must be easy to use without requiring users to memorize
commands, special terms, or notations. A new user should not require more than one hour of
training to get comfortable using the system.
System Architecture
We have elected to represent the architecture of this system with a use case view,
logical view, package view and architectural patterns.

Logical View

User Interface
Legend

Application Layer
Business Logic

Dependency

Data Access
Use-Case Summary

Login

Add New Employee

View Salary details

Administrator

View Loan details


Employee

View Leave details

View Income Tax rules

Credit Employee Account

Generate Salary Slip

Update Profile

View Deductions

View Earnings

Log Out
Architectural Analysis
As MVC architecture is used for the system it is easy to maintain quality and business
requirements of the user.
Utility Tree
Speed : As it is automated system for APP, it is definitely faster than the manual system.
Accuracy : As calculations are done by the system itself, high level of accuracy can be
maintained up to the desired decimal point.
Maintainability: System is looking into frequent backup and recovery mechanisms,
maintainability is high.
Compatibility : As it is client/server System, an ordinary browser can be used at client side
with the minimum requirement specified in SRS.
Optimization of Resources: As it is automated system and web based application so many hard
copies need not be maintained so that man power can be reduced.
Architectural Decisions:
-
User Interface Business Logic Interactions
Issue/Decision
1. Employee the MVC architecture.
Rationale
• MVC’s inherent separation of concern encourages many-to-many relationships among the
components, which supports reuse.
• MVC can be used with PHP.
• Different view components of MVC can be substituted for one another.MVC thus defines
an ideal set of boundaries for the switch between the differing user interface libraries of
PHP, or the different user interface libraries of the PC.
-
Business Logic Database Interface
Issue/Decision
The database access is organized as follows.

• Model classes that exist as data in the database manage their own creation, modification,
deletion and viewing.
• Model classes are responsible for enforcing constraints about the content of the database.
The database constraint-checking mechanisms are not used; However, Model classes can
rely on the database executing “cascading deletes” on all parent-child table relationships.
• Model classes are responsible for starting and ending database transactions.
• Model classes are rely on two transaction layers:
1. Broker which creates SQL statements for them and manages the connection with
the database system (open, close).
2. Platform-specific data services API.

Rationale
• Isolate SQL knowledge in one place.
• Allow replacement of the storage mechanism without affecting UI, control, or Business
classes.
• Minimize portability issues from PHP.
User Interface rules
Issue/Decision
The user interface will employ the same features across all platforms and
programming languages. Since the application is operated in web-based environment…
Rationale

• Portability and extensibility with reuse both argue in favor of minimizing differences,
even at the expense of not using “nice-to-have”, but non-standard features.
• Usability is enhanced for the users who may employ the product on different platforms at
the same time, or by switching from one to another.
LBRCE-JKC

Automated Payroll Processing

Release No.1

Logical Database Design


Version No.1.0

ND System Solutions
_________________________________________________________________
Automated Payroll Processing

Release No.1

Logical Database Design

Version No.1.0

Prepared By: Inspected/Reviewed By: Approved By:

NAME: Nalini.Y,
Naresh.Ch,
Nishitha.A,
Priyanka.G,
Poornima lavanya.M.

TITLE: Automated Payroll Processing

SIGNATURE:

DATE: 06-03-07

VERSION HISTORY

Version Date Changed Changes Made:


No. By:
1.0 06-03-07
Automated Payroll Processing
Logical Database Design

Table of Contents

OVERVIEW....................................................................................................................................................................6
CUSTOMER:......................................................................................................................................................................6
PURPOSE:.........................................................................................................................................................................6
SCOPE:............................................................................................................................................................................6
REFERENCES:....................................................................................................................................................................6
GENERAL REQUIREMENTS ....................................................................................................................................7
SYSTEM IN CONTEXT:........................................................................................................................................................7
USER CHARACTERISTICS: ..................................................................................................................................................7
CONSTRAINTS:..................................................................................................................................................................7
SYSTEM-WIDE REQUIREMENTS (RECEIVED):.........................................................................................................................7
SYSTEM-WIDE REQUIREMENTS (DERIVED):........................................................................................................................7
DETAILED REQUIREMENTS....................................................................................................................................8
FUNCTIONAL REQUIREMENTS..............................................................................................................................................8
Use-Case Overview .................................................................................................................................................8
Use-Cases Specifications.......................................................................................................................................10
TECHNICAL REQUIREMENTS..............................................................................................................................................15
Operational Environment:.....................................................................................................................................15
Development Environment:....................................................................................................................................15
........................................................................................................................................................................................18
OVERVIEW..................................................................................................................................................................20
PROBLEM FRAME............................................................................................................................................................20
REFERENCES...................................................................................................................................................................20
INTERFACE REQUIREMENTS ..............................................................................................................................20
USER INTERFACES...........................................................................................................................................................20
HARDWARE INTERFACES...................................................................................................................................................20
SOFTWARE INTERFACES....................................................................................................................................................20
COMMUNICATIONS INTERFACES..........................................................................................................................................20
FUNCTIONAL REQUIREMENTS............................................................................................................................20
FEATURE ANALYSIS.........................................................................................................................................................21
OBJECT ANALYSIS...........................................................................................................................................................25
STATE ANALYSIS.............................................................................................................................................................26
NONFUNCTIONAL REQUIREMENTS...................................................................................................................28
PERFORMANCE REQUIREMENTS..........................................................................................................................................29
SAFETY & RELIABILITY REQUIREMENTS ............................................................................................................................29
SECURITY REQUIREMENTS ...............................................................................................................................................29
SOFTWARE QUALITY ATTRIBUTES......................................................................................................................................29
INTRODUCTION ........................................................................................................................................................34
SCOPE:..........................................................................................................................................................................34
REFERENCES:..................................................................................................................................................................34
GENERAL CONSIDERATIONS................................................................................................................................34
DECISIONS:....................................................................................................................................................................35
DEPENDENCIES:..............................................................................................................................................................35
CONVENTIONS:...............................................................................................................................................................35
DETAILED DESIGN....................................................................................................................................................35
INTRODUCTION.........................................................................................................................................................43
THE “AUTOMATED PAYROLL PROCESSING” HELPS ADMINISTRATOR HONOR THEIR PROFESSIONAL COMMITMENTS BY
FOLLOWING A TAILORED VERSION OF THE ORGANIZATION’S STANDARD PROCESS. .......................................................................43
CONTEXT DIAGRAM........................................................................................................................................................43
REFERENCES...................................................................................................................................................................43
SYSTEM DESCRIPTION...........................................................................................................................................43
SCOPE...........................................................................................................................................................................43
SUCCESS CRITERIA..........................................................................................................................................................44
CONSTRAINTS............................................................................................................................................................44
TECHNICAL CONSTRAINTS................................................................................................................................................44
ARCHITECTURAL REQUIREMENTS...................................................................................................................44
SYSTEM ARCHITECTURE.......................................................................................................................................45
LOGICAL VIEW...............................................................................................................................................................45
USE-CASE SUMMARY......................................................................................................................................................46
ARCHITECTURAL ANALYSIS
.........................................................................................................................................................................................47
AS MVC ARCHITECTURE IS USED FOR THE SYSTEM IT IS EASY TO MAINTAIN QUALITY AND BUSINESS REQUIREMENTS OF THE USER. 47
UTILITY TREE................................................................................................................................................................47
Issue/Decision ....................................................................................................................................................47
........................................................................................................................................................................................51
OVERVIEW..................................................................................................................................................................53
SCOPE:..........................................................................................................................................................................53
REFERENCES:..................................................................................................................................................................53
DOMAIN DEFINITIONS:...........................................................................................................................................54
TABLE DEFINITIONS: ..............................................................................................................................................54
ADMIN..........................................................................................................................................................................54
EMPLOYEE.....................................................................................................................................................................54
DESIGNATION .................................................................................................................................................................55
LEAVE ..........................................................................................................................................................................55
LOAN ...........................................................................................................................................................................56
BANK............................................................................................................................................................................56
SAL SLIP........................................................................................................................................................................57
PURPOSE .....................................................................................................................................................................62
SOFTWARE LIFECYCLE..........................................................................................................................................62
SCHEDULE AND RESPONSIBILITIES ..................................................................................................................63
INTRODUCTION:.......................................................................................................................................................69
........................................................................................................................................................................................70
SCOPE...........................................................................................................................................................................70
REFERENCES...................................................................................................................................................................70
TESTING OBJECTIVE:.............................................................................................................................................70
Overview
This document defines what data are stored and how they are organized.This
purpose is to clarify what all developers involved in database access can expect from the database
The logical database design evolves from the conceptual database design
represented by the class diagrams in the soft ware requirement specifications.It, in turn, is the
basis for the physical database design which takes into account the practical constraints that the
Logical Database Design does not (i.e., the limitations of the platform or technology chosen for
the software development and deployment).
The Logical Database Design presents the data in normalized form. Any de-
normalization occurs as part of the Physical Database Design.

Scope:
The database supports management of employee details, Loan details, Leave
details, Tax details, Bank details, Salary slip details.

References:

• LBRCE-JKC.Business Case and Vision Document v.1.0.1


• LBRCE-JKC.Features List v.1.0.1.
Domain Definitions:
Seq. Name Format When Used
#
1 ID Type Varchar2(10) For Columns representing the database
generated Unique id.

Table Definitions:
Table No.: 1
Table Name: Admin
Table Description:
Seq. Column Column Column Type PK/FK? Null/ Remarks
# Name Description Not Null
1 ID Unique Varchar2(10) Not Null
identifier
2 password password Varchar2(10) Not Null

Relationships: Admin
Constraints: No

Table No.: 2
Table Name: Employee
Table Description: Contains information of the Employees.
Seq. Column Column Column Type PK/FK? Null/ Remarks
# Name Description Not Null
1 Eno Unique Number(10) PK Not Null
Identifier
2 Ename Gives name Varchar2(10)
of an Not Null
employee
3 Email-ID ID of an Varchar2(30) Not Null
employee
4 Designation Category of Varchar2(15) Not Null
an
Employee
5 Basic Salary Total Salary Number(10) Not Null
of an
employee
6 Taeleaves Total earned Number(10) Not Null
leaves of an
employee
7 Beleaves Balance Number(10) Not Null
earned
leaves of an
employee
8 Tpleaves Total Number(10) Not Null
privileged
leaves of an
employee
9 Bpleaves Balance Number(10) Not Null
privileged
leaves of an
employee

Relationships: Employee
Constraints: Eno Primary Key.

Table No.: 3
Table Name: Designation
Table Description: Gives category of an employee
Seq. Column Column Column Type PK/FK? Null/ Remarks
# Name Description Not Null
1 Dname Name of Varchar2(15) Not Null
designation
of an
employee
2 BasicSalary Total salary Number(10)
of an Not Null
employee
3 Earnedleaves Number(10) Not Null
4 Privillaged Number(10) Not Null
leaves

Relationships: Designation
Constraints: No

Table No.: 4
Table Name: Leave
Table Description: Gives Leave details of an employee
Seq. Column Column Column Type PK/FK? Null/ Remarks
# Name Description Not Null
1 Eno Unique Number(20) PK
identifier
2 Type of leave Leave type Varchar2(20)
Not Null

3 Total days of Number of Number(20)


leave leaves of an
employee
4 Leave balance Total days Number(20)
of leave –
leaves
availed
5 Leave availed Actual taken Number(20)
leaves

Relationships: Leave
Constraints: Eno is a primary key

Table No.: 5
Table Name: Loan
Table Description: Gives Loan details of an employee
Seq. Column Column Column Type PK/FK? Null/ Remarks
# Name Description Not Null
1 Loan number Unique Number(20) PK Not Null
identifier
2 Employee ID of an Number(20) FK
number employee Not Null

3 Total loan Actual loan Number(20) Not Null


amount for an
employee
4 Repaid Loan paid Number(20)
amount by an
employee
5 Balance total loan Number(20)
amount -repaid
6 EMI Every Number(20)
monthly
installment
7 Balance Balance Number(20)
duration amount/
EMI

Relationships: Loan, Leave, Employee.


Constraints: Loan number is a primary key
Eno is a Foreign key

Table No.: 6
Table Name: Bank
Table Description: Gives Bank details of an employee
Seq. Column Column Column Type PK/FK? Null/ Remarks
# Name Description Not Null
1 Account Unique Number(20) PK
number identifier
2 Employee ID of an Number(20) FK
number employee Not Null

3 Balance Number(20)
Relationships: Bank, loan, leave, employee
Constraints: Account number is a primary key
Eno is a foreign key.

Table No.: 7
Table Name: Sal slip
Table Description: Generate a Salary slip for an employee.
Seq. Column Column Column Type PK/FK? Null/ Remarks
# Name Description Not Null
1 Eno Unique Number(10) FK
Identifier
2 Slip number Unique Number(10) PK
Identifier Not Null

3 Salary date Date of Date Not Null


salary
4 Salary month Month of Varchar2(10) Not Null
salary
5 Salary year Year of a Number(10) Not Null
salary
6 Basic salary Actual Number(10) Not Null
salary of an
employee
7 DA 8% of Basic Number(10)
salary
8 HRA Total Number(10)
privileged
leaves of an
employee
9 PF Balance Number(10)
privileged
leaves of an
employee
10 Leave Fixed Number(10)
allowance amount
11 Income tax Amount Number(10)
deduced
from salary
12 Unpaid leave According Number(10)
deductions to unpaid
leave taken
in the month
13 EMI Every Number(10)
month
installment
14 Total earnings Earnings of Number(10)
an employee
15 Total Deductions Number(10)
deductions of an
employee
16 Net pay Final salary Number(10)
of an
employee

Relationships: Salslip, bank, loan, leave, employee.


Constraints: Slip number is a primary key
Eno Foreign Key.
Automated Payroll Processing

Release No.1

Software Project Management Plan


Version No.1.0

Institute For Electronic Governance


_______________________________________________________________
__
Automated Payroll Processing
Release No.1

Software Project Management Plan


Version No. 1.0

Prepared By Inspected/Reviewed By Approved By

NAME: Nalini.Y,
Naresh.Ch,
Nishitha.A,
Priyanka.G,
Poornima lavanya.M.

TITLE: Automated Payroll Processing

SIGNATURE:

DATE: 29-03-07

VERSION HISTORY

Version Date Changed By Changes Made


No.
1.0 29-03-
07
Table of Contents

OVERVIEW.......................................................................................................................................................................6
CUSTOMER:.........................................................................................................................................................................6
PURPOSE:............................................................................................................................................................................6
SCOPE:...............................................................................................................................................................................6
REFERENCES:.......................................................................................................................................................................6
GENERAL REQUIREMENTS .......................................................................................................................................7
SYSTEM IN CONTEXT:...........................................................................................................................................................7
USER CHARACTERISTICS: .....................................................................................................................................................7
CONSTRAINTS:.....................................................................................................................................................................7
SYSTEM-WIDE REQUIREMENTS (RECEIVED):...........................................................................................................................7
SYSTEM-WIDE REQUIREMENTS (DERIVED):...........................................................................................................................7
DETAILED REQUIREMENTS.......................................................................................................................................8
FUNCTIONAL REQUIREMENTS.................................................................................................................................................8
Use-Case Overview ...................................................................................................................................................8
Use-Cases Specifications..........................................................................................................................................10
TECHNICAL REQUIREMENTS.................................................................................................................................................15
Operational Environment:........................................................................................................................................15
Development Environment:......................................................................................................................................15
...........................................................................................................................................................................................18
OVERVIEW.....................................................................................................................................................................20
PROBLEM FRAME...............................................................................................................................................................20
REFERENCES......................................................................................................................................................................20
INTERFACE REQUIREMENTS .................................................................................................................................20
USER INTERFACES..............................................................................................................................................................20
HARDWARE INTERFACES......................................................................................................................................................20
SOFTWARE INTERFACES.......................................................................................................................................................20
COMMUNICATIONS INTERFACES.............................................................................................................................................20
FUNCTIONAL REQUIREMENTS...............................................................................................................................20
FEATURE ANALYSIS............................................................................................................................................................21
OBJECT ANALYSIS..............................................................................................................................................................25
STATE ANALYSIS................................................................................................................................................................26
NONFUNCTIONAL REQUIREMENTS......................................................................................................................28
PERFORMANCE REQUIREMENTS.............................................................................................................................................29
SAFETY & RELIABILITY REQUIREMENTS ...............................................................................................................................29
SECURITY REQUIREMENTS ..................................................................................................................................................29
SOFTWARE QUALITY ATTRIBUTES.........................................................................................................................................29
INTRODUCTION ...........................................................................................................................................................34
SCOPE:.............................................................................................................................................................................34
REFERENCES:.....................................................................................................................................................................34
GENERAL CONSIDERATIONS...................................................................................................................................34
DECISIONS:.......................................................................................................................................................................35
DEPENDENCIES:.................................................................................................................................................................35
CONVENTIONS:..................................................................................................................................................................35
DETAILED DESIGN.......................................................................................................................................................35
INTRODUCTION............................................................................................................................................................43
THE “AUTOMATED PAYROLL PROCESSING” HELPS ADMINISTRATOR HONOR THEIR PROFESSIONAL COMMITMENTS BY
FOLLOWING A TAILORED VERSION OF THE ORGANIZATION’S STANDARD PROCESS. ..........................................................................43
CONTEXT DIAGRAM...........................................................................................................................................................43
REFERENCES......................................................................................................................................................................43
SYSTEM DESCRIPTION..............................................................................................................................................43
SCOPE..............................................................................................................................................................................43
SUCCESS CRITERIA.............................................................................................................................................................44
CONSTRAINTS...............................................................................................................................................................44
TECHNICAL CONSTRAINTS...................................................................................................................................................44
ARCHITECTURAL REQUIREMENTS......................................................................................................................44
SYSTEM ARCHITECTURE..........................................................................................................................................45
LOGICAL VIEW..................................................................................................................................................................45
USE-CASE SUMMARY.........................................................................................................................................................46
ARCHITECTURAL ANALYSIS
............................................................................................................................................................................................47
AS MVC ARCHITECTURE IS USED FOR THE SYSTEM IT IS EASY TO MAINTAIN QUALITY AND BUSINESS REQUIREMENTS OF THE USER....47
UTILITY TREE...................................................................................................................................................................47
Issue/Decision .......................................................................................................................................................47
...........................................................................................................................................................................................51
OVERVIEW.....................................................................................................................................................................53
SCOPE:.............................................................................................................................................................................53
REFERENCES:.....................................................................................................................................................................53
DOMAIN DEFINITIONS:..............................................................................................................................................54
TABLE DEFINITIONS: ................................................................................................................................................54
ADMIN............................................................................................................................................................................54
EMPLOYEE........................................................................................................................................................................54
DESIGNATION ....................................................................................................................................................................55
LEAVE .............................................................................................................................................................................55
LOAN ..............................................................................................................................................................................56
BANK...............................................................................................................................................................................56
SAL SLIP...........................................................................................................................................................................57
PURPOSE ........................................................................................................................................................................62
SOFTWARE LIFECYCLE.............................................................................................................................................62
SCHEDULE AND RESPONSIBILITIES .....................................................................................................................63
INTRODUCTION:..........................................................................................................................................................69
...........................................................................................................................................................................................70
SCOPE..............................................................................................................................................................................70
REFERENCES......................................................................................................................................................................70
TESTING OBJECTIVE:................................................................................................................................................70

Purpose
The Software Project Management Plan organizes the production of the project
deliverables.

Software Lifecycle
The project follows a certain waterfall style pattern of development. It has following phases.
Stage Deliverable
Requirements Engineering Business Case and Vision
User Requirements Document
Software Requirements
Specification
High-Level Design High Level Design
Detailed Design Detailed Design
Logical Database Design
System Test Plan
Integration Test Plan
Unit Test Plan
Coding Code
Database
Unit Testing successful
Integration Testing Successfully integrated all the
units
System Testing Successfully generated pay slip

Schedule and Responsibilities


The project has been scheduled for three months. First the analysis phase
was started on 20-1-07 and was completed by 25th and all the team members were involved in this
phase. The output of this phase is database design. In the database design tables were designed in
such a way that it eliminates all the anomalies and it was also designed in such a way that it takes
less storage space and also reduces the burden on the server. The database design was done with in
two days and the responsibilities of the database designer is to resolve all the anomalies and ensure
that the database is stable and free from deadlocks and takes less storage space. It has to provide
certain features like concurrency control, highly extensible, reliable, flexible, API, etc.

After the database design has been completed the coding phase was started.
This project was implemented using JSP and java scripts was used to do the validations. The
coding was done for about One month. Many functions are used in the code so as to make it
efficient. The advantage of JSP is that it has many built in functions so the coder need not write
many lines of code for a task he can just use the functions. The front end design was started
simultaneously with the coding and this project uses HTML as the front end. The responsibility of
the front end designer to present the project in such a way that the client will get a good impression
as soon as he sees the project presentation. After the front end designing and coding has been
completed these two were integrated to run the project.

The system was tested using unit testing, integration testing which were
mentioned in the test plan document. Testing took about 10 days. Each unit has been tested by
using test cases.
LBRCE - JKC

Automated Payroll Processing


Release No. 1

Test Plan
Version No. 1.0

ND System Solutions
_________________________________________________________________
Automated Payroll Processing
Release No. 1

Test Plan
Version No. 1.0

Prepared By Inspected/Reviewed By Approved By

NAME: Nalini.Y,
Naresh.Ch,
Nishitha.A,
Priyanka.G,
Poornima lavanya.M.

TITLE : Automated Payroll Processing

SIGNATURE:

DATE: 29-03-07

VERSION HISTORY

Version Date Changed By Changes Made


No.
1.0 29-03-07

PET-TP Template v.1.0 Page 66 of 74


Automated Payroll processing

Test Plan

Table of Contents

OVERVIEW....................................................................................................................................................6
CUSTOMER:......................................................................................................................................................6
PURPOSE:........................................................................................................................................................6
SCOPE:............................................................................................................................................................6
REFERENCES:...................................................................................................................................................6
GENERAL REQUIREMENTS ....................................................................................................................7
SYSTEM IN CONTEXT:........................................................................................................................................7
USER CHARACTERISTICS: ..................................................................................................................................7
CONSTRAINTS:..................................................................................................................................................7
SYSTEM-WIDE REQUIREMENTS (RECEIVED):........................................................................................................7
SYSTEM-WIDE REQUIREMENTS (DERIVED):........................................................................................................7
DETAILED REQUIREMENTS....................................................................................................................8
FUNCTIONAL REQUIREMENTS..............................................................................................................................8
Use-Case Overview ................................................................................................................................8
Use-Cases Specifications.......................................................................................................................10
TECHNICAL REQUIREMENTS..............................................................................................................................15
Operational Environment:.....................................................................................................................15
Development Environment:...................................................................................................................15
.......................................................................................................................................................................18
OVERVIEW..................................................................................................................................................20
PROBLEM FRAME............................................................................................................................................20
REFERENCES..................................................................................................................................................20
INTERFACE REQUIREMENTS ..............................................................................................................20
USER INTERFACES...........................................................................................................................................20
HARDWARE INTERFACES...................................................................................................................................20
SOFTWARE INTERFACES....................................................................................................................................20
COMMUNICATIONS INTERFACES..........................................................................................................................20
FUNCTIONAL REQUIREMENTS............................................................................................................20
FEATURE ANALYSIS.........................................................................................................................................21
OBJECT ANALYSIS...........................................................................................................................................25
STATE ANALYSIS.............................................................................................................................................26
NONFUNCTIONAL REQUIREMENTS...................................................................................................28
PERFORMANCE REQUIREMENTS.........................................................................................................................29
SAFETY & RELIABILITY REQUIREMENTS ...........................................................................................................29
SECURITY REQUIREMENTS ...............................................................................................................................29

PET-TP Template v.1.0 Page 67 of 74


SOFTWARE QUALITY ATTRIBUTES......................................................................................................................29
INTRODUCTION .......................................................................................................................................34
SCOPE:..........................................................................................................................................................34
REFERENCES:.................................................................................................................................................34
GENERAL CONSIDERATIONS................................................................................................................34
DECISIONS:....................................................................................................................................................35
DEPENDENCIES:..............................................................................................................................................35
CONVENTIONS:...............................................................................................................................................35
DETAILED DESIGN...................................................................................................................................35
INTRODUCTION........................................................................................................................................43
THE “AUTOMATED PAYROLL PROCESSING” HELPS ADMINISTRATOR HONOR THEIR PROFESSIONAL
COMMITMENTS BY FOLLOWING A TAILORED VERSION OF THE ORGANIZATION’S STANDARD PROCESS. ..............................43
CONTEXT DIAGRAM........................................................................................................................................43
REFERENCES..................................................................................................................................................43
SYSTEM DESCRIPTION...........................................................................................................................43
SCOPE...........................................................................................................................................................43
SUCCESS CRITERIA..........................................................................................................................................44
CONSTRAINTS...........................................................................................................................................44
TECHNICAL CONSTRAINTS................................................................................................................................44
ARCHITECTURAL REQUIREMENTS...................................................................................................44
SYSTEM ARCHITECTURE......................................................................................................................45
LOGICAL VIEW...............................................................................................................................................45
USE-CASE SUMMARY......................................................................................................................................46
ARCHITECTURAL ANALYSIS
........................................................................................................................................................................47
AS MVC ARCHITECTURE IS USED FOR THE SYSTEM IT IS EASY TO MAINTAIN QUALITY AND BUSINESS REQUIREMENTS OF
THE USER.......................................................................................................................................................47
UTILITY TREE................................................................................................................................................47
Issue/Decision ....................................................................................................................................47
.......................................................................................................................................................................51
OVERVIEW..................................................................................................................................................53
SCOPE:..........................................................................................................................................................53
REFERENCES:.................................................................................................................................................53
DOMAIN DEFINITIONS:..........................................................................................................................54
TABLE DEFINITIONS: .............................................................................................................................54
ADMIN.........................................................................................................................................................54
EMPLOYEE.....................................................................................................................................................54
DESIGNATION ................................................................................................................................................55
LEAVE ..........................................................................................................................................................55
LOAN ...........................................................................................................................................................56
BANK............................................................................................................................................................56
SAL SLIP........................................................................................................................................................57
PURPOSE .....................................................................................................................................................62

PET-TP Template v.1.0 Page 68 of 74


SOFTWARE LIFECYCLE..........................................................................................................................62
SCHEDULE AND RESPONSIBILITIES .................................................................................................63
INTRODUCTION:.......................................................................................................................................69
.......................................................................................................................................................................70
SCOPE...........................................................................................................................................................70
REFERENCES..................................................................................................................................................70
TESTING OBJECTIVE:.............................................................................................................................70

INTRODUCTION:

In a software development project, errors can be injected at any stage during


development. The development of software involves a series of production activities
where opportunities for injection of human fallibilities are enormous. Because of human
inability to perform and communicate with perfection, software development is
accomplished by a quality assurance activity.

Testing is a process which reveals errors in the program. It is the major quality
measure employed during software development. During testing, the program is executed
with a set of test cases and the output of the program for the test cases is evaluated to
determine if the program is performing as it is expected to perform.

PET-TP Template v.1.0 Page 69 of 74


Scope This document describes all the tests taking place for JKC Release 1.0. It
covers the design elements specified in the OOD and the detailed
modeling elements of the system being tested.

References User requirements document,


Software Requirements specification document.
Detailed design document.

Testing Objective:
• Testing is a process of executing a program with the intent of finding an error.
• A good test case is the one that has a high probability of finding an as-yet
undiscovered error.
• A successful test is one that uncovers an as-yet undiscovered error.

In order to make sure that the system does not have errors, the different levels of
testing strategies that are applied at different stages of software development are:

 Unit Testing.
 System Testing.

Unit Testing:
Unit testing is done on individual modules as they are completed and become
executable. Unit testing treats each component as stand-alone entity which does not need
other components during the testing process.

System Testing:
This involves in-house testing of the entire system before delivery to the user. Its
aim is to satisfy the user. The system meets all the requirements of the client’s
specification.

Results:-

Administrator module:

1. Test case: Login

PET-TP Template v.1.0 Page 70 of 74


Input : ID, Password.
Process : Click on the login link. If administrator enters ID and password
correct it goes to
the admin services otherwise displays the same page with an error
message.
Output : Displays the admin services page.

2. Test case: Add new employee

Input : Name, Id, designation, Date of joining.


Process : A new employee can be added into the system and admin can
update his details.
Output : The employee can be credited salary based upon his details.

3. Test case: Salary details


Input : Id, designation, basic salary, PF, DA, HRA.
Process : The admin can update his salary details
Output : Employee salary details will be updated to the database.

4. Test case: Loan details


Input : Id, Loan number, EMI, Repaid amount, Balance amount.
Process : Administrator can update a particular employee’s loan details.
Output : Employee Loan details will be updated to the database.

5. Test case: Leave details


Input : Id, Type of leave, Number of Leaves.
Process : Administrator updates the leave details.
Output : Employee Leave details will be updated to the database.

6. Test case: Tax details


Input : Id, Basic salary, Tax percentage, income tax.
Process : The tax details of an employee can be updated by the
administrator.
Output : Employee Tax details will be updated to the database.

7. Test case: Salary slip


Input : Id, Basic salary, Designation, Net pay.

PET-TP Template v.1.0 Page 71 of 74


Process : Based on the leave, loan , tax details the slip will be generated
Output : Salary slip will be generated.

8. Test case: Bank details


Input : Id, Designation, salary
Process : The employee’s salary is credited to bank.
Output : Employee can View and receive the salary.

Employee module:

1. Test case: Login

Input : ID, Password.


Process : Click on the login link. If Employee enters ID and password
correct it goes to the
other page otherwise displays the same page with an error
message.
Output : Displays the Information to be viewed by an employee

2. Test case: Update profile


Input : Id, Name, Designation, Email-id, Mobile number, Address,key
skills,qualification
Process : The employee can update his profile if any modifications occur in
his details
Output : The details of an employee can be updated

3. Test case: Change password


Input : Id, Old password, New password
Process : Employee can be able to change his password by using this test
case
Output : Employee new password will be updated

4. Test case: View earnings


Input : ID, Month, Year.
Process : The earnings can be displayed by this test case
Output : The total earnings of an employee for the specified month and
year can be viewed

PET-TP Template v.1.0 Page 72 of 74


5. Test case: View deductions
Input : Id, Month, Year
Process : The deductions can be known by using this test case
Output : The total deductions of an employee for the specified month and
year can be viewed
6. Test case: View salary slip
Input : Id, Month, Year.
Process : The employee can view the salary slip.
Output : The salary slip of an employee for the specified month and year
can be viewed.

PET-TP Template v.1.0 Page 73 of 74


PET-TP Template v.1.0 Page 74 of 74