Payroll

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 ProcessingRelease 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 No.

Date Changed By: Changes Made:

1.0 30-03-07


User Requirements Document

Table of Contents

OVERVIEW....................................................................................................................................................................4

CUSTOMER....................................................................................................................................................................4PURPOSE........................................................................................................................................................................4SCOPE............................................................................................................................................................................4REFERENCES..................................................................................................................................................................4

GENERAL REQUIREMENTS.....................................................................................................................................5

SYSTEM IN CONTEXT....................................................................................................................................................5USER CHARACTERISTICS...............................................................................................................................................5CONSTRAINTS................................................................................................................................................................5SYSTEM-WIDE REQUIREMENTS (RECEIVED)................................................................................................................5SYSTEM-WIDE REQUIREMENTS (DERIVED).................................................................................................................5

DETAILED REQUIREMENTS....................................................................................................................................5

FUNCTIONAL REQUIREMENTS.......................................................................................................................................5Use-Case Overview..................................................................................................................................................6Use-Cases Specifications.........................................................................................................................................8

TECHNICAL REQUIREMENTS.......................................................................................................................................12Operational Environment.......................................................................................................................................12Development Environment....................................................................................................................................12

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 (Received):

The system generates the pay slip for an employee. The pay slip includes entire information about the earnings,

deductions. The employee can view the pay slip.

System-Wide Requirements (Derived):

The employee can update his personal profile. The employee can change password. 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:

Add New Employee

View Salary details

View Loan details

View Leave details

View Income Tax rules

Credit Employee Account

Generate Salary Slip

View Deductions

View Earnings

Log Out

Update Profile

Administrator

Login

Employee

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 VerifiableUS_APP_ADM_02 Add new employee High Stable VerifiableUS_APP_ADM_03 View Salary details High Stable Verifiable


US_APP_ADM_04 View Loan details High Stable VerifiableUS_APP_ADM_05 View Leave details High Stable VerifiableUS_APP_ADM_06 View Tax details High Stable VerifiableUS_APP_ADM_07 Credit employee

accHigh Stable Verifiable

US_APP_ADM_08 Generate salary slip High Stable Verifiable US_APP_ADM_09 Logout High Stable Verifiable


US_APP_EMP_01 Login High Stable verifiableUS_APP_EMP_02 Update profile High Stable VerifiableUS_APP_EMP_03 View Earnings High Stable VerifiableUS_APP_EMP_04 View Deductions High Stable VerifiableUS_APP_EMP_05 View salary slip High Stable VerifiableUS_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 loginPostconditions: Updates leave, loan and tax details and generates pay slip for an

employeeFrequency of Use: LowNormal Course of Events:

Admin logins the system 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: HighNormal Course of Events:

The new employee registration will be done.

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: HighNormal Course of Events:

Checks the details of an employee and update salary details.

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 employeeFrequency of Use: HighNormal Course of Events:

The loan details includes EMI, repaid amount, balance amount.

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 employeeFrequency of Use: High Normal Course of Events:

Based on the type of a leave and number of days the salary will be 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 employeeFrequency of Use: HighNormal Course of Events:

Based on the tax details his salary is given.

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 slipFrequency of Use: HighNormal Course of Events:

The employee salary will be credited in to his bank account.

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: HighNormal Course of Events:

The salary slip will be generated.

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 generatedPostconditions: The administrator can update other employee details.Frequency of Use: HighNormal Course of Events:

Administrator exits from this session.

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 profileFrequency of Use: HighNormal Course of Events:

Employee can update profile and view his earnings, deductions and 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: HighNormal Course of Events:

Employee can update his information.

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: HighNormal Course of Events:

Employee can view earnings, deductions and salary slip.

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: HighNormal Course of Events:

Employee can view deductions.

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 slipFrequency of Use: HighNormal Course of Events:

Employee salary slip can be viewed.

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 systemFrequency of Use: HighNormal Course of Events:

Employee exits from this session.

