Your SlideShare is downloading. ×
DDD eXchange 2010: Gojko Adzic on DDD, TDD, BDD
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Saving this for later?

Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime - even offline.

Text the download link to your phone

Standard text messaging rates apply

DDD eXchange 2010: Gojko Adzic on DDD, TDD, BDD

2,965
views

Published on

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, …

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.

Published in: Technology, Education

1 Comment
2 Likes
Statistics
Notes
  • For more details and podcasts from the DDD eXchange 2010 go to http://skillsmatter.com/event-details/podcast/ddd-exchange-2010
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
No Downloads
Views
Total Views
2,965
On Slideshare
0
From Embeds
0
Number of Embeds
6
Actions
Shares
0
Downloads
42
Comments
1
Likes
2
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. The three amigos @gojkoadzic
  • 2.  
  • 3.  
  • 4.  
  • 5.  
  • 6.  
  • 7. Effective models require a bigger picture … but KISS and YAGNI say don't... avoid BDUF
  • 8. … feature injection gives us right-size chunks
  • 9. Things can blow up during modelling...
    • … but domain experts often can't decide on scope
  • 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
  • 13. Domain experts don't really understand low level stuff
    • .... but where do we stop working with them?
  • 14. ...BDD outside in boundaries ...TDD emergent design to flesh out details
  • 15. Emergent design leads to too much inconsistency
    • … especially on big teams and across boundaries
  • 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
  • 19. We need to capture our models and what they mean
    • … but code is too low level and UML gets old very quickly...
  • 20. … live specification can explain our models and dynamics
  • 21. Emergent design advocates constant refactoring
    • … but in larger teams, refactoring cross cutting concerns can cause a ton of issues
  • 22. … bounded contexts help us coordinate changes
  • 23. Recipe for success
    • Use strategic design to decide what to build
    • Use feature injection to get the scope
    • Evolve a ubiquitous language with specification workshops
    • Establish guidelines with collaborative high-level domain design
    • TDD design below, respecting DDD guidelines
    • Use context mapping to facilitate cross team collaboration
  • 24. Questions?
    • http://gojko.net
    • @gojkoadzic
    • [email_address]