Software Requirements Specification

Software Requirements Specification For SYSTEM TO AUTOMATE PAYROLL PROCESSING Team members: CH. SAIKIRAN (08R01A0580)-CSE KANTAM RAMESH (08R01A0549)-CSE M. SAIMADHAVI -IT BATCH NO. : 1 TABLE OF CONTENTS 1. Abstract 2. Requirements Specification (RS) 3. Database Fields Specification 4. Operating Environment a. Software Requirements b. Hardware Requirements 5. High Level Design 6. Low Level Design a. Login b. Administrator c. Clerk d. Employee 7. Database Design 8. Test cases Abstract of the project: Consider a medium sized IT establishment which manages its own payroll requirements.

This project will aim to develop an automated system to pay employees their monthly wages. The system should store employee salary details and leave allowance. At the end of the month the system should automatically credit the employee’s bank account with their salary. Income tax and loan payments should be deducted at source and appropriate accounts credited. Salary slips should also be generated. This system can be integrated with Leave and loan systems to give a holistic solution to the organization. Requirements Specification (RS) |No. Requirement |Essential or |Description of the Requirement |Remarks | | | |Desirable | | | |RS1 |The system should have a login for |Essential |A login box should appear when the system is |The logins are assigned by the | | |Administrator | |invoked for Administrator with his/her user |admin. | | | |name and password. | | |RS2 |The system should have a login for |Essential |A login box should appear when the system is |The logins are assigned by the | | |staff. | |invoked for Staff with his/her user name and |admin. | | | | |password. | | |RS3 |Data Entry screens to maintain |Essential |Online screens should be created with inputs |The information maintained by | | |employee information. |from end user. |admin. | |RS4 |Data Entry screens to maintain |Essential |Online screens should be created with inputs |The information should be | | |Allowance information. | |from end user. |maintained by admin. | |RS5 |Data Entry screens to maintain |Essential |Online screens should be created with inputs |The information should be | | |Standard Deductions information. | |from end user. |maintained by admin. |RS6 |Data Entry screens to maintain |Essential |Online screens should be created with inputs |The information should be | | |Attendance information. | |from end user. |maintained by clerk. | |RS7 |Data Entry screens to maintain Other|Essential |Online screens should be created with inputs |The information should be | | |Deductions information. | |from end user. |maintained by | | | | | |Staff(clerk/employee). |RS8 |Automatic crediting of employee |Essential |These reports will created when a trigger is | | | |salary | |initiated by the user | | |RS9 |Generation of Salary slip |Desirable |Different Depreciation methodologies should be| | | | | |evaluated and uilt into the system. The end | | | | | |user should be allowed to choose any one. | | |RS10 |Generating Salary report |Desirable |Database can maintain the salary reports | | Database Fields Specification No. |Field Name |Data Type |Remarks | |1 |Employee Number |Text |This is the key field of the database as it is | | | | |unique for an employee.

This will also serve as | | | | |the login for the system. This is a primary key | |2 |Employee Name |Text |Special characters like underscore are not | | | | |allowed. |3 |Email id |Text | | |4 |Address |Memo | | |5 |Contacts |Number | | |6 |Designation |Text |Designation like Clerk, Emp etc | |7 |Qualification |Text |This specifies the Qualification of a employee | |8 |UName |Text | | |9 |PWord |Text | | |10 |DOR |Date/Time |Date of registration of a employee | |11 |Bsalary |Currency |Fixed amount as per employee | |12 |HRA |Text Primary key | |13 |PPA |Text | | |14 |Maint_Allow |Text | | |15 |SPL_Allow |Text | | |16 |EDU_Allow |Text | | |17 |Wash_Allow |Text | | |18 |Sun_Allow |Text | | |19 |EPF |Text |Primary key | |20 |VPF |Text | | |21 |LIC |Text | | |22 |Canteen |Text | | |23 |Transport |Text | | |24 |ITax |Text |According to income tax rule | |25 |PTax |Text |Professional Tax is fixed as per policy | |26 |AttndMonth |Text | Current Attendance month. | |27 |TotalDays |Number | | | | | |Total working days of an organization per month. |28 |PrsntDays |Number |Present Days of an Employee in current month. | |29 |AbsntDays |Number |Absent Days of an Employee in current month. | |30 |ExtraDays |Number |Extra working days of an Employee in current | | | | |month | |31 |PayDays |Number |Payable days | |32 |EntryDate |Text |Attendance Entry date. |33 |HomeLoan |Number |25% of Basic salary | |34 |EDULoan |Number |15% of Basic salary | |35 |HealthLoan |Number |5% of Basic salary | Operating Environment: Software Requirement: Operating System: Windows 2000 or Higher Service Pack: 2+ Platform: JAVA Language: HTML, JSP & JDBC Database :MS Access Web server : Tomcat server Hardware Requirement (Minimum) Processor: PIV Ram: 128 Mb Hard Disk: 1 GB Monitor: VGA Color (256) High Level/Detailed Design (HLD/DD): a. Login :

