"Why is it so hard to write good use cases?"

Use Cases are a wonderfully simple concept; describe a system’s functional requirements by telling stories about how that system delivers value to its users. Yet, for such a simple concept, good Use Cases are really hard to write. Use Case authors frequently must deal with the difficult questions of:

• How many use cases do I need?
• How large should a use case be?
• How should I structure the Use Case description?
• How precise should I be?
• How much detail should I express in the use case?
• When should I create uses and extends relationships between Use Cases?
• Why am I doing this in the first place?

Many use case authors and reviewers have difficulty describing what’s right and wrong about their use cases because there are few objective criteria for judging them. A use case pattern language provides the criteria by capturing and sharing the practical knowledge of experienced use case writers. Patterns are more effective than a simple set of guidelines because patterns capture the essential core of a problem and can be adapted to the nuances of the situation and organization.

Based on the his recent Use Case book, that author will show you how the use case pattern language can be a practical criteria for judging the quality of your use cases.