Comments on: How to Create a Business Domain Model

By: Martin L. Shoemaker

Martin L. Shoemaker — Tue, 05 May 2009 14:37:19 +0000

Needless to say, I highly approve of this message. I draw diagrams constantly as I work with customers, using the diagrams to highlight misunderstandings and spark conversations. I find that if I handle it right, I can act as their UML tool, drawing what they say without ever having to teach them notation. After all, the shapes and connectors are all labeled using terminology from their domain. They figure it out from there. Once in a while they’ll ask me about the shapes and arrows; but more often, they simply tell me how my diagram is wrong, and how I should correct it. It’s a very productive way to get them talking.

By: Tim

Tim — Tue, 24 Mar 2009 09:51:35 +0000

A bit nss.

I tend to use less formal diagrams initially as they are less intimidating. Interaction diagrams and ELH descriptions of key concepts are also v. useful in flushing out inconsistencies.

The annoying thing about most diagramming techniques is that there are many assumptions that cannot easily be formally captured, but which underpin whole business processes. But that’s not such an issue for getting this type of discussion going.

I also find it useful, sometimes, (especially where there are many groups involved) to have a ‘language definition’ session where we go over common terms and eliminate overlaps. My preference is to start by making up new terms for shared, inconsistent terms so that all baggage is removed.

By: Jeff Harrell

Jeff Harrell — Wed, 18 Mar 2009 00:26:08 +0000

Good tool! There are many who are visually inclined and this reaches them. Diagrams aren’t always the panacea to problem resolution, but they always seem to spark the discussion. I’ve found that matrices sometimes have the same effect.