IEEE Std 830-1998 IEEE Recommended Practice for Software Requirements Specifications -Description

Abstract: The content and qualities of a good software requirementsspecification (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. Guidelines for compliance with 12207.1-1997 are also provided.

Keywords: contract, customer, prototyping, software requirements specification, supplier, system requirements specifications

Content

• 1. Overview
• 2. Scope
• 3. References
• 4. Definitions
• 5. Considerations for producing a good SRS
• • 5.1 Nature of the SRS
  • 5.2 Environment of the SRS
  • 5.3 Characteristics of a good SRS
  • • 5.3.1 Correct
    • 5.3.2 Unambiguous
    • 5.3.3 Complete
    • 5.3.4 Consistent
    • 5.3.5 Ranked for importance and/or stability
    • 5.3.6 Verifiable
    • 5.3.7 Modifiable
    • 5.3.8 Traceable
  • 5.4 Joint preparation of the SRS
  • 5.5 SRS evolution
  • 5.6 Prototyping
  • 5.7 Embedding design in the SRS
  • • 5.7.1 Necessary design requirements
  • 5.8 Embedding project requirements in the SRS
• 6. The parts of an SRS
• • 6.1 Introduction (Section 1 of the SRS)
  • • 6.1.1 Purpose (1.1 of the SRS)
    • 6.1.2 Scope (1.2 of the SRS)
    • 6.1.3 Definitions, acronyms, and abbreviations (1.3 of the SRS)
    • 6.1.4 References (1.4 of the SRS)
    • 6.1.5 Overview (1.5 of the SRS)
  • 6.2 Overall description (Section 2 of the SRS)
  • • 6.2.1 Product perspective (2.1 of the SRS)
    • 6.2.2 Product functions (2.2 of the SRS)
    • 6.2.3 User characteristics (2.3 of the SRS)
    • 6.2.4 Constraints (2.4 of the SRS)
    • 6.2.5 Assumptions and dependencies (2.5 of the SRS)
    • 6.2.6 Apportioning of requirements (2.6 of the SRS)
  • 6.3 Specific requirements (Section 3 of the SRS)
  • • 6.3.1 External interfaces
    • 6.3.2 Functions
    • 6.3.3 Performance requirements
    • 6.3.4 Logical database requirements
    • 6.3.5 Design constraints
    • 6.3.6 Software system attributes
    • 6.3.7 Organizing the specific requirements
    • 6.3.8 Additional comments
  • 6.4 Supporting information
  • • 6.4.1 Table of contents and index
    • 6.4.2 Appendixes
• Annex A SRS templates
• Annex B Guidelines for compliance with IEEE/EIA 12207.1-1997
• • B.1 Overview
  • • B.1.1 Scope and purpose
  • B.2 Correlation
  • • B.2.1 Terminology correlation
    • B.2.2 Process correlation
    • B.2.3 Life cycle data correlation
  • B.3 Content mapping
  • • B.3.1 Compliance with information requirements of IEEE/EIA 12207.0-1996
    • B.3.2 Compliance with generic content guidelines of IEEE/EIA 12207.1-1997
    • B.3.3 Compliance with specific content requirements of IEEE/EIA 12207.1-1997
    • B.3.4 Compliance with life cycle data objectives
  • B.4 Conclusion

links: [Standard Status] - [Purchase] - [PDF^*] - [Software Engineering Collection - Description]

available for Standards Online Software Engineering Collection subscribers only