I'm working on a project right now and it's my first project using BDD. Up till now, the user stories have proven themselves a very valuable weapon to understand requirements and to specify the solution in a comprehensive, easy to understand language.

My question is this: now that my user stories are complete, how do I design my solution? I understand that I derive behavior tests from my user stories, and I have to do UI design, but am I supposed to use good ol' UML? I'm under the impression that when using user stories, UML is left out; is this correct?

  • 3
    You might want to provide a link to a definition of BDD or even state outright what BDD is in your question! My first hit searching on Google is not Behavior Driven Development, if that's what you mean. Commented Nov 15, 2012 at 3:45
  • 1
    Yes, I'm referring to Behavior-Driven Development. :)
    – Léster
    Commented Nov 15, 2012 at 13:08
  • 1
    user stories show what to do , uml shows how you do it. long story short: you need both.
    – devnull
    Commented Nov 15, 2012 at 13:43

1 Answer 1


In general userstories are requirements from the customer point of view that most of the time say what to implement (= features) but not how to do it (design, workflow).

If you want to create a new app out of nothing (greenfield-soulution) in a agile/scrum-like manner out of existing userstories i would suggest this workflow:

  • So, with the user stories I build a map detailing order and interactions, then I make UML diagrams as needed, and then I start building my tests. Am I getting this right?
    – Léster
    Commented Nov 15, 2012 at 18:44
  • i am not shure if you realy need uml diagrams. most of my projects lived happyly without them.
    – k3b
    Commented Nov 18, 2012 at 13:03

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.