|
|
Requirements review involves trying to ensure that the use cases and the domain model work together to address the customers' functional requirements. It also involves making sure that the customers have enough of an idea of what they want that our development team is able to base a design on those requirements. Some schools of thought hold that "customers never know what they want. the requirements change weekly, sometimes daily, even hourly," and use this to justify skipping analysis and design. This is an enormous cop-out. It's the analyst's job to help the customers focus their understanding of their requirements. Use cases, prototypes, and domain models are among the tools we can use to make this process work.
Figure 4-1 shows where we are.
|
|