UseCase

The term Use Case comes from software engineering, especially from research into the ObjectOriented UnifiedModelingLanguage (UML) and the HumanComputerInterface.

Use cases lead to detailed requirements, a functional specification, testing metrics, and validation of the model.

Called a scenario by an InformationArchitect, the use case describes a task or goal to be accomplished by the user, or actor, or persona.

It also includes the specific sequence of actions needed to achieve the goal, plus alternative sequences, discovered by UserResearch, documenting exactly how the user reacts to the model - see InteractionDesign.

The collection of use cases describes all the possible ways (good and bad, right and wrong) of using a system.

The results can be documented as WorkFlow with a FlowChart?, BubbleChart?, or DataFlowDiagram?.

RT - Scenario, Usability, UserExperience

Use Cases Tutorial

Up to CmsGlossary.