Rating: 
Summary: Your first read for learning UML
Review: While the authors provide excellent detail on most subjects, it is structured well enough not to overwhelm the beginner. UML Distilled is not necessarily the best place to start reading about UML unless you like the "...For Dummies" approach.
Rating: 
Summary: Object Oriented Hype...
Review: 90% hype + 9% empty space + 1% some ok idea
Rating: 
Summary: Good UML User's Guide
Review: Unfortunately, for this book, there is another book in the same series called "UML Distilled" that I find to be a better user's guide than the book at hand. However, UML Distilled does not go into much detail. You will find much more detail here in this book. One problem with the book is that since Booch, Jacobson, and Rumbaugh invited UML, they overhype it. For example, "If you can think it, the UML can model it." I regularly encounter situations where you have to force certain types of problems into UML and are better off not using it. On the other hand, in the same page, it says "You can model 80% of most problems by using about 20% of the UML." Here they are dead on target. You just have to evaluate what to listen to in this book because it is good ideas and hype mixed together. On the whole, it is a pretty good book. "UML Distilled" is even better though and the book I recommend for UML beginner. Also, one tactic is to read "UML Distilled" first, do some modeling, and graduate to the User Guide. This User Guide has a lot of depth to it.
Rating:
Summary: Great book; but get Fowler's "UML Distilled" as well!
Review: Yes, as others already have written, this is a "must-have" book. However, for a different point of view, I would suggest buying Martin Fowler's "UML Distilled" as well, and maybe even reading the two books in parallel. For me, the sum of the two books was greater than the parts (but YMMV).
Rating:
Summary: Small technical lapses mar otherwise definitive work
Review: This is a more than worthy successor to the two best OO design books of the early 90s(Booch's "Object-Oriented Analysis & Design with Applications" and Rumbaugh et al.'s "Object-Oriented Modeling and Design"). It is not as much, however, a follow-on to Jacobson's classic analysis and methodology book "Object-Oriented Software Engineering," so do not expect to walk away from this book with everything you need to implement a formal development process. This book is destined to become a core text for software developers wishing to master object-oriented design, which makes the occasional lapses in technical editing all the more regrettable. The introductory chapters, which I suspect weren't given the same scrutiny from authors and editors as the "meat" of the book, have just enough minor mistakes to introduce a vague feeling of mistrust. Small things like using the "simple notation" for realization in a diagram without having yet introduced it in the text and referring to a code file as Hello.java rather than HelloWorld.java may trip up newcomers and may make more advanced readers doubt the precision of the more advanced chapters. This is doubly a pity because chapters 1-3 contain some of the best advice in the book regarding the pragmatics of modeling. The core of the book, which presents a modeling notation and syntax designed to scale across the entire universe of software development, is far more formal. Each chapter ends with a discussion of how the particular diagram or relationship is commonly modeled, a nice device but one that falls short of presenting a unified methodology. Rather, the success of the book is the presentation of a modeling framework which can support many different methodologies. --Larry O'Brien founding editor, "Software Development" magazine
Rating:
Summary: What you need to know on UML notation is in this book
Review: I was looking forward to this books for a lot of months. I wasn't deceived. The book covers in-depth every UML concepts and techniques( structural, behavioral and architectural modelings ). Each chapter are well-written and clear. Each concept is applied with a lot of good examples from real life. Moreover, it is easy to read. Novices will be able to learn smoothly and clearly UML notation. Experts will find a complete reference and plenty of good tips and tricks. Unfortunately, I was expected more details on mapping between UML and programming languages ( Java and C++ ). Apart from that, it's an outstanding book. Buy it now !!!!
Rating:
Summary: A must have for UML
Review: The book explains UML in plain english. Great for the beginner
Rating:
Summary: Excellent Book
Review: It's an excellent book, every Software Engineer should have one, it teaches you not only how to use properly UML, but it also help you understand and improve your OO concepts. Lots of good examples from real life.
Rating:
Summary: An excellent tutorial on how to use the UML
Review: What I really like about this book is its orientation around how people can use the UML. Section headers like "Modeling the Seams in a System" and "Modeling a Flow of Control" get you right into how to use the notation effectively. The organization allows you to use the elements you need without having to know all the gory details. All in all it's an excellent book that gently gets you into the useful depths of the UML. (Ideal for those who found my book rather too thin!)
Rating:
Summary: Well worth the wait
Review: This book is well-written, consise and suprisingly easy to read. As somebody familar with OMT, I can't imagine it taking long at all to understand UML using this work.
| 
