BS EN 15876-2:2011 pdf download – Electronic fee collection — Evaluation of on-board and roadside equipment for conformity to EN 15509 Part 2: Abstract test suite
7.2.1.3 Test suite parameter declarations
If the test suite parameter references a Protocol Implementation Conformance Statement (PICS) item, the testsuite parameter identifiers are prefixed “TSPC_”.
EXAMPLE 1 TSPC_extended_rf_carriers.
If the test suite parameter references a PIXIT item, the suite parameter identifiers are prefixed “TSPX_”.
EXAMPLE 2 TSPX_pmid.
If the test suite parameter represents a system parameter, the complete name defined in the protocol is used.
7.2.1.4 Test case selection expression definition
The test case selection expression identifiers begin with the prefix “SEL_”.
7.2.1.5 Test suite constant declarations
The test suite constant identifiers are prefixed “TSC_”.
If the test suite constant represents a system parameter, the complete name defined in the protocol is used.
7.2.1.6 Test suite variable declarations
The test suite variable identifiers are prefixed “TSV_”.
Complete names as defined in the protocol are used.
7.2.1.7 Test case variable declarations
The test case variable identifiers are prefixed “TCV_”.
Complete names as defined in the protocol are used.
7.2.1.8 Timer declarations
Timers begin with the prefix “T_”.
7.2.1.9 ASP type definitions
The general conventions in 7.2.1.1 apply. All capital letters shall be used.
The identifier of an ASP type uses the same name as the name defined in the protocol.
7.2.1.10 PDU type definitions
The general conventions in 7.2.1.1 apply. All capital letters shall be used.
The identifier of a PDU type uses the same name as the name defined in the protocol.
7.2.1.11 Co-ordination Message (CM) type definitions
All capital letters shall be used.
7.2.1.12 Alias definitions
Alias definitions are not used.
7.2.2 Constraints part
This clause describes the naming conventions chosen for the elements of the ATS constraints part.
Constraints shall be written with all lowercase letters.
7.2.3 Dynamic part
7.2.3.1 General
This clause describes the naming conventions used for the elements of the ATS dynamic part.
All test cases shall be listed in the order in which they appear in the Test Suite Structure (TSS) and TP document.
7.2.3.2 Test Case (TC) identifier
The identifier of the test case is built in a similar way as for the test purpose.
The identifier of a TC is built according to Table 2.
7.2.3.3 Test step identifier
The test step identifier is built of substrings in lowercase letters, preceded by a string of uppercase letters. The substrings are joined by underscore characters. The first substring indicates the main function of the test step;
e.g. PR for PReamble, PO for POstamble, LTS for Local Tree and STP for general test step. The second substring indicates the purpose of the step.
EXAMPLE STP_emulate_mac.
7.2.3.4 Default identifier
The default identifiers begin with the prefix “DF_”, followed by a string in lowercase letters.
7.3 Implementation conventions
7.3.1 Declaration part The comment line of single element TTCN tables (e.g. test suite constants) is used to give a reference where the format and content of the element is described in the relevant protocol document. Any particularity of the element format or content is described in the comment line. The detailed comments are used to describe any peculiarity of the table. In the ASP, PDU, and CM type declarations, the comments column is used to identify if a parameter (in ASPs) or field (in PDUs) is mandatory or optional:  M: mandatory;
O: optional. In the ASP and PDU declarations the comments column is further used to give information about the parameter/field value, in particular if the parameter/field contains a fixed spare value.
7.3.2 Constraint part The ASPs and PDUs are defined in a way that all relevant parameters/fields are parameterized. That improves the transparency of the constraints in the dynamic part, as all values which are relevant for the test are always present.