Category Archives: Use Cases – Driven Requirements

Storyboards, Scenarios, Design Personas

“I almost always begin design by talking with users. Initially, my goal is simply to collect people’s stories. I believe that the stories people tell about what they do and how they do it contain information vital to designing good … Continue reading

Posted in Conceptual Design, Use Cases - Driven Requirements | Tagged , , | Leave a comment

Disadvantages of use cases and scenarios

Poor identification of structure and flow Geometric and temporal information hard to describe Unsystematic craft Time-consuming to generate Limited software tool support Handling unforeseen combinations of abnormal events Require the co-existence of prototypes Still poor integration with established methods Difficult to generalise from scenarios … Continue reading

Posted in Uncategorized, Use Cases - Driven Requirements | Tagged , , | Leave a comment

Advantages of use cases and scenarios

Places a requirement’s statement “in context” Acquiring requirements by exploring “what if” questions Scoping required system by exploring system actions Validating requirements by exploring alternative courses Provide a basis for system and acceptance testing Reduce system complexity Excellent for communicating/agreeing … Continue reading

Posted in Use Cases - Driven Requirements | Tagged , | Leave a comment

Use cases and Scenarions

A Use case is a “description of a set of actions, including variants, that a system performs that yields an observable result of value to a particular actor (Jacobson et al. 2000) A Scenario is ” a specific sequence of … Continue reading

Posted in Use Cases - Driven Requirements | Tagged , | Leave a comment