Update on the inverse use case.
diff --git a/usecases/inverse/index.php b/usecases/inverse/index.php
index 1cb5da4..b7e9857 100644
--- a/usecases/inverse/index.php
+++ b/usecases/inverse/index.php
@@ -27,7 +27,7 @@
<!-- Main part -->
<div id="midcolumn">
- <h1><font color='#280882'>AMW</font> Use Case - Inverting mappings</h1>
+ <h1><font color='#280882'>AMW</font> Use Case - Inverting metamodel mappings</h1>
<a name="goals"></a>
<img align="right" src="../../resources/amwLogoSmall.png" valign="top" style="padding-left: 10px;" alt="AMW Logo" />
@@ -52,7 +52,7 @@
<td>
</td>
<p align="justify">
- Inversing of mappings is on of the most important model management operators. Informally speaking, the operator puts back a given mapping of metamodels. The operator has multiple practical applications. One of them, often underlined in the literature, is support for schema evolution in this context the operator is used as an element of more complex algorithms - see works of Melnik [Mel04]. Below, we describe another possible application of inverses in Sales Force Automation Systems.
+ Inversing of mappings is one of the most important model management operators. Informally speaking, the operator puts back a given mapping of metamodels. The operator has multiple practical applications - it is essential in various model management applications like schema evolution [Mel04], it can also simply serve a role of an 'undo' facility, etc. In this use case, we introduce an application of inverses in system supporting work of salesmen, where there is a need to synchronize data between global database and some local databases stored on PDAs.
</p>
<p align="justify">
The objective of this use case is to show that AMW can easily support the process of inverse mapping generation.
@@ -64,10 +64,16 @@
<a name="overview">Overview</a></h4>
<p align="justify">
- In this use case we generate an inverse weaving model from the weaving model.
+In this use case we generate an inverse weaving model from the weaving model. The figure below presents consecutive steps of mapping inverting. In the first step we find correspondences between two input metamodels (it has a form of a weaving model). Although, core original AMW weaving metamodel is not directed (there is no distinction between source and target), in case of inverting metamodel mapping, such a distinction is necessary. (Therefore, we will use the terms weaving model and inverse weaving model.) In the following step, we generate an inverse weaving model on the basis of a weaving model. Further, we translate this weaving model into an executable ATL transformation, so we are able to transform data from one model to another.
+
<p/>
<p align="justify">
-The figure below shows the relationships between models, metamodels, and a metametamodel in AMW. Source and target models conform to their metamodels; in a special case, they can conform to the same metamodel. A weaving model conforms to its weaving metamodel and contains references to source and target metamodels. Furthermore, there is an ATL transformation that, based on a weaving model (and the weaving metamodel) generates an inverse weaving model. The inverse weaving model conforms to the same metamodel as the initial weaving model. The weaving model and inverse weaving model can be transformed into operational ATL transformations using a higher-order transformation (HOT).
+
+
+ <p/>
+ <p align="justify">
+
+
<p/>
<p align="center">
@@ -77,6 +83,13 @@
</p>
<p align="justify">
+
+
+ </p>
+
+ <p align="justify">
+
+
In order to support inverse metamodel mappings we introduced an extension to the <a href="http://wiki.eclipse.org/index.php/AMW#Core_weaving_metamodel">core weaving metamodel</a>. Among others, in this metamodel we associated with each supported type of a link/operation the type of a link/operation being its inverse (we store this information as annotations).
</p>
@@ -88,7 +101,7 @@
<p align="justify">
-We illustrate our approach to inversing metamodel mapping using an example with two metamodels that describe sale data (metamodels of databases are shown below). One of the metamodels is relational (it contains only flat tables), while the other is XML (nested).
+We illustrate our approach to inversing metamodel mapping using an example with two metamodels that describe sale data (metamodels of databases are shown below). One of the metamodels is relational (it contains only flat tables), while the other is XML (nested). This are metamodels used by a Sales Force Automation (SFA) i.e., a system aimed at automating business tasks of sales teams working out of their offices; such tasks include order processing, contact management, information sharing, customer management, etc. We have a global relational database kept in the headquates of a company (its fragment is presented in the figure below), and small salesmen applications designed for PDAs that uses only fragment of this database using XML format. In the periodical process of synchronisation of these databases inverse mappings are crucial.
</p>
@@ -114,7 +127,7 @@
<a href="../../examples/SFA/SFA.zip"><h3>Example</h3></a>
</td>
<td>
- This example implements an inversing metamodel mappings. It is based on the example described above in the paper.
+ This example implements inversing metamodel mappings. It is based on the example described above in the paper.
<p/>
</td>
</tr>
@@ -148,14 +161,6 @@
</tr>
</table>
-
-
- <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;">
- <a name="acknowledgement"></a>Acknowledgment
- </h4>
-
- This work was carried out during the tenure of an ERCIM "Alain Bensoussan" Fellowship Programme.
- <p/>
<h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;">
<a name="reference"></a>Reference
@@ -164,15 +169,6 @@
[Mel04] Sergey Melnik: Generic Model Management: Concepts and Algorithms Springer 2004
<p/>
</div><p/>
- <div id="rightcolumn">
- <div class="sideitem">
- <h6>General Information</h6>
- <ul>
- <li style="list-style:none">June 2007</li>
- <li style="list-style:none">By <a href="http://www.sciences.univ-nantes.fr/lina/atl/contrib/kozankiewicz">Hanna Kozankiewicz</a> (INRIA)</li>
- </ul>
- </div>
- </div>
EOHTML;
diff --git a/usecases/resources/genArch.png b/usecases/resources/genArch.png
index 6a37a1b..38aef69 100644
--- a/usecases/resources/genArch.png
+++ b/usecases/resources/genArch.png
Binary files differ
diff --git a/usecases/resources/mapping.png b/usecases/resources/mapping.png
index b5ef9ae..722a7f7 100644
--- a/usecases/resources/mapping.png
+++ b/usecases/resources/mapping.png
Binary files differ
