Streamlined Object Modeling: Patterns, Rules, and Implementation

Rating:
Summary: A great tutorial and reference
Review: After reading the book the first time and assimilating its content, I started applying it in one of the object models I was working on. I used the Streamlined Object Modeling techniques a little bit at first, and, after realizing some of the great benefits, I used them extensively, refactoring my model according to the book's principles. I've got yellow sticky notes throughout it, as it serves as a reference for me now; I wouldn't want to do analysis, design, or implementation without it.

When I discovered Peter Coad's Object Modeling in Color book (ISBN 013011510X), where I was introduced to his "domain neutral component" (DNC), I had an epiphany. Then, after experiencing the fractal application of the DNC, I started to notice the patterns that Nicola, Mayfield, and Abney lay down quite nicely. It is a natural maturation of thought from Coad's DNC; Coad himself even acknowledges the importance of the book.

If you want to become a good object oriented analyst, read this book, then read it again. If you think you're a good object oriented analyst, read this book, then read it again. In either case, after applying the principles described, I think you'll wonder how you ever got along without them.

Kudos to Nicola, Mayfield, and Abney for an intellectual milestone in object oriented technology. I wish someone had handed this book to me when I first started working with object oriented languages.

Rating:
Summary: A great tutorial and reference
Review: After reading the book the first time and assimilating its content, I started applying it in one of the object models I was working on. I used the Streamlined Object Modeling techniques a little bit at first, and, after realizing some of the great benefits, I used them extensively, refactoring my model according to the book's principles. I've got yellow sticky notes throughout it, as it serves as a reference for me now; I wouldn't want to do analysis, design, or implementation without it.

When I discovered Peter Coad's Object Modeling in Color book (ISBN 013011510X), where I was introduced to his "domain neutral component" (DNC), I had an epiphany. Then, after experiencing the fractal application of the DNC, I started to notice the patterns that Nicola, Mayfield, and Abney lay down quite nicely. It is a natural maturation of thought from Coad's DNC; Coad himself even acknowledges the importance of the book.

If you want to become a good object oriented analyst, read this book, then read it again. If you think you're a good object oriented analyst, read this book, then read it again. In either case, after applying the principles described, I think you'll wonder how you ever got along without them.

Kudos to Nicola, Mayfield, and Abney for an intellectual milestone in object oriented technology. I wish someone had handed this book to me when I first started working with object oriented languages.

Rating:
Summary: a MUST read - worldclass, best-practice domain modeling
Review: As others have stated, the content of this book is a tremendously important contribution to object-oriented analysis and modeling. The authors have successfully analyzed and pared down OOA to it's very essentials. Until you read this book you will not truly understand the significance of this. They have discovered an amazingly small set of irreducible patterns (not to be confused with design patterns, these are analysis patterns) and rules which can be applied to the modeling of any business domain - large or small, simple or complex. And which, when applied, lead to accurate and consistent models in the most direct and timely manner possible. No matter what methodology you subscribe to, if modeling the domain is one of the practices then this is how the modeling should be done. Study the patterns and rules, internalize them, your productivity will soar, your colleagues and customers will consider you a genius. It should not be hard as the presentation is clear and logical and the patterns and rules themselves have the simple elegance that fundamentally correct solutions usually exhibit. However, the authors are not ivory-tower academics presenting some arcane theory that is purely descriptive. They are practitioners with years of real-world experience, thus they show us the whats AND the hows. And they do not stop at analysis, the authors also do us the great favor of showing us how these patterns and rules actually end up being implemented in real code. This book now sits at my side as an essential reference. I plan to refer to it for my work, of course, but also to 'test' models I come across in other books.

I'm very surprised at the low Amazon.com sales rank of such a unique, insightful, and practical book. With agile and "extreme" methods and practices all the rage you would think a streamlined, dare I say 'agile', approach to modeling would have recieved more attention. I suppose the publisher missed a great opportunity by not putting "Agile" somewhere in the title. Having been the XP 'evangelist' and coach on an XP project I think it even has a place in XP (though purists will argue that point). This is my biggest problem with XP - XP recommends coming up with a "metaphor" for an application which gives the project "conceptual integrity" and will allow the customer and programmers to communicate clearly about the application. In the famous C3 payroll system project the sytem was likened to a manufacturing line in which paychecks were 'assembled' from hour 'parts' and various other 'parts'. Sorry, it may have worked but it is overly contrived and not "the simplest thing that could possibly work and no simpler". The other problem is that Beck himself says that coming up with a useful metaphor cannot be taught and that he can only come up with one on half his projects. So what if, instead of racking your brain to come up with a useful metaphor, which you will only come up with 50% of the time at best, you used a simple-as-possible-but-no-simpler modeling approach to model the *actual* business domain? Wouldn't that model provide the necessary "conceptual integrity" for the system under development and allow the customer and programmers to communicate clearly about the system, and do so *directly*? In the C3 case, paychecks would be paychecks and hours would be hours. No translating back and forth between different domains. I understand the purpose of having a good metaphor - to capture and allow communication of the essential entities and of the essential relationships between those entities. But I think that creating a basic domain model, quickly and iteratively, by applying the patterns, rules and techniques in Streamlined Object Modeling, is a cleaner and more direct practice than metaphors and fits in fine with XP. And creating such a domain model is possible not just 50% of the time, but 100% of the time. (The authors do make certain suggestions and recommendations here and there reflecting their own methodology and implementation preferences which do not always jive with agile and, especially, XP practices. But those are easily identified and agile/XP practitioners should not allowed them to distract from the core of this work.)

