Analysis Patterns: Reusable Object Models by Martin Fowler

Analysis Patterns: Reusable Object Models Reviews

• 
  Michael

  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.
• 
  Paolo Bizzarri

  The book is good, but I have mixed feelings about it.
  From one side, it has some very good conceptual models.
  From the other side, it is a bit outdated and the prose is somewhat a bit heavy.
  Anyway, a good addition to your conceptual toolbox.
• 
  Philip

  Edit:
  After skimming other reviews, I felt the need to add my professional context. I work as software developer and consultant in the heavy indsutry. Software is not "our" speciality, but we need it to survive. As such, I'm often confronted with tasks like digitalizing business processes that don't even exist in the heads of those who perform them, or literally don't exist because they are part of the change management agenda, who happily use software as their beast of burden.
  Since I'm not a domain expert myself, yet need to figure out what it is they are doing and needing - while communications are restricted, and legacy artefacts or even systems are everpresent - I need an abstract view-point from where to analyse and probe their concepts.
  
  Where this book, and most others of this genre I review, come into play:
  
  This book is exactly what it claims to be: A toolbox for analysing processes.
  
  It does not promise to solve your problems, or give you a guide to how to analyse them and design solutions based on your analysis. Instead, it offers you profound models and patterns, based on real life cases, which describe abstract scenarios which on their level of abstraction, or a higher one, might be useful for your specific case.
  
  As that, it provides a rich collection of such utility tools. As an analyst working part in software-engineer, part in business model reengineering, it happens there are mostly two chapters in this book I really use over and over. The patterns help me design how I question customers, where to look for the needle in the hay, or how to explain a solution to a domain expert.
  
  Thus they are more like a compass, a map for the lost, to help reorienting oneself in the complexities of real life and processes.
  
  In that regard it does a perfect job. I hope that one day it will be a common sight that senior analysts share the models from their life with the rest of the world, so that others may collect them - like explorers of the unknown would collect maps, descriptions and journals of other explorers before them.
• 
  Pavels Kletnojs

  For sure this is a decent book. But I don't think it worth reading it in 2021 unless you are interested in patterns history.
• 
  Steve Whiting

  Takes you through the thought process of developing some generic object models for common business-domain problems.
  
  Some good discussion about how to model and implement these, hampered by the notation of the (pre-UML) modelling diagrams.
  
  I also found it a bit dull, to be honest - not up to the standard of his other, more recent, books
• 
  pluton

  The patterns in the book are very high level and hard to understand on the first attempt. One probably needs considerable experience in developing big systems to read and understand the book.
  Also, the pre-UML models are confusing at the beginning.
• 
  Steven

  1 of the classic software texts on analysis and design.
• 
  Juan Ignacio Gelos

  Simply a must-read for any developer, dev lead, and even IT managers.
• 
  Dave Peticolas

  A nice collection of patterns for use in designing enterprise software systems.
• 
  Eduards Sizovs

  This book can be a good additional to Domain-Driven Design. Analysis Patterns is a listing of domain model skeletons for enterprise applications.