User stories and use case

Question

What is the difference between user scenarios and target use case?

Answer 1

Use cases are more like contracts , and Use Stories is a planning tool. Consequently, Use Cases usually survive User Stories, as they (should) serve as documentation that specifically reflects the embedded system.

User stories are recorded by the client / participant / client / user. User stories are not very detailed and relatively open to interpretation.

Use cases are more formal in structure and are often written by someone from the team - a requirements engineer / product manager. They are often more detailed, break down the interaction into separate steps, and clearly define preconditions and post-contests, such as failure conditions and success conditions.

While one use case can cover many scenarios - success and failure; validation errors; Helper applications and extensions — The user story is more limited in scope, usually describing one scenario.

See also User_story # Comparing_with_use_cases on Wikipedia , as well as the chapter “What to do with no cases” in the book Using Custom Stories .

Finally, according to Allistair Cockburn ...

User history is synonymous with the “function” used in the 1990s, a marker for what needs to be built, fine-grained enough to fit into modern iteration / sprint periods.

A use case provides a contextual view of what needs to be created in order to unite an organization.

Answer 2

"The user story is an example of use, because the gazelle is a gazebo." - cockburn

User stories (as opposed to requirements) are brief statements of intent that describe what the system should do for a certain user. This is the main method used by flexible teams to understand and meet customer requirements. This is certainly a convenient design, and small user stories help us manage the extreme instrumentalism that characterizes flexible development.

Using cases is a traditional way of expressing system behavior in complex systems. Use cases are the primary means of presenting UML requirements. They are well described there, as well as in various texts on this subject. Use cases can be used for both specification and analysis. They are especially useful when the system of interest, in turn, consists of other subsystems.

Books I recommend:

• Software Requirements (Dean Leffingwell)
• Writing Effective Use Cases (Alistair Cockburn)