Technical RequirementsThe 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 Environment:

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

Development Environment:

Requires JSP and remaining same as Operational Environment

LBRCE - JKC

Automated Payroll Processing Release No. 1

Software Requirements Specification Version No. 1.0

Institute For Electronic Governance _________________________________________________________________


Release No. 1

Software Requirements Specification Version No. 1.0

Prepared By: Inspected/Reviewed By: Approved By:


TITLE: Automated Payroll Processing

SIGNATURE:

DATE: 29-03-07

VERSION HISTORY

Version No.

Date Changed By: Changes Made:

1.0 29-03-07


Software Requirements Specification

Table of Contents

OVERVIEW 4

PROBLEM FRAME 4REFERENCES 4

INTERFACE REQUIREMENTS4

USER INTERFACES 4HARDWARE INTERFACES 4SOFTWARE INTERFACES 4COMMUNICATIONS INTERFACES 4

FUNCTIONAL REQUIREMENTS 5

FEATURE ANALYSIS 5OBJECT ANALYSIS 6STATE ANALYSIS 7FORMAL ANALYSIS 8

NON-FUNCTIONAL REQUIREMENTS 9

PERFORMANCE REQUIREMENTS 9SAFETY & RELIABILITY REQUIREMENTS 9SECURITY REQUIREMENTS 9Software Quality Attributes 9

OverviewThe 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.1Interface RequirementsThis section defines the parameters that the software product must follow while interacting with the outside world.User Interfaces 1. Login Screen

2. Menu selection Screen3. Employee Salary Details4. Employee Loan Details5. Employee Leave Details6. Employee Tax Details7. Generate Salary Slip8. Employee Bank Details

Hardware InterfacesServer 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/2000Language -- JSPDatabase – OracleNetwork -- LAN

Communications Interfaces

Communications interfaces can be provided through e-mail, web browser, 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 RequirementsThis 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 employee

Enter employee id

Salary details Loan details Leave details Tax details Salary slip Bank

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 password

Earnings Deductions salary slip

Logout

view earnings View deductions

View salary slip

Logout

Logout

Logout

Logout

Activity Diagram :

Login

Add new employee

Salary details

Loan details

Leave details

Tax details

Enter employee id Salary credited

view salary slip

Yes

Update salary details

No

Update Loan details

Update Leave details

Update Tax details

Generate salary slip

View the employ...

EmployeeAdministrator

Update profile

Change password

Earnings

Deductions

View salary slip

Logout

Class Diagram :

Add new employee

idnamedesignationdate of joining

update salary details

idnamedesignationbasic salaryDAHRAPF

calculate()

update loan details

idloan numberloan amountrepaid amountbalance amountEMIbalance duration

leave details

idearned leavesprivileged leavesunpaid leavestotal leave daysleave allowanceleave deductions

Deduction()

Tax details

idbasic salarytax percentagetax amount

taxdeduction()

Bank details

idAccount numberBalance amount

Administrator

idpassword

can

updatesupdates

verifies

login

usernamepasword

status='a'

Update profile

idnameemail idqualificationkey skillsaddress

update()

change password

idpassword

change password()

view earnings

idmonthyear

earnings()

view deductions

idmonthyear

deductions()

salary slip

salary monthsalary yeardatetotal earningstotal deductionsnet pay

netamount()

generates

Employee

idpassword

status='e'

System Feature ID: SRS_APP_ADM_01

System Feature Name: 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, Sequence Diagrams, Class Diagrams:

List the graphical models used to analyze the features and to better understand what needs to happen in the system. This 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 employee2. Update Salary details3. Update Loan details4. Update Leave details5. Update Tax details6. Generate Salary Slip7. Verify Employee’s Account

System Feature ID: SRS_APP_EMP_01

System Feature Name: 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, Sequence Diagrams, Class Diagrams:

List the graphical models used to analyze the features and to better understand what needs to happen in the system. This 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 Profile2. Change password3. View earnings4. view deductions5. view salary slip

