Sebastian Weber's List: Requirements Quality Rules / Checklists

• Each requirement shall appear in a separate statement.
• If a general term is used then the context must be specified.
• • The set of functional requirements must cover all the tasks the users wants the product to perform.
    
  The list of requirements must be complete in the sense that if the product satisfies every requirement, it will be acceptable.
• Requirements must avoid specifying the design.
• Requirements must be specified clearly enough to be turned over to an independent group for implementation and still be understood.

3 more annotations...