Skip to content

How to link User stories, DDD and BDD

June 17, 2013

User stories express (business) needs through a conversation and a confirmation, stored on a card

The conversation allows to the team to understand what the (business)  domain is, naturally defining a common language: this helps provide a software design that reflects the business domain: DDD, Domain Design Driven.

The confirmation could include (lots of) examples that validate business needs. These acceptance criteria will be needed by the PO for approval and for building a customer test suite (UAT): BDD, Behaviour Driven Development.


In a nutshell, when we discuss user stories (requirements), we build a language and contexts. Instead of reinventing the wheel, we match our design of the solution and the tests to this language and contexts – simple!


This picture below aims to summarise “interaction” between User stories,  DDD and BBD.

Agile US DDD BDD 4


From → Agile, Architecture

  1. Hi Christophe,

    You did a great summary linking that 3 concepts together.
    By the way, here are the slides on DDD from my talk at the Lausanne Java User Group last week :



Trackbacks & Pingbacks

  1. Agile Project Plan Template | christophelecoent

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: