This is such a cool concept.

When someone produces some user requirements, the first thing to do is to test to ensure they are fit for purpose.

In essence, this is a quality control review. However, it has a specific purpose. Each requirement must be:

  • uniquely identified
  • clear and unambiguous
  • provable
  • a requirement not a proposed solution

User requirements that meet these criteria form a basis for a successful and timely development. They allow the user to construct acceptance test cases easily (see v model). They allow the developer to evaluate alternatives and prepare a system proposal.

Log in or register to write something here or to contact authors.