Have you ever been struck with a question when defining use cases – how can I find useful use cases ?

There are various aspects you can work with, however few I remember from a UML reference book are pretty straight forward. To identify if any application requirement can be identified at a useful level ask your self the following questions.

1. BOSS Test

A necessary task but which may not be valuable just by itself.

Example: “Log in to the system” without doing anything meaningful does not make your boss happy.

2. Elementary Business Process Test

Can you break this requirement down into descent 10/20 pieces individually? not necessarily at the “click on button” level step. If yes, then this cannot be a use case by itself.

Example: “Process returns” would be a valid use case.

3. Size Test

If this requirement is very granular or way too large then it does not deserve a use case of itself.

Example: “Plug in the mouse”, or “click on the high level menu” would fail this test.

Please feel free to let us know if there are other ways you deal with this.

Regards, Sandeep