Changes for page SCCharts-Editor based on Yakindu
Last modified by Richard Kreissig on 2023/09/14 11:09
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Objects (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -1,158 +1,3 @@ 1 - =Yakindu SCT =1 +YAKINDU is a tool kit for model based development and the statechart tools are the first modules provided by this project. The tools apply the concept of state machines that are well understood and formal enough to describe behaviour unambiguously. The statechart tools support editing, validating, simulating state machines and generating code from state machines. The tools are provided as Eclipse-plugins and integrate tightly into the IDE ([[Yakindu SCT Website>>url:http://www.itemis.de/itemis-ag/produkte/yakindu-open-source/yakindu-statechart-tools/language=de/43437/produktbeschreibung||shape="rect"]]). 2 2 3 -YAKINDU Statechart Tools (SCT) is an open source tool for the specification and development of reactive, event-based systems using state machines. 4 - 5 -It consists of a graphical tool for editing and provides validation, simulation, and code generators for different target platforms. The tools are provided as Eclipse-plugins and integrate tightly into the IDE ([[Yakindu SCT Website>>url:http://www.itemis.de/itemis-ag/produkte/yakindu-open-source/yakindu-statechart-tools/language=de/43437/produktbeschreibung||shape="rect"]]). 6 - 7 7 [[image:attach:Yakindu SCT.png]] 8 - 9 -= Yakindu SCT Editor VS KIELER SyncCharts Editor = 10 - 11 -|=((( 12 - 13 -)))|=((( 14 -KIELER 15 -)))|=((( 16 -YAKINDU 17 -)))|=((( 18 - 19 -))) 20 -|((( 21 -Transition 22 -)))|((( 23 -[[image:attach:image2012-10-11 13:46:43.png]] 24 -)))|((( 25 -[[image:attach:image2012-10-11 13:46:50.png]] 26 -)))|((( 27 -**YAKINDU**: There is only one type for transitions 28 - 29 -**KIELER**: Strong Abort, Week Abort, Normal Termination 30 -))) 31 -|((( 32 -State 33 -)))|((( 34 -[[image:attach:image2012-10-11 13:47:11.png]] 35 -)))|((( 36 -[[image:attach:image2012-10-11 13:49:10.png]] 37 -)))|((( 38 - 39 -))) 40 -|((( 41 -Composite State 42 -)))|((( 43 -[[image:attach:image2012-10-11 13:47:20.png]] 44 -)))|((( 45 -[[image:attach:image2012-10-11 13:47:58.png]] 46 -)))|((( 47 - 48 -))) 49 -|((( 50 -Initial State 51 -)))|((( 52 -[[image:attach:image2012-10-15 14:41:10.png]][[image:attach:image2012-10-11 13:46:58.png]] 53 -)))|((( 54 -[[image:attach:image2012-10-11 13:52:3.png]] 55 -)))|((( 56 -**YAKINDU**: Initials State are pseudo states. The Initial State may not be a Composite State. (% style="color: rgb(0,0,0);" %)An initial state can only have one outgoing transition and no incoming. 57 - 58 -(% style="color: rgb(0,0,0);" %)**KIELER**: Initial states are supposed to have a thicker border than normal states 59 -))) 60 -|((( 61 -Final State 62 -)))|((( 63 -[[image:attach:image2012-10-15 14:40:31.png]][[image:attach:image2012-10-11 13:47:5.png]] 64 -)))|((( 65 -[[image:attach:image2012-10-11 13:51:43.png]] 66 -)))|((( 67 -**YAKINDU**: Final States are pseudo states. The Final State may not be a Composite State 68 - 69 -**KIELER**: Final states are depicted with a double border 70 -))) 71 -|((( 72 -History 73 -)))|((( 74 -[[image:attach:image2012-10-11 13:47:27.png]][[image:attach:image2012-10-11 13:47:32.png]] 75 -)))|((( 76 -[[image:attach:image2012-10-11 13:47:54.png]] 77 -)))|((( 78 -**YAKINDU**: 79 - 80 -* Shallow History: (% style="color: rgb(0,0,0);" %)is a pseudo state. It is placed inside a region of a composite state. 81 -* (% style="color: rgb(0,0,0);" %)Deep History: (% style="color: rgb(0, 0, 0); color: rgb(0, 0, 0)" %) is similar to shallow history. With a deep history the latest state of multiple nested states is remembered.- 82 - 83 -**KIELER**: A History is a attribute of a Transition 84 -))) 85 -|((( 86 -Synchronization 87 -)))|((( 88 - 89 -)))|((( 90 -[[image:attach:image2012-10-11 13:47:49.png]] 91 -)))|((( 92 - 93 -))) 94 -|((( 95 -Choice 96 -)))|((( 97 -[[image:attach:image2012-10-11 13:47:38.png]] 98 -)))|((( 99 -[[image:attach:image2012-10-11 13:47:44.png]] 100 -)))|((( 101 - 102 -))) 103 - 104 -|=((( 105 - 106 -)))|=((( 107 -KIELER 108 -)))|=((( 109 -YAKINDU 110 -))) 111 -|((( 112 -Interface declaration 113 -)))|((( 114 -[[image:attach:image2012-10-12 10:59:54.png]] 115 -)))|((( 116 -[[image:attach:image2012-10-12 10:51:52.png]] 117 -))) 118 - 119 -= Yakindu SCT module structure = 120 - 121 -[[See Yakindu Wiki>>url:http://svn.codespot.com/a/eclipselabs.org/yakindu/SCT2/trunk/plugins/org.yakindu.sct.doc.user/help/developer/01_Overview/overview.html||shape="rect"]] 122 - 123 -= Customizing Yakindu SCT Editor to SyncCharts = 124 - 125 -Two steps are required to adapt the Yakindu SCT Editor to the SyncCharts syntax: 126 - 127 -* adapting the graphical representation (sgraph) 128 -* extending or replacing the textual description language (stext) 129 - 130 -1. ((( 131 -== Adapting the graphical representation == 132 - 133 -(% style="color: rgb(0,0,0);" %)To adapt the graphical representation, several step is required:(%%) 134 -(% style="color: rgb(0,0,0);" %) (%%)\\ 135 - 136 -1. adapting the Metamodel for the graphical represenation (% style="color: rgb(0,0,0);" %)of the state machine models(%%) (org.yakindu.sct.model.sgraph)\\ 137 -11. [[Yakindu SCT Metamodel>>attach:Yakindu sgraph.pdf]] 138 -11. [[KIELER SyncCharts Metamodel>>attach:synccharts.pdf]] 139 -\\ 140 -1. Figures (org.yakindu.sct.ui.editor.editor.figures) 141 -\\ 142 -1. Editparts (org.yakindu.sct.ui.editor.editparts) 143 -\\ 144 -1. Propertysheets (org.yakindu.sct.ui.editor.propertysheets) 145 -\\ 146 -1. The palette (org.yakindu.sct.ui.editor/plugin.xml) 147 -))) 148 - 149 -(% style="margin-left: 60.0px;" %) 150 - 151 -Example: How to modify Initial and Finial States in Yakindu SCT Editor 152 -\\ 153 - 154 -1. ((( 155 -== Extending or replacing the textual description language == 156 - 157 -(% style="color: rgb(0,0,0);" %)The textual [[description language>>url:http://svn.codespot.com/a/eclipselabs.org/yakindu/SCT2/trunk/plugins/org.yakindu.sct.doc.user/help/user/05_Reference/reference.html#Statechartdescriptionlanguage||shape="rect"]] is used to declare and describe behaviors in the state machine. It is case sensitive. 158 -)))
- Confluence.Code.ConfluencePageClass[0]
-
- Id
-
... ... @@ -1,1 +1,1 @@ 1 -2982 1421 +2982039 - URL
-
... ... @@ -1,1 +1,1 @@ 1 -https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/KIELER/pages/2982 142/A SyncChart-Editor based on Yakindu1 +https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/KIELER/pages/2982039/A SyncChart-Editor based on Yakindu