By Topic

830-1984  -  IEEE Guide for Software Requirements Specifications

Sign In

Cookies must be enabled to login.After enabling cookies , please use refresh or reload or ctrl+f5 on the browser for the login options.

The purchase and pricing options are temporarily unavailable. Please try again later.

The content and qualities of a good software requirements specification (SRS) are described and several sample SRS outlines are presented. This recommended practice is aimed at specifying requirements of software to be developed but also can be applied to assist in the selection of in-house and commercial software products.

Scope
This is a guide for writing software requirements specifications. It describer' || ';' || ' the necessary content and qualities of a good Software Requirements Specification (SRS) and presents a prototype SRS outline.This guide does not specify industry-wide SRS standards nor state mandatory SRS requirements.This guide is written under the premise that the current state of the art does not warrant or support such a formal standards document.This guide is applicable to in-house and commercial software products. Special care, however,should be used in its application because: (1) This guide is aimed at specifying requirements of software to be developed. Application of this material to already developed software is counter-productive.(2) This guide does not cover the specification of requirements for software being developedusing the techniques of rapid prototyping.