Customer --> Supplier misleading arrow?!

ddd-crew / context-mapping

Creative Commons Attribution Share Alike 4.0 International

1.46k stars 125 forks source link

Customer --> Supplier misleading arrow?! #2

Open edlich opened 4 years ago

edlich commented 4 years ago

Great work! Just a micro remark: Wouldn't it be better to remove the arrow in the Customer-Supplier picture or turn it around?! I mean the "Customer gets" something which the "Supplier provides". Or did I miss something? Best greetings Stefan

sl-manuelguilbault commented 4 years ago

@edlich the way I understand it, the arrow shows the direction of the dependency. The customer depends on the supplier, not the other way around.

edlich commented 4 years ago

ok thanks.

stefan-ka commented 4 years ago

I'm probably biased because of the syntax in @ContextMapper, but: I would turn it around, because in the "DDD jargon" we always talk about Upstream-Downstream relationships and according to that metaphor I would illustrate "information flow" and not direction of dependency. The information flows from upstream to downstream; or from supplier to customer in this case. This is the reason why its the other way around in @ContextMapper: Customer <- Supplier or Supplier -> Customer

mploed commented 3 years ago

Sorry for joining in late to the discussion. I get your arguments and I come to the conclusion that arrows in context maps are a bad idea in general because they lead to many implicit assumptions depending on the context of the folks looking at them.

My suggestion is: let's just get rid of the arrow in the Customer-Supplier relationship visualization.