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
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:
- bring the userstories into an implementition order to find out which story to implement first. Start with stories that have as least dependencies to other stories as possible and that have most business-value. For details see StoryMaps-The new user story backlog is a map
- implement the first userstory as nesteted bdd/tdd loops
2