doc/TTCN3_Toolset_for_TITAN/FS/EPTF CLL for TTCN-3 toolset with TITAN, Function Specification.adoc - titan/titan.Libraries.CLL - Git at Google

 ---
 Author: Gábor Szalai
 Version: 155 17-CNL 113 512, Rev. C
 Date: 2009-03-05

 ---
 = EPTF CLL for TTCN-3 toolset with TITAN, Function Specification
 :author: Gábor Szalai
 :revnumber: 155 17-CNL 113 512, Rev. C
 :revdate: 2009-03-05
 :toc:

 == How to Read This Document

 This is the Function Specification for the Ericsson Performance Test Framework (TitanSim), Core Load Library (CLL). TitanSim CLL is developed for the TTCN-3 Toolset with TITAN ‎<<_2, [2]>>. This document should be read together the User's Guide <<_3, ‎[3]>>.

 == Scope

 This document is to specify the content and functionality of the TitanSim CLL.

 == Recommended Way of Reading

 The readers are supposed to get familiar with the scope and goals of the project from <<_5, ‎[5]>> and also the glossary therein. The next step is to read the Quick Study <<_6, ‎[6]>> and its glossary. Finally they should get familiar with the list of acronyms and the glossary in the Terminology section.

 = General

 This document specifies the functionality of the TitanSim CLL. Currently it contains a short overview of features and reference to their documentations in Section <<functional-specification, Functional Specification>>. Additionally, consult the TitanSim Reference Guide pages ‎<<_4, [4]>> for the TitanSim CLL.

 [[functional-specification]]
 = Functional Specification

 The TitanSim CLL consists of a number of features listed in this section. The detailed documentation for each feature can be found under the delivered directory _EPTF_Core_Library_CNL113512/doc_ with the following naming convention: __EPTF_CLL_<FeatureName>_FD__ for Function Description and __EPTF_CLL_<FeatureName>_UG__ for User Guide, respectively.

 == Base

 The EPTF Base component is a fundamental component that handles common tasks (e.g. managing cleanup functions, graceful termination, etc.) that should be implemented in all EPTF components. All EPTF components should extend this component (i.e. explicitly) or a component that extends this component (i.e. implicitly).

 See <<_7, ‎[7]>> for more details.

 == Central Scheduling

 The EPTF Central Scheduling feature makes it possible to write load test cases using similar methodology than in function test. Load testing means executing several traffic cases in parallel.

 See <<_30, ‎[30]>> for more details.

 == Common

 The EPTF Common feature contains common type and function definitions used by other EPTF features.

 See ‎<<_8, [8]>> for more details.

 == Execution Control

 The aim of the EPTF `ExecCtrl` feature is to provide common framework for configuring and handling multiple Load Generators in one test scenario.

 See ‎<<_9, [9]>> for more details.

 [[free_busy_queue]]
 == `FreeBusyQueue`

 The EPTF Free Busy Queue feature provides dynamic memory allocation for the TTCN-3 language in an efficient way.

 See <<_10, ‎[10]>> for more details.

 == `HashMap`

 The EPTF `HashMap` feature provides access to a well-tested, industry standard GCC `HashMap` implementation. `HashMap` is a hashed associate container that associates object of type key with object of type data.

 See <<_11, ‎[11]>> for more details.

 == `HostAdmin`

 The aim of the EPTF Host Admin feature is to provide processor and memory usage measurement for a given host it is started on. Remote measurements are also possible using the feature by subscribing to EPTF Variables (see <<variable, Variable>>).

 See ‎<<_12, [12]>> for more details.

 == `LGenBase`

 The EPTF `LGenBase` feature is the basis for all load generators (`LGens`) components of TitanSim, i.e. this feature should be used to write efficient load generators.

 See ‎<<_13, [13]>> for more details.

 == `LoadRegulator`

 The EPTF Load Regulator feature makes it possible to regulate the CPS of a load generator based on the load of the SUT.

 See <<_14, ‎[14]>> for more details.

 == `Logging`

 The aim of the EPTF Logging feature is, to use the library provided logging framework for event-class based per-PTC log control. The feature manages the logging database, defines default log classes and functions without the extension of GUI.

 See <<_15, ‎[15]>> for more details.

 == `NameService`

 The EPTF Name Service feature makes it possible to register and query component references by name.

 See <<_17, ‎[18]>> for more details.

 == `PTCDeployment`

 The EPTF `PTCDeployment` implements the functionality that allows components to select a host, where new PTCs can be deployed according to specified tasks (called roles) in the PTCD component.

 See ‎<<_18, [18]>> for more details.

 == `RandomNArray`

 The aim of the EPTF Random N Array feature is to provide dynamic memory allocation for the TTCN-3 language in an efficient way. The EPTF Random N Array feature makes it possible to manage lists over `record of' data structures easily using index-arithmetics.

 See ‎<<_32, [32]>> for more details.

 == `RedBlackTree`

 The EPTF Red Black Tree feature is a self-balancing binary search tree. It can be used to store indexes into an associated array, similar to the EPTF Free Busy Queue (see <<free_busy_queue, `FreeBusyQueue`>>).

 See ‎<<_19, [19]>> for more details.

 == `Rendezvous`

 The aim of the EPTF Rendezvous feature is, to make a _Rendezvous service_. `Rendezvous` service provides a generic solution for synchronization among/between various entities either locally and remotely.

 See <<_29, ‎[29]>> for more details.

 == `RingBuffer`

 The EPTF Ring Buffer feature provides a general ring buffer (or circular buffer) implementation. Ring buffer is a http://en.wikipedia.org/wiki/Data_structure[data structure] that uses a single, fixed-size http://en.wikipedia.org/wiki/Buffer_%28computer_science%29[buffer] as if it were connected end-to-end. This structure can be easily used for buffering http://en.wikipedia.org/wiki/Data_stream[data streams].

 See ‎<<_20, [20]>> for more details.

 == `Scheduler`

 The EPTF Scheduler feature makes it possible to schedule events (actions) that should happen at a given time measured from the start of the component or relative to the schedule of the event. The Scheduler is efficient, it uses only two TTCN-3 timers to implement scheduling.

 See <<_21, ‎[21]>> for more details.

 == `Semaphore`

 The EPTF Semaphore feature makes it possible to implement blocking functions and to perform synchronization in TTCN-3.

 See ‎[23] for more details.

 == `StatCapture`

 The aim of the EPTF Statistics Capture feature is to group Statistics into capture groups and to print capture group contents regularly at sampling intervals to predefined capture files.

 See ‎<<_23, [23]>> for more details.

 == `StatHandler`

 `StatHandler` feature makes it possible to collect global, aggregated statistics via the existing EPTF Variable interface.

 See ‎<<_33, [33]>> for more details.

 == `StatMeasure`

 The aim of the EPTF Statistics Measure feature is to create Statistics (stand-alone or belonging to a Variable) and update their value when required.

 See ‎<<_24, [24]>> for more details.

 == `StatReplay`

 The aim of the EPTF Statistics Replay feature is to display a given Statistics from a given capture group on the chart in a slider window in the GUI.

 See ‎<<_25, [25]>> for more details.

 == Time Profile Editor

 The EPTF CLL Time Profile Editor is an application which allows the user to create and edit time profiles used by the EPTF CLL Execution Control <<_9, ‎[9]>> component.

 See ‎<<_31, [31]>> for more details.

 == `Transport`

 The EPTF Transport Control feature makes it possible to

 * Route the incoming and outgoing messages between the components
 * Store messages and information in a `FreeBusyQueue`
 * Handle the UDP and IPL4 testports dynamically.

 See ‎<<_28, [28]>> for more details.

 == `UIHandler`

 With the EPTF `UIHandler` feature, the user can manage display and manipulation of subscribed Variables on the runtime GUI. Apart from this, it is even possible to change the runtime GUI. The user can add, remove, enable or disable GUI elements.

 See ‎<<_26, [26]>> for more details.

 [[variable]]
 == `Variable`

 The EPTF Variable feature makes it possible to access component variables in remote components and to create automatically calculated Variables triggered by the refresh of other Variables.

 See ‎<<_27, [27]>> for more details.

 = Terminology

 *TitanSim Application Library:* +
 It is that part of the TitanSim software that is (at-least partially) project dependent. (I.e., which is protocol-, and/or application-dependent). Any TitanSim application library is to be supplied and supported _either_ by the customer project _only_; or by the customer project _together_ with the TCC organization. Any TitanSim application library development is to be funded by the ordering projects.

 *TitanSim Core (Load) Library(CLL):* +
 It is that part of the TitanSim software that is totally project independent. (I.e., which is not protocol-, or application-dependent). The TitanSim CLL is to be supplied and supported by the TCC organization. Any TitanSim CLL development is to be funded centrally by Ericsson

 *Application Library (AppLib):* +
 It is that part of the TitanSim software that is although protocol, or application-area dependent, but can be _reused_ across many TitanSim applications. `AppLibs` are dependent on the CLL.

 *Control Logic:* +
 It is that part of the TitanSim software that is specific to a particular TitanSim application program. It is usually not directly reusable and is built upon the CLL and several `AppLibs`.

 *Entities:* +
 They are "things/objects" that are simulated by the `LGen`. Such "things" are usually the "users", "calls", "servers", "terminations", or anything whose external behavior is to be simulated by the `LGen`. Usually an LGen simulates more than one entity.

 *Entity context:* +
 It is an index-able generic data record describing an entity. It serves as a hub connecting all information related to the entity together by referring the respective associated _behavior contexts_ and _FSM contexts_ via their indices. The entity contexts are identified via their indices with respect to the entity context database stored in the `v_LGenBase_entities` component variable.

 *Behavior context:* +
 It is an index-able (set of) data record(s) that stores data and state information of a given entity with respect to a given _behavior type._ Storage for behavior contexts is to be provided by the respective `AppLibs`.

 *Behavior type:* +
 It is a concept for collectively referring a set of _behavior contexts, FSM inputs, test steps,_ and functions realizing methods conforming to given function signatures prescribed by the `LGenBase` feature. Behavior types are to be declared dynamically during run-time to the `LGenBase` by the component-type initialization function of some `AppLib`. Usually an AppLib product has only one behavior type, but it is permitted for `AppLibs` to declare more than one behavior types, if necessary. Behavior types are identified by their indices determined by the order of declaration and the declarations are stored in `v_LGenBase_behaviorTypes`

 *Entity type:* +
 It is a named list of references to declared _behavior types_. As such, it declares what type of behavior contexts are available on entities of this type.

 *Entity group:* +
 A group of entities with homogenous entity type. The indices of the entities of the group make a continuous interval that does not overlap with the indices range of any other entity group.

 *Test step:* +
 Test steps are functions whose signature conforms to a given function type. They _must_ not contain TTCN-3 statement with blocking semantics.

 *FSM table:* +
 It is a formal specification of the communication rules of Finite State Machines. These indexable records are stored in `v_LGenBase_fsmTables`. FSM tables realizing _traffic cases_ must obey certain rules.

 *Traffic case type:* +
 It is a prototype used as an input for instantiating traffic case instances on a specific entity group. It defines what _FSM table_ to use, what _entity type_ must be used by the _entity group_ where the _traffic case_ is to be deployed.

 *Traffic case:* +
 It is a behavior, defined by an FSM table, that is executed on a given entity group. All entities of the entity group participate in executing the the traffic case. An entity group may have more than one concurrent traffic cases.

 *Scenario:* +
 It is a collection of traffic cases deployed on an entity group.

 *TitanSim Variables:* +
 They are enhanced component variables that make it possible to access the values of other Variables in remote components.

 *TitanSim Statistics:* +
 They are Statistics of TitanSim Variables. Possible Statistics are among others minimum, maximum, mean, standard deviation, etc. and also the content of a Variable can be a Statistics itself. The values of such Statistics are automatically and periodically updated in the background.

 *Generated load of a traffic case:* +
 It is defined as the _aggregate_ load generated by _traffic case instances_ of the given _traffic case_

 *Generated load of the traffic mix:* +
 It is defined as the _aggregate_ load generated by the individual _traffic cases_ of the given _traffic mix_

 *Programming style, event driven:* +
 A programming style not-so "natural" for most people. It is atypical for function tests. It focuses on one or more threads of execution, however, _not_ in a sequential manner. Rather it defines states for execution where the program code wait for an event (any event) to happen, then based on the event it executes a state transition to a new state and continues to wait for another event. The flow of events _cannot be_ understood easily just by reading the source code sequentially, therefore it is less natural for many programmer.

 *Programming style, procedural:* +
 It is typical for functions tests. It focuses on a single thread of execution in a sequential manner. The "natural" programming style for most programmers, since the flow of events can be understood easily just by reading the source code sequentially.

 *Traffic case instance:* +
 It is a specific execution instance of the behavior (message sequence) defined by the _traffic case_

 *Traffic generator PTC:* +
 It is a PTC that actually generate the messages toward the SUT during the performance test campaign

 *Traffic group:* +
 It is a named instance of a _traffic mix_. Such traffic group may have _TitanSim Parameters_ that are common to each traffic cases within the group that realize the _traffic mix_. Such traffic group may have (potentially aggregate) _ TitanSim Statistics_ that provides (potentially aggregate) information about the execution of the _traffic cases_ within the group. Note, however, that the _traffic cases_ may have individual parameters and statistics, as well.

 *Traffic mix:* +
 It is a specific combination of _traffic cases_ that are to be executed concurrently by TitanSim. Each traffic case has a corresponding traffic weight assigned. The traffic mix has a load-level target that is an aggregate of the individual load-levels of the individual _traffic cases_, whose load levels are the result of the execution of their _traffic case instances_

 = Abbreviations

 API:: Application Programming Interface

 CLL:: Core Load Library

 TitanSim:: Ericsson Load Test Framework, formerly TITAN Load Test Framework

 IUT:: Implementation Under Test

 LGen:: Load Generator PTC

 PTC:: Parallel Test Component

 SUT:: System Under Test

 TCC:: Test Competence Center

 TLTF:: See TitanSim

 TTCN-3:: Testing and Test Control Notation version 3 ‎<<_1, [1]>>.

 = References

 See the introduction of Section ‎3 for the location of feature documentations in the delivery VOB.

 [[_1]]
 [1] ETSI ES 201 873-1 v3.2.1 (2007-02) +
 The Testing and Test Control Notation version 3. Part 1: Core Language

 [[_2]]
 [2] User Guide for the TITAN TTCN-3 Test Executor

 [[_3]]
 [3] TitanSim CLL for TTCN-3 toolset with TITAN, User Guide

 [[_4]]
 [4] TitanSim CLL for TTCN-3 toolset with TITAN +
 http://ttcn.ericsson.se/products/libraries.shtml[Reference Guide]

 [[_5]]
 [5] Project Specification for TitanSim R2

 [[_6]]
 [6] Quick Study on TITANSim R2 development

 [[_7]]
 [7] EPTF CLL Base, Function Description

 [[_8]]
 [8] EPTF CLL Common, Function Description

 [[_9]]
 [9] EPTF CLL ExecCtrl, Function Description

 [[_10]]
 [10] EPTF CLL Free Busy Queue, Function Description

 [[_11]]
 [11] EPTF CLL HashMap, Function Description

 [[_12]]
 [12] EPTF HostAdmin, Function Description

 [[_13]]
 [13] EPTF CLL LGenBase, Function Description

 [[_14]]
 [14] EPTF CLL LoadRegulator, Function Description

 [[_15]]
 [15] EPTF CLL Logging, Function Description

 [[_16]]
 [16] EPTF CLL LoggingUI, Function Description

 [[_17]]
 [17] EPTF CLL NameService, Function Description

 [[_18]]
 [18] EPTF CLL PTCDeployment, Function Description

 [[_19]]
 [19] EPTF CLL RedBlackTree, Function Description

 [[_20]]
 [20] EPTF CLL RingBuffer, Function Description

 [[_21]]
 [21] EPTF CLL Scheduler, Function Description

 [[_22]]
 [22] EPTF CLL Semaphore, Function Description

 [[_23]]
 [23] EPTF CLL StatCapture, Function Description

 [[_24]]
 [24] EPTF CLL StatMeasure, Function Description

 [[_25]]
 [25] EPTF CLL StatReplay, Function Description

 [[_26]]
 [26] EPTF CLL UIHandler, Function Description

 [[_27]]
 [27] EPTF CLL Variable, Function Description

 [[_28]]
 [28] EPTF CLL Transport, Function Description

 [[_29]]
 [29] EPTF CLL Rendezvous, Function Description

 [[_30]]
 [30] EPTF CLL Central Scheduling, Function Description

 [[_31]]
 [31] EPTF CLL Time Profile Editor, Function Description

 [[_32]]
 [32] EPTF CLL Random N Array, Function Description

 [[_33]]
 [33] EPTF CLL Stat Handler, Function Description
	---
	Author: Gábor Szalai
	Version: 155 17-CNL 113 512, Rev. C
	Date: 2009-03-05

	---
	= EPTF CLL for TTCN-3 toolset with TITAN, Function Specification
	:author: Gábor Szalai
	:revnumber: 155 17-CNL 113 512, Rev. C
	:revdate: 2009-03-05
	:toc:

	== How to Read This Document

	This is the Function Specification for the Ericsson Performance Test Framework (TitanSim), Core Load Library (CLL). TitanSim CLL is developed for the TTCN-3 Toolset with TITAN ‎<<_2, [2]>>. This document should be read together the User's Guide <<_3, ‎[3]>>.

	== Scope

	This document is to specify the content and functionality of the TitanSim CLL.

	== Recommended Way of Reading

	The readers are supposed to get familiar with the scope and goals of the project from <<_5, ‎[5]>> and also the glossary therein. The next step is to read the Quick Study <<_6, ‎[6]>> and its glossary. Finally they should get familiar with the list of acronyms and the glossary in the Terminology section.

	= General

	This document specifies the functionality of the TitanSim CLL. Currently it contains a short overview of features and reference to their documentations in Section <<functional-specification, Functional Specification>>. Additionally, consult the TitanSim Reference Guide pages ‎<<_4, [4]>> for the TitanSim CLL.

	[[functional-specification]]
	= Functional Specification

	The TitanSim CLL consists of a number of features listed in this section. The detailed documentation for each feature can be found under the delivered directory _EPTF_Core_Library_CNL113512/doc_ with the following naming convention: __EPTF_CLL_<FeatureName>_FD__ for Function Description and __EPTF_CLL_<FeatureName>_UG__ for User Guide, respectively.

	== Base

	The EPTF Base component is a fundamental component that handles common tasks (e.g. managing cleanup functions, graceful termination, etc.) that should be implemented in all EPTF components. All EPTF components should extend this component (i.e. explicitly) or a component that extends this component (i.e. implicitly).

	See <<_7, ‎[7]>> for more details.

	== Central Scheduling

	The EPTF Central Scheduling feature makes it possible to write load test cases using similar methodology than in function test. Load testing means executing several traffic cases in parallel.

	See <<_30, ‎[30]>> for more details.

	== Common

	The EPTF Common feature contains common type and function definitions used by other EPTF features.

	See ‎<<_8, [8]>> for more details.

	== Execution Control

	The aim of the EPTF `ExecCtrl` feature is to provide common framework for configuring and handling multiple Load Generators in one test scenario.

	See ‎<<_9, [9]>> for more details.

	[[free_busy_queue]]
	== `FreeBusyQueue`

	The EPTF Free Busy Queue feature provides dynamic memory allocation for the TTCN-3 language in an efficient way.

	See <<_10, ‎[10]>> for more details.

	== `HashMap`

	The EPTF `HashMap` feature provides access to a well-tested, industry standard GCC `HashMap` implementation. `HashMap` is a hashed associate container that associates object of type key with object of type data.

	See <<_11, ‎[11]>> for more details.

	== `HostAdmin`

	The aim of the EPTF Host Admin feature is to provide processor and memory usage measurement for a given host it is started on. Remote measurements are also possible using the feature by subscribing to EPTF Variables (see <<variable, Variable>>).

	See ‎<<_12, [12]>> for more details.

	== `LGenBase`

	The EPTF `LGenBase` feature is the basis for all load generators (`LGens`) components of TitanSim, i.e. this feature should be used to write efficient load generators.

	See ‎<<_13, [13]>> for more details.

	== `LoadRegulator`

	The EPTF Load Regulator feature makes it possible to regulate the CPS of a load generator based on the load of the SUT.

	See <<_14, ‎[14]>> for more details.

	== `Logging`

	The aim of the EPTF Logging feature is, to use the library provided logging framework for event-class based per-PTC log control. The feature manages the logging database, defines default log classes and functions without the extension of GUI.

	See <<_15, ‎[15]>> for more details.

	== `NameService`

	The EPTF Name Service feature makes it possible to register and query component references by name.

	See <<_17, ‎[18]>> for more details.

	== `PTCDeployment`

	The EPTF `PTCDeployment` implements the functionality that allows components to select a host, where new PTCs can be deployed according to specified tasks (called roles) in the PTCD component.

	See ‎<<_18, [18]>> for more details.

	== `RandomNArray`

	The aim of the EPTF Random N Array feature is to provide dynamic memory allocation for the TTCN-3 language in an efficient way. The EPTF Random N Array feature makes it possible to manage lists over `record of' data structures easily using index-arithmetics.

	See ‎<<_32, [32]>> for more details.

	== `RedBlackTree`

	The EPTF Red Black Tree feature is a self-balancing binary search tree. It can be used to store indexes into an associated array, similar to the EPTF Free Busy Queue (see <<free_busy_queue, `FreeBusyQueue`>>).

	See ‎<<_19, [19]>> for more details.

	== `Rendezvous`

	The aim of the EPTF Rendezvous feature is, to make a _Rendezvous service_. `Rendezvous` service provides a generic solution for synchronization among/between various entities either locally and remotely.

	See <<_29, ‎[29]>> for more details.

	== `RingBuffer`

	The EPTF Ring Buffer feature provides a general ring buffer (or circular buffer) implementation. Ring buffer is a http://en.wikipedia.org/wiki/Data_structure[data structure] that uses a single, fixed-size http://en.wikipedia.org/wiki/Buffer_%28computer_science%29[buffer] as if it were connected end-to-end. This structure can be easily used for buffering http://en.wikipedia.org/wiki/Data_stream[data streams].

	See ‎<<_20, [20]>> for more details.

	== `Scheduler`

	The EPTF Scheduler feature makes it possible to schedule events (actions) that should happen at a given time measured from the start of the component or relative to the schedule of the event. The Scheduler is efficient, it uses only two TTCN-3 timers to implement scheduling.

	See <<_21, ‎[21]>> for more details.

	== `Semaphore`

	The EPTF Semaphore feature makes it possible to implement blocking functions and to perform synchronization in TTCN-3.

	See ‎[23] for more details.

	== `StatCapture`

	The aim of the EPTF Statistics Capture feature is to group Statistics into capture groups and to print capture group contents regularly at sampling intervals to predefined capture files.

	See ‎<<_23, [23]>> for more details.

	== `StatHandler`

	`StatHandler` feature makes it possible to collect global, aggregated statistics via the existing EPTF Variable interface.

	See ‎<<_33, [33]>> for more details.

	== `StatMeasure`

	The aim of the EPTF Statistics Measure feature is to create Statistics (stand-alone or belonging to a Variable) and update their value when required.

	See ‎<<_24, [24]>> for more details.

	== `StatReplay`

	The aim of the EPTF Statistics Replay feature is to display a given Statistics from a given capture group on the chart in a slider window in the GUI.

	See ‎<<_25, [25]>> for more details.

	== Time Profile Editor

	The EPTF CLL Time Profile Editor is an application which allows the user to create and edit time profiles used by the EPTF CLL Execution Control <<_9, ‎[9]>> component.

	See ‎<<_31, [31]>> for more details.

	== `Transport`

	The EPTF Transport Control feature makes it possible to

	* Route the incoming and outgoing messages between the components
	* Store messages and information in a `FreeBusyQueue`
	* Handle the UDP and IPL4 testports dynamically.

	See ‎<<_28, [28]>> for more details.

	== `UIHandler`

	With the EPTF `UIHandler` feature, the user can manage display and manipulation of subscribed Variables on the runtime GUI. Apart from this, it is even possible to change the runtime GUI. The user can add, remove, enable or disable GUI elements.

	See ‎<<_26, [26]>> for more details.

	[[variable]]
	== `Variable`

	The EPTF Variable feature makes it possible to access component variables in remote components and to create automatically calculated Variables triggered by the refresh of other Variables.

	See ‎<<_27, [27]>> for more details.

	= Terminology

	TitanSim Application Library: +
	It is that part of the TitanSim software that is (at-least partially) project dependent. (I.e., which is protocol-, and/or application-dependent). Any TitanSim application library is to be supplied and supported _either_ by the customer project _only_; or by the customer project _together_ with the TCC organization. Any TitanSim application library development is to be funded by the ordering projects.

	TitanSim Core (Load) Library(CLL): +
	It is that part of the TitanSim software that is totally project independent. (I.e., which is not protocol-, or application-dependent). The TitanSim CLL is to be supplied and supported by the TCC organization. Any TitanSim CLL development is to be funded centrally by Ericsson

	Application Library (AppLib): +
	It is that part of the TitanSim software that is although protocol, or application-area dependent, but can be _reused_ across many TitanSim applications. `AppLibs` are dependent on the CLL.

	Control Logic: +
	It is that part of the TitanSim software that is specific to a particular TitanSim application program. It is usually not directly reusable and is built upon the CLL and several `AppLibs`.

	Entities: +
	They are "things/objects" that are simulated by the `LGen`. Such "things" are usually the "users", "calls", "servers", "terminations", or anything whose external behavior is to be simulated by the `LGen`. Usually an LGen simulates more than one entity.

	Entity context: +
	It is an index-able generic data record describing an entity. It serves as a hub connecting all information related to the entity together by referring the respective associated _behavior contexts_ and _FSM contexts_ via their indices. The entity contexts are identified via their indices with respect to the entity context database stored in the `v_LGenBase_entities` component variable.

	Behavior context: +
	It is an index-able (set of) data record(s) that stores data and state information of a given entity with respect to a given _behavior type._ Storage for behavior contexts is to be provided by the respective `AppLibs`.

	Behavior type: +
	It is a concept for collectively referring a set of _behavior contexts, FSM inputs, test steps,_ and functions realizing methods conforming to given function signatures prescribed by the `LGenBase` feature. Behavior types are to be declared dynamically during run-time to the `LGenBase` by the component-type initialization function of some `AppLib`. Usually an AppLib product has only one behavior type, but it is permitted for `AppLibs` to declare more than one behavior types, if necessary. Behavior types are identified by their indices determined by the order of declaration and the declarations are stored in `v_LGenBase_behaviorTypes`

	Entity type: +
	It is a named list of references to declared _behavior types_. As such, it declares what type of behavior contexts are available on entities of this type.

	Entity group: +
	A group of entities with homogenous entity type. The indices of the entities of the group make a continuous interval that does not overlap with the indices range of any other entity group.

	Test step: +
	Test steps are functions whose signature conforms to a given function type. They _must_ not contain TTCN-3 statement with blocking semantics.

	FSM table: +
	It is a formal specification of the communication rules of Finite State Machines. These indexable records are stored in `v_LGenBase_fsmTables`. FSM tables realizing _traffic cases_ must obey certain rules.

	Traffic case type: +
	It is a prototype used as an input for instantiating traffic case instances on a specific entity group. It defines what _FSM table_ to use, what _entity type_ must be used by the _entity group_ where the _traffic case_ is to be deployed.

	Traffic case: +
	It is a behavior, defined by an FSM table, that is executed on a given entity group. All entities of the entity group participate in executing the the traffic case. An entity group may have more than one concurrent traffic cases.

	Scenario: +
	It is a collection of traffic cases deployed on an entity group.

	TitanSim Variables: +
	They are enhanced component variables that make it possible to access the values of other Variables in remote components.

	TitanSim Statistics: +
	They are Statistics of TitanSim Variables. Possible Statistics are among others minimum, maximum, mean, standard deviation, etc. and also the content of a Variable can be a Statistics itself. The values of such Statistics are automatically and periodically updated in the background.

	Generated load of a traffic case: +
	It is defined as the _aggregate_ load generated by _traffic case instances_ of the given _traffic case_

	Generated load of the traffic mix: +
	It is defined as the _aggregate_ load generated by the individual _traffic cases_ of the given _traffic mix_

	Programming style, event driven: +
	A programming style not-so "natural" for most people. It is atypical for function tests. It focuses on one or more threads of execution, however, _not_ in a sequential manner. Rather it defines states for execution where the program code wait for an event (any event) to happen, then based on the event it executes a state transition to a new state and continues to wait for another event. The flow of events _cannot be_ understood easily just by reading the source code sequentially, therefore it is less natural for many programmer.

	Programming style, procedural: +
	It is typical for functions tests. It focuses on a single thread of execution in a sequential manner. The "natural" programming style for most programmers, since the flow of events can be understood easily just by reading the source code sequentially.

	Traffic case instance: +
	It is a specific execution instance of the behavior (message sequence) defined by the _traffic case_

	Traffic generator PTC: +
	It is a PTC that actually generate the messages toward the SUT during the performance test campaign

	Traffic group: +
	It is a named instance of a _traffic mix_. Such traffic group may have _TitanSim Parameters_ that are common to each traffic cases within the group that realize the _traffic mix_. Such traffic group may have (potentially aggregate) _ TitanSim Statistics_ that provides (potentially aggregate) information about the execution of the _traffic cases_ within the group. Note, however, that the _traffic cases_ may have individual parameters and statistics, as well.

	Traffic mix: +
	It is a specific combination of _traffic cases_ that are to be executed concurrently by TitanSim. Each traffic case has a corresponding traffic weight assigned. The traffic mix has a load-level target that is an aggregate of the individual load-levels of the individual _traffic cases_, whose load levels are the result of the execution of their _traffic case instances_

	= Abbreviations

	API:: Application Programming Interface

	CLL:: Core Load Library

	TitanSim:: Ericsson Load Test Framework, formerly TITAN Load Test Framework

	IUT:: Implementation Under Test

	LGen:: Load Generator PTC

	PTC:: Parallel Test Component

	SUT:: System Under Test

	TCC:: Test Competence Center

	TLTF:: See TitanSim

	TTCN-3:: Testing and Test Control Notation version 3 ‎<<_1, [1]>>.

	= References

	See the introduction of Section ‎3 for the location of feature documentations in the delivery VOB.

	[[_1]]
	[1] ETSI ES 201 873-1 v3.2.1 (2007-02) +
	The Testing and Test Control Notation version 3. Part 1: Core Language

	[[_2]]
	[2] User Guide for the TITAN TTCN-3 Test Executor

	[[_3]]
	[3] TitanSim CLL for TTCN-3 toolset with TITAN, User Guide

	[[_4]]
	[4] TitanSim CLL for TTCN-3 toolset with TITAN +
	http://ttcn.ericsson.se/products/libraries.shtml[Reference Guide]

	[[_5]]
	[5] Project Specification for TitanSim R2

	[[_6]]
	[6] Quick Study on TITANSim R2 development

	[[_7]]
	[7] EPTF CLL Base, Function Description

	[[_8]]
	[8] EPTF CLL Common, Function Description

	[[_9]]
	[9] EPTF CLL ExecCtrl, Function Description

	[[_10]]
	[10] EPTF CLL Free Busy Queue, Function Description

	[[_11]]
	[11] EPTF CLL HashMap, Function Description

	[[_12]]
	[12] EPTF HostAdmin, Function Description

	[[_13]]
	[13] EPTF CLL LGenBase, Function Description

	[[_14]]
	[14] EPTF CLL LoadRegulator, Function Description

	[[_15]]
	[15] EPTF CLL Logging, Function Description

	[[_16]]
	[16] EPTF CLL LoggingUI, Function Description

	[[_17]]
	[17] EPTF CLL NameService, Function Description

	[[_18]]
	[18] EPTF CLL PTCDeployment, Function Description

	[[_19]]
	[19] EPTF CLL RedBlackTree, Function Description

	[[_20]]
	[20] EPTF CLL RingBuffer, Function Description

	[[_21]]
	[21] EPTF CLL Scheduler, Function Description

	[[_22]]
	[22] EPTF CLL Semaphore, Function Description

	[[_23]]
	[23] EPTF CLL StatCapture, Function Description

	[[_24]]
	[24] EPTF CLL StatMeasure, Function Description

	[[_25]]
	[25] EPTF CLL StatReplay, Function Description

	[[_26]]
	[26] EPTF CLL UIHandler, Function Description

	[[_27]]
	[27] EPTF CLL Variable, Function Description

	[[_28]]
	[28] EPTF CLL Transport, Function Description

	[[_29]]
	[29] EPTF CLL Rendezvous, Function Description

	[[_30]]
	[30] EPTF CLL Central Scheduling, Function Description

	[[_31]]
	[31] EPTF CLL Time Profile Editor, Function Description

	[[_32]]
	[32] EPTF CLL Random N Array, Function Description

	[[_33]]
	[33] EPTF CLL Stat Handler, Function Description