Software requirements specification

For broader coverage of this topic, see Software requirements.

A software requirements specification (SRS) is a description of a software system to be developed. It is modeled after the business requirements specification (CONOPS). The software requirements specification lays out functional and non-functional requirements, and it may include a set of use cases that describe user interactions that the software must provide to the user for perfect interaction.

Software requirements specifications establish the basis for an agreement between customers and contractors or suppliers on how the software product should function (in a market-driven project, these roles may be played by the marketing and development divisions). Software requirements specification is a rigorous assessment of requirements before the more specific system design stages, and its goal is to reduce later redesign. It should also provide a realistic basis for estimating product costs, risks, and schedules.^[1] Used appropriately, software requirements specifications can help prevent software project failure.^[2]

The software requirements specification document lists sufficient and necessary requirements for the project development.^[3] To derive the requirements, the developer needs to have a clear and thorough understanding of the products under development. This is achieved through detailed and continuous communications with the project team and customer throughout the software development process.

The SRS may be one of a contract's deliverable data item descriptions^[4] or have other forms of organizationally-mandated content.

Typically a SRS is written by a technical writer, a systems architect, or a software programmer.^[5]

Structure

An example organization of an SRS is as follows:^[6]

1. Purpose
   1. Definitions
   2. Background
   3. System overview
   4. References
2. Overall description
   1. Product perspective
      1. System Interfaces
      2. User interfaces
      3. Hardware interfaces
      4. Software interfaces
      5. Communication Interfaces
      6. Memory constraints
   2. Design constraints
      1. Operations
      2. Site adaptation requirements
   3. Product functions
   4. User characteristics
   5. Constraints, assumptions and dependencies
3. Specific requirements
   1. External interface requirements
   2. Performance requirements
   3. Logical database requirement
   4. Software system attributes
      1. Reliability
      2. Availability
      3. Security
      4. Maintainability
      5. Portability
   5. Functional requirements
      1. Functional partitioning
      2. Functional description
      3. Control description
   6. Environment characteristics
      1. Hardware
      2. Peripherals
      3. Users
   7. Other

Requirements smell

Following the idea of code smells, the notion of requirements smell has been proposed to describe issues in requirements specification where the requirement is not necessarily wrong but could be problematic.^[7]

Examples of requirements smells are subjective language, ambiguous adverbs and adjectives, superlatives and negative statements.^[7]

See also

• System requirements specification
• Concept of operations
• Requirements engineering
• Software Engineering Body of Knowledge (SWEBOK)
• Design specification
• Specification (technical standard)
• Formal specification
• Abstract type

References

1. Bourque, P.; Fairley, R.E. (2014). "Guide to the Software Engineering Body of Knowledge (SWEBOK)". IEEE Computer Society. Archived from the original on 28 December 2014. Retrieved 17 July 2014.
2. "Software requirements specification helps to protect IT projects from failure". Retrieved 19 December 2016.
3. Pressman, Roger (2010). Software Engineering: A Practitioner's Approach. Boston: McGraw Hill. p. 123. ISBN 9780073375977.
4. "DI-IPSC-81433A, DATA ITEM DESCRIPTION SOFTWARE REQUIREMENTS SPECIFICATION (SRS)". everyspec.com. 1999-12-15. Retrieved 2013-04-04.
5. Donn Le Vie, Jr. "Writing Software Requirements Specifications (SRS)". 2010.
6. Stellman, Andrew & Greene, Jennifer (2005). Applied software project management. O'Reilly Media, Inc. p. 308. ISBN 978-0596009489.
7. Femmer, Henning; Méndez Fernández, Daniel; Wagner, Stefan; Eder, Sebastian (2017). "Rapid quality assurance with Requirements Smells". Journal of Systems and Software. 123: 190–213. arXiv:1611.08847. doi:10.1016/j.jss.2016.02.047. S2CID 9602750.

External links

• IEEE Guide for Software Requirements Specifications. 1984. doi:10.1109/IEEESTD.1984.119205. ISBN 978-0-7381-4418-4.
• IEEE Recommended Practice for Software Requirements Specifications. 1994. doi:10.1109/IEEESTD.1994.121431. ISBN 978-0-7381-4723-9.
• IEEE Recommended Practice for Software Requirements Specifications. 1998. doi:10.1109/IEEESTD.1998.88286. ISBN 978-0-7381-0332-7. S2CID 8674647.
• Systems and software engineering -- Life cycle processes --Requirements engineering. Iso/Iec/IEEE 29148:2018(E). 2018. 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 - ")
• Leffingwell, Dean; Widrig, Don (2003). Managing Software Requirements: A Use Case Approach (2nd ed.). Addison-Wesley. ISBN 978-0321122476.
• Gottesdiener, Ellen (2009). The Software Requirements Memory Jogger: A Desktop Guide to Help Business and Technical Teams Develop and Manage Requirements. Addison-Wesley. ISBN 978-1576811146.
• Wiegers, Karl; Beatty, Joy (2013). Software Requirements, Third Edition. Microsoft Press. ISBN 9780735679665.
• "IEEE SRS Template - rick4470/IEEE-SRS-Tempate". GitHub. Retrieved 27 Dec 2017.
• How to Write a Software Requirement Specification to Save Costs?

^[1]

1. Taaffe, Ed. "Mr". thebridger. Retrieved 2019-02-02.