Object Analysis 1. Admin2. Employee

S. No. Class Name Responsibility Persistent (Y / N)S1 Admin The admin must assign id’s to

all employees and assign a role to them

PermanentDatabase

S. No. Class Name Responsibility Persistent (Y / N)S2 Employee Employee updates his profile

and checks his salary slip.PermanentDatabase

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

Generate salary slip

Logout

Update Leave details

Update Loan details

Update salary details

Update Tax details

Verify bank details

For Employee:

Login

EmployeeEarnings Deductions

Role

Update profile

Logout

view salary slip

Nonfunctional Requirements

Performance Requirements

System can withstand even though many number of users requested 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 Requirements

By incorporating a robust and proven SQL into the system, reliable performance and integrity of data is ensured. There must be a power backup for server system.

Security Requirements

Sensitive data is protected from unwanted access by users appropriate technology and implementing strict user- access criteria.

Software Quality Attributes

Menu-driven programs with user friendly interface with simply hyper 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

_________________________________________________________________


Release No.1

Detailed Design Version No.1.0


NAME : Nalini.Y, Naresh.Ch, Nishitha.A, Priyanka.G, Poornima lavanya.M. TITLE : Automated Payroll Processing

SIGNATURE :

DATE : 06-03-07

VERSION HISTORY

Version No.

Date Changed By:

Changes Made:

1.0 06-03-07


Detailed Design

Table of Contents

INTRODUCTION 4

SCOPE 4REFERENCES 4

GENERAL CONSIDERATIONS4

DECISIONS 4DEPENDENCIES 4CONVENTIONS 4

DETAILED DESIGN 4

CLASS DESIGN 4USE-CASE DESIGN 4

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.

Add new employee

idnamedesignationdate of joining

update salary details

idnamedesignationbasic salaryDAHRAPF

calculate()

update loan details

idloan numberloan amountrepaid amountbalance amountEMIbalance duration

leave details

idearned leavesprivileged leavesunpaid leavestotal leave daysleave allowanceleave deductions

Deduction()

Tax details

idbasic salarytax percentagetax amount

taxdeduction()

Bank details

idAccount numberBalance amount

Administrator

idpassword

can

updatesupdates

verifies

login

usernamepasword

status='a'

Update profile

idnameemail idqualificationkey skillsaddress

update()

change password

idpassword

change password()

view earnings

idmonthyear

earnings()

view deductions

idmonthyear

deductions()

salary slip

salary monthsalary yeardatetotal earningstotal deductionsnet pay

netamount()

generates

Employee

idpassword

status='e'

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

Add New Employee

View Salary details

View Loan details

View Leave details




View Deductions

View Earnings

Log Out

Update Profile

Administrator

Login

Employee

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 DocumentVersion 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 No.

Date Changed By:

Changes Made:

1 23-02-2007

REPOSITORY SEARCH ENGINE FOR ALUMNI OF COLLEGE

High Level Design Document

Table of Contents

INTRODUCTION...........................................................................................................................................................4

CONTEXT DIAGRAM......................................................................................................................................................4REFERENCES..................................................................................................................................................................4

SYSTEM DESCRIPTION.............................................................................................................................................4

SCOPE............................................................................................................................................................................4SUCCESS CRITERIA........................................................................................................................................................4GLOSSARY.....................................................................................................................................................................4

CONSTRAINTS..............................................................................................................................................................4

TECHNICAL CONSTRAINTS............................................................................................................................................4BUSINESS CONSTRAINTS...............................................................................................................................................4

ARCHITECTURAL REQUIREMENTS.....................................................................................................................5

SYSTEM ARCHITECTURE.........................................................................................................................................5

LOGICAL VIEW..............................................................................................................................................................5ALTERNATE SUPPORTING VIEWS..................................................................................................................................5USE CASE SUMMARY....................................................................................................................................................5

ARCHITECTURAL ANALYSIS..................................................................................................................................5

