Summaries and Customer Reviews are supplied by Amazon.com
Summary:
Text describes how to gether and define software requirements using a process based on use cases. Show systems analysts and designers how use cases can provide solutions to the most challenging requirements issues; resulting in effective, quality systems that meet the needs of users. Previous ed: c2000. Softcover. DLC: System design.
Customer Reviews:
Average Customer Rating:
Excellent high level & indepth details in developing Use Cases
Customer Rating:
Too often you find books on these subjects that tend to talk theory, leaving it to you to determine how you'll apply that theory. This book in excellent, not only in presenting the theory, but even more so when it deals with interviewing, testing and taking a Use Case artifact through the various iterations to the Finished (polished) state.
If you've never done Use Cases, start with this book. If you've used Use Cases, but not studied the theory, continue with this book. If you want to teach others, apply this book.
It is great all around.
Excellent Book
Customer Rating:
Very interesting stuff and fluid understanding..Could have more topics though
A great path to follow
Customer Rating:
Being in the middle of a messy project this book came to me a little late. I consider is one of the best introductions to the understanding of what a use case is and WHAT things you should put in it. Everbody has suffered for long endless meetings discussing which is the scope of the use cases and how it should be used, I strongly recomend to read this book before start arguing. I give it four starts because it lacks in some way of paths that can work as guidelines trough the process, although is not the focus of this book, it would very useful to include a couple of pages reviewing this subject.
A Great Book for Use Case driven Requirements Modeling
Customer Rating:
I saw this book in a stall, while searching for some other book. I had a glance at it and really liked the simplicity and practical approach. Once I bought it and read it completely, I felt happy to find such a great book on Requirements Study. To read and understand this book you need not have a lot of experience or a Requirements Specialist. I feel anyone from Programmer to Project Manager will find this book very useful. The authors teach you in a very practical manner, how to come out with good Use Cases. I enjoyed reading this book, applied the concept in my projects while doing Requirements Study and now can happily recommend this book to others.
Three cheers to the authors for a great work.
Note: I found Craig Larmen, while talking about Use Cases in his best selling book on UML and Patterns talks highly about this book.
The Best Use Case Book I've Read So Far
Customer Rating:
Programmers naturally hate use cases. They seem boring, and having seen hundreds of them (written by others and handed to me) over the years, I had lost hope that this practice would ever be of any benefit. I had grown tired of constantly reading varying levels of abstraction and `use-case-itis'. All this, despite the fact that Jacobson's original work and the UDP incorporation of use cases as central to that process was clearly a better way to go than wading through hundreds, sometimes thousands of pages of `shall' statements that accompany most projects (and too often, lead to their failure).
Then I read this book. I now use it regularly in every requirements-related class I teach, and I tell every programmer I meet to buy this book. Imagine a use case book that programmers can actually get excited about! This book blazes new territory and its practical insights and humor make it a fun read, as well.
Here are the great highlights: 1. Properly scoping and relating use cases 2. Introducing Business Rules as 'first-class citizens" 3. Applying UDP iterations to the use case development process.
These last two items make the book stand out. Understanding the importance of business rules as enterprise-wide invariants that span use cases is ground-breaking. The four UDP iterations are ingenious because they can help to enforce the proper level of abstraction, which is a big problem area for use cases. Try it, you'll like it!
In addition, the book is loaded with great practical advice and examples of good (and bad!) use case text. And finally, the authors present the most compelling arguments I've ever heard for ditching traditional requirements-gathering methods (which have clearly FAILED), because use cases are, after all, requirements IN CONTEXT (like the title says). If every use case writer read this book and followed it's advice, the software crisis would be dealt a serious blow.
Bottom line : If you write use cases (or worse, are forced to implement bad use cases at gunpoint), get this book!
Select button not working? 
