Rating: 
Summary: Start with this one
Review: Many others have reviewed this book and rated it 5 stars so I will not waste time saying how good it is (see my rating).I teach Software Engineering at the University of Malaga in Spain and I reccomend this book for my students in the first Software Engineering course. Just try to use the books from Rumbaugh, Jacobson and Booch for this students and you'll see. While there are other books that cover UML in depth, this is the only one to guide the reader through the basic concepts and artifacts of UML keeping a coherent view. So, to summarize any newcomer to UML SHOULD start with this book and then proceed to get the in-depth knowledge using books like UML distilled or the three books from the "three amigos". Otherwise you will probably get lost in a sea of concepts, definitions ,notations and artifacts before you even realize what is UML about.
Rating: 
Summary: ok but the software is a 7 day trial
Review: The book claims you get a 30 day license for GDpro but you have to jump through hoops to get it. They first give out a 7 day and then you have to call...email..a couple of times to get the license extended. So you better teach yourself UML in 24 hours or at least a week.
Rating:
Summary: Excellent introduction to UML
Review: I was looking for an excellent book that would introduce me to UML and help me to start with object oriented design of a corporate system. With this book I got familiar with UML methodology and created a new corporate system design using this book as a guideline. It is simply perfect!
Rating:
Summary: You need a Book to start from..
Review: I was asked to start studying UML in order to begin applying it in our next project, it wasn't my responsibility to draw and create the diagrams from scratch, but at least i should understand them. I wanted a book that is written for a beginner,a book that will help me through my first step, i looked around on the other books,they were so huge and so detailed oriented, and most of them were for a higher level than a beginner. Whats so good about this book? - Style of writing,its so good, you can notice this right from the introduction. - The way he took the reader to the new world of diagramming through UML, he first explains what is UML..then why do we need it, and starts to give a brief about its component so you can imagine the big picture, in addition to the Object Oriented Design concepts. - The examples are very well chosen, simple yet so powerful to illustrate and understand. - The way he guides you through his explanation by starting with a simple model in each chapter that eventually ends as a different model by adding every thing you read to it. -The case study is very helpful to implement and make sure that you understand what you read. I recommend this book for every one who starts reading UML, its not the reference but its definitely the book you want to start with, after that you can move to another advanced book, and ofcourse i would recomend the modified modeling language refrence manual for the three amigos, although thier are many good and not detailied books such those books that deals with Java and UML or C and UML if you are to be specialaized oin one prgramming language.
Rating:
Summary: Perfect for the less technical
Review: I'm a tech writer who used to be a software engineer (10 years ago, before OO programming became popular and long before UML even existed). I just started a job where I'll be using UML content as source material, so I was looking for introductory information (I'm not going to be programming) that was very basic and easy for a less-tech (though not completely un-tech) person to understand. I started with the Three Amigos' "The UML User Guide" and Alhir's "UML in a Nutshell," and got nowhere (I mean *nowhere*) with them. Lacking much of the needed background, I needed lots of understandable examples of even the most basic concepts, and neither had many in their early chapters. (Also, like others who have posted comments on the "Nutshell" book, I found Alhir's writing horrible and very distracting, especially with the ultra-frequent bulleted lists and parenthetical remarks. I became so aware of the bad writing that I often forgot what he was talking about and had to re-read.) Both books assumed that the reader had a substantial background in OO programming and software project management, which I don't have (though admittedly the programmers who would read these books would have this background). Following recommendations I found here, I checked out this Schmuller book, and it gave me exactly what I needed: simple, basic introductory stuff very fitting for a non-expert who wanted to read, but not write, UML. I'm sure I'm not in the main audience this book was meant for, but in case there are a few others out there who need to just dip their toes in the water of UML and OO programming, this is the book to get.
Rating:
Summary: Author's Response to Larry4882
Review: Thanks for taking the time to review my book. I've been working with UML professionally for more than 3 years, and my goal was to help beginners learn UML as quickly and painlessly as possible. I spent more than 3 months writing it and made every effort to make it accessible for beginners. Given the almost universally positive responses I've gotten from readers, I'm a little surprised you found so many problems with the book. That said, if I can improve the book, I'd very much like to do so. If you'd like to email your specific feedback to me at jschmuller@yahoo.com I'll be sure to address any errors as quickly as possible. Also, if you could let me know who you may have spoken to at my publisher, I'd appreciate that as well. No one there has contacted either me or my agent about any problems with the book, so I'm not sure why anyone there would characterize me as being unhelpful. I truly care about what readers get out of my books and worked very hard to produce the absolute best book I could. Of course, I expect it to get even better in future editions and will look forward to receiving your feedback.
Rating: 
Summary: Great intro to UML diagrams, needs better RL examples
Review: As a software engineer, diagramming software is a large part of what I do. This book gave a great introduction to the process of doing UML. It goes through the basics of object modeling and then into process and use case methodologies. After this book though, you may want further information to see how this all works in a real life situation. That was the one thing lacking from this book. If you are a VB programmer, a good book is WROX VB6 UML. This book server as an axcellent jumping off point into that book.
Rating:
Summary: Great start
Review: This book has a nice level of depth to get you started with UML. I especially enjoyed the second section of the book, where a business application is designed from the ground up and you get to see all the pieces in actual use. Thankfully it's not some obscure science problem, but rather a restaurant that wants to have a computer system. Anyone who's ever eaten out will understand the things that are covered, so you don't spend time trying to figure out what's going on and can instead appreciate the point of the sample. The author's style of writing is very engaging and makes the topic stay interesting. Highly recommended. My boss has already asked to borrow my copy.
Rating: 
Summary: Book is full of errors
Review: Even the publisher states "Unfortunately, the author has not been responsive concerning this issue." Some figures (which are VERY important in the UML) are completely incorrect. Others are misleading. There are some typos that cause statements to be misleading. I do not recommend this book, especially for beginners.
Rating:
Summary: Simplifies a complex subject
Review: For those of you who think you will buy this book and then build complex software systems immediately after you're done -- forget it. The UML is fundamentally misunderstood. It is necessarily a very complex subject - more complex, in fact, than the OOP languages (C++, Java) that it helps to model. The idea here is not necessarily to simplify, but to provide an extensible modeling framework for creating software SYSTEMS as opposed to software PROGRAMS - a much more daunting task indeed. That said, this book does a fine job of covering the basics and distilling it for mortal consumption. My biggest complaint is that it seems... disconnected. He does a good job of explaning terminology, but I still don't understand how all the pieces fit together. That may be more due to my inexperience however, and since it is The UNIFIED Modeling Language, that implicitly means that several methods (any of which could represent a stage in designing a system) were brought together. All in all, a very good introductory text.
| 
