The Steps to Modeling Business Concepts
Who's on first, What's on second, I Don't Know is on third
As I mentioned in the:
This Agile Data Guide is slightly different to the previous Agile Data Guide in that its both being co-authored and that its describing the Pattern Storming process of Modeling Business Concepts, rather than describing a Pattern Template you use to define or Map the Business Concepts.
One of the first things Juha Korpela and I needed to define and agree is the steps in that process.
So here is the first very rough version that we have defined:
In the Agile Data Guides we use a pattern of describing the Pattern or Pattern Template in three different ways:
The left to right steps in image one
A narrative version in image two
A diagram or map version which we will create much later
The goal of this version is to elicit a conversation between Juha and myself. To be able to point at a specific step in the process and say “I don’t think it belongs there” or “I think it should be called something else” or “I think the description of that step needs to be iterated”, or just “WTF are you thinking”.
As part of our co-writing process I thought we could try a little audience participation.
So I am going to experiment with using the comments feature in Substack for this content to have the conversation with Juha on what I think we need to change.
Fell free to jump in and state an opinion if you so wish. We may agree with your comment and iterate the content based on it, we may not. But we will deffo read it.
We have both agreed that we will use the term Concepts as the thing to describe things, rather than entities, dimensions etc.
Concepts and Relationships sounds right to me.
Something I find helps with choosing the right verb is checking if the reverse verb makes sense.
Good: Customer buys Product -> Product bought by Customer
Bad: Employee belongs to Department -> ???