The review compares the author's approach to Cockburn's "Writing Effective Use Cases", a book which has helped me understand Use Cases and their application a little bit more.

"Kulak and Guiney focus quite strongly on software and on the Unified Modeling Language (UML), but at the same time propose their own definition of a use case and what it should contain, supported by clearly documented templates and examples. They explain in a fresh way the difference between the user’s and the developer’s points of view, and use this to critique traditional and older approaches to requirements -- would you really want users to look through DFDs, ERDs, and long lists of shalls, or try to define requirements by embodying them in prototypes? All those techniques have a place but they do not substitute for presenting things in a shared language."

Cockburn focuses on Use Case in their textual form.
12:48:24 PM    comment []  Google It!