Software requirements specification

IEEE Software Document Definitions
SQAP – Software Quality Assurance Plan IEEE 730 SCMP – Software Configuration Management Plan IEEE 828 STD – Software Test Documentation IEEE 829 SRS – Software requirements specification IEEE 830 SVVP – Software Validation & Verification Plan IEEE 1012 SDD – Software Design Description IEEE 1016 SPMP – Software Project Management Plan IEEE 1058 SUD – Software User Documentation IEEE 1063

A Software requirements specification (SRS), a requirements specification for a software system, is a complete description of the behavior of a system to be developed and may include a set of use cases that describe interactions the users will have with the software. In addition it also contains non-functional requirements. Non-functional requirements impose constraints on the design or implementation (such as performance engineering requirements, quality standards, or design constraints) .

The software requirements specification document enlists all necessary requirements that are required for the project development. To derive the requirements we need to have clear and thorough understanding of the products to be developed. This is prepared after detailed communications with the project team and customer.

The SRS may be one of a contract deliverable Data Item Descriptions or have other form of organizationally-mandated content. An example organization of an SRS is as follows

• Introduction
  • Purpose
  • Definitions
  • System overview
  • References
• Overall description
  • Product perspective
    • System Interfaces
    • User Interfaces
    • Hardware interfaces
    • Software interfaces
    • Communication Interfaces
    • Memory Constraints
    • Operations
    • Site Adaptation Requirements
  • Product functions
  • User characteristics
  • Constraints, assumptions and dependencies
• Specific requirements
  • External interface requirements
  • Functional requirements
  • Performance requirements
  • Design constraints
    • Standards Compliance
  • Logical database requirement
  • Software System attributes
    • Reliability
    • Availability
    • Security
    • Maintainability
    • Portability
  • Other requirements

External links

• 830-1984 - IEEE Guide to Software Requirements Specifications. 1984. doi:10.1109/IEEESTD.1984.119205. ISBN 0-7381-4418-5. 
• 830-1993 - IEEE Recommended Practice for Software Requirements Specifications. 1994. doi:10.1109/IEEESTD.1994.121431. ISBN 0-7381-4723-0. 
• 830-1998 - IEEE Recommended Practice for Software Requirements Specifications. 1998. doi:10.1109/IEEESTD.1998.88286. ISBN 0-7381-0332-2. 
• doi:10.1109/IEEESTD.2011.6146379
  This citation will be automatically completed in the next few minutes. You can jump the queue or expand by hand("This standard replaces IEEE 830-1998, IEEE 1233-1998, IEEE 1362-1998 - http://standards.ieee.org/findstds/standard/29148-2011.html")
• Leffingwell, Dean; Don Widrig (2003). Managing Software Requirements: A Use Case Approach (2nd ed.). Addison-Wesley. ISBN 032112247X. 
• Gottesdiener, Ellen (2009). The Software Requirements Memory Jogger: A Desktop Guide to Help Business and Technical Teams Develop and Manage Requirements. Addison-Wesley. ISBN 157681114X.