I am still working my way through the book but so far I am impressed by the authors direct no nonsense views on design and test. I am a software tester and my new project uses UML which I have not worked with before. This book has given me a good overview and explains the terms and diagrams used in UML design very clearly.
Keep up the good work guys.

The Rosenbert & Stephens's Book is a great example of doing by practice, but highly supported by foundations about what is important in UML.
The book offers a great discussion not only how use UML effectively, but how can you go through practice and coding. That's essencial if you want coding in a right way, but explore the UML notation.
The approach with ICONIX was fantastic. You develop a e-Commerce system completely using UML, Iconix process and coding with JAVA. I coudn't found books that offer this path.
Fantastic. Excelent aquisition.

Since 2001 I had a lot of courses on UML modelling at the university and in inhouse company workshops. But none of them gave me the real power to write use cases so that I can easilly extract an object model from it. I always had problems to bridge the use cases to sequence diagrams and class models.

This book gave me the clues (with red and bold highlighted) such
"You can't drive object-oriented designs from use-cases unless you tie your use cases to objects."

Now I have to say, I write use cases more confidetially, knowing that they build a real basis for futher object modelling. 5 stars!!

This book was extremely helpful because it takes the reader from Use Cases to code development using a real-life "sample" system (an internet book store) to describe the steps. The ICONIX Process is used in this book and the goal of the book is to get from Analysis to Code using a minimal, yet sufficient core subset of UML. Each step is broken down into detail and examples of how to do each step are provided and explained. Built into the "sample" project are mistakes (ones that are commonly made in real life) and the book shows those mistakes as well as the corrected versions. In addition, the book discusses the Enterprise Architect (EA) tool, which our company is evaluating, making the examples provided even more pertinent. The only thing that would have made this book more useful would have been appendices or detailed examples of using the EA tool with the "sample" project. It would be great if one could obtain the sample project in a *.EAP file where folks that have the EA tool could load the sample project to understand how the project was actually laid out in the EA tool. This book is very well-written and, as a bonus, has some decent humor throughout keeping the reader's interest. If you are using EA and Use Case Driven development, this is an excellent book for you.

This book does everything it promises and more. While reading this book you will learn a design methodology that will help you in every project you work on. What you won't learn is a framework that does all the work for you. You also won't learn to rely on someone else's code. Instead you will learn how to really think about your project from the initial design to the final solution. You will learn how to properly document the requirements and the user interaction with the system. You will learn how to be a Software "Developer" not just a Software "Programmer". Some will say there is no difference, but others that have read this book will understand the work and thought process that goes into real development of a software solution.