This module accepts the username and password which on validation passes the control to the respective module. This checks for the authorized users before logging in. b. Administrator: This module is for the administrator who maintains the information of the employees each identified with unique id numbers. c. Clerk: This module is for the staff to maintain the attendance of the employee and generate the salaries for that current month. d. Employee: This is for the employee who on logging in can view their basic salary, allowances and standard deductions provided by the company. Low Level Design The system is split in to its design components.

For each of the components, we provide information in the following format: 1. Login Module: This module accepts the username and password which on validation passes the control to the respective module. This checks for the authorized users before logging in. 2. Administrator Module: This module is for the administrator who maintains the information of the employees each identified with unique id numbers. Their basic salary, allowance and standard deduction percentages are specified by the administrator. He can view the salary reports of the selected employee for that month and for the given period. He can maintain the following information a. Employee info set by administrator b. Set Allowances c.

Set Standard deductions. d. View Other deductions. e. View Attendance info. f. View Salary Slip. 3. Clerk: This module is for the staff to maintain the attendance of the employee and generate the salaries for that current month. The salary reports for that month and over the given period can be viewed by the staff. He can also view the employee information with allowance and Standard deduction. And he can view the other deduction and salary reports. He can maintain the following information a. View Employee info. b. View Allowances info c. View Standard deductions. d. Set Other deductions. e. Set Attendance info. f. Prepare Salary Slip. 4. Employee:

This is for the employee who on logging in can view their basic salary, allowances and standard deductions provided by the company. They can specify their other deductions like Insurance, home loans etc which are to be deducted from the current month salary. These details are to be provide by the employee before the salary date. Employee can also view the attendance information, salary slip and salary information. He can maintain the following information a. View Employee info b. View Allowances c. View Standard deductions. d. Set Other deductions. e. View Attendance info. f. View Salary Slip. 5. Integration with leave and loan system if already existing, else create screens to key in leave and loan details. 6.

Credit Employee bank accounts electronically. 7. Generate electronic or hard copies of pay slips. 8. Enable users to modify income tax details as these may change frequently. OVERALL USECASE DIAGRAM FOR PAYROLL SYSTEM: [pic] USECASE DIAGRAM FOR STAFF: [pic] USECASE DIAGRAM FOR ADMIN: [pic] USECASE DIAGRAM FOR EMPLOYEE: [pic]ACTIVITY DIAGRAM FOR PAYROLL: [pic] CLASS DIAGRAM FOR PAYROLL SYSTEM: [pic] Sequence and Collaboration Diagram for Login: [pic] Employee Info: [pic] [pic] Allowances: [pic]c [pic] Standard Deductions: [pic] [pic] Attendance Info: [pic] [pic] OtherDeductions: [pic] [pic] [pic] [pic] [pic] [pic] [pic]Database Design: Employee table |No. Field Name |Data type |Remarks | |1 |Employee Number |Number |This is the key field of the database as it is | | | | |unique for an employee. This will also serve as | | | | |the login for the system. | |2 |Employee Name |Text |Special characters like underscore are not | | | | |allowed. |3 |Address |Text | | |4 |Contacts |Number | | |5 |EMail |Text | | |6 |Designation |Text |This specifies the designation in org | |7 |Qualification |Text |This specifies the Qualification of a employee | |8 |DOR |Date/Time |Date of registration of a employee | |9 |Bsalary |Currency |Fixed amount as per employee | |10 |UName |Text | | |11 |PWord |Text | | |12 |Status |Text | | Allowance Table: |No. |Field Name |Data type |Remarks | |1 |HRA |Number |Primary key. |2 |EDU_Allow |Number | | |3 |Maint_Allow |Number | | |4 |SPL_Allow |Number | | |5 |Wash_Allow |Number | | |6 | Sun_Allow |Number | | Standard Deductions Table: |No. |Field Name |Data type |Remarks | |1 |EPF |Number |Primary key. |2 |VPF |Number | | |3 |LIC |Number | | |4 |Canteen |Number | | |5 |ITax |Number |According to income tax rule | |6 |PTax |Number |Professional Tax is fixed as per policy | Attendance Table: |No. Field Name |Data type |Remarks | |1 |EmpNo |Number |This is the key field of the database as it is unique for an | | | | |employee. This will also serve as the login for the system. | |2 |Attndmonth |Date | Current Attendance month. | |3 |Tdays |Number | | | | | |Total working days of an organization per month. |4 |Pdays |Number |Present Days of an Employee in current month. | |5 |Adays |Number |Absent Days of an Employee in current month. | |6 |Edays |Number |Extra working days of an Employee in current month | |7 |Paydays |Number |Payable days | |8 |Edate |Date |Attendance Entry date. | | | | | Other Deductions Table: |No. Field Name |Data type |Remarks | |1 |EmpNo |Number |This is the key field of the database as it is | | | | |unique for an employee. This will also serve as | | | | |the login for the system. | |2 |Homeloan |Number |25% of Basic salary | |3 |EDUloan |Number |15% of Basic salary | |4 |Healthloan |Number |5% of Basic salary |

