# Applying Domain-Driven Design in Practice
Parts I and II gave you the tools. Part III is about using them on real projects: turning the
analysis into concrete design choices, keeping those choices up to date as things change, and
running a workshop that gets everyone to a shared model quickly.

10. [Chapter 10](/ch10) connects strategy to tactics with rules of thumb: which logic pattern, architecture and testing approach to use, and how wide to draw the first boundaries.
11. [Chapter 11](/ch11) covers what to do when the business, the organization, your understanding or the system's size changes, and how to migrate between patterns.
12. [Chapter 12](/ch12) walks through EventStorming, a sticky-note workshop for exploring a business process and building a shared language.

> **Coverage note:** these notes currently cover Chapters 10–12 of Part III.

## [10. Design Heuristics](/ch10)
- [What a heuristic is](/ch10#what-a-heuristic-is)
- [Sizing bounded contexts](/ch10#sizing-bounded-contexts)
- [Picking a business logic pattern](/ch10#picking-a-business-logic-pattern)
- [Picking an architecture](/ch10#picking-an-architecture)
- [Picking a testing strategy](/ch10#picking-a-testing-strategy)
- [The whole decision tree](/ch10#the-whole-decision-tree)

## [11. Evolving Design Decisions](/ch11)
- [When subdomains change type](/ch11#when-subdomains-change-type)
- [Migrating between patterns](/ch11#migrating-between-patterns)
- [Organizational change](/ch11#organizational-change)
- [Domain knowledge](/ch11#domain-knowledge)
- [Growth](/ch11#growth)

## [12. EventStorming](/ch12)
- [What it is](/ch12#what-it-is)
- [Who and what you need](/ch12#who-and-what-you-need)
- [The ten steps](/ch12#the-ten-steps)
- [When to run one](/ch12#when-to-run-one)
- [Facilitation tips](/ch12#facilitation-tips)
