Research method to define the domain is Domain Story Telling

Acronym

sig-eventing-domain-research

Belongs to

SIG Eventing

Responsible

kruck und Duzun

History

(v1)   2021-01-15 - created initially

(v2)   2021-01-19 - added sources

(v3)   2021-01-20 - added not considered alternatives

(v4)   2021-01-22 - added how this decision will be evaluated and changed the title

(v5)   2021-01-27 - added resolution details and reasons for the resolution

(v6)   2021-01-27 - presented

Why is there need for such a decision?

Decision is required for a unified understanding of domains and process flows.

Additional sources for better understanding the background

• Event-Storming
  • Further information about Event Storming by the Creator Alberto Brandolini
  • Full post here
• Domain-Storytelling
  • Further information

Viable Options

• Event-Storming
• Event-Storytelling
• Domain-Storytelling

Alternatives not seriously considered

• Mindmapping
  • Too simple for a proper Domain research
• Brainstorming
  • Could lead to overload

How is this decision evaluated?

The decision needs to be evaluated by research. Usually the workshops would take place on site. Therefore, it must also be evaluated whether the methods can be carried out online. Finally, a tool is needed that supports collaborative online work.

Resolution Details

We decided to use Domain Storytelling because it is best suited for domain modeling on remote. See further details in ‘Reasons for the resolution’.

Reasons for the resolution

Event-Storytelling will be excluded because it is not applicable for domain research. That method will be used for Events in reallife, not Server-Events. See Event-Storytelling.

Event-Storming would be a great opportunity to create a Big Picture. But it is hard to handle online. From experience we can say that this method won’t work out well this way. Also Alberto Brandolini, the creator of Event-Storming, wrote an article about remote Event-Storming, see Remote EventStorming. He rejects the creation of a big picture on remote, because too much of the value would be lost.