Domain Driven Design is often misunderstood as something that advocates a lot of upfront design and at odds with the evolutionary design principles of test driven development. In this presentation, Gojko Adzic will talk about reconciling the two approaches and getting the best of both worlds, and how DDD ideas play a crucial role in behaviour driven development.

1. The three amigos @gojkoadzic

7. Effective models require a bigger picture … but KISS and YAGNI say don't... avoid BDUF

8. … feature injection gives us right-size chunks

10. ...collaborative specifications cause things to blow up quicker

11. DDD advocates a ubiquitous language... … but it's very hard to ensure consistency

12. … evolve with specification workshops, enforce with tests

14. ...BDD outside in boundaries ...TDD emergent design to flesh out details

16. … use DDD building block patterns as guidelines

17. Effective iterative design requires effective regression testing … but unit tests are bound to a particular design

18. … business oriented specifications do not change

20. … live specification can explain our models and dynamics

22. … bounded contexts help us coordinate changes