Guide for Developing the Software Requirements Specification

Below are the steps to complete the Software Requirements Specification (SRS). Use the examples and templates as a starting point.

The goal of the SRS is to define the requirements, from a whole system perspective so that the development team and the client are aligned on the requirements to be developed for the product.

Using the Software Development Plan(SDP) as the starting point, develop each of the sections. Below are some guidelines:

Section 1 Introduction

  1. This section sets the expectations of the reader of the document. > Pull the introduction from the SDP explaining the project.

  2. Add an explanation of the purpose and goal of this document

Section 1.2 Scope

  1. This section comes from the SDP. Bring the Context Diagram, Persona > Descriptions and Use Case Diagram from the SDP

Section 2 Related Documents

  1. This Section has links to other project documents, right now just > the SDP

Section 3 Requirements

Each section 3.x is one Use Case from the SDP. This section only requires the use case name and a short high-level description. The detailed use case information should be in the SDP.

Section 4 Non Functional Requirements (NEW)

For each of these sections, what are the requirements that are measurable, that need to be met. For example: Security, performance, reliability, maintainability, budget

Section 5 Architecture

In the SDP Section 11, you listed the hardware components. Now, in the SRS, draw an architecture diagram. The physical devices that you’ll need for your platform. If its a PC for a game, then its just one box.