This article is here to compare three approaches to requirements analysis and business process modeling – Unified Modeling Language, Business Process Model and Notation, and Event Storming. The first two have an established position in the market and a certain degree of formality, while the third offers an entirely new way of describing businesses.
Hi, my name is Patryk, I’m a software developer. I mostly use PHP with Laravel in my daily coding process. In my work I focus on how to solve problems and prepare code to be “change-proof”. For some time I’ve been discovering the benefits of using Event Storming and how it helps to create clean architecture in real projects with real problems. The first thing I’ve learned from using Event Storming is peeling off sticky notes – you wouldn’t believe how many ways there are to do this. I’ve set out on my journey as a speaker at conferences and meetups. This is one of the reasons why I’ve started this blog. I want to share my experience with others and also improve my writing skills. I have never been a fan of writing essays but you should always try new things. What do I do in my spare time? I play board games, read books, watch English Premier League, hike in mountains and learn new stuff.