Changes for page SCCharts Development
Last modified by Richard Kreissig on 2023/09/14 10:04
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -71,7 +71,6 @@ 71 71 * **Overview and High-Level Transformations in Detail:** 72 72 (% style="color:#000000" %)Reinhard von Hanxleden and Björn Duderstadt and Christian Motika and Steven Smyth and Michael Mendler and Joaquín Aguado and Stephen Mercer and Owen O’Brien. SCCharts: Sequentially Constructive Statecharts for Safety-Critical Applications. Technical Report 1311, Christian-Albrechts-Universität zu Kiel, Department of Computer Science, December 2013. ISSN 2192-6247. (%%)[[pdf>>url:http://rtsys.informatik.uni-kiel.de/~~biblio/downloads/papers/report-1311.pdf||shape="rect"]](% style="color:#000000" %), (%%)[[bib>>url:http://rtsys.informatik.uni-kiel.de/~~biblio/cgi-bin/bibcgi.cgi?key=vonHanxledenDM+13b||shape="rect"]] 73 73 74 - 75 75 = The SCCharts Metamodel = 76 76 77 77 Navigate to the {{code language="none"}}models{{/code}} folder of the plugin {{code language="none"}}de.cau.cs.kieler.sccharts{{/code}}. Here, open the {{code language="none"}}sccharts.ecore{{/code}} and right-click on the {{code language="none"}}sccharts.ecore{{/code}} file and select //Visualize Ecore Model//. Since you also installed **EcoreViz** from the OpenKieler Suite, you should now see a graphical representation of the SCCharts metamodel. Every SCChart will be a model of this metamodel. ... ... @@ -102,8 +102,7 @@ 102 102 *1. Now, navigate to the //Super State: Strong Abort Transition //example. Write down (on paper) how the model of that SCCharts looks like. 103 103 *1. And finally a more sophisticated model: Write down the model of ABO (from [[doc:KIELER.Examples]]). 104 104 105 -{{info title=" 106 -KLighD Screenshots"}} 104 +{{info title="KLighD Screenshots"}} 107 107 By the way: You can //right-click// on the Diagram View surface and select //Save as image...// to create a screenshot! 108 108 {{/info}} 109 109 ... ... @@ -231,8 +231,7 @@ 231 231 *1. Click //Run// (or //Debug// if you opened// Debug Configuration...//) 232 232 *1. Create a new project and add you generated model. 233 233 234 -{{code language="java" title=" 235 -Root.sct"}} 232 +{{code language="java" title="Root.sct"}} 236 236 scchart Root { 237 237 initial state Init 238 238 --> Init with true; ... ... @@ -307,7 +307,7 @@ 307 307 *111. label: Tutorial Compilation 308 308 *111. priority: 101 309 309 *111. preferred: (leave it blank) 310 -*1. {{no tetitle="Plugin Tasks"}}In general it is bad to mix non-ui plugins/tasks with ui plugin/tasks because (in the context of KiCo) even if you're not working with an active UI your transformations should work (e.g. a command line compiler). To keep this tutorial simple, you can add this dependency to your plugin nevertheless. However, you shouldn't do this in real products. Always keep the UI separated.{{/note}}If you start your KIELER instance now, you should get a new compilation chain which has only one transformation: yours, which doesn't do anything.307 +*1. {{info title="Plugin Tasks"}}In general it is bad to mix non-ui plugins/tasks with ui plugin/tasks because (in the context of KiCo) even if you're not working with an active UI your transformations should work (e.g. a command line compiler). To keep this tutorial simple, you can add this dependency to your plugin nevertheless. However, you shouldn't do this in real products. Always keep the UI separated.{{/info}}If you start your KIELER instance now, you should get a new compilation chain which has only one transformation: yours, which doesn't do anything. 311 311 * If you want to rename your feature in the Compiler Selection (without changing its Id), override the {{code language="none"}}getName{{/code}} method and return a new name. Rename your feature appropriately. 312 312 313 313 [[image:attach:KielerSCTEditorOwnTransformation.png]] ... ... @@ -430,6 +430,4 @@ 430 430 *1. Optimize the given SCG and compare the result with the previous one. 431 431 *1. Make sure that the two SCGs are still semantically identical. 432 432 433 - 434 434 Congratulations! You finished the SCCharts Development Tutorial. Ask your supervisor for further instructions! 435 -