Test-Plan (Unit test-plan and integrated test-plan) |No. |Test case Title |Description |Expected Outcome |The requirement in RS|Result | | | | | |that is being tested | | |1 |Successful User |The login to the system should |Login should be |RS1, RS2 | | | |Verification |be tried with the login assigned|successful and the | | | | | |by the admin and the correct |user hould enter in | | | | | |password |to the system | | | |2 |Unsuccessful User |The login to the system should |Login should be |RS1, RS2 | | | |Verification |be tried with the login assigned|unsuccessful and the | | | | | |by the admin and the incorrect |user should enter in | | | | | |password |to the error page. | | |3 |Successful data entry |After login the user should |The data entry should |RS3 | | | |of employee information. |enter the correct employee |be successfull | | | | | |information. | | | | |4 |Unuccessful data entry |After login the user should |The data entry should |RS3 | | | |of employee information. |enter the incorrect employee |be unsuccessfull | | | | | |information. | | | | |Successful data entry |After login the user should |The data entry of |RS4 | | |5 |of Allowances. |enter the correct Allowances |allowances should be | | | | | |information. |successfull | | | |6 |Unsuccessful data entry |After login the user should |The data entry of |RS4 | | | |of |enter the incorrect Allowances |allowances should be | | | | |Allowances. |information. unsuccessfull | | | |7 |Successful data entry |After login the user should |The data entry of |RS5 | | | |of Standard deductions. |enter the correct Standard |Standard deductions | | | | | |deductions information. |should be | | | | | | |successfull | | | |8 |Unsuccessful data entry |After login the user should |The data entry of |RS5 | | | |of Standard deductions. enter the incorrect Standard |Standard deductions | | | | | |deductions information. |should be | | | | | | |successfull | | | |9 |Successful data entry of |After login the user should |The data entry of |RS6 | | | |Attendance. |enter the correct Attendance |Other deductions | | | | | |information. should be | | | | | | |successfull | | | | |Unsuccessful data entry |After login the user should |The data entry of |RS6 | | |10 |of Attendance. |enter the incorrect Attendance |Other deductions | | | | | |information. |should be | | | | | | |unsuccessfull | | | |11 |Successful data entry of |After login the user should |The data entry of |RS7 | | | |Other deductions. enter the correct Other |Other deductions | | | | | |deductions information. |should be | | | | | | |successfull | | | |12 |Unsuccessful data entry |After login the user should |The data entry of |RS7 | | | |of Other deductions. |enter the incorrect Other |Other deductions | | | | | |deductions information. should be | | | | | | |unsuccessfull | | | |13 |Navigation between |Screen navigation should be |The screens navigated | | | | |screens is Role based |checked to ensure correct |should be based on the| | | | | |sequence of screens is thrown to|role of user | | | | | |the user. | | | | |14 |Database interactions |Values stored in the database |Data retrieved should | | | | |should be accurate |should be what the user intended|be what is stored in | | | | | |to store. the database | | | |15 |Boundary conditions |When scrolling options are |UI should support | | | | |should be checked |enabled on screens data between |boundry level | | | | | |different pages should be |conditions | | | | | |accurate | | | | |16 |Accurate reports should |The reports should be accurate | | | | | |be created. | | | | | ———————– Employee details, investment details, salary details, tax rules, leave details Data entry for employee details, Income tax rules, Leave rules, loan details Apply leave, key in investment details, Employee Salary Slips Administrator