Scribd
Upload
814 views3 pages

Srs

Section 1 of the SRS document introduces the software product by outlining its purpose, scope, definitions, references, and overall organization. Section 2 provides a general description, including the product perspective within the overall system, key functions, intended users, general constraints, and assumptions. Section 3 specifies the requirements in detail, with subsections defining functional requirements, external interfaces, performance standards, design constraints, security and other attributes. Functional requirements specify inputs, processing, and expected outputs, while external interfaces address user experience, hardware and software integration, and communication protocols.

Uploaded by

Amanda Owen
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
814 views3 pages

Srs

Section 1 of the SRS document introduces the software product by outlining its purpose, scope, definitions, references, and overall organization. Section 2 provides a general description, including the product perspective within the overall system, key functions, intended users, general constraints, and assumptions. Section 3 specifies the requirements in detail, with subsections defining functional requirements, external interfaces, performance standards, design constraints, security and other attributes. Functional requirements specify inputs, processing, and expected outputs, while external interfaces address user experience, hardware and software integration, and communication protocols.

Uploaded by

Amanda Owen
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 3

SRS DOCUMENT FORMAT

Table of Contents
1. Introduction
1.1 Purpose
1.2 Scope
1.3 Definition, Acronyms, or Abbreviations
1.4 References
1.5 Overview
2. General Description
2.1 Product Perspective
2.2 Product Functions
2.3 User Characteristics
2.4 General Constraints
2.5 Assumptions
3. Specific Requirements
3.1 Functional Requirements
3.1.1 Functional Requirement 1
Introduction
Inputs
Processing
Outputs
3.1.2 Functional Requirement 2
.
.
.
3.1.n
Functional Requirement n
3.2 External Interface Requirements
3.2.1 User Interfaces
3.2.2 Hardware Interfaces
3.2.3 Software Interfaces
3.2.4 Communications Interfaces
3.3 Performance Requirements
3.4 Design Constraints
3.4.1 Standards Compliance
3.4.2 Hardware Limitations
3.5 Attributes
3.5.1 Security
3.5.2 Maintainability
3.6 Other Requirements
3.6.1 Database
3.6.2 Operations
3.6.3 Site Adaptation

Section 1 of SRS Document includes general information about the software


product ,its objectives and its scope.It also includes definitions ,acronyms
,abbreviations used in the SRS ,References to different books or resources and
overview of how rest of the SRS is organized
General Description Section of SRS (Section 2) should include general
information regarding the factors that affect the final product and its requirements.
The information to be included in section 2 of the SRS document includes the
following:
a) Product Perspective Product to be developed in proper perspective within the
overall system. a detailed description of use of any existing or new harware,
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. The specific requirements specifications are left for a
later point in the SRS document
c) User Characteristics- Description of any user characteristics that may be
required in the use of the software
d) General Constraints -Factors other than user and operator needs that may
impose constraints on a software product. For eg.harware limitations,
government polices,networks,interfaces to other applications etc..
e) Asumptions any assumptions made in the SRS documents or implicit
dependencies must be clearly stated.
Specific Requirements Section of SRS(section 3) must contain all of the technical
information and data needed to design the software
a) Functional requirements Describe the purpose of each functional
requirement.Special algorithms,formulas used
for each functional
requirement.Descripe 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.
b) External interface requirements This section should specify all the external
interface requirements needed to make the software product, a successfully
operational product such as user interface characteristics from the human
factors point of view, hardware interface to describe all the characteristics
required to interface the software product with each of the hardware product,
interfaces with other software components, communication interfaces
specifying interfaces between product and networks.
c) 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.
d) Design constraints Any form of design constraints caused by environmental
limitations, hardware limitations and compliance with standards would be
specified here.
e) 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.
f) Other 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.

You might also like