Writing Effective Use Cases Alistair Cockburn
Publisher: Addison-Wesley Professional

Retrieved from http://extremeprogramming.org/rules/userstories.html 5. €�Writing Effective Use Cases”, by Alistair Cockburn, is an excellent reading for those who want to learn the art of writing good behavioral specifications in the form of use cases. In order to write good use cases you must have a very clear idea about functionality you need. Write Effective Use Case[stage note]. That's why some 5 years ago I started reading books, followed lots of courses, like the one you wrote on UML , some stuff from A. Primary and Secondary Actors; Business Rules and Supplemental Specifications. Read the chapter on Parameterized Use Cases in “Writing Effective Use Cases”. An excellent and practical reference on writing use cases is "Writing Effective Use Cases," by Alistair Cockburn, part of the Agile Software Development Series, ISBN 0-201-70225-8. The most succinct definition I have found is Alistair Cockburn's (in Writing Effective Use Cases), in the reminders section rather than the main part of the book. To write effective use cases, be productive without perfection. Alistair Cockburn, an expert on use cases describes in “Writing Effective Use Cases” (2001) that a “fully dressed” use case is not always appropriate. Writing effective Use Case and User Story Examples: Tip 1. Use Cases – Best Practices, Examples and Applications; How to identify Actors? A common liability of use case diagrams is that the diagram diverts our attention from the real goal, which is to describe the use cases. This is why use cases are best written by business experts. The best help systems and user manuals are written with a goal-oriented organization; that is, 'to accomplish this, do that'—the short definition of a use case. As I am new to this, I'd like some recommendations on good BA, UML, use case, etc. A good use case is a unit of help. Below is a use case based on his “Casual Use Case” structure. I divide the energy of writing use cases into four stages of precision, according to the amount of energy required and the value of pausing after each stage: Actors & Goals. That will take care of most of the problem, because the differences between the companies will be on the data sheets not the use cases.