0008012: Use TDLan for TP and TD specifications

Notes
(0015920) Philip Makedonski (manager) 14-04-2021 14:44	One option would be to embed blocks / behaviours in STOs (or a separate meta class, e.g. ATO), event occurrence would then become an atomic behaviour (thus also qualifying it for use in TDs behaviours? or shall it be restricted (most likely, unless required otherwise)?).

(0015924) Philip Makedonski (manager) 19-04-2021 10:03	After further evaluation, the proposed course of action is to provide guidelines and a specialised syntax for using test descriptions to specify test objectives. The specialised syntax may add some restrictions (similar to locally ordered vs totally ordered test descriptions), along with predefined annotations for initial conditions, expected behaviour (+when / then clauses) and final conditions which are to be used with compound behaviours. The details of the representation will be described either as part of Part 4 (if normative, more likely) or as part of TR 103 119 (if informative). Dedicated textual and data representations will be elaborated further in Part 8. The proposed way of using test description elements for the specification of test objectives will serve as an alternative to structured test objectives. It will carry over the requirements for test descriptions (e.g. predefined data, configuration), possibly loosening some of the constraints (e.g. regarding data completeness), and introducing additional constraints (e.g. allowed behaviours, use of annotations, use of other constructs). In contrast to the previously proposed approach, there will be no possibility of mixing event occurrence specifications and atomic behaviours, as this will add complexity (for users and for tool vendors) while providing limited benefits.

(0015925) schauppk (reporter) 21-04-2021 08:46	Guidelines and rules to be applied are the last resort. The model must not allow implementations in a way, that makes further processing difficult. Without detailed knowledge of the "specialised syntax", it is hard to see the implications and restrictions behind. What we have to ensure, is to reach the intended goal and make chapter 6.3 of TR 103 119 obsolete, as this was the main motivation behind this CR. Sure, "Use TDLan for TP and TD specifications" may be just one solution to the goal and there may be others, even better ones. We should not wait for another 4 years for some commercial tool vendors to pop up with tooling in order to allow the TDL users to evolve existing or newly created TPs into TDs.

(0015926) Philip Makedonski (manager) 21-04-2021 14:03	The direction for the specialised syntax was discussed during the working session. Guidelines and rules provide a framework that user can chose to apply and get further benefits, or not apply if they are not suited for the intended usage context. We are talking about Test Purposes - since when do they have to be specified on level of detail of executable test cases? If that is what is actually desired - there are suitable languages and notations for that as well. I do not think we are not going to make chapter 6.3 obsolete. This CR has a different goal, which is provide alternative ways for users who choose to take advantage of them. If at some point this is all users, then chapter 6.3 can be made obsolete. What commercial tool vendors may or may not chose to do is up to the tool vendors. MTS has no influence on that. The specifications aim to not make that more difficult than it needs to be. The TOP aims to make that even easier. We welcome contributions to both that are aligned with these aims. Users have the choice to decide which process works for them. Tools can support that choice but do not need to. Restricting the options would only lead to alienating existing users.

Issue History
Date Modified	Username	Field	Change
06-03-2021 07:28	schauppk	New Issue
14-04-2021 14:44	Philip Makedonski	Note Added: 0015920
14-04-2021 14:44	Philip Makedonski	Assigned To	=> Philip Makedonski
14-04-2021 14:44	Philip Makedonski	Status	new => assigned
19-04-2021 10:03	Philip Makedonski	Note Added: 0015924
21-04-2021 08:46	schauppk	Note Added: 0015925
21-04-2021 14:03	Philip Makedonski	Note Added: 0015926

Relationships

ETSI's Bug Tracker