Please enable JavaScript.
Coggle requires JavaScript to display documents.
What Stories Are Not - Coggle Diagram
What Stories Are Not
User Stories Aren’t IEEE 830
What is this?
Set of guidelines write by The Computer Society of the Institute of Electrical and Electronics Engineers
Last revision was in 1998
Usual topics
How to organize the requirements specification document
The role of prototyping
The characteristics of good requirements.
Disadvantages
tedious
error-prone,
time-consuming
Borring
Not flexible
With stories, an estimate is associated with each story right up front
A document written at this level frequently
make it impossible for a reader to grasp the big picture.
This type of requirements have sent many projects astray
Difference between user stories
The latter the cost of each requirement is not made visible
until all the requirements are written down
User Stories Aren’t Scenarios
What is it?
A scenario is a detailed description of a user’s interaction with a computer
The scenarios of interaction design are not the same as a scenario of a use case
an interaction design scenario is often larger or more encompassing than even one use case.
Difference between stories
Unlike use cases, actors in interaction design
scenarios are always people and never other systems.
Each actor in a scenario is pursuing one or more goals.
Scenarios contain much more detail and their scope usually covers multiple stories.
Scenarios Include
Actors
Goals and Objectives
Setting
Actions and events
User Stories Are Not Use Cases
Are commonly associated with the Unified Process
What are they
They are 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.
They may be written in unstructured text
or to conform with a structured template
Difference between user stories
scope
stories are kept smaller in scope because we place constraints on their size
Each story is not necessarily equivalent to a main success scenario
They differ in the level of completeness
Use cases are more prone to including details
of the user interface
Use cases are often permanent artifacts that continue to exist as long as the product is under active development or maintenance.
Are written for different purposes
use cases are generally written as the result of an analysis activity