Scenario (computing)

From Wiki @ Karl Jones dot com
Revision as of 11:17, 19 April 2016 by Karl Jones (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

In computing, a scenario is a narrative of foreseeable interactions of user roles (sometimes known 'actors') and the technical system, for example a website.

Description

A scenario has a goal, which is usually functional. A scenario describes one way that a system is or is envisaged to be used in the context of activity in a defined time-frame.

The time-frame for a scenario could be (for example) a single transaction; a business operation; a day or other period; or the whole operational life of a system.

Similarly the scope of a scenario could be (for example) a single system or piece of equipment; an equipped team or department; or an entire organization.

Persona (user experience)

Scenarios often use persona -- imaginary users representing typical expected visitors.

Persona as typically used as actors in scenarios. The act of creating scenarios then become a kind of story-telling about the actors using the technology.

Use cases

Scenarios are often defined in use cases.

A use case is a list of steps, typically defining interactions between a role (sometimes called an actor) and a system, to achieve a goal.

Use in software design

Increasingly, scenarios are used directly to define the wanted behavior of software: replacing or supplementing traditional functional requirements.

Use in system development

Scenarios are frequently used as part of the system development process.

They are typically produced by usability or marketing specialists, often working in concert with end users and developers. Scenarios are written in plain language, with minimal technical details, so that stakeholders (designers, usability specialists, programmers, engineers, managers, marketing specialists, etc.) can have a common example which can focus their discussions.

See also

External Links