In the interest of full disclosure I should state I know and have had the privilege of working with all three of the authors. They gave me an early draft and I did not read it. The book was published and they gave me a copy and I did not read it. Sorry, guys and gal! But finally, this past week, I got around to reading it. Fantastic piece of work. I just wish I would have read it sooner!

Rating:
Summary: Great Book
Review: Great book. Every analyst and developers should keep a copy. Explains the object methodology in terms of patterns and rules. As mentioned in the book, this book helps to bring beauty and elegance in your architecture process.

Rating:
Summary: The "Aha!" of object-modeling
Review: I dont exactly remember on which mailing-list I saw this book mentioned but I will never regret my curiosity on that day.
I had been practising object modeling for some time before I read that book and was, at times, wondering :
-what could be the right objects in that situation ?
-where should I put this behavior ?
-do I need "services/processes" objects to operate on my "domain" objects ?

This book gave me really precious answers :
-use the patterns to identify objects
-Let the objects do the work
-Let the object that has the knowledge do the work that requires this knowledge.

I have been practising on new projects since and found the lessons invaluable.

That's why I am not surprised at all about other reviews and I have been recommending the book around me ever since.

The fundamental complexity of business systems is business, not transactions, persistence, gui or any other technical aspect. We have many years of experience with technical matters but we often strive to preserve/improve business value in the systems we build.

Rating:
Summary: Great Tutorial for New Modelers
Review: I'm relatively new to modeling and object programming. Up to this point, I have struggled to find objects and to develop their attributes and their relationships with other objects. This book has broken that barrier for me. It describes an intuitive set of patterns and rules for analyzing and modeling the business systems that form the basis of most software. The patterns are like pieces of an Erector set. Each one is simple; they are combined to form structures as complex as one needs. The rules describe how to combine the patterns. The Java prototypes are straightforward and easily implemented, providing a complete framework for development. If you are just starting out in modeling, I would recommend UML Distilled for an overview of UML and this book for a tutorial on how to use it. I'm moving a lot of other modeling and pattern books to the back room-- I think this book will be my primary modeling resource for the forseeable future.

Rating:
Summary: Extending the state-of-the-art
Review: Nicola, Mayfield and Abney take up the work that Mayfield and Coad did in their earlier book "Object Models". Nicola et al take a slightly different slant from Coad's 1999 book "Java Modeling" which introduced 4 Archetypes and the DNC. The Coad book was a quantum leap in the emerging science of business modeling. The book itself was hard to penetrate and wasn't as highly regarded as it ought to have been.

Nicola et al don't make the same mistake. This book is easy to read and well explained. It introduces some related ideas to the DNC and Archetypes from the Coad book. They call them Collaboration Patterns and Pattern Players. The techniques here are easy to understand and easy to use. They should be repeatable. As such this extends the state-of-the-art in business modeling.

There are very few people continuing to extend the knowledge in modeling business logic. However, the Coad Series authors including Nicola, Mayfield and Palmer continue to develop this valuable area. For those of us who value thought first and gaining an understanding of what we are doing before we cut any code, this new book from some of the World's best object modelers is a must read.

Rating:
Summary: Simple, Flexible
Review: There a simple beauty to good architecture. The authors boil down object modelling to 12 patterns that represent the simplest building blocks. With these you can model any system and have that model be comprehensive and flexible for any complex system.

A must read!

Rating:
Summary: Should be called Model Engineering
Review: This is one of those books that comes along every now and then- that only the fortunate few find and buy and think, what a truly insightful peice of work. This book is one of those times. ANd consider yourself fortunate that you have found it. And to make it even cooler: it is actually good to read!

It is both a philosphical and technical blueprint for the modeling process: forget use cases and such. This is about modeling the domain using twelve pattern players that, alone and in combination, describe virtually all domains. Twelve simple pieces that can be snapped together to make extremely complex models that are robust, resilient and extensible. Amazing stuff.

At 400 pages this is the perfect size book: there is no bloat...just a fortright exposition that well explained and diagramed. This isn't a book burdened with UML (I have a beginners guide to UML that is about the same thickness...UML has lost its way: it's become ridiculously bloated and cubersome and oh so self-important). This book helps your pare away the edifice of UML that adds major complexity to the modelign process and get down to the point of the exercise: modeling. Simple.

This book will give you a set of tools for analayzing domains efficiently: because you will permeate what it teaches you through all your domain analyses, which then make the process easier, quicker, and more effective and the net result will be better and stronger. Then you can layer as much UML on it as you like (UML is like butter, full of cholestorol that clogs the arteries). I guess you could call the tools it teaches you- Rapid Modeling.

This is a good book. Try it and find out. Definintely 5 stars.

Rating:
Summary: The Best Book of OOA - Strongly Recommended
Review: This is really the best OOA book I have ever read - concise, in-depth and practical. Thanks for the authors, they make complicated things simple and well-organized.
It would be fantastic if the authors write another OOA book titled "Applied Steamlined Object Modeling" to show how to use SOM by example.