Customer Review: I purchased this book after getting a consultant job in which I had to develop use-cases for the project I was involved in. Having never worked with them before, I found this book to be very helpful and by reading through it, I was able to create use-cases that were relevant and user-friendly.
more info
Customer Review: The "Agile" umbrella includes multiple approaches/lenses from which to view, practice and evolve software and teams. Alistair's material offers an additional lens. So when reading this material, I don't believe it was ever his intent for people to pick up Crystal and say "This is it". Rather, this... more info
Customer Review: I picked this book up because of the Jolt Award. I was amazed as what I read. I give kudos to anyone who tries to apply game theory to their decision making process. This has grown to be the accepted way economists discuss decisions between agents, so why shouldn't we apply that to architecture or... more info
Customer Review: This book attempts to take use cases to a higher level of science and in part succeed. Its plus points are discussions on management of use cases and the processes a team goes through in completing the creation / validation cycle. There's a lot of good sense here. Some of the patterns are useful.... more info
Customer Review: This book is simply great, and one of the few pieces or literature in a field that deserve to be considered as a 'must' for that field. I use this opportunity to thank Mr. Cockburn for writing this book and to congratulate him for his top-of-class thinking and writing. I am really enjoying this... more info
Customer Review: Even though it was written in 1998, the advice in this book has not diminished with age. There are many claims made about the advantages of moving to object-oriented technologies (OOTs), and while most are true, the difficulties are almost always understated. Not in this book. Cockburn is very... more info
Customer Review: L'approche des cas d'utilisations de cet auteur est très structurée. Il a comprit que c'est le texte des cas d'utilisation qui constitue le coeur des cas d'utilisations plutôt que le graphique UML. Il présente en fait une approche itérative des projets, avec une... more info
