-
Notifications
You must be signed in to change notification settings - Fork 20
Documentation
This page contains the guidelines and first elements for the activity of languages and tools evaluation (subtasks T1.1 and T1.2 of WP7)
The proposal of languages and tools are given in Benchmark to evaluate model and tools.
You can also read Open Question for Modelling Benchmark.
The description of a model should follow the Model documentation template.
##Languages evaluation criteria
According to the description of work of WP7, the languages may have to be adapted in the process. The identification and definition will distinguish between wide-spectrum modelling languages suitable for a wide variety of modelling domains such as UML, SysML, B, and domain-specific languages (DSL) designed and optimised for application in a specific application domain only. For wide-spectrum languages their metamodels will be analysed with respect to their expressive power and resulting adequateness for designing ERTMS models. For DSL candidates the associated meta-metamodels will be analysed with respect to their capabilities to support language extensions that may become necessary for novel releases of the ERTMS specification the in the future. Since no language is universal (i.e. able to address all aspects of design needs) the proposed approach is likely to involve several modelling languages supporting different viewpoints and working at different levels of abstractions. With this kind of approach, we will need to check the compatibility of the semantics of the modelling languages that address overlapping viewpoints. There are two problems here. First, when dealing with an heterogeneous specification, we need a common semantical basis to check the compatibility of the models. More pragmatically, when we deal with two models (expressed in a different language) that describe the same part of the system, we need to show that they are consistent with each other. Candidate languages will be subsequently evaluated against the requirements from WP2. If a suitable language is identified, but no partner steps up to model the prototype, it will not be considered.
A template of criteria on means is available in Means of description and methodology criteria - Template.
According to the description of work of WP7, corresponding to language evaluation, the objective of this subtask is the identification of the primary modelling tools (analysis and other secondary tools will be the subject of Section 2), based on the analysis from WP2, by using it for the prototyping described in Section 1.1. The experience with the tools will be recorded, and the tools will be evaluated against the requirements from WP2. In particular, the compliance of the candidate tools with respect to EN50128 constraints will be investigated.
A template of criteria on tools is available Tools criteria - Template.