Artifact: Scenario
A scenario represents, at some level of abstraction, an interaction among elements of interest.
A scenario can be used to represent a flow of services realizing a coherent set of requirements (e.g. use case), depict the execution of elements, or as a test vector.

A scenario is a partially ordered flow of messages among a set of elements at some level of abstraction. It is a common way to represent a path through a use case, and the elaboration of that path as object analysis and design proceeds. Indeed, the continuous execution policy encouraged by the Harmony process means that these scenarios are continually being elaborated and re-executed as the system analysis and design efforts proceed. Additionally, a scenario can be easily converted into a test case and executed as part of a test suite.

A scenario may be drawn to represent a desired behavior - and this is how "specification scenarios" are used to detail use cases. They may also be created automatically from the execution of the system or some portion thereof. These "execution scenarios" can then be compared - either manually or automatically - to the specification scenarios to ensure the behavior of the model is as desired.

Notation
UML sequence diagrams are the most common notation, but communication and timing diagrams are available alternatives.
Key Considerations
Over use of sequence diagram operators (opt, alt, etc) is discouraged because it complicates the scenario by (essentially) representing multiple scenarios on a single diagram. It is recommended to limit nesting of operators to no more than 2 levels and add multiple scenarios separately when needed.
Relationships
More Information
Checklists
Guidelines