TOPIC NAME, E.G. DOCUMENTATION AND WEB SUPPORT

Title, e.g. Documentation Authors’ Guide

Author(s)

Date

Revision History

Date	Revision	Description	Author
03/02/00	1.0	Initial Version	Author Name
mm/dd/yy

Table of Contents

1. Purpose

1.1. Scope

1.2. Definitions, Acronyms, Abbreviations

1.2.1. Definitions

1.2.2. Acronyms

1.3. References

1.4. Overview

2. Overall Description

2.1. Product Perspective

2.2. Product Architecture

2.3. Product Functionality/Features

2.4. User Characteristics

2.5. Constraints

2.6. Assumptions and Dependencies

3. Specific Requirements

3.1. Functional Requirements

3.2. External Interface Requirements

3.3. Internal Interface Requirements

3.4. Internal Data Requirements

3.5. Design and Implementation Constraints

3.6. Other Requirements

4. Non-Functional Requirements

4.1. Safety Requirements

4.2. Security and Privacy Requirements

4.3. Environmental Requirements

4.4. Computer Resource Requirements

4.4.1. Computer Hardware Requirements

4.4.2. Computer Hardware Resource Utilization Requirements

4.4.3. Computer Software Requirements

4.4.4. Computer Communication Requirements

4.5. Software Quality Factors

4.6. Packaging Requirements

4.7. Precedence and Criticality of Requirements

5. Qualification Provisions

6. Requirements Traceability

6.1. Upward Traceability

6.2. Downward Traceability

Purpose

This document provides a template for Software Requirements Specifications and for User Guides. For Software Requirements Specifications, both the formatting can be used, and the headings can be used as a template. For User Guides only the formatting should be used.

Scope

State the scope extent of this document.

Definitions, Acronyms, Abbreviations

The following is a list of commonly used definitions used throughout this document:

Definitions

Provide a list of items and definitions that may be required, or be helpful to the intended audience.

Acronyms

Provide a list of used acronyms and their associated definitions.

References

Give a list of documents are referenced within the text of this document:

Overview

This paragraph shall briefly state the purpose of the system and the software to which this document applies. It can describe the general nature of the system and software and summarize the history of the system development.

Overall Description

Product Perspective

Provide a description of this product, where it fits into the Company’s overall structure, and what functionality is provided by this product. An existing Product Requirements Specification (PRD) would cover these items in much more detail and with far greater depth.

Product Architecture

Overview the products architecture, covering the essential components of the system.

Product Functionality/Features

Overview the essential functionality, features that are important to this product.

User Characteristics

State any User characteristics that may be influential or significant in the structure of the product.

Constraints

State any known constraints.

Assumptions and Dependencies

State any known assumptions and dependencies.

Specific Requirements

Functional Requirements

Specify required behavior and include parameters such as response times, throughput times, other timing constraints, sequencing, accuracy, capacities, priorities, etc.

External Interface Requirements

State any External interface requirements. These requirements may exist in greater detail in an Interface description document, or other requirements document. Reference these documents if they exist.

Internal Interface Requirements

Internal Data Requirements

Design and Implementation Constraints

Other Requirements

Non-Functional Requirements

Safety Requirements

Security and Privacy Requirements

Environmental Requirements

Computer Resource Requirements

Computer Hardware Requirements

Computer Hardware Resource Utilization Requirements

Computer Software Requirements

Computer Communication Requirements

Software Quality Factors

Packaging Requirements

Precedence and Criticality of Requirements

Qualification Provisions

This section defines a set of qualification methods. For each requirement in Section 3, specify the methods to be used to ensure that the requirement has been met. A table may be used to present this information, or each requirement may be annotated with the method(s) to be used. Qualification methods may include: Demonstration, Test, Analysis, Inspection, Special.

Requirements Traceability

Upward Traceability

Traceability from each requirement in this specification to the system or subsystem requirements it addresses.

Downward Traceability

Traceability from each system or subsystem requirement to the requirements contained in this specification

Product Requirements Document	Project Name

Page ii

i

ii

iii

Software Requirements Specification

Software Requirement Specification

Date

3/2/00 12:59 PM	Rev

1	Page

1

Software Requirements Specification

1.0

cfagan

2003-06-02

Greg White

Rational Software Corporation