Find Missing Requirements

The first check in the review determines whether all of the requirements types appropriate to your product are present in the specification. Use the Volere Requirements Specification Template and its requirements types as a guide in determining whether your specification contains the requirements of the types called for by the nature of the product. The goal of the project, together with any strategic plan for the product, usually indicate the appropriate types of requirements. For example, if you are developing a financial product but you have no security requirements, something is definitely missing. Similarly, a Web product that lacks either usability or look and feel requirements is certainly in trouble.

The Volere Requirements Specification Template is found in appendix B.

The functional requirements should be sufficient to complete the work of each use case. To check this, play through each of the product use cases as if you were the product. If you do everything the requirements call for, do you arrive at the outcome for the use case? Are your users (you should have them with you when you perform this role-play) satisfied the product will do what they need for their work?

Look for exceptions to the normal things the product must do. Have you generated enough exception and alternative scenarios to cover these eventualities, and do your functional requirements reflect this? Revisit your scenarios and, for each step, determine whether exceptions can occur there or whether an exception can prevent that step from being reached.

Scenarios are discussed in Chapter 6.

Check each product use case against the nonfunctional requirement types. Does it have the nonfunctional requirements that it needs and that are appropriate for this kind of use case? Use the requirements template as a checklist. Go through the nonfunctional requirements types, read their descriptions, and ensure that the correct nonfunctional requirements have been included.