Changes for page SCCharts Development

Last modified by Richard Kreissig on 2023/09/14 10:04

From version < 72.1 >

edited by Niklas Rentz
on 2023/09/12 12:30

To version < 70.1 >

edited by Alexander Schulz-Rosengarten
on 2023/07/11 10:37

Change comment: Renamed back-links.

Raw
Rendered

Summary

Page properties (2 modified, 0 added, 0 removed)

Details

Page properties

Author

@@ -1,1 +1,1 @@
--XWiki.nre
++XWiki.als

Content

@@ -1,3 +1,6 @@
++{{layout}}
++{{layout-section ac:type="single"}}
++{{layout-cell}}
  This is a light-weight tutorial for developing transformations/additions for SCCharts in KIELER. It will use Eclipse, EMF, and Xtend and therefore, finishing the corresponding tutorials could prove useful. However, they are not a strict requirement for this tutorial.
  {{warning title="Outdated!"}}
@@ -17,8 +17,11 @@
  == Required Software ==
  As you're going to develop for KIELER SCCharts, we recommend to use the Oomph setup as described in [[doc:KIELER.Getting Eclipse]] (Oomph Setup). However, you could also install all componentes by yourself. Please consult the other tutorials if you want to do that. You would need to install the Modeling Tools and the Xtext SDK.
++{{/layout-cell}}
++{{/layout-section}}
--
++{{layout-section ac:type="three_equal"}}
++{{layout-cell}}
  \\
  Additionally, install the** EcoreViz** from the **Ecore Model Visualization** category from the **OpenKieler** update site: [[http:~~/~~/rtsys.informatik.uni-kiel.de/~~~~kieler/updatesite/nightly-openkieler/>>url:http://rtsys.informatik.uni-kiel.de/~~kieler/updatesite/nightly-openkieler/||rel="nofollow" shape="rect"]]. For this, choose //Install New Software...// in the //Help// tab.
@@ -29,16 +29,25 @@
  * KIELER Lightweight Diagrams Generic Diagram View.
  (This step should be obsolete in the near future.)
++{{/layout-cell}}
++{{layout-cell}}
  \\
  [[image:attach:InstallEcoreViz.png]]
++\\
++{{/layout-cell}}
--\\\\
++{{layout-cell}}
++\\
  [[image:attach:InstallKLighDFeatures.png]]
++{{/layout-cell}}
++{{/layout-section}}
++{{layout-section ac:type="single"}}
++{{layout-cell}}
  == Recommended Tutorials ==
  We recommend that you have completed the following tutorials before diving into this one (or at least sweep over them). However, this is not a strict requirement.
@@ -76,7 +76,11 @@
  (% style="color: rgb(0,0,0);" %)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: rgb(0,0,0);" %), (%%)[[bib>>url:http://rtsys.informatik.uni-kiel.de/~~biblio/cgi-bin/bibcgi.cgi?key=vonHanxledenDM+13b||shape="rect"]]
  \\
++{{/layout-cell}}
++{{/layout-section}}
++{{layout-section ac:type="two_right_sidebar"}}
++{{layout-cell}}
  = The SCCharts Metamodel =
  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.
@@ -112,14 +112,20 @@
  {{info title="KLighD Screenshots"}}
  By the way: You can //right-click// on the Diagram View surface and select //Save as image...// to create a screenshot!
  {{/info}}
++{{/layout-cell}}
++{{layout-cell}}
  [[image:attach:sccharts_metamodel.png]]
  [[image:attach:sccharts_metamodel_treeEditor.png]]
  [[image:attach:KLighDSaveAsImage.png]]
++{{/layout-cell}}
++{{/layout-section}}
--= Creating SCCharts Models Programmatically =
++{{layout-section ac:type="single"}}
++{{layout-cell}}
++= Creating SCCharts Models Programmatically  =
  == Creating a Test Project ==
@@ -214,7 +214,11 @@
  File extensions are important! They define the parser/serializer that EMF uses. Always use the file extension that is defined for a particular model.
  {{/info}}
  )))
++{{/layout-cell}}
++{{/layout-section}}
++{{layout-section ac:type="two_right_sidebar"}}
++{{layout-cell}}
  ==== Model Creation Task ====
  You are now equipped with the fundamentals you need to create models programmatically. Let's try it:
@@ -238,7 +238,9 @@
  *1. Create a new project and add you generated model.
  \\
