title: Is behaviour driven development about design or analysis?
body: <p>The more I read about BDD and how it is supposed to be improved TDD the more confusing it all seems to me. I've found quotes from expert that say it's about design, but also from other experts that say it's about analysis.</p>
  
  <p>The way I currently see it is this:</p>
  
  <p>1) analysis: BDD</p>
  
  <p>from <a href="http://en.wikipedia.org/wiki/Object-oriented_analysis_and_design" rel="nofollow noreferrer">wikipedia</a></p>
  
  <blockquote>
    <p>The result of object-oriented analysis
    is a description of what the system is
    functionally required to do, in the
    form of a conceptual model.</p>
  </blockquote>
  
  <p>So after BDD we have the requirements (stories and the scenarios). But I'm not sure about the conceptual model part.</p>
  
  <p>2) design: eg with tools like resonsibility driven design using CRC cards</p>
  
  <p>3) code: coding the design, optionally use testing (like what they say about TDD done wrong, which I also find useful)</p>
  
  <p>Am I wrong in how I see this? I'm having trouble seeing the forest through the trees at the moment.</p>