This document is a software requirements specification for a Salary Management System. It includes sections on the introduction and purpose, overall description of the system including features, external interface requirements, and other non-functional requirements. The document specifies requirements for employee, search, attendance, and salary modules. It describes user classes, hardware and software interfaces, operating environment, and design constraints.

1. Software Requirements
Specification
for
<Salary Management System>
Version 1.0 approved
Prepared by <Rana Zohaib Khalid>
<Govt. Municipal Degree College FSD>
29-05-2018

2. Software Requirements Specification for <Salary Management System>
Table of Contents
1. Introduction:.............................................................................................................................. 1
2. Overall Description:...................................................................................................................2
3. External Interface Requirements:............................................................................................4
4. System Features:........................................................................................................................ 5
5. Other Nonfunctional Requirements:........................................................................................5
Revision History
Name Date Reason for Changes Version

3. Software Requirements Specification for <Salary Management System>
Page 1
1. Introduction:
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 and Salaries paid or to be
paid to employees. We are committed to bring the best way of management in the
various forms of EPM. We understand that EPM in not just a product to be sold, it is a
tool to manage the inner operation of Company related to employee leave and Payroll.
1.2 Document Conventions:
Headings Times New Roman/18 font size/Bold/Underlined
Sub Headings Times New Roman/14 font size
1.3 Intended Audience and Reading Suggestions:
The audience and Reading Suggestions like, the different types of reader that the
document is intended for, such as developers, project managers, marketing staff, users,
testers, and documentation writers.
1.4 Product Scope:
This Application works in Multiple PC’s installed on multiple Computers by
sharing same database by which users of different departments can use it sitting at
different locations simultaneously.
We have made an Application where the database will be hosted in order to
manage the all departments which will be located in different places.
1.5 References:
• Wikipedia.org
• Programming Visual Basic .NET, Second Edition by Jesse Liberty
• Jones and Bartlett Publishers - Essential SQL on SQL Server 2008, 2011
• Software Engineering by “Ian Sommerville”.

4. Software Requirements Specification for <Salary Management System>
Page 2
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 Employee module:
• Designation
• Department
• Employee details
2.2.2 Search module:
2.2.3 Attendance module:
• Leave
• Attendance
• Managing Leave
2.2.4 Salary module
• Allowance
• Deduction
• Pay Slip
2.3 User Classes and Characteristics
2.3.1 End user:
• No specific knowledge or skills are required from the end user
• End user should have basic idea about computer operations.

5. Software Requirements Specification for <Salary Management System>
Page 3
2.3.2 Administrator:
• Administrator must be capable 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.
2.4 Operating Environment
• Memory minimum of 512MB RAM (1GB Recommended)
• Hard disk of 40 GB
• Printer
• Operating System Windows XP.
• Front End Microsoft VB.Net 2008
• Backend MS SQL Server 2008
2.5 Design and Implementation Constraints
• The system runs under Windows XP / 7 / 8 / 8.1 or Any version of Linux.
• The application is developed on VB.Net platform and SQL server 2008 as
back end.
2.6 User Documentation
• Wikipedia.org
2.7 Assumptions and Dependencies
• The product must have an interface which is simple enough to understand.
• 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.

6. Software Requirements Specification for <Salary Management System>
Page 4
3. External Interface Requirements:
3.1 User Interfaces:
3.1.1 End user:
• No specific knowledge or skills are required from the end user.
• End user should have basic idea about computer operations.
3.1.2 Administrator
 Administrator must be capable 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.
3.2 Hardware Interfaces
• Memory minimum of 512MB RAM (1GB Recommended)
• Hard disk of 40 GB
• Printer
3.3 Software Interfaces
• Operating System Windows XP.
• Front End Microsoft VB.Net 2008
• Backend MS SQL Server 2008
3.4 Communications Interfaces
Salary slip is transfer by using E-mail OR may be uploaded at browser.

7. Software Requirements Specification for <Salary Management System>
Page 5
4. System Features:
<This template illustrates organizing the functional requirements for the product by system
features, the major services provided by the product. You may prefer to organize this section by
use case, mode of operation, user class, object class, functional hierarchy, or combinations of
these, whatever makes the most logical sense for your product.>
4.1 System Feature 1
<Don’t really say “System Feature 1.” State the feature name in just a few words.>
4.1.1 Description and Priority
<Provide a short description of the feature and indicate whether it is of High,
Medium, or Low priority. You could also include specific priority component ratings,
such as benefit, penalty, cost, and risk (each rated on a relative scale from a low of
1 to a high of 9).>
4.1.2 Stimulus/Response Sequences
<List the sequences of user actions and system responses that stimulate the
behavior defined for this feature. These will correspond to the dialog elements
associated with use cases.>
4.1.3 Functional Requirements
<Itemize the detailed functional requirements associated with this feature. These
are the software capabilities that must be present in order for the user to carry out
the services provided by the feature, or to execute the use case. Include how the
product should respond to anticipated error conditions or invalid inputs.
Requirements should be concise, complete, unambiguous, verifiable, and
necessary. Use “TBD” as a placeholder to indicate when necessary information is
not yet available.>
<Each requirement should be uniquely identified with a sequence number or a
meaningful tag of some kind.>
REQ-1:
REQ-2:
5. Other Nonfunctional Requirements:
5.1 Performance Requirements
• The overall system should be fast and error free.
• It should have built in error checking and correction facilities.
• The system should be able to handle large amount of data comfortably.
5.2 Safety Requirements
<Specify those requirements that are concerned with possible loss, damage, or harm that could
result from the use of the product. Define any safeguards or actions that must be taken, as well
as actions that must be prevented. Refer to any external policies or regulations that state safety

8. Software Requirements Specification for <Salary Management System>
Page 6
issues that affect the product’s design or use. Define any safety certifications that must be
satisfied.>
5.3 Security Requirements
<Specify any requirements regarding security or privacy issues surrounding use of the product or
protection of the data used or created by the product. Define any user identity authentication
requirements. Refer to any external policies or regulations containing security issues that affect
the product. Define any security or privacy certifications that must be satisfied.>
5.4 Software Quality Attributes
<Specify any additional quality characteristics for the product that will be important to either the
customers or the developers. Some to consider are: adaptability, availability, correctness,
flexibility, interoperability, maintainability, portability, reliability, reusability, robustness, testability,
and usability. Write these to be specific, quantitative, and verifiable when possible. At the least,
clarify the relative preferences for various attributes, such as ease of use over ease of learning.>
5.5 Business Rules
<List any operating principles about the product, such as which individuals or roles can perform
which functions under specific circumstances. These are not functional requirements in
themselves, but they may imply certain functional requirements to enforce the rules.>