Rating: 
Summary: Amazingly right on the spot
Review: I never give review, although I read them before buying almost anything. But, this book is just amazing. Defining all the terms so exactly. Explaining patterns so simply. Proposing a practical approach that makes sense (Operation Contract for examle). I have almost 30 books from process to code. This book could easily replace and do a better job than half of them. If I had known! But maybe you'll not make the same mistake!
Rating: 
Summary: Made my class a nightmare
Review: I don't know if it was just me or the professor (and it may have been either or both) but this book did not work for me. It uses a point of sale system as its example case. It dives _way_ too deep into the case within the material being taught and makes it very hard to get at the meat of the material. Learning from the book required more time and effort/struggle than I had to give. I also felt a general lack of purpose in the book - is it a book on UML, UP, or Design Patterns? I don't know. Some have reviewed this book very positively. I am glad some people have had a positive experience with the book, because I certainly have not. Though not one who usually sells books back to the bookstore, I will make an exception for this book.
Rating: 
Summary: Trying to make a complex reality simple
Review: I've been working with advanced, high-performance, scalable real-time solutions for more than 25 years, and this book really is a denial of my whole professional career and my experiences.
If system development was as rudimentary as Larman claims he seems to have a lot to learn.
In the early 80:s I was involved in developing one of the worlds largest and most advanced flight-booking systems, using very complex real-time logic and long running transactions. It was a complete "non object oriented" system from the beginning but has evolved a lot since.
I've had the privilige to work in all possible roles, similar and identical to the ones that are covered in (R)UP and there is (almost) nothing in practice or in theory that proofs any benefits of using design patterns, use case driven system development. Mr. Larman; please take in consideration the problems you get with serious tangling and redundance when developing object oriented systems. Today I work at NASA as a technical/method coordinator of a space shuttle project. It seems that much of the education in computer science nowadays is based on topics like Agile, RUP, Active databases, XP, OOA/OOD,HGS,...,...
"Houston we have a problem" I really wonder how much money the three amigos has cost the world..?
Rating:
Summary: Our standard
Review: Highly recommended. This book has become our development standard for OOA/OOD using the UML. New developers on the team are pointed to this book for analysis and design activities. The content on design patterns and the concepts of low coupling/ high cohesion are worth the price of the book alone. Also, includes a practical implementation of RUP without all the fluff.
Rating:
Summary: Excellent book and video combination!
Review: Larman's book and video are concise and educational. I have increased my understanding of UML and UP tenfold and I am still learning from this material. I highly recommend both to anyone wanting to learn and apply the Unified Modeling Language using the Unified Process. In addition, coverage of fundamental design patterns makes this combination an excellent value. Feel free to send me an email with any questions about my experience with the book or video. I have no affiliation with Mr. Larman or associated publishers. I am just a very satisfied customer. I hope that more authors/publishers choose a similar format to this combination. Especially the large hard cover text book packaging at the right price.
Rating:
Summary: A must read for those new to OOAD and iterative development
Review: I am new to Iterative development as well as to design in the OOAD perspective. I found this book to be very helpful enabling me to grasp the design concepts.These concepts were introduced very well and provides a pretty systematic approach to design. A book worth having in any person's/organization's (interested in OOAD) library.
Rating:
Summary: Great Ideas for Improving OOAD Teaching!
Review: I recommend that book to everyone I train or work with. After you've read this book, you won't explain OOAD the same way.
The formalization of key architecture principles as patterns for distributing responsibilities is the great invention of the book. We knew these principles before (high cohesion, low coupling) but the lack of formalism made it difficult to explain and communicate the consequences in a way that looked rigorous, rational and comprehensive.
When teaching OOAD at Rational, I successfully used the GRASP patterns to have the students think early in terms of architecture. Identifying, explaining and using these patterns immediately raises the level abstraction. You have the students be aware that drawing a message from an object to another might be an architecturally significant decision. This decision is based on tradeoffs that in the end configure the attributes of the system in terms of flexibility, maintainability, reuse, etc. Craig made practical and understandable ideas that took so long to be understood before! It turns hackers into "beginner" architects.
He also greatly illustrates and warns about the "put-patterns-everywhere" syndrome that we see so often in the field. I also loved how the code samples are introduced progressively...
That book will have designers - who believe UML is about drawing pictures of their code - realize why and how they can work differently. Deep thoughts, easy reading: definitely a must read for every OO practitioner or teacher!
Rating:
Summary: A Must for OOAD
Review: This is the best book I have seen on OOAD.
Rating:
Summary: A masterful OOA/D and UML text.
Review: I highly recommend this book to anyone working in Object-Oriented development or anyone who plans to work in that field. This is THE book to read.
Rating:
Summary: Mikhail Vlasov - A critique Of
Review: Absolutely worst review I ever read. It is obvious the reviewer never read the book. Stick to needlepoint, sir.
| 
