Logo

IEEE 830-1993

Historical Revision

IEEE Recommended Practice for Software Requirements Specifications

$119.00


Sub Total (1 Item(s))

$ 0.00

Estimated Shipping

$ 0.00

Total (Pre-Tax)

$ 0.00


Stay effortlessly up-to-date with the latest standard revisions. When new versions are released, they're automatically charged and delivered to you, ensuring seamless compliance.

Document Preview Not Available...

Revision Standard - Superseded. 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.
This is a recommended practice for writing software requirements specifications. It describes the content and qualities of a good software requirements specification (SRS) and presents several sample SRS outlines. 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. However, application to already-developed software could be counterproductive. When software is embedded in some larger system, such as medical equipment, then issues beyond those identified in this standard may have to be addressed. This recommended practice describes the process of creating a product and the content of the product. The product is a software requirements specification. This recommended practice can be used to create such software requirements specification directly or can be used as a model for a more specific standard. This recommended practice does not identify any specific method, nomenclature, or tool for preparing an SRS.
This recommended practice describes recommended approaches for the specification of software requirements. It is divided into five clauses. Clause 1 explains the scope of this recommended practice. Clause 2 lists the references made to other standards. Clause 3 provides definitions of specific terms used. Clause 4 provides background information for writing a good SRS. Clause 5 discusses each of the essential parts of an SRS. This recommended practice also has an annex, which provides alternate format templates.

SDO IEEE: Institute of Electrical and Electronics Engineers
Document Number 830
Publication Date April 8, 1994
Language en - English
Page Count 32
Revision Level
Supercedes
Committee Software & Systems Engineering Standards Committee
Publish Date Document Id Type View
Oct. 20, 1998 830-1998 Revision
April 8, 1994 830-1993 Revision
Feb. 10, 1984 830-1984 Revision