Analysis Patterns: Reusable Object Models by Martin Fowler - Presentation Transcript
Analysis Patterns: Reusable Object
Models by Martin Fowler
Study, Don't Just Read This Book.
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 todays financial markets. Fowlers
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.
Personal Review: Analysis Patterns: Reusable Object Models by
Martin Fowler
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 discussion 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.
For More 5 Star Customer Reviews and Lowest Price:
Analysis Patterns: Reusable Object Models by Martin Fowler 5 Star Customer Reviews
and Lowest Price!
I bet you are an object oriented software developer more
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 discussion 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. less
0 comments
Post a comment