Chapter 1. What Is a Quality Use Case?
The hardest single part of building a software system is deciding precisely what to build. | ||
| --Frederick Brooks, “No Silver Bullet: Essence and Accidents of Software Engineering” | ||
Why Use Cases at All?
“I understand the requirements, but what does it actually do?” is a question often asked by systems analysts, business analysts, product managers, and programmers when confronted by two hundred pages of traditional IEEE-standard-style “The system shall . . .” functional requirements. After reading these convoluted documents, many of us have often gone back to the customers and pleaded, “What do you want this system to do? Tell me a story about how you are going to use this system.”
People like stories, and from ...
Get Patterns for Effective Use Cases 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.
