Difference between revisions of "Secrets of defining requirements"

From DarkWiki
Jump to: navigation, search
(Three magic words)
Line 1: Line 1:
 
===Three magic words===
 
===Three magic words===
  
1. MUST  This word, or the terms "REQUIRED" or "SHALL", mean that the
+
1. MUST  This word, or the terms "REQUIRED" or "SHALL", mean that the definition is an absolute requirement of the specification.
  definition is an absolute requirement of the specification.
 
  
2. MUST NOT  This phrase, or the phrase "SHALL NOT", mean that the
+
2. MUST NOT  This phrase, or the phrase "SHALL NOT", mean that the definition is an absolute prohibition of the specification.
  definition is an absolute prohibition of the specification.
 
  
3. SHOULD  This word, or the adjective "RECOMMENDED", mean that there
+
3. SHOULD  This word, or the adjective "RECOMMENDED", mean that there may exist valid reasons in particular circumstances to ignore a particular item, but the full implications must be understood and carefully weighed before choosing a different course.
  may exist valid reasons in particular circumstances to ignore a
 
  particular item, but the full implications must be understood and
 
  carefully weighed before choosing a different course.
 
  
4. SHOULD NOT  This phrase, or the phrase "NOT RECOMMENDED" mean that
+
4. SHOULD NOT  This phrase, or the phrase "NOT RECOMMENDED" mean that there may exist valid reasons in particular circumstances when the particular behaviour is acceptable or even useful, but the full implications should be understood and the case carefully weighed before implementing any behaviour described with this label.
  there may exist valid reasons in particular circumstances when the
 
  particular behavior is acceptable or even useful, but the full
 
  implications should be understood and the case carefully weighed
 
  before implementing any behavior described with this label.
 
  
5. MAY  This word, or the adjective "OPTIONAL", mean that an item is
+
5. MAY  This word, or the adjective "OPTIONAL", mean that an item is truly optional.  One vendor may choose to include the item because a
  truly optional.  One vendor may choose to include the item because a
+
particular marketplace requires it or because the vendor feels that
  particular marketplace requires it or because the vendor feels that
+
it enhances the product while another vendor may omit the same item.
  it enhances the product while another vendor may omit the same item.
+
An implementation which does not include a particular option MUST be
  An implementation which does not include a particular option MUST be
+
prepared to interoperate with another implementation which does
  prepared to interoperate with another implementation which does
+
include the option, though perhaps with reduced functionality. In the same vein an implementation which does include a particular option MUST be prepared to interoperate with another implementation which does not include the option (except, of course, for the feature the option provides.)
  include the option, though perhaps with reduced functionality. In the
 
  same vein an implementation which does include a particular option
 
  MUST be prepared to interoperate with another implementation which
 
  does not include the option (except, of course, for the feature the
 
  option provides.)
 
  
 
===Never say never===
 
===Never say never===

Revision as of 08:05, 25 June 2019

Three magic words

1. MUST This word, or the terms "REQUIRED" or "SHALL", mean that the definition is an absolute requirement of the specification.

2. MUST NOT This phrase, or the phrase "SHALL NOT", mean that the definition is an absolute prohibition of the specification.

3. SHOULD This word, or the adjective "RECOMMENDED", mean that there may exist valid reasons in particular circumstances to ignore a particular item, but the full implications must be understood and carefully weighed before choosing a different course.

4. SHOULD NOT This phrase, or the phrase "NOT RECOMMENDED" mean that there may exist valid reasons in particular circumstances when the particular behaviour is acceptable or even useful, but the full implications should be understood and the case carefully weighed before implementing any behaviour described with this label.

5. MAY This word, or the adjective "OPTIONAL", mean that an item is truly optional. One vendor may choose to include the item because a particular marketplace requires it or because the vendor feels that it enhances the product while another vendor may omit the same item. An implementation which does not include a particular option MUST be prepared to interoperate with another implementation which does include the option, though perhaps with reduced functionality. In the same vein an implementation which does include a particular option MUST be prepared to interoperate with another implementation which does not include the option (except, of course, for the feature the option provides.)

Never say never

The words never and always should not be used in requirements definitions. This is because it would take forever to prove the statement true or false, and is therefore impossible to be used as an axiom.

Incorrect Correct
Users never want to see their email on the screen Users do not want to see their email on the screen