In Chapter 4, we discussed the importance of identifying requirements. In particular, we discussed use cases and how they can be used to gather and communicate requirements.
Once you have identified a requirement, you need to validate the requirement with the customer. If you find a problem with a requirement definition before implementation, it will save a lot of time and money over finding it later in the development process.
Customers’ eyes may glaze over if the requirement is not communicated in a way they can understand. Words are great, but sometimes diagrams are a more effective way to communicate requirements. ...