Instant UML

I was quite surprised after reading this book to read some of the negative reviews on it. I find the book to be excellent, to the point, very clear, and very concise. However, I already know this field rather well (UML, OO modeling, etc.) so it is hard for me to imagine what it would be like for a beginner trying to use this book to learn UML. Beginners seem to be giving it the worst reviews.I would strongly recommend this book as a reference book for those engaged in OO modeling, for those learning OO modeling under the guidance of an instructor, and for seasoned modelers who can pick up new ideas and interesting angles on the whole modeling process from the book. There are so many horrible technical books out there in the computer world -- this is not one of them.

After reading the fisrt 2 chapters and deeming this book garbage, I later decided to read the case study in chapter 5. This really should have been the 2nd chapter in the book. If you read this chapter 1st everything becomes clear. You can use the other chapters as reference as needed. This really should have been called UML Reference.

A fairly experienced software developer with no previous knowledge of UML may find it the best introduction to the subject. Just as WROX promise, there is no trivial introduction, no attempts at teaching the reader what he/she already knows, and then repeating it four times. It's concise and to the point, unlike practically all other books on the subject of systems analysis and design, that I had in my hands. At the same time, it manages to give the reader a very clear idea of the concepts behind the pictures. I find the quality of presentation on par with Stroustup's ARM and a few other classics.This book assumes the reader already knows a lot about systems analysis, but nothing about UML. If this description fits you, it's for you. If you look for an introductory text about systems analysis or OOP, you might need another resource.

This book is an excellent reference/introduction for the experienced OO engineer with little knowledge of UML. THIS BOOK WILL NOT TEACH YOU OO THEORY OR CONCEPTS! You must have a working knowledge of OO analysis, design, and implementation in order to derive any value from this text. The experienced engineer with little or no knowledge of UML, but a knowledge of some kind of OO documentation methodology, will find that this book teaches UML in a direct concise way.I recommend this book to all "hard core" architects and engineers who need to gain a working knowledge of UML and how it applies to software systems.In short, I think this book is excellent.

Instant UML is concise and to the point. I'm sick of texts which blather about simplistic issues for the developer-wanna-be$ and never get to the good stuff. (Especially when this injustice is in the supposed name of "pragmatism," but it's really just dumbed-down for the masses.)The book is very practical and helpful for solving the real-world problem of formalizing OO design for your clients. If you're working on OO projects, like me you have trouble collecting requirements and commuicating iterative design to your client and among your team members (especially if you're attempting RAD ;-Instant UML's straightforward recommendations for UML and iterative design are what you're looking for. This book not only documents the syntax of UML but discusses the practical application of UML to your OO design methodology. I strongly recommend it to project leaders and project architects.If you feel this book is too "academic" or complex, you need to stay away from real-world application development larger than a weekend project with one developer. Find another career.If you want to test-run this book, there's at least a full chapter avaiable at the MSDN library in the partial books section.