Talk:Software requirements specification

From Wikipedia, the free encyclopedia
Jump to: navigation, search
          This article is of interest to the following WikiProjects:
WikiProject Software / Computing   
WikiProject icon This article is within the scope of WikiProject Software, a collaborative effort to improve the coverage of software on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.
 ???  This article has not yet received a rating on the project's quality scale.
 ???  This article has not yet received a rating on the project's importance scale.
Taskforce icon
This article is supported by WikiProject Computing.
 
WikiProject Computer science  
WikiProject icon This article is within the scope of WikiProject Computer science, a collaborative effort to improve the coverage of Computer science related articles on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.
 ???  This article has not yet received a rating on the project's quality scale.
 ???  This article has not yet received a rating on the project's importance scale.
 
WikiProject Engineering  
WikiProject icon This article is within the scope of WikiProject Engineering, a collaborative effort to improve the coverage of engineering on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.
 ???  This article has not yet received a rating on the project's quality scale.
 ???  This article has not yet received a rating on the project's importance scale.
 

IEEE defines a requirement as[edit]

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 possessed by a system... to satisfy a    
      contract ,standard ,specification , or other formal imposed document."


i would like to ask what is the difference between requirement in general and requirement specification? —Preceding unsigned comment added by 188.48.114.196 (talk) 17:02, 15 January 2010 (UTC)


"A Requirement is a statement of one thing a product must do or a quality it must have. A Requirement Specification is a collection of the set of all requirements that are to be imposed on the design and verification of the product. The specification also contains other related information necessary for the design, verification, and maintenance of the product."

From an article, "What is the difference between a Requirement and a Specification?" by Ivy Hooks

JerryBowman (talk) 15:05, 21 January 2010 (UTC)

((edited)) 66.97.213.52 (talk) 00:42, 16 August 2010 (UTC)

SRS = IEEE 830?[edit]

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)dsfsdf

→ It does not always refer to the IEEE 830. However, in the context of this article I believe that it should be changed to conform to the IEEE 830 or otherwise noted that this article does not explicitly conform to the IEEE 830. This is because this article is linked by the following article: http://en.wikipedia.org/wiki/Template:IEEE_software_documents 71.244.159.177 (talk) 15:34, 9 September 2008 (UTC)

Relevance of linked article[edit]

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)

This article is misleading[edit]

1. An SRS is not a "complete" description of a system. An SRS is one of a number of different specifications required to provide a complete description.

2. Use cases are not a mandatory part of an SRS. Use cases should employed when system USE needs to be defined. If there is no user-system interaction, use cases should be avoided. I see far too much ABuse of use cases attempting to document what a state machine diagram, or simply a section of a document containing paragraphs would better represent.

... I could probably continue the list but I've only started my first cup of coffee this morning. ;) —Preceding unsigned comment added by Leeconte (talkcontribs) 14:42, 23 March 2009 (UTC)

PROD Contested[edit]

I removed the PROD on this page. As noted in my summary, the SRS is an extremely important concept in software engineering to-date and deserves its own page. This page needs a LOT of work, but it should not be deleted. --Mpdelbuono (talk) 23:08, 9 October 2009 (UTC)

Wikipedia style?[edit]

Does this page conform to relevant Wikipedia styles? It doesn't feel to me like it is part of Wikipedia, but more like it was copied from somewhere (the IEEE standard?) and simply edited to a "walkthrough" style. There needs to be more discussion on the SRS itself, and I really think that the whole style of the document, aside from the opening paragraph reads too much like a page designed to tell you how to write an SRS, not an encyclopedia article on the SRS document, and the IEEE standard that is most commonly associated with it. Also, is there a particular reason that we have the IEEE definition for a requirement at the top of this page? Bobbias (talk) 05:09, 24 December 2009 (UTC)


Requested move[edit]

The following discussion is an archived discussion of a requested move. Please do not modify it. Subsequent comments should be made in a new section on the talk page. No further edits should be made to this section.

The result of the move request was: moved to Software requirements specification. Favonian (talk) 13:24, 13 March 2012 (UTC)


Software Requirements SpecificationSoftware requirements specification — This is a common noun phrase. It may be a proper name when the term refers to a IEEE document but here we are just referring to a generic requirements spec document. Jojalozzo 14:08, 6 March 2012 (UTC)

Survey[edit]

Feel free to state your position on the renaming proposal by beginning a new line in this section with *'''Support''' or *'''Oppose''', then sign your comment with ~~~~. Since polling is not a substitute for discussion, please explain your reasons, taking into account Wikipedia's policy on article titles.
  • Support, I think this is standard Wikipedia style unless it is a trademark or proper name. Cross porpoises (talk) 18:38, 8 March 2012 (UTC)

Discussion[edit]

Any additional comments:
The above discussion is preserved as an archive of a requested move. Please do not modify it. Subsequent comments should be made in a new section on this talk page. No further edits should be made to this section.

This article is NOT about IEEE 830[edit]

I think there should be a separate IEEE 830 article if one is needed. SRS has been around a long time and IEEE 830 is only one version. This article does not reference IEEE 830 (except in external links) nor does it comply with it. I think this article should be about the general concept of SRS and a future IEEE 830 article could be created for that specific implementation. As I see it, this would simply require removing both the IEEE SW standards template and the external links to the standards and editing the template to reference a redlinked IEEE 830 article. Jojalozzo 16:14, 17 December 2012 (UTC)

IEEE 830 superseded[edit]

IEEE 830 has been superseded by ISO/IEC/IEEE 29148. This should be mentioned in the article. Information about SRS in the new document should be incorporated in the article. --217.243.209.74 (talk) 16:21, 24 April 2013 (UTC)