Slide 1
Slide 1 text
@kenny_baas @joaoasrosa
From EventStorming
to CoDDDing
Slide 2
Slide 2 text
2
Strategic software delivery -
Domain-Driven Design -
Continuous Delivery -
Socio-technical engineers -
Collaborative modellers and
facilitators
@kenny_baas
baasie.com
@joaoasrosa
joaorosa.io
Slide 3
Slide 3 text
@kenny_baas @joaoasrosa
Slide 4
Slide 4 text
@kenny_baas @joaoasrosa
Slide 5
Slide 5 text
@kenny_baas @joaoasrosa
Using models for creating software
Slide 6
Slide 6 text
@kenny_baas @joaoasrosa
Slide 7
Slide 7 text
7
The fundamental horror of this anti-pattern
is that it's so contrary to the basic idea
of object-oriented designing;
which is to combine
data and process together.
- Martin Fowler
@kenny_baas @joaoasrosa
Slide 8
Slide 8 text
8
What's worse, many people think that
anemic objects are real objects,
and thus completely miss the point of what
object-oriented design is all about.
- Martin Fowler
@kenny_baas @joaoasrosa
Slide 9
Slide 9 text
9
@kenny_baas @joaoasrosa
Slide 10
Slide 10 text
10
@kenny_baas @joaoasrosa
Slide 11
Slide 11 text
@kenny_baas @joaoasrosa
Shared language created through conversations
between business people (specialists) and
software people which becomes
the ubiquitous language
Slide 12
Slide 12 text
12
@kenny_baas @joaoasrosa
Slide 13
Slide 13 text
13
@kenny_baas @joaoasrosa
Slide 14
Slide 14 text
@kenny_baas @joaoasrosa
Slide 15
Slide 15 text
@kenny_baas @joaoasrosa
Slide 16
Slide 16 text
@kenny_baas @joaoasrosa
Slide 17
Slide 17 text
17
“That shallowness of knowledge produces software that
does a basic job but lacks a deep connection to the
domain expert’s way of thinking.”
- Eric Evans
@kenny_baas @joaoasrosa
Slide 18
Slide 18 text
@kenny_baas @joaoasrosa
Focus on a language where we really
crisply concisely describe
the situation in the domain
Slide 19
Slide 19 text
@kenny_baas @joaoasrosa
Slide 20
Slide 20 text
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
@kenny_baas @joaoasrosa
Slide 21
Slide 21 text
@kenny_baas @joaoasrosa
Instead of one canonical language,
create multiple bounded languages
Slide 22
Slide 22 text
22
@kenny_baas @joaoasrosa
Slide 23
Slide 23 text
“A loosely coupled software architecture
and org structure to match” is a key
predictor of:
1. Continuous Delivery Performance
2. Ability to scale org and increase
performance linearly
Credits: Nick Tune
@kenny_baas @joaoasrosa
Slide 24
Slide 24 text
@kenny_baas @joaoasrosa
Focus on part of the software handling
complex business requirements
Slide 25
Slide 25 text
@kenny_baas @joaoasrosa Photo by Product School on Unsplash
Slide 26
Slide 26 text
26
@kenny_baas @joaoasrosa
Slide 27
Slide 27 text
27
It is not the domain experts knowledge
that goes to production, it is the
assumption of the developers
that goes to production
- Alberto Brandolini
@kenny_baas @joaoasrosa
Slide 28
Slide 28 text
@kenny_baas @joaoasrosa
Slide 29
Slide 29 text
29
Big Picture
Business process
modelling
Software
design
@kenny_baas @joaoasrosa
Slide 30
Slide 30 text
30
@kenny_baas @joaoasrosa
Credits: EventStorming.com
Slide 31
Slide 31 text
31
@kenny_baas @joaoasrosa
Slide 32
Slide 32 text
32
@kenny_baas @joaoasrosa
Slide 33
Slide 33 text
@kenny_baas @joaoasrosa
Slide 34
Slide 34 text
@kenny_baas @joaoasrosa
Slide 35
Slide 35 text
35
Source: https://medium.freecodecamp.org/coding-explained-in-25-profound-comics-8847ea03819c
@kenny_baas @joaoasrosa
Slide 36
Slide 36 text
36
Source: https://nl.pinterest.com/pin/550846598149452758/
@kenny_baas @joaoasrosa
Slide 37
Slide 37 text
37
Source:https://www.dw.com/en/maligned-ronaldo-statue-replaced-at-madeira-airport/a-44279114
@kenny_baas @joaoasrosa
Slide 38
Slide 38 text
38
@kenny_baas @joaoasrosa
Slide 39
Slide 39 text
39
A model is a simplified representation of a thing
or phenomenon that intentionally emphasizes
certain aspects while ignoring others.
Abstraction with a specific use in mind.
@kenny_baas @joaoasrosa
Slide 40
Slide 40 text
40
@kenny_baas @joaoasrosa
Slide 41
Slide 41 text
41
Business
@kenny_baas @joaoasrosa
Slide 42
Slide 42 text
42
Business
Architects
@kenny_baas @joaoasrosa
Slide 43
Slide 43 text
43
Business
Architects
Developers
@kenny_baas @joaoasrosa
Slide 44
Slide 44 text
44
Business
Architects
Developers
@kenny_baas @joaoasrosa
Slide 45
Slide 45 text
45
https://domainlanguage.com
@kenny_baas @joaoasrosa
Slide 46
Slide 46 text
@kenny_baas @joaoasrosa
Slide 47
Slide 47 text
47
Try at least to find three models,
even if you think you already found
the “right model”
@kenny_baas @joaoasrosa
Slide 48
Slide 48 text
48
https://domainlanguage.com
@kenny_baas @joaoasrosa
Slide 49
Slide 49 text
49
@kenny_baas @joaoasrosa
https://blog.ncrunch.net/post/london-tdd-vs-detroit-tdd.aspx
Slide 50
Slide 50 text
@kenny_baas @joaoasrosa
Slide 51
Slide 51 text
51
Source: https://nl.pinterest.com/pin/550846598149452758/
@kenny_baas @joaoasrosa
1. Write a coarse-grain acceptance test
a. Outside-in testing
2. Start with entrypoint of our model
3. Design-by-Coding
4. Assess if the models can easily evolve
to support other features
Slide 52
Slide 52 text
52
@kenny_baas @joaoasrosa
Slide 53
Slide 53 text
53
1. Protects business invariants
2. Design them small
3. Reference other by ID only
4. Update other aggregates
using eventual consistency
@kenny_baas @joaoasrosa
Slide 54
Slide 54 text
@kenny_baas @joaoasrosa
Slide 55
Slide 55 text
55
https://domainlanguage.com
@kenny_baas @joaoasrosa
Slide 56
Slide 56 text
56
Essence of Domain-Driven Design
➔ 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
Slide 57
Slide 57 text
57
Software Development is
a learning process, working code is a
side effect.
- Alberto Brandolini
@kenny_baas @joaoasrosa
Slide 58
Slide 58 text
58
Serious software development is
the practice of symmathesy.
“Sym” = together, “mathesy” = learning.
- Jessica Kerr
@kenny_baas @joaoasrosa
Slide 59
Slide 59 text
@kenny_baas @joaoasrosa
Virtual Domain-Driven Design
https://virtualddd.com
Slide 60
Slide 60 text
#CatTax
@kenny_baas @joaoasrosa
https://github.com/xebia/CoDDDing-labs