User Stories vs. Use Cases

We are currently in a “strange situation”. There are user stores and usage case scenarios, of which the latter can be divided into formal and informal use cases as well as summaries of use cases. What are they different and what are they the same?

Use cases, usage case scenarios and user stories document the description of how the product should be used. They differ on a continuum in terms of the amount of additional data required to create each one.

  • Formal use cases require the most effort. There is splendor in them and there are many things happening in them, but they describe all the combinations of how different people perform the same activity (or its variation).
  • Informal use cases are more or less the same – just that they are less formal. The challenge is to provide an adequate level of detail, without elements that lead to formal use cases that are to be used as a reminder.
  • Abstracts of use cases almost have no additional data, but they contain the same challenges – how much is this enough? what informal use cases, but to a greater extent.
  • User stories have the least additional data and provide the smallest context.

Use case scenarios are a slightly different case. Like the user story, the usage case scenario describes one path through a multi-track use case. It is worth combining the weakness of the use case (high amount of additional data) with the weakness of the user story (limited context), which in turn will give a fairly consistent and agile and helpful artifact.

More from my site

  • Managing Relationships Between Requirements Requirements management is an important element of the software development process. One of its elements is building and managing relationships between requirements. The most common is […]
  • Business Requirements vs System Requirements There is a lot of talk about the need to identify project goals, organization goals and the need to identify business and system requirements. All in order to better understand the […]
  • Mappings That Go Beyond Enterprise Architecture Some month ago in the post I wrote My Favorite Perspectives in Enterprise Architecture I presented a few diagrams describing enterprise architecture from different perspectives. The […]
  • Registration of Problems Identified During the Analysis I received an interesting question by e-mail: According to your knowledge, is there an object in EA that would be best suited for registering problems identified during business or […]
  • User Stories vs Requirements When writing any specification of requirements and the product register and sprint register, non-functional requirements should be included in this specification. While the user's […]

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top