Wiki source code of A SyncChart-Editor based on Yakindu
Version 27.1 by wah on 2012/10/15 11:17
Show last authors
| author | version | line-number | content |
|---|---|---|---|
| 1 | = Yakindu SCT = | ||
| 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 | [[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 | Initial State | ||
| 33 | )))|((( | ||
| 34 | [[image:attach:image2012-10-11 13:46:58.png]] | ||
| 35 | )))|((( | ||
| 36 | [[image:attach:image2012-10-11 13:52:3.png]] | ||
| 37 | )))|((( | ||
| 38 | **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. | ||
| 39 | ))) | ||
| 40 | |((( | ||
| 41 | Final State | ||
| 42 | )))|((( | ||
| 43 | [[image:attach:image2012-10-11 13:47:5.png]] | ||
| 44 | )))|((( | ||
| 45 | [[image:attach:image2012-10-11 13:51:43.png]] | ||
| 46 | )))|((( | ||
| 47 | **YAKINDU**: Final States are pseudo states. The Final State may not be a Composite State | ||
| 48 | ))) | ||
| 49 | |((( | ||
| 50 | State | ||
| 51 | )))|((( | ||
| 52 | [[image:attach:image2012-10-11 13:47:11.png]] | ||
| 53 | )))|((( | ||
| 54 | [[image:attach:image2012-10-11 13:49:10.png]] | ||
| 55 | )))|((( | ||
| 56 | |||
| 57 | ))) | ||
| 58 | |((( | ||
| 59 | Composite State | ||
| 60 | )))|((( | ||
| 61 | [[image:attach:image2012-10-11 13:47:20.png]] | ||
| 62 | )))|((( | ||
| 63 | [[image:attach:image2012-10-11 13:47:58.png]] | ||
| 64 | )))|((( | ||
| 65 | |||
| 66 | ))) | ||
| 67 | |((( | ||
| 68 | History | ||
| 69 | )))|((( | ||
| 70 | [[image:attach:image2012-10-11 13:47:27.png]][[image:attach:image2012-10-11 13:47:32.png]] | ||
| 71 | )))|((( | ||
| 72 | [[image:attach:image2012-10-11 13:47:54.png]] | ||
| 73 | )))|((( | ||
| 74 | **YAKINDU**: | ||
| 75 | |||
| 76 | * Shallow History: (% style="color: rgb(0,0,0);" %)is a pseudo state. It is placed inside a region of a composite state. | ||
| 77 | * (% 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.- | ||
| 78 | |||
| 79 | **KIELER**: A History is a attribute of a Transition | ||
| 80 | ))) | ||
| 81 | |((( | ||
| 82 | Synchronization | ||
| 83 | )))|((( | ||
| 84 | |||
| 85 | )))|((( | ||
| 86 | [[image:attach:image2012-10-11 13:47:49.png]] | ||
| 87 | )))|((( | ||
| 88 | |||
| 89 | ))) | ||
| 90 | |((( | ||
| 91 | Choise | ||
| 92 | )))|((( | ||
| 93 | [[image:attach:image2012-10-11 13:47:38.png]] | ||
| 94 | )))|((( | ||
| 95 | [[image:attach:image2012-10-11 13:47:44.png]] | ||
| 96 | )))|((( | ||
| 97 | |||
| 98 | ))) | ||
| 99 | |||
| 100 | |=((( | ||
| 101 | |||
| 102 | )))|=((( | ||
| 103 | KIELER | ||
| 104 | )))|=((( | ||
| 105 | YAKINDU | ||
| 106 | ))) | ||
| 107 | |((( | ||
| 108 | Interface declaration | ||
| 109 | )))|((( | ||
| 110 | [[image:attach:image2012-10-12 10:59:54.png]] | ||
| 111 | )))|((( | ||
| 112 | [[image:attach:image2012-10-12 10:51:52.png]] | ||
| 113 | ))) | ||
| 114 | |||
| 115 | = Yakindu SCT module structure = | ||
| 116 | |||
| 117 | [[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"]] | ||
| 118 | |||
| 119 | = Customizing Yakindu SCT Editor to SyncCharts = | ||
| 120 | |||
| 121 | Two steps are required to adapt the Yakindu SCT Editor to the SyncCharts syntax: | ||
| 122 | |||
| 123 | * adapting the graphical representation (sgraph) | ||
| 124 | * extending or replacing the textual description language (stext) | ||
| 125 | |||
| 126 | 1. ((( | ||
| 127 | == Adapting the graphical representation == | ||
| 128 | |||
| 129 | (% style="color: rgb(0,0,0);" %)To adapt the graphical representation, several step is required:(%%) | ||
| 130 | (% style="color: rgb(0,0,0);" %) (%%)\\ | ||
| 131 | |||
| 132 | 1. adapting the Metamodel for the graphical represenation (% style="color: rgb(0,0,0);" %)of the state machine models(%%) (org.yakindu.sct.model.sgraph)\\ | ||
| 133 | 11. [[Yakindu SCT Metamodel>>attach:Yakindu sgraph.pdf]] | ||
| 134 | 11. [[KIELER SyncCharts Metamodel>>attach:synccharts.pdf]] | ||
| 135 | \\ | ||
| 136 | 1. Figures (org.yakindu.sct.ui.editor.editor.figures) | ||
| 137 | \\ | ||
| 138 | 1. Editparts (org.yakindu.sct.ui.editor.editparts) | ||
| 139 | \\ | ||
| 140 | 1. Propertysheets (org.yakindu.sct.ui.editor.propertysheets) | ||
| 141 | \\ | ||
| 142 | 1. The palette (org.yakindu.sct.ui.editor/plugin.xml) | ||
| 143 | \\ | ||
| 144 | ))) | ||
| 145 | 1. ((( | ||
| 146 | == Extending or replacing the textual description language == | ||
| 147 | |||
| 148 | (% 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. | ||
| 149 | ))) |