 |
GetTextbooks.co.uk
Compare Prices & Save up to 90% |
|
|
|
| Login | Sign up | My Wish List |
 | | Object Models: Strategies, Patterns, and Applications (2nd Edition) (Yourdon Press Computing Series) by Peter Coad, David North, Mark Mayfield ISBN-10: 9780138401177 ISBN-10: 0-13-840117-9 ISBN-13: 9780138401177 ISBN-13: 978-0-13-840117-7 Paperback 1996-10-20 Prentice Hall PTR Find Lowest Price |
Reviews | ||
Painfully unreadable; academic and boring This book seems to me the notes of a college professor hoping to create a standard in modeling and chartifying object orientation. It's about 80% charts (his format, often complex and useless without study), endlessly repetitive simplistic strange outlines, and loads of tedious chatty faux-dialog with lots! of! exclamation! points!! If they gave me this book as a textbook in college, I'd drop the course. If I spent too much time with it, I'd give up programming. BORING, TEDIOUS, and unreadable. I ended up skimming this book. Frustratingly, every 40 pages or so, there's a couple paragraphs that are relevant and useful. Fortunately, they're easy to find because there are so few spots where he bothers to write whole paragraphs. I'm looking for a book that helps me tune my sensibilities in designing and implementing object orientation, without boring me to death. If anyone can help, please comment or email me. | ||
I keep coming back to this book I have struggled a bit with Peter Coad. Nonetheless, I always felt that I would get to grips with his somewhat unusual style and that it would be worth the effort. Indeed it has been! This book was well ahead of its time in terms of its approach to OO design. Chapter 7 presents 148 strategies that guide you in your design effort. It also has a number of analysis patterns which are very useful. Personally, I had no problem with the notation he used, in fact, I found it more intuitive that UML. The material in this book is refined in Streamlined Object Modelling (Nicola, et al) and Java Design (Coad, et al) but this is it's starting point. | ||
Somewhat dated, but still valuable Published in 1995, this book suffers from the affliction of coming into being before the Unified Modeling Language (UML) was defined. Inside the front cover, there are three instances of the Object Model, one in Coad notation, the second in Booch notation and the third in Rumbaugh notation. Having worked in UML since it was developed, I found the trip back to the before time to be unnerving. I spent some time going over the diagrams and found the differences in notation so significant that it took me awhile to equate the three diagrams. The inside of the book is easier to understand, largely because understandable applications that are represented. They are: *) Connie's convenience store (a point-of-sale application). *) Wally's warehouse (a warehouse application) *) Ollie's order center (an order-entry application) *) Dani's diverters (a soft real-time application) *) Andi's autopilot (a hard real-time application) Each is developed from the beginning, the first step in all cases is "Identifying system purpose and features." From this, the objects are identified and defined, followed by a section on applying patterns. Coad and his group was one of the earliest to include patterns as a fundamental component of their development strategies, so this book is secondarily a textbook on what patterns are and how they are used. This book has worn better over the years than many of the others written about object models. Coad notation is used throughout and it is very similar to UML. This makes it much easier for people experienced in UML to read and understand what is being done. For this reason and because the applications are so well developed, I can recommend this book to all modern developers using object-oriented design strategies. | ||
A Quantity of Strategies and Patterns Shows you how to create object models (analysis models) through indepth examples and guidance by presenting strategies and patterns as you need them as you work through the examples. The strategies tell you how to approach a task such as how to select objects. Strategies are short, focused. For example, a strategy may have three or four one-sentence things to do to accomplish a goal. The patterns present template objects and their typical interactions. The examples are relevant to business analysts. After working through even just one example, you will be able to create object models and using the strategies and patterns. Includes reference section containing all of the strategies and patterns. The book uses COAD notation to present the examples, so for people familiar with UML it takes a little getting used to. | ||
Learn by Example The strategies and patterns mentioned in the book are really helpful. They improve the object think. The examples explain the author's point of view clearly. This book complements other books in OOAD and patterns by Craig Larmen, GoF, Martin Fowler etc. One interesting point is that the author shows how same strategy or pattern helps in design in various problems. Many authors do not do this. For beginners, it is often difficult to grasp a strategy or pattern with just one example. One drawback is it uses UML notation very less. But Coad notation is simple and we can easily grasp to understand the diagrams in the book. If you want to learn from solid examples, this is a good choice. If you are very new to OOAD, this is not the one to start with. | ||