UTILITY TREE................................................................................................................................................................5ARCHITECTURAL DECISIONS.........................................................................................................................................5

Issue/Decision/Rationale..........................................................................................................................................6

Open Issues.......................................................................................................................................................................6

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

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

System DescriptionScope 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

Event DrivenWeb based System

PPS SystemBusiness Logic

Data Access

PersonalPersistent

Data Repository

Storage Subsystem

Application Layer Interface

Application Layer

needlessly duplicating user interface software, database software, etc. Its main focus is on the generation of reports at any time. Success CriteriaThis 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

Business Logic

Data Access

Legend

Application Layer

Dependency

Use-Case Summary

Add New Employee

View Salary details

View Loan details

View Leave details




View Deductions

View Earnings

Log Out

Update Profile

Administrator

Login

Employee

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


Release No.1

Logical Database Design Version No.1.0

ND System Solutions _________________________________________________________________


Release No.1

Logical Database Design

Version No.1.0




SIGNATURE:

DATE: 06-03-07

VERSION HISTORY

Version No.

Date Changed By:

Changes Made:

1.0 06-03-07

Automated Payroll ProcessingLogical Database Design

Table of Contents

OVERVIEW 4

SCOPE: 4REFERENCES: 4

TABLE DEFINITIONS: 5

ADMIN 5EMPLOYEE 5DESIGNATION 6LEAVE 7LOAN 7BANK8Salslip 8

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.: 1Table Name: AdminTable Description:Seq. #

Column Name

Column Description

Column Type PK/FK? Null/Not Null

Remarks

1 ID Unique identifier

Varchar2(10) Not Null

2 password password Varchar2(10) Not Null

Relationships: AdminConstraints: No

Table No.: 2Table Name: EmployeeTable Description: Contains information of the Employees.Seq. #

Column Name

Column Description


Remarks

1 Eno Unique Identifier

Number(10) PK Not Null

2 Ename Gives name of an employee

Varchar2(10)Not Null

3 Email-ID ID of an employee


4 Designation Category of an Employee


5 Basic Salary Total Salary of an employee

Number(10) Not Null

6 Taeleaves Total earned leaves of an employee

Number(10) Not Null

7 Beleaves Balance earned leaves of an employee

Number(10) Not Null

8 Tpleaves Total privileged leaves of an employee

Number(10) Not Null

9 Bpleaves Balance privileged leaves of an employee

Number(10) Not Null

Relationships: Employee Constraints: Eno Primary Key.

Table No.: 3Table Name: Designation Table Description: Gives category of an employeeSeq. #

Column Name

Column Description


Remarks

1 Dname Name of designation of an employee


2 BasicSalary Total salary of an employee

Number(10)Not Null

3 Earnedleaves Number(10) Not Null 4 Privillaged

leavesNumber(10) Not Null

Relationships: Designation Constraints: No

Table No.: 4Table Name: Leave Table Description: Gives Leave details of an employeeSeq. #

Column Name

Column Description


Remarks

1 Eno Unique identifier

Number(20) PK

2 Type of leave Leave type Varchar2(20)Not Null

3 Total days of leave

Number of leaves of an employee

Number(20)

4 Leave balance Total days of leave – leaves availed

Number(20)

5 Leave availed Actual taken leaves

Number(20)

Relationships: Leave

Constraints: Eno is a primary key

Table No.: 5Table Name: Loan Table Description: Gives Loan details of an employeeSeq. #

Column Name

Column Description


Remarks

1 Loan number Unique identifier

Number(20) PK Not Null

2 Employee number

ID of an employee

Number(20) FKNot Null

3 Total loan amount

Actual loan for an employee

Number(20) Not Null

4 Repaid amount

Loan paid by an employee

Number(20)

5 Balance amount

total loan -repaid

Number(20)

6 EMI Every monthly installment

Number(20)

7 Balance duration

Balance amount/EMI

Number(20)

Relationships: Loan, Leave, Employee.Constraints: Loan number is a primary key Eno is a Foreign key

