How does Behaviour Driven Development (BDD) work with Domain Driven Design (DDD)
===

My understanding of BDD is that one describes a system in user stories and then developers take those user stories and turn them into an application with the intention of adding real business value with every 'sprint' (period of software development). The result (as far as I can tell) is that **the domain model emerges from the user stories** throughout the development process. That is, after the first 'sprint' much of the domain model will not have been designed. 

My understanding of DDD is that software development continues with reference to a full domain model, albeit an evolving one. In BDD the model is expected to change, but it is nonetheless 'complete' at all times.

This seems to be a fundamental difference between the two approaches. How have people handled this?