Behaviour Driven Development (BDD) is a term that was coined by Dan North in 2006. It came about as a response to a very specific problem – teaching developers how to think about testing their code. It incorporates the ubiquitous language idea from Eric Evan’s book Domain-Driven Design, and this evolved into a technique used by the whole team to collaboratively specify how the finished system should behave. While both approaches focus on collaboration, DDD focuses on a shared model for building software and BDD focusses on specifying the behaviour of the system. So what can we learn from both our techniques? Join us in this session were Seb Rose, Steve Tooke and Matt Wynne will discuss with us how we can improve modelling with BDD. We will bust popular BDD myths and talk about their favourite collaboration techniques.
It’s like 10,000 streams when what you need is a queue – Chris Simon
🎶🎵 A new dev team adopted E-D-A Got head of line blocking, on their very first day Isn't it ironic, don't you think 🎶🎵 The last few years have seen widespread adoption of Event-Driven Architecture, supported by DDD practices...
