Rating: 
Summary: Cpre 486
Review: I felt that the this book descibed the individual patterns that could be implemented in the unified process well. The diagrams that were used in the book were extremely helpful in understanding the relationships between classes and enhanced the understanding of the patterns and the unified process.
Rating: 
Summary: Decent, but too narrowly focused
Review: This book was pretty informative concerning the application of UML, but only to an automated Point-of-Sale System. Lahrman included an excellent number of diagrams and examples of the different UML notations, however, they all focused on the POS system, and were thus sometimes hard to apply out of that context. The book did a good job presenting GRASP and GoF patterns, but the lack of variety in the examples made for confusion when discussing applying different patterns in the same type of system. One very nice feature of this book is the set of quick-reference diagrams inside the front and back covers of the book. These come in very handy.
Rating:
Summary: Good book on OOA/D
Review: This book helps introduce OOA/D, UML(very thoroughly), software patterns, use cases, iterative development, and other topics. It also gives insight on object oriented programming issues. One of the best features of the book is that you're able to read it and not have to illustrate by one programming language. I think the author using POS example was a good idea but could used couple more to add diversity. This book makes object oriented programming seems easy! Good start for students wanted to be software engineers.
Rating:
Summary: Useful, but limited
Review: While this book gives a good overview of the UP, I found it to be somewhat lacking in the "applying patterns" aspect. It did describe GRASP and GoF patterns consisely, but the examples, which all centered around a single system, were so simple and completely applicable, that it made applying the patterns to a totally different type of system, and seeing them from any but the very obvious angle in which they were introduced, difficult.
Rating:
Summary: Good Book, but not enough detail.
Review: This book was used as are main text book for CprE 486 at Iowa State University. And proved to be highly useful for learning the concepts, but it stopped there. It seems like it introduces stuff and then almost immediately moves on. This makes it hard to try and use it as a reference when trying to accomplish assignments for it doesn't always provide clear and concise examples of how things are suppose to work. It introduces the notation, but leaves one kind of high and dry of how exactly to use. I would definitely recommend reading this book at least once, but whether or not it should be kept or traded in for Beer and Pizza is highly debatable. JB
Rating:
Summary: This is a great book.
Review: This has been my most used book this semester. It is a must have for any software engineer. I will not be selling this book back. The pace is very good, as well has great references on the inside covers.
Rating:
Summary: excellent book for ooad
Review: The book is very effective in guiding the reader by giving a real-world example throughout the chapters. It covers concepts of solid object-oriented design principles, which helps improve a software designer's skill set. Especially as a student from other books I used this book is very clear and easy to understand thru out the chapters. The Author does a good job of showing how patterns are used within the context of the UP. The discussion on the FURPS & GRASP patterns is exceptional, because their application in more complex design patterns is shown as well. Also all the diagram that were listed have a a detailed brief dicription about them.
One thing i didn't like about this book is that, the Author tend to conflict with its statement. If someone went thru each line of the book it is easy to find where two ideas conflict to each other. And it very helpful to have guidance about the conflicting topics to be singled out by instructors, experience Engineers which helps me in my experience.
Rating:
Summary: Review of Applying UML and Patterns
Review: Applying UML and Patterns is a very good book for learning OO anlalysis and design. The book is very well written and makes it easy to find stuff. The diagrams are very helpful and it gives you great hints and tips when trying to write different diagrams ( SSD, DCD, domain model, collaboration diagram, interaction diagrams, etc...). I enjoyed the book and would recommend it to anyone that needs a reference for an OO analysis and design class.
Rating: 
Summary: OOA/D (CprE 486)
Review: A job well done!! This book genuinely gives a visualization of how to work with a software product. A thought that exceeds the idea of programming is explained by defining the how to solve a problem, and how to make a successful product with the help of analysis and design. I enjoyed learning from this book and did not have to consult any other related material because the examples provided in the book are very helpful and convey the understanding. I think that the author Larman has done a very nice job managing the software analysis and design as well as explaining things.
Rating:
Summary: A good textbook for learning the Unified Process
Review: This book introduced the concepts of Object-Oriented Analysis and Design in a very iterative and clear way just like the Unified Process itself. FURPS+ requirements, GRASP design patterns, GoF design patterns, architectural patterns, and many other OOA/D principles where detailed and then implemented in this book with very concrete examples using the Universal Modeling Language. The author does a very good job of breaking down and explaining the many examples of UML artifacts(diagrams, use-cases, etc.) created during the Inception and Elaboration phases of the development cycle. The one thing I found missing in this book was an appendix. I felt it would have been easier to follow if the author used an appendix with the artifacts of his POS after each iteration.
| 
