EventModeling & EventStorming what tooling is required

If you executed the EventStorming or EventModeling workshop, most likely you found out that the outcome is awesome. Understanding of the solution has sky-rocket. But then a question rises:

How to use it more frequently???

With tools like Miro and Mural, you certainly can model stuff, but the board becomes soon a nightmare:

1. It's hard to track the progress of work with slices, if you don't have appropriate integration with tools like Jira.

2. It's hard to have your board in sync with source code. If you cannot update the model from code or at least validate it, then your model soon will be out of sync.

3. Copying stuff from one board to another system is a chore. Jira <-> Confluence <-> IDE. No one wants to update documentation, no one what to do a stupid job just for the sake of keeping systems in sync.

What do we want to achieve?

We want to engage businesses in modeling their domain. But we also want software engineers to make their descriptions precise. Modellution let engineers to mark blocks as specification, but also let business freely model stuff that they yet, don't know how to express. The blended view can be easily filtered.

We also want engineers to be incentivized in using Event Storming and Event Modeling. When using other board apps, parts of content need to be copied to source code. With Modellution Software Engineers can use plugins in their IDEs in order to insert customized code-snippets. Once the code is in place, Modellution provides SDK that allows them to easily update the model in Modellution based on your source-code (through Reflection).

Modellution Beta is coming soon!

With Modellution you'll get much more and finally, you can frequently use #EventStorming and #EventModeling. Schema register, swim lanes, Jira integration, IDE plugins, and much more. If you want to test us - join the beta program now :)

Sign up free