jastram
commented
11 years ago I integrated parts of the text into D7.3, but kept it much more concise, as Section 2 is meant to be a summary (more information can be provided in Appendix A). I updated the picture to reflect that the Papyurs model could be edited with the Scade tools as well. This has been committed as eb56fde1270411aa17d9b05bc48e1268b62a5de5
The following section:
"SCADE. A SCADE-based primary toolchain would consist of the two tools Papyrus and SCADE. An integration between the tools already exists, and both tools cover all activities. The biggest advantage is that there would be little additional work necessary to cover the primary toolchain. The biggest drawback of this solution is the fact that SCADE is not open source."
should be rephrased as follows:
"SCADE Tools Chain: "A SCADE-based primary toolchain can be used as is, since it is a commercially available tools chain for model driven software development supporting formal methoths with strict sematics and sytax and already certified for use in safety critical applications up to high safety integrity levels in various domains like raiway (EN50128, SIL4), avionics (DO178C), and automotive (ISO26262). An integration between the tools already exists, and both tools cover all activities. The biggest advantage is that there would be almost no additional work necessary to cover the primary tools chain. The biggest drawback of this solution is the fact that SCADE is not open source, but provides artifacts (SysML, XML, Lystre, ASCII text, PDF, C or ADA), which are openly defined and which can therefore be used to design open Source documents, models, or software.
In the top level SCADE System has adapted a restricted version of Papyrus so that artifacts are interchangeable between both tools. In that level Papyrus can be used alternatively, given that only SysML elements supported by SCADE System are actually used only. This can be checked with the SCADE tools. At the lowest level, the code generation, other alternative code generators can be used as well. Within the scope of the openETCS project no development work is planned to adapt SCADE tools to the open proofs tools chain, as long as SCADE is not licensed under an OSI certified open source license."
Figure 2 should be adapted, so that SCADE System and Papyrus can be used alternatively, with certain restrictions on the use of Papyrus, so that the Artifacts in that level are interchangebale.