Markdown Editor
Editor öffnen

Kit Domain-Driven Design

Domäne modellieren: Event Storming, Core Domain Chart, Bounded Contexts, Sprache, Nachrichtenflüsse, Kontext- und Teamkarten, CQRS.

11 Vorlagen in 4 Schritten, in der Reihenfolge der Nutzung. Öffnen Sie eine Vorlage im Editor, füllen Sie sie aus und exportieren Sie sie als PDF, DOCX oder HTML.

Schritt 1

Discovery-Phase

  1. EventStorming Workshop Summary Template

    Standard

    Record an EventStorming session: events timeline, commands, actors, policies, read models, hotspots, context candidates

    EventStorming (Alberto Brandolini)

  2. Core Domain Chart Template

    Standard

    Core, supporting and generic classification: differentiation and complexity scores, quadrant chart, findings, expected movement, decisions

    DDD Crew Core Domain Charts; Domain-Driven Design (Evans)

  3. Wardley Map Template

    Vollständig

    Strategic question, users and needs, value chain, evolution assessment, quadrant map and map source, movement, inertia, options and gameplay, doctrine, decision, signposts

    Wardley Maps (Simon Wardley, concept names only)
Schritt 2

Domänenmodellierung

  1. Bounded Context Canvas Template (DDD Crew)

    Standard

    Design one DDD bounded context: purpose, strategic classification, roles, inbound/outbound messages, language, rules, metrics

    Bounded Context Canvas V5 (DDD Crew); Domain-Driven Design (Evans)

  2. Ubiquitous Language Glossary Template (DDD)

    Kompakt

    Glossary of domain terms per bounded context with synonyms to avoid, examples, code names, owners and change rules

    Domain-Driven Design (Evans)

  3. Domain Message Flow Template

    Standard

    One scenario as numbered commands, events and queries between contexts: notation, sequence diagram, message register, checks, failure paths

    DDD Crew Domain Message Flow Modelling
Schritt 3

Entwurf

  1. DDD Context Map Template

    Standard

    Map bounded contexts and their DDD relationships (ACL, OHS, conformist, shared kernel), team ties and evolution plan

    Domain-Driven Design context mapping patterns (Evans)

  2. Team Interaction Map Template (Team Topologies)

    Standard

    Team types, interaction modes, cognitive load, as-is and target team diagrams, findings and a dated evolution plan

    Team Topologies, 2nd edition (2025), names only

  3. Team API Template (Team Topologies)

    Standard

    A team's public interface: type, mission, owned services, versioning, channels, ways of working, roadmap, interaction modes

    Team Topologies Team API
Schritt 4

Umsetzung

  1. Event Sourcing and CQRS Design Template

    Standard

    Event-sourced service design: fit check, event catalogue, versioning and upcasting, store, projections, idempotency, crypto-shredding

    Event Sourcing (Fowler 2005); CQRS Documents (Young 2010); GDPR Art. 17 examples

  2. Microservice Specification Template (Service Canvas)

    Standard

    Service canvas: bounded context, owner, APIs and events, data owned, dependencies, SLOs, scaling, config, deploy, observability

    Microservice Canvas (Richardson); OpenAPI 3.2.1; AsyncAPI 3.1.0; RFC 9745, RFC 8594