Sign in with Facebook
Loading...
Writing Effective Use Cases
-- A practical methodology that makes use cases more accessible than ever before.
-- Project standards, formats, style, and detailed "do's and don'ts" for creating use cases that work.
-- Based on Cockburn's acclaimed tutorials at OOPSLA and Software Development Conferences!Use cases have never been this easy to understand -- or this easy to create! In Writing Effective Use...more
-- Project standards, formats, style, and detailed "do's and don'ts" for creating use cases that work.
-- Based on Cockburn's acclaimed tutorials at OOPSLA and Software Development Conferences!Use cases have never been this easy to understand -- or this easy to create! In Writing Effective Use...more
Paperback, 304 pages
Published
October 5th 2000
by Addison-Wesley Professional
Friend Reviews
To see what your friends thought of this book,
please sign up.
This book is not yet featured on Listopia.
Add this book to your favorite list »
Community Reviews
(showing
1-30
of
333)
Alistair is _the_ master of use cases, with many years of consulting, teaching, and careful thought. I suspect no one knows more about what use cases are, or should be, than the author. The advice in this book shows the polish of much practice and feedback, with insights and tips from the small-scale notational to large-scale process context. I recommend buying this book and making it the cornerstone bible of our use case practice. His emphasis that use case work is about writing text and storie...more
It's unfortunate that the authors became too enamored with their own cleverness that they forgot to actually involve with consumers of their book. For example, they offer a section on “graphical icons to highlight goal levels.” To quote from the book:
and:
”Very summary (very white) use cases get a cloud, [cloud icon:]. Use this on that rarest of occasions when you see that the steps in the use case are themselves white goals.”
and:
”Some subfunctions (black) should never be written. Use a clam, [clam i...more
The book describes the methodology of putting the software requirements in written through the use cases. Very systematic and logical approach, clear and easy to understand guidelines for writing, quite good examples.
Sometimes, the methodology as a whole feels too dogmatic and sets quite strict limits. I did not find suggestions for schematic icons too useful either. Besides, the methodology feels a little bit outdated in 2012 (the book was written in 2001).
Overall, recommended to software anal...more
Sometimes, the methodology as a whole feels too dogmatic and sets quite strict limits. I did not find suggestions for schematic icons too useful either. Besides, the methodology feels a little bit outdated in 2012 (the book was written in 2001).
Overall, recommended to software anal...more
I've adapted Cockburn's principles and actual templates effectively to every form of agile or waterfall estimation & planning process I've worked with. I'll always believe success of such things is 70% how you apply them to team & org context, but Cockburn is usually my starting point for documenting human-centric requirements, with little competition. These templates can work so well and robustly with test-driven development, a variety of flow-based planning methods, and classic BMP and...more
This is one of the most useful technical books that i ever read. Cockburn presents a pragmatic, hands-on method for writing use cases. There's lots of useful advice, including a number of templates that can be adapted to any real project. When I'm writing use cases, this is the book I always return to.
Excellent book for information on preparing effective use cases. Recommended highly for business analysts and software testers as an approach to preparing requirements for software development.
Excellent book I was referred to during a job interview. They requested I submit a use case to them as a followup to my interview and as a demonstration of my skill level.
This is probably the 'bible' for anything use case related. It shows how we can be flexible in the requirements space and still achieve project success
Not as good as it is been reviewed. But a good reading. More about methodology than about philosophy.
This book is ancient in Software Development terms, but I guess it's still one of the very few good reference books on use cases. It clearly describes how use cases can and should be used, and what the possibilities and limitations are. It would be interesting to have an updated version, especially regarding the tools that can be used to create and manage use case sets.
Part of my on-going Business Analysis education...
One of the best books I've read on Use Cases.
This book should be "in the canon" for anyone who designs software. The only thing that keeps me from five stars is that there is probably more detail and variation than most folks need in the latter half of the book.
Object oriented, functional, procedural, process, business analysis or just about whatever in the IT/corporate sector - you can't go wrong reading this.
This is probably the best book on writing use cases for systems engineering requirements.
Let me read and put some comments here
May 20, 2013
Md. Abul
marked it as to-read
May 18, 2013
Olumuyiwa
marked it as to-read
May 16, 2013
Wayne
marked it as to-read
May 16, 2013
Devon
is currently reading it
May 15, 2013
Abu
marked it as to-read
May 03, 2013
Brian Breidenbach
added it
May 03, 2013
Javas Nzima
added it
There are no discussion topics on this book yet.
Be the first to start one »
