|
gptkbp:instanceOf
|
gptkb:standard
|
|
gptkbp:documentType
|
recommended practice
|
|
gptkbp:field
|
software engineering
|
|
gptkbp:focusesOn
|
software requirements specification
|
|
gptkbp:fullName
|
gptkb:IEEE_Recommended_Practice_for_Software_Requirements_Specifications
|
|
https://www.w3.org/2000/01/rdf-schema#label
|
IEEE Std 830-1993
|
|
gptkbp:language
|
English
|
|
gptkbp:partOfSeries
|
IEEE Software Engineering Standards
|
|
gptkbp:provides
|
template for software requirements specification
|
|
gptkbp:publicationYear
|
1993
|
|
gptkbp:publishedBy
|
gptkb:Institute_of_Electrical_and_Electronics_Engineers
|
|
gptkbp:recognizedBy
|
characteristics of good software requirements
|
|
gptkbp:replacedBy
|
gptkb:IEEE_Std_830-1998
IEEE Std 830-1984
|
|
gptkbp:scope
|
guidelines for writing software requirements specifications
|
|
gptkbp:standardNumber
|
830-1993
|
|
gptkbp:status
|
superseded
|
|
gptkbp:targetAudience
|
software engineers
project managers
system analysts
|
|
gptkbp:usedFor
|
defining requirements for software systems
|
|
gptkbp:bfsParent
|
gptkb:IEEE_Std_830-1998
|
|
gptkbp:bfsLayer
|
6
|