The completed requirements specification should be a clearly defined statement of the design intent, including

• The business requirements that need to be satisfied
• The user needs that must be addressed

The project team should evaluate the specification to ensure it correctly reflects the current understanding of real needs: this understanding may have improved during the translation process.

Throughout the remainder of the design process, further knowledge gained should be used to update and improve the requirements specification. Any changes made should be clearly identified, dated and traceable.

Using the specification to generate design concepts is one way of testing both its validity and clarity. If such concepts satisfy the requirements, but not the real needs, then some aspect of the specification is flawed.