Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Crunching 'Real-Life Stories' with DDD Event Storming and Combining it with BDD Techniques @ P3X

Crunching 'Real-Life Stories' with DDD Event Storming and Combining it with BDD Techniques @ P3X

To really understand what your users will need, you want to have a first-hand experience from 'real-life stories' before you can model and create your software. While both the DDD and BDD techniques emphasis on ‘real-life stories’ by doing collaborative deliberate learning, they both focus on different goals. DDD focuses more on creating bounded contexts in which a single model is created, BDD focuses more on different scenarios and can create executable specifications as an outcome.

By doing EventStorming and using techniques from BDD, such as Example Mapping or Feature Mapping, you can create more insights. You can simultaneously create a model and executable specifications for your user needs. This way, you can write software and tests which matches the shared understanding of the user, creating a ubiquitous language. Value will be shipped at a faster pace.

In this session, Kenny will explain how to do Process EventStorming. He will use Example Mapping, or Feature Mapping to get more insights into his process. The outcome can drive your Software Modelling EventStorming and create Executable Specifications

Kenny Baas-Schwegler

November 09, 2018
Tweet

More Decks by Kenny Baas-Schwegler

Other Decks in Programming

Transcript

  1. @kenny_baas Kenny Baas-Schwegler Software Consultant - EventStormer Domain Driven Design

    Behaviour Driven Development Continuous Delivery @kenny_baas Baasie.com xebia.com/blog/author/kbaas/
  2. @kenny_baas It is not the domain experts knowledge that goes

    to production, it is the assumption of the developers that goes to production - Alberto Brandolini
  3. @kenny_baas To communicate effectively, the code must be based on

    the same language used to write the requirements - the same language that the developers speak with each other and with domain experts - Eric Evans
  4. @kenny_baas We all know or should know that language is

    fluid, liquid, subject to the whims of the people. Language evolves, as it should. Because language changes to accommodate new users, the older users resist and complain. http://tednellen.blogspot.com/2013/04/language-is-fluid.html
  5. @kenny_baas Every tool has its blind spots. That blind spot

    might as well be your million dollar mistake.
  6. @kenny_baas Serious software development is the practice of symmathesy. “Sym”

    = together, “mathesy” = learning. - Jessica Kerr