From EventStorming to CoDDDing - Techorama NL 2019

From EventStorming to CoDDDing - Techorama NL 2019

To really understand what our users need so that we can build the right thing, we want to have a first-hand experience of 'real-life stories' before we model and create our software. To quote Alberto Brandolini "it is not the domain expert's knowledge that goes into production, it is the developer's assumption of that knowledge that goes into production". EventStorming is a visual technique that minimizes assumptions by engaging in collaborative deliberate learning across different disciplines. This helps to solve complex business problems in the most effective way.

Although the learning of the domain helps us to understand the domain better, EventStorming can be quite an overwhelming experience. Developers can be left with the question of how to turn a few stickies on a wall into working code.

Join us in this talk in which we show the basic principles of EventStorming. We will cover the different forms of EventStorming and in which situation they best can be applied. And, we will show how you can leverage DDD (Domain-Driven Design) patterns in an EventStorming software modeling session that will ultimately result in coding TDD (Test Driven Development) style!

Bf5494be4dd7a8e936cd964374d86eb0?s=128

João Rosa

October 02, 2019
Tweet

Transcript

  1. None
  2. 2 Strategic software delivery - Domain-Driven Design - Continuous Delivery

    - Socio-technical engineers - Collaborative modellers and facilitators
  3. None
  4. None
  5. None
  6. None
  7. 7

  8. 8

  9. 9

  10. 10

  11. None
  12. 12

  13. 13

  14. None
  15. None
  16. None
  17. 17

  18. 18 https://lizkeogh.com/2015/09/09/on-epiphany-and-apophany/

  19. None
  20. 20

  21. None
  22. None
  23. http://tednellen.blogspot.com/2013/04/language-is-fluid.html

  24. None
  25. 25

  26. None
  27. None
  28. None
  29. 29

  30. 30

  31. None
  32. 32

  33. 33

  34. 34

  35. 35

  36. None
  37. None
  38. 38 Source: https://medium.freecodecamp.org/coding-explained-in-25-profound-comics-8847ea03819c

  39. 39 Source: https://nl.pinterest.com/pin/550846598149452758/

  40. 40 Source:https://www.dw.com/en/maligned-ronaldo-statue-replaced-at-madeira-airport/a-44279114

  41. 41

  42. 42

  43. 43

  44. 44

  45. 45 https://domainlanguage.com

  46. None
  47. 47

  48. 48 https://domainlanguage.com

  49. 49 https://blog.ncrunch.net/post/london-tdd-vs-detroit-tdd.aspx

  50. None
  51. 51 Source: https://nl.pinterest.com/pin/550846598149452758/

  52. 52

  53. 53

  54. None
  55. 55 https://domainlanguage.com

  56. 56 ➔ Using models for creating software ➔ Focus on

    part of the software handling complex business requirements ➔ Focus on a language where we really crisply concisely describe the situation in the domain ➔ Shared language created through conversations between business people (specialists) and software people which becomes the ubiquitous language ➔ Instead of one canonical language, create multiple bounded languages
  57. 57

  58. 58

  59. None
  60. None