01 August 2008

Book Notes: Writing Effective Use Cases

As I read books, I note the contents that I think are most important - for me. You might find it useful, but consider reading the book for yourself: Alistair Cockburn: Writing Effective Use Cases.

This books describes, quite formally, how use cases should be written. Personally, I did not like the book because of that formalism. Most of it deals with highly detailed fields you should have in your use cases, which might be required in some large scale enterprise systems where there are many QA-infected people around who actually believe that such details really help anyone. I don't, but your mileage may vary.

Nonetheless, I found some valuable information in the book.
  • Stories (scrum) are de-facto use cases, but very informal ones.
  • Each story should have 2 ends: the success scenario, and failure scenario. Describe both.
  • Never write stories in passive form, always include WHO does WHAT. Example: "Error is being displayed" is bad, better is "Error view displays a list of all errors".
Use cases should always be easy to read, in simple grammar. They should cover and describe scope, actor and goal-level.

Pass/Fail test for use cases:
  1. Ask your user if he understands what is going on in the use case.
  2. Ask developers if they are able to implement a feature based on the use case.
Formally, the book mentions these parts of a use case:
  • Actor
  • Stakeholder
  • Scope
  • Preconditions and Guarantees (=Postconditions)
  • Main Success Scenario
  • Extensions (like failure scenarios, what can happen differently)
Final advice: Always control your scope. Make a in/out list of items that are in your scope and those that are not. This applies to everything, not only stories but also meetings, papers, documents etc.

No comments: