Applying UML and Patterns is a great introduction to UML and Object Oriented Analysis and Design. It has a nice slow curve to help introduce newcomers. Each chapter builds upon the concepts and examples of previous chapters to help walk the reader through the process. A point of sale system is used as a consistent example throughout the book. Each chapter adds new features to this system, while simultaniously introducing the reader to new UML concepts. Each new idea is accompanied by several example diagrams with notes to highlight important concepts. Each chapter also includes a quote that should appeal to ones inner computer geek. The linear progression of this book does have its downsides, however. It is difficult to find specific information, or to start in the middle. Each section assumes youve read everything up to that point, and those expecting to use the book as a refresher or reference may find it difficult to find the information they desire. Similarly, one may confuse the notes on the example diagrams as a part of the diagram if not familiar with the style of the notes. Overall it is a very well written book that should prove very useful to those new to UML and OOA/D. Those already familiar with the topic should probably look for a less structured source, but beginners should definitely give this book a try.
This book is a great guide for an object-oriented project using UML and (R)UP. The book doesnt learn much of UML nor UP has the title said (Applying...not Learning...). I recommend read first some basic tutorials on UML as UML Distilled by Fowler and the introduction for RUP by Kruchten. Then, you can return to this one and get amazing. The book emphasizes in the business modeling, requirements and design disciplines (RUP), and clearly shows us how to convert a use case into a design model, applying patterns and the tools of UML in the best easy way. Sorry for the Phd that hates OOA/D. If youre in the precedural programming world (repeating code over and over again, no inheritance, no polimorphism, etc., etc.), why read this book? But if you want to get the idea of OOP and want some good advise in this jungle get this book! Definitely, one of the best and complete books I read of OOA/D: common UML, patterns, UP and lots of advices in a few pages.
I am in agreement with some of the observations made in the 1-out-of-5 review by wiredweird. However, I am inclined to rate this book a 5 out of 5. There are a lot of books out there that talk about O-O but stop at inane and condescending examples that limits what knowledge, if any, you could get from the books. On the other side of the spectrum, you have outstanding books like "Design Patterns" that might be a little hard to follow for people like, for instance, me. The uniqueness of this book by Craig Larman is that it effectively bridges the yawning gap between the O-O for idiots approach and the O-O for experts approach. Granted that Mr. Larman seems to be calling "Principles" as "Patterns" -- it is kind of a stretch to call "Polymorphism" a pattern, but nomenclature aside, the emphasis is rightly on general principles that prevade patterns of design. Larman might have stretched the limits of UML notation here and there -- but it is almost always to emphasize an idea. The main portion of the book deals with a case study involving a POS system -- good choice, a POS system is something we are all familiar with and it offers a lot of possiblities to show the application of design principles and patterns. Its possible that this is not the best book to teach (or to learn) O-O design -- but I havent come across one that is better. An irritant i have with this book is the quality of the paper used -- it reflects light making it a strain to read it under fluorescent light. Maybe they will fix it in the next edition so that the reader is the only one doing the reflecting.
