Talk:Software Requirements Specification

From Wikipedia, the free encyclopedia

IEEE defines a requirement as

  "1. A condition of capability needed by the a user to solve a problem or achieve  an objective.
   2. A condition or a capability that must be met or possesed by a system... to satisfy a    contract ,standard ,specification , or other formalimposed document."

[edit] SRS = IEEE 830?

Does SRS always mean IEEE 830? If yes, then this article should be upgraded based on information from IEEE reference document.

→ I'd say not. You can use the general waterfall phases (requirements->design->implementation->test), and have an SRS be the interface between reqs and design phases, w/o necessarily complying with or even using IEEE 830. 199.171.110.112 21:45, 24 June 2007 (UTC)

[edit] Relevance of linked article

The linked article, <A HREF="http://cswww.essex.ac.uk/staff/turnr/publications/foundations-specification.pdf">"The Foundations of Specification"</A> is not about building an SRS, but rather a description of formal specification, reducing requirements to predicate logic statements. I will remove it to see if anyone protests. -Fuzzy (talk) 19:04, 5 February 2008 (UTC)