scheduling.html

  
 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">

<!--
 Documentation of Defining a Schedule.
 
 @author hoelzl
 @ConQAT.Rating GREEN Hash: DDE205B09061118C148CF63FA1F48401
-->

<html>
<head>
	<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
	<title>Defining a Schedule using AutoFOCUS3 (AF3)</title>
</head>
<body>

<h2><u><font color="#336699">Defining a Schedule for a given Deployment</font></u></h2>

AutoFOCUS supports schedule generation for a given deployment of component architectures to platform architectures. Note that this feature is still under development.
You can generate a schedule for a deployment to your model using the deployment context menu. The deployment is automatically linked to your project.

<br><br>
<img src="./pictures/Scheduling.1.png">
<br><br>
The first step of generating an (optimized) schedule for the given deployment is providing information to the wizard page. The user needs to select the top-level component, that indicates
which part of the system should be scheduled. For instance, the user might have modeled the environment that does not need to be scheduled. Thus, this wizards provides the capability to determine
the system to be scheduled (e.g. the "AdaptiveCruiseControl" as in the picture below).
<br><br>
The filter mechanism enables the selection of components below the selected component. "First-level components indicate that child components of the selected component are scheduled. Note, that all components need to be deploymed.
<br><br>
<img src="./pictures/Scheduling.2.png">
<br><br>
Based on the selection all tasks, w.r.t the component architecture, and their precedence relations are extracted and visualized in a given precedence graph.
<br><br>
<img src="./pictures/Scheduling.3.png">
<br><br>

Selecting the "Scheduling Editor" in the lower end of editor enables the scheduling functionality do be displayed. The user is enabled to choose, whether an optimized or a single solution is needed. Note that for larger system, the 
timeout could be usefull as the solver might use a some time to find for solutions in the design space. 

<br><br>
<img src="./pictures/Scheduling.4.png">
<br><br>
After calculation of possible solutions (by choosing the "optimal solution"), all results are displayed in the result section. A visualization of the schedule is given in the "Scheduling View".

<br><br>
<img src="./pictures/Scheduling.5.png">

</font>
</body>
</html>