Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-Tutorial on KIELER Light-weight Diagrams
	1	+Tutorial on KIELER Lightweight Diagrams

Content

...	...	@@ -4,4 +4,30 @@
4	4
5	5	= Preliminaries =
6	6
7		-Install the KLighD from our latest release update site as demonstrated on [[doc:Lightweight Diagrams (KLighD)]].
	7	+1. Read about the ideas & motivation of KLighD in our paper "//Just Model!// – Putting Automatic Synthesis of Node-Link-Diagrams into Practice", cited at [[doc:Lightweight Diagrams (KLighD)]]
	8	+1*. You can skip the size estimation parts and focus on section I, III, and V.
	9	+1. Install the KLighD from our latest release update site as demonstrated on [[doc:Lightweight Diagrams (KLighD)]] and import the examples project.
	10	+1. Make yourself familiar with the (% style="line-height: 1.4285715;" %){{code language="none"}}UML2UseCaseDiagramSynthesis{{/code}} contained that project
	11	+1*. (((
	12	+(% style="line-height: 1.4285715;" %)Have also a look at the {{code language="none"}}...Extensions{{/code}} classes mentioned in UML2UseCaseDiagramSynthesis, especially {{code language="none"}}KNodeExtensions{{/code}}.
	13	+What is the purpose of {{code language="none"}}createNode(...){{/code}} and {{code language="none"}}getNode(...){{/code}}?
	14	+)))
	15	+
	16	+= Implement a simple turing diagram synthesis =
	17	+
	18	+1. Create a new diagram synthesis implementation by means of the KLighD project wizard as illustrated on [[doc:Lightweight Diagrams (KLighD)]].
	19	+1. Add a dependency of the newly introduced plug-in project to the project defining your turing modeling language.
	20	+1. Let your diagram synthesis create a node for each state declared in your state machine.
	21	+1*. Let those node be depicted by ellipses or rounded rectangles containing a text field showing the corresponding state's name
	22	+1. Let your diagram synthesis create an edge for each transition being depicted by a polyline
	23	+1*. Attach arrow decorators to those polylines.
	24	+
	25	+= Augment your diagram synthesis =
	26	+
	27	+1. The actor nodes in {{code language="none"}}UML2UseCaseDiagramSynthesis{{/code}} are equipped with (node) labels. This is done by means of a convenience method provided {{code language="none"}}KLabelExtensions{{/code}}.
	28	+1*. Equip the edges of your turing diagrams with labels exhibiting the guard, new symbol, etc; use a fitting method for edge labels from {{code language="none"}}KLabelExtensions{{/code}}.
	29	+1. Improve the layout of your diagrams
	30	+11. switch the layout algorithm to Graphviz {{code language="none"}}dot{{/code}} by setting the property //LayoutOptions//{{code language="none"}}.ALGORITHM{{/code}} on the root node to {{code language="none"}}de.cau.cs.kieler.graphviz.dot{{/code}}.
	31	+11. change the edge figures from polylines to splines.
	32	+
	33	+

Confluence.Code.ConfluencePageClass[0]

Id

...	...	@@ -1,1 +1,1 @@
1		-8651127
	1	+8651131

URL

...	...	@@ -1,1 +1,1 @@
1		-https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/KIELER/pages/8651127/Tutorial on KIELER Light-weight Diagrams
	1	+https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/KIELER/pages/8651131/Tutorial on KIELER Lightweight Diagrams