Requirement Document

Concise (minimal, understandable). The requirement statement includes only one requirement stating what must be done and only what must be done, stated simply and clearly. It is easy to read and understand.
Implementation free. The requirement states what is required, not how the requirement should be met. A requirement statement should not reflect a design or implementation nor should it describe an operation. However, the treatment of interface requirements is generally an exception

  2 Users have rated as useful.

  

Login to rate this answer.

A good requirement document is defined as below:

1. Describes the fucntional specs clearly without any creep
2. Describes additional non functional requirements from the system
3. Describes the user associated with the system
4. Clearly shows the activity flow from one user to the other using use cases, activity diagrams etc.
5. Is signed off the customer