-
Notifications
You must be signed in to change notification settings - Fork 20
Tool Description Template
i.e. to someone that has authority to answer questions on this tool and that can answer promptly; it can be an alias
- Modelling
- Code generation
- Test case generation
- Model verification
- Code verification
- Other (Please elaborate)
Brief introduction to what the tool does
short list (max. 2) of publications related to the tool with a URL to download a copy. If possible a tutorial/user guide to the tool and/or the languages it is based on + reference document
Which kind of support is provided? Commercial support through a company, community support through a mailing list, both, other? Pricing.
Is the tool likely to exist in 10 years? Is it supported by a strong company that can fix potential bugs in the tool?
e.g. only a subset of the target language is covered
e.g. which steps are manual and automatic in the use of the tool.
e.g. which prerequisite is needed to use the tool
E.g. Framework, .NET vs. Java, etc.
Describe requirement to install/run the tool (all that is necessary to make the tool work fine: OS, Java version, dependencies with other tools, Eclipse version, ...)
Industrials need to maintain some traceability between source documents and deliverables, for certification purposes, as well as for maintenance and evolution purposes. Does the tool provide such traceability, or does it integrate in such a way that the traceability is maintained in a satisfactory way (notably WRT CENELEC requirements)?
can the tool be used by a team working on different fragments of the model? is there a support for versioning?
can the tool be used in a SIL-rated development process? There is a mention of this in the "Existing industrial usage" section, but I suggest to put it as a top-level item in the template.
For instance: are the underlying assumptions of the model acceptable WRT the development of systems evolving in real physical environment? This might not be the case if we consider models with a discrete (tic-based) model of time.
People or parties who have developed this and are currently driving the project including their affiliations
If different, version of the tool that should be used for the project
Especially if the tool has been qualified for CENELEC 50128 or other (DO-178)
List of projects or toolboxes (only list the representative examples) where the tool has been integrated + some information on the toolchain architecture that has been used (e.g. Eclipse Modelling / OSGi / UML / ...).
All further developments that are relevant for openETCS, even if not conducted directly within the project.