++{{/layout-cell}}
++{{layout-cell}}
  {{code language="java" title="Root.sct"}}
  scchart Root {
    initial state Init
@@ -247,7 +247,11 @@
  {{/code}}
  [[image:attach:RunConfiguration.png]]
++{{/layout-cell}}
++{{/layout-section}}
++{{layout-section ac:type="two_right_sidebar"}}
++{{layout-cell}}
  = Model-to-Model Transformations with KiCo =
  You can use the [[Kieler Compiler>>url:http://rtsys.informatik.uni-kiel.de/confluence/display/KIELER/Kieler+Compiler||shape="rect"]] (KiCo) to handle all the model input/output tasks and concentrate on the actual transformation. If you executed the **Model Creation Task correctly**, you should now have a complete running SCT Editor instance that looks like the one on the right. You should see the //KIELER Compiler Selection// n the lower right part of the working space. Here you can select specific transformations that will be applied to the actual model. Simply select a transformation to test it.
@@ -255,9 +255,15 @@
  == Creating a new Transformation ==
  Now, you're going to write your own transformation with **Xtend** *drumroll*, a programming language that looks very similar to Java, but which adds some very convenient features. Xtend code compiles to Java and and was developed using Xtext. In fact, once you gain experience working with Xtend you will probably appreciate the power of Xtext even more. Xtend is particularly useful to browse & modify EMF models. You get the point... we like it. :)
++{{/layout-cell}}
++{{layout-cell}}
  [[image:attach:KielerSCTEditor.png]]
++{{/layout-cell}}
++{{/layout-section}}
++{{layout-section ac:type="two_right_sidebar"}}
++{{layout-cell}}
  ==== Transformation Creation Task ====
  * Create your first transformation...
@@ -302,7 +302,15 @@
  You should really think about some constants here. You can also look at the sccharts transformation and features constants in the sccharts plugin.
  {{/info}}
  )))
++{{/layout-cell}}
++{{layout-cell}}
++\\
++{{/layout-cell}}
++{{/layout-section}}
++
++{{layout-section ac:type="two_right_sidebar"}}
++{{layout-cell}}
  * KiCo must know about the new feature and also about your new transformation.
  *1. Add a new Xtend class with Feature as superclass. Add all unimplemented methods. Also set** sccharts.doubleStates** as Id.
  *1. Go to the Extension tab inside your plugin configuration.
@@ -316,9 +316,15 @@
  *111. preferred: (leave it blank)
  *1. {{note 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.{{/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.
  * 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.
++{{/layout-cell}}
++{{layout-cell}}
  [[image:attach:KielerSCTEditorOwnTransformation.png]]
++{{/layout-cell}}
++{{/layout-section}}
++{{layout-section ac:type="two_right_sidebar"}}
++{{layout-cell}}
  * Now, fill your transformation with life:
  *1. Inside your transformation class, add a new method with the following signature: {{code language="none"}}def State transform(State rootState, KielerCompilerContext context){{/code}}. This transformation will be executed if the feature is selected in the Compiler Selection.
  *1. (((
@@ -353,11 +353,15 @@
  Extensions are also just classes. You can add your own to improve the structure of your own projects. In KIELER all extensions end with "Extensions"; except SCChartsExtension for legacy reasons. This will be renamed in after the next snapshot to SCChartsExtensions. So, if you're going to add new extensions to the project, please name them accordingly.
  {{/note}}
  )))
++{{/layout-cell}}
++{{layout-cell}}
  [[image:attach:KielerSCTEditorOwnTransformationOlolo.png]]
++{{/layout-cell}}
++{{/layout-section}}
--
--
++{{layout-section ac:type="two_right_sidebar"}}
++{{layout-cell}}
  * Extend your transformation so that it is applied on all states (except the root state). Try your new transformation with ABO. The result should look like the example on the right.
  == The existing Compilation Chain ==
@@ -369,7 +369,9 @@
  //We will add more content to this subsection in the future...//
  \\
++{{/layout-cell}}
++{{layout-cell}}
  [[image:attach:ABODoubleStates.png]]
  \\
@@ -376,6 +376,12 @@
  \\
++\\
++{{/layout-cell}}
++{{/layout-section}}
++
++{{layout-section ac:type="single"}}
++{{layout-cell}}
  = Model-to-Model Transformations between Metamodels =
  Transformations from one model to another may be performed within the same metamodel or from metamodel to a different metamodel. Both methods are used in KIELER and in principle they do not really differ in implementation. Nevertheless, if working within the same metamodel you should keep in mind that you're potentially changing the actual model instead of changing another instance (after copying). When transforming to another metamodel, you're always generating a new model. So there is no in-place transformation. Both is possible. Just make sure that you know what you're doing.
@@ -421,13 +421,23 @@
  [[image:attach:abo_scg_HandleA.png]]
  )))
  )))
++{{/layout-cell}}
++{{/layout-section}}
++{{layout-section ac:type="two_equal"}}
++{{layout-cell}}
  The next figure depicts the direct mapping from normalized SCCharts to their corresponding SCG.
  Inspect the metamodel of the SCGs in plugin de.cau.cs.kieler.scg. SCGs are used for analyses and optimization and include a lot of additional elements. However, for this tutorial it should be sufficient to look at the SCGraph class, its nodes attribute, the important node classes and the controlflow class. Important nodes for this SCG are entry, exit, assignment, conditional,
++{{/layout-cell}}
++{{layout-cell}}
  [[image:attach:sccharts-scg.png]]
++{{/layout-cell}}
++{{/layout-section}}
++{{layout-section ac:type="two_right_sidebar"}}
++{{layout-cell}}
  ==== Transformation Creation Task 2 ====
  Write a transformation that transforms your normalized version of ABO's HandleA into its corresponding SCG.
@@ -445,3 +445,10 @@
  Congratulations! You finished the SCCharts Development Tutorial. Ask your supervisor for further instructions!
  \\
++{{/layout-cell}}
++
++{{layout-cell}}
++\\
++{{/layout-cell}}
++{{/layout-section}}
++{{/layout}}

Changes for page SCCharts Development

Summary

Details

Navigation

Quick Links