Rating: 
Summary: There's a good, more practical alternative
Review: " Applying Use Cases : A Practical Guide" is not bad, but when I browsed through several Use Case books at a local book store, I decided to buy "Use Cases: Requirements in Context", which - to me - seems to be a far more practical book than this one.Check out "Use Cases: Requirements in Context" before you buy any book on this topic.
Rating: 
Summary: Meu Consultor Pessoal sobre Uses Cases
Review: A aplicação de use cases em projeto OO é talvez onde se tenha maior a maior quantidade de dúvidas. Isso é natural pois o objetivo é mapear as necesidades do usuário para uma arquitetura de software. Li este livro em um fim-de-semana e já pude obter os benefícios dessa leitura na confecção de meus projetos. Um livro que precisa ser lido por todos aqueles que trabalham com use cases. Nota 10.
Rating:
Summary: Useful introduction to Use case concepts
Review: A useful introduction to use case concepts in an easy to read style, although the case study dialog that other reviwers have mentioned does rather spoil the book - does it really matter that Tara can cook? (p12). However, overall a useful addition to your OO library - particularly as there are so few good books on the subject.
Rating:
Summary: Puts the Unified Process and UML into perspective
Review: After reading through the sixth chapter of this book the light bulb goes on and suddenly you start to understand how everything fits together using the UML and Unified Process (UP). This book is the how-to of applying UML and UP where as the Unified Modeling Language Users Guide and the Unified Software Development Process are the foundation on which to build this understanding. If you read the two previous mentioned books first and then read Applying Use Cases then the overall brilliance of using a modern use case driven, architecture-centric, iterative/incremental software development process will fall into place. This book is the missing link for UP and UML.
Rating:
Summary: Use Case Points
Review: An excellent book. Gustav Karner did a really good job, finding the solution of estimating resources for object oriented projects.
Rating: 
Summary: Great place to start with Use Cases, but you'll want more
Review: As another reviewer pointed out, the campy dialog that this book relies on to help guide you through the process of developing use cases sometimes hinders the cause more than it helps. Luckily, you can either skim or ignore it altogether and still garner valuable insight into the process of using use cases. This book has served as my read-along guide for a current project and I have found the chapter outlining the final use case documentation for the books' fictional project to be a great aid. I wish there were more books on this topic, especially some with 'real-life' use cases that led to successful projects, but this book is a very good place to start.
Rating:
Summary: Useful as a refresher
Review: As someone who has followed the development of UML and Use Cases for the past several years and who is now confronted with a project needing definition, I find the Scheider-Winters book very helpful -- not only in applying Use Cases, but also in defining the project itself. I chose this book because I know Geri Schneider-Winters as a professional (we worked together at UCSC Extension.) I was not disappointed.
Rating:
Summary: Was OK in its time
Review: Back when, this was probably an OK book for the real novice - easy reading. Nowadays there are better ones, the Cockburn and Kulak ones contain real information. Get this one as an adjunct to the others and for the real basic intro.
Rating:
Summary: Even shorter than it looks
Review: Be warned that this already-thin book contains wide swaths of "sample" documentation describing the project referred to throughout. Probably about forty or fifty pages of such. The rest of the content is good, however.
Rating:
Summary: Recommended for introducing the concept of use cases
Review: Excellent short book with examples following the text. I would recommend the book for anyone needing an introduction to the usage of use case in software development. The only complaint is that the book is too short. With its small size, the areas that the authors declared as outside the scope of the book, could have been at least been discussed briefly. Also, there are several modeling tools now available that allow developers to create use cases and business rules and automatically generate object models. These also are not mentioned.
| 
