Software Requirements Specification free essay sample

Programming Requirements Specification For SYSTEM TO AUTOMATE PAYROLL PROCESSING Team individuals: CH. SAIKIRAN (08R01A0580)- CSE KANTAM RAMESH (08R01A0549)- CSE M. SAIMADHAVI - IT BATCH NO. : 1 TABLE OF CONTENTS 1. Conceptual 2. Necessities Specification (RS) 3. Database Fields Specification 4. Working Environment a. Programming Requirements b. Equipment Requirements 5. Significant Level Design 6. Low Level Design a. Login b. Manager c. Assistant d. Representative 7. Database Design 8. Experiments Abstract of the undertaking: Consider a medium estimated IT foundation which deals with its own finance necessities. This task will intend to build up a mechanized framework to pay representatives their month to month compensation. The framework should store worker compensation subtleties and leave remittance. Toward the month's end the framework ought to consequently credit the employee’s financial balance with their pay. Annual expense and advance installments ought to be deducted at source and fitting records credited. Pay slips ought to likewise be created. This framework can be coordinated with Leave and credit frameworks to give an all encompassing answer for the association. We will compose a custom exposition test on Programming Requirements Specification or then again any comparative point explicitly for you Don't WasteYour Time Recruit WRITER Just 13.90/page Necessities Specification (RS) |No. Prerequisite |Essential or |Description of the Requirement |Remarks | |Desirable | |RS1 |The framework ought to have a login for |Essential |A login box ought to show up when the framework is |The logins are relegated by the | |Administrator | |invoked for Administrator with his/her client |admin. | |name and secret phrase. | |RS2 |The framework ought to have a login for |Essential |A login box ought to show up when the framework is |The logins are doled out by the | |staff. | |invoked for Staff with his/her client name and |admin. | |password. | |RS3 |Data Entry screens to keep up |Essential |Online screens ought to be made with inputs |The data kept up by | |employee data. |from end client. |admin. | |RS4 |Data Entry screens to keep up |Essential |Online screens ought to be made with inputs |The data ought to be | |Allowance data. | |from end client. |maintained by administrator. | |RS5 |Data Entry screens to keep up |Essential |Online screens ou ght to be made with inputs |The data ought to be | |Standard Deductions data. | |from end client. |maintained by administrator. |RS6 |Data Entry screens to keep up |Essential |Online screens ought to be made with inputs |The data ought to be | |Attendance data. | |from end client. |maintained by agent. | |RS7 |Data Entry screens to keep up Other|Essential |Online screens ought to be made with inputs |The data ought to be | |Deductions data. | |from end client. |maintained by | |Staff(clerk/worker). |RS8 |Automatic crediting of worker |Essential |These reports will made when a trigger is | |salary | |initiated by the client | |RS9 |Generation of Salary slip |Desirable |Different Depreciation procedures ought to be| | |evaluated and uilt into the framework. The end | |user ought to be permitted to pick any one. | |RS10 |Generating Salary report |Desirable |Database can keep up the pay reports | Database Fields Specification No. |Field Name |Data Type |Remarks | |1 |Employee Number |Te xt |This is the key field of the database as it is | |unique for a worker. This will likewise fill in as | |the login for the framework. This is an essential 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 and so forth | |7 |Qualification |Text |This determines the Qualification of a worker | |8 |UName |Text | |9 |PWord |Text | |10 |DOR |Date/Time |Date of enlistment of a representative | |11 |Bsalary |Currency |Fixed sum according to worker | |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 personal assessment rule | |25 |PTax |Text |Professional Tax is fixed according to strategy | |26 |AttndMonth |Text | Current Attendance month. | |27 |TotalDays |Number | |Total working days of an association for every 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 pay | |34 |EDULoan |Number |15% of Basic pay | |35 |HealthLoan |Number |5% of Basic pay | 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 acknowledges the username and secret key which on approval passes the control to the individual module. This checks for the approved clients before signing in. b. Chairman: This module is for the executive who keeps up the data of the representatives each related to extraordinary id numbers. c. Representative: This module is for the staff to keep up the participation of the worker and produce the compensations for that present month. d. Representative: This is for the worker who on signing in can see their essential pay, stipends and standard findings gave by the organization. Low Level Design The framework is part in to its plan segments. For every one of the parts, we give data in the accompanying organization: 1. Login Module: This module acknowledges the username and secret key which on approval passes the control to the separate module. This checks for the approved clients before signing in. 2. Overseer Module: This module is for the executive who keeps up the data of the representatives each related to one of a kind id numbers. Their fundamental pay, stipend and standard finding rates are indicated by the executive. He can see the compensation reports of the chose representative for that month and for the given time frame. He can keep up the accompanying data a. Worker information set by head b. Set Allowances c. Set Standard reasonings. d. View Other conclusions. e. View Attendance information. f. View Salary Slip. 3. Representative: This module is for the staff to keep up the participation of the worker and produce the pay rates for that present month. The pay reports for that month and over the given time frame can be seen by the staff. He can likewise see the worker data with stipend and Standard reasoning. Also, he can see the other finding and pay reports. He can keep up the accompanying data a. View Employee information. b. View Allowances data c. View Standard findings. d. Set Other derivations. e. Set Attendance data. f. Get ready Salary Slip. 4. Worker: This is for the representative who on signing in can see their essential compensation, recompenses and standard reasonings gave by the organization. They can determine their different reasonings like Insurance, home advances and so forth which are to be deducted from the present month compensation. These subtleties are to be give by the representative before the compensation date. Worker can likewise see the participation data, compensation slip and pay data. He can keep up the accompanying data a. View Employee information b. View Allowances c. View Standard findings. d. Set Other conclusions. e. View Attendance data. f. View Salary Slip. 5. Mix with leave and credit framework if previously existing, else make screens to enter in leave and advance subtleties. 6. Credit Employee financial balances electronically. 7. Create electronic or printed copies of pay slips. 8. Empower clients to alter annual expense subtleties as these may change much of the time. In general 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] Allowances: [pic]c [pic] Standard Deductions: [pic] Attendance Info: [pic] OtherDeductions: [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 a representative. This will likewise fill in as | |the login for the framework. | |2 |Employee Name |Text |Special characters like underscore are not | |allowed. |3 |Address |Text | |4 |Contacts |Number | |5 |EMail |Text | |6 |Designati on |Text |This determines the assignment in organization | |7 |Qualification |Text |This indicates the Qualification of a representative | |8 |DOR |Date/Time |Date of enlistment of a worker | |9 |Bsalary |Currency |Fixed sum according to representative | |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 annual expense rule | |6 |PTax |Number |Professional Tax is fixed according to strategy | Attendance Table: |No. Field Name |Data type |Remarks | |1 |EmpNo |Number |This is the key field of the database all things considered