Chapter 11. Reviewing Use Cases

Reviews are often neglected. In the course of the project, effort is typically focused on producing artifacts—requirements, use cases, test cases, code itself—but often little time is given to reviewing these artifacts. This is a grave error; reviews are an excellent and inexpensive way of spotting errors early enough to do something about them.

The typical error with use cases is that they tend to be written and more or less forgotten; they are often never really reviewed with the stakeholders to ensure that the team has the right understanding of the required behavior. This is not entirely the fault of the development team; it is often difficult to get stakeholders to take an active interest in reviewing use cases. ...

Get Use Case Modeling now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.