Wiki source code of SCCharts Development
Version 11.1 by ssm on 2016/04/21 16:56
Hide last authors
| author | version | line-number | content |
|---|---|---|---|
 |
7.1 | 1 | {{layout}} |
| 2 | {{layout-section ac:type="single"}} | ||
| 3 | {{layout-cell}} | ||
| 4 | |||
| 5 | |||
| |
5.1 | 6 | This is a light-weight tutorial for developing 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. |
| |
1.1 | 7 | |
| 8 | = Preliminaries = | ||
| 9 | |||
| 10 | There's a few things to do before we dive into the tutorial itself. For example, to do Eclipse programming, you will have to get your hands on an Eclipse installation first. Read through the following sections to get ready for the tutorial tasks. | ||
| 11 | |||
| 12 | == Required Software == | ||
| 13 | |||
| 14 | As you're going to develop for KIELER SCCharts we recommend to use the semantic 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. | ||
| |
7.1 | 15 | {{/layout-cell}} |
| 16 | {{/layout-section}} | ||
| |
1.1 | 17 | |
| |
8.1 | 18 | {{layout-section ac:type="three_equal"}} |
| |
7.1 | 19 | {{layout-cell}} |
| |
11.1 | 20 | |
| 21 | |||
| |
7.1 | 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. |
| |
8.1 | 23 | |
| 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 | ||
| 25 | |||
| 26 | * KIELER Lightweight Diagrams - Developer Resources and | ||
| 27 | * KIELER Lightweight Diagrams Generic Diagram View. | ||
| 28 | |||
| 29 | (This step should be obsolete in the near future.) | ||
| |
7.1 | 30 | {{/layout-cell}} |
| |
1.1 | 31 | |
| |
7.1 | 32 | {{layout-cell}} |
| |
11.1 | 33 | |
| 34 | |||
| |
7.1 | 35 | [[image:attach:InstallEcoreViz.png]] |
| 36 | {{/layout-cell}} | ||
| |
8.1 | 37 | |
| 38 | {{layout-cell}} | ||
| |
11.1 | 39 | |
| 40 | |||
| |
8.1 | 41 | [[image:attach:InstallKLighDFeatures.png]] |
| 42 | {{/layout-cell}} | ||
| |
7.1 | 43 | {{/layout-section}} |
| 44 | |||
| 45 | {{layout-section ac:type="single"}} | ||
| 46 | {{layout-cell}} | ||
| |
1.1 | 47 | == Recommended Tutorials == |
| 48 | |||
| 49 | 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. | ||
| 50 | |||
| 51 | 1. [[doc:Eclipse Plug-ins and Extension Points]] | ||
| 52 | 1. [[doc:Eclipse Modeling Framework (EMF)]] | ||
| 53 | 11. This tutorial needs the turingmachine.ecore and the controller you've implemented in the EMF tutorial. If you did not complete the EMF tutorial, you may download a working turing machine here... (in the future). | ||
| 54 | 1. ((( | ||
| 55 | (% class="with-breadcrumbs" %) | ||
| 56 | [[Xtend 2 - Model Transformations>>url:http://rtsys.informatik.uni-kiel.de/confluence/display/TUT/Xtend+2+-+Model+Transformations||shape="rect"]] | ||
| 57 | ))) | ||
| 58 | |||
| 59 | == Helpful Tutorials == | ||
| 60 | |||
| 61 | When developing within the KIELER semantics team, you will most likely be confronted with Xtext and [[doc:KIELER.Lightweight Diagrams (KLighD)]]. The following tutorials may be helpful but not required for this tutorial. | ||
| 62 | |||
| 63 | 1. [[doc:Xtext 2 - Creating a Grammar from Scratch]] | ||
| 64 | 1. [[doc:Lightweight Diagrams (KLighD)]] | ||
| 65 | |||
| 66 | == Finding Documentation == | ||
| 67 | |||
| |
5.1 | 68 | You can find additional documentation to the aforementioned topics in the corresponding tutorials. If you get stuck with a particular topic, please consult that tutorial. For SCCharts, you should read the SCCharts confluence page in our wiki: [[doc:KIELER.SCCharts]] |
| |
1.1 | 69 | |
| 70 | As usual, documentation often gets obsolete or wrong if not maintained regularly, so please, if you find missing, misleading, or outdated information, please let us know. | ||
| 71 | |||
| 72 | Additionally, the following list will give a short overview over the most important publications: | ||
| 73 | |||
| 74 | * (% style="color: rgb(0,0,0);" %)**Main paper:** | ||
| 75 | 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"]] | ||
| 76 | * **SLIC Compilation:** | ||
| 77 | (% 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"]] | ||
| 78 | * **Theoretical Foundations:** | ||
| 79 | (% 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"]] | ||
| 80 | * **Overview and High-Level Transformations in Detail:** | ||
| 81 | (% 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"]] | ||
| |
9.1 | 82 | {{/layout-cell}} |
| 83 | {{/layout-section}} | ||
| |
1.1 | 84 | |
| |
9.1 | 85 | {{layout-section ac:type="two_right_sidebar"}} |
| 86 | {{layout-cell}} | ||
| |
1.1 | 87 | = The SCCharts Metamodel = |
| 88 | |||
| |
9.1 | 89 | 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. |
| |
1.1 | 90 | |
| 91 | Try to understand most parts of the metamodel. You don't have to understand every detail but you should get the idea. | ||
| 92 | |||
| 93 | ==== Model Task ==== | ||
| 94 | |||
| |
9.1 | 95 | 1. Answer the following questions |
| 96 | 11. Name the class of the root element of an SCChart | ||
| 97 | 11. How do you describe a superstate in the model? | ||
| 98 | 11. What is a valued object? | ||
| 99 | 11. How do you get the type of an interface variable? | ||
| |
5.1 | 100 | 11. Outline the relationship between states, regions, transitions, and valued objects |
| |
9.1 | 101 | 11. What other metamodels are needed for the SCCharts metamodel and write down which one is needed for what? |
| 102 | 1. Write down (on paper, text editor, etc) how the following SCChart models look like | ||
| 103 | 11. Open the wiki page that explains the [[doc:KIELER.Textual SCCharts Language SCT]]. | ||
| 104 | 11. Search the //SCChart, Initial State, State, Transition and Immediate Transition //example and ... | ||
| |
5.1 | 105 | 111. write down (on paper or text editor, etc) how the model of that SCChart looks like. |
| 106 | 111. The user now marks C as final. What has to be changed in the model? What semantic problem do you see? | ||
| |
9.1 | 107 | 11. Now, navigate to the //Super State: Strong Abort Transition //example. Write down (on paper) how the model of that SCCharts looks like. |
| |
5.1 | 108 | 11. And finally a more sophisticated model: Write down the model of ABO (from [[doc:KIELER.Examples]]). |
| |
4.1 | 109 | |
| |
9.1 | 110 | |
| 111 | |||
| 112 | {{info title="KLighD Screenshots"}} | ||
| 113 | By the way: You can //right-click// on the Diagram View surface to select //Save as image...// to create a screenshot! | ||
| 114 | {{/info}} | ||
| 115 | {{/layout-cell}} | ||
| 116 | |||
| 117 | {{layout-cell}} | ||
| |
10.1 | 118 | |
| 119 | |||
| 120 | |||
| 121 | |||
| |
9.1 | 122 | [[image:attach:sccharts_metamodel.png]] |
| 123 | |||
| 124 | |||
| 125 | |||
| 126 | |||
| 127 | |||
| 128 | |||
| 129 | |||
| 130 | |||
| 131 | |||
| 132 | [[image:attach:KLighDSaveAsImage.png]] | ||
| 133 | {{/layout-cell}} | ||
| 134 | {{/layout-section}} | ||
| 135 | |||
| 136 | {{layout-section ac:type="single"}} | ||
| 137 | {{layout-cell}} | ||
| 138 | |||
| 139 | |||
| 140 | |||
| 141 | {{/layout-cell}} | ||
| 142 | {{/layout-section}} | ||
| 143 | |||
| 144 | {{layout-section ac:type="single"}} | ||
| 145 | {{layout-cell}} | ||
| 146 | |||
| 147 | {{/layout-cell}} | ||
| 148 | {{/layout-section}} | ||
| 149 | |||
| 150 | {{layout-section ac:type="single"}} | ||
| 151 | {{layout-cell}} | ||
| |
4.1 | 152 | = Creating SCCharts Models Programmatically = |
| 153 | |||
| 154 | == Creating a Test Project == | ||
| 155 | |||
| 156 | We need a project for testing. Do the following: | ||
| 157 | |||
| 158 | 1. Create a new empty //Plug-In Project//. | ||
| 159 | 1. Add the project that contains the sccharts metamodel as a dependency of your new project through the //Plugin Manifest Editor//. | ||
| 160 | 1. Create a simple Java class that implements a main method. Hint: In a new Java class, simply type main and hit Ctrl+Space. Eclipse content assist will create the method for you. | ||
| 161 | |||
| 162 | == Creating a Model == | ||
| 163 | |||
| 164 | To create a model programmatically you cannot directly use the Java classes generated for the model. Instead, the main package contains interfaces for all of your model object classes. The {{code language="none"}}impl{{/code}} package contains the actual implementation and the {{code language="none"}}util{{/code}} package contains some helper classes. Do not instantiate objects directly by manually calling {{code language="none"}}new{{/code}}. EMF generates a Factory to create new objects. The factory itself uses the singleton pattern to get access to it: | ||
| 165 | |||
| 166 | {{code language="java"}} | ||
| 167 | SCChartsFactory sccFactory = SCChartsFactory.eINSTANCE; | ||
| 168 | State state = sccFactory .createState(); | ||
| 169 | Transition transition = sccFactory .createTransition(); | ||
| 170 | {{/code}} | ||
| 171 | |||
| 172 | Important: The SCCharts grammar is build on top of several other grammars. Therefore, not all language objects can be found in the SCCharts factory. For example, all expression elements are part of the KExpressions grammar and hence, have their own factory. If you need other factories, don't forget to add the corresponding plugin to your plugin dependency list. | ||
| 173 | |||
| 174 | {{code language="java"}} | ||
| 175 | KExpressionsFactory kFactory = KExpressionsFactory.eINSTANCE; | ||
| 176 | BooleanValue boolValue = kFactory.createBooleanValue(); | ||
| 177 | {{/code}} | ||
| 178 | |||
| 179 | For all simple attributes, there are getter and setter methods: | ||
| 180 | |||
| 181 | {{code language="java"}} | ||
| 182 | state.setId("Root"); | ||
| 183 | boolValue.setValue(true); | ||
| 184 | {{/code}} | ||
| 185 | |||
| 186 | Simple references (multiplicity of 1) also have getters and setters: | ||
| 187 | |||
| 188 | {{code language="java"}} | ||
| 189 | transition.setTrigger(boolValue); | ||
| 190 | {{/code}} | ||
| 191 | |||
| 192 | List references (multiplicity of > 1) have only a list getter, which is used to manipulate the list: | ||
| 193 | |||
| 194 | {{code language="java"}} | ||
| 195 | state.outgoingTransitions.add(transition); | ||
| 196 | {{/code}} | ||
| 197 | |||
| 198 | == Saving a Model == | ||
| 199 | |||
| 200 | EMF uses the [[Eclipse Resource concept>>url:http://help.eclipse.org/juno/topic/org.eclipse.platform.doc.isv/guide/resInt.htm?cp=2_0_10||rel="nofollow" shape="rect" class="external-link"]] to save models to files and load models from files. It can use different //Resource Factories// that determine how exactly models are serialized. We will use the [[XMIResourceFactoryImpl>>url:http://download.eclipse.org/modeling/emf/emf/javadoc/2.8.0/org/eclipse/emf/ecore/xmi/impl/XMIResourceFactoryImpl.html||rel="nofollow" shape="rect" class="external-link"]] to save our models to XML files: | ||
| 201 | |||
| 202 | 1. Add a dependency to the {{code language="none"}}org.eclipse.emf.ecore.xmi{{/code}} plug-in. | ||
| 203 | 1. ((( | ||
| 204 | Use something like the following code to save the model from above: | ||
| 205 | |||
| 206 | {{code language="java"}} | ||
| 207 | // Create a resource set. | ||
| 208 | ResourceSet resourceSet = new ResourceSetImpl(); | ||
| 209 | |||
| 210 | // Register the default resource factory -- only needed for stand-alone! | ||
| 211 | // this tells EMF to use XML to save the model | ||
| 212 | resourceSet.getResourceFactoryRegistry().getExtensionToFactoryMap().put( | ||
| 213 | Resource.Factory.Registry.DEFAULT_EXTENSION, new SCTResourceFactoryImpl()); | ||
| 214 | // Get the URI of the model file. | ||
| 215 | URI fileURI = URI.createFileURI(new File("myABO.sct").getAbsolutePath()); | ||
| 216 | |||
| 217 | // Create a resource for this file. | ||
| 218 | Resource resource = resourceSet.createResource(fileURI); | ||
| 219 | |||
| 220 | // Add the model objects to the contents. | ||
| 221 | resource.getContents().add(myModel); | ||
| 222 | |||
| 223 | // Save the contents of the resource to the file system. | ||
| 224 | try | ||
| 225 | { | ||
| 226 | resource.save(Collections.EMPTY_MAP); // the map can pass special saving options to the operation | ||
| 227 | } catch (IOException e) { | ||
| 228 | /* error handling */ | ||
| 229 | } | ||
| 230 | {{/code}} | ||
| 231 | ))) | ||
| 232 | |||
| 233 | ==== Model Creation Task ==== | ||
| 234 | |||
| 235 | With these information out of the way, on we go to some model creation: | ||
| 236 | |||
| 237 | 1. Programmatically create a valid model of ABO in the {{code language="none"}}main(){{/code}} method. | ||
| 238 | 1. 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. | ||
| 239 | 1. Execute the main method. | ||
| 240 | 1. Inspect your SCT file. | ||
| 241 | 1. Start your SCChart Editor Eclipse instance and load your SCT file. KLighD should now be able to visualize your ABO correctly. | ||
| 242 | |||
| 243 | = Transforming SCCharts = | ||
| 244 | |||
| 245 | 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). Both is possible. Just make sure that you know what you're doing. | ||
| 246 | |||
| 247 | Now, you're going to transform the normalized form of HandleA from ABO to an SCG. The Sequentially Constructive Graph is a control-flow graph which can be seen as another representation of the same program. The SCG of the normalized version of ABO's HandleA is depicted on the right. | ||
| 248 | |||
| 249 | |((( | ||
| 250 | {{code}} | ||
| 251 | scchart ABO_norm_HandleA { | ||
| 252 | input output bool A; | ||
| 253 | input output bool B; | ||
| 254 | output bool O1; | ||
| 255 | output bool O2; | ||
| 256 | region HandleA: | ||
| 257 | initial state WaitA | ||
| 258 | --> _S immediate with A | ||
| 259 | --> _Pause immediate; | ||
| 260 | final state DoneA; | ||
| 261 | state _S | ||
| 262 | --> _S2 immediate with / B = true; | ||
| 263 | state _S2 | ||
| 264 | --> DoneA immediate with / O1 = true; | ||
| 265 | state _Pause | ||
| 266 | --> _Depth; | ||
| 267 | state _Depth | ||
| 268 | --> _S immediate with A | ||
| 269 | --> _Pause immediate; | ||
| 270 | } | ||
| 271 | {{/code}} | ||
| 272 | )))|((( | ||
| 273 | [[image:attach:abo_norm_HandleA.png]] | ||
| 274 | )))|(% colspan="1" %)(% colspan="1" %) | ||
| 275 | ((( | ||
| 276 | [[image:attach:abo_scg_HandleA.png]] | ||
| 277 | ))) | ||
| 278 | |||
| 279 | The next figure depicts the direct mapping from normalized SCCharts to their corresponding SCG. | ||
| 280 | |||
| 281 | [[image:attach:sccharts-scg.png]] | ||
| 282 | |||
| 283 | 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, | ||
| 284 | |||
| 285 | ==== Transformation Task ==== | ||
| 286 | |||
| 287 | Write a transformation that transforms your normalized version of ABO's HandleA into its corresponding SCG. | ||
| 288 | |||
| 289 | 1. ((( | ||
| 290 | **Writing a Model Transformation** | ||
| 291 | |||
| 292 | This time we want you to integrate your transformation into your SCCharts Editor instance. Therefore,... | ||
| 293 | (% style="color: rgb(51,51,51);line-height: 1.66667;" %)\\ | ||
| 294 | |||
| 295 | 1. Add a new package | ||
| 296 | |||
| 297 | {{code language="none"}} | ||
| 298 | <project>.transformations | ||
| 299 | {{/code}} to your project. | ||
| 300 | 1. Add an //Xtend Class// to the new package. | ||
| 301 | 1. If you notice that your new class is marked with an error marker because of a missing dependency of the new plug-in project to | ||
| 302 | |||
| 303 | {{code language="none"}} | ||
| 304 | org.eclipse.xtext.xbase.lib, | ||
| 305 | {{/code}}you can hover over the error with your mouse and have Eclipse add all libraries required by Xtend to your project. | ||
| 306 | 1. | ||
| 307 | |||
| 308 | Define an entry method for the transformation that takes an SCChart program instance as an argument and returns an SCG {{code language="none"}}Program{{/code}}. You can use the following (incomplete) method as a starting point: | ||
| 309 | |||
| 310 | ((( | ||
| 311 | (% class="syntaxhighlighter sh-confluence nogutter java" %) | ||
| 312 | ((( | ||
| 313 | |||
| 314 | |||
| 315 | |((( | ||
| 316 | (% class="container" title="Hint: double-click to select code" %) | ||
| 317 | ((( | ||
| 318 | (% class="line number1 index0 alt2" %) | ||
| 319 | ((( | ||
| 320 | {{code language="none"}} | ||
| 321 | /** | ||
| 322 | {{/code}} | ||
| 323 | ))) | ||
| 324 | |||
| 325 | (% class="line number2 index1 alt1" %) | ||
| 326 | ((( | ||
| 327 | {{code language="none"}} | ||
| 328 | |||
| 329 | {{/code}} | ||
| 330 | |||
| 331 | {{code language="none"}} | ||
| 332 | * Transforms a given SCCharts program into an SCG. | ||
| 333 | {{/code}} | ||
| 334 | ))) | ||
| 335 | |||
| 336 | (% class="line number3 index2 alt2" %) | ||
| 337 | ((( | ||
| 338 | {{code language="none"}} | ||
| 339 | |||
| 340 | {{/code}} | ||
| 341 | |||
| 342 | {{code language="none"}} | ||
| 343 | * | ||
| 344 | {{/code}} | ||
| 345 | ))) | ||
| 346 | |||
| 347 | (% class="line number4 index3 alt1" %) | ||
| 348 | ((( | ||
| 349 | {{code language="none"}} | ||
| 350 | */ | ||
| 351 | {{/code}} | ||
| 352 | ))) | ||
| 353 | |||
| 354 | (% class="line number8 index7 alt1" %) | ||
| 355 | ((( | ||
| 356 | {{code language="none"}} | ||
| 357 | def SCGraph transform(State rootState) { | ||
| 358 | {{/code}} | ||
| 359 | ))) | ||
| 360 | |||
| 361 | (% class="line number9 index8 alt2" %) | ||
| 362 | ((( | ||
| 363 | {{code language="none"}} | ||
| 364 | |||
| 365 | {{/code}} | ||
| 366 | |||
| 367 | {{code language="none"}} | ||
| 368 | // Create the SCG | ||
| 369 | {{/code}} | ||
| 370 | ))) | ||
| 371 | |||
| 372 | (% class="line number10 index9 alt1" %) | ||
| 373 | ((( | ||
| 374 | {{code language="none"}} | ||
| 375 | |||
| 376 | {{/code}} | ||
| 377 | |||
| 378 | {{code language="none"}} | ||
| 379 | val scg = SCGraphFactory::eINSTANCE.createSCGraph() | ||
| 380 | {{/code}} | ||
| 381 | ))) | ||
| 382 | |||
| 383 | (% class="line number11 index10 alt2" %) | ||
| 384 | ((( | ||
| 385 | {{code language="none"}} | ||
| 386 | |||
| 387 | {{/code}} | ||
| 388 | ))) | ||
| 389 | |||
| 390 | (% class="line number12 index11 alt1" %) | ||
| 391 | ((( | ||
| 392 | {{code language="none"}} | ||
| 393 | |||
| 394 | {{/code}} | ||
| 395 | |||
| 396 | {{code language="none"}} | ||
| 397 | // TODO: Your transformation code | ||
| 398 | {{/code}} | ||
| 399 | ))) | ||
| 400 | |||
| 401 | (% class="line number13 index12 alt2" %) | ||
| 402 | ((( | ||
| 403 | {{code language="none"}} | ||
| 404 | |||
| 405 | {{/code}} | ||
| 406 | ))) | ||
| 407 | |||
| 408 | (% class="line number14 index13 alt1" %) | ||
| 409 | ((( | ||
| 410 | {{code language="none"}} | ||
| 411 | |||
| 412 | {{/code}} | ||
| 413 | |||
| 414 | {{code language="none"}} | ||
| 415 | // Return the transformed program | ||
| 416 | {{/code}} | ||
| 417 | ))) | ||
| 418 | |||
| 419 | (% class="line number15 index14 alt2" %) | ||
| 420 | ((( | ||
| 421 | {{code language="none"}} | ||
| 422 | scg | ||
| 423 | {{/code}} | ||
| 424 | ))) | ||
| 425 | |||
| 426 | (% class="line number16 index15 alt1" %) | ||
| 427 | ((( | ||
| 428 | {{code language="none"}} | ||
| 429 | } | ||
| 430 | {{/code}} | ||
| 431 | ))) | ||
| 432 | ))) | ||
| 433 | ))) | ||
| 434 | |||
| 435 | |||
| 436 | ))) | ||
| 437 | ))) | ||
| 438 | |||
| 439 | ((( | ||
| 440 | (% class="syntaxhighlighter nogutter java" %) | ||
| 441 | ((( | ||
| 442 | There's a few points to note here: | ||
| 443 | ))) | ||
| 444 | ))) | ||
| 445 | |||
| |
1.1 | 446 | \\ |
| |
4.1 | 447 | |
| 448 | 1. | ||
| 449 | 1*. Lines in Xtend code don't have to and with a semicolon. | ||
| 450 | 1*. We have been explicit about the method's return type, but we could have easily omitted it, letting Xtend infer the return type. | ||
| 451 | 1*. The keyword | ||
| 452 | |||
| 453 | {{code language="none"}} | ||
| 454 | val | ||
| 455 | {{/code}} declares a constant, while | ||
| 456 | |||
| 457 | {{code language="none"}} | ||
| 458 | var | ||
| 459 | {{/code}} declares a variable. Try to make do with constants where possible. | ||
| 460 | 1*. The methods you call should be declared as | ||
| 461 | |||
| 462 | {{code language="none"}} | ||
| 463 | def private | ||
| 464 | {{/code}} since they are implementation details and shouldn't be called by other classes. | ||
| 465 | 1*. You may be tempted to add a few global variables that hold things like a global input variable or a pointer to the current state. While you could to that, | ||
| 466 | |||
| 467 | {{code language="none"}} | ||
| 468 | def create | ||
| 469 | {{/code}}methods might offer a better alternative... | ||
| 470 | \\ | ||
| 471 | 1. Replace the TODO with an transformation code that takes an extended BF program and transforms it into an semantically equivalent BF program that only uses standard BF instructions. | ||
| 472 | HINT: Some of the extended BF commands can only be expressed by standard operations if you can write to other cells. Therefore you are allowed to perform side effects on the tape. | ||
| 473 | 1. Open the //Plug-In Manifest Editor// and switch to the Runtime tab. Add the package containing your transformation to the list of exported packages. (You may have to check the //Show non-Java packages// option in the //Exported Packages// dialog to see the package.) | ||
| 474 | \\ | ||
| 475 | ))) | ||
| 476 | 1. **Verify your generated SCG**. If you added your transformation correctly, the SCG should be displayed automatically as soon as selected. If your SCG looks like the SCG depicted earlier, then everything is fine. | ||
| 477 | 1. Check your SCG semantically. Is there anything you could improve/optimize? | ||
| 478 | 11. Write a second transformation (just as before) and add it to the transformation chain right after the transformation you already added. | ||
| 479 | 11. Optimize the given SCG and compare the result with the previous one. | ||
| 480 | 11. Make sure that the two SCGs are still semantically identical. | ||
| 481 | |||
| 482 | Congratulations! You finished the SCCharts Development Tutorial. Ask your supervisor for further instructions! | ||
| 483 | |||
| 484 | |||
| |
7.1 | 485 | {{/layout-cell}} |
| 486 | {{/layout-section}} | ||
| 487 | {{/layout}} |