IT training across Europe - tecnovy makes you future-ready.

Switch to English
E-Learning

iSAQB® DDD - Domain-Driven Design

In the meeting it is a contract, in the source code an Agreement, in the database a Policy. Whether those mean the same thing, nobody can say for certain. Domain-driven design starts exactly there: one business vocabulary that stays identical in conversation, in the model and in the code. In the tecnovy DDD training you model entities, value objects and aggregates with it, and decide where one bounded context ends and the next begins.
iSAQB Accredited Training PartnerAttendance certificate4.8/5 on ProvenExpert

What this module delivers.

The ubiquitous language is the reference point everything in the DDD training hangs on: aggregates, bounded contexts, context mapping. You draw it out with domain experts and cut a model developers and the business share.

How the training runs

Method
Team modelling exercises on one example domain
Outcome
30 credit points: 20 methodical, 10 communicative, no course exam

Dates & booking

Choose a date that fits

5 dates

  • EUREuro
  • USDUS Dollar
  • CHFSwiss Franc

Sessions with this symbol offer up to 25% group discount. Click “Details & Registration” to learn more.

25–27 Aug 2026CEST
Tue–Thu 09:00–17:00
Online training Group Discount Guaranteed
Time zone CEST
Language German
Trainer Matthias Bohlen
Seats Only 4 left
15% Monthly Pick

2,200 €−330 €1,870 €

excl. VAT
22–24 Sep 2026CEST
Tue–Thu 09:00–17:00
Online training Sold out
Time zone CEST
Language English
Trainer Matthias Bohlen

2,200 €

No longer bookable
13–15 Oct 2026CEST
Tue–Thu 09:00–17:00
Germany Group Discount
City Cologne
Language German
Trainer Matthias Bohlen
Seats 5+ seats
10% Earlybird Discount

2,450 €−245 €2,205 €

excl. VAT
20–22 Oct 2026CEST
Tue–Thu 09:00–17:00
Switzerland Group Discount Guaranteed
City Zürich
Language English
Trainer Matthias Bohlen
Seats Only 2 left

3,053 €

excl. VAT
24–26 Nov 2026CET
Tue–Thu 09:00–17:00
Germany Group Discount
City Munich
Language English
Trainer Matthias Bohlen
Seats 5+ seats
10% Earlybird Discount

2,450 €−245 €2,205 €

excl. VAT

Fit

Who this module is designed for

Typical roles

  • You model business concepts with domain experts and carry them over into code.
  • You break a grown domain model down into clearly separated sub-models.
  • You own how two teams couple their models to each other.

Prerequisites

No prerequisites

You can start right away. Helpful: practical experience in object-oriented software development, experience modelling object-oriented architectures, knowledge of agile methods such as Scrum, Kanban or XP.

Consider instead FLEX Tests a module cut against quality goals, levels of isolation and coupling in source code, build artefacts and network protocol, where DDD builds the domain model itself.

Curriculum

CPSA® DDD Course in Detail

Curriculum 2023.2 splits DDD into seven parts. Six of them carry the 1020 minutes of teaching and practice and run from the ubiquitous language through knowledge crunching and implementation to context mapping. The seventh part collects optional deep dives that are picked up depending on the group.

01Domain, model, and ubiquitous language

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
02Knowledge Crunching: The path to the model

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
03From the model to the implementation

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
04The model in the application architecture

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
05Strategic Design 1: Cutting and distinguishing models from one another

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
06Strategic Design 2: Context Mapping

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
07Optional: Related Topics

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
Official syllabus(external link)

Outcome

What you will be able to do afterwards

  1. 01

    You model a domain using entities, value objects, aggregates and domain events.

  2. 02

    You establish a ubiquitous language and keep it identical in the model and in the code.

  3. 03

    You elicit domain knowledge through interviews, field observation and EventStorming workshops.

  4. 04

    You test domain classes against cohesion, coupling, SOLID and the Law of Demeter.

  5. 05

    You place the domain model inside a ports-and-adapters architecture and separate read paths from write paths.

  6. 06

    You cut large models into bounded contexts and classify subdomains as core, supporting or generic.

  7. 07

    You shape relationships between contexts using anticorruption layers, open-host services and published languages.

Credit points toward CPSA-A

Methodical competence
20
Technical competence
0
Communicative competence
10

30 of 70 points toward CPSA-A admission

Credit point rules Guide →

Trainers

Matthias Bohlen

Matthias Bohlen

