1. TDL Standardization and Development – Building a Community
Input to TDL steering group meeting
Andreas Ulrich, Siemens AG |
TDL Standardization and Development – Building a Community

2. Status

3. Our assets – What we have on language design
A maturing series of standards that is ready for deployment
The ETSI standard series ES , parts 1 – 4
Why a standardized test language?
TDL-MM, part 1: Abstract Syntax and Associated Semantics v.1.3.1
TDL-GR, part 2: Graphical Syntax v.1.2.1
TDL-XF, part 3: Exchange Format v.1.2.1
TDL-TO, part 4: Structured Test Objective Language v.1.2.1
Published documents:
Creates open platform and ecosystem for development of a versatile tool landscape
Independence from a single technology or tool vendor
Joint effort of industrial users, tool providers, academia
Stays abreast of new technological trends
Community building
TDL-GR
TDL-XF
TDL-TO
Other syntax
TDL-MM
Abstract Syntax
Concrete Syntax

4. Our assets – What we have on tools and how it could evolve
Based on open standards and supporting the integration of open-source and third-party components
UML-based Graph. Editor
TDL Model Analyzer
Report
Textual Editor (incl. ES )
TDL Test Generator
TDL Exchange Format (ES )
Graphical Editor (ES )
Graph. Viewer & Doc. Gen.
Test Code Generator
C-code,
TTCN-3
Test Plan
Front-end tool
Back-end tool
Artefact (output)
(Partially) covered in ETSI TDL phase 3

5. Building the TDL community
Attached MindMap diagram:
As explored during previous meeting on Nov 16, 2015

6. Proposed Follow-up Activities

7. Community Services Responsibilities
Continued activity, mostly voluntary
 Tasks taken by the web editor group TWT;
up to 5 members;
reports at the MTS meeting;
MTS members should express their interest;
Andreas, Andrej, Philip, Martti
ETSI TDL website maintenance, TDL user group
Setup responsible editors
Feeding new content on tools, standards, applications, events
Blogging on TDL related topics
Approaching ETSI TBs via CTI (use of TDL in document-centric standardization)
Promotion of TDL
Understand their needs
Help in setting up tools
Approaching newly interested parties and involve them into standardization or tooling or others
For example from UCAAT 2015
Nyspyre, (Philip knows the name)
Sela, Natalia Meergus (“Using MBT to Check Safety of Medical Devices”)
TDL events
Workshops, tutorials, white papers etc.
Managing STF activities for TDL within MTS
 Miguel, Anthony
 Emmanuelle, MTS Chairman
 done within MTS
 Steering Group inside MTS

8. STF Standardization Activities
Summary of activities
Language maintenance, improving existing standards, driven via Mantis
New language features
Operations over test configurations (left-over from TDL-2)
High-level TDL specification (a.k.a. “control part”)
Data pools
High-level test descriptions (similar to HL-MSCs)
Features for performance and security testing
Open Source tool maintenance
Keeping tools consistent with standards
TDL libraries (need to be also reflected in standards)
Standard data types, e.g. int, double
Higher-level data: Lists and data type parameters
Standard mappings from/to TDL data types
Serving the needs of the tool stakeholders, e.g. CTI
Improving TDL semantics
TDL-to-TTCN-3 translation rules (ETSI Standard)
Mapping of TDL language elements to TTCN-3 code
Resolving ambiguities of dynamic semantics
Supporting TDL users
(tool-independent) Guidelines on the application of TDL (ETSI Guide)
Tuned to specific applications, demonstrating profiling of TDL features
Requires the availability of tools (editors, compilers)

9. Proposed Next TDL Phases for STF Work
Timeframe: June 2016 – December 2019 (3+ years)
2016/17 TDL 4 Raising the fidelity of TDL: TDL-to-TTCN-3 translation; improving dynamic semantics
2017/18 TDL 5 Helping TDL users: guidelines; high-level TDL specs, further new features; improved tools
2018/19 TDL 6 Extending the scope: TDL for performance and security testing
_____________________
ToR submission for April?
No tool development anymore
ToR requires only mentioning efforts, no budget
Meeting with Alberto on March 11 to clarify details of the ToR process
 Next meeting: March 22, 10:00

10. Some Further Details

11. Operations over test configurations
Some details worked out in TDL-2, but not yet implemented
Suggestions: Operations to build and modify test configurations (TCs)  Further ops needed?
Configuration use: a TC of name tc2 is used within the TC of name tc1; meaning: all CIs in tc2 and connections between them become accessible in tc1
Component merge: a CI c2 in TC tc2 and a CI c1 in TC tc1 are merged to a single one; the CI c1 will prevail after the merge
Component hide: a CI c can be hidden in a TC tc; meaning: a hidden CI becomes not accessible in the TC and connections from other CIs to this CI are also hidden and not accessible, e.g. in interactions
Renaming of CIs and GIs: the name of a CI from a used TC can be renamed, including the gate instances attached to this CI
Role (re-)assignment of CIs {Tester, SUT}: overwrites an existing assignment
Adding variables to CIs: a new variable is added to a CI (tester or SUT?)
Redefining compatibility: Super and sub test configurations are built in a constructive manner from other test configurations
A TD td2 running of TC tc2 can be called from TD td1 running on TC tc1 iff tc2 is used in the definition of tc1

12. High-level test descriptions
General idea: combine test descriptions to form higher-level behavior, enabling abstract test generation
vs.
Test generator generates tests according to chosen coverage criterion.
User models tests explicitly and keeps control over them.