Payroll
This document was uploaded by user and they confirmed that they have the permission to share it. If you are author or own the copyright of this book, please report to us by using this DMCA report form. Report DMCA
Overview
Download & View Payroll as PDF for free.
More details
- Words: 8,896
- Pages: 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 NAME:
Inspected/Reviewed By
Approved By
Nalini.Y, Naresh.Ch, Nishitha.A, Priyanka.G, Poornima lavanya.M.
TITLE: Automated Payroll Processing. SIGNATURE: DATE: 30-03-07
VERSION HISTORY Version No. 1.0
Date 30-03-07
Changed By:
Changes Made:
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 .......................................................................43 CONTEXT DIAGRAM........................................................................................................................................................43 REFERENCES...................................................................................................................................................................43 FOLLOWING A TAILORED VERSION OF THE ORGANIZATION’S STANDARD PROCESS.
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. 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.
System in Context:
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):
• • •
System-Wide Requirements (Derived):
• • •
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. 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:
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 US_APP_ADM_02 US_APP_ADM_03
Login Add new employee View Salary details
High High High
Stable Stable Stable
Verifiable Verifiable Verifiable
Use-Case ID
Use-Case Name
Priority
Stability
Verifiability
US_APP_ADM_04 US_APP_ADM_05 US_APP_ADM_06 US_APP_ADM_07
View Loan details View Leave details View Tax details Credit employee acc Generate salary slip Logout
High High High High
Stable Stable Stable Stable
Verifiable Verifiable Verifiable Verifiable
High High
Stable Stable
Verifiable Verifiable
US_APP_ADM_08 US_APP_ADM_09
Use-Case ID
Use-Case Name
Priority
Stability
Verifiability
US_APP_EMP_01 US_APP_EMP_02 US_APP_EMP_03 US_APP_EMP_04 US_APP_EMP_05 US_APP_EMP_06
Login Update profile View Earnings View Deductions View salary slip Logout
High High High High High High
Stable Stable Stable Stable Stable Stable
verifiable Verifiable Verifiable Verifiable Verifiable Verifiable
Use-Cases Specifications Use-Case ID: US_APP_ADM_01 Description:
Use Case Name: Login
The Administrator enters the site through this usecase. This use case provided with ability to view, update and generate salary slip for an
Preconditions: Postconditions: Frequency of Use: Normal Course of Events: Alternative Courses:
employee. Identification of login Updates leave, loan and tax details and generates pay slip for an employee Low Admin logins the system Checks the details of an employee and generate salary slip Administrator has all rights to view and modify or update the all details of an employee.
Use-Case ID: US_APP_ADM_02 Description: Preconditions: Postconditions: Frequency of Use: Normal Course of Events:
The administrator enters the details of new employee. Each employee is provided id and designation. The login id of admin is checked and verified. If it was correct then admin is able to login else rejected. Updates the employee details. High The new employee registration will be done.
Use-Case ID: US_APP_ADM_03 Description: Preconditions: Postconditions: Frequency of Use: Normal Course of Events:
Preconditions: Postconditions: Frequency of Use: Normal Course of Events:
Use Case Name: View salary details
The Administrator view and update the salary details of an employee. The administrator enters the particular employee id, month and year to view the details of an employee. Updates leave, loan and tax details and generates pay slip for an employee High Checks the details of an employee and update salary details.
Use-Case ID: US_APP_ADM_04 Description:
Use Case Name: Add new employee
Use Case Name: View Loan details
The Administrator updates the loan details. Based on this details his salary will be credited. If the employee id is a valid one. he admin will update the loan details of corresponding employee. Updates leave, tax details and generates pay slip for an employee High The loan details includes EMI, repaid amount, balance amount.
Use-Case ID: US_APP_ADM_05 Description: Preconditions: Postconditions: Frequency of Use: Normal Course of Events:
The Administrator updates the leave details. Based on this details his salary will be credited. If the employee id is a valid one. The admin will update the leave details of corresponding employee. Updates tax details and generates pay slip for an employee High Based on the type of a leave and number of days the salary will be credited.
Use-Case ID: US_APP_ADM_06 Description: Preconditions: Postconditions: Frequency of Use: Normal Course of Events:
Preconditions: Postconditions: Frequency of Use: Normal Course of Events:
Preconditions: Postconditions: Frequency of Use: Normal Course of Events:
Use Case Name: Credit employee account
The salary of an employee is credited into his account. The entire details of an employee will be updated by the administrator. Employee can view his salary slip High The employee salary will be credited in to his bank account.
Use-Case ID: US_APP_ADM_08 Description:
Use Case Name: View Tax details
The Administrator updates the Tax details. Based on this details his salary will be credited. If the employee id is a valid one. The admin will update the tax details of corresponding employee. Generates pay slip for an employee High Based on the tax details his salary is given.
Use-Case ID: US_APP_ADM_07 Description:
Use Case Name: View Leave details
Use Case Name: Generate salary slip
The administrator will update the details of an employee and salary slip will be generated. The employee details include loan, leave, tax will be updated. The employee can view the salary slip. High The salary slip will be generated.
Use-Case ID: US_APP_ADM_09 Description: Preconditions: Postconditions: Frequency of Use: Normal Course of Events:
After completion of updating employee details administrator exit from the system. Employee salary slip is generated The administrator can update other employee details. High Administrator exits from this session.
Use-Case ID: US_APP_EMP_01 Description: Preconditions: Postconditions: Frequency of Use: Normal Course of Events:
Preconditions: Postconditions: Frequency of Use: Normal Course of Events:
Use Case Name: Update profile
The employee can update his information.The information include id, designation, email-id, phone number etc. The login id of employee is checked and verified. If it was correct then employee is able to login otherwise rejected. View earnings, deductions and salary slip. High Employee can update his information.
Use-Case ID: US_APP_EMP_03 Description:
Use Case Name: Login
The employee enters the site through this usecase. This use case provided with update profile, view earnings, view deductions, view salary slip. Identification of login. Employee can update profile High Employee can update profile and view his earnings, deductions and salary slip.
Use-Case ID: US_APP_EMP_02 Description:
Use Case Name: Logout
Use Case Name: View earnings The employee can view his earnings that are based on his loan,
Preconditions: Postconditions: Frequency of Use: Normal Course of Events:
leave, tax details. The login id of employee is checked and verified. If it was correct then employee is able to login otherwise rejected. Employee views deductions and salary slip. High Employee can view earnings, deductions and salary slip.
Use-Case ID: US_APP_EMP_04 Description: Preconditions: Postconditions: Frequency of Use: Normal Course of Events:
The employee can view deductions that are based on his loan, leave details. The login id of employee is checked and verified. If it was correct then employee is able to login otherwise rejected. Employee can view his salary slip. High Employee can view deductions.
Use-Case ID: US_APP_EMP_05 Description: Preconditions: Postconditions: Frequency of Use: Normal Course of Events:
Use Case Name: View salary slip Employee can view his salary slip
The entire details of an employee will be updated by the administrator. Employee can view his salary slip High Employee salary slip can be viewed.
Use-Case ID: US_APP_EMP_06 Description:
Use Case Name: View deductions
Use Case Name: Logout
After completion of viewing employee details employee exit from the system.
Preconditions: Postconditions: Frequency of Use: Normal Course of Events:
Employee can view his salary slip. Logout from the system High Employee exits from this session.
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 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 _________________________________________________________________
Automated Payroll Processing Release No. 1
Software Requirements Specification Version No. 1.0
Prepared By: NAME:
Inspected/Reviewed By:
Approved By:
Nalini.Y, Naresh.Ch, Nishitha.A, Priyanka.G, Poornima lavanya.M.
TITLE: Automated Payroll Processing SIGNATURE: DATE: 29-03-07
VERSION HISTORY Version No. 1.0
Date 29-0307
Changed By:
Changes Made:
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 .......................................................................43 CONTEXT DIAGRAM........................................................................................................................................................43 REFERENCES...................................................................................................................................................................43 FOLLOWING A TAILORED VERSION OF THE ORGANIZATION’S STANDARD PROCESS.
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 usecases 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. Machine Domain --- Automated Payroll Processing Problem Frame Problem Domain --- Maintaining employee records, updating profiles, . updating loans LBRCE –JKC. User Requirements Document v.1.0.1 References 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
Software Interfaces
Communications 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. Operating system – WindowsXP/2000 Language -- JSP Database – Oracle Network -- LAN 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 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 employee Verifies and adds
Enter employee id
Salary details
Loan details
Leave details
Tax details
Salary slip
Bank
logout
Gives id
View salary details update loan details update leave details perform tax calculations Generate salary slip
Logout
For Employee:
verify employee account
Employee
Update profile
Change password
Earnings
view earnings
Deductions
salary slip
View deductions View salary slip
Logout Logout
Logout Logout
Logout
Activity Diagram :
Login
Employee
Administrator
Update profile
Add new employee
Salary details
Change password
Loan details
Earnings
Leave details
Deductions
Tax details View salary slip Enter employee id
Salary credited
Yes view salary slip
No
Update salary details
Update Loan details
Update Leave details
Update Tax details
Generate salary slip
View the employ...
Logout
Class Diagram :
status='e' login username pasword
status='a'
Add new employee id name designation date of joining
can
Administrator id password
Bank details id Account number Balance amount
verifies
generates
updates
update salary details id name designation basic salary DA HRA PF
Update profile id name email id qualification key skills address
Employee id password
updates
update() change password id password
salary slip salary month salary year date total earnings total deductions net pay
change password()
view earnings id month year
netamount() update loan details id loan number loan amount repaid amount balance amount EMI balance duration
calculate()
leave details id earned leaves privileged leaves unpaid leaves total leave days leave allowance leave deductions
Tax details id basic salary tax percentage tax amount
earnings()
view deductions id month year
taxdeduction()
Deduction()
deductions()
System Feature ID:
System Feature Name:
SRS_APP_ADM_01 Description:
Activity Diagrams, Sequence Diagrams, Class Diagrams:
Admin Services
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. 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. 2. 3. 4. 5. 6. 7.
Add new employee Update Salary details Update Loan details Update Leave details Update Tax details Generate Salary Slip Verify Employee’s Account
System Feature ID:
System Feature Name:
SRS_APP_EMP_01 Description:
Activity Diagrams, Sequence Diagrams, Class Diagrams:
Employee Services
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 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): •
•
•
Operations:
Object Analysis
1. 2. 3. 4. 5.
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. Update Profile Change password View earnings view deductions view salary slip
1. Admin 2. Employee
S. No. S1
Class Name Admin
Responsibility The admin must assign id’s to all employees and assign a role to them
Persistent (Y / N) Permanent Database
S. No. S2
Class Name Employee
Responsibility Employee updates his profile and checks his salary slip.
Persistent (Y / N) Permanent Database
State Analysis
State Diagram:
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.
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
Earnings
Role
Employee
Update profile
view salary slip
Logout
Nonfunctional Requirements
Deductions
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 By incorporating a robust and proven SQL into the system, reliable performance and integrity of data is ensured. There must be a power Requirements backup for server system.
Performance Requirements
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 _________________________________________________________________
Automated Payroll Processing Release No.1
Detailed Design Version No.1.0
Prepared By: NAME :
Inspected/Reviewed By:
Approved By:
Nalini.Y, Naresh.Ch, Nishitha.A, Priyanka.G, Poornima lavanya.M.
TITLE : Automated Payroll Processing SIGNATURE : DATE : 06-03-07
VERSION HISTORY Version No. 1.0
Date 06-03-07
Changed By:
Changes Made:
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 ...........................................................................43 CONTEXT DIAGRAM............................................................................................................................................................43 REFERENCES.......................................................................................................................................................................43 FOLLOWING A TAILORED VERSION OF THE ORGANIZATION’S STANDARD PROCESS.
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: References:
The Scope of this document is to maintain list of employee ids and related information. • • •
General Considerations
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
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. •
Dependencies: Conventions:
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. The Automated Payroll system details the module uses PHP parser. • 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.
status='e' login username pasword
status='a'
Add new employee id name designation date of joining
can
Administrator id password
update salary details id name designation basic salary DA HRA PF calculate()
Bank details id Account number Balance amount
verifies
generates
updates
Employee id password
updates
update() salary slip salary month salary year date total earnings total deductions net pay netamount()
update loan details id loan number loan amount repaid amount balance amount EMI balance duration
leave details id earned leaves privileged leaves unpaid leaves total leave days leave allowance leave deductions Deduction()
Update profile id name email id qualification key skills address
Tax details id basic salary tax percentage tax amount taxdeduction()
change password id password change password()
view earnings id month year earnings()
view deductions id 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: NAME:
Inspected By:
Approved By:
Nalini.Y, Naresh.Ch, Nishitha.A, Priyanka.G, Poornima lavanya.M.
TITLE:
Automated Payroll Processing
SIGNATURE:
DATE:
23-02-2007
VERSION HISTORY Version No. 1
Date 23-02-2007
Changed By:
Changes Made:
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 .......................................................................43 CONTEXT DIAGRAM........................................................................................................................................................43 REFERENCES...................................................................................................................................................................43 FOLLOWING A TAILORED VERSION OF THE ORGANIZATION’S STANDARD PROCESS.
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
Data Access
Storage Subsystem 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
Business Logic
Legend
Application Layer 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: NAME:
Inspected/Reviewed By:
Approved By:
Nalini.Y, Naresh.Ch, Nishitha.A, Priyanka.G, Poornima lavanya.M.
TITLE: Automated Payroll Processing SIGNATURE: DATE: 06-03-07
VERSION HISTORY Version No. 1.0
Date 06-03-07
Changed By:
Changes Made:
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 .......................................................................43 CONTEXT DIAGRAM........................................................................................................................................................43 REFERENCES...................................................................................................................................................................43 FOLLOWING A TAILORED VERSION OF THE ORGANIZATION’S STANDARD PROCESS.
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 denormalization 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. # 1
Name
Format
When Used
ID Type
Varchar2(10)
For Columns representing the database generated Unique id.
Table Definitions: Table No.: Table Name: Table Description: Seq. Column # Name 1 ID 2
password
1
Admin Column Description Unique identifier password
Column Type Varchar2(10)
PK/FK? Null/ Not Null Not Null
Varchar2(10)
Not Null
Remarks
Relationships: Admin Constraints: No Table No.: Table Name: Table Description: Seq. Column # Name 1 Eno 2
Ename
3
Email-ID
4
Designation
5
Basic Salary
6
Taeleaves
7
Beleaves
8
Tpleaves
2
Employee Contains information of the Employees. Column Column Type PK/FK? Description Unique Number(10) PK Identifier Gives name Varchar2(10) of an employee ID of an Varchar2(30) employee Category of Varchar2(15) an Employee Total Salary Number(10) of an employee Total earned Number(10) leaves of an employee Balance Number(10) earned leaves of an employee Total Number(10) privileged leaves of an employee
Null/ Not Null Not Null Not Null Not Null Not Null Not Null Not Null Not Null
Not Null
Remarks
9
Bpleaves
Balance privileged leaves of an employee
Number(10)
Not Null
Relationships: Employee Constraints: Eno Primary Key. Table No.: Table Name: Table Description: Seq. Column # Name 1 Dname
2 3 4
BasicSalary Earnedleaves Privillaged leaves
3
Designation Gives category of an employee Column Column Type Description Name of Varchar2(15) designation of an employee Total salary Number(10) of an employee Number(10) Number(10)
PK/FK? Null/ Not Null Not Null
Remarks
Not Null Not Null Not Null
Relationships: Designation Constraints: No Table No.: Table Name: Table Description: Seq. Column # Name 1 Eno 2
Type of leave
3
Total days of leave
4
Leave balance
5
Leave availed
Relationships: Leave
4
Leave Gives Leave details of an employee Column Column Type PK/FK? Null/ Description Not Null Unique Number(20) PK identifier Leave type Varchar2(20) Not Null Number of Number(20) leaves of an employee Total days Number(20) of leave – leaves availed Actual taken Number(20) leaves
Remarks
Constraints: Eno is a primary key Table No.: Table Name: Table Description: Seq. Column # Name 1 Loan number 2
Employee number
3
Total loan amount
4
Repaid amount
5
Balance amount EMI
6 7
Balance duration
5
Loan Gives Loan details of an employee Column Column Type PK/FK? Null/ Description Not Null Unique Number(20) PK Not Null identifier ID of an Number(20) FK employee Not Null Actual loan for an employee Loan paid by an employee total loan -repaid Every monthly installment Balance amount/ EMI
Number(20)
Remarks
Not Null
Number(20) Number(20) Number(20) Number(20)
Relationships: Loan, Leave, Employee. Constraints: Loan number is a primary key Eno is a Foreign key Table No.: Table Name: Table Description: Seq. Column # Name 1 Account number 2 Employee number 3
Balance
6
Bank Gives Bank details of an employee Column Column Type PK/FK? Null/ Description Not Null Unique Number(20) PK identifier ID of an Number(20) FK employee Not Null Number(20)
Remarks
Relationships: Bank, loan, leave, employee Constraints: Account number is a primary key Eno is a foreign key. Table No.: Table Name: Table Description: Seq. Column # Name 1 Eno 2
Slip number
3
Salary date
4
Salary month
5
Salary year
6
Basic salary
7
DA
8
HRA
9
PF
10
Leave allowance Income tax
11 12
Unpaid leave deductions
13
EMI
14
Total earnings
15
Total deductions
7
Sal slip Generate a Salary slip for an employee. Column Column Type PK/FK? Null/ Description Not Null Unique Number(10) FK Identifier Unique Number(10) PK Identifier Not Null Date of salary Month of salary Year of a salary Actual salary of an employee 8% of Basic salary Total privileged leaves of an employee Balance privileged leaves of an employee Fixed amount Amount deduced from salary According to unpaid leave taken in the month Every month installment Earnings of an employee Deductions of an employee
Date
Not Null
Varchar2(10)
Not Null
Number(10)
Not Null
Number(10)
Not Null
Number(10) Number(10)
Number(10)
Number(10) Number(10) Number(10)
Number(10) Number(10) Number(10)
Remarks
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.
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 NAME:
Inspected/Reviewed By
Approved By
Nalini.Y, Naresh.Ch, Nishitha.A, Priyanka.G, Poornima lavanya.M.
TITLE: Automated Payroll Processing SIGNATURE: DATE: 29-03-07
VERSION HISTORY Version No. 1.0
Date 29-0307
Changed By
Changes Made
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 ..........................................................................43
FOLLOWING A TAILORED VERSION OF THE ORGANIZATION’S STANDARD PROCESS.
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 Detailed Design Logical Database Design System Test Plan Integration Test Plan Unit Test Plan Code Database successful Successfully integrated all the units Successfully generated pay slip
High-Level Design Detailed Design
Coding Unit Testing Integration Testing System Testing
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 NAME:
Inspected/Reviewed By
Approved By
Nalini.Y, Naresh.Ch, Nishitha.A, Priyanka.G, Poornima lavanya.M.
TITLE : Automated Payroll Processing SIGNATURE: DATE: 29-03-07 VERSION HISTORY Version No. 1.0
Date
Changed By
Changes Made
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 ..............................43 CONTEXT DIAGRAM........................................................................................................................................43 REFERENCES..................................................................................................................................................43 COMMITMENTS BY FOLLOWING A TAILORED VERSION OF THE ORGANIZATION’S STANDARD PROCESS.
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 Process
: ID, Password. : Click on the login link. If administrator enters ID and password
Output
correct it goes to the admin services otherwise displays the same page with an error message. : Displays the admin services page.
2. Test case: Add new employee Input Process
: Name, Id, designation, Date of joining. : 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 Process Output
: Id, designation, basic salary, PF, DA, HRA. : The admin can update his salary details : Employee salary details will be updated to the database.
4. Test case: Loan details Input
Process Output
: Id, Loan number, EMI, Repaid amount, Balance amount. : Administrator can update a particular employee’s loan details. : Employee Loan details will be updated to the database.
5. Test case: Leave details Input Process Output
: Id, Type of leave, Number of Leaves. : Administrator updates the leave details. : Employee Leave details will be updated to the database.
6. Test case: Tax details Input Process
: Id, Basic salary, Tax percentage, income tax. : 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 PET-TP Template v.1.0
: Id, Basic salary, Designation, Net pay.
Page 71 of 74
Process Output
: Based on the leave, loan , tax details the slip will be generated : Salary slip will be generated.
8. Test case: Bank details Input Process Output
: Id, Designation, salary : The employee’s salary is credited to bank. : Employee can View and receive the salary.
Employee module: 1. Test case: Login Input Process
: ID, Password. : Click on the login link. If Employee enters ID and password
Output
correct it goes to the other page otherwise displays the same page with an error message. : 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 Process
: Id, Old password, New password : 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 Process Output year can be
PET-TP Template v.1.0
: ID, Month, Year. : The earnings can be displayed by this test case : The total earnings of an employee for the specified month and viewed
Page 72 of 74
5. Test case: View deductions Input Process Output year can be
: Id, Month, Year : The deductions can be known by using this test case : The total deductions of an employee for the specified month and viewed
6. Test case: View salary slip Input Process Output
: Id, Month, Year. : The employee can view the salary slip. : 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
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 NAME:
Inspected/Reviewed By
Approved By
Nalini.Y, Naresh.Ch, Nishitha.A, Priyanka.G, Poornima lavanya.M.
TITLE: Automated Payroll Processing. SIGNATURE: DATE: 30-03-07
VERSION HISTORY Version No. 1.0
Date 30-03-07
Changed By:
Changes Made:
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 .......................................................................43 CONTEXT DIAGRAM........................................................................................................................................................43 REFERENCES...................................................................................................................................................................43 FOLLOWING A TAILORED VERSION OF THE ORGANIZATION’S STANDARD PROCESS.
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. 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.
System in Context:
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):
• • •
System-Wide Requirements (Derived):
• • •
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. 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:
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 US_APP_ADM_02 US_APP_ADM_03
Login Add new employee View Salary details
High High High
Stable Stable Stable
Verifiable Verifiable Verifiable
Use-Case ID
Use-Case Name
Priority
Stability
Verifiability
US_APP_ADM_04 US_APP_ADM_05 US_APP_ADM_06 US_APP_ADM_07
View Loan details View Leave details View Tax details Credit employee acc Generate salary slip Logout
High High High High
Stable Stable Stable Stable
Verifiable Verifiable Verifiable Verifiable
High High
Stable Stable
Verifiable Verifiable
US_APP_ADM_08 US_APP_ADM_09
Use-Case ID
Use-Case Name
Priority
Stability
Verifiability
US_APP_EMP_01 US_APP_EMP_02 US_APP_EMP_03 US_APP_EMP_04 US_APP_EMP_05 US_APP_EMP_06
Login Update profile View Earnings View Deductions View salary slip Logout
High High High High High High
Stable Stable Stable Stable Stable Stable
verifiable Verifiable Verifiable Verifiable Verifiable Verifiable
Use-Cases Specifications Use-Case ID: US_APP_ADM_01 Description:
Use Case Name: Login
The Administrator enters the site through this usecase. This use case provided with ability to view, update and generate salary slip for an
Preconditions: Postconditions: Frequency of Use: Normal Course of Events: Alternative Courses:
employee. Identification of login Updates leave, loan and tax details and generates pay slip for an employee Low Admin logins the system Checks the details of an employee and generate salary slip Administrator has all rights to view and modify or update the all details of an employee.
Use-Case ID: US_APP_ADM_02 Description: Preconditions: Postconditions: Frequency of Use: Normal Course of Events:
The administrator enters the details of new employee. Each employee is provided id and designation. The login id of admin is checked and verified. If it was correct then admin is able to login else rejected. Updates the employee details. High The new employee registration will be done.
Use-Case ID: US_APP_ADM_03 Description: Preconditions: Postconditions: Frequency of Use: Normal Course of Events:
Preconditions: Postconditions: Frequency of Use: Normal Course of Events:
Use Case Name: View salary details
The Administrator view and update the salary details of an employee. The administrator enters the particular employee id, month and year to view the details of an employee. Updates leave, loan and tax details and generates pay slip for an employee High Checks the details of an employee and update salary details.
Use-Case ID: US_APP_ADM_04 Description:
Use Case Name: Add new employee
Use Case Name: View Loan details
The Administrator updates the loan details. Based on this details his salary will be credited. If the employee id is a valid one. he admin will update the loan details of corresponding employee. Updates leave, tax details and generates pay slip for an employee High The loan details includes EMI, repaid amount, balance amount.
Use-Case ID: US_APP_ADM_05 Description: Preconditions: Postconditions: Frequency of Use: Normal Course of Events:
The Administrator updates the leave details. Based on this details his salary will be credited. If the employee id is a valid one. The admin will update the leave details of corresponding employee. Updates tax details and generates pay slip for an employee High Based on the type of a leave and number of days the salary will be credited.
Use-Case ID: US_APP_ADM_06 Description: Preconditions: Postconditions: Frequency of Use: Normal Course of Events:
Preconditions: Postconditions: Frequency of Use: Normal Course of Events:
Preconditions: Postconditions: Frequency of Use: Normal Course of Events:
Use Case Name: Credit employee account
The salary of an employee is credited into his account. The entire details of an employee will be updated by the administrator. Employee can view his salary slip High The employee salary will be credited in to his bank account.
Use-Case ID: US_APP_ADM_08 Description:
Use Case Name: View Tax details
The Administrator updates the Tax details. Based on this details his salary will be credited. If the employee id is a valid one. The admin will update the tax details of corresponding employee. Generates pay slip for an employee High Based on the tax details his salary is given.
Use-Case ID: US_APP_ADM_07 Description:
Use Case Name: View Leave details
Use Case Name: Generate salary slip
The administrator will update the details of an employee and salary slip will be generated. The employee details include loan, leave, tax will be updated. The employee can view the salary slip. High The salary slip will be generated.
Use-Case ID: US_APP_ADM_09 Description: Preconditions: Postconditions: Frequency of Use: Normal Course of Events:
After completion of updating employee details administrator exit from the system. Employee salary slip is generated The administrator can update other employee details. High Administrator exits from this session.
Use-Case ID: US_APP_EMP_01 Description: Preconditions: Postconditions: Frequency of Use: Normal Course of Events:
Preconditions: Postconditions: Frequency of Use: Normal Course of Events:
Use Case Name: Update profile
The employee can update his information.The information include id, designation, email-id, phone number etc. The login id of employee is checked and verified. If it was correct then employee is able to login otherwise rejected. View earnings, deductions and salary slip. High Employee can update his information.
Use-Case ID: US_APP_EMP_03 Description:
Use Case Name: Login
The employee enters the site through this usecase. This use case provided with update profile, view earnings, view deductions, view salary slip. Identification of login. Employee can update profile High Employee can update profile and view his earnings, deductions and salary slip.
Use-Case ID: US_APP_EMP_02 Description:
Use Case Name: Logout
Use Case Name: View earnings The employee can view his earnings that are based on his loan,
Preconditions: Postconditions: Frequency of Use: Normal Course of Events:
leave, tax details. The login id of employee is checked and verified. If it was correct then employee is able to login otherwise rejected. Employee views deductions and salary slip. High Employee can view earnings, deductions and salary slip.
Use-Case ID: US_APP_EMP_04 Description: Preconditions: Postconditions: Frequency of Use: Normal Course of Events:
The employee can view deductions that are based on his loan, leave details. The login id of employee is checked and verified. If it was correct then employee is able to login otherwise rejected. Employee can view his salary slip. High Employee can view deductions.
Use-Case ID: US_APP_EMP_05 Description: Preconditions: Postconditions: Frequency of Use: Normal Course of Events:
Use Case Name: View salary slip Employee can view his salary slip
The entire details of an employee will be updated by the administrator. Employee can view his salary slip High Employee salary slip can be viewed.
Use-Case ID: US_APP_EMP_06 Description:
Use Case Name: View deductions
Use Case Name: Logout
After completion of viewing employee details employee exit from the system.
Preconditions: Postconditions: Frequency of Use: Normal Course of Events:
Employee can view his salary slip. Logout from the system High Employee exits from this session.
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 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 _________________________________________________________________
Automated Payroll Processing Release No. 1
Software Requirements Specification Version No. 1.0
Prepared By: NAME:
Inspected/Reviewed By:
Approved By:
Nalini.Y, Naresh.Ch, Nishitha.A, Priyanka.G, Poornima lavanya.M.
TITLE: Automated Payroll Processing SIGNATURE: DATE: 29-03-07
VERSION HISTORY Version No. 1.0
Date 29-0307
Changed By:
Changes Made:
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 .......................................................................43 CONTEXT DIAGRAM........................................................................................................................................................43 REFERENCES...................................................................................................................................................................43 FOLLOWING A TAILORED VERSION OF THE ORGANIZATION’S STANDARD PROCESS.
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 usecases 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. Machine Domain --- Automated Payroll Processing Problem Frame Problem Domain --- Maintaining employee records, updating profiles, . updating loans LBRCE –JKC. User Requirements Document v.1.0.1 References 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
Software Interfaces
Communications 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. Operating system – WindowsXP/2000 Language -- JSP Database – Oracle Network -- LAN 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 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 employee Verifies and adds
Enter employee id
Salary details
Loan details
Leave details
Tax details
Salary slip
Bank
logout
Gives id
View salary details update loan details update leave details perform tax calculations Generate salary slip
Logout
For Employee:
verify employee account
Employee
Update profile
Change password
Earnings
view earnings
Deductions
salary slip
View deductions View salary slip
Logout Logout
Logout Logout
Logout
Activity Diagram :
Login
Employee
Administrator
Update profile
Add new employee
Salary details
Change password
Loan details
Earnings
Leave details
Deductions
Tax details View salary slip Enter employee id
Salary credited
Yes view salary slip
No
Update salary details
Update Loan details
Update Leave details
Update Tax details
Generate salary slip
View the employ...
Logout
Class Diagram :
status='e' login username pasword
status='a'
Add new employee id name designation date of joining
can
Administrator id password
Bank details id Account number Balance amount
verifies
generates
updates
update salary details id name designation basic salary DA HRA PF
Update profile id name email id qualification key skills address
Employee id password
updates
update() change password id password
salary slip salary month salary year date total earnings total deductions net pay
change password()
view earnings id month year
netamount() update loan details id loan number loan amount repaid amount balance amount EMI balance duration
calculate()
leave details id earned leaves privileged leaves unpaid leaves total leave days leave allowance leave deductions
Tax details id basic salary tax percentage tax amount
earnings()
view deductions id month year
taxdeduction()
Deduction()
deductions()
System Feature ID:
System Feature Name:
SRS_APP_ADM_01 Description:
Activity Diagrams, Sequence Diagrams, Class Diagrams:
Admin Services
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. 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. 2. 3. 4. 5. 6. 7.
Add new employee Update Salary details Update Loan details Update Leave details Update Tax details Generate Salary Slip Verify Employee’s Account
System Feature ID:
System Feature Name:
SRS_APP_EMP_01 Description:
Activity Diagrams, Sequence Diagrams, Class Diagrams:
Employee Services
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 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): •
•
•
Operations:
Object Analysis
1. 2. 3. 4. 5.
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. Update Profile Change password View earnings view deductions view salary slip
1. Admin 2. Employee
S. No. S1
Class Name Admin
Responsibility The admin must assign id’s to all employees and assign a role to them
Persistent (Y / N) Permanent Database
S. No. S2
Class Name Employee
Responsibility Employee updates his profile and checks his salary slip.
Persistent (Y / N) Permanent Database
State Analysis
State Diagram:
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.
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
Earnings
Role
Employee
Update profile
view salary slip
Logout
Nonfunctional Requirements
Deductions
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 By incorporating a robust and proven SQL into the system, reliable performance and integrity of data is ensured. There must be a power Requirements backup for server system.
Performance Requirements
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 _________________________________________________________________
Automated Payroll Processing Release No.1
Detailed Design Version No.1.0
Prepared By: NAME :
Inspected/Reviewed By:
Approved By:
Nalini.Y, Naresh.Ch, Nishitha.A, Priyanka.G, Poornima lavanya.M.
TITLE : Automated Payroll Processing SIGNATURE : DATE : 06-03-07
VERSION HISTORY Version No. 1.0
Date 06-03-07
Changed By:
Changes Made:
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 ...........................................................................43 CONTEXT DIAGRAM............................................................................................................................................................43 REFERENCES.......................................................................................................................................................................43 FOLLOWING A TAILORED VERSION OF THE ORGANIZATION’S STANDARD PROCESS.
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: References:
The Scope of this document is to maintain list of employee ids and related information. • • •
General Considerations
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
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. •
Dependencies: Conventions:
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. The Automated Payroll system details the module uses PHP parser. • 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.
status='e' login username pasword
status='a'
Add new employee id name designation date of joining
can
Administrator id password
update salary details id name designation basic salary DA HRA PF calculate()
Bank details id Account number Balance amount
verifies
generates
updates
Employee id password
updates
update() salary slip salary month salary year date total earnings total deductions net pay netamount()
update loan details id loan number loan amount repaid amount balance amount EMI balance duration
leave details id earned leaves privileged leaves unpaid leaves total leave days leave allowance leave deductions Deduction()
Update profile id name email id qualification key skills address
Tax details id basic salary tax percentage tax amount taxdeduction()
change password id password change password()
view earnings id month year earnings()
view deductions id 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: NAME:
Inspected By:
Approved By:
Nalini.Y, Naresh.Ch, Nishitha.A, Priyanka.G, Poornima lavanya.M.
TITLE:
Automated Payroll Processing
SIGNATURE:
DATE:
23-02-2007
VERSION HISTORY Version No. 1
Date 23-02-2007
Changed By:
Changes Made:
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 .......................................................................43 CONTEXT DIAGRAM........................................................................................................................................................43 REFERENCES...................................................................................................................................................................43 FOLLOWING A TAILORED VERSION OF THE ORGANIZATION’S STANDARD PROCESS.
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
Data Access
Storage Subsystem 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
Business Logic
Legend
Application Layer 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: NAME:
Inspected/Reviewed By:
Approved By:
Nalini.Y, Naresh.Ch, Nishitha.A, Priyanka.G, Poornima lavanya.M.
TITLE: Automated Payroll Processing SIGNATURE: DATE: 06-03-07
VERSION HISTORY Version No. 1.0
Date 06-03-07
Changed By:
Changes Made:
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 .......................................................................43 CONTEXT DIAGRAM........................................................................................................................................................43 REFERENCES...................................................................................................................................................................43 FOLLOWING A TAILORED VERSION OF THE ORGANIZATION’S STANDARD PROCESS.
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 denormalization 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. # 1
Name
Format
When Used
ID Type
Varchar2(10)
For Columns representing the database generated Unique id.
Table Definitions: Table No.: Table Name: Table Description: Seq. Column # Name 1 ID 2
password
1
Admin Column Description Unique identifier password
Column Type Varchar2(10)
PK/FK? Null/ Not Null Not Null
Varchar2(10)
Not Null
Remarks
Relationships: Admin Constraints: No Table No.: Table Name: Table Description: Seq. Column # Name 1 Eno 2
Ename
3
Email-ID
4
Designation
5
Basic Salary
6
Taeleaves
7
Beleaves
8
Tpleaves
2
Employee Contains information of the Employees. Column Column Type PK/FK? Description Unique Number(10) PK Identifier Gives name Varchar2(10) of an employee ID of an Varchar2(30) employee Category of Varchar2(15) an Employee Total Salary Number(10) of an employee Total earned Number(10) leaves of an employee Balance Number(10) earned leaves of an employee Total Number(10) privileged leaves of an employee
Null/ Not Null Not Null Not Null Not Null Not Null Not Null Not Null Not Null
Not Null
Remarks
9
Bpleaves
Balance privileged leaves of an employee
Number(10)
Not Null
Relationships: Employee Constraints: Eno Primary Key. Table No.: Table Name: Table Description: Seq. Column # Name 1 Dname
2 3 4
BasicSalary Earnedleaves Privillaged leaves
3
Designation Gives category of an employee Column Column Type Description Name of Varchar2(15) designation of an employee Total salary Number(10) of an employee Number(10) Number(10)
PK/FK? Null/ Not Null Not Null
Remarks
Not Null Not Null Not Null
Relationships: Designation Constraints: No Table No.: Table Name: Table Description: Seq. Column # Name 1 Eno 2
Type of leave
3
Total days of leave
4
Leave balance
5
Leave availed
Relationships: Leave
4
Leave Gives Leave details of an employee Column Column Type PK/FK? Null/ Description Not Null Unique Number(20) PK identifier Leave type Varchar2(20) Not Null Number of Number(20) leaves of an employee Total days Number(20) of leave – leaves availed Actual taken Number(20) leaves
Remarks
Constraints: Eno is a primary key Table No.: Table Name: Table Description: Seq. Column # Name 1 Loan number 2
Employee number
3
Total loan amount
4
Repaid amount
5
Balance amount EMI
6 7
Balance duration
5
Loan Gives Loan details of an employee Column Column Type PK/FK? Null/ Description Not Null Unique Number(20) PK Not Null identifier ID of an Number(20) FK employee Not Null Actual loan for an employee Loan paid by an employee total loan -repaid Every monthly installment Balance amount/ EMI
Number(20)
Remarks
Not Null
Number(20) Number(20) Number(20) Number(20)
Relationships: Loan, Leave, Employee. Constraints: Loan number is a primary key Eno is a Foreign key Table No.: Table Name: Table Description: Seq. Column # Name 1 Account number 2 Employee number 3
Balance
6
Bank Gives Bank details of an employee Column Column Type PK/FK? Null/ Description Not Null Unique Number(20) PK identifier ID of an Number(20) FK employee Not Null Number(20)
Remarks
Relationships: Bank, loan, leave, employee Constraints: Account number is a primary key Eno is a foreign key. Table No.: Table Name: Table Description: Seq. Column # Name 1 Eno 2
Slip number
3
Salary date
4
Salary month
5
Salary year
6
Basic salary
7
DA
8
HRA
9
PF
10
Leave allowance Income tax
11 12
Unpaid leave deductions
13
EMI
14
Total earnings
15
Total deductions
7
Sal slip Generate a Salary slip for an employee. Column Column Type PK/FK? Null/ Description Not Null Unique Number(10) FK Identifier Unique Number(10) PK Identifier Not Null Date of salary Month of salary Year of a salary Actual salary of an employee 8% of Basic salary Total privileged leaves of an employee Balance privileged leaves of an employee Fixed amount Amount deduced from salary According to unpaid leave taken in the month Every month installment Earnings of an employee Deductions of an employee
Date
Not Null
Varchar2(10)
Not Null
Number(10)
Not Null
Number(10)
Not Null
Number(10) Number(10)
Number(10)
Number(10) Number(10) Number(10)
Number(10) Number(10) Number(10)
Remarks
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.
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 NAME:
Inspected/Reviewed By
Approved By
Nalini.Y, Naresh.Ch, Nishitha.A, Priyanka.G, Poornima lavanya.M.
TITLE: Automated Payroll Processing SIGNATURE: DATE: 29-03-07
VERSION HISTORY Version No. 1.0
Date 29-0307
Changed By
Changes Made
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 ..........................................................................43
FOLLOWING A TAILORED VERSION OF THE ORGANIZATION’S STANDARD PROCESS.
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 Detailed Design Logical Database Design System Test Plan Integration Test Plan Unit Test Plan Code Database successful Successfully integrated all the units Successfully generated pay slip
High-Level Design Detailed Design
Coding Unit Testing Integration Testing System Testing
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 NAME:
Inspected/Reviewed By
Approved By
Nalini.Y, Naresh.Ch, Nishitha.A, Priyanka.G, Poornima lavanya.M.
TITLE : Automated Payroll Processing SIGNATURE: DATE: 29-03-07 VERSION HISTORY Version No. 1.0
Date
Changed By
Changes Made
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 ..............................43 CONTEXT DIAGRAM........................................................................................................................................43 REFERENCES..................................................................................................................................................43 COMMITMENTS BY FOLLOWING A TAILORED VERSION OF THE ORGANIZATION’S STANDARD PROCESS.
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 Process
: ID, Password. : Click on the login link. If administrator enters ID and password
Output
correct it goes to the admin services otherwise displays the same page with an error message. : Displays the admin services page.
2. Test case: Add new employee Input Process
: Name, Id, designation, Date of joining. : 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 Process Output
: Id, designation, basic salary, PF, DA, HRA. : The admin can update his salary details : Employee salary details will be updated to the database.
4. Test case: Loan details Input
Process Output
: Id, Loan number, EMI, Repaid amount, Balance amount. : Administrator can update a particular employee’s loan details. : Employee Loan details will be updated to the database.
5. Test case: Leave details Input Process Output
: Id, Type of leave, Number of Leaves. : Administrator updates the leave details. : Employee Leave details will be updated to the database.
6. Test case: Tax details Input Process
: Id, Basic salary, Tax percentage, income tax. : 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 PET-TP Template v.1.0
: Id, Basic salary, Designation, Net pay.
Page 71 of 74
Process Output
: Based on the leave, loan , tax details the slip will be generated : Salary slip will be generated.
8. Test case: Bank details Input Process Output
: Id, Designation, salary : The employee’s salary is credited to bank. : Employee can View and receive the salary.
Employee module: 1. Test case: Login Input Process
: ID, Password. : Click on the login link. If Employee enters ID and password
Output
correct it goes to the other page otherwise displays the same page with an error message. : 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 Process
: Id, Old password, New password : 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 Process Output year can be
PET-TP Template v.1.0
: ID, Month, Year. : The earnings can be displayed by this test case : The total earnings of an employee for the specified month and viewed
Page 72 of 74
5. Test case: View deductions Input Process Output year can be
: Id, Month, Year : The deductions can be known by using this test case : The total deductions of an employee for the specified month and viewed
6. Test case: View salary slip Input Process Output
: Id, Month, Year. : The employee can view the salary slip. : 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
