Misuse of Use Cases

[dbJav]

Hi there,

I found this interesting (though not recent) article on how to avoid the misuse of Use Cases:

http://www.korson-mcgregor.com/publications/korson/Korson9803om.htm

I'd love to get your thoughts about the ideas expressed in this paper, and particularly on the 1st part of the article where the author proposes to create "use cases" at different levels of abstraction.  At the lowest levels of abstractions, detailed use cases would be written to provide the complete detailed spec (see fig.1).  And... the idea of keeping requirements separate from interface specifications ("accept payment from customer" vs. "insert coin into slot") is only valid for the 1st level of use cases (the Business requirements).  

But first of all I wonder if use cases should not just be limited to the 1st level of abstraction (as described by the author).  :-/   Aren't the other levels of abstractions just represented by the other UML models that will be produced during the project (Analysis and Design models).

Denis

[thomaskilian]

Denis,
that seems to be really outdated. More than 12.000 Use Cases   Funny also that the development teams wrote the Use Cases. They should come from the people using the system (supported by Use Case Modelers). Maybe you could read here http://www.sparxsystems.com.au/cgi-bin/yabb/YaBB.cgi?board=UMLPRO;action=display;num=1078736293