Software Requirement Specification Format

1. Introduction
1.1 Purpose
1.2 Scope of the Project
1.3 Definitions, Acronyms, and Abbreviations
1.4 References
1.5 Overview of Document
( This section should include general information about the software product, its objectives and
its scope.
It should also specify definitions, acronyms & abbreviations, if any, used in the SRS.
List out the referenced books or websites or resources.
Give an overview of how rest of the SRS is organized )
2. Overall Description
2.1 Product Perspective
2.2 Product Functions
2.3 User Classes and Characteristics
2.4 Operating Environment
2.5 Design and Implementation Constraints
2.6 General Constraints, Assumptions and Guidelines
( This section should include general information regarding the factors that affect the final
product and its requirements.
a) Product Perspective Product to be developed in proper perspective within the overall
system. A detailed description of use of any existing or new hardware, evaluation of
any extra loads caused by the introduction of this product should be specified here
b) Product Functions- Short description of the functions performed by the software.
Functional specifications must be in a form understandable to users, operators and
client.

c) User Classes and Characteristics- Identify the various user classes who will use this
product. Description of any user characteristics that may be required in the use of the
software
d) Operating Environment - Describe the environment in which the software will
operate, including the hardware platform, operating system and versions, and any
other software components or applications that is compatible.
e) Design and Implementation Constraints - Describe any items or issues that will limit
the options available to the developers. It includes: corporate or regulatory policies,
hardware limitations, interfaces to other applications, specific technologies, tools, and
databases to be used, language requirements, communications protocols,
programming standards etc.
f) General Constraints - This section describes non-functional requirements or
constraints like hardware limitations or requirements, the amount of memory
available, policies, interfaces to other application software, networks, environmental
limitations, compliance with relevant standards. It should also include any
assumptions made in the SRS documents)
3. External Interface Requirements
`3.1 User Interfaces
3.2 Hardware Interfaces
3.3 Software Interfaces
3.4 Communications Interfaces
(This section should specify
1. logical characteristics of each interface between the software product and the users -sample
screen images, screen layout constraints, standard buttons and functions that will appear on
every screen, keyboard shortcuts, error message display standards, and so on
2. hardware interface to describe all the characteristics required to interface the software
product with each of the hardware product
3. Interfaces with other software components.
4. Communication interfaces specifying interfaces between product and networks.)
.
4. Functional Requirements
4.1 Functional Requirements
Functional Requirement 1
Introduction
Inputs
Processing

Outputs
Functional Requirement 2
.
.
.
Functional Requirement n

Functional requirements Describe the purpose of each functional requirement. Special

algorithms, formulas used for each functional requirement. Describe the input to the function like
what inputs must be accepted, in what form, from what sources inputs are derived
Describe in unambiguous and precise language the process that the function must perform on the
input data it receives. This process must be described from the outcome point of view, not from
the implementation point of view.
Describe the output desired from the function. This description should include the following - the
form and the shape of the output, the destination for the output, volume of output, output timing,
and the range of parameters in the output.
5. Other Requirements
5.1 Performance Requirements
5.2 Design Constraints and Attributes
5.3 Security Requirements
5.3 Special User Requirements
5.3.1 Database
5.3.2 Backup and Recovery
5.3.3 Installation
( This section should include,
a) Performance requirements This section should include any form of static or
dynamic requirements specified by exact measurements. Such requirements may
include the number of connections to the system, number of simultaneous users,
response time, number of files, number of open files, and amount of data to be
processed within a time unit.
b) Design constraints Any form of design constraints caused by environmental
limitations, hardware limitations and compliance with standards would be specified
here.
c) Attributes Most of the attributes required for the software product would be
specified here, such as detailed security requirements, software product availability

requirement, product maintainability requirement, mobility requirement and

reliability requirement.
d) 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.
e) Special user requirements It includes database requirements specifying any
database to be used by the software and its specifications, operational modes
specifying modes of operation including back-up and disaster recovery plans, site
adaptation requirements specifying data, initialization and other features that are
specific to the operational site. )