Table No.: 6Table Name: BankTable Description: Gives Bank details of an employeeSeq. #

Column Name

Column Description


Remarks

1 Account number

Unique identifier

Number(20) PK

2 Employee number

ID of an employee

Number(20) FKNot Null

3 Balance Number(20)

Relationships: Bank, loan, leave, employeeConstraints: Account number is a primary key

Eno is a foreign key.

Table No.: 7Table Name: Sal slipTable Description: Generate a Salary slip for an employee.Seq. #

Column Name

Column Description


Remarks

1 Eno Unique Identifier

Number(10) FK

2 Slip number Unique Identifier

Number(10) PKNot Null

3 Salary date Date of salary

Date Not Null

4 Salary month Month of salary


5 Salary year Year of a salary

Number(10) Not Null

6 Basic salary Actual salary of an employee

Number(10) Not Null

7 DA 8% of Basic salary

Number(10)

8 HRA Total privileged leaves of an employee

Number(10)

9 PF Balance privileged leaves of an employee

Number(10)

10 Leave allowance

Fixed amount

Number(10)

11 Income tax Amount deduced from salary

Number(10)

12 Unpaid leave deductions

According to unpaid leave taken in the month

Number(10)

13 EMI Every month installment

Number(10)

14 Total earnings Earnings of an employee

Number(10)

15 Total deductions

Deductions of an employee

Number(10)

16 Net pay Final salary of an employee

Number(10)

Relationships: Salslip, bank, loan, leave, employee. Constraints: Slip number is a primary key Eno Foreign Key.


Release No.1

Software Project Management Plan Version No.1.0

Institute For Electronic Governance _______________________________________________________________

__


Release No.1

Software Project Management Plan Version No. 1.0




SIGNATURE:

DATE: 29-03-07

VERSION HISTORY

Version No.

Date Changed By Changes Made

1.0 29-03-07

Table of Contents

1 PURPOSE...............................................................................................................................................3

2 SOFTWARE LIFECYCLE...................................................................................................................3

3 WORK BREAKDOWN STRUCTURE...............................................................................................3

4 SCHEDULE AND RESPONSIBILITIES...............................................................................................3

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

deliverables.

Software LifecycleThe project follows a certain waterfall style pattern of development. It has following phases.

Stage Deliverable

Requirements Engineering Business Case and Vision User Requirements DocumentSoftware Requirements Specification

High-Level Design High Level DesignDetailed Design Detailed Design

Logical Database DesignSystem Test PlanIntegration Test PlanUnit Test Plan

Coding CodeDatabase

Unit Testing successfulIntegration Testing Successfully integrated all the

unitsSystem 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 PlanVersion No. 1.0

ND System Solutions _________________________________________________________________


Release No. 1

Test Plan Version No. 1.0



TITLE : Automated Payroll Processing

SIGNATURE:

DATE: 29-03-07

VERSION HISTORY

Version No.

Date Changed By Changes Made

1.0 29-03-07

PET-TP Template v.1.0 of 64

Automated Payroll processing

Test Plan

Table of Contents

INTRODUCTION 4

SCOPE 4REFERENCES 4

SYSTEM TEST PLAN 4

INTEGRATION TEST PLAN 5

UNIT TEST 5

MANUAL TEST SCRIPTS 6

Automated Test Scripts 6


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.

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

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 detailsOutput : 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.Process : Based on the leave, loan , tax details the slip will be generatedOutput : Salary slip will be generated.

8. Test case : Bank details

Input : Id, Designation, salaryProcess : 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,qualificationProcess : The employee can update his profile if any modifications occur in his detailsOutput : The details of an employee can be updated

3. Test case : Change password


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

4. Test case : View earnings

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

5. Test case : View deductions

Input : Id, Month, YearProcess : The deductions can be known by using this test caseOutput : The total deductions of an employee for the specified month and year can be viewed6. 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.


Payroll

Documents

Transcript of Payroll