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.
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.