Rating: 
Summary: Great Introduction to OOAD
Review: The book is very effective in leading the reader thru the same real-world example throughout the chapters. It covers concepts of solid object-oriented design principles, which helps improve a software designer's skill set. Larman does a good job of showing how patterns are used within the context of the Unified Process. The discussion on the GRASP patterns is exceptional, because their application in more complex design patterns is shown as well.
Rating:
Summary: Amazing
Review: The Bible for people who wants/needs to be involved in the process of learning OOA and OOD. Apart from Addison Wesley's UML Series, this is the first book you should buy in case of being in the mentioned situation. A Must.
Rating:
Summary: Amazing
Review: The Bible for people who wants/needs to be involved in the process of learning OOA and OOD. Apart from Addison Wesley's UML Series, this is the first book you should buy in case of being in that situation
Rating:
Summary: Except for the title, a great book!
Review: This book IS what the subtitle says: An Intro to OO Analysis and Design and the Unified Process. It is a GREAT introduction. It also uses patterns and does a good job of explaining why various approaches are what *good* programmers do. But it does strike me that the main title was invented to get the most "hits" on a variety of searches one might try. It's not primarily about "applying UML" which is a good thing, despite the title. It does use UML as its notation whenever notation is needed and it explains the usage well. I am using this book as a text in the first of a 3-course graduate series on software engineering. The reactions from students (all with industry experience, most without OO experience) have been quite positive. The use of an example that runs throughout the book provides a vehicle for getting deeper and deeper into certain topics. Larman writes in a very readable style but he doesn't write "down" to the reader. His motivations for various techniques/approaches are reasoned and appropriate. He references excellent books as well. As the professor, I have used some of these to develop certain topics more deeply in my accompanying lectures.
Rating:
Summary: The Best OO Analysis and Design tutorial book
Review: There are already some great reviews for this book and I don't feel like I can add anything new, but I still want to get my vote in and say that this book is really THE BEST Object Orientated Analysis and Design tutorial book.The book starts and builds upon itself, chapters after chapter as you move forward through the book using the Java programming language. The topics covered in this book include OO fundamentals, UML, design patterns, Unified process, and many other great topics. I wanted to steal a line from the review by Dan Moth where he says, 'Craig Larman proves it (OOA/D) to be a science and not art or magic'. I couldn't have stated this any better. This is a great book and must be in every developer's book shelf, especially ones starting out in OOA/D.
Rating:
Summary: Great Introduction To OO Analysis and Design
Review: This book is the best introduction I have seen to object-oriented analysis and design. It explains the 'Unified Process' of analysis and design, including UML and the use of patterns. I am a big fan of this book because it emphasizes the "why"--the reason for each element of the process from a business perspective. For example, instead of simply offering a recipe for writing use cases, the book talks about why one might include or exclude specific elements to achieve specific objectives. Those (like me) who have avoided Unified Process because it looks too rigid, bureaucratic, and form-laden will love this book. The author argues convincingly that UP is best implemented in an iterative process that looks more like Extreme Programming than the cumbersome waterfall process one typically associates with UP. Then the book shows how to implement a UP process in enough detail, with enough examples, and with enough flexibility, that a project leader can readily put this form of UP into practice. I have avoided UP for years, but this book may have made a convert out of me. It's the first book I have seen that makes an effective business case for UP and presents a practical guide to its implementation. I have no hesitation recommending it to anyone, from novice project leaders to seasoned software architects.
Rating: 
Summary: UML & Patterns in One Book
Review: In general the book is good. If you're looking for an introductory guidance and help with UML, you should take a look at it. This book alone will not make you a UML neither a Patterns expert but it will contribute to your general designing knowledge. I'm not sure how successful was the author by hooking up UML and Patterns. It's not an easy task to include both in one book. Here are some of my remarks: 1. I agree with the UML process that is represented in the book, but I have a strong suspicion that the Grady Booch methodology dominated most of the chapters. The Booch methodology emerged in the early 90th. It was later folded in UML along with others in 1998. 2. The term "Object" is replaced with "Concept". I totally agree that you should be able to conceptualize your model after you have written use cases (based on your business requirements), but your objects are the outcome of your conceptualization process. In this book, the Concepts that are extracted from use cases never become Objects, unfortunately. 3. UML notation is another weak issue in the book. By limiting UML notation, your model will not become a good re-usable component because of a weak abstraction layer that was developed from a limited notation. 4. There is a weak class creation process description. It's not clear how Concepts become classes. Or how Objects become classes. 5. I think that it's a mistake to apply the attribution process to the conceptual model. The attribution should be applied to classes and not to concepts.
Rating: 
Summary: Very disappointed
Review: I was looking for a book on the UML and this book was not it. The subtitle was much more descriptive of the content than the title. The title was very misleading. The book was a very detailed introduction to OOA/D, with minimal descriptions of UML scattered throughout each section. IMO, the writing style was much more complicated than it needed to be--the book didn't have a clear flow; rather, it seemed to jump around and repeat a lot. I'm returning this book now, and I will start looking for a better book on the UML. I'm glad I only wasted 2 weeks reading this one.
Rating: 
Summary: The worst book about UML and UP I've ever seen
Review: Absolutely useless book. For beginners it contains too many details, for professionals it doesn't contain anything interesting. It is clear that the author didn't ever take part in a real development of a real large project. Lost time, lost money.
Rating:
Summary: 10 Stars
Review: First of all, this is not just a book for novice OO programmers. It is a booked aimed at developers and architects as well. There are a lot of methodologies out there, but many of them are inaccessible. This is a full-fledged OO development methodology that is really understandable. Huge bonus: Grasp, which tell you how to construct classes. Bonus 2: UML explained, in depth, from a design standpoint, in the context of a design. It's just so nice to see it finally explained in a useful manner. Best of all: in depth, thorough, patient, approachable explanations about how design decisions are made. I would recommend this book if you do any kind of architectural work at all. It's much better than UML Distilled, the UML Users Guide, UML Components because it's written in an approachable style and doesn't skimp on the explanations. Fantastic, cannot say enough about it.
| 
