This document completely describes the system in terms of functional and nonfunctional requirements and serves as a contractual basis between the customer and the developer. The final Non-Functional Requirement Document must be signed-off from all the project stakeholders. In order to identify the items being tested, features to be tested, testing tasks to be performed, personnel responsible for each task, the risks associated with this plan, etc. The client agrees to find a product satisfactory if it provides the capabilities specified in the functional requirements document. We use an example template for a RAD introduced in the book. or whether every requirement statement is to have its own priority.>