Slide 1

Slide 1 text

Bartek Słota @bartekslota Context Mapping The Missing Link in Your Organization’s Technical Strategy

Slide 2

Slide 2 text

417 * State of DevOps 2022 *

Slide 3

Slide 3 text

* State of DevOps 2022

Slide 4

Slide 4 text

„Teams that focus on building software with loosely- coupled architectures are in a better position to perform strongly across stability, reliability, and throughput.”* * State of DevOps 2022

Slide 5

Slide 5 text

Example

Slide 6

Slide 6 text

Example

Slide 7

Slide 7 text

Example

Slide 8

Slide 8 text

Example

Slide 9

Slide 9 text

Sub-domains

Slide 10

Slide 10 text

Bounded contexts

Slide 11

Slide 11 text

Organization architecture

Slide 12

Slide 12 text

Architecture

Slide 13

Slide 13 text

Architecture

Slide 14

Slide 14 text

Architecture

Slide 15

Slide 15 text

Architecture

Slide 16

Slide 16 text

Business processes

Slide 17

Slide 17 text

Business processes

Slide 18

Slide 18 text

No content

Slide 19

Slide 19 text

Architecture

Slide 20

Slide 20 text

Architecture

Slide 21

Slide 21 text

Architecture

Slide 22

Slide 22 text

Business process

Slide 23

Slide 23 text

Business process

Slide 24

Slide 24 text

No content

Slide 25

Slide 25 text

Dependencies between teams

Slide 26

Slide 26 text

Dependencies between teams

Slide 27

Slide 27 text

Upstream-Downstream

Slide 28

Slide 28 text

Relations between contexts Eric Evans, Domain-Driven Design: Tackling Complexity in the Heart of Software

Slide 29

Slide 29 text

Open-Host Service

Slide 30

Slide 30 text

Published Language

Slide 31

Slide 31 text

Conformist

Slide 32

Slide 32 text

Anti-Corruption Layer

Slide 33

Slide 33 text

Shared Kernel

Slide 34

Slide 34 text

Partnership

Slide 35

Slide 35 text

Customer-Supplier

Slide 36

Slide 36 text

Separate Ways

Slide 37

Slide 37 text

Exemplary context map

Slide 38

Slide 38 text

Architecture - once again

Slide 39

Slide 39 text

Architecture - once again

Slide 40

Slide 40 text

Architecture - once again

Slide 41

Slide 41 text

Architecture - once again

Slide 42

Slide 42 text

Business process - once again

Slide 43

Slide 43 text

Business process - once again

Slide 44

Slide 44 text

The art of compromise Eric Evans, Domain-Driven Design: Tackling Complexity in the Heart of Software

Slide 45

Slide 45 text

System of systems

Slide 46

Slide 46 text

Team topologies

Slide 47

Slide 47 text

„The design... is almost never the best possible, the prevailing system concept may need to change. Therefore, fl exibility of organization is important to e ff ective design.” Mel Conway