Update in the use cases section
diff --git "a/examples/AOM/AMW_AOP_2006\1330.5\135.ppt" b/examples/AOM/AMW_AOP_2007.ppt
similarity index 82%
rename from "examples/AOM/AMW_AOP_2006\1330.5\135.ppt"
rename to examples/AOM/AMW_AOP_2007.ppt
index f4960bc..72a5148 100644
--- "a/examples/AOM/AMW_AOP_2006\1330.5\135.ppt"
+++ b/examples/AOM/AMW_AOP_2007.ppt
Binary files differ
diff --git a/examples/Scade/ScadeFull.zip b/examples/Scade/ScadeFull.zip
new file mode 100644
index 0000000..b1d9702
--- /dev/null
+++ b/examples/Scade/ScadeFull.zip
Binary files differ
diff --git a/examples/Scade/ScadeSimple.zip b/examples/Scade/ScadeSimple.zip
new file mode 100644
index 0000000..27c76f8
--- /dev/null
+++ b/examples/Scade/ScadeSimple.zip
Binary files differ
diff --git a/examples/Scade/Scade_doc.php b/examples/Scade/Scade_doc.php
new file mode 100644
index 0000000..0e171b5
--- /dev/null
+++ b/examples/Scade/Scade_doc.php
@@ -0,0 +1,128 @@
+<?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'
+
+ #*****************************************************************************
+ #
+ # AMW_Match_SF_doc.php
+ #
+ # Author: Marcos Didonet Del Fabro
+ # Date: 2005-07-24
+ #
+ # Description: Type your page comments here - these are not sent to the browser
+ #
+ #
+ #****************************************************************************
+
+ #
+ # Begin: page-specific settings. Change these.
+ $pageTitle = "HowTo - Metamodel comparison use case";
+ $pageKeywords = "";
+ $pageAuthor = "Marcos Didonet Del Fabro";
+
+ # Paste your HTML content between the EOHTML markers!
+ $html = <<<EOHTML
+
+<!-- Main part -->
+ <div id="midcolumn">
+ <table width="100%">
+ <tr>
+ <td width="50%">
+ <h1>$pageTitle</h1>
+ </td>
+ </tr>
+ </table>
+
+ <p>
+
+ This HowTo explains how to create weaving models that are used to compare metamodels and to produce ATL transformation. <p/>
+
+ The general approach of this use case is explained in more details in the <a href="../../usecases/">Use Cases</a> section.
+
+ <h2>Instructions</h2>
+
+ <b>Metamodels</b>: these metamodels are injected into Ecore by clicking in the context menu "Inject KM3 into Ecore metamodel":<br/>
+ - <i>Scade.km3</i><br/>
+ - <i>ScadeNew.km3</i>; <br/>
+
+ <h4>Producing a new weaving model</h4>
+ A weaving model containing a reference to the woven models (Scade versions) is created manually using the AMW wizard. It creates one
+ root element:<br/>
+
+ <p/>
+ <ul class="midlist">
+ <li>
+ In the "models" folder, select "New...", "Weaving Model".
+ </li><p/>
+ <li>
+ <b>In the AMW wizard first page</b>, the following metamodel extensions must be selected: <br/>
+ <i>- mw_base_extension.km3:</i> the base extension to the core metamodel. It extends all abstract classes of the core weaving metamodel.<br/>
+ <i>- mmw_match.km3:</i> defines simple links between classes, attributes and references.<br/>
+ <i>- mmw_compare.km3:</i> defines links with elements without any equivalence in both metamodels.<br/>
+ <i>- mmw_propagation.km3:</i> defines a set of auxiliary structures to execute the Similarity Flooding algorithm.<br/>
+ </li><p/>
+ <li>
+ <b>In the wizard second page</b>, select "New model" and fill the text field with the name of the weaving model (ScadeCmp.amw). After that, select "MatchModel" as the current "WModel".
+ This type of WModel must be selected to be able to execute the matching heuristics correclty.
+ </li><p/>
+ <li>
+ <b>The wizard third page</b> sets up the two models that will be woven. Select first the "leftM" model, and click on "Edit selected model".
+ This button opens a new window. Select "ModelRef" in the "WModelRef" combo. Then
+ select "DefaultWovenPanelExtension", that is the implementation for this type of "WModelRef" (standard identification mechanism of EMF).
+ Finally, select "Scade.ecore" in the metamodel text field. <br/>
+ The same procedure must be done for the right metamodel, "ScadeNew.ecore".
+ </li>
+ </ul>
+
+ <h4>Executing the matching transformations</h4>
+
+ The AMW plug-in provides a set of matching transformations that automate the task of creating weaving models. To execute these transformations,
+ open the context menu of the weaving panel (the middle panel) and select the "Match" submenu.
+ This submenu contains a list of the matching transformations available. <br/>
+ This use case executes 5 matching transformations: "Cartesian product", "Name Similarity", "Threshold", "Link rewriting" and
+ "Link rewriting - non equivalence". Each matching transformation produces a new weaving model, and adds a predefined suffix to it. This is because we don't want to override the current model.
+ Thus, the new weaving model should be opened to be able to execute the subsequent transformation.
+ <p/>
+ <ul class="midlist">
+ <li>
+ Cartesian product: produces a Cartesian product of the elements with the same type. It produces a new weaving model with the suffix
+ "_cp" (ScadeCmp_cp.amw).
+ </li>
+ <li>
+ Name similarity: this transformation assigns a high similarity value to the elements that have the same name.
+ It produces a model with the suffix "_equal". (ScadeCmp_cp_equal.amw)
+ </li>
+ <li>
+ Threshold: selects the links with the highest similarity values.
+ Produced model: (ScadeCmp_cp_equal_thres.amw). Suffix: "_thres"
+ </li>
+ <li>
+ Link rewriting: reorganizes the links according to the containment relationships between Classes, Attributes and References.
+ Produced model: (ScadeCmp_cp_equal_thres_lr.amw). Suffix: "_lr"
+ </li>
+ <li>
+ Link rewriting - non equivalence: creates links with the elements that do not have equivalence in the left or right metamodels.
+ Produced model: (ScadeCmp_cp_equal_thres_lr_noneq.amw). Suffix: "_noneq"
+ </li>
+ </ul>
+
+ <h4>Generating and extracting the ATL transformation</h4>
+
+ The AMW plug-in contains a higher-order transformation (HOT) that interprets the weaving model and that produces an ATL transformation.
+ To execute this transformation, open the context menu of the weaving panel (the middle panel) and select the "Transform" submenu. Then click on "Generate transformation (HOT)".
+ This action produces an ATL model (ScadeCmp_cp_equal_thres_lr_hot.ecore). <br/>
+ The output transformation model is extracted to an ATL file by clicking in the context menu "Extract ATL-0.2 model to ATL-0.2 file".<br/>
+
+ <p/>
+ <b>Installation requirements:</b> <p/>
+ The AMW, ATL and AM3 plug-ins must be installed. See the <a href="../../download">download page</a>.
+ <p/>
+ <b>Remark(s):</b></p>
+ All the injection and extraction menus (Ecore and ATL) are available in the "AM3" perspective and in the "AM3 Resource Navigator" view.
+ <p/>
+ </div>
+
+EOHTML;
+
+
+ # Generate the web page
+ $App->generatePage($theme, $Menu, $Nav, $pageAuthor, $pageKeywords, $pageTitle, $html);
+?>
diff --git a/examples/amwExamples.xml b/examples/amwExamples.xml
index 06e51dc..dcc2853 100644
--- a/examples/amwExamples.xml
+++ b/examples/amwExamples.xml
@@ -105,6 +105,25 @@
</amwExample>
</category>
+
+ <category>
+ <name>Metamodel comparison</name>
+ <description>
+ </description>
+ <amwExample>
+ <shortName>Scade_compare</shortName>
+ <name>Scade metamodel comparison</name>
+ <docLink>../usecases/compare/</docLink>
+ <sourceLink>Scade/ScadeSimple.zip</sourceLink>
+ <description>
+ This example automatically produces a weaving model used to compare two versions of the same Scade
+ metamodel. A complete description of this example is available in the <a href="../usecases/compare/">
+ use cases</a> section.
+ </description>
+ <pubDate>17/01/2007</pubDate>
+ </amwExample>
+
+ </category>
<category>
<name>Semi-automatic generation of weaving models</name>
diff --git a/examples/index.php b/examples/index.php
index 1647f6c..7bec71d 100644
--- a/examples/index.php
+++ b/examples/index.php
@@ -16,7 +16,7 @@
# Begin: page-specific settings. Change these.
$pageTitle = "AMW Examples";
$pageKeywords = "AMW, model transformation, model, metamodel extension";
- $pageAuthor = "Freddy Allilaire";
+ $pageAuthor = "Marcos Didonet Del Fabro";
# End: page-specific settings
#
diff --git a/index.php b/index.php
index 584cbed..c36ab4c 100644
--- a/index.php
+++ b/index.php
@@ -46,9 +46,9 @@
<hr/>
<b><a href="usecases/">Use cases</a></b><br/>
The establishement of links between model or metamodel elements is present
- in numerous application scenarios. For that reason, there are many possible application scenarios, such as
- <b>metamodel comparison, model traceability, model alignment, model annotation, interoperability.</b> <br />
- More information about the use cases is available <b><a href="usecases/">here</a></b>.
+ in numerous application scenarios, such as <b>metamodel comparison, traceability, model matching, model annotation, interoperability.</b> <br />
+ The <b><a href="usecases/">use cases</a></b> section provides a set of key scenarios that use weaving models.
+ The use cases contain a general overview, extra documentation and examples.
<hr/>
AMW provides a base weaving metamodel enabling to create links between model elements and associations between links. The
metamodel may be extended to add other mapping semantics. This way there is the possibility of creating variable mapping
@@ -85,7 +85,7 @@
<table width="100%">
<tr>
<td width="80%" valign="bottom">
- <b><a href="publication.php">Publications</a></b><font size="-3"></font>
+ <b><a href="publication.php">Publications</a></b><font size="-3">(new)</font>
</td>
<td align="right">
<a href="publication.php"><img align="right" src="../resources/images/reference.gif" valign="top"/></a>
@@ -110,7 +110,7 @@
<table width="100%">
<tr>
<td width="80%" valign="bottom">
- <a href="examples/"><b>AMW Examples</b>, matching library</a><font size="-3"> (new)</font>
+ <a href="examples/"><b>AMW Examples</b>, matching library</a><font size="-3"></font>
</td>
<td align="right">
<a href="examples/"><img align="right" src="resources/amwLogoSmall.png" valign="top" /></a>
diff --git a/publication.php b/publication.php
index 956688d..07bca90 100644
--- a/publication.php
+++ b/publication.php
@@ -43,41 +43,47 @@
<br/><br/>
<h4>2007</h4>
+
<li><a href="http://www.sciences.univ-nantes.fr/lina/atl/bibliography/SAC07">[SAC07]</a></td>
Del Fabro, MD, and Valduriez, P :
Semi-automatic Model Integration using Matching Transformations and Weaving Models .
In: The 22th Annual ACM SAC, MT 2007 - Model Transformation Track, Seoul (Korea), 2007.
To appear.
- <a href="http://www.model-transformation.org/MT2007/">(link)</a>
- </li>
-
+ <a href="http://www.sciences.univ-nantes.fr/lina/atl/www/papers/didonet/web_sac_matching.pdf">(link)</a>
+ </li><br />
+ <li><a href="http://www.sciences.univ-nantes.fr/lina/atl/bibliography/ICSEM07">[ICSEM07]</a></td>
+ Jossic, A, Didonet Del Fabro, M, Lerat, JP, Bézivin, J, Jouault, F. Model Integration with Model Weaving: a Case Study in System Architecture
+ In: ICSEM'07 - International Conference on Systems Engineering and Modeling. Israel, 2007.
+ To appear.
+ <a href="http://www.sciences.univ-nantes.fr/lina/atl/www/papers/didonet/ModelIntegrationICSEM07_draft.pdf">(link)</a>
+ </li>
<h4>2006</h4>
<li>
<a href="http://www.sciences.univ-nantes.fr/lina/atl/bibliography/ODBASE06">[ODBASE2006]</a>
Didonet Del Fabro, M, Bézivin, J, and Valduriez, P : Model-driven Tool Interoperability:
an Application in Bug Tracking. In: ODBASE'06(OTM Federated Conferences). 2006.
- </li><br /><br />
+ </li><br />
<li>
<a href="http://www.sciences.univ-nantes.fr/lina/atl/bibliography/ESUMMIT_AMW06">[ESummit2006]</a>
Didonet Del Fabro, M, Bézivin, J, and Valduriez, P : Weaving Models with the Eclipse AMW plugin.
In: Eclipse Modeling Symposium, Eclipse Summit Europe 2006, Esslingen, Germany, 2006.
- </li><br /><br />
+ </li><br />
<li>
<a href="http://www.sciences.univ-nantes.fr/lina/atl/bibliography/MA06">[ECOOP2006]</a> Kurtev, I, and Didonet Del Fabro, M : A DSL for Definition of Model Composition Operators.
In 2nd Workshop on Models and Aspects - Handling Crosscutting Concerns in MDSD, ECOOP 2006, Nantes, France. 2006
- </li><br /><br />
+ </li><br />
<li>
<a href="http://www.sciences.univ-nantes.fr/lina/atl/bibliography/eTX2006_3">[eTX2006]</a>
Didonet Del Fabro, M, Bézivin, J, and Valduriez, P : Designing an Adaptive Weaving Workbench using
Eclipse Contributions.
In: Proceedings of the Eclipse Technology eXchange workshop (eTX) at the ECOOP 2006 Conference,
Nantes, France. 2006.
- </li><br /><br />
+ </li><br />
<li>
<a href="http://www.sciences.univ-nantes.fr/lina/atl/bibliography/ECMDA06">[ECMDA2006]</a> Bézivin J, Bouzitouna S, Didonet Del Fabro M, Gervais M P, Jouault F, Kolovos D, Kurtev I, Paige R F.
A Canonical Scheme for Model Composition, In Proc. European Conference in Model Driven Architecture (EC-MDA) 2006,
- Bilbao, Spain, July 2006 <br /><br />
+ Bilbao, Spain, July 2006 <br />
</li>
<h4>2005</h4>
@@ -85,30 +91,28 @@
<li>
<a href="http://www.sciences.univ-nantes.fr/lina/atl/bibliography/BDA05">[BDA2005]</a>
Didonet Del Fabro, M, Bézivin, J, Jouault, F, and Valduriez, P : Applying Generic Model Management to Data Mapping. In: Proceedings of Bases de Données Avancées (BDA05), 17-20 october 2005, Saint-Malo, France.
- <br /><br />
- </li>
+
+ </li><br />
<li>
<a href="http://www.sciences.univ-nantes.fr/lina/atl/bibliography/ECOOP2005">[ECOOP2005]</a>
Bézivin, J, Didonet Del Fabro, M, Jouault, F, and Valduriez, P : Combining Concerns with Models. In: First Workshop on Models and Aspects - Handling Crosscutting Concerns in Model-Driven Software Development (MDSD), ECOOP 2005.
- <br /><br />
- </li>
+
+ </li><br />
<li>
<a href="http://www.sciences.univ-nantes.fr/lina/atl/bibliography/GTTSE05_Didonet">[GTTSE2005]</a>
Didonet Del Fabro, M, and Jouault, F : Model Transformation and Weaving in the AMMA Platform. In: Pre-proceedings of the Generative and
Transformational Techniques in Software Engineering (GTTSE 05), Workshop. Centro de Ciências e Tecnologias de Computação, Departemento de Informatica, Universidade do Minho, Braga, Portugal, pages 71--77.
- <br /><br />
- </li>
+
+ </li><br />
<li>
<a href="http://www.sciences.univ-nantes.fr/lina/atl/bibliography/MDSD05_1">[MDSD05]</a>
Abouzahra, A, Bézivin, J, Didonet Del Fabro, M, and Jouault, F : A Practical Approach to Bridging Domain Specific Languages with UML profiles. In: Proceedings of the Best Practices for Model Driven Software Development at OOPSLA 05, San Diego, California, USA.
- <br /><br />
- </li>
+
+ </li><br />
<li>
<a href="http://www.sciences.univ-nantes.fr/lina/atl/bibliography/IDM2005">[IDM2005]</a>
- Didonet Del Fabro, M, Bézivin, J, Jouault, F, Breton, E, and Gueltas, G : AMW: a generic model weaver. In: Proceedings of the 1ères Journées sur l'Ingénierie Dirigée par les Modèles.
- <br /><br />
+ Didonet Del Fabro, M, Bézivin, J, Jouault, F, Breton, E, and Gueltas, G : AMW: a generic model weaver. In: Proceedings of the 1ères Journées sur l'Ingénierie Dirigée par les Modèles.
</li>
-
<h4>2004</h4>
<li>
diff --git a/usecases/AOM/index.php b/usecases/AOM/index.php
index 61451eb..3ba7946 100644
--- a/usecases/AOM/index.php
+++ b/usecases/AOM/index.php
@@ -49,14 +49,15 @@
<td></td>
<td>
- In traditional aspect oriented programming, a program implements the business logic to
- solve a specific problem. Usually there are many cross cutting concerns that are not
- part of main problem, such as security, logging, tracing, persistency, etc.
- These concerns are created separately, and woven in the code.
<p/>
In aspect oriented modeling, the program and the cross cutting concerns are represented by models.
Consequently, there is no preferential model. This means the weaving can be done in any model (e.g., weavings in the cross
- cutting concern as well). <br/>
+ cutting concern as well).
+ <br/>
+ This is different from traditional aspect oriented programming, because a program implements the business logic to
+ solve a specific problem. Usually there are many cross cutting concerns that are not
+ part of main problem, such as security, logging, persistency, etc.
+ These concerns are created separately, and woven in the code.
<h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;"><a name="overview">Overview</a></h4>
@@ -132,16 +133,21 @@
<td align="center">
<!-- <a href="../../examples/#Matching transformation library">-->
- <h3>Aspect Oriented Modeling</h3><!--</a>-->
+ <h3><a href="../../examples/AOM/AOM.zip">Communication <br/>example</a></h3>
</td>
<td>
- <a href="../../examples/AOM/AOM.zip">Simple communication example<p/>
- <a href="../../examples/AOM/AMW_AOP_2006[0.5].ppt">Presentation<p/>
-
+ Implementation of the simple communication example using AMW and ATL .
</td>
</tr>
-
-
+ <td align="center">
+ <!-- <a href="../../examples/#Matching transformation library">-->
+ <h3><a href="../../examples/AOM/AMW_AOP_2007.ppt">Presentation</a></h3>
+ </td>
+ <td>
+ This presentation is a general overview about how Aspect Oriented Modeling is
+ used to solve current AOP problems.
+ </td>
+ </tr>
</table>
</div>
</div>
diff --git a/usecases/TGen/index.php b/usecases/TGen/index.php
new file mode 100644
index 0000000..4ad6504
--- /dev/null
+++ b/usecases/TGen/index.php
@@ -0,0 +1,164 @@
+<?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 Case - ATL Generation";
+ $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 Case - ATL Generation</h1>
+
+ <a name="goals"></a>
+ <img align="right" src="../../resources/amwLogoSmall.png" valign="top" style="padding-left: 10px;" alt="AMW Logo" />
+ <blockquote>
+ <ul>
+ <li><a href="#overview"><b>Overview</b></a></li>
+ <li><a href="#download"><b>Download and examples</b></a></li>
+ <!--<li><a href="#documentation"><b>Documentation</b></a></li>-->
+ </ul>
+ </blockquote>
+
+ <hr class="clearer" />
+
+ <div id="container>
+ <table>
+ <COLGROUP>
+ <COL width="2%">
+ <COL width="98%">
+ <tr><td></td>
+
+ <td>
+
+ Model transformations
+
+ To support interoperability between different tools, it is necessary to represent the semantic heterogeneities between the 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.
+
+ <br/>
+ A weaving model is capable of capturing different kinds of links.
+ The establishement of links between model or metamodel elements is present in numerous application scenarios,
+ such as model comparison, model alignment, merging, etc.
+
+
+ <br/>
+ It is of major importance to provide mechanisms to easily create these links. <br/>
+ The creation of links is usually a semi-automatic phase. The links can be created manually with the help
+ of a user interface (e.g., the Atlas Model Weaver), and with the help of different matching heuristics.
+ This process is called <b>Matching</b>.
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;"><a name="overview">Overview</a></h4>
+
+ <p align="justify">
+
+ Consider it is necessary to establish links between two metamodels, <i>MMa</i> and <i>MMb</i>.
+ The general process to create the links between them is the following: the two metamodels are the input of a matching transformation (see below).
+ This first transformation creates a weaving model between these metamodels. This weaving model is the input
+ of other matching transformations that are sequentially executed. Every matching transformation
+ create more accurate links according to specific similarity criteria.
+ At any time after the execution of one matching transformation, the weaving model can be
+ verified and refined in a Model Weaver graphical interface.
+ </p>
+ <p align="center">
+ <img src="../resources/interop.png"/>
+ <br /><br />
+ <b>"Interoperability" Use Case's Overview</b>
+ </p>
+ <p align="justify">
+ Every matching transformation executes a different heuristic to calculate a similarity estimation between
+ each pair model elements. There are several ways to calculate the similarity between two model elements.
+ For instance, using the string similarity between names, using a dictionary os synonyms, or taking into
+ account the structure of model elements. More complex links between several model elements are often created
+ manually with the help of a Model Weaver interface.
+ </p>
+ <p align="center">
+ <img src="../resources/matching_transfos.png"/>
+ <br /><br />
+ <b>Examples</b>
+ </p>
+
+ <br>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C;
+ background-position: top left; background-repeat; repeat-x;">
+ <a name="download">Download and examples</a></h4>
+
+ <table>
+ <COLGROUP>
+ <COL width="15%">
+ <COL width="20%">
+ <COL width="65%">
+ <tr>
+ <td ALIGN=center></td>
+
+ <td align="center">
+ <a href="../../examples/#Matching transformation library">
+ <h3>Matching transformations</h3>
+ </a>
+ </td>
+ <td>
+ The Atlas Model Weaver plugin has an integrated environment to execute a set of matching transformations.
+ Go to the <a href="../../download/">download page</a>.
+ Many matching transformations are also available in the
+ <a href="../../examples/#Matching transformation library">matching transformation library</a>.
+
+ </td>
+ </tr>
+
+ <tr>
+ <td></td>
+ <td align="center">
+ <a href="../../examples/#Semi-automatic generation of weaving models"><h3>Examples</h3></a>
+ </td>
+ <td>
+ This set of examples are complete application scenarios that combine different matching transformations
+ to produce weaving models for different purposes.
+ They are available in <a href="../../examples/#Semi-automatic generation of weaving models">examples page</a>.
+ </td>
+ </tr>
+ </table>
+ </div>
+ </div>
+
+ <!-- Right Part
+ <div id="rightcolumn">
+ <div class="sideitem">
+ <h6>Related Links</h6>
+ <ul>
+ <li><a href="http://"></a></li>
+ <li>-------------------------------------</li>
+ <li><a href="http:///"></a></li>
+ <li>-------------------------------------</li>
+ <li><a href="http://"></a></li>
+ </ul>
+ </div>
+
+ </div>-->
+
+
+EOHTML;
+
+
+ # Generate the web page
+ $App->generatePage($theme, $Menu, $Nav, $pageAuthor, $pageKeywords, $pageTitle, $html);
+?>
\ No newline at end of file
diff --git a/usecases/compare/index.php b/usecases/compare/index.php
index f3a3eef..3616c56 100644
--- a/usecases/compare/index.php
+++ b/usecases/compare/index.php
@@ -51,7 +51,8 @@
Metamodels need to be compared for several reasons. Two important reasons are:
1) to transform the models conforming to different versions of a metamodel;
- 2) to represent the differences between two similar metamodels. In this use case the objective is to demonstrate
+ 2) to represent the differences between two similar metamodels.
+ <p/>In this use case, the objective is to demonstrate
how weaving models created with the help of the AMW plugin are used to compare different models and
to produce executable model transformations.
@@ -59,19 +60,24 @@
<p align="justify">
- Consider two different versions of the same metamodel <i>MMs(v1)</i> and <i>MMs(v2)</i>.
- The goal is to transform the source model conforming to <i>MMs(v1)</i> into the target model conforming to <i>MMs(v2)</i>.
- to be able to correclty transform the equivalent elements, it is necessary to compare the set of elements from both metamodels.
+ This use case compares two different versions of the same metamodel, <i>Scade(v1)</i> and <i>Scade(v2)</i>. The different versions
+ have been developed by two different persons, based on a formal specification. <a href="http://www.esterel-technologies.com/products/scade-suite/">Scade</a> is a standard for
+ development of embedded software for the Avionics Industry.
+
+ The goal is to produce a transformation that transforms the source model conforming to <i>Scade(v1)</i> into the target model conforming
+ to <i>Scade(v2)</i>.
+ To be able to correclty transform the equivalent elements, it is necessary to compare the elements from both metamodels.
<p/>
The first step is to create a weaving model containing equivalence links between the model elements. This is done by
- executing transformations and by refining the weaving model with the AMW prototype.
- These transformations assign a similarity value between the elements of both metamodels. A high similarity value means
+ executing matching transformations and by refining the weaving model in the AMW prototype.
+ These transformations assign a similarity value between the elements of both metamodels. For instance, we assign high similarity values
+ for elements that have the same name and type. A high similarity value means
the element have a good probability to the equivalent. <p/>
This weaving model is a declarative representation of the links between the metamodels. The weaving model is used to produce
a model transformation. This model transformation is responsible to translate the source model into the target model.
</p>
<p align="center">
- <img src="../resources/comparison.png"/>
+ <img src="../resources/compare_scade.png"/>
<br /><br />
<b>"Metamodel comparison" Use Case's Overview</b>
</p>
@@ -80,15 +86,21 @@
The metamodel extension contains an <i>Equivalent</i> link. This link contains a <i>similarity</i> attribute that saves the similarity
estimation between a <i>left</i> and a <i>right</i> element.
This link is extended by different kinds of links, depending on the type of elements that are being compared, for example <i>AttributeEqual</i> and
- <i>ReferenceEqual</i>.
- For the elements that have very low similarity value, the <i>Equivalent</i> links may be transformed into a <i>NotEquivalent</i> link.
+ <i>ReferenceEqual</i>. The relations between <i>ElementEqual</i> and <i>AttributeEqual</i> links are created according to the containment
+ relations between Classes and Attributes. For the elements that have similarity value lower than a given threshold,
+ the <i>Equivalent</i> links are rewritten into <i>NotEquivalent</i> links.
</p>
<p align="center">
<img src="../resources/comparison_metamodel.png"/>
<br /><br />
<b>Metamodel extension for comparison (excerpt)</b>
</p>
-
+ The weaving model is used to produce a transformation from the source model into the target model.
+ A rule from this transformation is shown below.
+ <p align="center">
+ <img src="../resources/compare_transformation.png"/>
+ <br /><br />
+ <b>Transformation rule automatically generated</b>
<br>
<h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C;
@@ -103,19 +115,39 @@
<tr>
<td align="center">
- <!-- <a href="../../examples/#Matching transformation library">-->
- <h3>Metamodel Comparison</h3><!--</a>-->
+ <h3><a href="../../download/">Metamodel<br/>Comparison</a></h3><!--</a>-->
</td>
<td>
- The Atlas Model Weaver plugin has an integrated environment that enables comparing two models.
- It provides a set of transformations that create weaving models.
+ The Atlas Model Weaver plugin has an integrated environment that enables to easily compare two models.
Go to the <a href="../../download/">download page</a>. AMW also produces a model transformation based on
a weaving model. These functionalities are available on the weaving panel context menu. <p/>
The accuracy of the weaving model depends on the proximity of the models that are compared.
</td>
</tr>
+ <td align="center">
+ <h3><a href="../../examples/Scade/ScadeSimple.zip">Scade simple</a></h3><!--</a>-->
+ </td>
+ <td>
+ This example uses two simplified versions of the Scade metamodels (arround 30 classes) to easily illustrate
+ the metamodel comparison use case.
+ </td>
+ </tr>
-
+ <td align="center">
+ <h3><a href="../../examples/Scade/ScadeFull.zip">Scade complete</a></h3><!--</a>-->
+ </td>
+ <td>
+ This example is a full version of the Scade metamodels, with arround 400 elements each. It contains
+ the weaving models and the transformation that was generated.
+ </td>
+ </tr>
+ <td align="center">
+ <h3><a href="../../examples/Scade/Scade_doc.php">Example HowTo</a></h3><!--</a>-->
+ </td>
+ <td>
+ This document is a step-by-step <b>HowTo</b> that explains how to execute the examples.
+ </td>
+ </tr>
</table>
</div>
</div>
diff --git a/usecases/index.php b/usecases/index.php
index 15f6a8c..5b52420 100644
--- a/usecases/index.php
+++ b/usecases/index.php
@@ -34,7 +34,22 @@
<p align="justify">
</p>
- We describe here a set of use cases for model weaving.
+
+ 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>
@@ -99,7 +114,10 @@
</td>
</tr>
</table>
- </li><li>
+ </li>
+
+
+ <li>
<table width="100%">
<tr>
<td width="20%" valign="middle">
@@ -116,6 +134,25 @@
</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>
@@ -134,24 +171,7 @@
</tr>
</table>
</li>
- <li>
- <table width="100%">
- <tr>
- <td width="20%" valign="middle">
- <h2><!--<a href="interoperability/"> -->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>
+
</ul>
</div>
diff --git a/usecases/resources/compare_scade.PNG b/usecases/resources/compare_scade.PNG
new file mode 100644
index 0000000..28badfa
--- /dev/null
+++ b/usecases/resources/compare_scade.PNG
Binary files differ
diff --git a/usecases/resources/compare_transformation.png b/usecases/resources/compare_transformation.png
new file mode 100644
index 0000000..e3dfe8f
--- /dev/null
+++ b/usecases/resources/compare_transformation.png
Binary files differ
diff --git a/usecases/resources/comparison_title.jpg b/usecases/resources/comparison_title.jpg
new file mode 100644
index 0000000..56e7d98
--- /dev/null
+++ b/usecases/resources/comparison_title.jpg
Binary files differ
