Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I’m trying to explore Behavior Driven Design and Domain Driven Design. I’m getting that written specifications drive the tests in BDD, but also that business logic can be encapsulated using the specification pattern for re-use in domain objects and repositories, etc.
Are these basically the same concept just used in different ways, used in conjunction together, or am I completely confusing the concepts?
Please shed some light, if possible.
BDD or context specification is a style of writing unit tests in a test first manner. DDD is a term coined by Eric Evans that basically re-introduces appropriate design patterns when you are constructing software systems. If you are wanting to do test first development in a context specification style then see this link. From a BDD standpoint there are lots of resources out there if you really want to design your software systems using the patterns described in Eric Evans’ book you will find some good resources here