iSAQB®

Why tecnovy

What you get on top with us

01

iSAQB® Accredited Provider

We are an officially accredited Training Provider of the International Software Architecture Qualification Board.

02

Certificate Showroom

Get your certificate of participation and, if you have one, add your exam certificate from E-Learning. Fully automated, beautifully designed. Just for you, only at tecnovy.

03

No Slideshow, Hands-On!

Promised: no PowerPoint marathon. We work in groups, tie theory to practice, and you get real project examples from our experienced trainers plus the exchange with like-minded people.

04

Attend Twice, Pay Once

You are welcome to attend the training online again within a year as a refresher.

05

Learn from Experts

We always guarantee you the use of didactically and methodically first-class qualified trainers who draw their knowledge from training experience as well as professional practical and project experience.

06

Flexible Date Change

If you are not able to attend the course, you can rebook your training free of charge up to one week before the start of the training.

Experiences

What participants say

The contact with Mr. Topuzoglu was very appreciative, friendly and courteous. The entire planning of the training went smoothly. This is not a matter of course in the current climate and also speaks in favor of tecnovy. The Domain Driven Design training, which I organized for myself and my colleagues, was conducted remotely with excellent organization and structure. Likewise, Matthias Bohlen (our training manager) repeatedly incorporated exciting elements for interactive collaboration. All in all, it was a successful three days and we were able to take away many new impressions. We are also planning to conduct the next training with tecnovy.
Dominik G. Principal Consultant | esentri AG

FAQs

Frequently asked questions

01Do I need CPSA-F to attend the tecnovy DDD training?
No. The iSAQB curriculum for the DDD module lists prior knowledge of object-oriented development and modelling as its prerequisites, not a certification. For the later CPSA-A certification, CPSA-F is mandatory.
02Is there a DDD examination?
No. There is no examination for the DDD module. The tecnovy DDD training earns you 30 credit points and a certificate of participation; the assessment comes later on the path to CPSA-A certification, and it covers all modules together.
03How many credit points does DDD carry?
The tecnovy DDD training carries 30 credit points: 20 methodical and 10 communicative. DDD awards no technical points, which matters for your planning: CPSA-A admission requires 70 points in total and at least 10 in each of the three areas of competence. The iSAQB may re-evaluate point allocations every 12 months; these figures are as of August 2026.
04How does the CPSA-A certification work?
CPSA-A certification consists of a written assignment. Two examiners recognised by the iSAQB assess it, and you then defend it in discussion with them. You can take it in German or English, and tecnovy is glad to help if you have questions about the process.
05How long is the DDD training?
The tecnovy DDD training runs for three days. The iSAQB curriculum recommends at least three days and prescribes 1020 minutes of teaching and practice for accredited courses, which is exactly 17 hours. Its largest single block is the 240 minutes on knowledge crunching, the work with domain experts.
06What is the difference between DDD and FLEX?
DDD builds a domain model: ubiquitous language, tactical building blocks, bounded contexts and context mapping patterns fill the module's 1020 minutes of teaching and practice. FLEX cuts technically and assesses module boundaries against quality goals and against coupling in source code, build artefacts and network protocol; bounded contexts are only one of several decomposition approaches there. The points differ too: DDD awards 20 methodical and 10 communicative, FLEX 10 methodical and 20 technical.
07Is the DDD training tied to a programming language or a framework?
No, the tecnovy DDD training assumes no particular language and no framework. The iSAQB curriculum treats DDD as a design method: modelling, tactical building blocks and the cut into bounded contexts, not the library that implements them. The exercises work object-oriented, and tool training is not part of the module.
08Are CQRS and event sourcing part of the DDD training?
In the tecnovy DDD training CQRS is a fixed part of the curriculum, while event sourcing is optional. Curriculum 2023.2 covers CQRS in part four, alongside ports and adapters and the layered architecture. Event sourcing, team topologies, data mesh and the tools and materials approach sit in the optional seventh part, which the trainer picks up depending on the group.
09Do I get the flipcharts from the DDD training?
Yes. Whatever the modelling exercises in the tecnovy DDD training produce on flipcharts and modelling walls reaches you as a photo protocol after the seminar.
DDDDDD - Domain-Driven Design

Ready for the next step?

Choose a public date or plan the course for your team.

Feedback Form
What should we improve?

Tell us what we can do better next time.

Success
Error

© Copyright 2026, tecnovy GmbH, All Rights Reserved