Please enable JavaScript.

Coggle requires JavaScript to display documents.

Domain Driven Design (Ubiquitous Language (WHY? (To avoid misunderstanding…

- - - - Noun
      - Verb
- - - - To identify events and commands
      - To explore complex business domain and understand how it works
    - - Invite the right people: people with questions and people with answers (mix of curiosity and wisdom)
      - Provide unlimited modelling space (a wall and sticky notes)
      - explore the domain
        
        start with domain/business EVENTS
        
        Events always have a name in its past-tense form:
        OrderWasAccepted, OrderHasShipped (orange)
        
        find what causes the event
        
        user action?
        
        represent it as a COMMAND
        
        Commands always have a name its imperative form:
        CreateOrder, ShipOrder (blue)
        
        A command supports a single Use Case and targets a single Business Object
        
        external system? (purple)
        
        another event? (orange)
        
        Event is something meaningful happened in the domain
        
        look for AGGREGATES
        
        An Aggregate is the portion of the system that receives commands and decides whether to execute them or not, thus producing a domain event
      - (optionally) Invite Facilitator who can lead the meeting