From EventStorming to CoDDDing @ Techorama

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. During a live EventStorming software modelling session, we will show how you can leverage Domain-Driven Design patterns that will ultimately result in coding TDD (Test Driven Development) style!

github: https://github.com/joaoasrosa/xpirit-magazine-from-eventstorming-to-coddding

Transcript

1. View Slide

2. 2
   Strategic software delivery -
   Domain-Driven Design -
   Continuous Delivery -
   Socio-technical engineers -
   Collaborative modellers and
   facilitators
   

   View Slide

3. View Slide

4. View Slide

5. View Slide

6. View Slide

7. View Slide

8. View Slide

9. View Slide

10. View Slide

11. View Slide

12. View Slide

13. View Slide

14. View Slide

15. View Slide

16. View Slide

17. View Slide

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

    View Slide

19. View Slide

20. View Slide

21. View Slide

22. View Slide

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

    View Slide

24. View Slide

25. View Slide

26. View Slide

27. View Slide

28. View Slide

29. View Slide

30. View Slide

31. View Slide

32. View Slide

33. View Slide

34. View Slide

35. View Slide

36. View Slide

37. View Slide

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

    View Slide

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

    View Slide

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

    View Slide

41. View Slide

42. View Slide

43. View Slide

44. View Slide

45. 45
    https://domainlanguage.com
    

    View Slide

46. View Slide

47. View Slide

48. 48
    https://domainlanguage.com
    

    View Slide

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

    View Slide

50. View Slide

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

    View Slide

52. View Slide

53. View Slide

54. View Slide

55. 55
    https://domainlanguage.com
    

    View Slide

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
    

    View Slide

57. View Slide

58. View Slide

59. View Slide

60. View Slide