This part settles the language everything else refers back to.

• How the domain, the model and the running software relate to one another
• The ubiquitous language as one vocabulary for the business and the team
• Tactical building blocks: entity, value object, aggregate and service
• Factory, repository, domain event and modules as a grouping mechanism

The longest part of the curriculum: how knowledge gets out of people and into the model.

• What domain experts contribute and how you involve them
• Interview techniques for business relationships and rules
• Field observation and apprenticing as quiet ways of gathering knowledge
• Collaborative modeling with EventStorming, Domain Storytelling and user story mapping

Here the model becomes source code without losing the business vocabulary.

• Cohesion and coupling as the yardstick for the design
• SOLID and the Law of Demeter applied to domain classes
• Modeling and naming domain classes
• Adding technically motivated building blocks without diluting the domain model

This part gives the domain model its place in the overall system.

• Ports and adapters, also known as hexagonal architecture
• Layered architecture and dependency inversion
• CQRS: running read paths and write paths separately
• Where DDD ends and BDD begins

From here on it is about large systems, where a single model no longer holds.

• Telling the problem space and the solution space apart
• Classifying subdomains as core, supporting or generic
• The bounded context as the boundary inside which the language stays unambiguous
• Conway's law, and what organisational boundaries have to do with model boundaries

To close, you describe how the contexts you cut deal with each other.

• Context mapping patterns from open-host service and anticorruption layer to shared kernel and separate ways
• Customer-supplier, conformist, partnership and published language compared
• Naming team dependencies as mutual dependency, upstream-downstream or free
• Domain events as the channel between bounded contexts

The curriculum sets no fixed time for this part; it is picked up according to the interests of the group.

• Event sourcing and a deeper look at CQRS
• Team topologies, Wardley mapping and data mesh
• The bounded context canvas and the tools and materials approach
• Artificial intelligence in the context of DDD