Use Case and/vs User Stories RRS feed

  • General discussion

  • Hello,

    I tend to use Mind Mapping software to catch all the user stories, it's helping me to visualize the stories and sort them all in one place.

    Now, when I'm conceptualizing the model of the domain during analysis I tend to Use-Case diagrams to visualize the relations between some of these stories to put everything together and build up a high level view to get a clue about the flow and relations in the system, as well as catching the entities in the model.

    Just to be clear, I don't use detailed Use-Cases or Use-Case descriptions but merely visualizing the stories in a Use-Case diagram.

    For me it works pretty good, however, I wonder whether developers that do use Agile and User Stories still use Use-Case diagrams ? if not, why ? what's your thoughts/opinion about it ?

    Eyal (http://shilony.net), Regards.
    • Edited by Eyal Solnik Tuesday, November 8, 2011 4:57 PM
    Tuesday, November 8, 2011 4:04 PM

All replies

  • I tend to only use Give-When-Then style SpecFlow tests now. I've found that Use Case tend to focus on specifics and provide a narrow view of the requirements, i.e they are very prescriptive. Whereas I've found GWT tends to talk more about the What rather than the How. I've found the team tend to get more involved with GWT whereas they tend to just blindly start implementing Use Cases. Obviously that doesn't mean that you cannot foster the same experience with Use Cases, it's just my experience.


    Tuesday, November 15, 2011 2:16 PM
  • @pkr2000, yes this seems like a pure TDD approach and User Stories are complementary to this and overall to the Agile paradigm, what I want to know is whether developers or teams use both User Stories and Use Cases Diagrams to draw the stories then go directly to high level view of a class diagram rather than using CRC cards ?

    Eyal (http://shilony.net), Regards.
    • Edited by Eyal Solnik Wednesday, November 16, 2011 3:37 AM
    Wednesday, November 16, 2011 3:37 AM
  • I find that it's very difficult to explain all functionality in terms of user stories or use case.

    I like to also have a descriptive spec.

    A recent view I was writing, I was given a bunch of use cases.

    They proved almost useless in interpreting the requirement.

    (Admittedly quite a fiddly view.)

    Anyhow, I had to spend several sessions with business analysts before the requirement was finalised.

    Wednesday, November 16, 2011 8:53 AM
  • Hi Eyal,

    Agile is itself agile.


    "The programmer, like the poet, works only slightly removed from pure thought-stuff. He builds his castles in the air, from air, creating by exertion of the imagination." - Fred Brooks
    Wednesday, November 16, 2011 9:31 AM
  • @Andy ONeill, I see, but that's the thing with User Stories they are written progressively and are relatively small, they shouldn't describe everything and that's the beauty of it at least in my opinion. ;)

    @Derek Smyth, Yes I know that's why it's so nice yet I like to know how it's working for others and what are the tools they use to analyse the requirements. :)

    Eyal (http://shilony.net), Regards.
    • Edited by Eyal Solnik Wednesday, November 16, 2011 10:15 AM
    Wednesday, November 16, 2011 10:15 AM
  • As I said, I tend to only use GWT now. I discourage the use of Use Cases/diagrams as they tend to be lead to misuse. Not to say I ban them, if they convery something in a good way then I'd be happy with it. I'm not prescriptive with my requirements or my tools.
    Wednesday, November 16, 2011 1:03 PM