We are convinced that the mother of success of a project are its requirements. That implies to live the following advices:

• keep them non-ambiguous, consistent, testable, complete and understandable to make the work of the programmers and testers more effective (see IEEE, 1998)
• granulate them into CRQs, PRQs, UCQ/SRQ/TRQs and USPs to achieve a higher test coverage over the different abstraction levels
• allocate them to the criticality high, medium or low to enable risk-based testing and to handle the fact that time and budget are limited