IEEE 830 (Software Requirements Specification standard)

E3022

IEEE 830 (Software Requirements Specification standard) is a widely recognized IEEE guideline that defines the recommended structure and content for documenting software requirements in a clear, complete, and verifiable manner.

All labels observed (5)

How this entity was disambiguated

Statements (48)

Predicate Object
instanceOf IEEE standard
software requirements specification standard
technical guideline
alsoKnownAs IEEE 830 (Software Requirements Specification standard)
surface form: IEEE 830-1998

IEEE 830 (Software Requirements Specification standard)
surface form: IEEE Recommended Practice for Software Requirements Specifications
appliesTo software requirements specification
category software engineering standard
defines recommended sections of a software requirements specification
field software engineering
focusesOn clarity of requirements
completeness of requirements
consistency of requirements
modifiability of requirements
traceability of requirements
verifiability of requirements
fullName IEEE 830 (Software Requirements Specification standard) self-linksurface differs
surface form: IEEE Std 830-1998
governingBody IEEE Software
surface form: IEEE Software and Systems Engineering Standards Committee
hasSuccessor ISO/IEC/IEEE 29148
surface form: ISO/IEC/IEEE 29148:2011

ISO/IEC/IEEE 29148
surface form: ISO/IEC/IEEE 29148:2018
language English
organization Institute of Electrical and Electronics Engineers
surface form: IEEE
publishedBy Institute of Electrical and Electronics Engineers
surface form: IEEE
publisher IEEE Computer Society
Institute of Electrical and Electronics Engineers
purpose to define recommended practices for writing software requirements specifications
to improve clarity, completeness, and verifiability of software requirements
recommends inclusion of assumptions and dependencies in the SRS
inclusion of constraints in the SRS
inclusion of design constraints in the SRS
inclusion of interfaces description in the SRS
inclusion of performance requirements in the SRS
inclusion of software system attributes such as reliability and maintainability
organization of requirements into functional and non-functional categories
standard structure for software requirements specifications
use of clear and unambiguous language in requirements
region international
scope documentation of software requirements
standardNumber 830
status superseded
supersededBy ISO/IEC/IEEE 29148
surface form: IEEE 29148

ISO/IEC/IEEE 29148
usedBy requirements engineers
software engineers
systems analysts
usedFor basis for software design and testing
contractual agreements between customers and suppliers
documenting software requirements
yearOfCurrentEdition 1998

How these facts were elicited

Referenced by (5)

Full triples — surface form annotated when it differs from this entity's canonical label.

IEEE Computer Society developsStandard IEEE 830 (Software Requirements Specification standard)
IEEE 830 (Software Requirements Specification standard) fullName IEEE 830 (Software Requirements Specification standard) self-linksurface differs
subject surface form: IEEE 830
this entity surface form: IEEE Std 830-1998
IEEE 830 (Software Requirements Specification standard) alsoKnownAs IEEE 830 (Software Requirements Specification standard)
subject surface form: IEEE 830
this entity surface form: IEEE 830-1998
IEEE 830 (Software Requirements Specification standard) alsoKnownAs IEEE 830 (Software Requirements Specification standard)
subject surface form: IEEE 830
this entity surface form: IEEE Recommended Practice for Software Requirements Specifications
ISO/IEC/IEEE 29148 replaces IEEE 830 (Software Requirements Specification standard)
this entity surface form: IEEE 830