Mon premier blog

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

They are especially useful when the system of interest is in turn composed of other subsystems. 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. Write good use cases to design and develop a stable system. 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. It is very educative and probably highly applicable in certain teams and projects but it's far from universal. This tutorial has used Alistair Cockburn's template from Writing Effective Use Cases (**PRE-PUB. In order to write good use cases you must have a very clear idea about functionality you need. Introduction This article is inspired by two more of Alistair Cockburn's “gold nuggets” found in his book Writing Effective Use Cases . Alistair Cockburn's in his pivotal book “Writing Effective Use Cases” describes five levels of use cases (a use case isn't exactly a user story, but this concept is a great parallel for writing user stories at an appropriate level). I just read a recent blog (wiki) entry by Alistair Cockburn (of "writing effective use cases" fame) called "why I still use use cases". Writing Effective Use Cases This was boring for me. Retrieved from http://extremeprogramming.org/rules/userstories.html 5. Use case structure varies from organization to organization which can seriously impact the Estimation.