simon
/
yakindu


			
				
					
						
						
							123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132
							<?xml version='1.0' encoding='utf-8' ?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
	<head>
		<meta http-equiv="Content-Type" content="text/html; charset=utf-8"/>
		<title>concepts</title>
		<link type="text/css" rel="stylesheet" href="../style.css"/>
	</head>
	<body>
		<h1 id="YakinduStatecharttoolconcepts">Yakindu Statechart tool concepts</h1>
		<h2 id="Modeling">Modeling</h2>
		<p>Yakindu Statechart Models are based on statecharts as defined by David Harel and are close to UML state machines. Thus, they support all structural model elements as defined by the UML specification, which are States (orthogonal and hierarchical), Regions, Transitions and Pseudo States (History, Deep History, Initial, Final, Choice, Join / Fork).
			<br/>In addition, Yakindu Statechart Models specify interfaces that define the interaction of the state machine with its environment. Besides some more advanced concepts like Entry / Exit Points, an interface basically consists of in and out Events as well as Variables including types. These well-defined statechart interfaces are especially useful in the context of component models and product line engineering.
		</p>
		<p>For defining interfaces and modeling the dynamic aspects of statecharts (triggers, guards and actions) SCT provides a statically typed, textual action language. It tightly integrates into the graphical editor and supports the user with code completion, syntax highlighting, cross referencing and validation during modeling.</p>
		<p>Declarations of interfaces, events, variables etc. are done in a textual modeling field in the editor. The language expressions that define actions are directly added to the elements like states or transitions. </p>
		<h2 id="Simulation">Simulation</h2>
		<p>Yakindu Statechart Models can be executed via an integrated simulation engine. The simulation engine supports two different types of execution semantics:</p>
		<ul>
			<li>cycle based </li>
			<li>event driven</li>
		</ul>
		<p>The default execution semantic is 
			<strong>cycle based</strong> which executes a statechart cycle within a fixed period of time and thus allows processing of concurrent events. In contrast, the 
			<strong>event based</strong> approach executes a statechart cycle as soon as an event occurrs.
		</p>
		<p>During simulation, the currently active states and the transition path including the previous states are highlighted in the editor for visual debugging. An additional view shows the variable values and allows to raise events. </p>
		<p>Apart from that, the engine uses a 
			<strong>virtual time</strong> during simulation. The user can provide a time scaling factor that is multiplied with the real time. This is especially useful during debugging, if the statechart model contains very tight or long running time triggers.
		</p>
		<h2 id="CodeGeneration">Code Generation</h2>
		<p>Yakindu Statechart Tools currently support the generation of Java, C and C++ Code.  All generators can be customized with a 
			<strong>generator model</strong>. This is a textual model file where generator features, like the execution type (event or cycle based), or the interface styles (static or generic), can be specified. The code generation process can either be executed with a builder that starts code generation on resource change or manually with a context menu action.
		</p>
		<h2 id="Domainspecificadaptability">Domain specific adaptability</h2>
		<p>Yakindu Statechart Tools were developed with a domain specific adaptability in mind. Several extension points allow the customization of all mentioned aspects. It is possible to contribute a custom type system or custom action languages which may be a dialect of the textual description language or a complete new language.</p>
		<p>Also, the different code generators can be customized or new code generators for other target languages can be plugged in easily.</p>
		<h2 id="YakinduSCModelingperspective">Yakindu SC Modeling perspective</h2>
		<p>For state machine modeling purposes open the Yakindu 
			<strong>SC Modeling</strong> perspective by clicking 
			<strong>Window</strong> &gt; 
			<strong>Open Perspective</strong> &gt; 
			<strong>SC Modeling</strong>. This perspective is optimized for statechart modeling. It consists of 
		</p>
		<ul>
			<li>
				<a href="PLUGIN_ROOT/org.eclipse.platform.doc.user/concepts/cnav.htm">Project Explorer</a> on the left
			</li>
			<li>
				<a href="PLUGIN_ROOT/org.eclipse.platform.doc.user/concepts/coutline.htm">Outline</a> View on the right
			</li>
			<li>YAKINDU Statechart Editor at the top</li>
			<li>
				<a href="PLUGIN_ROOT/org.eclipse.platform.doc.user/concepts/cprbview.htm">Problems</a> and 
				<a href="PLUGIN_ROOT/org.eclipse.platform.doc.user/concepts/cpropview.htm">Properties View</a> at the bottom
			</li>
		</ul>
		<p>
			<img border="0" src="../02_Getting_Started/images/sc_modeling_perspective.jpg"/>
		</p>
		<h2 id="YakinduSCSimulationperspective">Yakindu SC Simulation perspective</h2>
		<p>To simulate a state machine use the Yakindu 
			<strong>SC Simulation</strong> perspective by clicking 
			<strong>Window</strong> &gt; 
			<strong>Open Perspective</strong> &gt; 
			<strong>SC Simulation</strong>. This perspective is optimized for simulation purposes and consists of:
		</p>
		<ul>
			<li>
				<a href="PLUGIN_ROOT/org.eclipse.platform.doc.user/concepts/cnav.htm">Project Explorer</a> on the left
			</li>
			<li>
				<a href="PLUGIN_ROOT/org.eclipse.platform.doc.user/concepts/coutline.htm">Outline</a> view on the right top
			</li>
			<li>Simulation View on the right bottom</li>
			<li>Debug view at the top</li>
			<li>YAKINDU Statechart Editor at the bottom</li>
		</ul>
		<p>
			<img border="0" src="../02_Getting_Started/images/sc_simulation_perspective.jpg"/>
		</p>
		<h2 id="YAKINDUStatechartEditor">YAKINDU Statechart Editor</h2>
		<p>With the YAKINDU Statechart editor you create or modify state models. The editor automatically opens on .sct files. To create a new YAKINDU statechart model click 
			<strong>File</strong> &gt; 
			<strong>New</strong> &gt; 
			<strong>Other...</strong> &gt; 
			<strong>YAKINDU Statechart model</strong>. Give it a speaking name and click 
			<strong>Finish</strong>. The newly created model opens in the statechart editor. Also the SC Modeling perspective opens.
		</p>
		<p>
			<img border="0" src="../02_Getting_Started/images/sc_editor_01.jpg"/>
		</p>
		<p>The editor consists of three parts: </p>
		<ul>
			<li>the graphic canvas to design the state machine</li>
			<li>the palette on the right that owns the elements to design the state machine </li>
			<li>a textual modeling field on the left</li>
		</ul>
		<p>You can use the textual modeling field to define internal behavior of states and declare events or variables. The 
			<a href="../05_Reference/reference.html#Statechartdescriptionlanguage">reference</a> explains this language.
		</p>
		<p>Elements that cause problems get warning and error markers attached. For more details about the problems open the 
			<strong>Problems View</strong>.
		</p>
		<h2 id="SimulationView">Simulation View</h2>
		<p>The simulation view is an interactive view to watch and control the state machine simulation. To get it open the simulation perspective. </p>
		<p>Start a simulation by clicking 
			<strong>Run</strong> &gt; 
			<strong>Run</strong>. 
		</p>
		<p>
			<img border="0" src="../02_Getting_Started/images/simulation_view_active.jpg"/>
		</p>
		<p>During the simulation in the statechart editor the active state gets a red color. The previous transition is green. The simulation view shows the events that trigger the states. You can change values here to trigger events. Beneath the table there are two clocks. One for the 
			<em>virtual time</em> and one for the 
			<em>real time</em> and a slider to change virtual time.
		</p>
		<p>You can also select an 
			<em>event driven</em> or 
			<em>cycle based</em> run configuration.
		</p>
		<h2 id="YAKINDUSCTNature">YAKINDU SCT Nature</h2>
		<p>YAKINDU model projects are associated with the 
			<strong>YAKINDU SCT nature</strong>. On projects with 
			<strong>YAKINDU SCT nature</strong> 
			<em>.sct</em> and 
			<em>.sgen</em> files are automatically build and checked for problems. So you get fast feedback during editing. You can toggle the SCT nature by right clicking 
			<strong>Configure</strong> &gt; 
			<strong>Add</strong> or 
			<strong>Remove YAKINDU SCT Nature</strong> on the project.
		</p>
	</body>
</html>