2 Why We Need Model-Based Testing

Appendices 327
sandbox. Atest harness in which normally observable actions are made controllable,
so a normally reactive system can be tested as a closed system.
scenario. A collection of related runs (perhaps just one). A scenario can be expressed
by a scenario model program.
scenario control. Limiting analysis and testing to particular runs of interest.
self-loop. Atransition where there is no change of state; the current state and next
state are the same. So called because of its appearance in a state transition diagram.
sequence. An ordered collection of (possibly repeating) elements. In the NModel
library, sequence is a compound value.
set. An unordered collection of distinct elements. In the NModel library, set is a
compound value.
scenario FSM. Ascenario model program expressed as an FSM.
scenario model program. Amodel program that defines a scenario, usually intended
for scenario control. Contrast to contract model program.
shared action.Anaction whose action symbol appears in the action vocabulary of
two or more programs. Under composition, model programs synchronize steps for
shared actions.
side effect. Any effect of evaluating an expression or executing a statement, other
than computing a value. Updating variables, allocating storage, or performing input
or output are examples of side effects.
signature. The name and parameters of a method, or the action symbol and parameters
of an action.
simple name. In C#, a name not including the namespace. A simple name need not
be unique. Contrast to fully qualified name.
simulation. Amodel-based analysis technique, where runs of a model program
are observed. Each run of a model program is a simulation of some behavior
of the implementation. Simulation can include run-time checks. Sometimes called
animation. Compare to exploration.
slice. A collection of features.
sliding window. Aprotocol that uses a pool of resources (the “window”) whose
contents change (“slide”) as time progresses.
source program. In C#, the collection of source code files (perhaps just one) that
are compiled to produce an assembly.
specification. A description of what a program, component, or system is supposed
to do. A specification should be a complete description of behavior that describes
more free ebooks download links at:
http://www.ebook-x.com