Software requirements specification

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.^[1] 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^[2] or have other forms of organizationally-mandated content. An example organization of an SRS is as follows: ^[3][4]

• 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

References

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. 
• 29148-2011 - Systems and software engineering -- Life cycle processes --Requirements engineering. 2011. pp. 1 – 94. doi:10.1109/IEEESTD.2011.6146379. ISBN 978-0-7381-6591-2. ("This standard replaces IEEE 830-1998, IEEE 1233-1998, IEEE 1362-1998 - http://standards.ieee.org/findstds/standard/29148-2011.html")
• Leffingwell, Dean; Widrig, Don (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. 
• Wiegers, Karl; Beatty, Joy (2013). Software Requirements, Third Edition. Microsoft Press. ISBN 9780735679665.