|
|
We need some further information regarding the desired change:
"During the specification of Test Purposes for the IoT-Testware we experienced the lack of the possibility to group Test Purposes. Although in ES 203 119-4 a keyword "Group" is specified, the semantic behind does not fit our needs (please find attached sample)."
The semantic behind it is that of grouping related elements in a package ("Group" is a concrete syntax representation for "Package"). In which way does it not fit the needs? What other semantics is required for groups?
"Due to that, we are missing the possibility to reflect the specified TSS properly within the TPs. Especially in combination with the "Word document export feature", the generated TP tables are in a flat structure. Though, we intend to reflect the TSS within TPs section in the final document (e.g. TS 103 192-2 chapter 7.2)"
This seems like a tooling issue. From what I understand, the group / package structure shall be translated to headings structure in the output document. This can be arranged within the tool implementation, not sure there is a need for a language change based on the description above.
"Using the approach of defining Test Purposes in TDL-TO and publishing them as Technical Specifications afterwards, adds a tedious manual and error-prone step (and probably a second one on reviewing before publishing)."
Looking at TS 103 192-2 chapter 7.2, there seems to be a lot of content beyond what is provided by TDL-TO so manual steps are probably necessary in any case. Could you provide more detail of what your desired input should look like and what your desired output shall be? That would be very helpful for the team to determine the exact features that need to be added to both the language and the tooling in order to streamline your work. |
|
mqtt_samples.tplan2 (2,206) 11-10-2018 15:46