SCCharts Development

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.

5

6

7

The KiCo part "Model-to-Model Transformations with KiCo" is outdated. We will update this tutorials in the near future.

\\

= Preliminaries =

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.

19

20

== Required Software ==

21

22

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.

\\

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.

31

32

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

33

34

* KIELER Lightweight Diagrams - Developer Resources and

35

* KIELER Lightweight Diagrams Generic Diagram View.

36

37

(This step should be obsolete in the near future.)

\\

[[image:attach:InstallEcoreViz.png]]

\\

\\

[[image:attach:InstallKLighDFeatures.png]]

== Recommended Tutorials ==

58

59

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.

60

61

1. [[doc:TUT.Tutorials.Eclipse.Eclipse Plug-ins and Extension Points.WebHome]]

62

1. [[doc:TUT.Tutorials.Eclipse.Eclipse Modeling Framework (EMF).WebHome]]

63

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).

64

1. (((

65

(% class="with-breadcrumbs" %)

66

[[Xtend 2 - Model Transformations>>url:http://rtsys.informatik.uni-kiel.de/confluence/display/TUT/Xtend+2+-+Model+Transformations||shape="rect"]]

67

)))

68

69

== Helpful Tutorials ==

70

71

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.

72

73

1. [[doc:TUT.Tutorials.Xtext and Xtend.Xtext 2 - Creating a Grammar from Scratch.WebHome]]

74

1. [[doc:Kieler.Tutorials.Diagrams and Layout.Lightweight Diagrams (KLighD).WebHome]]

75

76

== Finding Documentation ==

77

78

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 (pre 1\.0)]]

79

80

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.

81

82

Additionally, the following list will give a short overview over the most important publications:

83

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"]]

86

* **SLIC Compilation:**

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"]]

88

* **Theoretical Foundations:**

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"]]

90

* **Overview and High-Level Transformations in Detail:**

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"]]

\\

= The SCCharts Metamodel =

100

101

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

103

To see all class information check //Attributes/Literals// in the Diagram Options on the right.

104

105

EcoreViz gives you an overview over the selected Ecore diagram. However, Ecore model definitions may depend on other Ecore definitions that are not displayed in the diagram. You can open new diagrams for these Ecore files as described before or use the Ecore tree editor to inspect all classes.

106

107

Try to understand most parts of the metamodel. You don't have to understand every detail but you should get the idea.

==== Model Task ====

* (((

(% style="line-height: 1.42857;" %)Answer the following questions

113

114

1. How do you describe a superstate in the model?

115

1. Outline the relationship between states, regions, transitions, and valued objects.\\

116

1. Name the class of the root element of an SCChart.

117

1. What is a valued object?

118

1. How do you get the type of an interface variable?

119

1. What other metamodels are needed for the SCCharts metamodel and write down which one is needed for what?

120

)))

121

* Write down (on paper, text editor, etc) how the following SCChart models look like

122

*1. Open the wiki page that explains the [[doc:KIELER.Textual SCCharts Language SCT]].

123

*1. Search the //SCChart, Initial State, State, Transition and Immediate Transition //example and ...

124

*11. write down (on paper or text editor, etc) how the model of that SCChart looks like.

125

*11. The user now marks C as final. What has to be changed in the model? What semantic problem do you see?

126

*1. Now, navigate to the //Super State: Strong Abort Transition //example. Write down (on paper) how the model of that SCCharts looks like.

127

*1. And finally a more sophisticated model: Write down the model of ABO (from [[doc:KIELER.Examples]]).

\\

By the way: You can //right-click// on the Diagram View surface and select //Save as image...// to create a screenshot!

[[image:attach:sccharts_metamodel.png]]

138

139

[[image:attach:sccharts_metamodel_treeEditor.png]]

140

141

[[image:attach:KLighDSaveAsImage.png]]

= Creating SCCharts Models Programmatically =

148

149

== Creating a Test Project ==

150

151

We need a project for testing. Do the following:

152

153

* If you used the standard KIELER Oomph installation setup, create a new Working Set named Tutorial in the Package Explorer. Then...

154

* Create a new empty //Plug-In Project//.

155

* Add the project that contains the sccharts metamodel as a dependency of your new project through the //Plugin Manifest Editor//.

156

* 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.

157

158

== Creating a Model ==

159

160

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:

161

162

163

SCChartsFactory sccFactory = SCChartsFactory.eINSTANCE;

164

State state = sccFactory.createState();

165

Transition transition = sccFactory.createTransition();

166

167

168

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.

169

170

171

KExpressionsFactory kFactory = KExpressionsFactory.eINSTANCE;

172

BoolValue boolValue = kFactory.createBoolValue();

173

174

175

For all simple attributes, there are getter and setter methods:

state.setId("Init");

boolValue.setValue(true);

180

181

182

Simple references (multiplicity of 1) also have getters and setters:

183

184

185

transition.setTrigger(boolValue);

186

187

188

List references (multiplicity of > 1) have only a list getter, which is used to manipulate the list:

189

190

191

state.getOutgoingTransitions().add(transition);

You may have noticed that is was not necessary to add a dependency for the kexpressions classes. The SCCharts plugin reexports the dependencies of the other EMF metamodels. Look at the plugin.xml in the SCCharts plugin in the dependency tab for more information.

== Saving a Model ==

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

* (((

203

Add a dependency to the {{code language="none"}}com.google.inject, org.eclipse.core.resources, {{/code}}and{{code language="none"}} de.cau.cs.kieler.sccharts.text{{/code}} plug-ins.

204

205

206

Don't worry. You will be experienced enough to add mandatory dependencies quickly in the future. However, for now just add the dependencies to proceed with the tutorial.

)))

* (((

Use something like the following code to save the model from above:

211

212

213

// Create a resource set.

214

ResourceSet resourceSet = new ResourceSetImpl();

215

216

// Register the resource factory -- only needed for stand-alone!

217

SctStandaloneSetup.doSetup();

218

219

220

// Get the URI of the model file.

221

URI fileURI = URI.createFileURI(new File("myABO.sct").getAbsolutePath());

222

223

// Create a resource for this file.

224

Resource resource = resourceSet.createResource(fileURI);

225

226

// Add the model objects to the contents. Usually, this is the root node of the model.

227

resource.getContents().add(myModel);

228

229

// Save the contents of the resource to the file system.

230

try

231

{

232

resource.save(Collections.EMPTY_MAP); // the map can pass special saving options to the operation

233

} catch (IOException e) {

/* error handling */

}

File extensions are important! They define the parser/serializer that EMF uses. Always use the file extension that is defined for a particular model.

)))

==== Model Creation Task ====

248

249

You are now equipped with the fundamentals you need to create models programmatically. Let's try it:

250

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.

253

*1. Execute the main method.

254

*1. (((

255

(% style="line-height: 1.42857;" %)Inspect your SCT file. (Press F5 to refresh your file view.)

256

257

258

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.

259

260

)))

261

* Now, create a new Java class and proceed as before to generate a model of ABO in the {{code language="none"}}main(){{/code}} method.

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.(%%)\\

263

*1. For this, open tab //Run// and select// Run Configurations...//

264

*1. Create a new //Eclipse Application// and name it appropriately.

265

*1. As product select {{code language="none"}}de.cau.cs.kieler.core.product.product{{/code}}.

266

*1. Click //Run// (or //Debug// if you opened// Debug Configuration...//)

267

*1. Create a new project and add you generated model.

\\

scchart Root {

initial state Init

--> Init with true;

}

[[image:attach:RunConfiguration.png]]

= Model-to-Model Transformations with KiCo =

287

288

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.

289

290

== Creating a new Transformation ==

291

292

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. :)

[[image:attach:KielerSCTEditor.png]]

==== Transformation Creation Task ====

303

304

* Create your first transformation...

305

*1. Create a new project within your tutorial working set as before.

306

*1. Add plugin dependencies to {{code language="none"}}de.cau.cs.kieler.kico{{/code}} and {{code language="none"}}de.cau.cs.kieler.sccharts{{/code}}.

307

*1. Create a new //Xtend class// in you package and name it "DoubleStates" and use {{code language="none"}}AbstractProductionTransformation{{/code}} as superclass.

308

*1. Here, you can automatically add the missing Xtend files by using the quickfix //Add Xtend lib to class path. //Alternatively you can simply add {{code language="none"}}com.google.guava{{/code}}, {{code language="none"}}org.eclipse.xtext.xbase.lib{{/code}}, {{code language="none"}}org.eclipse.xtend.lib{{/code}}, and {{code language="none"}}org.eclipse.xtend.lib.macro{{/code}} to you plugin dependencies.

309

*1. Click on //Add unimplemented methods//.

310

*1. (((

311

Now, you should have a class similar to the following one.

312

313

314

package tutorial.transformation

315

316

import de.cau.cs.kieler.kico.transformation.AbstractProductionTransformation

317

318

class DoubleStates extends AbstractProductionTransformation {

319

320

override getProducedFeatureId() {

321

throw new UnsupportedOperationException("TODO: auto-generated method stub")

}

override getId() {

throw new UnsupportedOperationException("TODO: auto-generated method stub")

}

}

* Lines in Xtend code don't have to and with a semicolon.

333

* We have been explicit about the method's return type, but we could have easily omitted it, letting Xtend infer the return type.

334

* The keyword {{code language="none"}}val{{/code}} declares a constant, while {{code language="none"}}var{{/code}} declares a variable. Try to make do with constants where possible.

335

* The methods you call should be declared as {{code language="none"}}def private{{/code}} since they are implementation details and shouldn't be called by other classes.

336

* 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, {{code language="none"}}def create {{/code}}methods might offer a better alternative...

)))

* (((

As you can see, it is mandatory to add an id for the transformation and another id of the feature that this transformation produces. Name your transformation **tutorial.doubleStates **and the id of feature you want to produce is **sccharts.doubleStates**.

341

342

343

You should really think about some constants here. You can also look at the sccharts transformation and features constants in the sccharts plugin.

)))

\\

* KiCo must know about the new feature and also about your new transformation.

356

*1. Add a new Xtend class with Feature as superclass. Add all unimplemented methods. Also set** sccharts.doubleStates** as Id.

357

*1. Go to the Extension tab inside your plugin configuration.

358

*11. Add a new Extension Point de.cau.cs.kieler.kico.feature. Create a new featureClass and point it to your new feature class.

359

*11. Also add a new Extension Point de.cau.cs.kieler.kico.transformation. Create a new productionTransformationClass and point it to your transformation class.

360

*11. Finally, you have to link your transformation to the SCT Editor. Add the Extension point de.cau.cs.kieler.kico.ui.transformation. Create an editor link and fill in the following values:

361

*111. editor: {{code language="none"}}de.cau.cs.kieler.sccharts.text.sct.Sct{{/code}}

362

*111. features: sccharts.doubleStates

363

*111. label: Tutorial Compilation

364

*111. priority: 101

365

*111. preferred: (leave it blank)

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.

367

* 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.

[[image:attach:KielerSCTEditorOwnTransformation.png]]

* Now, fill your transformation with life:

378

*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.

379

*1. (((

380

Add thew following body to the function and try to understand the Xtend code. Import unknown class via code assist.

381

382

383

def State transform(State rootState, KielerCompilerContext context) {

384

val newState = SCChartsFactory.eINSTANCE.createState => [

id = "ololo"

label = "ololo"

]

rootState.regions.filter(ControlflowRegion).head.states += newState

rootState

}

)))

*1. When selecting your transformation, the SCChart gets transformed and looks like the version on the right.

396

* Extend the transformation so that the transition is split up in two and connected via a transient state meaning that the original transformation should point to the new state and a new immediate transformation then points to the original target state. Try it out.

397

* (((

398

Xtend supports extensions that can be used to extend the function set of you classes (i.e. models). Add {{code language="none"}}com.google.inject{{/code}} to the dependencies of your plugin. Now, add the following code fragment to the beginning of your class.

@Inject

extension SCChartsExtension

403

404

405

There are several Extensions classes within the KIELER project that extend the functionality of various classes. Basically, there are one or more for each metamodel (e.g. SCCharts, SCG, KExpressions, etc). You don't want to invent the wheel again. Use these methods. For example: there is a method that gives you all contained states of a state in a list: {{code language="none"}}getAllContainedStatesList{{/code}}. You can use it on your {{code language="none"}}rootState{{/code}}: {{code language="none"}}rootState.allContainedStatesList{{/code}}. There are also several convenient methods for creating model elements so that you don't have to use the factories directly.

406

407

408

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.

)))

[[image:attach:KielerSCTEditorOwnTransformationOlolo.png]]

* 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.

421

422

== The existing Compilation Chain ==

423

424

Congratulations. You added and executed your own KiCo transformation. Nevertheless, often you want to extend the existing compilation chain. To do this, you proceed as before but instead of creating your own compilation chain, you must modify the existing chains (e.g. the netlist compilation in de.cau.cs.kieler.sccharts.ui). To add a specific transformation at a specific point in the chain, you must tell KiCo what features are required for the transformation. For that you must override the method getRequiredFeatureIds and return a set with all required features.

425

426

Also, if you're developing for the master chain, you should obey the package structure. Look at the sccharts plugins. All features, transformation, extensions, the metamodel, ui elements, etc are separated from each other. You should always do the same!

427

428

//We will add more content to this subsection in the future...//

\\

[[image:attach:ABODoubleStates.png]]

\\

\\

\\

= Model-to-Model Transformations between Metamodels =

447

448

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.

449

450

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.

451

452

(% class="wrapped" %)

453

|(((

454

(% class="content-wrapper" %)

455

(((

456

457

scchart ABO_norm_HandleA {

input output bool A;

input output bool B;

output bool O1;

output bool O2;

region HandleA:

initial state WaitA

--> _S immediate with A

465

--> _Pause immediate;

466

final state DoneA;

467

state _S

468

--> _S2 immediate with / B = true;

469

state _S2

470

--> DoneA immediate with / O1 = true;

state _Pause

--> _Depth;

state _Depth

--> _S immediate with A

475

--> _Pause immediate;

}

)))

)))|(((

(% class="content-wrapper" %)

481

(((

482

[[image:attach:abo_norm_HandleA.png]]

483

)))

484

)))|(% colspan="1" %)(% colspan="1" %)

485

(((

486

(% class="content-wrapper" %)

487

(((

488

[[image:attach:abo_scg_HandleA.png]]

)))

)))

The next figure depicts the direct mapping from normalized SCCharts to their corresponding SCG.

497

498

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,

[[image:attach:sccharts-scg.png]]

==== Transformation Creation Task 2 ====

509

510

Write a transformation that transforms your normalized version of ABO's HandleA into its corresponding SCG.

511

512

* Proceed as before. Create a new plugin (or copy your last one) Make sure, you also add de.cau.cs.kieler.scg to your dependencies.

513

* Write a transformation that is able to transform {{code language="none"}}ABO_norm_HandleA{{/code}} into its corresponding SCG.

514

* **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.

515

* Check your SCG semantically. Is there anything you could improve/optimize?

516

*1. Write a second transformation (just as before) and add it to the transformation chain right after the transformation you already added.

517

*1. Optimize the given SCG and compare the result with the previous one.

518

*1. Make sure that the two SCGs are still semantically identical.

519

520

\\

521