Reviews for Analysis Patterns

The average rating for Analysis Patterns based on 2 reviews is 3 stars.

Review # 1 was written on 2010-04-24 00:00:00 James Fitzgerald the majority of this book is devoted to discussing analysis patterns for specific contexts - e.g., what might we use as a design for a system that needs to be able to manage accounts, convert between currencies, etc. this seems like an extension of the "reusability myth" - now that we're doing object oriented programming, we can reuse our objects all over the place, and consequently have to write less code. this kind of reuse has been shown to work in two limited contexts: libraries and frameworks. code reuse is harder than it seems as the objects need to interact with other parts of a specialized system, and each system has its own special needs. it would be easier to reuse the design rather than the code, and that's Fowler's basic idea here. all the same, when designing a new system, I would want to focus my analysis on the specific needs of that system. I could see, e.g., skimming the section on currency conversions in this book of I was designing an app that needed to do currency conversions, to maybe get some ideas. but my hunch is that I would come up with a decent design based solely on the qualities of the specific system being designed. the remainder of the book is on support patterns, or patterns in implementing a design into software. the presentation on three-tier architecture gives an interesting precursor to the idea developed by Eric Evans in Domain Driven Design. most of the remainder deals with implementation issues relating to rather old-fashioned OO programming languages. like many software books, this text had not aged well. the biggest thing I got out of skimming through these analysis patterns was the impression that UML was not a very suitable tool for this kind of work, and in some ways quite OO-specific. many implementation concerns addressed are non-issues in modern languages such as Scala. a lot of the underlying landscape idea-wise has changed as well with concepts like DDD and event sourcing. more than anything else, this book helped me so appreciate programming in a language like Scala rather than a language like Java or C++.

Review # 2 was written on 2018-07-19 00:00:00 Mario Espinoza Good but outdated This book was great at a time writing. It is less useful now. It still contains many valuable pieces about OO modeling, but reader should not hesitate to skip over some chapters.