blob: 692af7a2be89cdd95181d5070235efe0d0846003 [file] [log] [blame]
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML>
<HEAD>
<meta name="copyright" content="Copyright (c) Thales Corporate Services S.A.S, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
<meta name="author" content="Benoit Langlois" >
<meta name="keywords" content="factory"/>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
<title>Orchestration</title>
</HEAD>
<BODY BGCOLOR="#ffffff">
<table border="0" cellpadding="2" cellspacing="0" width="100%">
<tbody>
<tr>
<td colspan="2" align="left" bgcolor="#0080c0" valign="top">
<h2><font face="Arial,Helvetica"><font color="#ffffff">
&nbsp;Orchestration
</font></font></h2>
</td>
</tr>
</tbody>
</table>
<a name="definition"><h2>Definition</h2></a>
<p class="Para">An orchestration definies how to conduct a set of activities and how activities transform data.</p>
<a name="motivation"><h2>Motivation</h2></a>
<p class="Para">An orchestration is the logic to achieve a generation target. However, an orchestration is also a data workflow. Input data can be injected at different stages; an activity output is potentially an input of a next activity.</p>
<a name="structure"><h2>Structure</h2></a>
<p class="Para">An orchestration works with a data context, a set of activities, and a workflow which defines how to conduct the activities. A workflow conforms to a language (e.g., BPMN).</p>
<p align="center">
<img src="./images/orchestrationStructure.jpg" alt="Orchestration structure"/>
</p>
<p align="center">
<i>Figure 1. Orchestra structure</i>
</p>
<br>
</body>
</html>