DITA XML Websites
A Scenario is the InformationDesign variation on what system designers have called a UseCase.
Use Cases were exhaustive lists of the many things that might be done with a system to help the system designers WalkThrough? all the possible uses and make sure the system was thoroughly debugged.
A Scenario attempts to prioritize the most important uses that are likely, and these for the most important types of user, as collected in the abstract user concept of the Persona.
It is still a collection of tasks or goals that need to be accomplished with a system being designed.
It helps identify the WorkFlow for all possible paths in the InteractionDesign.
A scenario is a ... set of one-or-more typical interaction dialogs between the users of a system (people or other systems) and a proposed system that is about to be developed. Scenarios are developed during the analysis phase of system development to assist in understanding business events, objects and interactions. Scenarios document specific transaction sequences, transformations, interfaces and information exchange. They represent cases that should be included in the Software QualityAssurance? Test Plan, and may be used for end user training after the system is completed. UseCase scenarios facilitate communication between the people who request a system, analysts, developers and testers. They are used to validate understanding, and to identify normal and special use situations. Scenarios clarify an evolving agreement between requesters and development teams.
BT - UseCase
RT - Scenario, WalkThrough?, WorkFlow, InformationDesign, InteractionDesign
Up to CmsGlossary.