Disambiguation evidence for IEEE 830 (Software Requirements Specification standard) via surface form

"IEEE 830"


As subject (48)

Triples where this entity appears as subject under the label "IEEE 830".

Predicate Object
alsoKnownAs IEEE 830 (Software Requirements Specification standard)
surface form: IEEE 830-1998
alsoKnownAs 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
focusesOn completeness of requirements
focusesOn consistency of requirements
focusesOn modifiability of requirements
focusesOn traceability of requirements
focusesOn 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
hasSuccessor ISO/IEC/IEEE 29148
surface form: ISO/IEC/IEEE 29148:2018
instanceOf IEEE standard
instanceOf software requirements specification standard
instanceOf technical guideline
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
publisher Institute of Electrical and Electronics Engineers
purpose to define recommended practices for writing software requirements specifications
purpose to improve clarity, completeness, and verifiability of software requirements
recommends inclusion of assumptions and dependencies in the SRS
recommends inclusion of constraints in the SRS
recommends inclusion of design constraints in the SRS
recommends inclusion of interfaces description in the SRS
recommends inclusion of performance requirements in the SRS
recommends inclusion of software system attributes such as reliability and maintainability
recommends organization of requirements into functional and non-functional categories
recommends standard structure for software requirements specifications
recommends 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
supersededBy ISO/IEC/IEEE 29148
usedBy requirements engineers
usedBy software engineers
usedBy systems analysts
usedFor basis for software design and testing
usedFor contractual agreements between customers and suppliers
usedFor documenting software requirements
yearOfCurrentEdition 1998

As object (1)

Triples where some other subject referred to this entity as "IEEE 830".