Enterprise Patterns and MDA: Building Better Software with Archetype Patterns and UML (Addison-Wesley Object Technology) [Englisch] [Taschenbuch]

The authors start the journey by introducing concepts and techniques such as archetypes (universal, recurring "things") and archetype patterns, and Model Driven Architecture. Furthermore, the authors have dedicated one chapter for describing a technique called Literate modeling (combining traditional visual modeling with an accessible business context provided via a narrative text, for example).

Up to this point (vicinity of page 116), the authors' writing style has been flawless, in my opinion, and easy to read. From chapter 4 onwards, the authors have provided a huge pattern catalog for archetype patterns. The catalog has been divided into chapters around archetypes such as Party, Order, Customer, and so on. Each archetype pattern introduces a business context, a high-level overview model, and descriptions of the related archetypes, their properties and related activities.

I didn't go through even nearly all patterns in the catalog. However, I feel confident that I will dive into the catalog looking for insight when moving to a new problem domain on a new project. Enterprise Patterns and MDA is a nice resource to have on your bookshelf.

Chapter breakdown: Archetypes and Archetype Patterns; Model Driven Architecture with Archetype Patterns; Literate Modeling; Party Archtype Pattern; PartyRelationship Patter; Customer Relationship Management Pattern; Product Pattern; Inventory Pattern; Order Pattern; Quantity Pattern; Money Pattern; Rule Pattern; Summary; Archetype Glossary; Bibliography; Index

Now, when I requested this for review, I was expecting something in terms of programming patterns and technical material. What I got was a great business tool for modeling typical business objects and transactions. The authors take a business concept like Inventory, and they build a model around it. The model is an archetype, or a entity that exists in some shape in every business. Through UML diagrams, you'll see all the parts that make up the archetype and how to take the parts you need to build your own version of the entity. While the Inventory model is very comprehensive in the book, you can also pull the pieces you need to model the reality that exists in your own business.

There's some very practical benefits you can gain from this book. If you're building an application and need to track a customer (for example), you can turn to the Party model and see all the parts that make up that type of entity. This will help you to understand all the data elements that make up a Party, such as address (web, email, telephone, geographic), organization, person/gender/ethnicity, relationship, etc. These are elements you might think of and/or remember to include, but having the model there helps you get it right early on.

If you're a business analyst, you will really get your value from this book. And if you're a developer who also has to design the systems, you'll look like a wizard when you complete a solid design with features the customer didn't even realize they needed.