usecases/index.php - gerrit/www.eclipse.org/amw - Git at Google

 <?php  																														require_once($_SERVER['DOCUMENT_ROOT'] . "/eclipse.org-common/system/app.class.php");	require_once($_SERVER['DOCUMENT_ROOT'] . "/eclipse.org-common/system/nav.class.php"); 	require_once($_SERVER['DOCUMENT_ROOT'] . "/eclipse.org-common/system/menu.class.php"); 	$App 	= new App();	$Nav	= new Nav();	$Menu 	= new Menu();		include($App->getProjectCommon());    # All on the same line to unclutter the user's desktop'

 	#*****************************************************************************
 	#
 	# template.php
 	#
 	# Author: 		Freddy Allilaire
 	# Date:			2005-12-07
 	#
 	# Description: Type your page comments here - these are not sent to the browser
 	#
 	#
 	#****************************************************************************

 	#
 	# Begin: page-specific settings.  Change these.
 	$pageTitle 		= "AMW Use Cases";
 	$pageKeywords	= "";
 	$pageAuthor		= "Marcos Didonet Del Fabro";

 	# End: page-specific settings
 	#

 	# Paste your HTML content between the EOHTML markers!
 	$html = <<<EOHTML

 	<!-- Main part -->
 	<div id="midcolumn">
 		<h1><font color='#280882'>AMW</font> Use Cases</h1>

 		<a name="goals"></a>
 		<img align="right" src="../resources/amwLogoSmall.png" valign="top" style="padding-left: 10px;" alt="AMW Logo" />

     	<p align="justify">

     	</p>

     		Weaving models may be used in several application scenarios, such as <b>metamodel comparison, traceability,
     		model matching, model annotation, interoperability</b>.</b> <br />
     		This is because it is often necessary to establish relationships between elements of different
     		models.
     		<p/>
     		These use cases are implemented using AMW. AMW supports such a variety of application scenarios
     		because it has an adaptive interface
     		that handles different metamodel extensions (AMW is fully implemented using the reflective API of EMF).
     		<br/>
     		The plug-in also provides a set of extensions points that enables to add new functionalities when necessary.

     		<p/>This section describes a set of key use cases of AMW. The use cases are illustrated with a general overview.
     		Some of them provide more precise documentation, as well as fully implemented examples.
     		<p/>

     	<p align="justify">
     	</p>

 		<hr class="clearer" />

 	    <div class="homeitem3col">
 			<h3>List of use cases</h3>
 	    	<ul class="midlist">

 	    		<li>
 	    			<table width="100%">
 						<tr>
 							<td width="20%" valign="middle">
 					    		<h2><a href="compare/">Metamodel comparison</a></h2>
 		  					</td>
 							<td width="60%" align="justify">
 								A weaving model contains links that are used to compare different metamodels.
 								Metamodels need to be compared for several reasons.
 								Two important reasons are: <br/>
 								<b>1)</b> to transform the models conforming to different versions of a metamodel; <br/>
 								<b>2)</b> to represent the differences between two similar metamodels.<br/>
 							</td>
 							<td align="center">
 								<a href="http://www.inria.fr/recherche/equipes/atlas.en.html">INRIA ATLAS</a>
 							</td>
 						</tr>
 					</table>
 	    		</li>
 				<li>
 	    			<table width="100%">
 						<tr>
 							<td width="20%" valign="middle">
 					    		<h2><a href="traceability/">Traceability</a></h2>
 		  					</td>
 							<td width="60%" align="justify">
 								Traceability is used in different applications. We consider here the transformation of
 								a source model into a target model. It is often necessary to know the set of elements
 								of the source model that were used to produce one target model element.
 								Weaving models define links to save this traceability information.
 							</td>
 							<td align="center">
 								<a href="http://www.inria.fr/recherche/equipes/atlas.en.html">INRIA ATLAS</a>
 							</td>
 						</tr>
 					</table>
 	    		</li>
 					<li>
 	    			<table width="100%">
 						<tr>
 							<td width="20%" valign="middle">
 					    		<h2><a href="AOM/">Aspect oriented modeling</a></h2>
 		  					</td>
 							<td width="60%" align="justify">
 								Aspect oriented modeling aims at weaving business models and cross cutting models in a single model.
 								There is no preferential model. This means the weaving can be done in any model (e.g., weavings in the cross
 								cutting concern AND/OR in the business model).
 								The AMW enables to create aspect oriented modeling extensions. The weaving models are interpreted by ATL
 								transformations to weave the models.
 							</td>
 							<td align="center">
 								<a href="http://www.inria.fr/recherche/equipes/atlas.en.html">INRIA ATLAS</a>
 							</td>
 						</tr>
 					</table>
 	    		</li>


 	    		<li>
 	    			<table width="100%">
 						<tr>
 							<td width="20%" valign="middle">
 					    		<h2><a href="matching/">Matching</a></h2>
 		  					</td>
 							<td width="60%" align="justify">
 								Matching is the semi-automatic process of creating weaving models.
 								A matching creates links and calculates a similarity measure between model elements.
 								The maching process is the basis for almost all utilisation of weaving models.
 							</td>
 							<td align="center">
 								<a href="http://www.inria.fr/recherche/equipes/atlas.en.html">INRIA ATLAS</a>
 							</td>
 						</tr>
 					</table>
 	    		</li>
 				<li>
 	    			<table width="100%">
 						<tr>
 							<td width="20%" valign="middle">
 					    		<h2><a href="interoperability/"> Tool interoperability<!--</a> --></h2>
 		  					</td>
 							<td width="60%" align="justify">
 								To support interoperability between different models, it is necessary to represent the
 								semantic heterogeneities between the model elements.
 								The weaving model is used to capture the semantic heterogeneities between different models or metamodels.
 								The weaving model acts as a high-level specification for producing executable model transformations.
 							</td>
 							<td align="center">
 								<a href="http://www.inria.fr/recherche/equipes/atlas.en.html">INRIA ATLAS</a>
 							</td>
 						</tr>
 					</table>
 	    		</li>

 	    		<li>
 	    			<table width="100%">
 						<tr>
 							<td width="20%" valign="middle">
 					    		<h2><!--<a href="matching/">-->Model alignment<!--</a>--></h2>
 		  					</td>
 							<td width="60%" align="justify">
 								A model alignement consists of a set of links between the model elements.
 								An alignment is used to create an integrated view of two models.
 								The alignment may be used as an input to merge algorithms.
 								<br/>
 							</td>
 							<td align="center">
 								<a href="http://www.inria.fr/recherche/equipes/atlas.en.html">INRIA ATLAS</a>
 							</td>
 						</tr>
 					</table>
 	    		</li>


 	    	</ul>
 	    </div>
 		<hr class="clearer" />
 	</div>

 	<div id="rightcolumn">

 	</div>

 EOHTML;


 	# Generate the web page
 	$App->generatePage($theme, $Menu, $Nav, $pageAuthor, $pageKeywords, $pageTitle, $html);
 ?>
	<?php require_once($_SERVER['DOCUMENT_ROOT'] . "/eclipse.org-common/system/app.class.php"); require_once($_SERVER['DOCUMENT_ROOT'] . "/eclipse.org-common/system/nav.class.php"); require_once($_SERVER['DOCUMENT_ROOT'] . "/eclipse.org-common/system/menu.class.php"); $App = new App(); $Nav = new Nav(); $Menu = new Menu(); include($App->getProjectCommon()); # All on the same line to unclutter the user's desktop'

	#*****************************************************************************
	#
	# template.php
	#
	# Author: Freddy Allilaire
	# Date: 2005-12-07
	#
	# Description: Type your page comments here - these are not sent to the browser
	#
	#
	#****************************************************************************

	#
	# Begin: page-specific settings. Change these.
	$pageTitle = "AMW Use Cases";
	$pageKeywords = "";
	$pageAuthor = "Marcos Didonet Del Fabro";

	# End: page-specific settings
	#

	# Paste your HTML content between the EOHTML markers!
	$html = <<<EOHTML

	<!-- Main part -->
	<div id="midcolumn">
	<h1><font color='#280882'>AMW</font> Use Cases</h1>

	<a name="goals"></a>
	<img align="right" src="../resources/amwLogoSmall.png" valign="top" style="padding-left: 10px;" alt="AMW Logo" />

	<p align="justify">

	</p>

	Weaving models may be used in several application scenarios, such as <b>metamodel comparison, traceability,
	model matching, model annotation, interoperability</b>.</b> <br />
	This is because it is often necessary to establish relationships between elements of different
	models.
	<p/>
	These use cases are implemented using AMW. AMW supports such a variety of application scenarios
	because it has an adaptive interface
	that handles different metamodel extensions (AMW is fully implemented using the reflective API of EMF).
	<br/>
	The plug-in also provides a set of extensions points that enables to add new functionalities when necessary.

	<p/>This section describes a set of key use cases of AMW. The use cases are illustrated with a general overview.
	Some of them provide more precise documentation, as well as fully implemented examples.
	<p/>

	<p align="justify">
	</p>

	<hr class="clearer" />

	<div class="homeitem3col">
	<h3>List of use cases</h3>
	<ul class="midlist">

	<li>
	<table width="100%">
	<tr>
	<td width="20%" valign="middle">
	<h2><a href="compare/">Metamodel comparison</a></h2>
	</td>
	<td width="60%" align="justify">
	A weaving model contains links that are used to compare different metamodels.
	Metamodels need to be compared for several reasons.
	Two important reasons are: <br/>
	<b>1)</b> to transform the models conforming to different versions of a metamodel; <br/>
	<b>2)</b> to represent the differences between two similar metamodels.<br/>
	</td>
	<td align="center">
	<a href="http://www.inria.fr/recherche/equipes/atlas.en.html">INRIA ATLAS</a>
	</td>
	</tr>
	</table>
	</li>
	<li>
	<table width="100%">
	<tr>
	<td width="20%" valign="middle">
	<h2><a href="traceability/">Traceability</a></h2>
	</td>
	<td width="60%" align="justify">
	Traceability is used in different applications. We consider here the transformation of
	a source model into a target model. It is often necessary to know the set of elements
	of the source model that were used to produce one target model element.
	Weaving models define links to save this traceability information.
	</td>
	<td align="center">
	<a href="http://www.inria.fr/recherche/equipes/atlas.en.html">INRIA ATLAS</a>
	</td>
	</tr>
	</table>
	</li>
	<li>
	<table width="100%">
	<tr>
	<td width="20%" valign="middle">
	<h2><a href="AOM/">Aspect oriented modeling</a></h2>
	</td>
	<td width="60%" align="justify">
	Aspect oriented modeling aims at weaving business models and cross cutting models in a single model.
	There is no preferential model. This means the weaving can be done in any model (e.g., weavings in the cross
	cutting concern AND/OR in the business model).
	The AMW enables to create aspect oriented modeling extensions. The weaving models are interpreted by ATL
	transformations to weave the models.
	</td>
	<td align="center">
	<a href="http://www.inria.fr/recherche/equipes/atlas.en.html">INRIA ATLAS</a>
	</td>
	</tr>
	</table>
	</li>


	<li>
	<table width="100%">
	<tr>
	<td width="20%" valign="middle">
	<h2><a href="matching/">Matching</a></h2>
	</td>
	<td width="60%" align="justify">
	Matching is the semi-automatic process of creating weaving models.
	A matching creates links and calculates a similarity measure between model elements.
	The maching process is the basis for almost all utilisation of weaving models.
	</td>
	<td align="center">
	<a href="http://www.inria.fr/recherche/equipes/atlas.en.html">INRIA ATLAS</a>
	</td>
	</tr>
	</table>
	</li>
	<li>
	<table width="100%">
	<tr>
	<td width="20%" valign="middle">
	<h2><a href="interoperability/"> Tool interoperability<!--</a> --></h2>
	</td>
	<td width="60%" align="justify">
	To support interoperability between different models, it is necessary to represent the
	semantic heterogeneities between the model elements.
	The weaving model is used to capture the semantic heterogeneities between different models or metamodels.
	The weaving model acts as a high-level specification for producing executable model transformations.
	</td>
	<td align="center">
	<a href="http://www.inria.fr/recherche/equipes/atlas.en.html">INRIA ATLAS</a>
	</td>
	</tr>
	</table>
	</li>

	<li>
	<table width="100%">
	<tr>
	<td width="20%" valign="middle">
	<h2><!--<a href="matching/">-->Model alignment<!--</a>--></h2>
	</td>
	<td width="60%" align="justify">
	A model alignement consists of a set of links between the model elements.
	An alignment is used to create an integrated view of two models.
	The alignment may be used as an input to merge algorithms.
	<br/>
	</td>
	<td align="center">
	<a href="http://www.inria.fr/recherche/equipes/atlas.en.html">INRIA ATLAS</a>
	</td>
	</tr>
	</table>
	</li>


	</ul>
	</div>
	<hr class="clearer" />
	</div>

	<div id="rightcolumn">

	</div>

	EOHTML;


	# Generate the web page
	$App->generatePage($theme, $Menu, $Nav, $pageAuthor, $pageKeywords, $pageTitle, $html);
	?>