User Story - User Stories and Use Cases

User Stories and Use Cases

While both user stories and use cases serve the purpose to capture specific user requirements in terms of interactions between the user and the system, there are major differences between them.

User Stories Use Cases
  • Provide a small-scale and easy-to-use presentation of information. Are generally formulated in the everyday language of the user and contain little detail, thus remaining open to interpretation. They should help the reader understand what the software should accomplish.
  • Must be accompanied by Acceptance Testing procedures (acceptance criteria) for clarification of behavior where stories appear ambiguous.
  • Describe a process and its steps in detail, and may be worded in terms of a formal model. A use case is intended to provide sufficient detail for it to be understood on its own. A use case has been described as “a generalized description of a set of interactions between the system and one or more actors, where an actor is either a user or another system”.
  • May be delivered in a stand-alone document.

Read more about this topic:  User Story

Famous quotes containing the words user, stories and/or cases:

    “A worker may be the hammer’s master, but the hammer still prevails. A tool knows exactly how it is meant to be handled, while the user of the tool can only have an approximate idea.”
    —Milan Kundera (b. 1929)

    “I found that they knew but little of the history of their race, and could be entertained by stories about their ancestors as readily as any way.”
    —Henry David Thoreau (1817–1862)

    “There are some cases ... in which the sense of injury breeds—not the will to inflict injuries and climb over them as a ladder, but—a hatred of all injury.”
    —George Eliot [Mary Ann (or Marian)