About Duffbert...

Duffbert's Random Musings is a blog where I talk about whatever happens to be running through my head at any given moment... I'm Thomas Duff, and you can find out more about me here...

Email Me!

Search This Site!

Custom Search

I'm published!

Co-author of the book IBM Lotus Sametime 8 Essentials: A User's Guide
SametimeBookCoverImage.jpg

Purchase on Amazon

Co-author of the book IBM Sametime 8.5.2 Administration Guide
SametimeAdminBookCoverImage.jpg

Purchase on Amazon

MiscLinks

Visitor Count...



View My Stats

« And some random Microsoft articles... | Main| Sarbanes-Oxley Act and Notes software development documentation... a question »

Book Review - Enterprise Patterns And MDA by Jim Arlow and Ila Neustadt

Category Book Reviews

Over the last month or so, I've been reading Enterprise Patterns And MDA - Building Better Software With Archetype Patterns And UML by Jim Arlow and Ila Newstadt (Addison-Wesley).  This is another one of those books that I thought would deliver one thing and instead produced much more than I expected.

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.

Post A Comment

:-D:-o:-p:-x:-(:-):-\:angry::cool::cry::emb::grin::huh::laugh::lips::rolleyes:;-)

Want to support this blog or just say thanks?

When you shop Amazon, start your shopping experience here.

When you do that, all your purchases during that session earn me an affiliate commission via the Amazon Affiliate program. You don't have to buy the book I linked you to (although I wouldn't complain!). Simply use that as your starting point.

Thanks!

Thomas "Duffbert" Duff

Ads of Relevance...

Monthly Archives