|
Software
Requirement Specifications on
|
PAYROLL SYSTEM
|
********PAGE BREAK************
|
Table
of Contents
1.1
Purpose……………………………………………….……................3
1.2
Scope…………………………………………………………...........3
1.3
Benefits………………………………………………..……..….......3
1.4
Definitions……………………………………………..…..…...…...3
1.5
References…………………………………………..…..…….....…..3
1.6
Project Overview……………………………………......…..….……4
2.
Overall descriptions………………………………………........4
2.1
Product
Perspective…………..…………………….………….4
2.2
Product Functions……………………...……..…………........4
2.2.1
Master Module…………………………..…….……………….....4
2.2.2
Employee Module………………………….…………………..…4
2.2.3
Attendance Module………………………….……………..……..4
2.2.4
Salary
Module…………………………………………….……..4
2.3
User Characteristics………………………..………………….5
2.3.1
End User………………………………………………....….......5
2.3.2
Administrator…………………………………………….….…..5
2.4 Assumptions
& Dependencies………………………..….…......5
3.
Specific Requirements………………………………….……...6
3.1
External interface requirements………………………..…...…..6
3.1.1
User interface requirement…………………………….…..………6
3.1.2
Hardware interface requirement…………………………...….……6
3.1.3
Software interface
requirements…………………………..…..……6
4.
Functional Requirements……………………………..…...……6
4.1
Masters……………………………………………………....………6
4.2
Employee…………………………………………………..…..…….6
4.3
Search………………………………………………………....……..6
4.4
Attendences…………………………………………………....…….6
4.5
Salary……………………………………………………….…..…...6
5.
Other non functional requirements…………………….…..…..7
5.1 Performance
Requirements…………………………………..…..…7
5.2
Reliability……………………………………………………..….…7
5.3
Availability………………………………………………….….…...7
5.4
Security……………………………………………...………………7
6.
UML diagrams
6.1
USECASE
diagram
6.2
ACTIVITY diagram
6.3
CLASS diagram
6.4
SEQUENCE diagram
**********PAGE BREAK*********
1.Introduction
Payroll system is the heart of any Human Resource System
of an organization. The solution has to
take care of the calculation of salary as per rules of the company, income tax calculation and various
deductions to be done from the salary including
statutory deductions like Income tax and provident
fund deductions. It has to generate pay-slip, cheque summary and MIS reports.
It is
understood that we are tired of managing thousand of odd papers, pay slip , payroll reports, and salary details and so on. Imagine that we have a payroll processing system which will generate our pay slips and payroll reports within seconds.
We can help others automated your payroll system by developing a customized payroll application that suits
your specific requirements.
1.1 Purpose
Main aim of
developing Employee Payroll Management is
to provide an easy way not only to automate all functionalities involved
managing leaves and Payroll for the employees of Company, but also to provide
full functional reports to management of Company with the details about usage
of leave facility.
We are committed to
bring the best way of management in the various forms of EPM. We
understand that EPM in not a product to be sold, it is a tool to manage
the inner operation of Company related to employee leave and Payroll.
1.2
Scope
This Application
works in Multiple PC’s installed on multiple Computers but sharing same
database by which users of different department can use it sitting at different
locations simultaneously.
But in future we can make the
Application where the database will be hosted in order to manage the all
departments which will be located in different places and by keeping domain of
Application as Online.
1.3 Benefits
- To improve
the efficiency.
- Quickly
find out information of an employee details.
- To provide
easy and faster access information.
- To
provide user friendly environment.
1.4 Definitions, Acronyms, Abbreviations
SRS -
Software
Requirements Specification.
EPM - Employee Payroll Management.
1.5 References
·
Software Engineering by
“Roger Pressman”.
1.6 Project Overview
·
The following subsections provide the
complete overview of the software specifications requirements documentation for
the product Employee Payroll Management. The entire SRS is documented in view
of User and the following sub sections are arranged to give a complete outlook
of the software, its perspective, features, system requirements and users know
how it is.
2.
Overall description
2.1
Product perspective
·
This software is developed specifically
to cater the company employees leave management, is totally self contained and
works efficiently. It provides simple database rather than complex ones for
high requirements and it provides good and easy graphical user interface to
both new as well as experienced user of the computer.
2.2 Product functions
2.2.1 Master module
- Designation : Contains the position or status of employee in
departments.
- Department : Contains the information about different departments
in any company.
2.2.2 Employee module
·
Employee
details :This module contains the whole detail of employees of any system.
2.2.3 Attendance module
- Leave : This module is for keeping the records of leave taken by
any employee.
- Attendance : This module is for keeping the records of employee’s
presence.
2.2.4 Salary module
- Allowance : This module is for calculating the allowance given to
employee by the instution.
- Deduction : This module calculates the amount from number of days
taken as leave and deduct these amount from salary.
- Pay Slip : This module is for generating the final pay slip.
2.3
User Characteristics
2.3.1 End Users
Ø No specific knowledge or skills
are required from the end user.
Ø End user should have basic idea about computer operations and
database.
2.3.2 Administrator
Ø Administrator must be having good knowledge of
database management system.
Ø Administrator to manage user rights.
Ø If the network connection does not work properly than our system
should not work as intended.
Ø Also that is assumed that the product is installed properly at web
server.
Ø This system will not take care of any virus problem, which might occur
either on the client
or the server system. Avoiding the use of pirated software and ensuring that
floppies
and other removable media are scanned for
viruses before
use could minimize the possibility of viral
infection
Ø Recovery of data after a system crash will be
possible only if backups are taken at regular intervals.
Ø Manual interfaces cannot be
fully avoided. Documented proofs like data entry of employees etc. will have to
be verified by the concerned management staff
before entering it into the computerized system.
2.4 Assumptions and
Dependencies
2.4.1 Assumptions:
·
The code should be free with compilation
errors/syntax errors.
·
The product must have an interface which is
simple enough to understand.
2.4.2 Dependencies:
·
All necessary hardware and software are available
for implementing and use of the tool.
·
The proposed system would be designed,
developed and implemented based on the software requirements specifications
document.
·
End users should have basic knowledge of
computer and we also assure that the users will be given software training
documentation and reference material.
·
The
system is not required to save generated reports.
3. Specific requirements
3.1 External
interface requirements
3.1.1 User interfaces
·
The software provides good graphical
interface to the user.
3.1.2 Hardware interfaces
·
Mouse
·
Keyboard
·
Printer
·
Hard disk
·
Ram with memory 256 MB or more
3.1.3 Software interfaces
·
Operating system : Windows XP/Vista or any main stream
OS
4. Functional requirements
4.1 Masters:
·
This module helps the administrator to
enter the designation and the related description. It also helps to add the
department.
4.2
Employee:
·
This module helps to add the details of the employee like
the personal detail and the employee detail.
4.3
Search:
·
This module helps to search the employee
details department wise and designation wise.
·
This module helps to different types of
leave for different year. It also helps the employee to enter their entry and
exit time. Using the attendance module the employee can also check their
remaining leaves and also apply for the leave.
4.4
Salary:
·
This module helps to calculate the
salary by adding the allowances and the basic salary and by deducting the
deductions based on the leaves and also the PF. It also helps to generate the
employee pay slip.
5. Other
Non-functional requirements
5.1 Performance Requirements
1)
The
overall system should be fast and error free.
2)
It
should have built in error checking and correction facilities.
3) The
system should be able to handle large amount of data comfortably.
5.2 Reliability
·
In order to ensure reliability, this
system is being designed using software that is established to be stable and
easy to use.
5.3 Availability
·
This system is designed
to run 24/7 and be readily available to the user.
5.4 Security
·
The access to the software is given only
to valid operators. We need a specific ID and password to get access to the
software.
·
Communication needs to be restricted
when the application is validating the user or licence.
************************************
