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

From EventStorming to CoDDDing @ DDD Taiwan

From EventStorming to CoDDDing @ DDD Taiwan

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". Visual collaboration are tools that minimize 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, visual collaboration tools like EventStorming and Example Mapping can be quite an overwhelming experience. Developers can be left with the question of how to turn a few stickies or index cards into working code.

Join us in this talk where we will leverage Eric Evans model exploration whirlpool. During a live EventStorming and Example Mapping software modelling session, we will show how with that outcome you can leverage Responsibility Mapping to propose a model with Domain-Driven Design patterns. It will ultimately result in coding by doing outside in Test Driven Development! You will leave with the knowledge to go from visual collaborate modelling to coding while refining your ubiquitous language.

Bf5494be4dd7a8e936cd964374d86eb0?s=128

João Rosa

November 27, 2020
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. None
  19. None
  20. http://tednellen.blogspot.com/2013/04/language-is-fluid.html

  21. None
  22. 22

  23. None
  24. None
  25. None
  26. 26

  27. 27

  28. None
  29. 29

  30. 30

  31. 31

  32. 32

  33. None
  34. None
  35. 35 Source: https://medium.freecodecamp.org/coding-explained-in-25-profound-comics-8847ea03819c

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

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

  38. 38

  39. 39

  40. 40

  41. 41 Business

  42. 42 Business Architects

  43. 43 Business Architects Developers

  44. 44 Business Architects Developers

  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