<< A stimulus as a model element | Runtime Tracing >>

Stimuli can have either names or signatures

Test RealTime - User Guide

Different types of stimuli can be used to model different flows of control.

Type

Shape

Description

Procedure Call or
Nested Flow of
Control

Models either a call to an operation or a call to a nested
flow of control. When calling a nested flow of control,
the system waits for the nested flow of control to
complete before continuing with the outer flow.

Asynchronous Flow of
Control

Models an asynchronous stimulus between two objects.
The source object sends the stimulus and immediately
continues with the next step.

Return from a
Procedure Call

Models a return from a call to a procedure. This type of
stimulus can be omitted from diagrams because it is
assumed that every call has a return.

Naming Conventions

Stimuli can have either names or signatures.

Type

Example

Description

Name

// Get the Password

A name identifies only the name of the stimulus.
Simple names are often used in diagrams
developed during analysis because the stimuli are
identified by their responsibilities and not by their
operations. One convention uses double slashes
(//) to indicate that the stimulus name is not
associated with an operation.

Signature

getPassword(String)

When an operation is assigned to a stimulus, you
can display the operation signature to identify the
name of the operation and its parameters.
Signatures are often used in diagrams developed
during design because the provide the detail that
developers need when they code the design.

Actions

An action is represented as shown below:

The action box displays the name of the action.

The action is linked to its source file. In the UML/SD Viewer, click an action to open
the Text Editor at the corresponding line in the source code.