
ETSI
NOTE 2: As address is more a predefined type name than a distinct type with its own properties, the root type of
an address type and all of its derivatives are the same, as the root type was, if the type was defined
with a name different from address.
static parameterization: form of parameterization, in which actual parameters are independent of run-time events;
i.e. known at compile time or in case of module parameters are known by the start of the test suite execution
NOTE 1: A static parameter is to be known from the test suite specification, (including imported definitions), or the
test system is aware of its value before execution time.
NOTE 2: All types are known at compile time, i.e. are statically bound.
strong typing: strict enforcement of type compatibility by type name equivalence with no exceptions
System Under Test (SUT): See ISO/IEC-9646-1 [6].
template: TTCN-3 templates are specific data structures for testing; used to either transmit a set of distinct values or to
check whether a set of received values matches the template specification
template parameterization: ability to pass a template as an actual parameter into a parameterized object via a template
parameter
NOTE 1: This actual template parameter is added to the specification of that object and may complete it.
NOTE 2: Values passed to template formal parameters are considered to be in-line templates (see clause 15.4).
test behaviour: (or behaviour) test case or a function started on a test component when executing an execute or a
start component statement and all functions and altsteps called recursively
NOTE: During a test case execution each test components have its own behaviour and hence several test
behaviour may run concurrently in the test system (i.e. a test case can be seen as a collection of test
behaviours).
test case: See ISO/IEC-9646-1 [6].
test case error: See ISO/IEC-9646-1 [6].
test suite: set of TTCN-3 modules that contains a completely defined set of test cases, optionally supplemented with
one or more TTCN-3 control parts
test system: See ISO/IEC-9646-1 [6].
test system interface: test component that provides a mapping of the ports available in the (abstract) TTCN-3 test
system to those offered by the SUT
timer parameterization: ability to pass a timer as an actual parameter into a parameterized object via a timer
parameter
NOTE: This actual timer parameter is added to the specification of that object and may complete it.
type compatibility: language feature that allows to use values, expressions or templates of a given type as actual values
of another type (e.g. at assignments, as actual parameters at calling a function, referencing a template, etc. or as a return
value of a function)
unqualified name: the unqualified name of a TTCN-3 element is its name without any qualification
user-defined type: type that is defined by subtyping of a basic type or declaring a structured type
NOTE: User-defined types are referenced by their identifiers (names).
value notation: notation by which an identifier is associated with a given value or range of a particular type
NOTE: Values may be constants or variables.
value parameterization: ability to pass a value as an actual parameter into a parameterized object via a value
parameter