Unread use-cases

Now a days (almost) everybody is convinced about the advantages of use-cases. They provide a formal specification of some piece of functionality in an natural language, so don’t require extensive training to read them. But why is it then that users don’t seem to read them.

Recently is was in a project where we wrote use-cases which where reviewed by non-technical users. An no feedback came back.. that felt great (but you can see it more like a silent alarm is discovered). And after the first iteration which produced functionality a pile of feedback came back.

I questioned my self how can this be, are the use-cases too technical, high- level,…


Now a while later i read the use-cases again and afterwards it is was like a big boring book. Everybody seems (including me) is thinking that use-cases due to the natural language are easily read. But the opposite is true, the give to much detail for the business person and to few detail for the developer..

This is yet an other example why use-cases do not work always..

Categories: Requirements Tags: ,
  1. No comments yet.
  1. No trackbacks yet.