Changes for page SCCharts Development
Last modified by Richard Kreissig on 2023/09/14 10:04
<
>
edited by Richard Kreissig
on 2023/09/14 10:03
on 2023/09/14 10:03
edited by Alexander Schulz-Rosengarten
on 2023/07/11 10:37
on 2023/07/11 10:37
Change comment:
Renamed back-links.
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki.s tu2309801 +XWiki.als - Content
-
... ... @@ -1,3 +1,6 @@ 1 +{{layout}} 2 +{{layout-section ac:type="single"}} 3 +{{layout-cell}} 1 1 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. 2 2 3 3 {{warning title="Outdated!"}} ... ... @@ -4,6 +4,7 @@ 4 4 The KiCo part "Model-to-Model Transformations with KiCo" is outdated. We will update this tutorials in the near future. 5 5 {{/warning}} 6 6 10 +\\ 7 7 8 8 9 9 ... ... @@ -16,9 +16,13 @@ 16 16 == Required Software == 17 17 18 18 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. 23 +{{/layout-cell}} 24 +{{/layout-section}} 19 19 26 +{{layout-section ac:type="three_equal"}} 27 +{{layout-cell}} 28 +\\ 20 20 21 - 22 22 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. 23 23 24 24 Due to the ongoing migration you have to install a workaround for EcoreViz to function. You have to install the KLighD diagram view directly from [[http:~~/~~/rtsys.informatik.uni-kiel.de/~~~~kieler/updatesite/release_pragmatics_2016-02/>>url:http://rtsys.informatik.uni-kiel.de/~~kieler/updatesite/release_pragmatics_2016-02/||shape="rect"]]. Select the features ... ... @@ -27,14 +27,25 @@ 27 27 * KIELER Lightweight Diagrams Generic Diagram View. 28 28 29 29 (This step should be obsolete in the near future.) 38 +{{/layout-cell}} 30 30 40 +{{layout-cell}} 41 +\\ 31 31 32 32 [[image:attach:InstallEcoreViz.png]] 33 33 45 +\\ 46 +{{/layout-cell}} 34 34 48 +{{layout-cell}} 49 +\\ 35 35 36 36 [[image:attach:InstallKLighDFeatures.png]] 52 +{{/layout-cell}} 53 +{{/layout-section}} 37 37 55 +{{layout-section ac:type="single"}} 56 +{{layout-cell}} 38 38 == Recommended Tutorials == 39 39 40 40 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. ... ... @@ -62,15 +62,21 @@ 62 62 63 63 Additionally, the following list will give a short overview over the most important publications: 64 64 65 -* (% style="color: #000000" %)**Main paper:**(%%)66 - (% 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. In (% class="cmti-10" %)Proc. ACM SIGPLAN Conference on Programming Language Design(%%) (% class="cmti-10" %)and Implementation (PLDI’14)(%%), Edinburgh, UK, June 2014. ACM. [[pdf>>url:http://rtsys.informatik.uni-kiel.de/~~biblio/downloads/papers/pldi14.pdf||shape="rect"]](% style="color:#000000" %), (%%)[[talk>>url:http://rtsys.informatik.uni-kiel.de/~~biblio/downloads/talks/pldi14-talk.pdf||shape="rect"]](% style="color:#000000" %), (%%)[[bib>>url:http://rtsys.informatik.uni-kiel.de/~~biblio/cgi-bin/bibcgi.cgi?key=vonHanxledenDM+14||shape="rect"]]84 +* (% style="color: rgb(0,0,0);" %)**Main paper:** 85 +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. In (% class="cmti-10" %)Proc. ACM SIGPLAN Conference on Programming Language Design(%%) (% class="cmti-10" %)and Implementation (PLDI’14)(%%), Edinburgh, UK, June 2014. ACM. [[pdf>>url:http://rtsys.informatik.uni-kiel.de/~~biblio/downloads/papers/pldi14.pdf||shape="rect"]](% style="color: rgb(0,0,0);" %), (%%)[[talk>>url:http://rtsys.informatik.uni-kiel.de/~~biblio/downloads/talks/pldi14-talk.pdf||shape="rect"]](% style="color: rgb(0,0,0);" %), (%%)[[bib>>url:http://rtsys.informatik.uni-kiel.de/~~biblio/cgi-bin/bibcgi.cgi?key=vonHanxledenDM+14||shape="rect"]] 67 67 * **SLIC Compilation:** 68 -(% style="color: #000000" %)Christian Motika and Steven Smyth and Reinhard von Hanxleden. Compiling SCCharts—A Case-Study on Interactive Model-Based Compilation. In (% class="cmti-10" %)Proceedings of(%%) (% class="cmti-10" %)the 6th International Symposium on Leveraging Applications of Formal(%%) (% class="cmti-10" %)Methods, Verification and Validation (ISoLA 2014)(%%), volume 8802 of (% class="cmti-10" %)LNCS(%%), page 443–462, Corfu, Greece, October 2014. The [[original publication>>url:http://dx.doi.org/10.1007/978-3-662-45234-9||shape="rect"]](% style="color:#000000" %) is available at (%%)[[http:~~/~~/link.springer.com>>url:http://link.springer.com/||shape="rect"]](% style="color:#000000" %). (%%)[[pdf>>url:http://rtsys.informatik.uni-kiel.de/~~biblio/downloads/papers/isola14.pdf||shape="rect"]](% style="color:#000000" %), (%%)[[bib>>url:http://rtsys.informatik.uni-kiel.de/~~biblio/cgi-bin/bibcgi.cgi?key=MotikaSvH14||shape="rect"]]87 +(% style="color: rgb(0,0,0);" %)Christian Motika and Steven Smyth and Reinhard von Hanxleden. Compiling SCCharts—A Case-Study on Interactive Model-Based Compilation. In (% class="cmti-10" %)Proceedings of(%%) (% class="cmti-10" %)the 6th International Symposium on Leveraging Applications of Formal(%%) (% class="cmti-10" %)Methods, Verification and Validation (ISoLA 2014)(%%), volume 8802 of (% class="cmti-10" %)LNCS(%%), page 443–462, Corfu, Greece, October 2014. The [[original publication>>url:http://dx.doi.org/10.1007/978-3-662-45234-9||shape="rect"]](% style="color: rgb(0,0,0);" %) is available at (%%)[[http:~~/~~/link.springer.com>>url:http://link.springer.com/||shape="rect"]](% style="color: rgb(0,0,0);" %). (%%)[[pdf>>url:http://rtsys.informatik.uni-kiel.de/~~biblio/downloads/papers/isola14.pdf||shape="rect"]](% style="color: rgb(0,0,0);" %), (%%)[[bib>>url:http://rtsys.informatik.uni-kiel.de/~~biblio/cgi-bin/bibcgi.cgi?key=MotikaSvH14||shape="rect"]] 69 69 * **Theoretical Foundations:** 70 -(% style="color: #000000" %)Reinhard von Hanxleden and Michael Mendler and Joaquín Aguado and Björn Duderstadt and Insa Fuhrmann and Christian Motika and Stephen Mercer and Owen O’Brien and Partha Roop. Sequentially Constructive Concurrency—A Conservative Extension of the Synchronous Model of Computation. (% class="cmti-10" %)ACM Transactions on Embedded Computing(%%) (% class="cmti-10" %)Systems, Special Issue on Applications of Concurrency to System Design(%%), 13(4s):144:1–144:26, July 2014. [[pdf>>url:http://rtsys.informatik.uni-kiel.de/~~biblio/downloads/papers/tecs14.pdf||shape="rect"]](% style="color:#000000" %), (%%)[[bib>>url:http://rtsys.informatik.uni-kiel.de/~~biblio/cgi-bin/bibcgi.cgi?key=vonHanxledenMA+14||shape="rect"]]89 +(% style="color: rgb(0,0,0);" %)Reinhard von Hanxleden and Michael Mendler and Joaquín Aguado and Björn Duderstadt and Insa Fuhrmann and Christian Motika and Stephen Mercer and Owen O’Brien and Partha Roop. Sequentially Constructive Concurrency—A Conservative Extension of the Synchronous Model of Computation. (% class="cmti-10" %)ACM Transactions on Embedded Computing(%%) (% class="cmti-10" %)Systems, Special Issue on Applications of Concurrency to System Design(%%), 13(4s):144:1–144:26, July 2014. [[pdf>>url:http://rtsys.informatik.uni-kiel.de/~~biblio/downloads/papers/tecs14.pdf||shape="rect"]](% style="color: rgb(0,0,0);" %), (%%)[[bib>>url:http://rtsys.informatik.uni-kiel.de/~~biblio/cgi-bin/bibcgi.cgi?key=vonHanxledenMA+14||shape="rect"]] 71 71 * **Overview and High-Level Transformations in Detail:** 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.#000000" %), (%%)[[bib>>url:http://rtsys.informatik.uni-kiel.de/~~biblio/cgi-bin/bibcgi.cgi?key=vonHanxledenDM+13b||shape="rect"]]91 +(% 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"]] 73 73 93 +\\ 94 +{{/layout-cell}} 95 +{{/layout-section}} 96 + 97 +{{layout-section ac:type="two_right_sidebar"}} 98 +{{layout-cell}} 74 74 = The SCCharts Metamodel = 75 75 76 76 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. ... ... @@ -84,10 +84,10 @@ 84 84 ==== Model Task ==== 85 85 86 86 * ((( 87 -(% style="line-height:1.42857" %)Answer the following questions 112 +(% style="line-height: 1.42857;" %)Answer the following questions 88 88 89 89 1. How do you describe a superstate in the model? 90 -1. Outline the relationship between states, regions, transitions, and valued objects. 115 +1. Outline the relationship between states, regions, transitions, and valued objects.\\ 91 91 1. Name the class of the root element of an SCChart. 92 92 1. What is a valued object? 93 93 1. How do you get the type of an interface variable? ... ... @@ -101,17 +101,25 @@ 101 101 *1. Now, navigate to the //Super State: Strong Abort Transition //example. Write down (on paper) how the model of that SCCharts looks like. 102 102 *1. And finally a more sophisticated model: Write down the model of ABO (from [[doc:KIELER.Examples]]). 103 103 129 +\\ 130 + 104 104 {{info title="KLighD Screenshots"}} 105 105 By the way: You can //right-click// on the Diagram View surface and select //Save as image...// to create a screenshot! 106 106 {{/info}} 134 +{{/layout-cell}} 107 107 136 +{{layout-cell}} 108 108 [[image:attach:sccharts_metamodel.png]] 109 109 110 110 [[image:attach:sccharts_metamodel_treeEditor.png]] 111 111 112 112 [[image:attach:KLighDSaveAsImage.png]] 142 +{{/layout-cell}} 143 +{{/layout-section}} 113 113 114 -= Creating SCCharts Models Programmatically = 145 +{{layout-section ac:type="single"}} 146 +{{layout-cell}} 147 += Creating SCCharts Models Programmatically = 115 115 116 116 == Creating a Test Project == 117 117 ... ... @@ -206,23 +206,27 @@ 206 206 File extensions are important! They define the parser/serializer that EMF uses. Always use the file extension that is defined for a particular model. 207 207 {{/info}} 208 208 ))) 242 +{{/layout-cell}} 243 +{{/layout-section}} 209 209 245 +{{layout-section ac:type="two_right_sidebar"}} 246 +{{layout-cell}} 210 210 ==== Model Creation Task ==== 211 211 212 212 You are now equipped with the fundamentals you need to create models programmatically. Let's try it: 213 213 214 -* (% style="line-height:1.42857" %)The code fragments listed above do not suffice to create a grammatically correct model. Try to generate a model that corresponds with the serialized model listed on the right side. 215 -*1. (% style="line-height:1.42857" %)Run the {{code language="none"}}main(){{/code}} method by right-clicking its class and selecting //Run as// -> //Java Application//. Note that this runs your {{code language="none"}}main(){{/code}} method as a simple Java program, not a complete Eclipse application. EMF models can be used in any simple Java context, not just in Eclipse applications. 251 +* (% style="line-height: 1.42857;" %)The code fragments listed above do not suffice to create a grammatically correct model. Try to generate a model that corresponds with the serialized model listed on the right side. 252 +*1. (% style="line-height: 1.42857;" %)Run the {{code language="none"}}main(){{/code}} method by right-clicking its class and selecting //Run as// -> //Java Application//. Note that this runs your {{code language="none"}}main(){{/code}} method as a simple Java program, not a complete Eclipse application. EMF models can be used in any simple Java context, not just in Eclipse applications. 216 216 *1. Execute the main method. 217 217 *1. ((( 218 -(% style="line-height:1.42857" %)Inspect your SCT file. (Press F5 to refresh your file view.) 255 +(% style="line-height: 1.42857;" %)Inspect your SCT file. (Press F5 to refresh your file view.) 219 219 220 -{{ info title="Kext Warning"}}257 +{{note title="Kext Warning"}} 221 221 It is possible that kext generates a Null Pointer Exception when you save your model this way. This is a known issue. We're working on it. Just ignore it for now. 222 -{{/ info}}259 +{{/note}} 223 223 ))) 224 224 * Now, create a new Java class and proceed as before to generate a model of ABO in the {{code language="none"}}main(){{/code}} method. 225 -* (% style="line-height:1.42857" %)Start your SCChart Editor Eclipse instance and load your SCT file. KLighD should now be able to visualize your ABO correctly. 262 +* (% style="line-height: 1.42857;" %)Start your SCChart Editor Eclipse instance and load your SCT file. KLighD should now be able to visualize your ABO correctly.(%%)\\ 226 226 *1. For this, open tab //Run// and select// Run Configurations...// 227 227 *1. Create a new //Eclipse Application// and name it appropriately. 228 228 *1. As product select {{code language="none"}}de.cau.cs.kieler.core.product.product{{/code}}. ... ... @@ -229,6 +229,10 @@ 229 229 *1. Click //Run// (or //Debug// if you opened// Debug Configuration...//) 230 230 *1. Create a new project and add you generated model. 231 231 269 +\\ 270 +{{/layout-cell}} 271 + 272 +{{layout-cell}} 232 232 {{code language="java" title="Root.sct"}} 233 233 scchart Root { 234 234 initial state Init ... ... @@ -237,7 +237,11 @@ 237 237 {{/code}} 238 238 239 239 [[image:attach:RunConfiguration.png]] 281 +{{/layout-cell}} 282 +{{/layout-section}} 240 240 284 +{{layout-section ac:type="two_right_sidebar"}} 285 +{{layout-cell}} 241 241 = Model-to-Model Transformations with KiCo = 242 242 243 243 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. ... ... @@ -245,9 +245,15 @@ 245 245 == Creating a new Transformation == 246 246 247 247 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. :) 293 +{{/layout-cell}} 248 248 295 +{{layout-cell}} 249 249 [[image:attach:KielerSCTEditor.png]] 297 +{{/layout-cell}} 298 +{{/layout-section}} 250 250 300 +{{layout-section ac:type="two_right_sidebar"}} 301 +{{layout-cell}} 251 251 ==== Transformation Creation Task ==== 252 252 253 253 * Create your first transformation... ... ... @@ -292,7 +292,15 @@ 292 292 You should really think about some constants here. You can also look at the sccharts transformation and features constants in the sccharts plugin. 293 293 {{/info}} 294 294 ))) 346 +{{/layout-cell}} 295 295 348 +{{layout-cell}} 349 +\\ 350 +{{/layout-cell}} 351 +{{/layout-section}} 352 + 353 +{{layout-section ac:type="two_right_sidebar"}} 354 +{{layout-cell}} 296 296 * KiCo must know about the new feature and also about your new transformation. 297 297 *1. Add a new Xtend class with Feature as superclass. Add all unimplemented methods. Also set** sccharts.doubleStates** as Id. 298 298 *1. Go to the Extension tab inside your plugin configuration. ... ... @@ -304,11 +304,17 @@ 304 304 *111. label: Tutorial Compilation 305 305 *111. priority: 101 306 306 *111. preferred: (leave it blank) 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.366 +*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. 308 308 * 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. 368 +{{/layout-cell}} 309 309 370 +{{layout-cell}} 310 310 [[image:attach:KielerSCTEditorOwnTransformation.png]] 372 +{{/layout-cell}} 373 +{{/layout-section}} 311 311 375 +{{layout-section ac:type="two_right_sidebar"}} 376 +{{layout-cell}} 312 312 * Now, fill your transformation with life: 313 313 *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. 314 314 *1. ((( ... ... @@ -343,11 +343,15 @@ 343 343 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. 344 344 {{/note}} 345 345 ))) 411 +{{/layout-cell}} 346 346 413 +{{layout-cell}} 347 347 [[image:attach:KielerSCTEditorOwnTransformationOlolo.png]] 415 +{{/layout-cell}} 416 +{{/layout-section}} 348 348 349 - 350 - 418 +{{layout-section ac:type="two_right_sidebar"}} 419 +{{layout-cell}} 351 351 * 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. 352 352 353 353 == The existing Compilation Chain == ... ... @@ -358,11 +358,22 @@ 358 358 359 359 //We will add more content to this subsection in the future...// 360 360 430 +\\ 431 +{{/layout-cell}} 361 361 433 +{{layout-cell}} 362 362 [[image:attach:ABODoubleStates.png]] 363 363 436 +\\ 364 364 438 +\\ 365 365 440 +\\ 441 +{{/layout-cell}} 442 +{{/layout-section}} 443 + 444 +{{layout-section ac:type="single"}} 445 +{{layout-cell}} 366 366 = Model-to-Model Transformations between Metamodels = 367 367 368 368 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. ... ... @@ -408,13 +408,23 @@ 408 408 [[image:attach:abo_scg_HandleA.png]] 409 409 ))) 410 410 ))) 491 +{{/layout-cell}} 492 +{{/layout-section}} 411 411 494 +{{layout-section ac:type="two_equal"}} 495 +{{layout-cell}} 412 412 The next figure depicts the direct mapping from normalized SCCharts to their corresponding SCG. 413 413 414 414 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, 499 +{{/layout-cell}} 415 415 501 +{{layout-cell}} 416 416 [[image:attach:sccharts-scg.png]] 503 +{{/layout-cell}} 504 +{{/layout-section}} 417 417 506 +{{layout-section ac:type="two_right_sidebar"}} 507 +{{layout-cell}} 418 418 ==== Transformation Creation Task 2 ==== 419 419 420 420 Write a transformation that transforms your normalized version of ABO's HandleA into its corresponding SCG. ... ... @@ -427,4 +427,15 @@ 427 427 *1. Optimize the given SCG and compare the result with the previous one. 428 428 *1. Make sure that the two SCGs are still semantically identical. 429 429 520 +\\ 521 + 430 430 Congratulations! You finished the SCCharts Development Tutorial. Ask your supervisor for further instructions! 523 + 524 +\\ 525 +{{/layout-cell}} 526 + 527 +{{layout-cell}} 528 +\\ 529 +{{/layout-cell}} 530 +{{/layout-section}} 531 +{{/layout}}