Talk:Requirement

From Wikipedia, the free encyclopedia

This article is related to Wikipedia:WikiProject Method engineering.
Please note that the use of Wikipedia to host this project has been questioned. Please read this discussion and, if you wish, contribute your thoughts there.


The page originally began with a definition of system requirement that was inappropriately attributed to the label "software requirement. I changed it to generalize the term, but retained the bulk of the article for now. ThreePD 00:25, 23 November 2005 (UTC)


"There are more than 21 more powerful ways to test or evaluate requirements adequacy and more than 15 ways to strengthen testing or evaluation of design adequacy."

The above puzzles me. Suggest deletion or expansion into something useful. Matt Whyndham 16:20, 3 April 2006 (UTC)

[edit] Questions

  1. Certain requirements, by their very structure, are not testable. These include requirements that say the system shall never or always exhibit a particular property. Proper testing of these requirements would require an infinite testing cycle. Such requirements are often rewritten to state a more practical time period.
    So a requirement such as the pacemaker should never fail becomes the pacemaker should fail after a testable time...?
  2. What is the relation between requirements (as in this article) and specifications in (software) engineering?

--Abdull 19:39, 1 June 2007 (UTC)

I removed the phrase "JOEL BURNS MONKEY FISH!" despite being pretty amused by it. -MCF —Preceding unsigned comment added by 12.111.169.2 (talk) 15:55, 26 October 2007 (UTC)

[edit] Derived Requirement

I'd like to know exactly what a "derived requirement" is. I can't seem to get a straight answer that is sufficiently robust. It'd be nice if this article discussed derived requirements a bit. Vincent J Ree Jr (talk) 14:32, 20 December 2007 (UTC)

A "derived requiement" is a more detailed requirement than the original (decomposition in the systems engeering process" or it is a requirement which was created by an associated analysis. Examples would be:

 "An integral fan shall provide cooling air."
 "The device shall include a fuseholder that is externally accessible."

Often derived requirements come from reliability, maintainability, safety, envirdonmental, etc. The basis for the requirement is related to compliance with regulatory (government) or industry recommendations. Bjbuelow (talk) 18:27, 6 February 2008 (UTC)

[edit] Usenet

Are there any usenet groups for software requirements engineering? A link in the article, or at least a bullet item, would be helpful. DRogers (talk) 15:27, 9 April 2008 (UTC)