What do you think?
Rate this book
Enterprise Patterns and MDA: Building Better Software with Archetype Patterns and UML
This book presents a proven method of successfully addressing the significant challenges of developing applications for the business world. Borrowing from their significant experience in corporate development, the authors present a catalog of proven and supremely useful patterns that can be applied to the idiosyncrasies of the business domain. This book also explains how to use Model-Driven Architecture to increase the efficiency of your designs, and how to further the capabilities of the industry-standard Unified Modeling Language. The result is a practical, no-nonsense approach to building robust business applications that can be immediately applied in a corporate setting.
528 pages, Paperback
First published January 1, 2003
11 people are currently reading
162 people want to read
Ratings & Reviews
Friends & Following
Create a free account to discover what your friends think of this book!
Community Reviews
Displaying 1 - 2 of 2 reviews
October 16, 2020
It's very difficult to rate and recommend the whole book all together. Basically each chapter should be treated individually. Some of them are just waste of time, some are putting a lot of great insights which definitely are very valuable at the beginning of the design process.
I enjoy the whole concept of using archetypes and reading about a few of them definitely helps. Usually, an implementation process starts from a blank page and slowly adds new things to meet business requirements. If an archetype pattern can be identified while gathering requirements the whole process is reversed, you start with a very extensive model and you start removing elements from it that are not needed. It still requires times and energy but seems like deciding what not to implement is more conscious with fewer surprises in the future that business works this way.
I enjoy the whole concept of using archetypes and reading about a few of them definitely helps. Usually, an implementation process starts from a blank page and slowly adds new things to meet business requirements. If an archetype pattern can be identified while gathering requirements the whole process is reversed, you start with a very extensive model and you start removing elements from it that are not needed. It still requires times and energy but seems like deciding what not to implement is more conscious with fewer surprises in the future that business works this way.
April 1, 2013
understanding the party model and ecommerce foundation - excellent book !
Displaying 1 - 2 of 2 reviews
Can't find what you're looking for?
Get help and learn more about the design.