Regular marked price: $64.99Discount Price: $51.99
Cost Savings: $13.00 (20%)Price fluctuation possible.
How soon does it ship: Normal ship time within one day
Shipping? Absolutely FREE if you qualify for Super Saver Shipping.
Type of bind: Hardcover
Dewey Decimal Number: 005.12
EAN num: 9780201895421
ISBN number: 0201895420
Label: Addison-Wesley Professional
Manufacturer: Addison-Wesley Professional
Quantity: 1
Page Count: 384
Printing Date: October 19, 1996
Publishing house: Addison-Wesley Professional
Sale Popularity Level: 110768
Studio: Addison-Wesley Professional
Other books you might be interested in perusing:
Editor's Notes and Comments:
Product Description:
Martin Fowler is a consultant specializing in object-oriented analysis and design. This book presents and discusses a number of object models derived from various problem domains. All patterns and models presented have been derived from the author's own consulting work and are based on real business cases.
Amazon.com Review:
Patterns are higher-order designs that can be reused across projects and types of computer systems. Analysis Patterns: Reusable Object Models defines over 70 patterns, beginning with some from the business world, such as the Party and Accountability patterns, which define the players in organizations and whom they report to. Many of the other patterns are drawn from the health care industry and mainly show patterns of doctor-patient interactions.
The patterns for financial markets will probably be accessible for the majority of readers. Author Martin Fowler defines a Transaction pattern (and related patterns) as well as several patterns for the Accounting of Objects. He moves on to modeling stock markets with Portfolio, Quote, and Scenario patterns, which define how a price for a stock is determined for a given moment. Interestingly, he establishes patterns for Forward Contracts (for derivatives) as well as Options, and so takes on a complicated area in today's financial markets.
Fowler's considerable design experience in these fields is beneficial, as he is able to define each pattern in both text and software engineering diagrams. Only rarely does the author provide implementations of these designs and those that are furnished are done in Smalltalk, which makes this book more suitable for those who have experience in object design.
User popularity level:
Rated by buyers 
-
This is Martin Fowler's very first book, published in 1997. The book is divided into two large sections.
The very first section details analysis patterns that Fowler has encountered across industries. These chapters cover several common domain patterns including representing organizational hierarchies, inventory, accounting, and others. Fowler approaches these chapters by starting with a simple model and repeatedly expanding on this model to fit more and more complex needs. This section of the book is interesting from an academic and a practical perspective. It was interesting to see how Fowler has approached different domain problems and I expect to reference these chapters as I tackle similar problems in the future.
The second section of the book covers what Fowler calls Support Patterns. In these chapters Fowler discusses tiered architecture, presentation layers, facades, and association patterns. The second section on support patterns is less useful and some chapters are quite dated. While this information may have been useful in 1997, if you are looking for more information on layered architectures read Enterprise Application Architecture - a more recent book by the same author.
I found this book to be quite good. I enjoy Fowler's style of writing and for the most part I found the book easy to follow. However, this is Fowler's very first book and it lacks the polish of his more recent other books -- in a few spots it was hard for me to follow the author's train of thought.
This book predates UML and the diagrams used throughout the book take a while to understand. There is a key to the models on the inside cover of the book, but if the diagrams had been updated to UML they would have been easier to understand. If needed, you can find UML diagrams for this book on Martin Fowler's website. I think sample code would have helped clarify some of the models as well, as was used in the "Gang of Four" book.
If you are designing a domain model for a complex business, I think this book would be useful for you. If you are looking for similar books, I would suggest Design Patterns by Gamma, et al. ("Gang of Four" book), Patterns of Enterprise Application Architecture, and Refactoring both by Fowler.
Rated by buyers 
-
What I am nearly always missing when reading about design (esp. when sifting through design case studies) is the path that lead to a design. The weighing of arguments that made the author/designer choose the solution at hand. The context and the "drivers". Fowler is the only one achieving this: offering different solutions and discussing their advantages and disadvanteges. Yes he dives deep and goes into abstract concepts, but sometimes solutions only differ from an abstract viewpoint. You need quite some understanding of design principles, to (i) understand the book and (ii) be a good designer.
For me this is the book that helped me understand the design process as it should be. And using "analysis patterns" he gives plentiful of concrete examples, sharpening your mind.
One remark to everyone critcizing Fowler for not using UML: This book does not use UML since it dates back to 1996! When UML was not really there. Version 0.9 of the UML came out in the second half of 1996. And btw. Martin Fowler has written the very very first -- and still one of the best -- book on UML ("UML Distilled", now in its 3rd edition).
Rated by buyers -
Kind of funny, reading the reviews here makes it clear that this book is something of a sleeper, it has not gotten the exposure that a lot of the other pillars of the pattern community have. I think the reason is that people may glance at it and think that it is too domain-specific. In fact, this book does a lot of great things, it is a meditation on some crucial OO modeling issues.
The very first problem Fowler broaches is a patient's weight and he states, correctly I'm sure, that most programmers would just make weight a class property and make it be of type integer. But there are problems with that approach. First one is the issue of units. If you make it an int you are assuming that it is just a count of pounds. What happens if you want another measure? Furthermore, what happens when someone asks where the patient's weight has gone in the last month.
From this point of departure, many issues are taken up. For people who have grappled with OLAP before and know something about dimensional models, it will seem as though he is trying to make an operational into an analytical model, which experience has taught us is not good. But, in fact, there is sanity to Fowler's approach.
Personally, if he ever does rev this book (read on his site that he is thinking about it), I wish he would consider writing a section that attempts to hide the observation elements and seamlessly map them back into the object model. Having a separate class keeping track of what the weight of a person represented by another class is does ultimately seem to undo the objectness of the model, but that's a minor nit. Definitely a book that I've returned to many times.
Rated by buyers -
I bet you are an object oriented software developer striving to build better applications. If you have not read GoF Design Patterns and followed that with Vlissides's Pattern Hatching, read those first. Follow those with this, Martin Fowler's Analysis Patterns.
As two readings of Design Patterns took my OO knowledge from infancy to adolecence, Analysis Patterns will take you from adolecence to adulthood. Fowler's work does not put together patterns from the Design Patterns book, but takes its time to decompose actual application domain concepts to applicable object models. It will then be up to you to use your knowledge from Design Patterns to create mechanisms that support properly modeled business concepts as Analysis Patterns describes.
If you like OO modeling and design, but are wondering how better to apply your modeling concepts, Fowler's book is something you will definitely benefit from. However, make a pot of coffee per chapter-this book is very dense with concepts.
Fowler ends Analysis Patterns with some more easily read chapters on application design on a larger scale. You've heard of "n-tier," his discusion of the concepts of "n-tier" at the end of the book are possibly worth reading first.
After reading this book-and understanding it's motivations-you will never again be tempted to take "innocent" shortcuts in your application design. You will not be motivated to use "Strings" for "measurements" or "doubles" for "distances." You will look upon your peer's object designs either with a new understanding that they know that going the distance with their object model is worth it-and you won't demand they dumb down their design ever again-and you'll likewise gain intuition about where a simplistic business domain model is going to fail.
Rated by buyers 
-
There are lots of interesting ideas here, but the actual patterns themselves are not that useful as they are too abstract.
Find other books like this one:
