Changes for page SCCharts Development

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

From version < 19.1 >

edited by ssm
on 2016/04/21 19:55

To version < 12.1 >

edited by ssm
on 2016/04/21 16:57

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (1 modified, 0 added, 0 removed)
Objects (1 modified, 0 added, 0 removed)
- Confluence.Code.ConfluencePageClass[0]

Details

Page properties

Content

@@ -83,8 +83,6 @@
  (% 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"]]
  * **Overview and High-Level Transformations in Detail:**
  (% 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}}
@@ -94,20 +94,16 @@
  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.
--To see all class information check //Attributes/Literals// in the Diagram Options on the right.
--
--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.
--
  Try to understand most parts of the metamodel. You don't have to understand every detail but you should get the idea.
  ==== Model Task ====
 . Answer the following questions
++11. Name the class of the root element of an SCChart
 . How do you describe a superstate in the model?
--11. Outline the relationship between states, regions, transitions, and valued objects.\\
--11. Name the class of the root element of an SCChart.
 . What is a valued object?
 . How do you get the type of an interface variable?
++11. Outline the relationship between states, regions, transitions, and valued objects
 . What other metamodels are needed for the SCCharts metamodel and write down which one is needed for what?
 . Write down (on paper, text editor, etc) how the following SCChart models look like
 . Open the wiki page that explains the [[doc:KIELER.Textual SCCharts Language SCT]].
@@ -120,15 +120,25 @@
  {{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!
++By the way: You can //right-click// on the Diagram View surface to 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}}
@@ -135,6 +135,20 @@
  {{layout-section ac:type="single"}}
  {{layout-cell}}
++
++
++
++{{/layout-cell}}
++{{/layout-section}}
++
++{{layout-section ac:type="single"}}
++{{layout-cell}}
++
++{{/layout-cell}}
++{{/layout-section}}
++
++{{layout-section ac:type="single"}}
++{{layout-cell}}
  = Creating SCCharts Models Programmatically  =
  == Creating a Test Project ==
@@ -141,7 +141,6 @@
  We need a project for testing. Do the following:
--1. If you used the standard KIELER Oomph installation setup, create a new Working Set named Tutorial in the Package Explorer. Then...
 . Create a new empty //Plug-In Project//.
 . Add the project that contains the sccharts metamodel as a dependency of your new project through the //Plugin Manifest Editor//.
 . 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.
@@ -148,12 +148,12 @@
  == Creating a Model ==
--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:
++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:
  {{code language="java"}}
  SCChartsFactory sccFactory = SCChartsFactory.eINSTANCE;
--State state = sccFactory.createState();
--Transition transition = sccFactory.createTransition();
++State state = sccFactory .createState();
++Transition transition = sccFactory .createTransition();
  {{/code}}
  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.
@@ -160,13 +160,13 @@
  {{code language="java"}}
  KExpressionsFactory kFactory = KExpressionsFactory.eINSTANCE;
--BoolValue boolValue = kFactory.createBoolValue();
++BooleanValue boolValue = kFactory.createBooleanValue();
  {{/code}}
  For all simple attributes, there are getter and setter methods:
  {{code language="java"}}
--state.setId("Init");
++state.setId("Root");
  boolValue.setValue(true);
  {{/code}}
@@ -179,25 +179,15 @@
  List references (multiplicity of > 1) have only a list getter, which is used to manipulate the list:
  {{code language="java"}}
--state.getOutgoingTransitions().add(transition);
++state.outgoingTransitions.add(transition);
  {{/code}}
--{{info title="Plugin Dependencies"}}
--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.
--{{/info}}
--
  == 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:
++1. Add a dependency to the {{code language="none"}}org.eclipse.emf.ecore.xmi{{/code}} plug-in.
 . (((
--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.
--
--{{info title="Additional Dependencies"}}
--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.
--{{/info}}
--)))
--1. (((
  Use something like the following code to save the model from above:
  {{code language="java"}}
@@ -204,10 +204,10 @@
  // Create a resource set.
  ResourceSet resourceSet = new ResourceSetImpl();
--// Register the resource factory -- only needed for stand-alone!
--SctStandaloneSetup.doSetup();
--
--
++// Register the default resource factory -- only needed for stand-alone!
++// this tells EMF to use XML to save the model
++resourceSet.getResourceFactoryRegistry().getExtensionToFactoryMap().put(
++    Resource.Factory.Registry.DEFAULT_EXTENSION, new SCTResourceFactoryImpl());
  // Get the URI of the model file.
  URI fileURI = URI.createFileURI(new File("myABO.sct").getAbsolutePath());
@@ -226,47 +226,17 @@
  }
  {{/code}}
  )))
--{{/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:
++With these information out of the way, on we go to some model creation:
--1. 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.
--11. Run the {{code language="none"}}main(){{/code}} method by right-clicking its class and selecting (% style="line-height: 1.42857;" %)//Run as//(%%) -> (% style="line-height: 1.42857;" %)//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.
--11. Execute the main method.
--11. Inspect your SCT file. (Press F5 to refresh your file view.)
--1. Now, create a new Java class and proceed as before to generate a model of ABO in the {{code language="none"}}main(){{/code}} method.
++1. Programmatically create a valid model of ABO in the {{code language="none"}}main(){{/code}} method.
++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.
++1. Execute the main method.
++1. Inspect your SCT file.
 . Start your SCChart Editor Eclipse instance and load your SCT file. KLighD should now be able to visualize your ABO correctly.
--
--{{/layout-cell}}
--
--{{layout-cell}}
--{{code language="java" title="Root.sct"}}
--scchart Root {
--  initial state Init
--  --> Init with true;
--}
--{{/code}}
--{{/layout-cell}}
--{{/layout-section}}
--
--{{layout-section ac:type="two_right_sidebar"}}
--{{layout-cell}}
--
--{{/layout-cell}}
--
--{{layout-cell}}
--
--{{/layout-cell}}
--{{/layout-section}}
--
--{{layout-section ac:type="single"}}
--{{layout-cell}}
  = Transforming SCCharts =
  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.

Confluence.Code.ConfluencePageClass[0]

Id

@@ -1,1 +1,1 @@
--16810366
++16810304

URL

@@ -1,1 +1,1 @@
--https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/TUT/pages/16810366/SCCharts Development
++https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/TUT/pages/16810304/SCCharts Development

Changes for page SCCharts Development

Summary

Details

Navigation

Quick Links