Scenario

We can script a sequence of one or more planned stimuli and responses or conditions of interest to drive and observe the behavior of a System.

A Scenario can be as simple as just a single stimulus, such as an injected event, that springs the System into action.

We can also use a Scenario to simulate the responses of System components that have not yet been implemented (or for other reasons are not available) in the System.

The scenario Stimulus below represents an asynchronous service invocation by the UI domain which is not present in the System on the EVMAN domain which is available.

UI >|| EVMAN : Stop request -> ASLEV <S1-3>

The Scenario will just issue the Stop request event on the right side directed at an instance of ASLEV in the EVMAN domain. As far as the EVMAN domain is concerned, the UI is, in fact, even though it is only simulated by the Scenario.

Identifiers

1. Name

Attributes

Name

A descriptive name such as One bank one shaft L to 3 or maybe just 1B1S_L_to_3

Type: Scenario Name -> Name

Description

A general or detailed explanation of what the Scenario is doing such as:

Issue a stop request to a Cabin on the lobby level with its Door closed to go to the 3rd Floor

Type: Description -> String