moved resources from deprecated m2m/atl location
diff --git a/atlTransformations/ATL2BindingDebugger/ATL2BindingDebugger.zip b/atlTransformations/ATL2BindingDebugger/ATL2BindingDebugger.zip
new file mode 100644
index 0000000..247295c
--- /dev/null
+++ b/atlTransformations/ATL2BindingDebugger/ATL2BindingDebugger.zip
Binary files differ
diff --git a/atlTransformations/ATL2BindingDebugger/README.txt b/atlTransformations/ATL2BindingDebugger/README.txt
new file mode 100644
index 0000000..8ffc073
--- /dev/null
+++ b/atlTransformations/ATL2BindingDebugger/README.txt
@@ -0,0 +1,43 @@
+The ATL2BindingDebugger ATL transformation adds a debug instruction to each binding in an ATL transformation.
+
+For instance:
+rule R1 {
+ from
+ s : ATL!Module
+ to
+ t : ATL!Module (
+ name <- s.name
+ )
+}
+
+Will be transformed into:
+rule R1 {
+ from
+ s : ATL!Module
+ to
+ t : ATL!Module (
+ name <- s.name.debug('R1.t.name')
+ )
+}
+
+The following debug information is displayed in a console view or in a terminal when the generated transformation is executed:
+ R1.t.name: 'ATL2BindingDebugger'
+
+This transformation uses ATL refining mode as defined in [1].
+This kind of transformation is a HOT (Higher Order Transformation): it takes a transformation as source and as target.
+
+Source and target models conform to ATL metamodel.
+A sample source model (sample-ATL-0.2.ecore) and its corresponding target model (Sample-ATL-0.2(Debug).ecore) are given.
+
+File Configuration.png shows how to configure the transformation for launch.
+It is now possible to use the "Metamodel by URI" button to use a metamodel already registered in EMF.
+We advise you to use this new feature to configure this transformation because ATL metamodel is already registered in EMF by ADT plugins.
+Thanks to that, the latest version of ATL metamodel will always be used.
+
+To serialize the generated ATL transformation you can use ATL extractor available in AM3 project (http://dev.eclipse.org/viewcvs/indextech.cgi/~checkout~/gmt-home/subprojects/AM3/index.html).
+You can create easily input models thanks to ATL injector (also available in AM3 project).
+
+If you have some problems with this, please use ATL mailing list (http://groups.yahoo.com/group/atl_discussion/).
+
+References:
+[1] Jouault, F., and Kurtev, I., Transforming Models with ATL, in proceedings of the Model Transformation in Practice Workshop, October 3rd 2005, part of the MoDELS 2005 conference
diff --git a/atlTransformations/ATL2Problem/ATL2Problem.zip b/atlTransformations/ATL2Problem/ATL2Problem.zip
new file mode 100644
index 0000000..e3e931e
--- /dev/null
+++ b/atlTransformations/ATL2Problem/ATL2Problem.zip
Binary files differ
diff --git "a/atlTransformations/ATL2Problem/ExampleATL2Problem\133v00.01\135.pdf" "b/atlTransformations/ATL2Problem/ExampleATL2Problem\133v00.01\135.pdf"
new file mode 100644
index 0000000..c7faddd
--- /dev/null
+++ "b/atlTransformations/ATL2Problem/ExampleATL2Problem\133v00.01\135.pdf"
Binary files differ
diff --git a/atlTransformations/ATL2Tracer/ATL2Tracer.zip b/atlTransformations/ATL2Tracer/ATL2Tracer.zip
new file mode 100644
index 0000000..381b248
--- /dev/null
+++ b/atlTransformations/ATL2Tracer/ATL2Tracer.zip
Binary files differ
diff --git a/atlTransformations/ATL2Tracer/README.txt b/atlTransformations/ATL2Tracer/README.txt
new file mode 100644
index 0000000..5a13f60
--- /dev/null
+++ b/atlTransformations/ATL2Tracer/README.txt
@@ -0,0 +1,27 @@
+The ATL2Tracer transformation shows how traceability generating code can be relatively easily added to
+ATL code. It moreover shows that this process can be fully automated.
+To find more details concerning dealing traceability in ATL, please refer to [1].
+
+This transformation uses ATL refining mode as defined in [2].
+This kind of transformation is a HOT (Higher Order Transformation): it takes a transformation as source and as target.
+
+Source and target models conform to ATL metamodel.
+A sample source model (sample-ATL-0.2.ecore in ATL2Tracer folder) and its corresponding target model (sample-ATL-0.2-Tracer.ecore in Tracertest/Input) are given.
+
+File configurationATL2Tracer.png shows how to configure the transformation for launch.
+It is now possible to use the "Metamodel by URI" button to use a metamodel already registered in EMF.
+We advise you to use this new feature to configure this transformation because ATL metamodel is already registered in EMF by ADT plugins.
+Thanks to that, the latest version of ATL metamodel will always be used.
+
+To serialize the generated ATL transformation you can use ATL extractor available in AM3 project (http://dev.eclipse.org/viewcvs/indextech.cgi/~checkout~/gmt-home/subprojects/AM3/index.html).
+You can create easily input models thanks to ATL injector (also available in AM3 project).
+
+Once the target model with tracer is created. You can test this transformation.
+File configurationTracerTest.png shows how to configure the transformation for launch.
+Sample target models (sample-ATL-0.2-OUT.ecore and sample-Trace-OUT.ecore in Tracertest/Output) are given.
+
+If you have some problems, please use ATL mailing list (http://groups.yahoo.com/group/atl_discussion/).
+
+References:
+[1] Jouault, F : Loosely Coupled Traceability for ATL. In: Proceedings of the European Conference on Model Driven Architecture (ECMDA) workshop on traceability, Nuremberg, Germany.
+[2] Jouault, F., and Kurtev, I., Transforming Models with ATL, in proceedings of the Model Transformation in Practice Workshop, October 3rd 2005, part of the MoDELS 2005 conference
diff --git a/atlTransformations/Ant2Maven/Ant2Maven.zip b/atlTransformations/Ant2Maven/Ant2Maven.zip
new file mode 100644
index 0000000..1ae28dd
--- /dev/null
+++ b/atlTransformations/Ant2Maven/Ant2Maven.zip
Binary files differ
diff --git "a/atlTransformations/Ant2Maven/ExampleAnt2Maven\133v00.01\135.pdf" "b/atlTransformations/Ant2Maven/ExampleAnt2Maven\133v00.01\135.pdf"
new file mode 100644
index 0000000..7c1bb28
--- /dev/null
+++ "b/atlTransformations/Ant2Maven/ExampleAnt2Maven\133v00.01\135.pdf"
Binary files differ
diff --git a/atlTransformations/AssertionModification/AssertionModification.pdf b/atlTransformations/AssertionModification/AssertionModification.pdf
new file mode 100644
index 0000000..092e850
--- /dev/null
+++ b/atlTransformations/AssertionModification/AssertionModification.pdf
Binary files differ
diff --git a/atlTransformations/AssertionModification/AssertionModification.zip b/atlTransformations/AssertionModification/AssertionModification.zip
new file mode 100644
index 0000000..70ba748
--- /dev/null
+++ b/atlTransformations/AssertionModification/AssertionModification.zip
Binary files differ
diff --git a/atlTransformations/BibTeXML2DocBook/BibTeXML2DocBook.zip b/atlTransformations/BibTeXML2DocBook/BibTeXML2DocBook.zip
new file mode 100644
index 0000000..a88de33
--- /dev/null
+++ b/atlTransformations/BibTeXML2DocBook/BibTeXML2DocBook.zip
Binary files differ
diff --git "a/atlTransformations/BibTeXML2DocBook/ExampleBibTeXML2DocBook\133v00.01\135.pdf" "b/atlTransformations/BibTeXML2DocBook/ExampleBibTeXML2DocBook\133v00.01\135.pdf"
new file mode 100644
index 0000000..eb193c8
--- /dev/null
+++ "b/atlTransformations/BibTeXML2DocBook/ExampleBibTeXML2DocBook\133v00.01\135.pdf"
Binary files differ
diff --git a/atlTransformations/Book2Publication/Book2Publication.zip b/atlTransformations/Book2Publication/Book2Publication.zip
new file mode 100644
index 0000000..516e383
--- /dev/null
+++ b/atlTransformations/Book2Publication/Book2Publication.zip
Binary files differ
diff --git a/atlTransformations/Book2Publication/ExampleBook2Publication.pdf b/atlTransformations/Book2Publication/ExampleBook2Publication.pdf
new file mode 100644
index 0000000..f9af9f4
--- /dev/null
+++ b/atlTransformations/Book2Publication/ExampleBook2Publication.pdf
Binary files differ
diff --git "a/atlTransformations/Book2Publication/ExampleBook2Publication\133v00.02\135.pdf" "b/atlTransformations/Book2Publication/ExampleBook2Publication\133v00.02\135.pdf"
new file mode 100644
index 0000000..f38b862
--- /dev/null
+++ "b/atlTransformations/Book2Publication/ExampleBook2Publication\133v00.02\135.pdf"
Binary files differ
diff --git a/atlTransformations/CPL2SPL/CPL2SPL.pdf b/atlTransformations/CPL2SPL/CPL2SPL.pdf
new file mode 100644
index 0000000..7a96862
--- /dev/null
+++ b/atlTransformations/CPL2SPL/CPL2SPL.pdf
Binary files differ
diff --git a/atlTransformations/CPL2SPL/CPL2SPL.zip b/atlTransformations/CPL2SPL/CPL2SPL.zip
new file mode 100644
index 0000000..6630eec
--- /dev/null
+++ b/atlTransformations/CPL2SPL/CPL2SPL.zip
Binary files differ
diff --git a/atlTransformations/CPL2SPL/README.txt b/atlTransformations/CPL2SPL/README.txt
new file mode 100644
index 0000000..f572b1c
--- /dev/null
+++ b/atlTransformations/CPL2SPL/README.txt
@@ -0,0 +1,54 @@
+This project contains a relatively complex example, which handles several aspects of two telephony DSLs: SPL and CPL.
+The complexity of this project shows that ATL can be used to handle such scenarios.
+
+The Doc/CPL2SPL.pdf document is a paper, which briefly presents CPL, SPL as well as motivation, challenges, and results of this experiment.
+
+Transformation files:
+ - CPL/XMLSyntax/XML2CPL.atl: ATL transformation that transforms an XML model into a CPL model.
+ - CPL/XMLSyntax/XMLHelpers.atl: ATL library of helpers used by XML2CPL.atl.
+ - CPL2SPL.atl: ATL transformation that transforms CPL models into SPL models.
+ - CPL2SPL.xml:
+ ant script that automatically applies the CPL2SPL transformation to all the examples provided in the Samples/ directory.
+ It also handles getting from XML document (*.cpl) to XML model, then to CPL model, and from SPL model to SPL program.
+ This is an example of batch execution of ATL transformations.
+ It can be executed by right-clicking on it, then clicking on "Run As->Ant Build".
+ It creates *.spl files in the Samples/ directory as well as *.ecore files in the DebuggingInformation/ directory.
+ These *.ecore files correspond to the intermediary steps of the transformation (i.e. XML model, CPL model, and SPL model).
+ They have the same base name as the original *.cpl file and the -<metamodel-name>Model.ecore suffix.
+ They are serialized for debugging purpose and to allow viewing these intermediary results.
+
+Metamodel files:
+ - AMMACore/XML.ecore: XML metamodel in EMF XMI 2.0 format.
+ This metamodel is part of standard metamodels used with ATL.
+ It is used when XML documents are tranformed into models.
+ - AMMACore/TCS.ecore: TCS metamodel in EMF XMI 2.0 format.
+ This metamodel is part of standard metamodels used with ATL.
+ It is used to represent textual syntaxes of metamodels.
+ This file is used here to transform SPL models into their equivalent textual representations (i.e. programs).
+ - CPL/CPL.km3: CPL metamodel in KM3 textual syntax.
+ - CPL/CPL.ecore: CPL metamodel in Ecore EMF XMI 2.0 format.
+ - SPL/SPL.km3: SPL metamodel in KM3 textual syntax.
+ - SPL/SPL.ecore: SPL metamodel in Ecore EMF XMI 2.0 format.
+
+Sample files:
+ - The Samples/ directory contains a set of *.cpl files.
+ These examples are CPL programs (therefore in XML) taken from the CPL specification (i.e. RFC3880).
+ They are transformed into *.spl programs with the same base name by the CPL2SPL.xml ant script.
+ - The StepByStep/ directory contains a set of files prepared for step-by-step execution of the CPL2SPL
+ transformation. We give here the actions to perform in order to get to the result
+ (all paths are relative to the StepByStep/ directory):
+ - transform AComplexExample.cpl.xml XML document into an XML model:
+ right-click on it and select "Inject XML file to XML model (Ecore based)".
+ Note that this action is only available from "AM3 Resource Navigator" view.
+ It can be activated by switching to AM3 perspective or going in menu
+ "Window->Show View->Other..." and then in "ATL".
+ This results in file AComplexExample.cpl-XML.ecore.
+ - transform XML model into CPL model: go to menu "Run->Run...",
+ then choose "XML2CPL" in the left pane and click on "Run" button on the bottom right.
+ This results in file AComplexExample.cpl-CPL.ecore.
+ - transform CPL model into SPL model: go to menu "Run->Run...",
+ then choose "CPL2SPL" in the left pane and click on "Run" button on the bottom right.
+ This results in file AComplexExample.cpl-SPL.ecore.
+ - transform SPL model into SPL program: right-click on "SPL2Text.xml",
+ then click on "Run As->Ant Build".
+ This results in file AComplexExample.cpl-SPL.spl.
diff --git a/atlTransformations/CatalogueModelTransformations/CatalogueModelTransformations.pdf b/atlTransformations/CatalogueModelTransformations/CatalogueModelTransformations.pdf
new file mode 100644
index 0000000..8d1ea89
--- /dev/null
+++ b/atlTransformations/CatalogueModelTransformations/CatalogueModelTransformations.pdf
Binary files differ
diff --git a/atlTransformations/CatalogueModelTransformations/CatalogueModelTransformations.zip b/atlTransformations/CatalogueModelTransformations/CatalogueModelTransformations.zip
new file mode 100644
index 0000000..8d60704
--- /dev/null
+++ b/atlTransformations/CatalogueModelTransformations/CatalogueModelTransformations.zip
Binary files differ
diff --git a/atlTransformations/Class2Relational/Class2Relational.zip b/atlTransformations/Class2Relational/Class2Relational.zip
new file mode 100644
index 0000000..e8f5528
--- /dev/null
+++ b/atlTransformations/Class2Relational/Class2Relational.zip
Binary files differ
diff --git a/atlTransformations/Class2Relational/ExampleClass2Relational.pdf b/atlTransformations/Class2Relational/ExampleClass2Relational.pdf
new file mode 100644
index 0000000..c4b6812
--- /dev/null
+++ b/atlTransformations/Class2Relational/ExampleClass2Relational.pdf
Binary files differ
diff --git "a/atlTransformations/Class2Relational/ExampleClass2Relational\133v00.01\135.pdf" "b/atlTransformations/Class2Relational/ExampleClass2Relational\133v00.01\135.pdf"
new file mode 100644
index 0000000..783f2c2
--- /dev/null
+++ "b/atlTransformations/Class2Relational/ExampleClass2Relational\133v00.01\135.pdf"
Binary files differ
diff --git a/atlTransformations/CodeCloneTools2SVG/CodeCloneTools2SVG.pdf b/atlTransformations/CodeCloneTools2SVG/CodeCloneTools2SVG.pdf
new file mode 100644
index 0000000..a9f6d93
--- /dev/null
+++ b/atlTransformations/CodeCloneTools2SVG/CodeCloneTools2SVG.pdf
Binary files differ
diff --git a/atlTransformations/CodeCloneTools2SVG/CodeCloneTools2SVG.ppt b/atlTransformations/CodeCloneTools2SVG/CodeCloneTools2SVG.ppt
new file mode 100644
index 0000000..0eda94c
--- /dev/null
+++ b/atlTransformations/CodeCloneTools2SVG/CodeCloneTools2SVG.ppt
Binary files differ
diff --git a/atlTransformations/CodeCloneTools2SVG/CodeCloneTools2SVG.xml b/atlTransformations/CodeCloneTools2SVG/CodeCloneTools2SVG.xml
new file mode 100644
index 0000000..7925a1c
--- /dev/null
+++ b/atlTransformations/CodeCloneTools2SVG/CodeCloneTools2SVG.xml
@@ -0,0 +1,14 @@
+<atlTransformation>
+ <shortName>CodeCloneTools2SVG</shortName>
+ <name>Code Clone Tools to SVG</name>
+ <docLink>CodeCloneTools2SVG.pdf</docLink>
+ <sourceLink>VisualRepCodeClone.zip</sourceLink>
+ <description>
+ This example describes a transformation from the text result generated by code clone detection tools
+ into SVG code in order to realize an uniform representation for different code clone analysis result.
+ At first, specific DSLs for different code clone tools (Simian, simScan, CloneDr) are defined. Then these
+ models can be transformed to a generic DSL for Code Clone. Then, the generic model will be transformed to
+ SVG model. Finally, SVG code can be extracted from the SVG model.
+ </description>
+ <pubDate></pubDate>
+</atlTransformation>
\ No newline at end of file
diff --git a/atlTransformations/CodeCloneTools2SVG/Readme.txt b/atlTransformations/CodeCloneTools2SVG/Readme.txt
new file mode 100644
index 0000000..f0781ec
--- /dev/null
+++ b/atlTransformations/CodeCloneTools2SVG/Readme.txt
@@ -0,0 +1,26 @@
+Readme
+
+
+Metamodels:
+ -- Simian.km3 Metamodel for Simian
+ -- SimScan.km3 Metamodel for SimScan
+ -- CloneDr.km3 Metamodel for CloneDr
+ -- FileInfo.km3 Metamodel for FileInfo
+ -- CodeClone.km3 Metamodel for Generic Code Clone DSL
+ -- SVG.km3 Metamodel for SVG
+ -- XML.km3 Metamodel for XML
+
+TCS Syntaxs:
+ -- Simian.tcs Syntax for Simian
+ -- SimScan.tcs Syntax for SimScan
+ -- CloneDr.tcs Syntax for CloneDr
+ -- FileInfo.tcs Syntax for FileInfo
+
+Transformations:
+ -- Simian2CodeClone.atl Transformation from the Simian model to generic Code Clone model
+ -- SimScan2CodeClone.atl Transformation from the SimScan model to generic Code Clone model
+ -- CloneDr2CodeClone.atl Transformation from the CloneDr model to generic Code Clone model
+ -- CodeClone2SVG.atl Transformation from the generic Code Clone model to SVG model in the first kind of visual representation
+ -- CodeClone2SVG2.atl Transformation from the generic Code Clone model to SVG model in the second kind of visual representation
+ -- SVG2XML.atl Transformation from SVG model to XML model
+
diff --git a/atlTransformations/CodeCloneTools2SVG/VisualRepCodeClone.zip b/atlTransformations/CodeCloneTools2SVG/VisualRepCodeClone.zip
new file mode 100644
index 0000000..97810c7
--- /dev/null
+++ b/atlTransformations/CodeCloneTools2SVG/VisualRepCodeClone.zip
Binary files differ
diff --git a/atlTransformations/DSL2EMF/DSLBridge.zip b/atlTransformations/DSL2EMF/DSLBridge.zip
new file mode 100644
index 0000000..670ce80
--- /dev/null
+++ b/atlTransformations/DSL2EMF/DSLBridge.zip
Binary files differ
diff --git "a/atlTransformations/DSL2EMF/ExampleDSL2EMF\133v00.01\135.pdf" "b/atlTransformations/DSL2EMF/ExampleDSL2EMF\133v00.01\135.pdf"
new file mode 100644
index 0000000..db1a63d
--- /dev/null
+++ "b/atlTransformations/DSL2EMF/ExampleDSL2EMF\133v00.01\135.pdf"
Binary files differ
diff --git a/atlTransformations/Disaggregation/Disaggregation.pdf b/atlTransformations/Disaggregation/Disaggregation.pdf
new file mode 100644
index 0000000..04badc7
--- /dev/null
+++ b/atlTransformations/Disaggregation/Disaggregation.pdf
Binary files differ
diff --git a/atlTransformations/Disaggregation/Disaggregation.zip b/atlTransformations/Disaggregation/Disaggregation.zip
new file mode 100644
index 0000000..b29de5e
--- /dev/null
+++ b/atlTransformations/Disaggregation/Disaggregation.zip
Binary files differ
diff --git a/atlTransformations/EMF2KM3/EMF2KM3.zip b/atlTransformations/EMF2KM3/EMF2KM3.zip
new file mode 100644
index 0000000..1e34ce0
--- /dev/null
+++ b/atlTransformations/EMF2KM3/EMF2KM3.zip
Binary files differ
diff --git a/atlTransformations/EMF2KM3/README.txt b/atlTransformations/EMF2KM3/README.txt
new file mode 100644
index 0000000..0b122ff
--- /dev/null
+++ b/atlTransformations/EMF2KM3/README.txt
@@ -0,0 +1,21 @@
+The KM3 plugin implements several transformations, including the generation of a KM3 model from an
+Ecore metamodel: EMF2KM3. This distribution provides source code for the EMF2KM3 transformation
+available in the KM3 plugin as of December 12th, 2005.
+
+EMF2KM3 is usually used through the KM3 plugin, as the "Extract Ecore metamodel to KM3" action available
+on *.ecore files. Some users may however want to customize this transformation.
+Here is the procedure to replace the standard transformation with a custom one:
+ * modify EMF2KM3.atl to support desired features,
+ * compile it into EMF2KM3.asm (this is normally automatically performed by the ATL builder),
+ * copy EMF2KM3.asm into org.atl.eclipse.km3 / src / org / atl / eclipse / km3 / resources,
+ * restart Eclipse.
+
+Files:
+ * README.txt: this small note.
+ * EMF2KM3.atl: an ATL transformation that transforms Ecore metamodels into KM3 models.
+ * Sample.ecore: a sample Ecore model that may be used as input for EMF2KM3.atl.
+ * Sample-KM3.ecore: a sample KM3 model that was obtained by applying EMF2KM3.atl to Sample.ecore.
+ * LaunchConfiguration.png: a screenshot showing how to configure a launch for EMF2KM3.atl. Note
+ that the KM3 metamodel is not loaded from an XMI file but referenced to by its xml namespace URI.
+ This mechanism ensures that the latest version of KM3 is always used. It however requires a version of
+ ADT more recent than December 12th, 2005.
diff --git a/atlTransformations/EliminateRedundantInheritance/EliminateRedundantInheritance.pdf b/atlTransformations/EliminateRedundantInheritance/EliminateRedundantInheritance.pdf
new file mode 100644
index 0000000..ca7ba35
--- /dev/null
+++ b/atlTransformations/EliminateRedundantInheritance/EliminateRedundantInheritance.pdf
Binary files differ
diff --git a/atlTransformations/EliminateRedundantInheritance/EliminateRedundantInheritance.zip b/atlTransformations/EliminateRedundantInheritance/EliminateRedundantInheritance.zip
new file mode 100644
index 0000000..9d349bb
--- /dev/null
+++ b/atlTransformations/EliminateRedundantInheritance/EliminateRedundantInheritance.zip
Binary files differ
diff --git a/atlTransformations/EquivalenceAttributesAssociations/EquivalenceAttributesAssociations.pdf b/atlTransformations/EquivalenceAttributesAssociations/EquivalenceAttributesAssociations.pdf
new file mode 100644
index 0000000..67c7324
--- /dev/null
+++ b/atlTransformations/EquivalenceAttributesAssociations/EquivalenceAttributesAssociations.pdf
Binary files differ
diff --git a/atlTransformations/EquivalenceAttributesAssociations/EquivalenceAttributesAssociations.zip b/atlTransformations/EquivalenceAttributesAssociations/EquivalenceAttributesAssociations.zip
new file mode 100644
index 0000000..1b0ec50
--- /dev/null
+++ b/atlTransformations/EquivalenceAttributesAssociations/EquivalenceAttributesAssociations.zip
Binary files differ
diff --git a/atlTransformations/Families2Persons/Families2Persons.zip b/atlTransformations/Families2Persons/Families2Persons.zip
new file mode 100644
index 0000000..9e3181b
--- /dev/null
+++ b/atlTransformations/Families2Persons/Families2Persons.zip
Binary files differ
diff --git "a/atlTransformations/GeometricalTransformations/ExampleGeometricalTransformations\133v00.02\135.pdf" "b/atlTransformations/GeometricalTransformations/ExampleGeometricalTransformations\133v00.02\135.pdf"
new file mode 100644
index 0000000..d172b3e
--- /dev/null
+++ "b/atlTransformations/GeometricalTransformations/ExampleGeometricalTransformations\133v00.02\135.pdf"
Binary files differ
diff --git a/atlTransformations/GeometricalTransformations/Geometry.zip b/atlTransformations/GeometricalTransformations/Geometry.zip
new file mode 100644
index 0000000..d2e4d8e
--- /dev/null
+++ b/atlTransformations/GeometricalTransformations/Geometry.zip
Binary files differ
diff --git "a/atlTransformations/Grafcet2PetriNet/ExampleGrafcet2PetriNet\133v00.01\135.pdf" "b/atlTransformations/Grafcet2PetriNet/ExampleGrafcet2PetriNet\133v00.01\135.pdf"
new file mode 100644
index 0000000..f6d17b9
--- /dev/null
+++ "b/atlTransformations/Grafcet2PetriNet/ExampleGrafcet2PetriNet\133v00.01\135.pdf"
Binary files differ
diff --git a/atlTransformations/Grafcet2PetriNet/Grafcet2PetriNet.zip b/atlTransformations/Grafcet2PetriNet/Grafcet2PetriNet.zip
new file mode 100644
index 0000000..64e3199
--- /dev/null
+++ b/atlTransformations/Grafcet2PetriNet/Grafcet2PetriNet.zip
Binary files differ
diff --git a/atlTransformations/IEEE1471_2_MoDAF/IEEE1471_2_MoDAF.doc b/atlTransformations/IEEE1471_2_MoDAF/IEEE1471_2_MoDAF.doc
new file mode 100644
index 0000000..3334658
--- /dev/null
+++ b/atlTransformations/IEEE1471_2_MoDAF/IEEE1471_2_MoDAF.doc
Binary files differ
diff --git a/atlTransformations/IEEE1471_2_MoDAF/IEEE1471_2_MoDAF.zip b/atlTransformations/IEEE1471_2_MoDAF/IEEE1471_2_MoDAF.zip
new file mode 100644
index 0000000..e1c61c1
--- /dev/null
+++ b/atlTransformations/IEEE1471_2_MoDAF/IEEE1471_2_MoDAF.zip
Binary files differ
diff --git a/atlTransformations/IntroducePrimaryKey/IntroducePrimaryKey.pdf b/atlTransformations/IntroducePrimaryKey/IntroducePrimaryKey.pdf
new file mode 100644
index 0000000..baa570f
--- /dev/null
+++ b/atlTransformations/IntroducePrimaryKey/IntroducePrimaryKey.pdf
Binary files differ
diff --git a/atlTransformations/IntroducePrimaryKey/IntroducePrimaryKey.zip b/atlTransformations/IntroducePrimaryKey/IntroducePrimaryKey.zip
new file mode 100644
index 0000000..601d34d
--- /dev/null
+++ b/atlTransformations/IntroducePrimaryKey/IntroducePrimaryKey.zip
Binary files differ
diff --git a/atlTransformations/IntroducingInterface/IntroducingInterface.pdf b/atlTransformations/IntroducingInterface/IntroducingInterface.pdf
new file mode 100644
index 0000000..fa5729c
--- /dev/null
+++ b/atlTransformations/IntroducingInterface/IntroducingInterface.pdf
Binary files differ
diff --git a/atlTransformations/IntroducingInterface/IntroducingInterface.zip b/atlTransformations/IntroducingInterface/IntroducingInterface.zip
new file mode 100644
index 0000000..339b690
--- /dev/null
+++ b/atlTransformations/IntroducingInterface/IntroducingInterface.zip
Binary files differ
diff --git "a/atlTransformations/Java2Table/ExampleJavaSource2Table\133v00.01\135.pdf" "b/atlTransformations/Java2Table/ExampleJavaSource2Table\133v00.01\135.pdf"
new file mode 100644
index 0000000..88834e5
--- /dev/null
+++ "b/atlTransformations/Java2Table/ExampleJavaSource2Table\133v00.01\135.pdf"
Binary files differ
diff --git a/atlTransformations/Java2Table/Java2Table.zip b/atlTransformations/Java2Table/Java2Table.zip
new file mode 100644
index 0000000..03f3bcf
--- /dev/null
+++ b/atlTransformations/Java2Table/Java2Table.zip
Binary files differ
diff --git a/atlTransformations/KM32ATLCopier/KM32ATLCopier.zip b/atlTransformations/KM32ATLCopier/KM32ATLCopier.zip
new file mode 100644
index 0000000..4576b3d
--- /dev/null
+++ b/atlTransformations/KM32ATLCopier/KM32ATLCopier.zip
Binary files differ
diff --git a/atlTransformations/KM32ATLCopier/README.txt b/atlTransformations/KM32ATLCopier/README.txt
new file mode 100644
index 0000000..b5f1ed2
--- /dev/null
+++ b/atlTransformations/KM32ATLCopier/README.txt
@@ -0,0 +1,16 @@
+The KM32ATLCopier transformation creates a transformation of copy for a KM3 model.
+
+This kind of transformation is a HOT (Higher Order Transformation): it takes a transformation as target.
+
+Source model conforms to KM3 metamodel and target model conforms to ATL metamodel.
+A sample source model (sample-KM3.ecore) and its corresponding target model (ATLCopier.ecore) are given.
+
+File configuration.PNG shows how to configure the transformation for launch.
+It is now possible to use the "Metamodel by URI" button to use a metamodel already registered in EMF.
+We advise you to use this new feature to configure this transformation because ATL metamodel is already registered in EMF by ADT plugins.
+Thanks to that, the latest version of ATL metamodel will always be used.
+
+To serialize the generated ATL transformation you can use ATL extractor available in AM3 project (http://dev.eclipse.org/viewcvs/indextech.cgi/~checkout~/gmt-home/subprojects/AM3/index.html).
+You can create easily input models thanks to ATL injector (also available in AM3 project).
+
+If you have some problems, please use ATL mailing list (http://groups.yahoo.com/group/atl_discussion/).
diff --git "a/atlTransformations/KM32DOT/ExampleKM32DOT\133v00.01\135.pdf" "b/atlTransformations/KM32DOT/ExampleKM32DOT\133v00.01\135.pdf"
new file mode 100644
index 0000000..7e432d7
--- /dev/null
+++ "b/atlTransformations/KM32DOT/ExampleKM32DOT\133v00.01\135.pdf"
Binary files differ
diff --git a/atlTransformations/KM32DOT/KM32DOT.zip b/atlTransformations/KM32DOT/KM32DOT.zip
new file mode 100644
index 0000000..e062bf5
--- /dev/null
+++ b/atlTransformations/KM32DOT/KM32DOT.zip
Binary files differ
diff --git a/atlTransformations/KM32EMF/KM32EMF.zip b/atlTransformations/KM32EMF/KM32EMF.zip
new file mode 100644
index 0000000..82db5b7
--- /dev/null
+++ b/atlTransformations/KM32EMF/KM32EMF.zip
Binary files differ
diff --git a/atlTransformations/KM32EMF/README.txt b/atlTransformations/KM32EMF/README.txt
new file mode 100644
index 0000000..8603f1e
--- /dev/null
+++ b/atlTransformations/KM32EMF/README.txt
@@ -0,0 +1,30 @@
+The KM3 plugin implements several transformations, including the generation of an Ecore metamodel
+from a KM3 model: KM32EMF.
+This distribution provides source code for the KM32EMF transformation
+available in the KM3 plugin as of May 24th, 2006.
+
+KM32EMF is usually used through the KM3 plugin, as the "Inject KM3 to Ecore metamodel" action available
+on *.km3 files. Some users may however want to customize this transformation.
+Here is the procedure to replace the standard transformation with a custom one:
+ * modify KM32EMF.atl to support desired features,
+ * compile it into KM32EMF.asm (this is normally automatically performed by the ATL builder),
+ * copy KM32EMF.asm into org.atl.eclipse.km3 / src / org / atl / eclipse / km3 / resources,
+ * restart Eclipse.
+
+Files:
+ * README.txt: this small note.
+ * KM32EMF.atl: an ATL transformation that transforms KM3 models into Ecore metamodels.
+ * Sample-KM3.ecore: a sample KM3 model that may be used as input for KM32EMF.atl.
+ * Sample.ecore: a sample Ecore metamodel that was obtained by applying KM32EMF.atl to Sample-KM3.ecore.
+ * KM32EMF.launch: the launch configuration for running KM32EMF.atl on Sample-KM3.ecore to obtain
+ Sample.ecore. Note that the KM3 metamodel is not loaded from an XMI file but referenced to by its XML namespace URI.
+ This mechanism ensures that the latest version of KM3 is always used. It however requires a version of
+ ADT more recent than May 24th, 2006.
+
+
+Remarks:
+
+This transformation illustrates how various metadata may be specified as KM3 comments and translated
+into EMF-specific constructs. The getMetadata(name : String) helper is used to get the value of nsURI
+and nsPrefix from KM3 comments. The values returned by the helper are then used to initialize the
+corresponding EMF properties of EPackage.
diff --git "a/atlTransformations/KM32Measure/ExampleKM32Measure\133v00.01\135.pdf" "b/atlTransformations/KM32Measure/ExampleKM32Measure\133v00.01\135.pdf"
new file mode 100644
index 0000000..3fcfe60
--- /dev/null
+++ "b/atlTransformations/KM32Measure/ExampleKM32Measure\133v00.01\135.pdf"
Binary files differ
diff --git "a/atlTransformations/KM32Measure/ExampleKM32Measure\133v00.02\135.pdf" "b/atlTransformations/KM32Measure/ExampleKM32Measure\133v00.02\135.pdf"
new file mode 100644
index 0000000..f67e321
--- /dev/null
+++ "b/atlTransformations/KM32Measure/ExampleKM32Measure\133v00.02\135.pdf"
Binary files differ
diff --git a/atlTransformations/KM32Measure/KM32Measure.zip b/atlTransformations/KM32Measure/KM32Measure.zip
new file mode 100644
index 0000000..a1acb1e
--- /dev/null
+++ b/atlTransformations/KM32Measure/KM32Measure.zip
Binary files differ
diff --git "a/atlTransformations/KM32Metrics/ExampleKM32Metrics\133v00.01\135.pdf" "b/atlTransformations/KM32Metrics/ExampleKM32Metrics\133v00.01\135.pdf"
new file mode 100644
index 0000000..c95e01a
--- /dev/null
+++ "b/atlTransformations/KM32Metrics/ExampleKM32Metrics\133v00.01\135.pdf"
Binary files differ
diff --git a/atlTransformations/KM32Metrics/KM32Metrics.zip b/atlTransformations/KM32Metrics/KM32Metrics.zip
new file mode 100644
index 0000000..2c1b13b
--- /dev/null
+++ b/atlTransformations/KM32Metrics/KM32Metrics.zip
Binary files differ
diff --git a/atlTransformations/KM32OWL/KM32OWL.zip b/atlTransformations/KM32OWL/KM32OWL.zip
new file mode 100644
index 0000000..60ff805
--- /dev/null
+++ b/atlTransformations/KM32OWL/KM32OWL.zip
Binary files differ
diff --git a/atlTransformations/KM32OWL/README.txt b/atlTransformations/KM32OWL/README.txt
new file mode 100644
index 0000000..28dea6d
--- /dev/null
+++ b/atlTransformations/KM32OWL/README.txt
@@ -0,0 +1,35 @@
+This ATL scenario shows up a traduction of KM3 into OWL (Web Ontology language) ontology language. This scenario is composed
+of one transformation (KM32OWL) and an OWL extractor that produces XML documents conform to the OWL syntax
+defined by the W3C. Resulting ontology can be used into ontology development tools like Protégé
+(see http://protege.stanford.edu).
+
+See also:
+ -- UML2OWL scenario http://www.eclipse.org/atl/usecases/ODMImplementation/
+ -- OWL (Web Ontology language) http://www.w3.org/2004/OWL/
+
+Transformation files:
+ - KM32OWL.atl: The core transformation of the scenario. It is the implementation in ATL of
+ the QVT mapping UML2OWL from ODM specification. It produces an OWL Model from a UML 2.0 Model.
+ - OWL2XML.atl: ATL transformation that transforms an OWL Model into
+ an XML models with OWL/XML syntax elements.
+ - build.xml: An ANT script that automatically executes the 2 ATL transformations and
+ the XML extractor to produce from a uml model an owl document that contains the ontology.
+ It can be executed by right-clicking on it, then clicking on "Run As->Ant Build". To execute
+ this transformation on other km3 examples, place your km3 models in the Samples folder and make
+ necessary changes in ANT script.
+
+Metamodel files:
+ - XML.ecore: XML metamodel in EMF XMI 2.0 format.
+ This metamodel is part of standard metamodels used with ATL.
+ It is used when models are tranformed into XML documents or vice versa.
+ - OWL.km3: OWL Metamodel in km3 textual syntax. This Metamodel has been designed
+ by following the ODM specification.
+ - OWL.ecore: OWL Metamodel in Ecore EMF XMI 2.0 format.
+
+Sample files:
+ - Samples/Museum.km3: This metamodel represents is an excerpt of a Museum metamodel and is used as input
+ example by this transformation scenario.
+
+ - Samples/Museum.owl: This file is the Museum ontology in OWL/XML format after executing the OWL2XML
+ transformation and the XML extractor. This file can be used in an ontology editor like Protégé.
+
\ No newline at end of file
diff --git "a/atlTransformations/KM32Problem/ExampleKM32Problem\133v00.01\135.pdf" "b/atlTransformations/KM32Problem/ExampleKM32Problem\133v00.01\135.pdf"
new file mode 100644
index 0000000..512ddf9
--- /dev/null
+++ "b/atlTransformations/KM32Problem/ExampleKM32Problem\133v00.01\135.pdf"
Binary files differ
diff --git a/atlTransformations/KM32Problem/KM32Problem.zip b/atlTransformations/KM32Problem/KM32Problem.zip
new file mode 100644
index 0000000..7803d00
--- /dev/null
+++ b/atlTransformations/KM32Problem/KM32Problem.zip
Binary files differ
diff --git a/atlTransformations/KM32XML/KM32XML.zip b/atlTransformations/KM32XML/KM32XML.zip
new file mode 100644
index 0000000..bc6bbad
--- /dev/null
+++ b/atlTransformations/KM32XML/KM32XML.zip
Binary files differ
diff --git a/atlTransformations/KM32XML/readme.txt b/atlTransformations/KM32XML/readme.txt
new file mode 100644
index 0000000..bcb1784
--- /dev/null
+++ b/atlTransformations/KM32XML/readme.txt
@@ -0,0 +1,20 @@
+Metamodel file
+---------------
+ * XML.ecore
+
+Example files
+-------------
+ * JavaAbstractSyntax.km3: KM3 sample file
+ * JavaAbstractSyntax.xml: XML file created from the sample KM3 file
+
+Transformation files
+--------------------
+ * KM32XML.atl
+ * LibFAQL.atl
+
+The KM32XML transformation ("KM32XML.atl") can be tested with the KM3 file ("JavaAbstractSyntax.km3") as input.
+It returns an XML file ("JavaAbstractSyntax.xml").
+
+Launch Configuration
+--------------------
+build.xml: Ant Script to execute this scenario
\ No newline at end of file
diff --git "a/atlTransformations/KMLInjector/ExampleKMLInjector\133v00.01\135.pdf" "b/atlTransformations/KMLInjector/ExampleKMLInjector\133v00.01\135.pdf"
new file mode 100644
index 0000000..f59ecf7
--- /dev/null
+++ "b/atlTransformations/KMLInjector/ExampleKMLInjector\133v00.01\135.pdf"
Binary files differ
diff --git a/atlTransformations/KMLInjector/KMLInjector.zip b/atlTransformations/KMLInjector/KMLInjector.zip
new file mode 100644
index 0000000..1013276
--- /dev/null
+++ b/atlTransformations/KMLInjector/KMLInjector.zip
Binary files differ
diff --git a/atlTransformations/ListMetamodelRefactoring/ListMetamodelRefactoring.zip b/atlTransformations/ListMetamodelRefactoring/ListMetamodelRefactoring.zip
new file mode 100644
index 0000000..99bc483
--- /dev/null
+++ b/atlTransformations/ListMetamodelRefactoring/ListMetamodelRefactoring.zip
Binary files differ
diff --git a/atlTransformations/MDL2GMF/org.eclipse.m2m.atl.mdl2gmf.zip b/atlTransformations/MDL2GMF/org.eclipse.m2m.atl.mdl2gmf.zip
new file mode 100644
index 0000000..0017323
--- /dev/null
+++ b/atlTransformations/MDL2GMF/org.eclipse.m2m.atl.mdl2gmf.zip
Binary files differ
diff --git a/atlTransformations/METAH2ACME/METAH2ACME.pdf b/atlTransformations/METAH2ACME/METAH2ACME.pdf
new file mode 100644
index 0000000..1b20f3a
--- /dev/null
+++ b/atlTransformations/METAH2ACME/METAH2ACME.pdf
Binary files differ
diff --git a/atlTransformations/METAH2ACME/METAH2ACME.zip b/atlTransformations/METAH2ACME/METAH2ACME.zip
new file mode 100644
index 0000000..b9f4867
--- /dev/null
+++ b/atlTransformations/METAH2ACME/METAH2ACME.zip
Binary files differ
diff --git "a/atlTransformations/MOF2UML/ExampleMOF2UML\133v00.01\135.pdf" "b/atlTransformations/MOF2UML/ExampleMOF2UML\133v00.01\135.pdf"
new file mode 100644
index 0000000..c473f7e
--- /dev/null
+++ "b/atlTransformations/MOF2UML/ExampleMOF2UML\133v00.01\135.pdf"
Binary files differ
diff --git a/atlTransformations/MOF2UML/UML2MOF.zip b/atlTransformations/MOF2UML/UML2MOF.zip
new file mode 100644
index 0000000..4cc5f95
--- /dev/null
+++ b/atlTransformations/MOF2UML/UML2MOF.zip
Binary files differ
diff --git "a/atlTransformations/MSOfficeExcel2SoftwareQualityControl/ExampleMicrosoftOfficeExcel2SoftwareQualityControl\133v00.01\135.pdf" "b/atlTransformations/MSOfficeExcel2SoftwareQualityControl/ExampleMicrosoftOfficeExcel2SoftwareQualityControl\133v00.01\135.pdf"
new file mode 100644
index 0000000..99e2607
--- /dev/null
+++ "b/atlTransformations/MSOfficeExcel2SoftwareQualityControl/ExampleMicrosoftOfficeExcel2SoftwareQualityControl\133v00.01\135.pdf"
Binary files differ
diff --git a/atlTransformations/MSOfficeExcel2SoftwareQualityControl/MicrosoftOfficeExcel2SoftwareQualityControl.zip b/atlTransformations/MSOfficeExcel2SoftwareQualityControl/MicrosoftOfficeExcel2SoftwareQualityControl.zip
new file mode 100644
index 0000000..20a2255
--- /dev/null
+++ b/atlTransformations/MSOfficeExcel2SoftwareQualityControl/MicrosoftOfficeExcel2SoftwareQualityControl.zip
Binary files differ
diff --git "a/atlTransformations/MSOfficeExcelExtractor/ExampleMicrosoftOfficeExcelExtractor\133v00.01\135.pdf" "b/atlTransformations/MSOfficeExcelExtractor/ExampleMicrosoftOfficeExcelExtractor\133v00.01\135.pdf"
new file mode 100644
index 0000000..3db9746
--- /dev/null
+++ "b/atlTransformations/MSOfficeExcelExtractor/ExampleMicrosoftOfficeExcelExtractor\133v00.01\135.pdf"
Binary files differ
diff --git a/atlTransformations/MSOfficeExcelExtractor/MicrosoftOfficeExcelExtractor.zip b/atlTransformations/MSOfficeExcelExtractor/MicrosoftOfficeExcelExtractor.zip
new file mode 100644
index 0000000..8eab357
--- /dev/null
+++ b/atlTransformations/MSOfficeExcelExtractor/MicrosoftOfficeExcelExtractor.zip
Binary files differ
diff --git "a/atlTransformations/MSOfficeExcelInjector/ExampleMicrosoftOfficeExcelInjector\133v00.01\135.pdf" "b/atlTransformations/MSOfficeExcelInjector/ExampleMicrosoftOfficeExcelInjector\133v00.01\135.pdf"
new file mode 100644
index 0000000..a6443f5
--- /dev/null
+++ "b/atlTransformations/MSOfficeExcelInjector/ExampleMicrosoftOfficeExcelInjector\133v00.01\135.pdf"
Binary files differ
diff --git a/atlTransformations/MSOfficeExcelInjector/MicrosoftOfficeExcelInjector.zip b/atlTransformations/MSOfficeExcelInjector/MicrosoftOfficeExcelInjector.zip
new file mode 100644
index 0000000..23e01b7
--- /dev/null
+++ b/atlTransformations/MSOfficeExcelInjector/MicrosoftOfficeExcelInjector.zip
Binary files differ
diff --git "a/atlTransformations/Make2Ant/ExampleMake2Ant\133v00.01\135.pdf" "b/atlTransformations/Make2Ant/ExampleMake2Ant\133v00.01\135.pdf"
new file mode 100644
index 0000000..a5eceb1
--- /dev/null
+++ "b/atlTransformations/Make2Ant/ExampleMake2Ant\133v00.01\135.pdf"
Binary files differ
diff --git a/atlTransformations/Make2Ant/Make2Ant.zip b/atlTransformations/Make2Ant/Make2Ant.zip
new file mode 100644
index 0000000..ce52dcc
--- /dev/null
+++ b/atlTransformations/Make2Ant/Make2Ant.zip
Binary files differ
diff --git a/atlTransformations/MakePartialRoleTotal/MakePartialRoleTotal.zip b/atlTransformations/MakePartialRoleTotal/MakePartialRoleTotal.zip
new file mode 100644
index 0000000..6aaf236
--- /dev/null
+++ b/atlTransformations/MakePartialRoleTotal/MakePartialRoleTotal.zip
Binary files differ
diff --git "a/atlTransformations/MakePartialRoleTotal/MakingPartialRoleTotal\050a\051.pdf" "b/atlTransformations/MakePartialRoleTotal/MakingPartialRoleTotal\050a\051.pdf"
new file mode 100644
index 0000000..f10cb2b
--- /dev/null
+++ "b/atlTransformations/MakePartialRoleTotal/MakingPartialRoleTotal\050a\051.pdf"
Binary files differ
diff --git "a/atlTransformations/MakePartialRoleTotal/MakingPartialRoleTotal\050b\051.pdf" "b/atlTransformations/MakePartialRoleTotal/MakingPartialRoleTotal\050b\051.pdf"
new file mode 100644
index 0000000..7705fc7
--- /dev/null
+++ "b/atlTransformations/MakePartialRoleTotal/MakingPartialRoleTotal\050b\051.pdf"
Binary files differ
diff --git "a/atlTransformations/Maven2Ant/ExampleMaven2Ant\133v00.01\135.pdf" "b/atlTransformations/Maven2Ant/ExampleMaven2Ant\133v00.01\135.pdf"
new file mode 100644
index 0000000..c6d3b3b
--- /dev/null
+++ "b/atlTransformations/Maven2Ant/ExampleMaven2Ant\133v00.01\135.pdf"
Binary files differ
diff --git a/atlTransformations/Maven2Ant/Maven2Ant.zip b/atlTransformations/Maven2Ant/Maven2Ant.zip
new file mode 100644
index 0000000..9e5b7b0
--- /dev/null
+++ b/atlTransformations/Maven2Ant/Maven2Ant.zip
Binary files differ
diff --git "a/atlTransformations/Measure2Table/ExampleMeasure2Table\133v00.01\135.pdf" "b/atlTransformations/Measure2Table/ExampleMeasure2Table\133v00.01\135.pdf"
new file mode 100644
index 0000000..4c3ab39
--- /dev/null
+++ "b/atlTransformations/Measure2Table/ExampleMeasure2Table\133v00.01\135.pdf"
Binary files differ
diff --git a/atlTransformations/Measure2Table/Measure2Table.zip b/atlTransformations/Measure2Table/Measure2Table.zip
new file mode 100644
index 0000000..db47bfa
--- /dev/null
+++ b/atlTransformations/Measure2Table/Measure2Table.zip
Binary files differ
diff --git a/atlTransformations/Measure2Table/README.txt b/atlTransformations/Measure2Table/README.txt
new file mode 100644
index 0000000..6f1b92f
--- /dev/null
+++ b/atlTransformations/Measure2Table/README.txt
@@ -0,0 +1,50 @@
+--------------------------------------------------------------------------------
+For questions and/or comments:
+
+ Eric Vepa (evepa <at> sodius.com)
+
+ SODIUS (www.sodius.com)
+ 6, rue de la Cornouaille - BP 91941
+ 44319 Nantes, France
+--------------------------------------------------------------------------------
+
+The Measure2Table project is used to creates generic tables from a measure
+ model.
+
+Contents:
+ --> "Measure2Table": The ATL project folder.
+
+ |--> "InputModels": The folder which contains the input example in Ecore
+ format.
+ \--> "example-Measure.ecore": An example of input.
+
+ |--> "Metamodels": The folder which contains the metamodels in KM3 and
+ Ecore format.
+ \--> "Measure.{km3,ecore}": The Measure metamodel.
+ \--> "Table.{km3,ecore}": The Table metamodel.
+
+ |--> "OutputModels": The folder which contains the generated models. This
+ folder is generated by the ANT script so you can delete it before building.
+ \--> "example-Table.uml": An example of output.
+
+ |--> "Transformations": The folder which contains the transformations in
+ ATL and ASM format.
+ \--> "Measure2Table.{atl,asm}": The Measure2Table transformation.
+
+ |--> "build.xml": The ANT script of the project for launching the
+ transformation.
+
+ |--> "Measure2Table build.xml.launch": The configuration file of the ANT
+ script "build.xml".
+
+ |--> "epl-v10.html": This project is under the Eclipse Public License.
+
+ |--> "README.txt": This file.
+
+HowTo:
+ --> Open the AM3 Perspective.
+ --> Run the "build.xml" (the launch file is already configured):
+ Right click on "build.xml" file --> Run As --> Ant Build.
+ --> The generated output model is in the "OutputModels" folder.
+
+
\ No newline at end of file
diff --git "a/atlTransformations/Measure2XHTML/ExampleMeasure2XHTML\133v00.01\135.pdf" "b/atlTransformations/Measure2XHTML/ExampleMeasure2XHTML\133v00.01\135.pdf"
new file mode 100644
index 0000000..d40546a
--- /dev/null
+++ "b/atlTransformations/Measure2XHTML/ExampleMeasure2XHTML\133v00.01\135.pdf"
Binary files differ
diff --git a/atlTransformations/Measure2XHTML/Measure2XHTML.zip b/atlTransformations/Measure2XHTML/Measure2XHTML.zip
new file mode 100644
index 0000000..251cdad
--- /dev/null
+++ b/atlTransformations/Measure2XHTML/Measure2XHTML.zip
Binary files differ
diff --git "a/atlTransformations/MeasuringModelRepositories/ExampleMeasuringModelRepositories\133v00.01\135.pdf" "b/atlTransformations/MeasuringModelRepositories/ExampleMeasuringModelRepositories\133v00.01\135.pdf"
new file mode 100644
index 0000000..3dc63fa
--- /dev/null
+++ "b/atlTransformations/MeasuringModelRepositories/ExampleMeasuringModelRepositories\133v00.01\135.pdf"
Binary files differ
diff --git a/atlTransformations/MeasuringModelRepositories/MeasuringModelRepositories.zip b/atlTransformations/MeasuringModelRepositories/MeasuringModelRepositories.zip
new file mode 100644
index 0000000..d767d1b
--- /dev/null
+++ b/atlTransformations/MeasuringModelRepositories/MeasuringModelRepositories.zip
Binary files differ
diff --git a/atlTransformations/MergingPartialClasses/MergingPartialClasses.pdf b/atlTransformations/MergingPartialClasses/MergingPartialClasses.pdf
new file mode 100644
index 0000000..428a00b
--- /dev/null
+++ b/atlTransformations/MergingPartialClasses/MergingPartialClasses.pdf
Binary files differ
diff --git a/atlTransformations/MergingPartialClasses/MergingPartialClasses.zip b/atlTransformations/MergingPartialClasses/MergingPartialClasses.zip
new file mode 100644
index 0000000..5349660
--- /dev/null
+++ b/atlTransformations/MergingPartialClasses/MergingPartialClasses.zip
Binary files differ
diff --git a/atlTransformations/ModelMeasurement/ModelsMeasurement.zip b/atlTransformations/ModelMeasurement/ModelsMeasurement.zip
new file mode 100644
index 0000000..2a0249a
--- /dev/null
+++ b/atlTransformations/ModelMeasurement/ModelsMeasurement.zip
Binary files differ
diff --git a/atlTransformations/ModelMeasurement/README.txt b/atlTransformations/ModelMeasurement/README.txt
new file mode 100644
index 0000000..ba47055
--- /dev/null
+++ b/atlTransformations/ModelMeasurement/README.txt
@@ -0,0 +1,100 @@
+--------------------------------------------------------------------------------
+For questions and/or comments:
+
+ Eric Vepa (evepa <at> sodius.com)
+
+ SODIUS (www.sodius.com)
+ 6, rue de la Cornouaille - BP 91941
+ 44319 Nantes, France
+--------------------------------------------------------------------------------
+
+The ModelsMeasurement project is used to collect measurement data on KM3
+ metamodels or UML2 models, using libraries implementing some metrics
+ (MOOD, MOOD2, MOOSE, EMOOSE and QMOOD).
+ The measure level can be changed by setting an other value for the first helper
+ measureLevel of the transformation KM32Measure or UML22Measure.
+
+Required:
+ - UML2 Eclipse plugin (the UML2 metamodel is needed by URI)
+ - Jar2UML Eclipse plugin (for more examples from Jar files)
+
+Contents:
+ --> "ModelsMeasurement": The ATL project folder.
+
+ |--> "InputModels": The folder which contains the input example in .uml
+ format and the injected model in Ecore format.
+ \--> "example.km3": The WordprocessingMLSimplified metamodel is an
+ example of input.
+ \--> "example.uml": An example of input model imported from
+ org.eclipse.core.runtime.jar with Jar2UML plug-in.
+
+ |--> "Libraries": The folder which contains the libraries, used by the
+ transformations, in ATL and ASM format.
+ \--> "EMOOSE4KM3.{atl,asm}": The EMOOSE4KM3 library.
+ \--> "EMOOSE4UML2.{atl,asm}": The EMOOSE4UML2 library.
+ \--> "FLAME4KM3.{atl,asm}": The FLAME4KM3 library.
+ \--> "FLAME4UML2.{atl,asm}": The FLAME4UML2 library.
+ \--> "MOOD4KM3.{atl,asm}": The MOOD4KM3 library.
+ \--> "MOOD4UML2.{atl,asm}": The MOOD4UML2 library.
+ \--> "QMOOD4KM3.{atl,asm}": The QMOOD4KM3 library.
+ \--> "QMOOD4UML2.{atl,asm}": The QMOOD4UML2 library.
+ \--> "TableHelpers.{atl,asm}": The TableHelpers library.
+
+ |--> "Metamodels": The folder which contains the metamodels in KM3 and
+ Ecore format.
+ \--> "HTML.{km3,ecore}": The HTML metamodel.
+ \--> "Measure.{km3,ecore}": The Measure metamodel.
+ \--> "SVG.{km3,ecore}": The SVG metamodel.
+ \--> "Table.{km3,ecore}": The Table metamodel.
+ \--> "XML.{km3,ecore}": The XML metamodel.
+
+ |--> "OutputModels": The folder which contains the generated models in
+ Ecore format. This folder is generated by the ANT script so you can delete it
+ before building.
+ \--> "example-Measure.ecore": A temporary model of measure.
+ \--> "example-SVGBarChart4KM3.ecore": The model generated for the
+ example.km3 and for SVG bar chart presentation.
+ \--> "example-SVGBarChart4UML2.ecore": The model generated for the
+ example.uml and for SVG bar chart presentation.
+ \--> "example-SVGPieChart4KM3.ecore": The model generated for the
+ example.km3 and for SVG pie chart presentation.
+ \--> "example-SVGPieChart4UML2.ecore": The model generated for the
+ example.uml and for SVG pie chart presentation.
+ \--> "example-TabularHTML4KM3.ecore": The model generated for the
+ example.km3 and for HTML presentation.
+ \--> "example-TabularHTML4UML2.ecore": The model generated for the
+ example.uml and for HTML presentation.
+
+ |--> "Transformations": The folder which contains the transformations in
+ ATL and ASM format.
+ \--> "HTML2XML.{atl,asm}": The HTML2XML transformation.
+ \--> "KM32Measure.{atl,asm}": The KM32Measure transformation.
+ \--> "Measure2Table.{atl,asm}": The Measure2Table transformation.
+ \--> "SVG2XML.{atl,asm}": The SVG2XML transformation.
+ \--> "Table2SVGBarChart.{atl,asm}": The Table2SVGBarChart transformation.
+ \--> "Table2SVGPieChart.{atl,asm}": The Table2SVGPieChart transformation.
+ \--> "Table2TabularHTML.{atl,asm}": The Table2TabularHTML transformation.
+ \--> "UML22Measure.{atl,asm}": The UML22Measure transformation.
+
+ |--> "ant-contrib.jar": Additional ANT tasks. This jar should be downloaded from here: http://ant-contrib.sourceforge.net/
+
+ |--> "build.xml": The ANT script of the project for launching the
+ transformation.
+
+ |--> "epl-v10.html": This project is under the Eclipse Public License.
+
+ |--> "ModelsMeasurement build.xml.launch": The configuration file of the
+ ANT script "build.xml".
+
+ |--> "README.txt": This file.
+
+HowTo:
+ --> Open the AM3 Perspective.
+ --> In the build.xml:
+ --> Choose an input terminal model to measure among {KM3,UML2}
+ --> Choose an output presentation format among {HTML,SVG}
+ --> If SVG is choosen, choose a kind of chart among {Bar,Pie}
+ --> Run the "build.xml" (the launch file is already configured):
+ Right click on "build.xml" file --> Run As --> Ant Build.
+ --> The generated output model is in the "OutputModels" folder.
+
\ No newline at end of file
diff --git "a/atlTransformations/Monitor2Semaphore/ExampleMonitor2Semaphore\133v00.01\135.pdf" "b/atlTransformations/Monitor2Semaphore/ExampleMonitor2Semaphore\133v00.01\135.pdf"
new file mode 100644
index 0000000..715c7c1
--- /dev/null
+++ "b/atlTransformations/Monitor2Semaphore/ExampleMonitor2Semaphore\133v00.01\135.pdf"
Binary files differ
diff --git a/atlTransformations/Monitor2Semaphore/Monitor2Semaphore.zip b/atlTransformations/Monitor2Semaphore/Monitor2Semaphore.zip
new file mode 100644
index 0000000..c34bfd3
--- /dev/null
+++ b/atlTransformations/Monitor2Semaphore/Monitor2Semaphore.zip
Binary files differ
diff --git "a/atlTransformations/MySQL2KM3/ExampleMySQL2KM3\133v00.01\135.pdf" "b/atlTransformations/MySQL2KM3/ExampleMySQL2KM3\133v00.01\135.pdf"
new file mode 100644
index 0000000..f032a62
--- /dev/null
+++ "b/atlTransformations/MySQL2KM3/ExampleMySQL2KM3\133v00.01\135.pdf"
Binary files differ
diff --git a/atlTransformations/MySQL2KM3/MySQL2KM3.zip b/atlTransformations/MySQL2KM3/MySQL2KM3.zip
new file mode 100644
index 0000000..102bbef
--- /dev/null
+++ b/atlTransformations/MySQL2KM3/MySQL2KM3.zip
Binary files differ
diff --git a/atlTransformations/OCL2R2ML/OCL2R2ML.zip b/atlTransformations/OCL2R2ML/OCL2R2ML.zip
new file mode 100644
index 0000000..01cb91a
--- /dev/null
+++ b/atlTransformations/OCL2R2ML/OCL2R2ML.zip
Binary files differ
diff --git a/atlTransformations/OCL2R2ML/README.txt b/atlTransformations/OCL2R2ML/README.txt
new file mode 100644
index 0000000..5b7db4c
--- /dev/null
+++ b/atlTransformations/OCL2R2ML/README.txt
@@ -0,0 +1,60 @@
+*********************************************************
+** Description: OCL2R2ML ATL transformation scenario
+** Author: Milan Milanovic <milan at milanovic.org>
+** Date: October 10, 2006
+********************************************************
+
+This ATL scenario transforms OCL (Object Constraint Language) into R2ML (REWERSE I1 Markup Language).
+It is composed of OCL EBNF injector (to OCL metamodel), transformations (OCL2R2ML) and an R2ML extractor
+that produces XML documents that conform to the R2ML syntax defined by REWERSE I1 group. To find more
+details about this transformation scenario, please refer to [1]-[2].
+
+See also:
+ -- R2ML2OCL transformations scenario
+ -- R2ML (REWERSE I1 Rule Markup Language) - http://oxygen.informatik.tu-cottbus.de/rewerse-i1/?q=node/6
+ -- Object Constraint Language - OMG Available Specification, Version 2.0, formal/06-05-01.
+ [Online] http://www.omg.org/cgi-bin/doc?formal/06-05-01
+
+Transformation files:
+---------------------
+ - R2ML2XML.atl: ATL transformation that transforms an R2ML model into an
+ an XML models with R2ML syntax elements.
+
+ - OCL2R2ML.atl: The core transformation, that produced an R2ML model from
+ a OCLmodel (instance of OCLmetamodel).
+
+ - OCL2R2ML.xml: An ANT script that automatically executes the 2 ATL transformations,
+ EBNF injector to produce OCL model from OCL file, and a XML extractor
+ to produce R2ML XML documents from R2ML model. It can be
+ executed by right-clicking on it, then clicking on "Run As->Ant Build".
+ To execute this transformation on other SWRL examples, place your OCL invariant files
+ in the models/ocl folder and make necessary changes in ANT script.
+
+Metamodel files:
+----------------
+ - XML.xmi: XML metamodel in MOF XMI 1.2 format (MOF-1.4). This metamodel is part of standard metamodels
+ used with ATL. It is used when models are tranformed into XML documents or vice versa.
+
+ - OCL.xmi: OCL metamodel in MOF XMI 1.2 format (MOF-1.4). This model represents an abstract syntax for
+ the OCL language.
+
+ - R2ML.xmi: R2ML metamodel in MOF XMI 1.2 format (MOF-1.4). Metamodel of the R2ML language.
+
+ - Every metamodel have KM3 and Ecore EMF XMI 2.0 format versions.
+
+Sample files:
+-------------
+ - Models/ocl/m1.ocl: This file is simple OCL invariant and is used as input example by
+ this transformation scenario.
+
+ - Models/r2ml-xml/R2MLRule.xml: This file is R2ML rule in the R2ML XML format after executing OCL EBNF injector,
+ the OCL2R2ML transformation, the R2ML2XML transformation and XML extractor.
+
+Other files:
+------------
+ - OCL-ebnfinjector.jar: OCL EBNF injector that is used to translate OCL code into OCL model.
+
+References:
+-----------
+[1] Milanović, M., Gašević, D., Guirca, A., Wagner, G., Devedžić, V., "Towards Sharing Rules Between OWL/SWRL and UML/OCL", Electronic Communications of the European Association of Software Science and Technology, Volume 5, 2006.
+[2] Milanović, M. "Modeling rules on the Semantic Web", master thesis, GOOD OLD AI Lab, Faculty of organizational sciences, University of Belgrade.
diff --git a/atlTransformations/OCL2SWRL/OCL2SWRL.zip b/atlTransformations/OCL2SWRL/OCL2SWRL.zip
new file mode 100644
index 0000000..58dead4
--- /dev/null
+++ b/atlTransformations/OCL2SWRL/OCL2SWRL.zip
Binary files differ
diff --git a/atlTransformations/OCL2SWRL/README.txt b/atlTransformations/OCL2SWRL/README.txt
new file mode 100644
index 0000000..c00fce2
--- /dev/null
+++ b/atlTransformations/OCL2SWRL/README.txt
@@ -0,0 +1,81 @@
+*********************************************************
+** Description: OCL2SWRL ATL transformation scenario
+** Author: Milan Milanovic <milan at milanovic.org>
+** Date: February 15 , 2007
+********************************************************
+
+This ATL scenario transforms OCL (Object Constraint Language) invariants into the R2ML (REWERSE I1 Markup Language) rules,
+which is used as intermediary language, and then into the SWRL rules (Semantic Web Rule Language). It is composed of OCL
+EBNF injector (to OCL metamodel), transformations (OCL2R2ML, R2ML2RDM) and an XML extractor that produces
+XML documents that conform to the SWRL XML syntax and R2ML syntax defined by REWERSE I1 group. To find more
+details about this transformation scenario, please refer to [1]-[2]-[3]. This transformation scenario includes
+two other transformation scenarios (OCL2R2ML and R2ML2SWRL), see below.
+
+See also:
+ -- OCL2R2ML transformation scenario - http://www.eclipse.org/atl/atlTransformations/#OCL2R2ML
+ -- R2ML2SWRL transformation scenario - http://www.eclipse.org/atl/atlTransformations/#R2ML2SWRL
+ -- R2ML (REWERSE I1 Rule Markup Language) - http://oxygen.informatik.tu-cottbus.de/rewerse-i1/?q=node/6
+ -- SWRL (Semantic Web Rule Language) - http://www.w3.org/Submission/SWRL/
+ -- RDM metamodel - http://www.aifb.uni-karlsruhe.de/WBS/sbr/publications/owl-metamodeling.pdf
+ -- OWL Web Ontology Language: XML Presentation Syntax - http://www.w3.org/TR/owl-xmlsyntax/
+ -- OWL (Web Ontology language) - http://www.w3.org/2004/OWL/
+ -- Object Constraint Language - OMG Available Specification, Version 2.0, formal/06-05-01.
+ [Online] http://www.omg.org/cgi-bin/doc?formal/06-05-01
+
+Transformation files:
+---------------------
+ - R2ML2XML.atl: ATL transformation that transforms an R2ML model into an
+ an XML models with R2ML syntax elements.
+
+ - RDM2XML.atl: ATL transformation that transforms an RDM model into an
+ an XML models with SWRL/OWL syntax elements.
+
+ - OCL2R2ML.atl: The core transformation, that produced an R2ML model from
+ a OCL model (instance of OCL metamodel).
+
+ - R2ML2RDM.atl: The core transformation, that produced an RDM model from
+ a R2ML model (instance of R2ML metamodel).
+
+ - OCL2SWRL.xml: An ANT script that automatically executes the 2 main ATL transformations (OCL2R2ML and R2ML2RDM),
+ EBNF injector to produce OCL model from OCL file, and a XML extractor
+ to produce R2ML XML documents from R2ML model and SWRL XML documents from RDM model.
+ It can be executed by right-clicking on it, then clicking on "Run As->Ant Build".
+ To execute this transformation on other SWRL examples, place your OCL invariant files
+ in the models/ocl folder and make necessary changes in ANT script.
+
+Metamodel files:
+----------------
+ - XML.xmi: XML metamodel in MOF XMI 1.2 format (MOF-1.4). This metamodel is part of standard metamodels
+ used with ATL. It is used when models are tranformed into XML documents or vice versa.
+
+ - OCL.xmi: OCL metamodel in MOF XMI 1.2 format (MOF-1.4). This model represents an abstract syntax for
+ the OCL language.
+
+ - RDM.xmi: RDM metamodel in MOF XMI 1.2 format (MOF-1.4). This model represents an abstract syntax for
+ the SWRL language.
+
+ - R2ML.xmi: R2ML metamodel in MOF XMI 1.2 format (MOF-1.4). Metamodel of the R2ML language.
+
+ - Every metamodel have KM3 and Ecore EMF XMI 2.0 format versions.
+
+Sample files:
+-------------
+ - Models/ocl/m1.ocl: This file is simple OCL invariant and is used as input example by
+ this transformation scenario (it must be invariant with implication, because
+ SWRL rules are represented as implications).
+
+ - Models/r2ml-xml/R2MLRule.xml: This file is R2ML rule in the R2ML XML format after executing OCL EBNF injector,
+ the OCL2R2ML transformation, the R2ML2XML transformation and XML extractor.
+
+ - Models/swrl-xml/SWRLRule.xml: This file is SWRL rule in the SWRL XML format after executing the R2ML2RDM
+ transformation, the RDM2XML transformation and XML extractor.
+
+Other files:
+------------
+ - OCL-ebnfinjector.jar: OCL EBNF injector that is used to translate OCL code into OCL model.
+
+References:
+-----------
+[1] Milanović, M., Gašević, D., Guirca, A., Wagner, G., Devedžić, V., "Towards Sharing Rules Between OWL/SWRL and UML/OCL", Electronic Communications of the European Association of Software Science and Technology, Volume 5, 2006.
+[2] Milanović, M. "Modeling rules on the Semantic Web", master thesis, GOOD OLD AI Lab, Faculty of organizational sciences, University of Belgrade.
+[3] Milanović, M., Gašević, D., Guirca, A., Wagner, G., Devedžić, V., "Bridging Concrete and Abstract Syntax of Web Rule Languages", In Proceedings of the First International Conference on Web Reasoning and Rule Systems (RR2007), Innsbruck, Austria, 2007.
\ No newline at end of file
diff --git "a/atlTransformations/PathExp2PetriNet/ExamplePathExp2PetriNet\133v00.01\135.pdf" "b/atlTransformations/PathExp2PetriNet/ExamplePathExp2PetriNet\133v00.01\135.pdf"
new file mode 100644
index 0000000..c87219e
--- /dev/null
+++ "b/atlTransformations/PathExp2PetriNet/ExamplePathExp2PetriNet\133v00.01\135.pdf"
Binary files differ
diff --git a/atlTransformations/PathExp2PetriNet/PathExp2PetriNet.zip b/atlTransformations/PathExp2PetriNet/PathExp2PetriNet.zip
new file mode 100644
index 0000000..c680f1f
--- /dev/null
+++ b/atlTransformations/PathExp2PetriNet/PathExp2PetriNet.zip
Binary files differ
diff --git a/atlTransformations/Port/Port.zip b/atlTransformations/Port/Port.zip
new file mode 100644
index 0000000..484567a
--- /dev/null
+++ b/atlTransformations/Port/Port.zip
Binary files differ
diff --git a/atlTransformations/Public2Private/PetriNet-Privatized.png b/atlTransformations/Public2Private/PetriNet-Privatized.png
new file mode 100644
index 0000000..77bff31
--- /dev/null
+++ b/atlTransformations/Public2Private/PetriNet-Privatized.png
Binary files differ
diff --git a/atlTransformations/Public2Private/PetriNet.png b/atlTransformations/Public2Private/PetriNet.png
new file mode 100644
index 0000000..db0fa45
--- /dev/null
+++ b/atlTransformations/Public2Private/PetriNet.png
Binary files differ
diff --git a/atlTransformations/Public2Private/Public2Private.zip b/atlTransformations/Public2Private/Public2Private.zip
new file mode 100644
index 0000000..30c9530
--- /dev/null
+++ b/atlTransformations/Public2Private/Public2Private.zip
Binary files differ
diff --git a/atlTransformations/Public2Private/README.txt b/atlTransformations/Public2Private/README.txt
new file mode 100644
index 0000000..c3b4066
--- /dev/null
+++ b/atlTransformations/Public2Private/README.txt
@@ -0,0 +1,24 @@
+The Public2Private ATL transformation makes all public attributes of a UML 1.4 model private.
+Getters and setters are also created appropriately (i.e. no setter for a frozen attribute).
+
+This transformation uses ATL refining mode as defined in [1]:
+"In ATL, source models are read-only and target models are write-only;
+this prohibits in-place transformations. However, such transformations are
+quite common in certain domains. Therefore, ATL provides a mechanism to
+answer this need: refining mode. This mode can be used for transformations
+having the same source and target metamodel. Unmatched source elements are
+automatically copied into target model, as if a default copying rule was
+present."
+
+Thanks to refining mode, only two rules have to be written: one for read-only (i.e. "frozen"
+in UML terminology) attributes and one for read-write attributes.
+
+Source and target models conform to UML the 1.4 metamodel provided as UMLDI.xmi.
+A sample source model (PetriNet.xmi) and its corresponding target model (PetriNet-Privatized.xmi) are given.
+Both models are also given in PNG format for easy visualization.
+Additional source models may be created using Poseidon (http://www.gentleware.com/).
+
+File Configuration.png shows how to configure the transformation for launch.
+
+References:
+[1] Jouault, F., and Kurtev, I., Transforming Models with ATL, in proceedings of the Model Transformation in Practice Workshop, October 3rd 2005, part of the MoDELS 2005 conference
\ No newline at end of file
diff --git a/atlTransformations/QVT2ATLVM/QVT2ATLVM.zip b/atlTransformations/QVT2ATLVM/QVT2ATLVM.zip
new file mode 100644
index 0000000..198c63a
--- /dev/null
+++ b/atlTransformations/QVT2ATLVM/QVT2ATLVM.zip
Binary files differ
diff --git a/atlTransformations/R2ML2OCL/R2ML2OCL.zip b/atlTransformations/R2ML2OCL/R2ML2OCL.zip
new file mode 100644
index 0000000..ef8e960
--- /dev/null
+++ b/atlTransformations/R2ML2OCL/R2ML2OCL.zip
Binary files differ
diff --git a/atlTransformations/R2ML2OCL/README.txt b/atlTransformations/R2ML2OCL/README.txt
new file mode 100644
index 0000000..34b92e2
--- /dev/null
+++ b/atlTransformations/R2ML2OCL/README.txt
@@ -0,0 +1,60 @@
+*********************************************************
+** Description: R2ML2OCL ATL transformation scenario
+** Author: Milan Milanovic <milan at milanovic.org>
+** Date: October 10, 2006
+********************************************************
+
+This ATL scenario transforms R2ML (REWERSE I1 Markup Language) into OCL (Object Constraint Language).
+It is composed of R2ML injector (to R2ML metamodel), transformations (R2ML2OCL) and an OCL extractor
+that produces OCL documents that conform to the OCL grammar. To find more details about this
+transformation scenario, please refer to [1]-[2].
+
+See also:
+ -- OCL2R2ML transformations scenario
+ -- R2ML (REWERSE I1 Rule Markup Language) - http://oxygen.informatik.tu-cottbus.de/rewerse-i1/?q=node/6
+ -- Object Constraint Language - OMG Available Specification, Version 2.0, formal/06-05-01.
+ [Online] http://www.omg.org/cgi-bin/doc?formal/06-05-01
+
+Transformation files:
+---------------------
+ - XML2R2ML.atl: ATL transformation that transforms an XML model that are
+ injected from R2ML XML documents, into R2ML model.
+
+ - R2ML2OCL.atl: The core transformation, that produced an OCL model from
+ a R2ML model (instance of R2ML metamodel).
+
+ - R2ML2OCL.xml: An ANT script that automatically executes the 2 ATL transformations (XML2R2ML and R2ML2OCL)
+ and the EBNF extractor to produce a OCL code from OCL model. It can be
+ executed by right-clicking on it, then clicking on "Run As->Ant Build".
+ To execute this transformation on other R2ML examples, place your R2ML models
+ in the models/r2ml-xml folder and make necessary changes in ANT script.
+Metamodel files:
+----------------
+ - XML.xmi: XML metamodel in MOF XMI 1.2 format (MOF-1.4). This metamodel is part of standard metamodels
+ used with ATL. It is used when models are tranformed into XML documents or vice versa.
+
+ - OCL.xmi: OCL metamodel in MOF XMI 1.2 format (MOF-1.4). This model represents an abstract syntax for
+ the OCL language.
+
+ - R2ML.xmi: R2ML metamodel in MOF XMI 1.2 format (MOF-1.4). Metamodel of the R2ML language.
+
+ - TCS.xmi: Textual Concrete Syntax metamodel in MOF XMI 1.2 format (MOF-1.4).
+
+ - Every metamodel have KM3 and Ecore EMF XMI 2.0 format versions.
+
+Sample files:
+-------------
+ - Models/r2ml-xml/R2MLRule.xml: This file is R2ML rule in the R2ML XML format and is used as input example by
+ this transformation scenario.
+
+ - Models/ocl/m1.ocl: This file is OCL invariant after the XML injector, the R2ML2OCL transformation and
+ the OCL EBNF extractor.
+
+Other files:
+------------
+ - OCL.tcs: OCL textual concrete syntax
+
+References:
+-----------
+[1] Milanović, M., Gašević, D., Guirca, A., Wagner, G., Devedžić, V., "Towards Sharing Rules Between OWL/SWRL and UML/OCL", Electronic Communications of the European Association of Software Science and Technology, Volume 5, 2006.
+[2] Milanović, M. "Modeling rules on the Semantic Web", master thesis, GOOD OLD AI Lab, Faculty of organizational sciences, University of Belgrade.
diff --git a/atlTransformations/R2ML2SWRL/R2ML2SWRL.zip b/atlTransformations/R2ML2SWRL/R2ML2SWRL.zip
new file mode 100644
index 0000000..b6a94d0
--- /dev/null
+++ b/atlTransformations/R2ML2SWRL/R2ML2SWRL.zip
Binary files differ
diff --git a/atlTransformations/R2ML2SWRL/README.txt b/atlTransformations/R2ML2SWRL/README.txt
new file mode 100644
index 0000000..0bf8d59
--- /dev/null
+++ b/atlTransformations/R2ML2SWRL/README.txt
@@ -0,0 +1,62 @@
+*********************************************************
+** Description: R2ML2SWRL ATL transformation scenario
+** Author: Milan Milanovic <milan at milanovic.org>
+** Date: August 25, 2006
+********************************************************
+
+This ATL scenario transforms R2ML (REWERSE I1 Markup Language) into SWRL (Semantic Web Rule Language).
+It is composed of R2ML injector (to R2ML metamodel), transformations (R2ML2RDM) and an RDM extractor
+that produces XML documents that conform to the SWRL/OWL syntax defined by W3C. To find more
+details about this transformation scenario, please refer to [1]-[2].
+
+See also:
+ -- SWRL2R2ML transformations scenario
+ -- R2ML (REWERSE I1 Rule Markup Language) - http://oxygen.informatik.tu-cottbus.de/rewerse-i1/?q=node/6
+ -- SWRL (Semantic Web Rule Language) - http://www.w3.org/Submission/SWRL/
+ -- RDM metamodel - http://www.aifb.uni-karlsruhe.de/WBS/sbr/publications/owl-metamodeling.pdf
+ -- OWL Web Ontology Language: XML Presentation Syntax - http://www.w3.org/TR/owl-xmlsyntax/
+ -- OWL (Web Ontology language) - http://www.w3.org/2004/OWL/
+
+Transformation files:
+---------------------
+ - RDM2XML.atl: ATL transformation that transforms an RDM model into an
+ an XML models with SWRL/OWL syntax elements.
+
+ - R2ML2RDM.atl: The core transformation, that produced an RDM model from
+ a R2ML model (instance of R2ML metamodel).
+
+ - XML2R2ML.atl: ATL transformation that transforms an XML model that are
+ injected from R2ML XML documents, into R2ML model.
+
+ - R2ML2SWRL.xml: An ANT script that automatically executes the 3 ATL transformations and
+ the pair XML injector/extractor to produce a R2ML model from R2ML document,
+ and to produce SWRL XML documents from RDM model, respectively. It can be
+ executed by right-clicking on it, then clicking on "Run As->Ant Build".
+ To execute this transformation on other R2ML examples, place your R2ML models
+ in the models/r2ml-xml folder and make necessary changes in ANT script.
+
+Metamodel files:
+----------------
+ - XML.xmi: XML metamodel in MOF XMI 1.2 format (MOF-1.4). This metamodel is part of standard metamodels
+ used with ATL. It is used when models are tranformed into XML documents or vice versa.
+
+ - RDM.xmi: RDM metamodel in MOF XMI 1.2 format (MOF-1.4). This model represents an abstract syntax for
+ the SWRL language.
+
+ - R2ML.xmi: R2ML metamodel in MOF XMI 1.2 format (MOF-1.4). Metamodel of the R2ML language.
+
+ - Every metamodel have KM3 and Ecore EMF XMI 2.0 format versions.
+
+Sample files:
+-------------
+ - Models/swrl-xml/SWRLRule.xml: This file is SWRL rule in the SWRL XML format after executing XML injector,
+ the XML2R2ML transformation, the R2ML2RDM transformation, the RDM2XML transformation
+ and XML extractor.
+
+ - Models/r2ml-xml/R2MLRule.xml: This file is the R2ML rule in the R2ML XML format, and is used as input example
+ by this transformation scenario.
+
+References:
+-----------
+[1] Milanoviæ, M., Gaševiæ, D., Guirca, A., Wagner, G., Devedžiæ, V., "Towards Sharing Rules Between OWL/SWRL and UML/OCL", Electronic Communications of the European Association of Software Science and Technology, Volume 5, 2006.
+[2] Milanoviæ, M. "Modeling rules on the Semantic Web", master thesis, GOOD OLD AI Lab, Faculty of organizational sciences, University of Belgrade.
diff --git a/atlTransformations/RSS2ATOM/RSS2ATOM.doc b/atlTransformations/RSS2ATOM/RSS2ATOM.doc
new file mode 100644
index 0000000..b27aebf
--- /dev/null
+++ b/atlTransformations/RSS2ATOM/RSS2ATOM.doc
Binary files differ
diff --git a/atlTransformations/RSS2ATOM/RSS2ATOM.pdf b/atlTransformations/RSS2ATOM/RSS2ATOM.pdf
new file mode 100644
index 0000000..5d82969
--- /dev/null
+++ b/atlTransformations/RSS2ATOM/RSS2ATOM.pdf
Binary files differ
diff --git a/atlTransformations/RSS2ATOM/RSS2ATOM.zip b/atlTransformations/RSS2ATOM/RSS2ATOM.zip
new file mode 100644
index 0000000..8f66114
--- /dev/null
+++ b/atlTransformations/RSS2ATOM/RSS2ATOM.zip
Binary files differ
diff --git a/atlTransformations/RaiseSupplierAbstractionLevel/RaiseSupplierAbstractionLevel.pdf b/atlTransformations/RaiseSupplierAbstractionLevel/RaiseSupplierAbstractionLevel.pdf
new file mode 100644
index 0000000..7915b5c
--- /dev/null
+++ b/atlTransformations/RaiseSupplierAbstractionLevel/RaiseSupplierAbstractionLevel.pdf
Binary files differ
diff --git a/atlTransformations/RaiseSupplierAbstractionLevel/RaiseSupplierAbstractionLevel.zip b/atlTransformations/RaiseSupplierAbstractionLevel/RaiseSupplierAbstractionLevel.zip
new file mode 100644
index 0000000..d8794bc
--- /dev/null
+++ b/atlTransformations/RaiseSupplierAbstractionLevel/RaiseSupplierAbstractionLevel.zip
Binary files differ
diff --git a/atlTransformations/RedundantClassRemovable/RedundantClassRemovable.pdf b/atlTransformations/RedundantClassRemovable/RedundantClassRemovable.pdf
new file mode 100644
index 0000000..e109336
--- /dev/null
+++ b/atlTransformations/RedundantClassRemovable/RedundantClassRemovable.pdf
Binary files differ
diff --git a/atlTransformations/RedundantClassRemovable/RedundantClassRemovable.zip b/atlTransformations/RedundantClassRemovable/RedundantClassRemovable.zip
new file mode 100644
index 0000000..4373c2a
--- /dev/null
+++ b/atlTransformations/RedundantClassRemovable/RedundantClassRemovable.zip
Binary files differ
diff --git a/atlTransformations/RemovingAssociationClass/RemovingAssociationClass.pdf b/atlTransformations/RemovingAssociationClass/RemovingAssociationClass.pdf
new file mode 100644
index 0000000..e177e92
--- /dev/null
+++ b/atlTransformations/RemovingAssociationClass/RemovingAssociationClass.pdf
Binary files differ
diff --git a/atlTransformations/RemovingAssociationClass/RemovingAssociationClass.zip b/atlTransformations/RemovingAssociationClass/RemovingAssociationClass.zip
new file mode 100644
index 0000000..6ab013f
--- /dev/null
+++ b/atlTransformations/RemovingAssociationClass/RemovingAssociationClass.zip
Binary files differ
diff --git a/atlTransformations/RemovingManyManyAssociation/RemovingManyManyAssociation.pdf b/atlTransformations/RemovingManyManyAssociation/RemovingManyManyAssociation.pdf
new file mode 100644
index 0000000..3b433bb
--- /dev/null
+++ b/atlTransformations/RemovingManyManyAssociation/RemovingManyManyAssociation.pdf
Binary files differ
diff --git a/atlTransformations/RemovingManyManyAssociation/RemovingManyManyAssociation.zip b/atlTransformations/RemovingManyManyAssociation/RemovingManyManyAssociation.zip
new file mode 100644
index 0000000..2599723
--- /dev/null
+++ b/atlTransformations/RemovingManyManyAssociation/RemovingManyManyAssociation.zip
Binary files differ
diff --git a/atlTransformations/ReplaceAssociationByForeignKey/ReplaceAssociationByForeignKey.pdf b/atlTransformations/ReplaceAssociationByForeignKey/ReplaceAssociationByForeignKey.pdf
new file mode 100644
index 0000000..082d7f2
--- /dev/null
+++ b/atlTransformations/ReplaceAssociationByForeignKey/ReplaceAssociationByForeignKey.pdf
Binary files differ
diff --git a/atlTransformations/ReplaceAssociationByForeignKey/ReplaceAssociationByForeignKey.zip b/atlTransformations/ReplaceAssociationByForeignKey/ReplaceAssociationByForeignKey.zip
new file mode 100644
index 0000000..5d5d884
--- /dev/null
+++ b/atlTransformations/ReplaceAssociationByForeignKey/ReplaceAssociationByForeignKey.zip
Binary files differ
diff --git a/atlTransformations/ReplaceInheritanceByAssociation/ReplaceInheritanceByAssociation.pdf b/atlTransformations/ReplaceInheritanceByAssociation/ReplaceInheritanceByAssociation.pdf
new file mode 100644
index 0000000..715bb1c
--- /dev/null
+++ b/atlTransformations/ReplaceInheritanceByAssociation/ReplaceInheritanceByAssociation.pdf
Binary files differ
diff --git a/atlTransformations/ReplaceInheritanceByAssociation/ReplaceInheritanceByAssociation.zip b/atlTransformations/ReplaceInheritanceByAssociation/ReplaceInheritanceByAssociation.zip
new file mode 100644
index 0000000..9eabe65
--- /dev/null
+++ b/atlTransformations/ReplaceInheritanceByAssociation/ReplaceInheritanceByAssociation.zip
Binary files differ
diff --git a/atlTransformations/SSL2SDL/SSL2SDL.zip b/atlTransformations/SSL2SDL/SSL2SDL.zip
new file mode 100644
index 0000000..61998ea
--- /dev/null
+++ b/atlTransformations/SSL2SDL/SSL2SDL.zip
Binary files differ
diff --git a/atlTransformations/SSL2SDL/ssl2sdl.pdf b/atlTransformations/SSL2SDL/ssl2sdl.pdf
new file mode 100644
index 0000000..3fa67ef
--- /dev/null
+++ b/atlTransformations/SSL2SDL/ssl2sdl.pdf
Binary files differ
diff --git a/atlTransformations/SWRL2R2ML/README.txt b/atlTransformations/SWRL2R2ML/README.txt
new file mode 100644
index 0000000..d5c6c11
--- /dev/null
+++ b/atlTransformations/SWRL2R2ML/README.txt
@@ -0,0 +1,62 @@
+*********************************************************
+** Description: SWRL2R2ML ATL transformation scenario
+** Author: Milan Milanovic <milan at milanovic.org>
+** Date: August 10, 2006
+********************************************************
+
+This ATL scenario transforms SWRL (Semantic Web Rule Language) into R2ML (REWERSE I1 Markup Language).
+It is composed of SWRL injector (to RDM metamodel), transformations (RDM2R2ML) and an R2ML extractor
+that produces XML documents that conform to the R2ML syntax defined by REWERSE I1 group. To find more
+details about this transformation scenario, please refer to [1]-[2].
+
+See also:
+ -- R2ML2SWRL transformations scenario
+ -- R2ML (REWERSE I1 Rule Markup Language) - http://oxygen.informatik.tu-cottbus.de/rewerse-i1/?q=node/6
+ -- SWRL (Semantic Web Rule Language) - http://www.w3.org/Submission/SWRL/
+ -- RDM metamodel - http://www.aifb.uni-karlsruhe.de/WBS/sbr/publications/owl-metamodeling.pdf
+ -- OWL Web Ontology Language: XML Presentation Syntax - http://www.w3.org/TR/owl-xmlsyntax/
+ -- OWL (Web Ontology language) - http://www.w3.org/2004/OWL/
+
+Transformation files:
+---------------------
+ - R2ML2XML.atl: ATL transformation that transforms an R2ML model into an
+ an XML models with R2ML syntax elements.
+
+ - RDM2R2ML.atl: The core transformation, that produced an R2ML model from
+ a RDM model (instance of SWRL metamodel).
+
+ - XML2RDM.atl: ATL transformation that transforms an XML model that are
+ injected from SWRL XML documents, into RDM model.
+
+ - SWRL2R2ML.xml: An ANT script that automatically executes the 3 ATL transformations and
+ the pair XML injector/extractor to produce a RDM model from SWRL document,
+ and to produce R2ML XML documents from R2ML model, respectively. It can be
+ executed by right-clicking on it, then clicking on "Run As->Ant Build".
+ To execute this transformation on other SWRL examples, place your SWRL models
+ in the models/swrl-xml folder and make necessary changes in ANT script.
+
+Metamodel files:
+----------------
+ - XML.xmi: XML metamodel in MOF XMI 1.2 format (MOF-1.4). This metamodel is part of standard metamodels
+ used with ATL. It is used when models are tranformed into XML documents or vice versa.
+
+ - RDM.xmi: RDM metamodel in MOF XMI 1.2 format (MOF-1.4). This model represents an abstract syntax for
+ the SWRL language.
+
+ - R2ML.xmi: R2ML metamodel in MOF XMI 1.2 format (MOF-1.4). Metamodel of the R2ML language.
+
+ - Every metamodel have KM3 and Ecore EMF XMI 2.0 format versions.
+
+Sample files:
+-------------
+ - Models/swrl-xml/SWRLRule1.xml: This file is the SWRL rule in the SWRL/XML from the SWRL specification,
+ and is used as input example by this transformation scenario.
+
+ - Models/r2ml-xml/R2MLRule.xml: This file is R2ML rule in the R2ML XML format after executing XML injector,
+ the XML2RDM transformation, the RDM2R2ML transformation, the R2ML2XML transformation
+ and XML extractor.
+
+References:
+-----------
+[1] Milanović, M., Gašević, D., Guirca, A., Wagner, G., Devedžić, V., "Towards Sharing Rules Between OWL/SWRL and UML/OCL", Electronic Communications of the European Association of Software Science and Technology, Volume 5, 2006.
+[2] Milanović, M. "Modeling rules on the Semantic Web", master thesis, GOOD OLD AI Lab, Faculty of organizational sciences, University of Belgrade.
diff --git a/atlTransformations/SWRL2R2ML/SWRL2R2ML.zip b/atlTransformations/SWRL2R2ML/SWRL2R2ML.zip
new file mode 100644
index 0000000..f50f54f
--- /dev/null
+++ b/atlTransformations/SWRL2R2ML/SWRL2R2ML.zip
Binary files differ
diff --git a/atlTransformations/SideEffect/SideEffect.zip b/atlTransformations/SideEffect/SideEffect.zip
new file mode 100644
index 0000000..8bf42a1
--- /dev/null
+++ b/atlTransformations/SideEffect/SideEffect.zip
Binary files differ
diff --git a/atlTransformations/SimpleClass2SimpleRDBMS/README.txt b/atlTransformations/SimpleClass2SimpleRDBMS/README.txt
new file mode 100644
index 0000000..0d7574f
--- /dev/null
+++ b/atlTransformations/SimpleClass2SimpleRDBMS/README.txt
@@ -0,0 +1,39 @@
+This transformation implements the case study used in the Workshop Model Transformations
+in Practice collocated with the MoDELS Conference, October, 2005. The description of the
+case study can be found at the workshop web site: http://sosym.dcs.kcl.ac.uk/events/mtip05/.
+
+Two versions of the SimpleClass2SimpleRDBMS transformation have been developed:
+- The first one, which is presented in [1], uses some ATL features that are not implemented
+in the engine yet. Its purpose is to illustrate the planned features of the language.
+- The second one, coming with this README.txt, is another version that works with
+the ATL engine available on http://eclipse.org/gmt as of November 2005. This second version
+uses roughly the same helpers as the first version.
+
+Example files:
+
+ SimpleClass.km3 - the source metamodel expressed in KM3.
+
+ SimpleRDBMS.km3 - the target metamodel expressed in KM3.
+
+ KM32SimpleClass.atl - ATL transformation that creates a model conforming to
+ the source metamodel from a KM3 model: SimpleClass is really close
+ to KM3 and we do not want to type a sample in XMI.
+
+ Sample.km3 - this is a sample source model expressed in KM3. It must be transformed to
+ a SimpleClass model by using the KM32SimpleClass transformation.
+
+ Sample-KM3.ecore - this is an XMI version of Sample.km3: a sample KM3 model.
+
+ Sample-SimpleClass.ecore - a sample source model obtained by applying KM32SimpleClass
+ to Sample.km3.
+
+ SimpleClass2SimpleRDBMS.atl - the implementation of the case study in ATL.
+
+ Sample-SimpleRDBMS.ecore - the resulting model derived from Sample_SimpleClass.ecore after applying
+ the SimpleClass2SimpleRDBMS transformation.
+
+References:
+
+[1] Jouault, F., and Kurtev, I., Transforming Models with ATL, in proceedings of Model Transformations in Practice
+Workshop, October 3rd 2005, part of the MoDELS 2005 Conference
+This paper may be obtained from http://sosym.dcs.kcl.ac.uk/events/mtip05/submissions/jouault_kurtev__transforming_models_with_atl.pdf
\ No newline at end of file
diff --git a/atlTransformations/SimpleClass2SimpleRDBMS/SimpleClass2SimpleRDBMS.zip b/atlTransformations/SimpleClass2SimpleRDBMS/SimpleClass2SimpleRDBMS.zip
new file mode 100644
index 0000000..2567880
--- /dev/null
+++ b/atlTransformations/SimpleClass2SimpleRDBMS/SimpleClass2SimpleRDBMS.zip
Binary files differ
diff --git "a/atlTransformations/SoftwareQualityControl2Bugzilla/ExampleSoftwareQualityControl2Bugzilla\133v00.01\135.pdf" "b/atlTransformations/SoftwareQualityControl2Bugzilla/ExampleSoftwareQualityControl2Bugzilla\133v00.01\135.pdf"
new file mode 100644
index 0000000..92ab6d1
--- /dev/null
+++ "b/atlTransformations/SoftwareQualityControl2Bugzilla/ExampleSoftwareQualityControl2Bugzilla\133v00.01\135.pdf"
Binary files differ
diff --git a/atlTransformations/SoftwareQualityControl2Bugzilla/SoftwareQualityControl2Bugzilla.zip b/atlTransformations/SoftwareQualityControl2Bugzilla/SoftwareQualityControl2Bugzilla.zip
new file mode 100644
index 0000000..d1af1c4
--- /dev/null
+++ b/atlTransformations/SoftwareQualityControl2Bugzilla/SoftwareQualityControl2Bugzilla.zip
Binary files differ
diff --git "a/atlTransformations/SoftwareQualityControl2MantisBT/ExampleSoftwareQualityControl2MantisBugTracker\133v00.01\135.pdf" "b/atlTransformations/SoftwareQualityControl2MantisBT/ExampleSoftwareQualityControl2MantisBugTracker\133v00.01\135.pdf"
new file mode 100644
index 0000000..a14f029
--- /dev/null
+++ "b/atlTransformations/SoftwareQualityControl2MantisBT/ExampleSoftwareQualityControl2MantisBugTracker\133v00.01\135.pdf"
Binary files differ
diff --git a/atlTransformations/SoftwareQualityControl2MantisBT/SoftwareQualityControl2MantisBugTracker.zip b/atlTransformations/SoftwareQualityControl2MantisBT/SoftwareQualityControl2MantisBugTracker.zip
new file mode 100644
index 0000000..74cfca9
--- /dev/null
+++ b/atlTransformations/SoftwareQualityControl2MantisBT/SoftwareQualityControl2MantisBugTracker.zip
Binary files differ
diff --git a/atlTransformations/Syntax2SBVR2UML/Syntax2SBVR2UML.zip b/atlTransformations/Syntax2SBVR2UML/Syntax2SBVR2UML.zip
new file mode 100644
index 0000000..152e3eb
--- /dev/null
+++ b/atlTransformations/Syntax2SBVR2UML/Syntax2SBVR2UML.zip
Binary files differ
diff --git a/atlTransformations/TT2BDD/README b/atlTransformations/TT2BDD/README
new file mode 100644
index 0000000..5ca997f
--- /dev/null
+++ b/atlTransformations/TT2BDD/README
@@ -0,0 +1,171 @@
+
+Model transformation case study using ATL :
+Truth tables to Binary Decision Diagrams
+
+Guillaume Savaton, ESEO
+<guillaume (dot) savaton (at) eseo (dot) fr>
+
+-----------------------------------------------------------
+Summary
+-----------------------------------------------------------
+
+These files provide a case study for model transformation applied to digital logic circuits.
+Engineers can use various formalisms to represent combinatorial or sequential logic.
+The most widespread representations for combinatorial logic are truth tables and boolean equations.
+
+In many EDA tools, combinatorial logic is represented in a canonical form using Binary Decision
+Diagrams (BDD).
+BDDs are manly used for model checking and logic optimization.
+
+The purpose here is to use model transformation to transform a truth table into
+a binary decision diagram.
+
+-----------------------------------------------------------
+Truth tables
+-----------------------------------------------------------
+
+The test files provided correspond to the following example.
+Files TT/examples/Test.tt and Test.ttmodel contain representations of this truth table :
+
+ A B C D | S
+----------|---
+ 0 0 - - | 0
+ 0 1 0 0 | 1
+ 0 1 0 1 | 0
+ 0 1 1 - | 0
+ 1 0 0 0 | 0
+ 1 0 1 0 | 1
+ 1 - - 1 | 0
+ 1 1 0 0 | 1
+ 1 1 1 0 | 0
+
+A truth table (class TruthTable of the metamodel) has ports (class Port).
+Ports are either
+- input ports (class InputPort) such as A, B, C, D in the example ;
+- or output ports (class OutputPort) such as S in the example.
+
+A truth table is composed of rows (class Row of the metamodels) that can appear in any order.
+A row provides a mapping between an input pattern (a detected set of values of input ports)
+and an output pattern (values assigned to output ports).
+A row is made of cells (class Cell) : each cell associates a boolean value to a given port.
+
+Usually, boolean values are represented using symbols "0" (false) and "1" (true).
+In file Test.tt, the symbols used are "F" (false) and "T" (true).
+
+In a given row, the absence of a cell for a given input port means that the value of this port is
+indifferent with respect to the result. In the example, this is the case for ports C and D in the first row.
+However, in each row, all output ports must have a corresponding cell.
+
+-----------------------------------------------------------
+Binary decision diagrams
+-----------------------------------------------------------
+
+Here is a BDD representation for the example truth table :
+
+ (A)
+ |
+ 0 --------------------- 1
+ | |
+ (B) (D)
+ | |
+ 0 ------- 1 0 -------- 1
+ | | | |
+ | (C) (B) |
+ | | | |
+ | 0 --- 1 0---------1 |
+ | | | | | |
+ | (D) | (C) (C) |
+ | | | | | |
+ | 0 --- 1 | 0 --- 1 0 --- 1 |
+ | | | | | | | | |
+S = [0] [1] [0][0][0] [1] [1] [0][0]
+
+Usually, edges are distinguished by a line style :
+- dashed lines represent 0 (or false) decisions
+- continuouse lines represent 1 (or true) decisions.
+
+In file Test.bdd, edges are labelled with a symbol : "F" (false) or "T" (true).
+
+The evaluation process in a BDD is recursive and can be easily translated into an if-then-else
+hierarchy :
+
+if A=0 then
+ if B=0 then
+ S := 0;
+ else
+ if C=0 then
+ if D=0 then
+ S := 1;
+ else
+ S := 0;
+ endif
+ else
+ S := 0;
+ endif
+ endif
+else
+ if D=0 then
+ if B=0 then
+ if C=0 then
+ S := 0;
+ else
+ S := 1;
+ endif
+ else
+ if C=0 then
+ S := 1;
+ else
+ S := 0;
+ endif
+ endif
+ else
+ S := 0;
+ endif
+endif
+
+In our metamodel, a binary decision diagram (class BDD of the metamodel) has input and output ports in
+the same sense as truth tables.
+
+A BDD is composed of a tree (class Tree).
+A tree can be either a leaf node (class Leaf) or a subtree (class Subtree).
+A subtree has a reference to an input port (see nodes labeled A, B, C and D on the example).
+Upon the value of this port, two edges can be followed :
+- one corresponding to a 0 (false) value (reference subtreeForZero in the metamodel)
+- one corresponding to a 1 (true) value (reference subtreeForOne in the metamodel)
+
+Leaf nodes represent values assigned to output ports.
+In this example there is only one output port but the provided metamodel supports
+multiple output ports if needed.
+As a result, a leaf node is composed of one or several assignments (class Assignment).
+
+-----------------------------------------------------------
+File index
+-----------------------------------------------------------
+
+Folders :
+ TT/ - All files related to truth tables (metamodel, models, diagrams)
+ BDD/ - All files related to Binary Decision Diagrams (metamodel, models, diagrams)
+ TT2BDD/ - The transformation from truth table to BDD
+
+Files :
+
+ TT/TT.km3 - The Truth Table metamodel in text form (KM3 notation)
+ TT/TT.ecore - The Truth Table metamodel in XMI format
+
+ TT/diagrams/TT.png - Graphical representation of the Truth Table metamodel
+
+ TT/examples/Test.tt - An example truth table in text form
+ TT/examples/Test.ttmodel - The same example in XMI format
+
+ BDD/BDD.km3 - The BDD metamodel in text form (KM3 notation)
+ BDD/BDD.ecore - The BDD metamodel in XMI format
+
+ BDD/diagrams/BDD.png -
+ BDD/diagrams/Tree.png - Graphical representation of the BDD metamodel
+ BDD/diagrams/Nodes.png -
+
+ BDD/examples/Test.bdd - An example BDD in text form
+ BDD/examples/Test.bddmodel - The same example BDD in XMI format
+
+ TT2BDD/TT2BDD.atl - The transformation from Truth Table to BDD, in ATL
+
diff --git a/atlTransformations/TT2BDD/TT2BDD.zip b/atlTransformations/TT2BDD/TT2BDD.zip
new file mode 100644
index 0000000..b625654
--- /dev/null
+++ b/atlTransformations/TT2BDD/TT2BDD.zip
Binary files differ
diff --git "a/atlTransformations/Table2MSOfficeExcel/ExampleTable2MicrosoftOfficeExcel\133v00.01\135.pdf" "b/atlTransformations/Table2MSOfficeExcel/ExampleTable2MicrosoftOfficeExcel\133v00.01\135.pdf"
new file mode 100644
index 0000000..be5f4dc
--- /dev/null
+++ "b/atlTransformations/Table2MSOfficeExcel/ExampleTable2MicrosoftOfficeExcel\133v00.01\135.pdf"
Binary files differ
diff --git a/atlTransformations/Table2MSOfficeExcel/Table2MicrosoftOfficeExcel.zip b/atlTransformations/Table2MSOfficeExcel/Table2MicrosoftOfficeExcel.zip
new file mode 100644
index 0000000..dc536da
--- /dev/null
+++ b/atlTransformations/Table2MSOfficeExcel/Table2MicrosoftOfficeExcel.zip
Binary files differ
diff --git "a/atlTransformations/Table2SVGBarChart/ExampleTable2SVGBarChart\133v00.03\135.pdf" "b/atlTransformations/Table2SVGBarChart/ExampleTable2SVGBarChart\133v00.03\135.pdf"
new file mode 100644
index 0000000..e7e20eb
--- /dev/null
+++ "b/atlTransformations/Table2SVGBarChart/ExampleTable2SVGBarChart\133v00.03\135.pdf"
Binary files differ
diff --git "a/atlTransformations/Table2SVGBarChart/ExampleTable2SVGBarChart\133v00.04\135.pdf" "b/atlTransformations/Table2SVGBarChart/ExampleTable2SVGBarChart\133v00.04\135.pdf"
new file mode 100644
index 0000000..966cd7f
--- /dev/null
+++ "b/atlTransformations/Table2SVGBarChart/ExampleTable2SVGBarChart\133v00.04\135.pdf"
Binary files differ
diff --git "a/atlTransformations/Table2SVGBarChart/ExampleTable2SVGBarChart\133v00.05\135.pdf" "b/atlTransformations/Table2SVGBarChart/ExampleTable2SVGBarChart\133v00.05\135.pdf"
new file mode 100644
index 0000000..bf78f80
--- /dev/null
+++ "b/atlTransformations/Table2SVGBarChart/ExampleTable2SVGBarChart\133v00.05\135.pdf"
Binary files differ
diff --git a/atlTransformations/Table2SVGBarChart/Table2SVGBarChart.zip b/atlTransformations/Table2SVGBarChart/Table2SVGBarChart.zip
new file mode 100644
index 0000000..da17648
--- /dev/null
+++ b/atlTransformations/Table2SVGBarChart/Table2SVGBarChart.zip
Binary files differ
diff --git "a/atlTransformations/Table2SVGPieChart/ExampleTable2SVGPieChart\133v00.03\135.pdf" "b/atlTransformations/Table2SVGPieChart/ExampleTable2SVGPieChart\133v00.03\135.pdf"
new file mode 100644
index 0000000..a8516cb
--- /dev/null
+++ "b/atlTransformations/Table2SVGPieChart/ExampleTable2SVGPieChart\133v00.03\135.pdf"
Binary files differ
diff --git "a/atlTransformations/Table2SVGPieChart/ExampleTable2SVGPieChart\133v00.04\135.pdf" "b/atlTransformations/Table2SVGPieChart/ExampleTable2SVGPieChart\133v00.04\135.pdf"
new file mode 100644
index 0000000..dd9b3ac
--- /dev/null
+++ "b/atlTransformations/Table2SVGPieChart/ExampleTable2SVGPieChart\133v00.04\135.pdf"
Binary files differ
diff --git "a/atlTransformations/Table2SVGPieChart/ExampleTable2SVGPieChart\133v00.05\135.pdf" "b/atlTransformations/Table2SVGPieChart/ExampleTable2SVGPieChart\133v00.05\135.pdf"
new file mode 100644
index 0000000..20d5f64
--- /dev/null
+++ "b/atlTransformations/Table2SVGPieChart/ExampleTable2SVGPieChart\133v00.05\135.pdf"
Binary files differ
diff --git a/atlTransformations/Table2SVGPieChart/Table2SVGPieChart.zip b/atlTransformations/Table2SVGPieChart/Table2SVGPieChart.zip
new file mode 100644
index 0000000..7267070
--- /dev/null
+++ b/atlTransformations/Table2SVGPieChart/Table2SVGPieChart.zip
Binary files differ
diff --git "a/atlTransformations/Table2TabularHTML/ExampleTable2TabularHTML\133v00.03\135.pdf" "b/atlTransformations/Table2TabularHTML/ExampleTable2TabularHTML\133v00.03\135.pdf"
new file mode 100644
index 0000000..109ff10
--- /dev/null
+++ "b/atlTransformations/Table2TabularHTML/ExampleTable2TabularHTML\133v00.03\135.pdf"
Binary files differ
diff --git "a/atlTransformations/Table2TabularHTML/ExampleTable2TabularHTML\133v00.04\135.pdf" "b/atlTransformations/Table2TabularHTML/ExampleTable2TabularHTML\133v00.04\135.pdf"
new file mode 100644
index 0000000..7919c9a
--- /dev/null
+++ "b/atlTransformations/Table2TabularHTML/ExampleTable2TabularHTML\133v00.04\135.pdf"
Binary files differ
diff --git "a/atlTransformations/Table2TabularHTML/ExampleTable2TabularHTML\133v00.05\135.pdf" "b/atlTransformations/Table2TabularHTML/ExampleTable2TabularHTML\133v00.05\135.pdf"
new file mode 100644
index 0000000..95cc171
--- /dev/null
+++ "b/atlTransformations/Table2TabularHTML/ExampleTable2TabularHTML\133v00.05\135.pdf"
Binary files differ
diff --git a/atlTransformations/Table2TabularHTML/Table2TabularHTML.zip b/atlTransformations/Table2TabularHTML/Table2TabularHTML.zip
new file mode 100644
index 0000000..5b5d195
--- /dev/null
+++ b/atlTransformations/Table2TabularHTML/Table2TabularHTML.zip
Binary files differ
diff --git a/atlTransformations/Tree2List/Tree2List.zip b/atlTransformations/Tree2List/Tree2List.zip
new file mode 100644
index 0000000..258299b
--- /dev/null
+++ b/atlTransformations/Tree2List/Tree2List.zip
Binary files differ
diff --git "a/atlTransformations/UML22Measure/ExampleUML22Measure\133v00.01\135.pdf" "b/atlTransformations/UML22Measure/ExampleUML22Measure\133v00.01\135.pdf"
new file mode 100644
index 0000000..a03f021
--- /dev/null
+++ "b/atlTransformations/UML22Measure/ExampleUML22Measure\133v00.01\135.pdf"
Binary files differ
diff --git "a/atlTransformations/UML22Measure/ExampleUML22Measure\133v00.02\135.pdf" "b/atlTransformations/UML22Measure/ExampleUML22Measure\133v00.02\135.pdf"
new file mode 100644
index 0000000..aed72e4
--- /dev/null
+++ "b/atlTransformations/UML22Measure/ExampleUML22Measure\133v00.02\135.pdf"
Binary files differ
diff --git a/atlTransformations/UML22Measure/UML22Measure.zip b/atlTransformations/UML22Measure/UML22Measure.zip
new file mode 100644
index 0000000..6ee6403
--- /dev/null
+++ b/atlTransformations/UML22Measure/UML22Measure.zip
Binary files differ
diff --git "a/atlTransformations/UML2Amble/ExampleUML2Amble\133v00.01\135.pdf" "b/atlTransformations/UML2Amble/ExampleUML2Amble\133v00.01\135.pdf"
new file mode 100644
index 0000000..2424c84
--- /dev/null
+++ "b/atlTransformations/UML2Amble/ExampleUML2Amble\133v00.01\135.pdf"
Binary files differ
diff --git a/atlTransformations/UML2Amble/UML2Amble.zip b/atlTransformations/UML2Amble/UML2Amble.zip
new file mode 100644
index 0000000..d09ae00
--- /dev/null
+++ b/atlTransformations/UML2Amble/UML2Amble.zip
Binary files differ
diff --git a/atlTransformations/UML2AnyLogic/TUDEMFModelHandler.zip b/atlTransformations/UML2AnyLogic/TUDEMFModelHandler.zip
new file mode 100644
index 0000000..40c4212
--- /dev/null
+++ b/atlTransformations/UML2AnyLogic/TUDEMFModelHandler.zip
Binary files differ
diff --git a/atlTransformations/UML2AnyLogic/UML2AnyLogic.zip b/atlTransformations/UML2AnyLogic/UML2AnyLogic.zip
new file mode 100644
index 0000000..da7263c
--- /dev/null
+++ b/atlTransformations/UML2AnyLogic/UML2AnyLogic.zip
Binary files differ
diff --git a/atlTransformations/UML2Java/ExampleUML2Java.pdf b/atlTransformations/UML2Java/ExampleUML2Java.pdf
new file mode 100644
index 0000000..b0163c1
--- /dev/null
+++ b/atlTransformations/UML2Java/ExampleUML2Java.pdf
Binary files differ
diff --git "a/atlTransformations/UML2Java/ExampleUML2Java\133v00.01\135.pdf" "b/atlTransformations/UML2Java/ExampleUML2Java\133v00.01\135.pdf"
new file mode 100644
index 0000000..f326b0e
--- /dev/null
+++ "b/atlTransformations/UML2Java/ExampleUML2Java\133v00.01\135.pdf"
Binary files differ
diff --git a/atlTransformations/UML2Java/UML2Java.zip b/atlTransformations/UML2Java/UML2Java.zip
new file mode 100644
index 0000000..2f14bf3
--- /dev/null
+++ b/atlTransformations/UML2Java/UML2Java.zip
Binary files differ
diff --git a/atlTransformations/UML2KM3/UML2KM3.zip b/atlTransformations/UML2KM3/UML2KM3.zip
new file mode 100644
index 0000000..2c7e733
--- /dev/null
+++ b/atlTransformations/UML2KM3/UML2KM3.zip
Binary files differ
diff --git "a/atlTransformations/UML2MOF/ExampleUML2MOF\133v00.01\135.pdf" "b/atlTransformations/UML2MOF/ExampleUML2MOF\133v00.01\135.pdf"
new file mode 100644
index 0000000..126ac13
--- /dev/null
+++ "b/atlTransformations/UML2MOF/ExampleUML2MOF\133v00.01\135.pdf"
Binary files differ
diff --git a/atlTransformations/UML2MOF/UML2MOF.zip b/atlTransformations/UML2MOF/UML2MOF.zip
new file mode 100644
index 0000000..4cc5f95
--- /dev/null
+++ b/atlTransformations/UML2MOF/UML2MOF.zip
Binary files differ
diff --git a/atlTransformations/UML2OWL/README.txt b/atlTransformations/UML2OWL/README.txt
new file mode 100644
index 0000000..07cceab
--- /dev/null
+++ b/atlTransformations/UML2OWL/README.txt
@@ -0,0 +1,40 @@
+This project contains the UML2OWL scenario. This ATL scenario presents an implementation of the OMG's ODM
+specification. This transformation is used to produce an OWL ontology + OWL Individuals from a UML Model +
+UML Instances.
+
+-- Important -- --
+ To use this transformation scenario, you need to install the UML 2.0 plugin v2.0 or above available at
+ www.eclipse.org/uml2 in order to reference the UML Metamodel used by transformations.
+-- -- -- --
+
+Transformation files:
+ - UML2OWL.atl: The core transformation of the scenario. It is the implementation in ATL of
+ the QVT mapping UML2OWL from ODM specification. It produces an OWL Model from a UML 2.0 Model.
+ - OWL/XmlSyntax/OWL2XML.atl: ATL transformation that transforms an OWL Model into
+ an XML models with OWL/XML syntax elements.
+ - build.xml: An ANT script that automatically executes the 2 ATL transformations and
+ the XML extractor to produce from a uml model an owl document that contains the ontology.
+ It can be executed by right-clicking on it, then clicking on "Run As->Ant Build". To execute
+ this transformation on other uml examples, place your uml models in Samples/UMLModels and change
+ property -- model -- value in ANT script with your uml model name.
+
+Metamodel files:
+ - AMMACore/XML.ecore: XML metamodel in EMF XMI 2.0 format.
+ This metamodel is part of standard metamodels used with ATL.
+ It is used when models are tranformed into XML documents or vice versa.
+ - OWL/OWL.km3: OWL Metamodel in km3 textual syntax. This Metamodel has been designed
+ by following the ODM specification.
+ - OWL/OWL.ecore: OWL Metamodel in Ecore EMF XMI 2.0 format.
+
+Sample files:
+ - Samples/UMLModels/Museum.uml: This UML model represents a Museum. This example that is a well known in the
+ RQL (RDF Query language) communty. This Model also contains some Instances. These latters are used to demonstrate
+ the feasability to create a knowledge base (OWL Individuals) from UML Instances. This Model is conform to the
+ UML 2.0 Metamodel available at eclipse.org/uml2.
+
+ - Samples/OWLModels/Museum-OWL.ecore: The Museum Model conforms to the OWL Metamodel. This Model is obtained after
+ executing the UML2OWL.atl transformation.
+
+ - Samples/UMLFiles/Museum.owl: This file is the Museum ontology in OWL/XML format after executing the OWL2XML
+ transformation and the XML extractor. This file can be used in an ontology editor like Protégé.
+
\ No newline at end of file
diff --git a/atlTransformations/UML2OWL/UML2OWL.zip b/atlTransformations/UML2OWL/UML2OWL.zip
new file mode 100644
index 0000000..7b6e7b6
--- /dev/null
+++ b/atlTransformations/UML2OWL/UML2OWL.zip
Binary files differ
diff --git "a/atlTransformations/UMLActivityDiagram2MSProject/ExampleUmlActivityDiagram2MSProject\133v00.01\135.pdf" "b/atlTransformations/UMLActivityDiagram2MSProject/ExampleUmlActivityDiagram2MSProject\133v00.01\135.pdf"
new file mode 100644
index 0000000..ceb6c36
--- /dev/null
+++ "b/atlTransformations/UMLActivityDiagram2MSProject/ExampleUmlActivityDiagram2MSProject\133v00.01\135.pdf"
Binary files differ
diff --git a/atlTransformations/UMLActivityDiagram2MSProject/UmlActivityDiagram2MSProject.zip b/atlTransformations/UMLActivityDiagram2MSProject/UmlActivityDiagram2MSProject.zip
new file mode 100644
index 0000000..3ee2d1f
--- /dev/null
+++ b/atlTransformations/UMLActivityDiagram2MSProject/UmlActivityDiagram2MSProject.zip
Binary files differ
diff --git a/atlTransformations/UMLCD2UMLProfile/README.txt b/atlTransformations/UMLCD2UMLProfile/README.txt
new file mode 100644
index 0000000..087b775
--- /dev/null
+++ b/atlTransformations/UMLCD2UMLProfile/README.txt
@@ -0,0 +1,22 @@
+********************************************************
+** Description: UML Class Diagram to UML Profile ATL transformation scenario
+** Author: Freddy Allilaire
+** Date: Novembre 19, 2007
+********************************************************
+
+This ATL scenario transforms a UML2 Class Diagram into a UML2 Profile.
+
+Transformation files:
+---------------------
+- UML2Copy.atl: ATL transformation (generated by Dennis Wagelaar) made a copy a UML model. This transformation is used by the UMLCD2UMLProfile transformation thanks to superimposition mechanism.
+- UMLCD2UMLProfile: This ATL file transforms a UML Class Diagram into a UML Profile.
+
+Metamodel:
+----------
+ All the models conform to UML2 metamodel. The UML2 metamodel version is: http://www.eclipse.org/uml2/2.1.0/UML.
+
+Sample file:
+-------------
+ - InputModel/Book.uml: This file is simple UML Class Diagram file and is used as input example by this transformation scenario.
+
+RM: This scenario can be executed with the Ant file "Transformations/build.xml" or with the ATL launch configuration "Transformations/UMLCD2UMLProfile.launch".
\ No newline at end of file
diff --git a/atlTransformations/UMLCD2UMLProfile/UMLClassDiagram_to_UMLProfile_v0.1.zip b/atlTransformations/UMLCD2UMLProfile/UMLClassDiagram_to_UMLProfile_v0.1.zip
new file mode 100644
index 0000000..b296497
--- /dev/null
+++ b/atlTransformations/UMLCD2UMLProfile/UMLClassDiagram_to_UMLProfile_v0.1.zip
Binary files differ
diff --git a/atlTransformations/UMLDI2SVG/UMLDI2SVG.zip b/atlTransformations/UMLDI2SVG/UMLDI2SVG.zip
new file mode 100644
index 0000000..55acd4a
--- /dev/null
+++ b/atlTransformations/UMLDI2SVG/UMLDI2SVG.zip
Binary files differ
diff --git "a/atlTransformations/UMLDI2SVG/UMLDI2SVG\1330.04\135.pdf" "b/atlTransformations/UMLDI2SVG/UMLDI2SVG\1330.04\135.pdf"
new file mode 100644
index 0000000..a3f8260
--- /dev/null
+++ "b/atlTransformations/UMLDI2SVG/UMLDI2SVG\1330.04\135.pdf"
Binary files differ
diff --git a/atlTransformations/WSDL2R2ML/README.txt b/atlTransformations/WSDL2R2ML/README.txt
new file mode 100644
index 0000000..02f8f29
--- /dev/null
+++ b/atlTransformations/WSDL2R2ML/README.txt
@@ -0,0 +1,49 @@
+********************************************************
+** Description: WSDL2R2ML ATL transformation scenario
+** Author: Marko Ribaric <marko.ribaric at gmail.com>
+** Date: July 24, 2007
+********************************************************
+
+This ATL scenario transforms WSDL (Web Services Definition Language) into R2ML (REWERSE I1 Markup Language). It is composed of the following transformations: XML2WSDL, WSDL2R2ML (see below), and an R2ML extractor that produces XML documents that conform to the R2ML syntax defined by REWERSE I1 group. (also there are transformations in the other direction: XML2R2ML. R2ML2WSDL and WSDL2XML) To find more details about this transformation scenario, please refer to [1].
+
+See also:
+ -- XSD metamodel from http://www.eclipse.org/xsd/
+ -- WSDL metamodel (by prof Gerd Wagner, Institute of Informatics, Brandenburg Technical University at Cottbus, Germany)
+ -- R2ML (REWERSE I1 Rule Markup Language) - http://oxygen.informatik.tu-cottbus.de/rewerse-i1/?q=node/6
+
+Transformation files:
+---------------------
+- XML2WSDL.atl: ATL transformation that transforms an XML documents that conform to the WSDL syntax to an WSDL model. (also in the other direction WSDL2XML)
+
+ - WSDLR2ML.atl: The core transformation, that produced an R2ML model from
+ a WSDL model (instance of WSDL metamodel). (also in the other direction R2ML2WSDL)
+
+
+ - R2ML2XML.atl: ATL transformation that transforms an R2ML model into an
+ an XML model with R2ML syntax elements. (also in the other direction XML2R2ML). These transformations were originally developed by Milan Milanovic, and now they are extended with Reaction Rules.
+
+
+
+Metamodel files:
+----------------
+ - XML.xmi: XML metamodel in MOF XMI 1.2 format (MOF-1.4). This metamodel is part of standard metamodels used with ATL. It is used when models are tranformed into XML documents or vice versa.
+
+ - WSDL.xmi: WSDL metamodel in MOF XMI 1.2 format (MOF-1.4). This model represents an abstract syntax for the WSDL language. It also contains the XSD metamodel (http://www.eclipse.org/xsd/)
+
+ - R2ML.xmi: R2ML metamodel in MOF XMI 1.2 format (MOF-1.4). Metamodel of the R2ML language.
+
+ - Each metamodel has KM3 and Ecore EMF XMI 2.0 format versions.
+
+Sample files:
+-------------
+ - Models/wsdl-xml/hotelReservation.wsdl: This file is simple WSDL file and is used as input example by this transformation scenario.
+
+ - Models/r2ml-xml/R2MLRule.xml: This file is simple R2ML with Reaction Rules file and is used as input example by this transformation scenario.
+
+Other files:
+------------
+
+
+References:
+-----------
+[1] Lukichev, S., Guirca, A., Wagner, G., Gašević, D., Ribarić, M., “Rule-based Modeling of Web services,” International Journal on Data Management, 2007
diff --git a/atlTransformations/WSDL2R2ML/WSDL2R2ML.zip b/atlTransformations/WSDL2R2ML/WSDL2R2ML.zip
new file mode 100644
index 0000000..23467ee
--- /dev/null
+++ b/atlTransformations/WSDL2R2ML/WSDL2R2ML.zip
Binary files differ
diff --git a/atlTransformations/XSLT2XQuery/ExampleXSLT2XQuery.pdf b/atlTransformations/XSLT2XQuery/ExampleXSLT2XQuery.pdf
new file mode 100644
index 0000000..a5889ed
--- /dev/null
+++ b/atlTransformations/XSLT2XQuery/ExampleXSLT2XQuery.pdf
Binary files differ
diff --git "a/atlTransformations/XSLT2XQuery/ExampleXSLT2XQuery\133v00.01\135.pdf" "b/atlTransformations/XSLT2XQuery/ExampleXSLT2XQuery\133v00.01\135.pdf"
new file mode 100644
index 0000000..a5889ed
--- /dev/null
+++ "b/atlTransformations/XSLT2XQuery/ExampleXSLT2XQuery\133v00.01\135.pdf"
Binary files differ
diff --git a/atlTransformations/XSLT2XQuery/XSLT2XQuery.zip b/atlTransformations/XSLT2XQuery/XSLT2XQuery.zip
new file mode 100644
index 0000000..ff68f35
--- /dev/null
+++ b/atlTransformations/XSLT2XQuery/XSLT2XQuery.zip
Binary files differ
diff --git a/atlTransformations/atlTransformations.xml b/atlTransformations/atlTransformations.xml
new file mode 100644
index 0000000..4690649
--- /dev/null
+++ b/atlTransformations/atlTransformations.xml
@@ -0,0 +1,1558 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<atlTransformations>
+ <atlTransformation>
+ <shortName>Ant2Maven</shortName>
+ <name>Ant to Maven</name>
+ <docLink>Ant2Maven/ExampleAnt2Maven[v00.01].pdf</docLink>
+ <sourceLink>Ant2Maven/Ant2Maven.zip</sourceLink>
+ <description>
+ Ant is an open source build tool (a tool dedicated to the assembly of the different pieces of a program) from the Apache Software Foundation.
+ Ant is the most commonly used build tool for Java programs.
+ Maven is another build tool created by the Apache Software Foundation.
+ It is an extension of Ant because ant Tasks can be used in Maven.
+ The difference from Ant is that a project can be reusable.
+ This example describes a transformation from an Ant file to Maven files (project.xml and maven.xml).
+ </description>
+ <pubDate></pubDate>
+ </atlTransformation>
+ <atlTransformation>
+ <shortName>AssertionModification</shortName>
+ <name>AssertionModification</name>
+ <docLink>AssertionModification/AssertionModification.pdf</docLink>
+ <sourceLink>AssertionModification/AssertionModification.zip</sourceLink>
+ <description>
+ This example is extract from <a href="http://www.dcs.kcl.ac.uk/staff/kcl/tcat.pdf">Catalogue of Model Transformations by K. Lano</a>.
+ The purpose of this transformation is to weakening preconditions or strengthening postconditions.
+ This example was extracted by <a href="http://www.sciences.univ-nantes.fr/lina/atl/contrib/simon">Eric Simon</a>.
+ </description>
+ <pubDate></pubDate>
+ </atlTransformation>
+ <atlTransformation>
+ <shortName>ATL2BindingDebugger</shortName>
+ <name>ATL to BindingDebugger</name>
+ <docLink>ATL2BindingDebugger/README.txt</docLink>
+ <sourceLink>ATL2BindingDebugger/ATL2BindingDebugger.zip</sourceLink>
+ <description>
+ <p>
+ The ATL2BindingDebugger ATL transformation adds a debug instruction to each binding in an ATL transformation.
+ </p>
+ <p>
+ Source and target models conform to ATL metamodel.
+ A sample source model (sample-ATL-0.2.ecore) and its corresponding target model (Sample-ATL-0.2(Debug).ecore) are given.
+ </p>
+ </description>
+ <pubDate></pubDate>
+ </atlTransformation>
+ <atlTransformation>
+ <shortName>ATL2Problem</shortName>
+ <name>ATL to Problem</name>
+ <docLink>ATL2Problem/ExampleATL2Problem[v00.01].pdf</docLink>
+ <sourceLink>ATL2Problem/ATL2Problem.zip</sourceLink>
+ <description>
+ The ATL to Problem example describes a transformation from an ATL model into a Problem model.
+ The generated Problem model contains the list of non-structural errors (along with additional warnings) that have been detected within the input ATL model.
+ The transformation assumes the input ATL model is structurally correct, as those that have passed a syntactic analysis (for instance, a reference defined with cardinality [1-1] should not be undefined).
+ </description>
+ <pubDate></pubDate>
+ </atlTransformation>
+ <atlTransformation>
+ <shortName>ATL2Tracer</shortName>
+ <name>ATL to Tracer</name>
+ <docLink>ATL2Tracer/README.txt</docLink>
+ <sourceLink>ATL2Tracer/ATL2Tracer.zip</sourceLink>
+ <description>
+ <p>
+ The ATL2Tracer transformation shows how traceability generating code can be relatively easily added to
+ ATL code. It moreover shows that this process can be fully automated.
+ </p>
+ <p>
+ To find more details concerning dealing traceability in ATL, please refer to [1].
+ </p>
+ <p>
+ Source and target models conform to ATL metamodel.
+ A sample source model (sample-ATL-0.2.ecore in ATL2Tracer folder) and its corresponding target model (sample-ATL-0.2-Tracer.ecore in Tracertest/Input) are given.
+ </p>
+ <p>
+ References:
+ <ul>
+ <li>[1] Jouault, F : Loosely Coupled Traceability for ATL. In: Proceedings of the European Conference on Model Driven Architecture (ECMDA) workshop on traceability, Nuremberg, Germany.</li>
+ </ul>
+ </p>
+ </description>
+ <pubDate></pubDate>
+ </atlTransformation>
+ <atlTransformation>
+ <shortName>BibTeXML2DocBook</shortName>
+ <name>BibTeXML to DocBook</name>
+ <docLink>BibTeXML2DocBook/ExampleBibTeXML2DocBook[v00.01].pdf</docLink>
+ <sourceLink>BibTeXML2DocBook/BibTeXML2DocBook.zip</sourceLink>
+ <description>
+ The BibTeXML to DocBook example describes a transformation of a BibTeXML model to a DocBook
+ composed document. BibTeXML is an XML-based format for the BibTeX bibliographic tool.
+ DocBook, as for it, is an XML-based format for document composition.
+ </description>
+ <pubDate></pubDate>
+ </atlTransformation>
+ <atlTransformation>
+ <shortName>Book2Publication</shortName>
+ <name>Book to Publication</name>
+ <docLink>Book2Publication/ExampleBook2Publication[v00.02].pdf</docLink>
+ <sourceLink>Book2Publication/Book2Publication.zip</sourceLink>
+ <description>
+ The Book to Publication example describes a very simple transformation task. In the metamodel Book
+ the class Book contains an ordered set of Chapters. These Chapters hold the information of the
+ number of pages of Chapters. The metamodel Publication is simpler; its class Publication contains a
+ title and the total number of pages. For the transformation, all chapters of a Book have to be visited to
+ calculate the sum of all pages.
+ </description>
+ <pubDate></pubDate>
+ </atlTransformation>
+ <atlTransformation>
+ <shortName>CatalogueModelTransformations</shortName>
+ <name>CatalogueModelTransformations</name>
+ <docLink>CatalogueModelTransformations/CatalogueModelTransformations.pdf</docLink>
+ <sourceLink>CatalogueModelTransformations/CatalogueModelTransformations.zip</sourceLink>
+ <description>
+ All transformations have been extracted from the catalogue of models transformations: <a href="http://www.dcs.kcl.ac.uk/staff/kcl/tcat.pdf">http://www.dcs.kcl.ac.uk/staff/kcl/tcat.pdf</a>.
+ From this catalogue, the following ATL transformations have been created:
+ <ul>
+ <li>Assertion Modification</li>
+ <li>Disaggregation</li>
+ <li>Eliminate Redundant Inheritance</li>
+ <li>Equivalence of attributes and associations</li>
+ <li>Introduce Primary Key</li>
+ <li>Introducing an interface</li>
+ <li>Making partial role total</li>
+ <li>Merging Partial Classes</li>
+ <li>Raise Supplier Abstraction Level</li>
+ <li>Redundant Class Removable</li>
+ <li>Removing a Many Many Association</li>
+ <li>Removing An Association Class</li>
+ <li>Replace association by foreign key</li>
+ <li>Replace inheritance by association</li>
+ </ul>
+ They were extracted by <a href="http://www.sciences.univ-nantes.fr/lina/atl/contrib/simon">Eric Simon</a> and <a href="http://www.sciences.univ-nantes.fr/lina/atl/contrib/baudry">Julien Baudry</a>.
+ </description>
+ <pubDate></pubDate>
+ </atlTransformation>
+ <atlTransformation>
+ <shortName>Class2Relational</shortName>
+ <name>Class to Relational</name>
+ <docLink>Class2Relational/ExampleClass2Relational[v00.01].pdf</docLink>
+ <sourceLink>Class2Relational/Class2Relational.zip</sourceLink>
+ <description>
+ The Class to Relational example describes the simplified transformation of a class schema model to a
+ relational database model.
+ </description>
+ <pubDate></pubDate>
+ </atlTransformation>
+ <atlTransformation>
+ <shortName>CodeCloneTools2SVG</shortName>
+ <name>Code Clone Tools to SVG</name>
+ <docLink>CodeCloneTools2SVG/CodeCloneTools2SVG.pdf</docLink>
+ <sourceLink>CodeCloneTools2SVG/VisualRepCodeClone.zip</sourceLink>
+ <description>
+ This example describes a transformation from the text result generated by code clone detection tools
+ into SVG code in order to realize an uniform representation for different code clone analysis result.
+ At first, specific DSLs for different code clone tools (Simian, simScan, CloneDr) are defined. Then these
+ models can be transformed to a generic DSL for Code Clone. Then, the generic model will be transformed to
+ SVG model. Finally, SVG code can be extracted from the SVG model.
+ </description>
+ <pubDate></pubDate>
+ </atlTransformation>
+ <atlTransformation>
+ <shortName>CPL2SPL</shortName>
+ <name>CPL to SPL</name>
+ <docLink>CPL2SPL/README.txt</docLink>
+ <sourceLink>CPL2SPL/CPL2SPL.zip</sourceLink>
+ <description>
+ This example handles several aspects of two telephony DSLs: SPL and CPL.
+ </description>
+ <pubDate></pubDate>
+ </atlTransformation>
+ <atlTransformation>
+ <shortName>Disaggregation</shortName>
+ <name>Disaggregation</name>
+ <docLink>Disaggregation/Disaggregation.pdf</docLink>
+ <sourceLink>Disaggregation/Disaggregation.zip</sourceLink>
+ <description>
+ This example is extract from <a href="http://www.dcs.kcl.ac.uk/staff/kcl/tcat.pdf">Catalogue of Model Transformations by K. Lano</a>.
+ The purpose of this example is the following: "A class may become large and unmanageable, with several loosely connected functionalities. It should be split into several classes, such as a master/controller class and helper classes, which have more coherent functionalities and data."
+ This example was extracted by <a href="http://www.sciences.univ-nantes.fr/lina/atl/contrib/simon">Eric Simon</a>.
+ </description>
+ <pubDate></pubDate>
+ </atlTransformation>
+ <atlTransformation>
+ <shortName>DSL2EMF</shortName>
+ <name>DSL to EMF</name>
+ <docLink>DSL2EMF/ExampleDSL2EMF[v00.01].pdf</docLink>
+ <sourceLink>DSL2EMF/DSLBridge.zip</sourceLink>
+ <description>
+ This example provides you a complete overview of a transformation chain example between two technical spaces: Microsoft DSL (Domain Specific Languages) Tools and EMF (Eclipse Modeling Framework).
+ The aim of this example is to demonstrate the possibility to exchange models defined under different technologies.
+ In particular, the described bridges demonstrate that it should be possible to define metamodels and models using both Microsoft DSL Tools and Eclipse EMF technologies.
+ The bridge between MS/DSL and EMF spans two levels: the metamodel and model levels.
+ At the level of metamodels, it allows to transform MS/DSL domain models to EMF metamodels.
+ At the level of models, the bridge allows transforming MS/DSL models conforming to domain models to EMF models conforming to EMF metamodels.
+ At both levels, the bridge operates in both directions.
+ A chain of ATL-based transformations is used to implement the bridge at these two levels.
+ The benefit of using such a bridge is the ability to transpose MS/DSL work in EMF platform, and inversely.
+ </description>
+ <pubDate></pubDate>
+ </atlTransformation>
+ <atlTransformation>
+ <shortName>EliminateRedundantInheritance</shortName>
+ <name>EliminateRedundantInheritance</name>
+ <docLink>EliminateRedundantInheritance/EliminateRedundantInheritance.pdf</docLink>
+ <sourceLink>EliminateRedundantInheritance/EliminateRedundantInheritance.zip</sourceLink>
+ <description>
+ This example is extract from <a href="http://www.dcs.kcl.ac.uk/staff/kcl/tcat.pdf">Catalogue of Model Transformations by K. Lano</a>.
+ "A redundant inheritance conveys no extra information, but complicates the model. The previous figure shows a typical situation where class A directly inherits from class C, and also indirectly via a more specific class B. The first inheritance is redundant and can be removed. (In some languages, such as Java, such inheritances would actually be invalid)."
+ This example was extracted by <a href="http://www.sciences.univ-nantes.fr/lina/atl/contrib/baudry">Julien Baudry</a>.
+ </description>
+ <pubDate></pubDate>
+ </atlTransformation>
+ <atlTransformation>
+ <shortName>EMF2KM3</shortName>
+ <name>EMF2KM3 (Ecore to KM3)</name>
+ <docLink>EMF2KM3/README.txt</docLink>
+ <sourceLink>EMF2KM3/EMF2KM3.zip</sourceLink>
+ <description>
+ <p>
+ The KM3 plugin implements several transformations, including the generation of a KM3 model from an
+ Ecore metamodel: EMF2KM3. This distribution provides source code for the EMF2KM3 transformation
+ available in the KM3 plugin as of December 12th, 2005.
+ </p>
+ <p>
+ EMF2KM3 is usually used through the KM3 plugin, as the "Extract Ecore metamodel to KM3" action available
+ on *.ecore files. Some users may however want to customize this transformation.
+ Here is the procedure to replace the standard transformation with a custom one:
+ <ul>
+ <li>modify EMF2KM3.atl to support desired features,</li>
+ <li>compile it into EMF2KM3.asm (this is normally automatically performed by the ATL builder),</li>
+ <li>copy EMF2KM3.asm into org.atl.eclipse.km3 / src / org / atl / eclipse / km3 / resources,</li>
+ <li>restart Eclipse.</li>
+ </p>
+ </description>
+ <pubDate></pubDate>
+ </atlTransformation>
+ <atlTransformation>
+ <shortName>EquivalenceAttributesAssociations</shortName>
+ <name>EquivalenceAttributesAssociations</name>
+ <docLink>EquivalenceAttributesAssociations/EquivalenceAttributesAssociations.pdf</docLink>
+ <sourceLink>EquivalenceAttributesAssociations/EquivalenceAttributesAssociations.zip</sourceLink>
+ <description>
+ This example is extract from <a href="http://www.dcs.kcl.ac.uk/staff/kcl/tcat.pdf">Catalogue of Model Transformations by K. Lano</a>.
+ Qualified association cannot be represented as attributes, as there is no corresponding attribute notation, i.e., for specifying map data structures. In addition the multiplicity at the owning entity end of an association cannot be generally expressed in the attribute version. For an ordinary attribute this multiplicity is * and for an identity attribute (primary key) it is 0..1.
+ This example was extracted by <a href="http://www.sciences.univ-nantes.fr/lina/atl/contrib/baudry">Julien Baudry</a>.
+ </description>
+ <pubDate></pubDate>
+ </atlTransformation>
+ <atlTransformation>
+ <shortName>Families2Persons</shortName>
+ <name>Families to Persons</name>
+ <docLink>http://www.eclipse.org/atl/documentation/old/ATLUseCase_Families2Persons.pdf</docLink>
+ <sourceLink>Families2Persons/Families2Persons.zip</sourceLink>
+ <description>
+ This is the source code of the ATL Use Case: "Families to Persons".
+ This use case describes a very simple model transformation example, some kind of ATL "hello world".
+ </description>
+ <pubDate></pubDate>
+ </atlTransformation>
+ <atlTransformation>
+ <shortName>FM2BPMN</shortName>
+ <name>Feature Models for representing runtime variability in BIS to Business Process Model Notation</name>
+ <docLink>http://www.isa.us.es/uploads/tools/fm2bpmn/doc/draft.pdf</docLink>
+ <sourceLink>http://www.isa.us.es/uploads/tools/fm2bpmn/transformations/top-down/full/fm2bpmn.atl</sourceLink>
+ <description>
+ The FM to BPMN example describes a transformation from a feature model for representing runtime variability in business information systems created using FAMA (FeAture Model Analyzer) into a business process model diagram represented by means of BPMN metamodel provided by the Eclipse STP (SOA Tool Platform) project.
+ </description>
+ <pubDate/>
+ </atlTransformation>
+ <atlTransformation>
+ <shortName>GeometricalTransformations</shortName>
+ <name>Geometrical Transformations</name>
+ <docLink>GeometricalTransformations/ExampleGeometricalTransformations[v00.02].pdf</docLink>
+ <sourceLink>GeometricalTransformations/Geometry.zip</sourceLink>
+ <description>
+ This document illustrates an advanced ATL program in the area of geometrical transformations.
+ This transformation example describes geometrical transformations. Input of the transformation are
+ geometrical operations (rotate, move, explode) and geometrical data (based on a simplified DXF
+ metamodel). The output of the transformation is the geometrical data (based on the same simplified
+ DXF metamodel) that has been transformed according to the geometrical operations.
+ DXF<sup>TM</sup>, Drawing eXchange Format, is the native vector file format of Autodesk's AutoCAD CAD
+ application. DXF features include support for 3D objects, curves, text and associative dimensioning.
+ Particularity of the transformations is that it has two input metamodels and that one of the input
+ metamodels is the same as the output metamodel.
+ </description>
+ <pubDate></pubDate>
+ </atlTransformation>
+ <atlTransformation>
+ <shortName>Grafcet2PetriNet</shortName>
+ <name>Grafcet to PetriNet</name>
+ <docLink>Grafcet2PetriNet/ExampleGrafcet2PetriNet[v00.01].pdf</docLink>
+ <sourceLink>Grafcet2PetriNet/Grafcet2PetriNet.zip</sourceLink>
+ <description>
+ This ATL example describes bridges between Grafcet, Petri net, PNML, and XML.
+ This example provides an overview of the whole transformation sequence that enables to produce an XML Petri net representation (in the PNML format) from a textual definition of a grafcet.
+ It also describes the reverse transformation sequence that enables to build a textual grafcet representation from an XML definition of a PNML document.
+ </description>
+ <pubDate></pubDate>
+ </atlTransformation>
+ <atlTransformation>
+ <shortName>IEEE1471_2_MoDAF</shortName>
+ <name>IEEE1471 to MoDAF</name>
+ <docLink>IEEE1471_2_MoDAF/IEEE1471_2_MoDAF.doc</docLink>
+ <sourceLink>IEEE1471_2_MoDAF/IEEE1471_2_MoDAF.zip</sourceLink>
+ <description>
+ This ATL example realizes the transformation between IEEE1471-2000 and MoDAF-AV.
+ The IEEE1471 committee precises a recommended practice for the design and the analysis of Architecture of Software Intensive Systems.
+ It fixes a terminolgy for System, Architecture, Architectural Description, Stakeholder, Concerns, View ,and Viewpoints concepts.
+ MoDAF (Ministry of Defense Architecture Framework) is based on the DoDAF (Departement of Defense Architecture Framework).
+ DoDAF is a framework to design C4ISR systems. MoDAF-AV (Architecture View) used several concepts defined in the IEEE1471.
+ IEEE1471 to MoDAF was produced by <a href="http://www.sciences.univ-nantes.fr/lina/atl/contrib/jossic">Albin Jossic</a>.<br />
+ </description>
+ <pubDate></pubDate>
+ </atlTransformation>
+ <atlTransformation>
+ <shortName>IntroducePrimaryKey</shortName>
+ <name>IntroducePrimaryKey</name>
+ <docLink>IntroducePrimaryKey/IntroducePrimaryKey.pdf</docLink>
+ <sourceLink>IntroducePrimaryKey/IntroducePrimaryKey.zip</sourceLink>
+ <description>
+ This example is extract from <a href="http://www.dcs.kcl.ac.uk/staff/kcl/tcat.pdf">Catalogue of Model Transformations by K. Lano</a>.
+ This is an essential step for implementation of a data model in relational database.
+ This example was extracted by <a href="http://www.sciences.univ-nantes.fr/lina/atl/contrib/baudry">Julien Baudry</a>.
+ </description>
+ <pubDate></pubDate>
+ </atlTransformation>
+ <atlTransformation>
+ <shortName>IntroducingInterface</shortName>
+ <name>IntroducingInterface</name>
+ <docLink>IntroducingInterface/IntroducingInterface.pdf</docLink>
+ <sourceLink>IntroducingInterface/IntroducingInterface.zip</sourceLink>
+ <description>
+ This example is extract from <a href="http://www.dcs.kcl.ac.uk/staff/kcl/tcat.pdf">Catalogue of Model Transformations by K. Lano</a>.
+ This reduces the dependencies in the model and enables separate development of A and B, and permits them to be placed in different layers or tiers of the system.
+ This example was extracted by <a href="http://www.sciences.univ-nantes.fr/lina/atl/contrib/baudry">Julien Baudry</a>.
+ </description>
+ <pubDate></pubDate>
+ </atlTransformation>
+ <atlTransformation>
+ <shortName>Java2Table</shortName>
+ <name>Java source to Table</name>
+ <docLink>Java2Table/ExampleJavaSource2Table[v00.01].pdf</docLink>
+ <sourceLink>Java2Table/Java2Table.zip</sourceLink>
+ <description>
+ The JavaSource to Table example describes a transformation from a Java source code to a table
+ which summarizes how many times each method declared in the Java source code is called within the
+ definition of any declared method. A XML-based format, inspired from the JavaML, has been
+ developed to encode all interesting information available in the Java source code. We use, for this
+ transformation, a very basic abstract Table model which may be easily mapped to existing table
+ representations (XHTML, ExcelML, etc.).
+ </description>
+ <pubDate></pubDate>
+ </atlTransformation>
+ <atlTransformation>
+ <shortName>KM32ATLCopier</shortName>
+ <name>KM3 to ATL Copier</name>
+ <docLink>KM32ATLCopier/README.txt</docLink>
+ <sourceLink>KM32ATLCopier/KM32ATLCopier.zip</sourceLink>
+ <description>
+ The KM32ATLCopier transformation creates a transformation of copy for a KM3 model.
+ Source model conforms to KM3 metamodel and target model conforms to ATL metamodel.
+ A sample source model (sample-KM3.ecore) and its corresponding target model (ATLCopier.ecore) are given.
+ </description>
+ <pubDate></pubDate>
+ </atlTransformation>
+ <atlTransformation>
+ <shortName>KM32CONFATL</shortName>
+ <name>KM3 to ATL conformance checking transformation</name>
+ <docLink>http://www.st.ewi.tudelft.nl/~basgraaf/software/mde/atl/KM32CONFATL/README.txt</docLink>
+ <sourceLink>http://www.st.ewi.tudelft.nl/~basgraaf/software/mde/atl/KM32CONFATL/KM32CONFATL.zip</sourceLink>
+ <description>
+ This package includes a higher-order transformation (HOT) that, based on a metamodel (i.e., an injected KM3 model),
+ generates a transformation that checks the consistency of two source models that conform to that metamodel. The
+ target model of the (generated) transformation effectively is the union of the two source models with its elements
+ and relations labelled as convergent, divergent, or absent according to their occurrence in one or both of the source
+ models. The HOT provides a means to generically check to conformance of models associated with simple metamodels.
+ </description>
+ <pubDate></pubDate>
+ </atlTransformation>
+ <atlTransformation>
+ <shortName>KM32DOT</shortName>
+ <name>KM3 to DOT</name>
+ <docLink>KM32DOT/ExampleKM32DOT[v00.01].pdf</docLink>
+ <sourceLink>KM32DOT/KM32DOT.zip</sourceLink>
+ <description>
+ The KM3 to DOT example describes a transformation from a KM3 metamodel description into a class
+ diagram drawn with DOT. KM3 is a textual concrete syntax to describe metamodels. It has its advantages,
+ yet having a graphical presentation of a metamodel can be sometimes enlightening. DOT is an automatic
+ graph layout program from Graphviz. It can be used to create graphical files, such as PS, PNG... out of
+ its layout. The aim of this transformation is to generate a rough visualization, in the form of a class
+ diagram, of a KM3 model. A metamodel created with KM3 does not include any representation information,
+ so DOT, the Graphviz tool, is used to compute the layout and generate the output picture.
+ </description>
+ <pubDate></pubDate>
+ </atlTransformation>
+ <atlTransformation>
+ <shortName>KM32EMF</shortName>
+ <name>KM32EMF (KM3 to Ecore)</name>
+ <docLink>KM32EMF/README.txt</docLink>
+ <sourceLink>KM32EMF/KM32EMF.zip</sourceLink>
+ <description>
+ <p>
+ The KM3 plugin implements several transformations, including the generation of an Ecore metamodel
+ from a KM3 model: KM32EMF.
+ This distribution provides source code for the KM32EMF transformation
+ available in the KM3 plugin as of May 24th, 2006.
+ </p>
+ <p>
+ KM32EMF is usually used through the KM3 plugin, as the "Inject KM3 to Ecore metamodel" action available
+ on *.km3 files. Some users may however want to customize this transformation.
+ Here is the procedure to replace the standard transformation with a custom one:
+ <ul>
+ <li>modify KM32EMF.atl to support desired features,</li>
+ <li>compile it into KM32EMF.asm (this is normally automatically performed by the ATL builder),</li>
+ <li>copy KM32EMF.asm into org.atl.eclipse.km3 / src / org / atl / eclipse / km3 / resources,</li>
+ <li>restart Eclipse.</li>
+ </ul>
+ </p>
+ </description>
+ <pubDate></pubDate>
+ </atlTransformation>
+ <atlTransformation>
+ <shortName>KM32Measure</shortName>
+ <name>KM3 to Measure</name>
+ <docLink>KM32Measure/ExampleKM32Measure[v00.02].pdf</docLink>
+ <sourceLink>KM32Measure/KM32Measure.zip</sourceLink>
+ <description>
+ The KM3 to Measure example describes measurement on KM3 metamodels, using metrics defined as ATL libraries.
+ This scenario is an updated version of the scenario <a href="KM32Metrics">KM32Metrics</a>. It is contributed
+ by Eric Vépa (<a href="http://www.sodius.com">SODIUS</a>).
+ </description>
+ <pubDate></pubDate>
+ </atlTransformation>
+ <atlTransformation>
+ <shortName>KM32Metrics</shortName>
+ <name>KM3 to Metrics</name>
+ <docLink>KM32Metrics/ExampleKM32Metrics[v00.01].pdf</docLink>
+ <sourceLink>KM32Metrics/KM32Metrics.zip</sourceLink>
+ <description>
+ Due to the even growing complexity of metamodels, the establishment of metamodel metrics now requires the use of dedicated tools.
+ This ATL transformation example aims to show how the ATL language may be used to meet this objective by generating metrics models from metamodels.
+ The Kernel MetaMetaModel (KM3) is a simple textual notation enabling quick definition of metamodels.
+ The KM3 to Metrics ATL example aims to demonstrate the feasibility of computing some metamodel metrics by means of the ATL language.
+ For this purpose, we have developed a basic Metrics metamodel enabling to encode measures of different types.
+ The KM3 to Metrics ATL transformation defines different metamodel metrics that are relative either to the whole model, or to specific model elements.
+ The metrics provided in the scope of this transformation include simple measurements as well as more complex computations.
+ </description>
+ <pubDate></pubDate>
+ </atlTransformation>
+ <atlTransformation>
+ <shortName>KM32OWL</shortName>
+ <name>KM3 to OWL</name>
+ <docLink>KM32OWL/README.txt</docLink>
+ <sourceLink>KM32OWL/KM32OWL.zip</sourceLink>
+ <description>
+ This ATL scenario shows up a traduction of KM3 into OWL (Web Ontology language) ontology language. This scenario is composed
+ of one transformation (KM32OWL) and an OWL extractor that produces XML documents conform to the OWL syntax
+ defined by the W3C. Resulting ontology can be used into ontology development tools like Protege
+ <a href="http://protege.stanford.edu">(see http://protege.stanford.edu)</a>.
+ </description>
+ <pubDate></pubDate>
+ </atlTransformation>
+ <atlTransformation>
+ <shortName>KM32Problem</shortName>
+ <name>KM3 to Problem</name>
+ <docLink>KM32Problem/ExampleKM32Problem[v00.01].pdf</docLink>
+ <sourceLink>KM32Problem/KM32Problem.zip</sourceLink>
+ <description>
+ The KM3 to Problem example describes a transformation from a KM3 metamodel into a Problem model.
+ The generated Problem model contains the list of non-structural errors (along with additional warnings) that have been detected within the input KM3 metamodel.
+ The transformation assumes the input KM3 metamodel is structurally correct, as those that have passed a syntactic analysis (for instance, a reference defined with cardinality [1-1] should not be undefined).
+ It may therefore fails when executed on a KM3 metamodel produced from a MOF metamodel that has not been checked.
+ </description>
+ <pubDate></pubDate>
+ </atlTransformation>
+ <atlTransformation>
+ <shortName>KM32XML</shortName>
+ <name>KM3 to XML</name>
+ <docLink>KM32XML/readme.txt</docLink>
+ <sourceLink>KM32XML/KM32XML.zip</sourceLink>
+ <description>
+ The KM3 to XML scenario expresses each metamodel written in KM3 textual syntax with a default XML syntax.
+ As a default syntax, it is not the more concise but it is non-ambiguous and can be apply to any KM3 model.
+ </description>
+ <pubDate></pubDate>
+ </atlTransformation>
+ <atlTransformation>
+ <shortName>KMLInjector</shortName>
+ <name>KML Injector</name>
+ <docLink>KMLInjector/ExampleKMLInjector[v00.01].pdf</docLink>
+ <sourceLink>KMLInjector/KMLInjector.zip</sourceLink>
+ <description>
+ The KMLInjector example describes a transformation from a KML file to a KML model.
+ KML, or Keyhole Markup Language, is an XML grammar and file format for modeling and storing geographic features such as points, lines, images, and polygons for display in Google Earth.
+ </description>
+ <pubDate></pubDate>
+ </atlTransformation>
+ <atlTransformation>
+ <shortName>ListMetamodelRefactoring</shortName>
+ <name>List Metamodel Refactoring</name>
+ <docLink>http://www.eclipse.org/atl/documentation/basicExamples_Patterns/article.php?file=ListMetamodelRefactoring/index.html</docLink>
+ <sourceLink>ListMetamodelRefactoring/ListMetamodelRefactoring.zip</sourceLink>
+ <description>
+ In this example, we present some basic concepts of ATL through a simple use case. Our working context is to create a bridge between
+ two different versions of a List metamodel (A and B versions). This bridge consists on an ATL transformation from the metamodel A to the metamodel B.
+ </description>
+ <pubDate></pubDate>
+ </atlTransformation>
+ <atlTransformation>
+ <shortName>Make2Ant</shortName>
+ <name>Make to Ant</name>
+ <docLink>Make2Ant/ExampleMake2Ant[v00.01].pdf</docLink>
+ <sourceLink>Make2Ant/Make2Ant.zip</sourceLink>
+ <description>
+ Ant is an open source build tool (a tool dedicated to the assembly of the different pieces of a program) from the Apache Software Foundation.
+ Ant is the most commonly used build tool for Java programs.
+ Unlike many other build tools, Ant is independent of both the platform and the development environments.
+ Make (the most common build tool) is based on a particular shell or command interface and is therefore limited to the type of operating systems that use that shell.
+ Ant uses Java classes rather than shell-based commands.
+ Developers use XML to describe the modules in their program build.
+ This example describes a transformation from a Makefile to an Ant file.
+ </description>
+ <pubDate></pubDate>
+ </atlTransformation>
+ <atlTransformation>
+ <shortName>MakePartialRoleTotal</shortName>
+ <name>MakePartialRoleTotal</name>
+ <sourceLink>MakePartialRoleTotal/MakePartialRoleTotal.zip</sourceLink>
+ <docLink>MakePartialRoleTotal/MakingPartialRoleTotal(a).pdf</docLink>
+ <docLink>MakePartialRoleTotal/MakingPartialRoleTotal(b).pdf</docLink>
+ <description>
+ This example is extract from <a href="http://www.dcs.kcl.ac.uk/staff/kcl/tcat.pdf">Catalogue of Model Transformations by K. Lano</a>.
+ Total associations are generally easier to implement and manage than partial associations.
+ This example was extracted by <a href="http://www.sciences.univ-nantes.fr/lina/atl/contrib/baudry">Julien Baudry</a>.
+ </description>
+ <pubDate></pubDate>
+ </atlTransformation>
+ <atlTransformation>
+ <shortName>Maven2Ant</shortName>
+ <name>Maven to Ant</name>
+ <docLink>Maven2Ant/ExampleMaven2Ant[v00.01].pdf</docLink>
+ <sourceLink>Maven2Ant/Maven2Ant.zip</sourceLink>
+ <description>
+ Ant is an open source build tool (a tool dedicated to the assembly of the different pieces of a program) from the Apache Software Foundation.
+ Ant is the most commonly used build tool for Java programs.
+ Maven is another build tool created by the Apache Software Foundation.
+ It is an extension of Ant because ant Tasks can be used in Maven.
+ The difference from Ant is that a project can be reusable.
+ This document describes a transformation from a Maven files (project.xml and maven.xml) to an Ant file.
+ </description>
+ <pubDate></pubDate>
+ </atlTransformation>
+ <atlTransformation>
+ <shortName>Measure2Table</shortName>
+ <name>Measure to Table</name>
+ <docLink>Measure2Table/ExampleMeasure2Table[v00.01].pdf</docLink>
+ <sourceLink>Measure2Table/Measure2Table.zip</sourceLink>
+ <description>
+ The Measure2Table project is used to creates generic tables from a measure model.
+ This scenario is used by the scenario <a href="ModelMeasurement">Model Measurement</a>.
+ It is contributed by Eric Vépa (<a href="http://www.sodius.com">SODIUS</a>).
+ </description>
+ <pubDate></pubDate>
+ </atlTransformation>
+ <atlTransformation>
+ <shortName>Measure2XHTML</shortName>
+ <name>Measure to XHTML</name>
+ <docLink>Measure2XHTML/ExampleMeasure2XHTML[v00.01].pdf</docLink>
+ <sourceLink>Measure2XHTML/Measure2XHTML.zip</sourceLink>
+ <description>
+ The Measure to XHTML example describes a transformation from a Measure model to a XHTML file representing the measurement data.
+ This scenario is used by the scenario <a href="ModelMeasurement">Model Measurement</a>.
+ It is contributed by Eric Vépa (<a href="http://www.sodius.com">SODIUS</a>).
+ </description>
+ <pubDate></pubDate>
+ </atlTransformation>
+ <atlTransformation>
+ <shortName>MeasuringModelRepositories</shortName>
+ <name>Measuring Model Repositories</name>
+ <docLink>MeasuringModelRepositories/ExampleMeasuringModelRepositories[v00.01].pdf</docLink>
+ <sourceLink>MeasuringModelRepositories/MeasuringModelRepositories.zip</sourceLink>
+ <description>
+ The Measuring Model Repositories example generates some measures (graph and table format) on input KM3 models.
+ This example describes three transformations from a KM3 model to a Measure model, from a Measure model to a Measure model and from a Measure model to
+ a Table model. Finally, graphical outputs are generated (SVG and HTML).
+ </description>
+ <pubDate></pubDate>
+ </atlTransformation>
+ <atlTransformation>
+ <shortName>MergingPartialClasses</shortName>
+ <name>MergingPartialClasses</name>
+ <docLink>MergingPartialClasses/MergingPartialClasses.pdf</docLink>
+ <sourceLink>MergingPartialClasses/MergingPartialClasses.zip</sourceLink>
+ <description>
+ This example is extract from <a href="http://www.dcs.kcl.ac.uk/staff/kcl/tcat.pdf">Catalogue of Model Transformations by K. Lano</a>.
+ The purpose of this transformation is to merge the class link by a association one-one.
+ This example was extracted by <a href="http://www.sciences.univ-nantes.fr/lina/atl/contrib/simon">Eric Simon</a>.
+ </description>
+ <pubDate></pubDate>
+ </atlTransformation>
+ <atlTransformation>
+ <shortName>METAH2ACME</shortName>
+ <name>MetaH to ACME</name>
+ <docLink>METAH2ACME/METAH2ACME.pdf</docLink>
+ <sourceLink>METAH2ACME/METAH2ACME.zip</sourceLink>
+ <description>
+ The MetaH to ACME example describes a transformation from a MetaH format to ACME format.
+ The ACME interchange format was originally conceived as a way to share tool capabilities rovided by a particular ADL with other ADLs, while avoiding the production of many pair wise language translators.
+ The MetaH architectural description language (ADL) and associated toolset support architectural modeling of embedded real-time system applications.
+ MetaH to ACME was produced by <a href="http://www.sciences.univ-nantes.fr/lina/atl/contrib/baudry">Julien Baudry</a>.<br />
+ </description>
+ <pubDate></pubDate>
+ </atlTransformation>
+ <atlTransformation>
+ <shortName>MDL2GMF</shortName>
+ <name>MDL to GMF</name>
+ <docLink>http://www.eclipse.org/atl/usecases/MDL2GMF/</docLink>
+ <sourceLink>MDL2GMF/org.eclipse.m2m.atl.mdl2gmf.zip</sourceLink>
+ <description>
+ This use case shows how we can reuse UML projects created with Rational Rose and import them in GMF (specifically in UML2 Tools) using ATL transformations.
+ </description>
+ <pubDate></pubDate>
+ </atlTransformation>
+ <atlTransformation>
+ <shortName>ModelMeasurement</shortName>
+ <name>Models Measurement</name>
+ <docLink>http://www.eclipse.org/atl/usecases/ModelsMeasurement/</docLink>
+ <sourceLink>ModelMeasurement/ModelsMeasurement.zip</sourceLink>
+ <description>
+ The ModelsMeasurement project is used to collect measurement data on KM3 metamodels or UML2 models, using
+ libraries implementing some metrics (MOOD, MOOD2, MOOSE, EMOOSE and QMOOD).
+ The measure level can be changed by setting an other value for the first helper measureLevel of the
+ transformation KM32Measure or UML22Measure.
+ This scenario is contributed by Eric Vépa (<a href="http://www.sodius.com">SODIUS</a>).
+ </description>
+ <pubDate></pubDate>
+ </atlTransformation>
+ <atlTransformation>
+ <shortName>MOF2UML</shortName>
+ <name>MOF to UML</name>
+ <docLink>MOF2UML/ExampleMOF2UML[v00.01].pdf</docLink>
+ <sourceLink>MOF2UML/UML2MOF.zip</sourceLink>
+ <description>
+ The MOF (Meta Object Facility) is an OMG standard enabling to describe metamodels through common semantics. The UML (Unified Modelling
+ Language) Core standard is the OMG common modelling language. Although, the MOF is primarily designed for metamodel definitions and UML
+ Core for the design of models, the two standards handle very close notions. This example describes a transformation enabling to pass from
+ the MOF to the UML semantics. The transformation is based on the UML Profile for MOF OMG specification.
+ </description>
+ <pubDate></pubDate>
+ </atlTransformation>
+ <atlTransformation>
+ <shortName>Monitor2Semaphore</shortName>
+ <name>Monitor to Semaphore</name>
+ <docLink>Monitor2Semaphore/ExampleMonitor2Semaphore[v00.01].pdf</docLink>
+ <sourceLink>Monitor2Semaphore/Monitor2Semaphore.zip</sourceLink>
+ <description>
+ The Monitor to Semaphore example describes a transformation from a program containing Hoares
+ monitors definitions into an equivalent program in which synchronization operations are based on
+ Dijkstras semaphores. This is an example of end-to-end transformation, from code to code. It
+ strictly follows the operational semantic of monitors described in terms of semaphores and shows how
+ this abstract description may be implemented into an executable ATL transformation.
+ </description>
+ <pubDate></pubDate>
+ </atlTransformation>
+ <atlTransformation>
+ <shortName>MSOfficeExcelExtractor</shortName>
+ <name>Microsoft Office Excel Extractor</name>
+ <docLink>MSOfficeExcelExtractor/ExampleMicrosoftOfficeExcelExtractor[v00.01].pdf</docLink>
+ <sourceLink>MSOfficeExcelExtractor/MicrosoftOfficeExcelExtractor.zip</sourceLink>
+ <description>
+ The Microsoft Office Excel extractor's example describes a transformation from an Excel model to an Excel workbook. The transformation is
+ based on a simplified subset of the SpreadsheetML XML dialect which is the one used by Microsoft to import/export Excel workbook's data in
+ XML since the 2003 version of Microsoft Office. This transformation produces an Excel XML file which can be directly opened by Microsoft
+ Excel 2003. This file describes a workbook with the same content that the one of the input Excel model.
+ </description>
+ <pubDate></pubDate>
+ </atlTransformation>
+ <atlTransformation>
+ <shortName>MSOfficeExcelInjector</shortName>
+ <name>Microsoft Office Excel Injector</name>
+ <docLink>MSOfficeExcelInjector/ExampleMicrosoftOfficeExcelInjector[v00.01].pdf</docLink>
+ <sourceLink>MSOfficeExcelInjector/MicrosoftOfficeExcelInjector.zip</sourceLink>
+ <description>
+ The Microsoft Office Excel injector's example describes a transformation from an Excel workbook to an Excel model. The transformation is
+ based on a simplified subset of the SpreadsheetML XML dialect which is the one used by Microsoft to import/export Excel workbook's data
+ in XML since the 2003 version of Microsoft Office. This transformation produces an Excel model from an Excel XML file which can be
+ directly opened by Excel 2003. This Excel model describes a workbook with the same content that the one stored into the input Excel XML
+ file.
+ </description>
+ <pubDate></pubDate>
+ </atlTransformation>
+ <atlTransformation>
+ <shortName>MSOfficeExcel2SoftwareQualityControl</shortName>
+ <name>Microsoft Office Excel to Software Quality Control</name>
+ <docLink>MSOfficeExcel2SoftwareQualityControl/ExampleMicrosoftOfficeExcel2SoftwareQualityControl[v00.01].pdf</docLink>
+ <sourceLink>MSOfficeExcel2SoftwareQualityControl/MicrosoftOfficeExcel2SoftwareQualityControl.zip</sourceLink>
+ <description>
+ The "Microsoft Office Excel to Software Quality Control" example describes a transformation from an Excel workbook containing information
+ about quality controls of a software product to a model storing the same data in a more general and abstract structure. The transformation is
+ based on a simplified subset of the SpreadsheetML XML dialect which is the one used by Microsoft to import/export Excel workbook's data in XML
+ since the 2003 version of Microsoft Office. It is also based on a Software Quality Control metamodel which describes a simple structure to
+ manage software quality controls (for example bug-tracking). The input of the transformation is an Excel XML file, containing the description
+ of the Excel workbook, which can be directly opened by Excel 2003. The output is a model which conforms to the SoftwareQualityControl
+ metamodel.
+ </description>
+ <pubDate></pubDate>
+ </atlTransformation>
+ <atlTransformation>
+ <shortName>MySQL2KM3</shortName>
+ <name>MySQL to KM3</name>
+ <docLink>MySQL2KM3/ExampleMySQL2KM3[v00.01].pdf</docLink>
+ <sourceLink>MySQL2KM3/MySQL2KM3.zip</sourceLink>
+ <description>
+ The MySQL to KM3 transformation describes a transformation from the description of a relational database to metamodel semantics.
+ The example aims to demonstrate the possibility to translate data structure description from the RDBMS to the modelling technical space.
+ For this purpose, the popular open source MySQL RDBMS system has been considered as the database platform, and the KM3 notation as the metamodel description tool.
+ </description>
+ <pubDate></pubDate>
+ </atlTransformation>
+ <atlTransformation>
+ <shortName>OBL2UML</shortName>
+ <name>OpenBlueLab to UML</name>
+ <docLink>http://www.openbluelab.org/content/Bookmark.process@@docid=20070607144710186_315843775601&action=read&target=CommunityZone</docLink>
+ <sourceLink>http://forge.openbluelab.org/gf/project/omf/frs/</sourceLink>
+ <description>
+ <p>
+ <a href="http://www.openbluelab.org">OpenBlueLab</a> project's ambition is to provide an application which you can adapt easily by just updating UML models
+ contained in the <a href="http://www.openbluelab.org">OpenBlueLab</a> download, without writing any line of code. <a href="http://www.openbluelab.org">OpenBlueLab</a>
+ use as input XMI file but too OBL file conforms to our specialized metamodel used to generate a particular editor, <a href="http://forge.openbluelab.org/gf/project/omf/">OpenBlueLab Developer Studio</a>.
+ So we have made a transformation which permit to get XMI file conforms to the metamodel UML from OBL file if we want to re-integrate OBL models in UML modeler.
+ </p>
+ <p>This scenario is a contribution from Benjamin Chevallereau (<a href="http://www.openbluelab.org">OpenBlueLab</a>).</p>
+ </description>
+ <pubDate></pubDate>
+ </atlTransformation>
+ <atlTransformation>
+ <shortName>OCL2R2ML</shortName>
+ <name>OCL to R2ML</name>
+ <docLink>OCL2R2ML/README.txt</docLink>
+ <sourceLink>OCL2R2ML/OCL2R2ML.zip</sourceLink>
+ <description>
+ <p align="justify">
+ The OCL to R2ML transformation scenario describes a transformation from OCL (Object Constraint Language) metamodel (with EMOF metamodel) into a R2ML (REWERSE I1 Rule Markup
+ Language) metamodel. The Object Constraint Language (OCL) is a language that enables one to describe expressions and constraints on object-oriented (UML and MOF) models and
+ other object modeling artifacts. An expression is an indication or specification of a value. A constraint is a restriction on one or more values of (part of) an object-oriented
+ model or system. REWERSE I1 Rule Markup Language (R2ML) is a general web rule markup language, that can represent different rule types: integrity, reaction, derivation and production.
+ It is used as pivotal metamodel to enable sharing rules between different rule languages, in this case with the OCL.
+ </p>
+ <p>This scenario is a contribution from <a href="http://milan.milanovic.org/">Milan Milanovic</a>.</p>
+ </description>
+ <pubDate />
+ </atlTransformation>
+ <atlTransformation>
+ <shortName>OCL2SWRL</shortName>
+ <name>OCL to SWRL</name>
+ <docLink>OCL2SWRL/README.txt</docLink>
+ <sourceLink>OCL2SWRL/OCL2SWRL.zip</sourceLink>
+ <description>
+ <p align="justify">
+ The OCL to SWRL transformation scenario describes a transformation from OCL (Object Constraint Language)
+ metamodel (with EMOF metamodel) into a R2ML (REWERSE I1 Rule Markup Language) metamodel and then to the
+ SWRL (Semantic Web Rule Language) metamodel (RDM) with ODM (OWL language metamodel). The Object Constraint Language (OCL)
+ is a language that enables one to describe expressions and constraints on object-oriented (UML and MOF) models and other
+ object modeling artifacts. An expression is an indication or specification of a value. A constraint is a restriction on one
+ or more values of (part of) an object-oriented model or system. REWERSE I1 Rule Markup Language (R2ML) is a
+ general web rule markup language, that can represent different rule types: integrity, reaction, derivation
+ and production. It is used as pivotal metamodel to enable sharing rules between different rule languages, in this
+ case with the OCL. SWRL is a web rule language based on combination of the OWL DL and OWL Lite sublanguages of the
+ OWL Web Ontology Language, with the Unary/Binary Datalog RuleML sublanguages of the Rule Markup Language (RuleML).
+ </p>
+ <p>This scenario is a contribution from <a href="http://milan.milanovic.org/">Milan Milanovic</a>.</p>
+ </description>
+ <pubDate></pubDate>
+ </atlTransformation>
+ <atlTransformation>
+ <shortName>PathExp2PetriNet</shortName>
+ <name>PathExp to PetriNet</name>
+ <docLink>PathExp2PetriNet/ExamplePathExp2PetriNet[v00.01].pdf</docLink>
+ <sourceLink>PathExp2PetriNet/PathExp2PetriNet.zip</sourceLink>
+ <description>
+ The path expression to Petri nets example describes a transformation from a path expression to a Petri net.
+ This document provides an overview of the whole transformation sequence that enables to produce an XML Petri
+ net representation (in the PNML format) from a textual definition of a path expression.
+ Its also describes the reverse transformation sequence that enables to build a textual path expression
+ representation from a XML definition of a Petri net (in the PNML format).
+ </description>
+ <pubDate></pubDate>
+ </atlTransformation>
+ <atlTransformation>
+ <shortName>Port</shortName>
+ <name>Port</name>
+ <docLink>http://www.eclipse.org/atl/documentation/basicExamples_Patterns/article.php?file=Port/index.html</docLink>
+ <sourceLink>Port/Port.zip</sourceLink>
+ <description>
+ In this example, we present some basic concepts of ATL through a simple use case. This use case deals with situations where the source element meta type could not be simply
+ matched with the target meta type. The only way to resolve the target meta type is to browse source model
+ </description>
+ <pubDate></pubDate>
+ </atlTransformation>
+ <atlTransformation>
+ <shortName>Public2Private</shortName>
+ <name>Public to Private</name>
+ <docLink>Public2Private/README.txt</docLink>
+ <sourceLink>Public2Private/Public2Private.zip</sourceLink>
+ <description>
+ <p>
+ The Public2Private ATL transformation makes all public attributes of a UML 1.4 model private.
+ Getters and setters are also created appropriately (i.e. no setter for a frozen attribute).
+ This transformation uses ATL refining mode as defined in [1].
+ Thanks to refining mode, only two rules have to be written: one for read-only (i.e. "frozen"
+ in UML terminology) attributes and one for read-write attributes.
+ </p>
+ <p>
+ Source and target models conform to UML the 1.4 metamodel provided as UMLDI.xmi.
+ A sample source model (PetriNet.xmi) and its corresponding target model (PetriNet-Privatized.xmi) are given.
+ Both models are also given in PNG format for easy visualization: <a href="Public2Private/PetriNet.png">PetriNet.png</a> and <a href="Public2Private/PetriNet-Privatized.png">PetriNet-Privatized.png</a>.
+ Additional source models may be created using Poseidon (http://www.gentleware.com/).
+ </p>
+ <p>
+ References:
+ <ul>
+ <li>[1] <a href="http://www.sciences.univ-nantes.fr/lina/atl/bibliography/MTIP05">Jouault, F., and Kurtev, I., Transforming Models with ATL, in proceedings of the Model Transformation in Practice Workshop, October 3rd 2005, part of the MoDELS 2005 conference</a></li>
+ </ul>
+ </p>
+ </description>
+ <pubDate></pubDate>
+ </atlTransformation>
+ <atlTransformation>
+ <shortName>QVT2ATLVM</shortName>
+ <name>QVT to ATL Virtual Machine Compiler</name>
+ <docLink>../usecases/QVT2ATLVM/</docLink>
+ <sourceLink>QVT2ATLVM/QVT2ATLVM.zip</sourceLink>
+ <description>
+ <p>
+This work provides a QVT compiler that targets the ATL Virtual Machine (ATL VM).
+The code generator is written in the ACG (Atl Code Generation) Domain-Specific Language (DSL),
+which is a domain-specific model transformation language (its domain is ATL VM bytecode generation,
+i.e., a fixed target metamodel). It takes as input a QVT model (typically in XMI format)
+that may have been created by a QVT front-end (i.e., a parser and type checker) like Procedural QVT, or SmartQVT. The output of the code generator is a ".asm"
+file similar to the ones generated by the ATL compiler, or the ACG compiler (both also written in ACG).
+ </p>
+ </description>
+ <pubDate></pubDate>
+ </atlTransformation>
+ <atlTransformation>
+ <shortName>R2ML2OCL</shortName>
+ <name>R2ML to OCL</name>
+ <docLink>R2ML2OCL/README.txt</docLink>
+ <sourceLink>R2ML2OCL/R2ML2OCL.zip</sourceLink>
+ <description>
+ <p align="justify">
+ The R2ML to OCL transformation scenario describes a transformation from R2ML (REWERSE I1 Rule Markup Language) metamodel into a OCL (Object Constraint Language) metamodel (with EMOF
+ metamodel). The Object Constraint Language (OCL) is a language that enables one to describe expressions and constraints on object-oriented (UML and MOF) models and other object modeling
+ artifacts. An expression is an indication or specification of a value. A constraint is a restriction on one or more values of (part of) an object-oriented model or system. REWERSE I1 Rule
+ Markup Language (R2ML) is a general web rule markup language, that can represent different rule types: integrity, reaction, derivation and production. It is used as pivotal metamodel to
+ enable sharing rules between different rule languages, in this case with the OCL.
+ </p>
+ <p>This scenario is a contribution from <a href="http://milan.milanovic.org/">Milan Milanovic</a>.</p>
+ </description>
+ <pubDate />
+ </atlTransformation>
+ <atlTransformation>
+ <shortName>R2ML2SWRL</shortName>
+ <name>R2ML to SWRL</name>
+ <docLink>R2ML2SWRL/README.txt</docLink>
+ <sourceLink>R2ML2SWRL/R2ML2SWRL.zip</sourceLink>
+ <description>
+ <p align="justify">
+ The R2ML to SWRL transformation scenario describes a transformation from R2ML (REWERSE I1 Markup Language) metamodel into a SWRL (Semantic Web Rule Language) metamodel (RDM). SWRL is a
+ web rule language based on combination of the OWL DL and OWL Lite sublanguages of the OWL Web Ontology Language, with the Unary/Binary Datalog RuleML sublanguages of the Rule Markup
+ Language (RuleML). REWERSE I1 Rule Markup Language is a general web rule markup language, that can represent different rule types: integrity, reaction, derivation and production. It
+ is used as pivotal metamodel to enable sharing rules between different rule languages, in this case with the SWRL.
+ </p>
+ <p>This scenario is a contribution from <a href="http://milan.milanovic.org/">Milan Milanovic</a>.</p>
+ </description>
+ <pubDate />
+ </atlTransformation>
+ <atlTransformation>
+ <shortName>RaiseSupplierAbstractionLevel</shortName>
+ <name>RaiseSupplierAbstractionLevel</name>
+ <docLink>RaiseSupplierAbstractionLevel/RaiseSupplierAbstractionLevel.pdf</docLink>
+ <sourceLink>RaiseSupplierAbstractionLevel/RaiseSupplierAbstractionLevel.zip</sourceLink>
+ <description>
+ This example is extract from <a href="http://www.dcs.kcl.ac.uk/staff/kcl/tcat.pdf">Catalogue of Model Transformations by K. Lano</a>.
+ The purpose of this transformation is: "a class may become large and unmanageable, with several loosely connected functionalities. It should be split into several classes, such as a master/controller class and helper classes, which have more coherent functionalities and data."
+ This example was extracted by <a href="http://www.sciences.univ-nantes.fr/lina/atl/contrib/simon">Eric Simon</a>.
+ </description>
+ <pubDate></pubDate>
+ </atlTransformation>
+ <atlTransformation>
+ <shortName>RedundantClassRemovable</shortName>
+ <name>RedundantClassRemovable</name>
+ <docLink>RedundantClassRemovable/RedundantClassRemovable.pdf</docLink>
+ <sourceLink>RedundantClassRemovable/RedundantClassRemovable.zip</sourceLink>
+ <description>
+ This example is extract from <a href="http://www.dcs.kcl.ac.uk/staff/kcl/tcat.pdf">Catalogue of Model Transformations by K. Lano</a>.
+ The purpose of this transformation is: "duplication of classes will lead to over-complex models which are difficult to modify and analyse."
+ This example was extracted by <a href="http://www.sciences.univ-nantes.fr/lina/atl/contrib/simon">Eric Simon</a>.
+ </description>
+ <pubDate></pubDate>
+ </atlTransformation>
+ <atlTransformation>
+ <shortName>RemovingAssociationClass</shortName>
+ <name>RemovingAssociationClass</name>
+ <docLink>RemovingAssociationClass/RemovingAssociationClass.pdf</docLink>
+ <sourceLink>RemovingAssociationClass/RemovingAssociationClass.zip</sourceLink>
+ <description>
+ This example is extract from <a href="http://www.dcs.kcl.ac.uk/staff/kcl/tcat.pdf">Catalogue of Model Transformations by K. Lano</a>.
+ The purpose of this transformation is: "association classes cannot be represented directly in many object-oriented programming languages."
+ This example was extracted by <a href="http://www.sciences.univ-nantes.fr/lina/atl/contrib/simon">Eric Simon</a>.
+ </description>
+ <pubDate></pubDate>
+ </atlTransformation>
+ <atlTransformation>
+ <shortName>RemovingManyManyAssociation</shortName>
+ <name>RemovingManyManyAssociation</name>
+ <docLink>RemovingManyManyAssociation/RemovingManyManyAssociation.pdf</docLink>
+ <sourceLink>RemovingManyManyAssociation/RemovingManyManyAssociation.zip</sourceLink>
+ <description>
+ This example is extract from <a href="http://www.dcs.kcl.ac.uk/staff/kcl/tcat.pdf">Catalogue of Model Transformations by K. Lano</a>.
+ The purpose of this transformation is to substitute a many-many association by an introduction of class with two many-one associations.
+ This example was extracted by <a href="http://www.sciences.univ-nantes.fr/lina/atl/contrib/simon">Eric Simon</a>.
+ </description>
+ <pubDate></pubDate>
+ </atlTransformation>
+ <atlTransformation>
+ <shortName>ReplaceAssociationByForeignKey</shortName>
+ <name>ReplaceAssociationByForeignKey</name>
+ <docLink>ReplaceAssociationByForeignKey/ReplaceAssociationByForeignKey.pdf</docLink>
+ <sourceLink>ReplaceAssociationByForeignKey/ReplaceAssociationByForeignKey.zip</sourceLink>
+ <description>
+ This example is extract from <a href="http://www.dcs.kcl.ac.uk/staff/kcl/tcat.pdf">Catalogue of Model Transformations by K. Lano</a>.
+ This transformation applies to any explicit many-one association between persistent classes. It assumes that primary keys already exist for the classes linked by the association. It replaces the association by embedding values of the key of the entity at the one end of the association into the entity at the many ends.
+ This example was extracted by <a href="http://www.sciences.univ-nantes.fr/lina/atl/contrib/baudry">Julien Baudry</a>.
+ </description>
+ <pubDate></pubDate>
+ </atlTransformation>
+ <atlTransformation>
+ <shortName>ReplaceInheritanceByAssociation</shortName>
+ <name>ReplaceInheritanceByAssociation</name>
+ <docLink>ReplaceInheritanceByAssociation/ReplaceInheritanceByAssociation.pdf</docLink>
+ <sourceLink>ReplaceInheritanceByAssociation/ReplaceInheritanceByAssociation.zip</sourceLink>
+ <description>
+ This example is extract from <a href="http://www.dcs.kcl.ac.uk/staff/kcl/tcat.pdf">Catalogue of Model Transformations by K. Lano</a>.
+ This transformation replaces an inheritance relationship between two classes by an association between the classes.
+ This example was extracted by <a href="http://www.sciences.univ-nantes.fr/lina/atl/contrib/baudry">Julien Baudry</a>.
+ </description>
+ <pubDate></pubDate>
+ </atlTransformation>
+ <atlTransformation>
+ <shortName>RSS2ATOM</shortName>
+ <name>RSS to ATOM</name>
+ <docLink>RSS2ATOM/RSS2ATOM.pdf</docLink>
+ <sourceLink>RSS2ATOM/RSS2ATOM.zip</sourceLink>
+ <description>
+ RSS is a format for syndicating news and the content of news-like sites.<br />
+ Atom is an XML-based file format intended to allow lists of information, known as "feeds", to be synchronised between publishers and consumers.<br />
+ RSS to ATOM was produced by <a href="http://www.sciences.univ-nantes.fr/lina/atl/contrib/srour">Youssef Srour</a>.
+ </description>
+ <pubDate></pubDate>
+ </atlTransformation>
+ <atlTransformation>
+ <shortName>SideEffect</shortName>
+ <name>Side Effect</name>
+ <docLink>http://www.eclipse.org/atl/documentation/basicExamples_Patterns/article.php?file=SideEffect/index.html</docLink>
+ <sourceLink>SideEffect/SideEffect.zip</sourceLink>
+ <description>
+ This case deals with the way to handle side effects induced while transforming an element. We will start from an imperative algorithm to create a transformation between two
+ metamodels. This algorithm will introduce a side effect problem. After several iteration a solution will be provided following ATL philosophy.
+ </description>
+ <pubDate></pubDate>
+ </atlTransformation>
+ <atlTransformation>
+ <shortName>SimpleClass2SimpleRDBMS</shortName>
+ <name>Simple Class to Simple RDBMS</name>
+ <docLink>SimpleClass2SimpleRDBMS/README.txt</docLink>
+ <sourceLink>SimpleClass2SimpleRDBMS/SimpleClass2SimpleRDBMS.zip</sourceLink>
+ <description>
+ <p>
+ This transformation implements the case study used in the Workshop Model Transformations
+ in Practice collocated with the MoDELS Conference, October, 2005. The description of the
+ case study can be found at the workshop web site: http://sosym.dcs.kcl.ac.uk/events/mtip05/.
+ </p>
+ <p>
+ Two versions of the SimpleClass2SimpleRDBMS transformation have been developed:
+ <ul>
+ <li>The first one, which is presented in [1], uses some ATL features that are not implemented
+ in the engine yet. Its purpose is to illustrate the planned features of the language.
+ </li>
+ <li>The second one, coming with this README.txt, is another version that works with
+ the ATL engine available on http://eclipse.org/gmt as of November 2005. This second version
+ uses roughly the same helpers as the first version.
+ </li>
+ </ul>
+ </p>
+ <p>
+ References:
+ <ul>
+ <li>[1] <a href="http://sosym.dcs.kcl.ac.uk/events/mtip05/submissions/jouault_kurtev__transforming_models_with_atl.pdf">Jouault, F., and Kurtev, I., Transforming Models with ATL, in proceedings of Model Transformations in Practice
+ Workshop, October 3rd 2005, part of the MoDELS 2005 Conference
+ </li>
+ </ul>
+ </p>
+ </description>
+ <pubDate></pubDate>
+ </atlTransformation>
+ <atlTransformation>
+ <shortName>SimplePDL2Tina</shortName>
+ <name>SimplePDL2Tina: models verification through Petri nets</name>
+ <docLink>http://www.eclipse.org/atl/usecases/SimplePDL2Tina/</docLink>
+ <sourceLink>http://combemale.perso.enseeiht.fr/atlzoo/SimplePDL2TinaZoo.zip</sourceLink>
+ <description>
+ These transformations are part of a
+ <a href="http://www.combemale.fr/wiki/doku.php?id=private:enseignement:metamodeling">Course</a>
+ about metamodeling, models transformation and verification.
+ These transformations introduce a property-driven approach to validate models through a translational semantics to Petri nets.
+ </description>
+ <pubDate>30/01/07</pubDate>
+ </atlTransformation>
+ <atlTransformation>
+ <shortName>SoftwareQualityControl2Bugzilla</shortName>
+ <name>Software Quality Control to Bugzilla</name>
+ <docLink>SoftwareQualityControl2Bugzilla/ExampleSoftwareQualityControl2Bugzilla[v00.01].pdf</docLink>
+ <sourceLink>SoftwareQualityControl2Bugzilla/SoftwareQualityControl2Bugzilla.zip</sourceLink>
+ <description>
+ The Software Quality Control to Bugzilla example describes a transformation from a SoftwareQualityControl model to a simple Bugzilla XML file.
+ Bugzilla is a free "Defect Tracking System" or "Bug-Tracking System", originally developed by the Mozilla Foundation, which allows individual or groups of developers to effectively keep track of outstanding bugs in their product.
+ The transformation is based on a Software Quality Control metamodel which describes a simple structure to manage software quality controls (and more especially bug-tracking).
+ The input of the transformation is a model which conforms to the SoftwareQualityControl metamodel.
+ The output is an XML file whose content conforms to a simple Bugzilla DTD.
+ </description>
+ <pubDate></pubDate>
+ </atlTransformation>
+ <atlTransformation>
+ <shortName>SoftwareQualityControl2MantisBT</shortName>
+ <name>Software Quality Control to Mantis Bug Tracker</name>
+ <docLink>SoftwareQualityControl2MantisBT/ExampleSoftwareQualityControl2MantisBugTracker[v00.01].pdf</docLink>
+ <sourceLink>SoftwareQualityControl2MantisBT/SoftwareQualityControl2MantisBugTracker.zip</sourceLink>
+ <description>
+ The Software Quality Control to Mantis Bug Tracker example describes a transformation from a SoftwareQualityControl model to a simple Mantis XML file.
+ Mantis Bug Tracker is a free web-based bug-tracking system written in PHP that uses a MySQL database.
+ The transformation is based on a Software Quality Control metamodel which describes a simple structure to manage software quality controls (and more especially bug-tracking).
+ The input of the transformation is a model which conforms to the SoftwareQualityControl metamodel.
+ The output is an XML file whose content conforms to a Mantis XML schema.
+ </description>
+ <pubDate></pubDate>
+ </atlTransformation>
+ <atlTransformation>
+ <shortName>SSL2SDL</shortName>
+ <name>SSL to SDL</name>
+ <docLink>SSL2SDL/ssl2sdl.pdf</docLink>
+ <sourceLink>SSL2SDL/SSL2SDL.zip</sourceLink>
+ <description>
+ The SSL to SDL example describes a transformation which enables to create a SDL model from a SSL model,
+ using an auxiliary ODM model that contains the ontology elements referred in the SSL model.
+ SDL is a language for describing concrete service interfaces, from a technical point of view, while
+ SSL can be used to create semantic descriptions of services. SSL models can refer to terms defined
+ in an external ontology, therefore another metamodel, ODM, is used for querying ontologies.
+ <br /><br />
+ This transformation and associated metamodels is a contribution from
+ Irina Dumitrascu and Natalia Rebeja , <a href="http://www.soluta.net">Soluta.Net</a>.
+ </description>
+ <pubDate></pubDate>
+ </atlTransformation>
+ <atlTransformation>
+ <shortName>SWRL2R2ML</shortName>
+ <name>SWRL to R2ML</name>
+ <docLink>SWRL2R2ML/README.txt</docLink>
+ <sourceLink>SWRL2R2ML/SWRL2R2ML.zip</sourceLink>
+ <description>
+ <p align="justify">
+ The SWRL to R2ML transformation scenario describes a transformation from SWRL (Semantic Web Rule Language) metamodel (RDM) into a R2ML (REWERSE I1 Markup Language) metamodel. SWRL is
+ a web rule language based on combination of the OWL DL and OWL Lite sublanguages of the OWL Web Ontology Language, with the Unary/Binary Datalog RuleML sublanguages of the Rule Markup
+ Language (RuleML). REWERSE I1 Rule Markup Language is a general web rule markup language, that can represent different rule types: integrity, reaction, derivation and production. It is
+ used as pivotal metamodel to enable sharing rules between different rule languages, in this case with the SWRL.
+ </p>
+ <p>This scenario is a contribution from <a href="http://milan.milanovic.org/">Milan Milanovic</a>.</p>
+ </description>
+ <pubDate />
+ </atlTransformation>
+ <atlTransformation>
+ <shortName>Syntax2SBVR2UML</shortName>
+ <name>Syntax to SBVR to UML</name>
+ <docLink>../usecases/Syntax2SBVR2UML/</docLink>
+ <sourceLink>Syntax2SBVR2UML/Syntax2SBVR2UML.zip</sourceLink>
+ <description>
+ <p align="justify">
+ These transformations are used to produce a UML class diagram from controlled English text using SBVR and Syntax as intermediate layers.
+ Syntax is an original metamodel allowing to describe syntactical, grammatical and semantical properties of an english text.
+ SBVR is a metamodel, obtained from the OMG's specification, for describing semantics of business vocabularies and facts.
+ UML class diagrams allow to express concepts, relations and instances (a conceptual schema).
+ The aim of this scenario is to allow the automatic production of a SBVR model from a syntactical analysis of an english text, then produce a corresponding UML model.
+ The linguistic analysis itself, which may automatically produce a Syntax model from plain text, is outside the scope of this scenario.
+ </p>
+ </description>
+ <pubDate/>
+ </atlTransformation>
+ <atlTransformation>
+ <shortName>Table2MSOfficeExcel</shortName>
+ <name>Table to Microsoft Office Excel</name>
+ <docLink>Table2MSOfficeExcel/ExampleTable2MicrosoftOfficeExcel[v00.01].pdf</docLink>
+ <sourceLink>Table2MSOfficeExcel/Table2MicrosoftOfficeExcel.zip</sourceLink>
+ <description>
+ The Table to Microsoft Office Excel example describes a transformation from a very basic table representation (similar to the one produced by the <a href="#Java2Table">JavaSource to Table</a> transformation) to an Excel workbook with one single worksheet containing this table.
+ The transformation is based on a simplified subset of the SpreadsheetML XML dialect which is the one used by Microsoft to import/export Excel workbooks data in XML since the 2003 version of Microsoft Office.
+ This transformation produces an XML file which can be directly open by Excel 2003.
+ This file describes a workbook with the same content (i.e. the same table) that the one of the input Table model.
+ </description>
+ <pubDate></pubDate>
+ </atlTransformation>
+ <atlTransformation>
+ <shortName>Table2SVGBarChart</shortName>
+ <name>Table2SVGBarChart</name>
+ <docLink>Table2SVGBarChart/ExampleTable2SVGBarChart[v00.05].pdf</docLink>
+ <sourceLink>Table2SVGBarChart/Table2SVGBarChart.zip</sourceLink>
+ <description>
+ The Table to SVGBarChart example describes a transformation from a Table model to a SVG
+ file containing several bar chart representations.<br />
+ This scenario is contributed by Eric Vépa (<a href="http://www.sodius.com">SODIUS</a>).
+ </description>
+ <pubDate></pubDate>
+ </atlTransformation>
+ <atlTransformation>
+ <shortName>Table2SVGPieChart</shortName>
+ <name>Table2SVGPieChart</name>
+ <docLink>Table2SVGPieChart/ExampleTable2SVGPieChart[v00.05].pdf</docLink>
+ <sourceLink>Table2SVGPieChart/Table2SVGPieChart.zip</sourceLink>
+ <description>
+ The Table to SVGPieChart example describes a transformation from a Table model to a SVG
+ file containing several pie chart representations.<br />
+ This scenario is contributed by Eric Vépa (<a href="http://www.sodius.com">SODIUS</a>).
+ </description>
+ <pubDate></pubDate>
+ </atlTransformation>
+ <atlTransformation>
+ <shortName>Table2TabularHTML</shortName>
+ <name>Table2TabularHTML</name>
+ <docLink>Table2TabularHTML/ExampleTable2TabularHTML[v00.05].pdf</docLink>
+ <sourceLink>Table2TabularHTML/Table2TabularHTML.zip</sourceLink>
+ <description>
+ The Table to TabularHTML example describes a transformation from a Table model to an
+ HTML file containing HTML tables.<br />
+ This scenario is contributed by Eric Vépa (<a href="http://www.sodius.com">SODIUS</a>).
+ </description>
+ <pubDate></pubDate>
+ </atlTransformation>
+ <atlTransformation>
+ <shortName>Tree2List</shortName>
+ <name>Tree to List</name>
+ <docLink>../basicExamples_Patterns/Tree2List/</docLink>
+ <sourceLink>Tree2List/Tree2List.zip</sourceLink>
+ <description>
+ This transformation presents a basic example where a tree is transformed into a list. This kind of transformation is usually made by an
+ imperative Depth First Traversal algorithm. This scenario is a contribution from Cyril Faure (<a href="http://www.c-s.fr/">C-S</a>).
+ </description>
+ <pubDate></pubDate>
+ </atlTransformation>
+ <atlTransformation>
+ <shortName>TT2BDD</shortName>
+ <name>Truth Tables to Binary Decision Diagrams</name>
+ <docLink>TT2BDD/README</docLink>
+ <sourceLink>TT2BDD/TT2BDD.zip</sourceLink>
+ <description>
+ <p>
+ These files provide a case study for model transformation applied to digital logic circuits.
+ Engineers can use various formalisms to represent combinatorial or sequential logic.
+ The most widespread representations for combinatorial logic are truth tables and boolean equations.
+ </p>
+ <p>
+ In many EDA tools, combinatorial logic is represented in a canonical form using Binary Decision Diagrams (BDD).
+ BDDs are manly used for model checking and logic optimization.
+ </p>
+ <p>
+ The purpose here is to use model transformation to transform a truth table into a binary decision diagram.
+ </p>
+ <p>
+ This transformation and associated metamodels is a contribution from Guillaume Savaton, ESEO/TRAME.
+ </p>
+ </description>
+ <pubDate></pubDate>
+ </atlTransformation>
+ <atlTransformation>
+ <shortName>UML22Measure</shortName>
+ <name>UML2 to Measure</name>
+ <docLink>UML22Measure/ExampleUML22Measure[v00.02].pdf</docLink>
+ <sourceLink>UML22Measure/UML22Measure.zip</sourceLink>
+ <description>
+ The UML2 to Measure example describes measurement on UML2 models, using metrics defined as ATL libraries.
+ This scenario is contributed by Eric Vépa (<a href="http://www.sodius.com">SODIUS</a>).
+ </description>
+ <pubDate></pubDate>
+ </atlTransformation>
+ <atlTransformation>
+ <shortName>UML2Amble</shortName>
+ <name>UML to Amble</name>
+ <docLink>UML2Amble/ExampleUML2Amble[v00.01].pdf</docLink>
+ <sourceLink>UML2Amble/UML2Amble.zip</sourceLink>
+ <description>
+ The UML to Amble example describes a transformation from an UML model specifying different
+ aspects of a distributed program into an implementation of this distributed program in the Amble
+ programming language.<br /><br />
+ Amble is a distributed programming language based on Objective Caml. It enables to specify a
+ distributed program in terms of processes that run concurrently. These processes are designed as
+ states machines that are connected to each other by means of networks. Each network specifies a set
+ of channels. The source process of a channel is allowed to write to its target process. An Amble
+ program is composed of a single .ml file that includes the definition of the different process types that
+ are involved in the program, as well as a set of .topo files (one for each considered network) that
+ specifies the topology of the defined networks.
+ </description>
+ <pubDate></pubDate>
+ </atlTransformation>
+ <atlTransformation>
+ <shortName>UML2AnyLogic</shortName>
+ <name>UML to AnyLogic</name>
+ <docLink>http://www.eclipse.org/atl/usecases/UML2AnyLogic/</docLink>
+ <sourceLink>UML2AnyLogic/UML2AnyLogic.zip</sourceLink>
+ <description>
+ This use case presents a transformation from annotated UML2 activity diagrams to AnyLogic simulation models.
+ </description>
+ <pubDate></pubDate>
+ </atlTransformation>
+ <atlTransformation>
+ <shortName>UML2Java</shortName>
+ <name>UML to Java</name>
+ <docLink>UML2Java/ExampleUML2Java[v00.01].pdf</docLink>
+ <sourceLink>UML2Java/UML2Java.zip</sourceLink>
+ <description>
+ This document illustrates a (simplified) classical transformation example from UML models to Java models that has been implemented in ATL.
+ The UML to Java example describes the transformation of a UML model to a simplified Java model.
+ The Java model holds the information for the creation of Java classes, especially what concerns the
+ structure of these classes, namely the package reference, the attributes and the methods.
+ </description>
+ <pubDate></pubDate>
+ </atlTransformation>
+ <atlTransformation>
+ <shortName>UML2KM3</shortName>
+ <name>UML Class Diagram to KM3</name>
+ <docLink>http://www.eclipse.org/atl/usecases/UML2MOF/</docLink>
+ <sourceLink>UML2KM3/UML2KM3.zip</sourceLink>
+ <description>
+ This scenario generates a metamodel conforming to KM3 from a UML Class Diagram.
+ </description>
+ <pubDate></pubDate>
+ </atlTransformation>
+ <atlTransformation>
+ <shortName>UML2MOF</shortName>
+ <name>UML to MOF</name>
+ <docLink>UML2MOF/ExampleUML2MOF[v00.01].pdf</docLink>
+ <sourceLink>UML2MOF/UML2MOF.zip</sourceLink>
+ <description>
+ The MOF (Meta Object Facility) is an OMG standard enabling to describe metamodels through common semantics.
+ The UML (Unified Modelling Language) Core standard is the OMG common modelling language.
+ Although, the MOF is primarily designed for metamodel definitions and UML Core for the design of models, the two standards handle very close notions.
+ This example describes a transformation enabling to pass from the UML to the MOF semantics.
+ The transformation is based on the UML Profile for MOF OMG specification.
+ </description>
+ <pubDate></pubDate>
+ </atlTransformation>
+ <atlTransformation>
+ <shortName>UML2OWL</shortName>
+ <name>UML to OWL</name>
+ <docLink>UML2OWL/README.txt</docLink>
+ <sourceLink>UML2OWL/UML2OWL.zip</sourceLink>
+ <description>
+ This ATL scenario presents an implementation of the OMG's ODM specification.
+ This transformation is used to produce an OWL ontology + OWL Individuals from a UML Model + UML Instances.
+ </description>
+ <pubDate></pubDate>
+ </atlTransformation>
+ <atlTransformation>
+ <shortName>UMLActivityDiagram2MSProject</shortName>
+ <name>UML Activity Diagram to MSProject</name>
+ <docLink>UMLActivityDiagram2MSProject/ExampleUmlActivityDiagram2MSProject[v00.01].pdf</docLink>
+ <sourceLink>UMLActivityDiagram2MSProject/UmlActivityDiagram2MSProject.zip</sourceLink>
+ <description>
+ The UMLActivityDiagram to MSProject example describes a transformation from a loop free UML
+ activity diagram (describing some tasks series) to a MS Project. The transformation is based on a
+ simplified subset of the UML State Machine metamodel. This transformation produces a project
+ defined in conformance to a limited subset of the MSProject metamodel.
+ </description>
+ <pubDate></pubDate>
+ </atlTransformation>
+ <atlTransformation>
+ <shortName>UMLDI2SVG</shortName>
+ <name>UMLDI to SVG</name>
+ <docLink>UMLDI2SVG/UMLDI2SVG[0.04].pdf</docLink>
+ <sourceLink>UMLDI2SVG/UMLDI2SVG.zip</sourceLink>
+ <description>
+ The UMLDI to SVG example describes a transformation from a UML diagram, that has its presentation
+ information according to the UML Diagram Interchange standard, to its presentation using the W3C
+ standard SVG (Scalable Vector Graphics), an XMLbased format.
+ </description>
+ <pubDate></pubDate>
+ </atlTransformation>
+ <atlTransformation>
+ <shortName>UMLCopyModel</shortName>
+ <name>UML CopyModel, ModelCopy</name>
+ <docLink>http://ssel.vub.ac.be/ssel/research:mdd:casestudies#copymodel_modelcopy</docLink>
+ <sourceLink>http://ssel.vub.ac.be/viewcvs/viewcvs.py/svn-gen/UML1CaseStudies/uml1cs-transformations/</sourceLink>
+ <description>
+ <p>
+ These transformations are part of the <a href="http://ssel.vub.ac.be/ssel/research:mdd:casestudies">UML refinement transformations</a> by <a href="http://ssel.vub.ac.be/ssel/about:members:denniswagelaar">Dennis Wagelaar</a>.
+ </p>
+ <p>
+ Introduction: "UML allows for the introduction of custom abstractions using
+ stereotypes and/or profiles. These abstractions can be refined to a
+ lower-level UML description using refinement transformations. Several
+ refinement transformations are provided to refine such abstractions as
+ 'Observer', 'Singleton' and 'Applet'. Refinement transformations are also
+ provided to refine standard UML elements into lower-level structures, such as
+ associations to public attributes and public attributes to encapsulated
+ attributes (with getter and setter methods)."
+ </p>
+ <p>
+ The CopyModel transformation copies all elements of one model into another model.
+ There are two variants available:
+ </p>
+ <ul>
+ <li><b><a href="http://ssel.vub.ac.be/viewcvs/viewcvs.py/UML1CaseStudies/uml1cs-transformations/CopyModel.atl?view=markup">CopyModel.atl</a>:</b>
+ This version uses ATL refining mode (see the <a href="#Public2Private">Public2Private</a> transformation and documentation).
+ This means that copying rules are only required for the root model elements.
+ Also, the input and output model are required to have the same meta-model (and repository), since this is required by refinement mode.</li>
+ <li><b><a href="http://ssel.vub.ac.be/viewcvs/viewcvs.py/UML1CaseStudies/uml1cs-transformations/ModelCopy.atl?view=markup">ModelCopy.atl</a>:</b>
+ Another version based on auto-generated, explicit copying rules for each meta-class.
+ Different (yet compatible) meta-models can be used for input and output model.
+ Also, different repositories can be used, e.g. for copying a model from MDR to EMF.
+ </ul>
+ </description>
+ <pubDate></pubDate>
+ </atlTransformation>
+ <atlTransformation>
+ <shortName>UMLSD2STMD</shortName>
+ <name>UML Sequence Diagrams to Statechart Diagram</name>
+ <docLink>http://www.st.ewi.tudelft.nl/~basgraaf/software/mde/atl/UMLSD2STMD/README.txt</docLink>
+ <sourceLink>http://www.st.ewi.tudelft.nl/~basgraaf/software/mde/atl/UMLSD2STMD/UMLSD2STMD.zip</sourceLink>
+ <description>
+ These transformations are used by <a href="http://www.st.ewi.tudelft.nl/~basgraaf">Bas Graaf</a> to check
+ the conformance of behavioural specifications. These transformations transform a set of UML Sequence Diagrams into a (hierarchical) UML
+ State Machine. The complete generation of a State Machine from a set of scenarios comprises four consecutive model transformations.
+ </description>
+ <pubDate></pubDate>
+ </atlTransformation>
+ <atlTransformation>
+ <shortName>UMLMergeModel</shortName>
+ <name>UML MergeModel, ModelMerge</name>
+ <docLink>http://ssel.vub.ac.be/ssel/research:mdd:casestudies#mergemodel_modelmerge</docLink>
+ <sourceLink>http://ssel.vub.ac.be/viewcvs/viewcvs.py/svn-gen/UML1CaseStudies/uml1cs-transformations/</sourceLink>
+ <description>
+ <p>
+ These transformations are part of the <a href="http://ssel.vub.ac.be/ssel/research:mdd:casestudies">UML refinement transformations</a> by <a href="http://ssel.vub.ac.be/ssel/about:members:denniswagelaar">Dennis Wagelaar</a>.
+ </p>
+ <p>
+ These transformations are meant to merge a model with the main model.
+ The MERGE model is merged with the IN model and written to the OUT model.
+ They are currently limited to copying elements that can occur in UML Class Diagrams (including Action Semantics).
+ There are two variants available:
+ </p>
+ <ul>
+ <li><b><a href="http://ssel.vub.ac.be/viewcvs/viewcvs.py/UML1CaseStudies/uml1cs-transformations/MergeModel.atl?view=markup">MergeModel.atl</a>:</b>
+ Based on refinement mode. This means that all models are required to have the same meta-model (and repository), since this is required by refinement mode.
+ Partly optimised for speed by caching intermediate results in OCL helper attributes.</li>
+ <li><b><a href="http://ssel.vub.ac.be/viewcvs/viewcvs.py/UML1CaseStudies/uml1cs-transformations/ModelMerge.atl?view=markup">ModelMerge.atl</a>:</b>
+ Based on auto-generated, explicit copying rules for each meta-class. Different (yet compatible) meta-models (and repositories) can be used for the models.
+ NOTE: This transformation is no longer maintained/used because it is too complex/inefficient compared to its alternative.</li>
+ </ul>
+ </description>
+ <pubDate></pubDate>
+ </atlTransformation>
+ <atlTransformation>
+ <shortName>UMLAssociationAttributes</shortName>
+ <name>UML AssociationAttributes, Java2AssociationAttributes</name>
+ <docLink>http://ssel.vub.ac.be/ssel/research:mdd:casestudies#associationattributes_java2associationattributes</docLink>
+ <sourceLink>http://ssel.vub.ac.be/viewcvs/viewcvs.py/svn-gen/UML1CaseStudies/uml1cs-transformations/</sourceLink>
+ <description>
+ <p>
+ These transformations are part of the <a href="http://ssel.vub.ac.be/ssel/research:mdd:casestudies">UML refinement transformations</a> by <a href="http://ssel.vub.ac.be/ssel/about:members:denniswagelaar">Dennis Wagelaar</a>.
+ </p>
+ <p>
+ These transformations introduce Attributes (with Java initial values) for each Association End. There are two variants available:
+ </p>
+ <ul>
+ <li><b><a href="http://ssel.vub.ac.be/viewcvs/viewcvs.py/UML1CaseStudies/uml1cs-transformations/AssociationAttributes.atl?view=markup">AssociationAttributes.atl</a>:</b>
+ Uses strict Java 1 API. Works on J2ME MIDP 1.0 as well.</li>
+ <li><b><a href="http://ssel.vub.ac.be/viewcvs/viewcvs.py/UML1CaseStudies/uml1cs-transformations/Java2AssociationAttributes.atl?view=markup">Java2AssociationAttributes.atl</a>:</b>
+ Uses the Java 2 Collections framework. Works on J2ME PP 1.0 as well.</li>
+ </ul>
+ </description>
+ <pubDate></pubDate>
+ </atlTransformation>
+ <atlTransformation>
+ <shortName>UMLAccessors</shortName>
+ <name>UML Accessors, Java2Accessors</name>
+ <docLink>http://ssel.vub.ac.be/ssel/research:mdd:casestudies#accessors_java2accessors</docLink>
+ <sourceLink>http://ssel.vub.ac.be/viewcvs/viewcvs.py/svn-gen/UML1CaseStudies/uml1cs-transformations/</sourceLink>
+ <description>
+ <p>
+ These transformations are part of the <a href="http://ssel.vub.ac.be/ssel/research:mdd:casestudies">UML refinement transformations</a> by <a href="http://ssel.vub.ac.be/ssel/about:members:denniswagelaar">Dennis Wagelaar</a>.
+ </p>
+ <p>
+ These transformations introduce accessor Operations/Methods (with Java bodies) for each public Attribute.
+ The public Attributes are then made private. This transformation is also used in refactoring as "Encapsulate Field".
+ There are two variants available:
+ </p>
+ <ul>
+ <li><b><a href="http://ssel.vub.ac.be/viewcvs/viewcvs.py/UML1CaseStudies/uml1cs-transformations/Accessors.atl?view=markup">Accessors.atl</a>:</b>
+ Uses strict Java 1 API. Works on J2ME MIDP 1.0 as well.</li>
+ <li><b><a href="http://ssel.vub.ac.be/viewcvs/viewcvs.py/UML1CaseStudies/uml1cs-transformations/Java2Accessors.atl?view=markup">Java2Accessors.atl</a>:</b>
+ Uses the Java 2 Collections framework. Works on J2ME PP 1.0 as well.</li>
+ </ul>
+ </description>
+ <pubDate></pubDate>
+ </atlTransformation>
+ <atlTransformation>
+ <shortName>UMLObserver</shortName>
+ <name>UML Observer, JavaObserver</name>
+ <docLink>http://ssel.vub.ac.be/ssel/research:mdd:casestudies#observer_javaobserver</docLink>
+ <sourceLink>http://ssel.vub.ac.be/viewcvs/viewcvs.py/svn-gen/UML1CaseStudies/uml1cs-transformations/</sourceLink>
+ <description>
+ <p>
+ These transformations are part of the <a href="http://ssel.vub.ac.be/ssel/research:mdd:casestudies">UML refinement transformations</a> by <a href="http://ssel.vub.ac.be/ssel/about:members:denniswagelaar">Dennis Wagelaar</a>.
+ </p>
+ <p>
+ These transformations introduce the Java infrastructure to implement the "Observer", "Observable" and "subscribe" Stereotypes.
+ Any instances of "Observer" Classes that have a "subscribe" Association to an "Observable" Class,
+ will automatically be subscribed to the "Observable" instance that they are linked to.
+ In addition, all setter Methods of the "Observable" Class will be updated to do a notify as well.
+ An "update" Operation/Method will be introduced for each "Observer" Class,
+ which is configured to invoke any "onXYZChange" Operations, where "XYZ" is the name of the Attribute that is changed.
+ There are two variants available:
+ </p>
+ <ul>
+ <li><b><a href="http://ssel.vub.ac.be/viewcvs/viewcvs.py/UML1CaseStudies/uml1cs-transformations/Observer.atl?view=markup">Observer.atl</a>:</b>
+ Uses strict Java 1 API. Works on J2ME MIDP 1.0 as well.</li>
+ <li><b><a href="http://ssel.vub.ac.be/viewcvs/viewcvs.py/UML1CaseStudies/uml1cs-transformations/JavaObserver.atl?view=markup">JavaObserver.atl</a>:</b>
+ Uses the java.util.Observer framework. Also uses Java reflection to detect any "onXYZChange" handler methods.
+ This means that "onXYZChange" methods of subclasses will also be detected and without a recompile of the superclass.</li>
+ </ul>
+ </description>
+ <pubDate></pubDate>
+ </atlTransformation>
+ <atlTransformation>
+ <shortName>UMLSingleton</shortName>
+ <name>UML Singleton</name>
+ <docLink>http://ssel.vub.ac.be/ssel/research:mdd:casestudies#singleton</docLink>
+ <sourceLink>http://ssel.vub.ac.be/viewcvs/viewcvs.py/svn-gen/UML1CaseStudies/uml1cs-transformations/</sourceLink>
+ <description>
+ <p>
+ This transformation is part of the <a href="http://ssel.vub.ac.be/ssel/research:mdd:casestudies">UML refinement transformations</a> by <a href="http://ssel.vub.ac.be/ssel/about:members:denniswagelaar">Dennis Wagelaar</a>.
+ </p>
+ <p>
+ A simple transformation that adds a static "getInstance" Operation/Method and a static "instance" Attribute to each Class with a "Singleton" Stereotype.
+ Does not prevent direct usage of the constructor. Uses strict Java 1 API. Works on J2ME MIDP 1.0 as well.
+ </p>
+ </description>
+ <pubDate></pubDate>
+ </atlTransformation>
+ <atlTransformation>
+ <shortName>UMLApplet</shortName>
+ <name>UML Applet, MIDlet</name>
+ <docLink>http://ssel.vub.ac.be/ssel/research:mdd:casestudies#applet_midlet</docLink>
+ <sourceLink>http://ssel.vub.ac.be/viewcvs/viewcvs.py/svn-gen/UML1CaseStudies/uml1cs-transformations/</sourceLink>
+ <description>
+ <p>
+ These transformations are part of the <a href="http://ssel.vub.ac.be/ssel/research:mdd:casestudies">UML refinement transformations</a> by <a href="http://ssel.vub.ac.be/ssel/about:members:denniswagelaar">Dennis Wagelaar</a>.
+ </p>
+ <p>
+ These transformations introduce Java Applet infrastructure for each Class with an "Applet" stereotype. There are two variants available:
+ </p>
+ <ul>
+ <li><b><a href="http://ssel.vub.ac.be/viewcvs/viewcvs.py/UML1CaseStudies/uml1cs-transformations/Applet.atl?view=markup">Applet.atl</a>:</b>
+ Turns each "Applet" Class into a java.applet.Applet and introduces the "init", "getParameterInfo" and "getAppletInfo" Operations/Methods.</li>
+ <li><b><a href="http://ssel.vub.ac.be/viewcvs/viewcvs.py/UML1CaseStudies/uml1cs-transformations/MIDlet.atl?view=markup">MIDlet.atl</a>:</b>
+ Turns each "Applet" Class into a javax.microedition.midlet.MIDlet and introduces the "startApp", "pauseApp", "destroyApp", "init", "destroy", "start" and "stop" Operations/Methods.
+ Works on J2ME MIDP 1.0 or up.</li>
+ </ul>
+ </description>
+ <pubDate></pubDate>
+ </atlTransformation>
+ <atlTransformation>
+ <shortName>UMLDataTypes</shortName>
+ <name>UML DataTypes, Java2DataTypes</name>
+ <docLink>http://ssel.vub.ac.be/ssel/research:mdd:casestudies#datatypes_java2datatypes</docLink>
+ <sourceLink>http://ssel.vub.ac.be/viewcvs/viewcvs.py/svn-gen/UML1CaseStudies/uml1cs-transformations/</sourceLink>
+ <description>
+ <p>
+ These transformations are part of the <a href="http://ssel.vub.ac.be/ssel/research:mdd:casestudies">UML refinement transformations</a> by <a href="http://ssel.vub.ac.be/ssel/about:members:denniswagelaar">Dennis Wagelaar</a>.
+ </p>
+ <p>
+ These transformations replace the OCL types with Java types. There are two variants available:
+ </p>
+ <ul>
+ <li><b><a href="http://ssel.vub.ac.be/viewcvs/viewcvs.py/UML1CaseStudies/uml1cs-transformations/DataTypes.atl?view=markup">DataTypes.atl</a>:</b>
+ Uses strict Java 1 API. Works on J2ME MIDP 1.0 as well.</li>
+ <li><b><a href="http://ssel.vub.ac.be/viewcvs/viewcvs.py/UML1CaseStudies/uml1cs-transformations/Java2DataTypes.atl?view=markup">Java2DataTypes.atl</a>:</b>
+ Uses the Java 2 Collections framework. Works on J2ME PP 1.0 as well.</li>
+ </ul>
+ </description>
+ <pubDate></pubDate>
+ </atlTransformation>
+ <atlTransformation>
+ <shortName>UMLAsyncMethods</shortName>
+ <name>UML AsyncMethods</name>
+ <docLink>http://ssel.vub.ac.be/ssel/research:mdd:casestudies#asyncmethods</docLink>
+ <sourceLink>http://ssel.vub.ac.be/viewcvs/viewcvs.py/svn-gen/UML1CaseStudies/uml1cs-transformations/</sourceLink>
+ <description>
+ <p>
+ This transformation is part of the <a href="http://ssel.vub.ac.be/ssel/research:mdd:casestudies">UML refinement transformations</a> by <a href="http://ssel.vub.ac.be/ssel/about:members:denniswagelaar">Dennis Wagelaar</a>.
+ </p>
+ <p>
+ A simple transformation that wraps the Method body of each Operation with an "asynchronous" Stereotype inside a Thread.
+ Uses java.lang.Thread, which is part of the Java 1.0 API. Works on J2ME MIDP 1.0 as well.
+ </p>
+ </description>
+ <pubDate></pubDate>
+ </atlTransformation>
+ <atlTransformation>
+ <shortName>UMLCD2UMLProfile</shortName>
+ <name>UML Class Diagram to UML Profile</name>
+ <docLink>UMLCD2UMLProfile/README.txt</docLink>
+ <sourceLink>UMLCD2UMLProfile/UMLClassDiagram_to_UMLProfile_v0.1.zip</sourceLink>
+ <description>
+ This ATL scenario transforms a UML2 Class Diagram into a UML2 Profile.
+ </description>
+ <pubDate></pubDate>
+ </atlTransformation>
+ <atlTransformation>
+ <shortName>WSDL2R2ML</shortName>
+ <name>WSDL to R2ML</name>
+ <docLink>WSDL2R2ML/README.txt</docLink>
+ <sourceLink>WSDL2R2ML/WSDL2R2ML.zip</sourceLink>
+ <description>
+ <p align="justify">
+ The WSDL to R2ML transformation scenario describes a transformation from WSDL (Web Services Description Language)
+ metamodel into a R2ML (REWERSE I1 Markup Language) metamodel. "WSDL enables one to separate the description of the abstract
+ functionality offered by a service from concrete details of a service description such as 'how' and 'where' that
+ functionality is offered". REWERSE I1 Rule Markup Language is a general web rule markup language, that can represent
+ different rule types: integrity, reaction, derivation and production. It is used as pivotal metamodel to enable sharing
+ rules between different rule languages.
+ </p>
+ <p>
+ This scenario is a contribution from Marko Ribaric.
+ </p>
+ </description>
+ <pubDate></pubDate>
+ </atlTransformation>
+ <atlTransformation>
+ <shortName>XSLT2XQuery</shortName>
+ <name>XSLT to XQuery</name>
+ <docLink>XSLT2XQuery/ExampleXSLT2XQuery[v00.01].pdf</docLink>
+ <sourceLink>XSLT2XQuery/XSLT2XQuery.zip</sourceLink>
+ <description>
+ The XSLT to XQuery example describes a simplified transformation of XSLT code to XQuery code.
+ </description>
+ <pubDate></pubDate>
+ </atlTransformation>
+</atlTransformations>
\ No newline at end of file
diff --git a/atlTransformations/atlTransformations_script.php b/atlTransformations/atlTransformations_script.php
new file mode 100644
index 0000000..9d28a2f
--- /dev/null
+++ b/atlTransformations/atlTransformations_script.php
@@ -0,0 +1,85 @@
+<?php
+
+#*****************************************************************************
+#
+# atlTransformations_script.php
+#
+# Author: Freddy Allilaire
+# Date: 2005-11-13
+#
+#****************************************************************************
+
+require_once("atlTransformations_script_xml.php");
+
+function getAtlTransformations() {
+ $file_name = "./atlTransformations.xml";
+
+ $rss = getAtlTransformationsParsed($file_name);
+
+ $html1 = "<div class=\"homeitem3col\">";
+ $html1 .= "<h3>";
+ $html1 .= "ATL Transformations list";
+ $html1 .= "</h3>";
+
+ $html1 .= "<ul class=\"midlist\">";
+
+ $html2 = "";
+
+ $scenariosNumber = 0;
+ foreach ($rss->atlTransformations as $atlTransformation) {
+ $scenariosNumber++;
+
+ $html1 .= "<li>";
+ $html1 .= "<b><a href=\"#$atlTransformation->shortName\">$atlTransformation->name</a></b>: ";
+ $html1 .= "<a href=\"$atlTransformation->docLink\">Documentation</a>, ";
+ $html1 .= "<a href=\"$atlTransformation->sourceLink\">Source files</a>";
+ $html1 .= "</li>\n";
+
+ $html2 .= "<div class=\"homeitem3col\">";
+ $html2 .= "<a name=\"$atlTransformation->shortName\"></a>";
+ $html2 .= "<h3>";
+ $html2 .= $atlTransformation->name;
+ $html2 .= "</h3>";
+ $html2 .= "<ul>";
+ $html2 .= "<li>";
+ $html2 .= "<a href=\"$atlTransformation->docLink\">Documentation</a>, ";
+ $html2 .= "<a href=\"$atlTransformation->sourceLink\">Source files</a>";
+ $html2 .= "<blockquote>" . $atlTransformation->description . "</blockquote>";
+ $html2 .= "</li>\n";
+ $html2 .= "</ul>";
+ $html2 .= "<hr class=\"clearer\" />";
+ $html2 .= "</div>";
+ }
+ $html1 .= "</ul>";
+ $html1 .= "<hr class=\"clearer\" />";
+ $html1 .= "</div>";
+
+ $html0 = "<p>There are currently " . $scenariosNumber . " model transformations scenarios in this zoo.</p>\n";
+
+ $html = $html0 . $html1 . $html2;
+
+ return $html;
+}
+
+class ATLTransformationsList {
+ var $atlTransformations;
+
+ function ATLTransformationsList() {
+ $this->atlTransformations = array();
+ }
+
+ function add_atlTransformation(&$atlTransformations) {
+ array_push($this->atlTransformations, $atlTransformations);
+ }
+}
+
+class ATLTransformation {
+ var $shortName;
+ var $name;
+ var $docLink;
+ var $sourceLink;
+ var $description;
+ var $pubDate;
+}
+
+?>
diff --git a/atlTransformations/atlTransformations_script_xml.php b/atlTransformations/atlTransformations_script_xml.php
new file mode 100644
index 0000000..c229a4b
--- /dev/null
+++ b/atlTransformations/atlTransformations_script_xml.php
@@ -0,0 +1,87 @@
+<?php
+
+#*****************************************************************************
+#
+# atlTransformations_script_xml.php
+#
+# Author: Freddy Allilaire
+# Date: 2005-11-13
+#
+#****************************************************************************
+
+require_once($_SERVER['DOCUMENT_ROOT'] . "/gmt/resources/scripts/xml_sax_parsing_extension.php");
+
+function & getAtlTransformationsParsed($file_name) {
+ $handler = new ATLFileHandler();
+ parse_xml_file($file_name, $handler);
+ return $handler->atlTransformations;
+}
+
+class ATLFileHandler extends XmlFileHandler {
+ var $atlTransformations;
+
+ function get_root_element_handler() {
+ return new ATLRootHandler();
+ }
+
+ function end_root_element_handler($handler) {
+ $this->atlTransformations = & $handler->atlTransformations;
+ }
+}
+
+class ATLRootHandler extends XmlElementHandler {
+ var $atlTransformations;
+
+ function & get_atlTransformations_handler($attributes) {
+ return new ListHandler();
+ }
+
+ function end_atlTransformations_handler($handler) {
+ $this->atlTransformations = & $handler->atlTransformations;
+ }
+}
+
+class ListHandler extends XmlElementHandler {
+ var $atlTransformations;
+
+ function ListHandler() {
+ $this->atlTransformations = new ATLTransformationsList();
+ }
+
+ function & get_atlTransformation_handler(& $attributes) {
+ return new ATLHandler();
+ }
+
+ function end_atlTransformation_handler(& $handler) {
+ $this->atlTransformations->add_atlTransformation($handler->atlTransformation);
+ }
+}
+
+class ATLHandler extends XmlElementHandler {
+ var $atlTransformation;
+
+ function ATLHandler() {
+ $this->atlTransformation = new ATLTransformation();
+ }
+
+ function & get_shortName_handler($attributes) {
+ return new SimplePropertyHandler($this->atlTransformation, "shortName");
+ }
+ function & get_name_handler($attributes) {
+ return new SimplePropertyHandler($this->atlTransformation, "name");
+ }
+ function & get_docLink_handler($attributes) {
+ return new SimplePropertyHandler($this->atlTransformation, "docLink");
+ }
+ function & get_sourceLink_handler($attributes) {
+ return new SimplePropertyHandler($this->atlTransformation, "sourceLink");
+ }
+ function & get_description_handler($attributes) {
+ return new ComplexPropertyHandler($this->atlTransformation, "description");
+ }
+ function & get_location_handler($attributes) {
+ return new SimplePropertyHandler($this->atlTransformation, "pubDate");
+ }
+}
+
+?>
\ No newline at end of file
diff --git a/atlTransformations/index.php b/atlTransformations/index.php
new file mode 100644
index 0000000..b9ebeb7
--- /dev/null
+++ b/atlTransformations/index.php
@@ -0,0 +1,41 @@
+<?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'
+
+ #*****************************************************************************
+ #
+ # index.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 = "ATL Transformations";
+ $pageKeywords = "ATL, model transformation, model, metamodel, KM3";
+ $pageAuthor = "Freddy Allilaire";
+
+ # End: page-specific settings
+ #
+
+ include('atlTransformations_script.php');
+ $atlTransformations = getAtlTransformations();
+
+ # Paste your HTML content between the EOHTML markers!
+ $html = <<<EOHTML
+
+ <div id="midcolumn">
+
+ <h1>$pageTitle</h1>
+
+ $atlTransformations
+ </div>
+
+EOHTML;
+
+ # Generate the web page
+ $App->generatePage($theme, $Menu, $Nav, $pageAuthor, $pageKeywords, $pageTitle, $html);
+?>
diff --git a/usecases/BridgeBetweenBuildTools/img/Samples.png b/usecases/BridgeBetweenBuildTools/img/Samples.png
new file mode 100644
index 0000000..bfb300b
--- /dev/null
+++ b/usecases/BridgeBetweenBuildTools/img/Samples.png
Binary files differ
diff --git a/usecases/BridgeBetweenBuildTools/img/UseCaseOverview.png b/usecases/BridgeBetweenBuildTools/img/UseCaseOverview.png
new file mode 100644
index 0000000..251cf2e
--- /dev/null
+++ b/usecases/BridgeBetweenBuildTools/img/UseCaseOverview.png
Binary files differ
diff --git a/usecases/BridgeBetweenBuildTools/index.php b/usecases/BridgeBetweenBuildTools/index.php
new file mode 100644
index 0000000..dc10c31
--- /dev/null
+++ b/usecases/BridgeBetweenBuildTools/index.php
@@ -0,0 +1,194 @@
+<?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.
+ $shortTitle = "Software Build Tools Interoperability (Make, Ant, Maven)";
+ $pageTitle = "ATL Use Case - " . $shortTitle;
+ $pageKeywords = "Build Tools, Ant, Make, Maven";
+ $pageAuthor = "Freddy Allilaire";
+
+ # End: page-specific settings
+ #
+
+ # Paste your HTML content between the EOHTML markers!
+ $html = <<<EOHTML
+
+ <!-- Main part -->
+ <div id="midcolumn">
+ <h1>$pageTitle</h1>
+
+ <img align="right" src="../../resources/atlLogoSmall.png" valign="top" style="padding-left: 10px;" alt="ATL Logo" />
+ <blockquote>
+ <ul>
+ <li><a href="#keywords"><b>Keywords</b></a></li>
+ <li><a href="#overview"><b>Overview</b></a></li>
+ <li><a href="#relatedUseCases"><b>Related Use Cases</b></a></li>
+ <li><a href="#download"><b>Download</b></a></li>
+ <li><a href="#acknowledgement"><b>Acknowledgement</b></a></li>
+ </ul>
+ </blockquote>
+
+ <hr class="clearer" />
+
+ <div id="container>
+ <p align="justify">
+
+ </p>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;"><a name="keywords"></a>Keywords</h4>
+ <table width="100%">
+ <COLGROUP>
+ <COL width="2%" />
+ <COL width="98%" />
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ <p align="justify">
+ Interoperability,
+ <a href="http://en.wikipedia.org/wiki/Build_tool">Build Tools</a>,
+ <a href="http://ant.apache.org/">Ant</a>,
+ <a href="http://www.gnu.org/software/make/manual/html_node/index.html">Make</a>,
+ <a href="http://maven.apache.org/">Maven</a>
+ </p>
+ </td>
+ </tr>
+ </table>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;"><a name="overview"></a>Overview</h4>
+
+ <table width="100%">
+ <COLGROUP>
+ <COL width="2%" />
+ <COL width="98%" />
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ <p align="justify">
+ In this use case we present how to bridge different build tools between themselves: Make, Ant, and Maven.
+ Make, one of the most common build tool, has its own syntax and can be used only on UNIX platform.
+ Ant is platform-independent and its syntax is XML-based. It is extended using Java classes. Maven is an extension proposed in addition to Ant functionalities.
+ It proposes an easier creation of plug-in and it allows more reusability contrary to Ant. Maven need two build files: project.xml (project descriptor), and maven.xml.
+ </p>
+ <p align="justify">
+ In this case study, from a "Make configuration" we will generate a corresponding "Ant configuration" and "Maven configuration".
+ The overall approach is summarized in the following figure:
+ </p>
+ <p align="center">
+ <img src="img/UseCaseOverview.png" />
+ <br /><br />
+ <b>"$shortTitle" Use Case's Overview</b>
+ </p>
+ <p align="justify">
+ For each build tool, we have defined its metamodel by using the <a href="http://wiki.eclipse.org/index.php/KM3">KM3</a> textual format
+ (Ant, Make, Maven). A visual presentation of these metamodels is also available (Ant, Make, Maven).
+ </p>
+ <p align="justify">
+ The Injection and Extraction phases were implemented by using XML bridges. As the Ant and Maven files are XML-based, we can inject an
+ XML-based file or extract into an XML-based file the content of a model (conforms to the XML metamodel). As a Make is not an XML-based tool, we have created an
+ ad-hoc solution to transform a Makefile into a corresponding XML file.
+ </p>
+ <p align="justify">
+ The Model-to-Model transformation phase was implemented by using ATL model-to-model transformations. Following bridges "Make to Ant" and "Ant to Maven" have been developped
+ with ATL.
+ </p>
+ <p align="justify">
+ We provide below a set of screenshots showing the different input/output files provided/created with this use case:
+ </p>
+ <p align="center">
+ <img src="img/Samples.png" />
+ <br /><br />
+ <b>Screenshots of the input/outputs of the use case</b>
+ </p>
+ </td>
+ </tr>
+ </table>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;">
+ <a name="relatedUseCases"></a>Related Use Cases
+ </h4>
+ <table>
+ <COLGROUP>
+ <COL width="2%" />
+ <COL width="98%" />
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ <p align="justify">
+ None at the current time.
+ </p>
+ </td>
+ </tr>
+ </table>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;">
+ <a name="download">Download</a>
+ </h4>
+
+ <table width="100%">
+ <COLGROUP>
+ <COL width="25%">
+ <COL width="75%">
+ </COLGROUP>
+ <tr>
+ <td align="center"><a href="scenario.php"><h3>Complete scenario</h3></a></td>
+ <td>Scenario available in the ATL transformation zoo (with source files).</td>
+ </tr>
+ <tr>
+ <td align="center"><a href="metamodels.php"><h3>Metamodels</h3></a></td>
+ <td>All the provided metamodels are expressed in the Ecore format and also in the <a href="http://wiki.eclipse.org/index.php/KM3">KM3</a> textual format.</td>
+ </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>Acknowledgement
+ </h4>
+
+ <table width="100%">
+ <COLGROUP>
+ <COL width="2%">
+ <COL width="98%">
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ The present work is being supported by the <a href="http://openembedd.inria.fr/home_html-en?set_language=en&cl=en">OpenEmbeDD project</a>,
+ and the <a href="http://www.usine-logicielle.org">Usine Logicielle project of the System@tic Paris Region Cluster</a>.
+ </td>
+ </tr>
+ </table>
+
+ </div>
+ </div>
+
+ <div id="rightcolumn">
+ <div class="sideitem">
+ <h6>General Information</h6>
+ <ul>
+ <li style="list-style:none">February 2007</li>
+ <li style="list-style:none">By <a href="http://www.sciences.univ-nantes.fr/lina/atl/contrib/allilaire">Freddy Allilaire</a>, <a href="http://www.sciences.univ-nantes.fr/lina/atl/contrib/jouault">Frédéric Jouault</a> (INRIA)</li>
+ <li style="list-style:none"><br />Please, ask your questions on the <a href="news://news.eclipse.org/eclipse.modeling.m2m">M2M newsgroup</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/BridgeBetweenBuildTools/metamodels.php b/usecases/BridgeBetweenBuildTools/metamodels.php
new file mode 100644
index 0000000..9e4abe2
--- /dev/null
+++ b/usecases/BridgeBetweenBuildTools/metamodels.php
@@ -0,0 +1,130 @@
+<?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-05
+ #
+ # Description: Type your page comments here - these are not sent to the browser
+ #
+ #
+ #****************************************************************************
+
+ #
+ # Begin: page-specific settings. Change these.
+ $shortTitle = "Software Build Tools Interoperability";
+ $pageTitle = "ATL Use Case - " . $shortTitle . ": Used Metamodels";
+ $pageKeywords = "";
+ $pageAuthor = "Freddy Allilaire";
+
+ # End: page-specific settings
+ #
+
+ # Paste your HTML content between the EOHTML markers!
+ $html = <<<EOHTML
+
+ <!-- Main part -->
+ <div id="midcolumn">
+ <h1>$pageTitle</h1>
+
+ <img align="right" src="../../resources/atlLogoSmall.png" valign="top" style="padding-left: 10px;" alt="ATL Logo" />
+ <p>
+ We provide here the links to all the metamodels which have been developped and/or used within this use case.
+ These metamodels are available resources that may be used within other use cases, in other different contexts or for other purposes.
+ Each of them is provided in the Eclipse Ecore standard format and also in the <a href="http://wiki.eclipse.org/index.php/KM3">KM3</a> textual format.
+ </p>
+
+ <hr class="clearer" />
+
+ <div id="container>
+ <table>
+ <COLGROUP>
+ <COL width="2%">
+ <COL width="98%">
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;">Metamodels</h4>
+
+ <table border="1" frame="lhs" width="80%">
+ <COLGROUP>
+ <COL width="50%">
+ <COL width="50%">
+ </COLGROUP>
+ <tr>
+ <td align="center">
+ <b><font size="3"><i>Ecore</i> format</font></b>
+ </td>
+ <td align="center">
+ <b><font size="3"><i>KM3</i> format</font></b>
+ </td>
+ </tr>
+
+ <tr>
+ <td align="center">
+ <a href="http://www.eclipse.org/gmt/am3/zoos/atlantEcoreZoo/#XML">XML</a>
+ </td>
+ <td align="center">
+ <a href="http://www.eclipse.org/gmt/am3/zoos/atlanticZoo/#XML">XML</a>
+ </td>
+ </tr>
+
+ <tr>
+ <td align="center">
+ <a href="http://www.eclipse.org/gmt/am3/zoos/atlantEcoreZoo/#Ant">Ant</a>
+ </td>
+ <td align="center">
+ <a href="http://www.eclipse.org/gmt/am3/zoos/atlanticZoo/#Ant">Ant</a>
+ </td>
+ </tr>
+
+ <tr>
+ <td align="center">
+ <a href="http://www.eclipse.org/gmt/am3/zoos/atlantEcoreZoo/#Make">Make</a>
+ </td>
+ <td align="center">
+ <a href="http://www.eclipse.org/gmt/am3/zoos/atlanticZoo/#Make">Make</a>
+ </td>
+ </tr>
+
+ <tr>
+ <td align="center">
+ <a href="http://www.eclipse.org/gmt/am3/zoos/atlantEcoreZoo/#Maven%20(maven.xml)">Maven (maven.xml)</a>
+ </td>
+ <td align="center">
+ <a href="http://www.eclipse.org/gmt/am3/zoos/atlanticZoo/#Maven%20(maven.xml)">Maven (maven.xml)</a>
+ </td>
+ </tr>
+
+ <tr>
+ <td align="center">
+ <a href="http://www.eclipse.org/gmt/am3/zoos/atlantEcoreZoo/#Maven%20(project.xml)">Maven (project.xml)</a>
+ </td>
+ <td align="center">
+ <a href="http://www.eclipse.org/gmt/am3/zoos/atlanticZoo/#Maven%20(project.xml)">Maven (project.xml)</a>
+ </td>
+ </tr>
+
+ </table>
+ </td>
+ </tr>
+ </table>
+ </div>
+
+ <hr class="clearer" />
+ <br />
+ <a href="index.php">Back to the "$shortTitle" use case main page »</a>
+ <hr class="clearer" />
+ </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/BridgeBetweenBuildTools/scenario.php b/usecases/BridgeBetweenBuildTools/scenario.php
new file mode 100644
index 0000000..49b1630
--- /dev/null
+++ b/usecases/BridgeBetweenBuildTools/scenario.php
@@ -0,0 +1,90 @@
+<?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-05
+ #
+ # Description: Type your page comments here - these are not sent to the browser
+ #
+ #
+ #****************************************************************************
+
+ #
+ # Begin: page-specific settings. Change these.
+ $shortTitle = "Software Build Tools Interoperability";
+ $pageTitle = "ATL Use Case - " . $shortTitle . ": Complete Scenario";
+ $pageKeywords = "";
+ $pageAuthor = "Freddy Allilaire";
+
+ # End: page-specific settings
+ #
+
+ # Paste your HTML content between the EOHTML markers!
+ $html = <<<EOHTML
+
+ <!-- Main part -->
+ <div id="midcolumn">
+ <h1>$pageTitle</h1>
+
+ <img align="right" src="../../resources/atlLogoSmall.png" valign="top" style="padding-left: 10px;" alt="ATL Logo" />
+ <p>
+ We provide here the links to the different scenarios which have been used to create this complete use case.
+ These scenarios are available from the <a href="http://www.eclipse.org/atl/atlTransformations/">ATL Transformation Zoo</a>.
+ Each of them may be used within other use cases, in other different contexts or for other purposes.
+ </p>
+
+ <hr class="clearer" />
+
+ <div id="container>
+ <table>
+ <COLGROUP>
+ <COL width="2%">
+ <COL width="98%">
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;">List of scenarios used in this use case</h4>
+
+ <table border="1" frame="lhs" width="80%">
+ <tr>
+ <td align="center">
+ <b><font size="3">ATL Scenario</font></b>
+ </td>
+ </tr>
+
+ <tr>
+ <td align="center">
+ <a href="http://www.eclipse.org/atl/atlTransformations/#Make2Ant">Make to Ant</a>
+ </td>
+ </tr>
+
+ <tr>
+ <td align="center">
+ <a href="http://www.eclipse.org/atl/atlTransformations/#Ant2Maven">Ant to Maven</a>
+ </td>
+ </tr>
+
+ </table>
+ </td>
+ </tr>
+ </table>
+ </div>
+
+ <hr class="clearer" />
+ <br />
+ <a href="index.php">Back to the "$shortTitle" use case main page »</a>
+ <hr class="clearer" />
+ </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/BridgeRDBSchemaToMetamodel/img/Sample.png b/usecases/BridgeRDBSchemaToMetamodel/img/Sample.png
new file mode 100644
index 0000000..71f094a
--- /dev/null
+++ b/usecases/BridgeRDBSchemaToMetamodel/img/Sample.png
Binary files differ
diff --git a/usecases/BridgeRDBSchemaToMetamodel/img/UseCaseOverview.png b/usecases/BridgeRDBSchemaToMetamodel/img/UseCaseOverview.png
new file mode 100644
index 0000000..485af2d
--- /dev/null
+++ b/usecases/BridgeRDBSchemaToMetamodel/img/UseCaseOverview.png
Binary files differ
diff --git a/usecases/BridgeRDBSchemaToMetamodel/index.php b/usecases/BridgeRDBSchemaToMetamodel/index.php
new file mode 100644
index 0000000..10ef797
--- /dev/null
+++ b/usecases/BridgeRDBSchemaToMetamodel/index.php
@@ -0,0 +1,179 @@
+<?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.
+ $shortTitle = "Bridge between Relational Database Schema And Metamodel";
+ $pageTitle = "ATL Use Case - " . $shortTitle;
+ $pageKeywords = "";
+ $pageAuthor = "Freddy Allilaire";
+
+ # End: page-specific settings
+ #
+
+ # Paste your HTML content between the EOHTML markers!
+ $html = <<<EOHTML
+
+ <!-- Main part -->
+ <div id="midcolumn">
+ <h1>$pageTitle</h1>
+
+ <img align="right" src="../../resources/atlLogoSmall.png" valign="top" style="padding-left: 10px;" alt="ATL Logo" />
+ <blockquote>
+ <ul>
+ <li><a href="#keywords"><b>Keywords</b></a></li>
+ <li><a href="#overview"><b>Overview</b></a></li>
+ <li><a href="#relatedUseCases"><b>Related Use Cases</b></a></li>
+ <li><a href="#download"><b>Download</b></a></li>
+ <li><a href="#acknowledgement"><b>Acknowledgement</b></a></li>
+ </ul>
+ </blockquote>
+
+ <hr class="clearer" />
+
+ <div id="container>
+ <p align="justify">
+
+ </p>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;"><a name="keywords"></a>Keywords</h4>
+ <table width="100%">
+ <COLGROUP>
+ <COL width="2%" />
+ <COL width="98%" />
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ <p align="justify">
+ RDBMS,
+ Relation Database Schema,
+ <a href="http://www.mysql.com/">MySQL</a>,
+ <a href="http://www.eclipse.org/gmt/am3/zoos/atlanticZoo/#KM3">KM3</a>,
+ Metamodel
+ </p>
+ </td>
+ </tr>
+ </table>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;"><a name="overview"></a>Overview</h4>
+
+ <table width="100%">
+ <COLGROUP>
+ <COL width="2%" />
+ <COL width="98%" />
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ <p align="justify">
+ This use case aims to demonstrate the possibility to translate data structure description from the <i>RDBMS world</i> to the modeling technical space.
+ From the schema of a relational database we create the corresponding metamodel.
+ For this purpose, we have considered the open source MySQL RDBMS system as the database platform, and the KM3 notation as the metamodel description tool.
+ The overall approach is summarized in the following figure:
+ </p>
+ <p align="center">
+ <img src="img/UseCaseOverview.png" />
+ <br /><br />
+ <b>"$shortTitle" Use Case's Overview</b>
+ </p>
+ <p align="justify">
+ The XML description of a MySQL database can be obtained using the MyDB Studio tool.
+ This tool enables to export the structure of a table into a dedicated .xml file.
+ <p align="justify">
+ The Model-to-Model transformation phase was implemented by using ATL model-to-model transformations.
+ </p>
+ <p align="justify">
+ We provide below a set of screenshots showing the different input/output files provided/created with this use case:
+ </p>
+ <p align="center">
+ <img src="img/Sample.png" />
+ <br /><br />
+ <b>Screenshots of the input/outputs of the use case</b>
+ </p>
+ </td>
+ </tr>
+ </table>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;">
+ <a name="relatedUseCases"></a>Related Use Cases
+ </h4>
+ <table>
+ <COLGROUP>
+ <COL width="2%" />
+ <COL width="98%" />
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ <p align="justify">
+ <a href="http://www.eclipse.org/gmt/modisco/useCases/RelationalDBSchema/">MoDisco Use Case - Relational Database Schema</a>
+ </p>
+ </td>
+ </tr>
+ </table>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;">
+ <a name="download">Download</a>
+ </h4>
+
+ <table width="100%">
+ <COLGROUP>
+ <COL width="25%">
+ <COL width="75%">
+ </COLGROUP>
+ <tr>
+ <td align="center"><a href="http://www.eclipse.org/atl/atlTransformations/#MySQL2KM3"><h3>Complete scenario</h3></a></td>
+ <td>Scenario available in the ATL transformation zoo (with source files).</td>
+ </tr>
+ <tr>
+ <td align="center"><a href="http://www.eclipse.org/gmt/am3/zoos/atlanticZoo/#KM3"><h3>KM3 Metamodel</h3></a></td>
+ <td>KM3 metamodel is expressed in the <a href="http://wiki.eclipse.org/index.php/KM3">KM3</a> textual format.</td>
+ </tr>
+ <tr>
+ <td align="center"><a href="http://www.eclipse.org/gmt/am3/zoos/atlanticZoo/#MySQL"><h3>MySQL Metamodel</h3></a></td>
+ <td>MySQL metamodel is expressed in the <a href="http://wiki.eclipse.org/index.php/KM3">KM3</a> textual format.</td>
+ </tr>
+ <tr>
+ <td align="center"><a href="http://www.eclipse.org/gmt/am3/zoos/atlanticZoo/#XML"><h3>XML Metamodel</h3></a></td>
+ <td>XML metamodel is expressed in the <a href="http://wiki.eclipse.org/index.php/KM3">KM3</a> textual format.</td>
+ </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>Acknowledgement
+ </h4>
+
+ <table width="100%">
+ <COLGROUP>
+ <COL width="2%">
+ <COL width="98%">
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ The present work is being supported by the <a href="http://www.usine-logicielle.org">Usine Logicielle project of the System@tic Paris Region Cluster</a>.
+ </td>
+ </tr>
+ </table>
+
+ </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/BridgingGrafcetPetrinetPNML/img/Sample.png b/usecases/BridgingGrafcetPetrinetPNML/img/Sample.png
new file mode 100644
index 0000000..dd2ec1a
--- /dev/null
+++ b/usecases/BridgingGrafcetPetrinetPNML/img/Sample.png
Binary files differ
diff --git a/usecases/BridgingGrafcetPetrinetPNML/img/UseCaseOverview.png b/usecases/BridgingGrafcetPetrinetPNML/img/UseCaseOverview.png
new file mode 100644
index 0000000..82a01e3
--- /dev/null
+++ b/usecases/BridgingGrafcetPetrinetPNML/img/UseCaseOverview.png
Binary files differ
diff --git a/usecases/BridgingGrafcetPetrinetPNML/index.php b/usecases/BridgingGrafcetPetrinetPNML/index.php
new file mode 100644
index 0000000..9b66c9b
--- /dev/null
+++ b/usecases/BridgingGrafcetPetrinetPNML/index.php
@@ -0,0 +1,200 @@
+<?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.
+ $shortTitle = "Bridging Grafcet, Petrinet, and PNML";
+ $pageTitle = "ATL Use Case - " . $shortTitle;
+ $pageKeywords = "";
+ $pageAuthor = "Freddy Allilaire";
+
+ # End: page-specific settings
+ #
+
+ # Paste your HTML content between the EOHTML markers!
+ $html = <<<EOHTML
+
+ <!-- Main part -->
+ <div id="midcolumn">
+ <h1>$pageTitle</h1>
+
+ <img align="right" src="../../resources/atlLogoSmall.png" valign="top" style="padding-left: 10px;" alt="ATL Logo" />
+ <blockquote>
+ <ul>
+ <li><a href="#keywords"><b>Keywords</b></a></li>
+ <li><a href="#overview"><b>Overview</b></a></li>
+ <li><a href="#relatedUseCases"><b>Related Use Cases</b></a></li>
+ <li><a href="#download"><b>Download</b></a></li>
+ <li><a href="#acknowledgement"><b>Acknowledgement</b></a></li>
+ </ul>
+ </blockquote>
+
+ <hr class="clearer" />
+
+ <div id="container>
+ <p align="justify">
+
+ </p>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;"><a name="keywords"></a>Keywords</h4>
+ <table width="100%">
+ <COLGROUP>
+ <COL width="2%" />
+ <COL width="98%" />
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ <p align="justify">
+ Petrinet,
+ Grafcet,
+ PNML
+ </p>
+ </td>
+ </tr>
+ </table>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;"><a name="overview"></a>Overview</h4>
+
+ <table width="100%">
+ <COLGROUP>
+ <COL width="2%" />
+ <COL width="98%" />
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ <p align="justify">
+ This use case provides a complete bridge between Grafcet, Petri Net and PNML.
+ Petri net representation (in the PNML format) from a textual definition of a Grafcet and in the opposite way.
+ </p>
+ <p align="justify">
+ Grafcet is a mainly French-based representation support for discrete system. It is a mode of
+ representation and analysis of an automatism, particularly adapted to sequential systems with
+ evolution, i.e. decomposable in steps. The Grafcet's name came from "graph" because this model
+ had a graphic basis, and AFCET (Association francaise de cybernetique economique et technique)
+ from the scientific association which supported it. The Grafcet represents graphically the operation of
+ an automatism by: steps with associated action, transitions between steps, and directed connections
+ between the steps and the transitions.
+ </p>
+ <p align="justify">
+ Petri nets are also known as a place/transition net or P/T net. Defined in 1962 by Carl Adam Petri,
+ they extend state machines with a notion of concurrency. It is a graphical and mathematical
+ representation of discrete distributed systems. Petri nets consist of places, transitions and directed
+ arcs that connect them, so arcs run between places and transitions, not between places and places or
+ transitions and transitions. There are two sorts of arcs connecting place to transition or transition to place.
+ </p>
+ <p align="justify">
+ The Petri Net Markup Language (PNML) is a proposal of an XML-based interchange format for Petri
+ nets. Originally, it was intended to serve as a file format for the Java version of the Petri Net
+ Kernel. PNML is a concept for defining the overall structure of a Petri net file.
+ </p>
+ <p align="justify">
+ The overall approach is summarized in the following figure:
+ </p>
+ <p align="center">
+ <img src="img/UseCaseOverview.png" />
+ <br /><br />
+ <b>"$shortTitle" Use Case's Overview</b>
+ </p>
+ <p align="justify">
+ The Model-to-Model transformation phase was implemented by using ATL model-to-model transformations.
+ </p>
+ <p align="justify">
+ We provide below a set of screenshots showing the different input/output files provided/created with this use case:
+ </p>
+ <p align="center">
+ <img src="img/Sample.png" />
+ <br /><br />
+ <b>Screenshots of the input/outputs of the use case</b>
+ </p>
+ </td>
+ </tr>
+ </table>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;">
+ <a name="relatedUseCases"></a>Related Use Cases
+ </h4>
+ <table>
+ <COLGROUP>
+ <COL width="2%" />
+ <COL width="98%" />
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ <p align="justify">
+ None at the current time.
+ </p>
+ </td>
+ </tr>
+ </table>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;">
+ <a name="download">Download</a>
+ </h4>
+
+ <table width="100%">
+ <COLGROUP>
+ <COL width="25%">
+ <COL width="75%">
+ </COLGROUP>
+ <tr>
+ <td align="center"><a href="http://www.eclipse.org/atl/atlTransformations/#Grafcet2PetriNet"><h3>Complete scenario</h3></a></td>
+ <td>Scenario available in the ATL transformation zoo (with source files).</td>
+ </tr>
+ <tr>
+ <td align="center"><a href="http://www.eclipse.org/gmt/am3/zoos/atlanticZoo/#GRAFCET"><h3>Grafcet Metamodel</h3></a></td>
+ <td>KM3 metamodel is expressed in the <a href="http://wiki.eclipse.org/index.php/KM3">KM3</a> textual format.</td>
+ </tr>
+ <tr>
+ <td align="center"><a href="http://www.eclipse.org/gmt/am3/zoos/atlanticZoo/#PNML_basic"><h3>PNML basic Metamodel</h3></a></td>
+ <td>PNML metamodel is expressed in the <a href="http://wiki.eclipse.org/index.php/KM3">KM3</a> textual format.</td>
+ </tr>
+ <tr>
+ <td align="center"><a href="http://www.eclipse.org/gmt/am3/zoos/atlanticZoo/#PetriNet"><h3>PetriNet Metamodel</h3></a></td>
+ <td>PetriNet metamodel is expressed in the <a href="http://wiki.eclipse.org/index.php/KM3">KM3</a> textual format.</td>
+ </tr>
+ <tr>
+ <td align="center"><a href="http://www.eclipse.org/gmt/am3/zoos/atlanticZoo/#XML"><h3>XML Metamodel</h3></a></td>
+ <td>XML metamodel is expressed in the <a href="http://wiki.eclipse.org/index.php/KM3">KM3</a> textual format.</td>
+ </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>Acknowledgement
+ </h4>
+
+ <table width="100%">
+ <COLGROUP>
+ <COL width="2%">
+ <COL width="98%">
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ The present work is being supported by the <a href="http://www.usine-logicielle.org">Usine Logicielle project of the System@tic Paris Region Cluster</a>.
+ </td>
+ </tr>
+ </table>
+
+ </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/DSLsTelephony/AMMA-SPL&CPL.png b/usecases/DSLsTelephony/AMMA-SPL&CPL.png
new file mode 100644
index 0000000..d91f360
--- /dev/null
+++ b/usecases/DSLsTelephony/AMMA-SPL&CPL.png
Binary files differ
diff --git a/usecases/DSLsTelephony/CPL2SPL-fullScenario.png b/usecases/DSLsTelephony/CPL2SPL-fullScenario.png
new file mode 100644
index 0000000..af3067e
--- /dev/null
+++ b/usecases/DSLsTelephony/CPL2SPL-fullScenario.png
Binary files differ
diff --git a/usecases/DSLsTelephony/CPL2SPL.png b/usecases/DSLsTelephony/CPL2SPL.png
new file mode 100644
index 0000000..49006db
--- /dev/null
+++ b/usecases/DSLsTelephony/CPL2SPL.png
Binary files differ
diff --git a/usecases/DSLsTelephony/CPLMetamodel.png b/usecases/DSLsTelephony/CPLMetamodel.png
new file mode 100644
index 0000000..5e710d2
--- /dev/null
+++ b/usecases/DSLsTelephony/CPLMetamodel.png
Binary files differ
diff --git a/usecases/DSLsTelephony/SPLMetamodel.png b/usecases/DSLsTelephony/SPLMetamodel.png
new file mode 100644
index 0000000..316310a
--- /dev/null
+++ b/usecases/DSLsTelephony/SPLMetamodel.png
Binary files differ
diff --git a/usecases/DSLsTelephony/SimpleCPLScript.png b/usecases/DSLsTelephony/SimpleCPLScript.png
new file mode 100644
index 0000000..87c05a0
--- /dev/null
+++ b/usecases/DSLsTelephony/SimpleCPLScript.png
Binary files differ
diff --git a/usecases/DSLsTelephony/SimpleSPLProgram.png b/usecases/DSLsTelephony/SimpleSPLProgram.png
new file mode 100644
index 0000000..6e3fdbb
--- /dev/null
+++ b/usecases/DSLsTelephony/SimpleSPLProgram.png
Binary files differ
diff --git a/usecases/DSLsTelephony/XML2CPL.png b/usecases/DSLsTelephony/XML2CPL.png
new file mode 100644
index 0000000..b55d2c9
--- /dev/null
+++ b/usecases/DSLsTelephony/XML2CPL.png
Binary files differ
diff --git a/usecases/DSLsTelephony/index.php b/usecases/DSLsTelephony/index.php
new file mode 100644
index 0000000..f68d8f5
--- /dev/null
+++ b/usecases/DSLsTelephony/index.php
@@ -0,0 +1,305 @@
+<?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 = "ATL Use Case - DSLs coordination for Telephony";
+ $pageKeywords = "Telephony, SIP, CPL, SPL";
+ $pageAuthor = "Freddy Allilaire";
+
+ # End: page-specific settings
+ #
+
+ # Paste your HTML content between the EOHTML markers!
+ $html = <<<EOHTML
+
+ <!-- Main part -->
+ <div id="midcolumn">
+ <h1>$pageTitle</h1>
+
+ <img align="right" src="../../resources/atlLogoSmall.png" valign="top" style="padding-left: 10px;" alt="ATL Logo" />
+ <blockquote>
+ <ul>
+ <li><a href="#keywords"><b>Keywords</b></a></li>
+ <li><a href="#overview"><b>Overview</b></a></li>
+ <li><a href="#relatedUseCases"><b>Related Use Cases</b></a></li>
+ <li><a href="#references"><b>References</b></a></li>
+ <li><a href="#download"><b>Download</b></a></li>
+ <li><a href="#acknowledgement"><b>Acknowledgement</b></a></li>
+ </ul>
+ </blockquote>
+
+ <hr class="clearer" />
+
+ <div>
+ <p align="justify">
+ This work presents a case study of implementing two telephony languages: SPL and CPL. We show how it is possible to transform programs of one language into the
+ other one with the help of model engineering. This work has been done in collaboration between <a href="http://www.sciences.univ-nantes.fr/lina/atl/">ATLAS Group</a>
+ in Nantes and the <a href="http://phoenix.labri.fr/">PHOENIX Group</a> in Bordeaux.
+ </p>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;"><a name="keywords"></a>Keywords</h4>
+ <table width="100%">
+ <COLGROUP>
+ <COL width="2%" />
+ <COL width="98%" />
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ <p align="justify">
+ Telephony,
+ <a href="http://www.ietf.org/rfc/rfc3261.txt">SIP</a>,
+ <a href="http://www.faqs.org/rfcs/rfc3880.html">CPL</a>,
+ <a href="http://phoenix.labri.fr/software/spl/">SPL</a>.
+ </p>
+ </td>
+ </tr>
+ </table>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;"><a name="overview"></a>Overview</h4>
+
+ <table width="100%">
+ <COLGROUP>
+ <COL width="2%" />
+ <COL width="98%" />
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ <p align="justify">
+ In this work, we report on an experiment consisting of the implementation
+ of two languages specific to the domain of internet telephony. The first one is SPL (Session Processing Language), and the second
+ one is CPL (Call Processing Language). The outcome of this experiment provides an interesting example of DSL coordination. Three aspects of each DSL are taken into
+ account: abstract syntax, concrete syntax, and dynamic semantics. Moreover, our case study allows for different approaches to be illustrated.
+ SPL has a textual concrete syntax whereas CPL is XMLbased. Additionally, both languages being in the same domain, one can be defined using the other.
+ </p>
+ <p align="justify">
+ SPL and CPL are both in the application area of telephony. They are partially based on similar vocabularies.
+ However they are very different and have been designed to be used by different people.
+ </p>
+ <p align="justify">
+ In this use case, <a href="http://wiki.eclipse.org/index.php/AMMA">AMMA</a> and three of its core DSLs:
+ <a href="http://wiki.eclipse.org/index.php/KM3">KM3</a>, <a href="../../">ATL</a>, and <a href="http://wiki.eclipse.org/index.php/TCS">TCS</a> will be used.
+ AMMA is built on a model-based vision of DSLs. AMMA provides a set of core DSLs that may be used to specify new DSLs.
+ </p>
+ <p align="justify">
+ <b>SPL</b> (Session Processing Language) programs are used to control telephony agents (e.g. clients, proxies) implementing the SIP (Session Initiation Protocol)
+ protocol. SIP concepts are directly available in the language. Consequently, SPL programs are able to concisely and simply express
+ any telephony service. Additionally, SPL is capable of guaranteeing critical properties that could not be verified with a GPL. SPL
+ programs run on a Service Logic Execution Environment for SIP.
+ </p>
+ <p align="center">
+ <img src="SimpleSPLProgram.png" />
+ <br /><br />
+ <b>Simple SPL program: forwarding a call</b>
+ </p>
+
+ <p align="justify">
+ Every incoming call is redirected to SIP address sip:phoenix@barbade.enseirb.fr. The target address is declared on line 3. Lines 6-8
+ correspond to the definition of the action to perform on incoming calls. The return statement at line 7 forwards the call. The abstract syntax is specified
+ in KM3. The following figure is an excerpt of the SPL metamodel.
+ </p>
+ <p align="center">
+ <img src="SPLMetamodel.png" />
+ <br /><br />
+ <b>SPL metamodel excerpt</b>
+ </p>
+ <p align="justify">
+ Concrete syntax of SPL has been implemented in TCS. A grammar is automatically derived from both the KM3 metamodel and the TCS model to parse SPL programs into SPL models.
+ </p>
+ <p align="justify">
+ <b>CPL</b> (Call Processing Language) is a standard scripting language for the SIP protocol. It offers a limited set of language constructs. CPL is supposed to
+ be simple enough so that it is safe to execute untrusted scripts on public servers. The following figure gives a CPL example, which is equivalent
+ to the SPL example given.
+ </p>
+ <p align="center">
+ <img src="SimpleCPLScript.png" />
+ <br /><br />
+ <b>Simple CPL script: forwarding a call</b>
+ </p>
+ <p align="justify">
+ As for SPL, the abstract syntax of CPL is specified in KM3. The following figure is an excerpt of the CPL metamodel.
+ </p>
+ <p align="center">
+ <img src="CPLMetamodel.png" />
+ <br /><br />
+ <b>CPL metamodel excerpt</b>
+ </p>
+ <p align="justify">
+ Both CPL concrete syntax and semantics are handled by model transformations in ATL.
+ CPL concrete syntax is XML-based. TCS is therefore not really useful here. The solution we implemented is the following.
+ We use a generic XML parser to go from the XML document to an XML model conforming to an XML metamodel. This has an
+ extremely low cost since these XML parser and metamodel are provided as part of AMMA. In a second step, we transform our
+ XML model into a CPL model using ATL. The following figure gives
+ an excerpt of this XML2CPL transformation. It transforms an XML model into a CPL model (line 2) by using a library of
+ XML helpers (line 4) providing the getElemsByNames operation on XML elements. A single rule is shown: rule CPL (lines 6-17),
+ which transforms the root of the XML document into a CPL element. Nested incoming element is attached to this root (lines 13-15).
+ </p>
+ <p align="center">
+ <img src="XML2CPL.png" />
+ <br /><br />
+ <b>XML to CPL transformation excerpt, written in ATL</b>
+ </p>
+ <p align="justify">
+ A second transformation (CPL2SPL) provides an implementation of CPL semantics by translating CPL concepts into their SPL
+ equivalent concepts. The following figure provides an excerpt of this
+ transformation. Line 2 declares source and target models respectively conforming to CPL and SPL. Rule CPL2Program (lines 4-
+ 19) transforms the root CPL element (lines 5-6) into an SPL program (lines 8-10), an unnamed service (lines 11-15) and a dialog (lines 16-18).
+ </p>
+ <p align="center">
+ <img src="CPL2SPL.png"/>
+ <br /><br />
+ <b>CPL to SPL transformation excerpt, written in ATL</b>
+ </p>
+ <p align="justify">
+ The CPL script Sample.cpl conforming to the CPL schema is first translated
+ into an XML model conforming to an XML metamodel. Then it is transformed into a CPL model by XML2CPL.atl. The core
+ transformation CPL2SPL.atl is then applied to generate an SPL model. The latter is then serialized into an SPL program using
+ the TCS interpreter on the TCS syntax definition of SPL. This full transformation scenario (called CPL2SPL) is available in the ATL transformation zoo.
+ </p>
+
+ <p align="center">
+ <a href="CPL2SPL-fullScenario.png"><img src="CPL2SPL-fullScenario.png" width="700"/></a>
+ <br />
+ <b>Full CPL to SPL transformation scenario</b>
+ </p>
+
+ <p align="justify">
+ This case study illustrates how AMMA core DSLs can be used to capture different facets of a DSL. KM3 is used to express
+ Domain Definition MetaModels. Concrete syntaxes are defined in TCS. Dynamic semantics can be formally defined in ASM, which we have done for ATL and SPL.
+ Moreover, transformations from any DSLa to any DSLb can be implemented in ATL. This can, for instance, be used to implement
+ the semantics of DSLa in terms of the semantics of DSLb (e.g. from CPL to SPL, see section 4.3). Such a transformation may
+ then be used to translate programs expressed in DSLa into programs expressed in DSLb. Another use of ATL is to implement
+ concrete syntaxes of DSLs.
+ </p>
+ </td>
+ </tr>
+ </table>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;">
+ <a name="relatedUseCases"></a>Related Use Cases
+ </h4>
+ <table>
+ <COLGROUP>
+ <COL width="2%" />
+ <COL width="98%" />
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ <p align="justify">
+ None at the current time.
+ </p>
+ </td>
+ </tr>
+ </table>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;">
+ <a name="references"></a>References
+ </h4>
+
+ <table width="100%">
+ <tr valign="top">
+ <td>
+ <a href="http://www.sciences.univ-nantes.fr/lina/atl/bibliography/DSPD06">
+ [1]
+ </a>
+ </td>
+ <td>
+ Jouault, F, Bézivin, J, Consel, C, Kurtev, I, and Latry, F:
+ <em>Building DSLs with AMMA/ATL, a Case Study on SPL and CPL Telephony Languages</em>.
+ In: Proceedings of the 1st ECOOP Workshop on Domain-Specific Program Development (DSPD), July 3rd, Nantes, France. 2006.
+ </td>
+ </tr>
+ <tr valign="top">
+ <td>
+ <a href="http://www.sciences.univ-nantes.fr/lina/atl/bibliography/Jouault06">
+ [2]
+ </a>
+ </td>
+ <td>
+ Jouault, F:
+ <em>Contribution à l'étude des langages de transformation de modèles</em>,
+ Phd thesis, Université de Nantes. 2006.
+ </td>
+ </tr>
+ </table>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;">
+ <a name="download">Download</a>
+ </h4>
+
+ <table width="100%">
+ <COLGROUP>
+ <COL width="25%">
+ <COL width="75%">
+ </COLGROUP>
+ <tr>
+ <td align="center"><a href="http://www.eclipse.org/atl/atlTransformations/#CPL2SPL"><h3>Complete scenario</h3></a></td>
+ <td>Scenario CPL to SPL available in the ATL transformation zoo (with source files).</td>
+ </tr>
+ <tr>
+ <td align="center"><a href="http://www.eclipse.org/gmt/am3/zoos/atlanticZoo/#CPL"><h3>CPL metamodel</h3></a></td>
+ <td>Full CPL metamodel specified in KM3.</td>
+ </tr>
+ <tr>
+ <td align="center"><a href="http://www.eclipse.org/gmt/am3/zoos/atlanticZoo/#SPL"><h3>SPL metamodel</h3></a></td>
+ <td>Full SPL metamodel specified in KM3.</td>
+ </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>Acknowledgement
+ </h4>
+
+ <table width="100%">
+ <COLGROUP>
+ <COL width="2%">
+ <COL width="98%">
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ The present work is being supported by the <a href="http://www.modelplex-ist.org/">ModelPlex european project</a>,
+ the FLFS ANRT project (Families of Language for Families of Systems),
+ the <a href="http://openembedd.inria.fr/home_html-en?set_language=en&cl=en">OpenEmbeDD project</a>,
+ and the <a href="http://www.usine-logicielle.org">Usine Logicielle project of the System@tic Paris Region Cluster</a>.
+ </td>
+ </tr>
+ </table>
+
+ </div>
+ </div>
+
+ <div id="rightcolumn">
+ <div class="sideitem">
+ <h6>General Information</h6>
+ <ul>
+ <li style="list-style:none">February 2007</li>
+ <li style="list-style:none">
+ By <a href="http://www.sciences.univ-nantes.fr/lina/atl/contrib/allilaire">Freddy Allilaire</a> and
+ <a href="http://www.sciences.univ-nantes.fr/lina/atl/contrib/jouault">Frédéric Jouault</a> (INRIA)
+ </li>
+ <li style="list-style:none"><br />Please, ask your questions on the <a href="news://news.eclipse.org/eclipse.modeling.m2m">M2M newsgroup</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/FIACRE2LOTOS/FIACRE-Simple_enum.png b/usecases/FIACRE2LOTOS/FIACRE-Simple_enum.png
new file mode 100644
index 0000000..b251409
--- /dev/null
+++ b/usecases/FIACRE2LOTOS/FIACRE-Simple_enum.png
Binary files differ
diff --git a/usecases/FIACRE2LOTOS/LOTOS-Simple_enum.png b/usecases/FIACRE2LOTOS/LOTOS-Simple_enum.png
new file mode 100644
index 0000000..58648ed
--- /dev/null
+++ b/usecases/FIACRE2LOTOS/LOTOS-Simple_enum.png
Binary files differ
diff --git a/usecases/FIACRE2LOTOS/LOTOS-TGE.png b/usecases/FIACRE2LOTOS/LOTOS-TGE.png
new file mode 100644
index 0000000..9315075
--- /dev/null
+++ b/usecases/FIACRE2LOTOS/LOTOS-TGE.png
Binary files differ
diff --git a/usecases/FIACRE2LOTOS/index.php b/usecases/FIACRE2LOTOS/index.php
new file mode 100644
index 0000000..058925e
--- /dev/null
+++ b/usecases/FIACRE2LOTOS/index.php
@@ -0,0 +1,255 @@
+<?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 = "ATL Use Case - Compiling a new formal verification language to LOTOS (ISO 8807)";
+ $pageKeywords = "LOTOS, ISO 8807, FIACRE, formal verification, model-checking";
+ $pageAuthor = "Frédéric Jouault";
+
+ # End: page-specific settings
+ #
+
+ # Paste your HTML content between the EOHTML markers!
+ $html = <<<EOHTML
+
+ <!-- Main part -->
+ <div id="midcolumn">
+ <h1>$pageTitle</h1>
+
+ <img align="right" src="../../resources/atlLogoSmall.png" valign="top" style="padding-left: 10px;" alt="ATL Logo" />
+ <blockquote>
+ <ul>
+ <li><a href="#keywords"><b>Keywords</b></a></li>
+ <li><a href="#overview"><b>Overview</b></a></li>
+ <li><a href="#relatedUseCases"><b>Related Use Cases</b></a></li>
+ <li><a href="#download"><b>Download</b></a></li>
+ <li><a href="#acknowledgement"><b>Acknowledgement</b></a></li>
+ </ul>
+ </blockquote>
+
+ <hr class="clearer" />
+
+ <div>
+ <p align="justify">
+ <p>
+ In this use case, we translate <a href="http://www-sop.inria.fr/oasis/fiacre/">FIACRE</a> programs into
+ <a href="http://www.inrialpes.fr/vasy/cadp/">LOTOS</a> (<a href="http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=16258">ISO 8807</a>) programs.
+ This work is the result of the cooperation of two INRIA teams: <a href="http://www.sciences.univ-nantes.fr/lina/atl/">ATLAS</a> (Nantes), and <a href="http://www.inrialpes.fr/vasy/">VASY</a> (Grenoble),
+ in the context of the <a href="http://openembedd.inria.fr/">OpenEmbeDD</a> project.
+ </p>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;"><a name="keywords"></a>Keywords</h4>
+ <table width="100%">
+ <COLGROUP>
+ <COL width="2%" />
+ <COL width="98%" />
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ <p align="justify">
+ <a href="http://www.inrialpes.fr/vasy/cadp/">LOTOS</a>,
+ <a href="http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=16258">ISO 8807</a>,
+ <a href="http://www-sop.inria.fr/oasis/fiacre/">FIACRE</a>,
+ <a href="http://en.wikipedia.org/wiki/Formal_verification">formal verification</a>,
+ <a href="http://en.wikipedia.org/wiki/Model-checking">model-checking</a>.
+ </p>
+ </td>
+ </tr>
+ </table>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;"><a name="overview"></a>Overview</h4>
+
+ <table width="100%">
+ <COLGROUP>
+ <COL width="2%" />
+ <COL width="98%" />
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ <p align="justify">
+ <a href="http://www-sop.inria.fr/oasis/fiacre/">FIACRE</a> (french acronym of: Format Intermédiaire pour les Architectures de Composants Répartis Embarqués,
+ meaning: Intermediate Format for the Architectures of Embedded Distributed Components) is a new intermediate language for the formal description and verification of asynchronous concurrent systems.
+ In this work, we define a compiler from FIACRE to <a href="http://www.inrialpes.fr/vasy/cadp/">LOTOS</a> (Language Of Temporal Ordering Specification, <a href="http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=16258">ISO 8807</a>) using Model Engineering techniques.
+ The output of this compiler can then be verified using the <a href="http://www.inrialpes.fr/vasy/cadp/">CADP</a> toolbox.
+ The abstract syntax of each language is defined in <a href="http://wiki.eclipse.org/KM3">KM3</a>, and the concrete syntax in <a href="http://wiki.eclipse.org/TCS">TCS</a>.
+ The translation from FIACRE to LOTOS is defined as an <a href="http://wiki.eclipse.org/ATL">ATL</a> <a href="http://wiki.eclipse.org/M2M">model-to-model</a> transformation.
+ </p>
+ <p align="justify">
+ The current version is able to translate FIACRE types (e.g., enumerations, intervals, arrays), which definitions are relatively concise, into
+ equivalent LOTOS types, which definitions are typically more verbose.
+ For instance, the sample FIACRE program given in Figure 1 is automatically transformed into the LOTOS program given in Figure 2.
+ Note that both programs are presented as screenshots of TGE (Textual Generic Editor), the TCS-based editor.
+ This shows that once the concrete syntax of a language has been defined in TCS, TGE can be used to automatically provide a language-specific editor.
+ </p>
+ <p align="center">
+ <img src="FIACRE-Simple_enum.png" />
+ <br /><br />
+ <b>Figure 1. Simple FIACRE enumeration as seen in TGE</b>
+ </p>
+ <p align="center">
+ <a href="LOTOS-Simple_enum.png"><img src="LOTOS-Simple_enum.png" width="80%"/></a>
+ <br /><br />
+ <b>Figure 2. LOTOS type generated from the simple FIACRE enumeration (click picture for larger version)</b>
+ </p>
+ <p align="justify">
+ Although only types are transformed at the current time, the definitions (abstract and concrete syntaxes) of FIACRE and LOTOS cover larger parts of the languages.
+ For instance, Figure 3 shows how TGE can edit one of the LOTOS examples.
+ </p>
+ <p align="center">
+ <a href="LOTOS-TGE.png"><img src="LOTOS-TGE.png" width="80%"/></a>
+ <br /><br />
+ <b>Figure 3. The <a href="ftp://ftp.inrialpes.fr/pub/vasy/demos/demo_01/bitalt.lotos">bitalt.lotos</a> LOTOS example edited in TGE (click picture for larger version)</b>
+ </p>
+ <p align="justify">
+ We also created a <a href="http://www.sciences.univ-nantes.fr/lina/atl/atldemo/fiacre2lotos/">web service</a> to use this transformation scenario, so that it can be tested and used without having to install Eclipse.
+ You can see below a sample output of this web service invoked on the same sample FIACRE program as used in Figure 1.
+ </p>
+ <p align="center">
+ <b>Compilaton of a simple FIACRE enumeration into a LOTOS type with the <a href="http://www.sciences.univ-nantes.fr/lina/atl/atldemo/fiacre2lotos/">FIACRE2LOTOS web service</a></b>
+ </p>
+ <style>
+ .keyword {color: #7F0055; font-weight: bold;}
+ .comment {color: #008200; font-weight: italic;}
+ .string {color: #0000FF;}
+ .symbol {color: #7F0055; font-weight: bold;}
+ .error {border-bottom: #FF0000 1px solid;}
+ .lineWithError {color: #FF0000; font-weight: bold;}
+ .selection {color: white; background-color: #0A246A;}
+ </style>
+ <h2>Source: FIACRE Model </h2>
+<pre>1 <span class="keyword">type</span><span class="whitespace"> </span><span class="identifier">test</span><span class="whitespace"> </span><span class="keyword">is</span><span class="whitespace">
+2 </span><span class="keyword">enum</span><span class="whitespace"> </span><span class="identifier">a</span><span class="symbol">,</span><span class="whitespace"> </span><span class="identifier">b</span><span class="symbol">,</span><span class="whitespace"> </span><span class="identifier">c</span><span class="whitespace"> </span><span class="keyword">end</span><span class="whitespace">
+
+</span></pre>
+<hr>
+<h2>Target: LOTOS Model </h2>
+<pre>1 <span class="comment">(* ---------------------------------------------------------------------------- *)</span><span class="whitespace">
+</span>2 <span class="comment">(* Author: FIACRE2LOTOS.atl *)</span><span class="whitespace">
+</span>3 <span class="comment">(* Automatically generated code *)</span><span class="whitespace">
+</span>4 <span class="comment">(* ---------------------------------------------------------------------------- *)</span><span class="whitespace">
+</span>5 <span class="keyword">specification</span><span class="whitespace"> </span><span class="identifier">unnamed</span><span class="whitespace"> </span><span class="symbol">:</span><span class="whitespace"> </span><span class="keyword">noexit</span><span class="whitespace">
+6
+7 </span><span class="keyword">type</span><span class="whitespace"> </span><span class="identifier">test</span><span class="whitespace"> </span><span class="keyword">is</span><span class="whitespace"> </span><span class="identifier">Boolean</span><span class="whitespace">
+8 </span><span class="keyword">sorts</span><span class="whitespace">
+9 </span><span class="identifier">test</span><span class="whitespace">
+10 </span><span class="keyword">opns</span><span class="whitespace">
+11 </span><span class="identifier">a</span><span class="whitespace"> </span><span class="comment">(*! constructor *)</span><span class="whitespace">
+12 </span><span class="symbol">,</span><span class="whitespace"> </span><span class="identifier">b</span><span class="whitespace"> </span><span class="comment">(*! constructor *)</span><span class="whitespace">
+13 </span><span class="symbol">,</span><span class="whitespace"> </span><span class="identifier">c</span><span class="whitespace"> </span><span class="comment">(*! constructor *)</span><span class="whitespace">
+14 </span><span class="symbol">:</span><span class="whitespace"> </span><span class="symbol">-></span><span class="whitespace"> </span><span class="identifier">test</span><span class="whitespace">
+15 </span><span class="identifier">_eq_</span><span class="symbol">,</span><span class="whitespace"> </span><span class="identifier">_neq_</span><span class="whitespace"> </span><span class="symbol">:</span><span class="whitespace"> </span><span class="identifier">test</span><span class="symbol">,</span><span class="whitespace"> </span><span class="identifier">test</span><span class="whitespace"> </span><span class="symbol">-></span><span class="whitespace"> </span><span class="identifier">Bool</span><span class="whitespace">
+16 </span><span class="keyword">eqns</span><span class="whitespace">
+17 </span><span class="keyword">forall</span><span class="whitespace"> </span><span class="identifier">x</span><span class="symbol">,</span><span class="whitespace"> </span><span class="identifier">y</span><span class="whitespace"> </span><span class="symbol">:</span><span class="whitespace"> </span><span class="identifier">test</span><span class="whitespace">
+18
+19 </span><span class="keyword">ofsort</span><span class="whitespace"> </span><span class="identifier">Bool</span><span class="whitespace">
+20 </span><span class="identifier">x</span><span class="whitespace"> </span><span class="symbol">=</span><span class="whitespace"> </span><span class="identifier">y</span><span class="whitespace"> </span><span class="symbol">=></span><span class="whitespace"> </span><span class="identifier">x</span><span class="whitespace"> </span><span class="keyword">eq</span><span class="whitespace"> </span><span class="identifier">y</span><span class="whitespace"> </span><span class="symbol">=</span><span class="whitespace"> </span><span class="keyword">true</span><span class="symbol">;</span><span class="whitespace">
+21 </span><span class="identifier">x</span><span class="whitespace"> </span><span class="keyword">eq</span><span class="whitespace"> </span><span class="identifier">y</span><span class="whitespace"> </span><span class="symbol">=</span><span class="whitespace"> </span><span class="keyword">false</span><span class="symbol">;</span><span class="whitespace">
+22 </span><span class="identifier">x</span><span class="whitespace"> </span><span class="keyword">neq</span><span class="whitespace"> </span><span class="identifier">y</span><span class="whitespace"> </span><span class="symbol">=</span><span class="whitespace"> </span><span class="identifier">not</span><span class="symbol">(</span><span class="identifier">x</span><span class="whitespace"> </span><span class="keyword">eq</span><span class="whitespace"> </span><span class="identifier">y</span><span class="symbol">)</span><span class="symbol">;</span><span class="whitespace">
+23 </span><span class="keyword">endtype</span><span class="whitespace">
+</span>24 <span class="keyword">behaviour</span><span class="whitespace">
+25 </span><span class="whitespace">
+26 </span><span class="whitespace">
+27 </span><span class="whitespace">
+</span>28 <span class="keyword">endspec</span></pre>
+ </td>
+ </tr>
+ </table>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;">
+ <a name="relatedUseCases"></a>Related Use Cases
+ </h4>
+ <table>
+ <COLGROUP>
+ <COL width="2%" />
+ <COL width="98%" />
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ <p align="justify">
+ None at the current time.
+ </p>
+ </td>
+ </tr>
+ </table>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;">
+ <a name="download">Download</a>
+ </h4>
+
+ <table width="100%">
+ <COLGROUP>
+ <COL width="25%">
+ <COL width="75%">
+ </COLGROUP>
+ <tr>
+ <td align="center"><a href="http://dev.eclipse.org/viewcvs/indextech.cgi/org.eclipse.gmt/org.eclipse.gmt.tcs/syntaxes/FIACRE/"><h3>FIACRE Language Project</h3></a></td>
+ <td><a href="http://wiki.eclipse.org/TCS/Language_Project">Language Project</a> defining FIACRE:
+ <a href="http://dev.eclipse.org/viewcvs/indextech.cgi/org.eclipse.gmt/org.eclipse.gmt.tcs/syntaxes/FIACRE/Metamodel/FIACRE.km3?view=markup">KM3 metamodel</a>,
+ <a href="http://dev.eclipse.org/viewcvs/indextech.cgi/org.eclipse.gmt/org.eclipse.gmt.tcs/syntaxes/FIACRE/Syntax/FIACRE.tcs?view=markup">TCS model</a>,
+ and <a href="http://dev.eclipse.org/viewcvs/indextech.cgi/org.eclipse.gmt/org.eclipse.gmt.tcs/syntaxes/FIACRE/Compiler/FIACRE2LOTOS.atl?view=markup">FIACRE2LOTOS.atl compiler</a>.</td>
+ </tr>
+ <tr>
+ <td align="center"><a href="http://dev.eclipse.org/viewcvs/indextech.cgi/org.eclipse.gmt/org.eclipse.gmt.tcs/syntaxes/LOTOS/"><h3>LOTOS Language Project</h3></a></td>
+ <td><a href="http://wiki.eclipse.org/TCS/Language_Project">Language Project</a> defining LOTOS:
+ <a href="http://dev.eclipse.org/viewcvs/indextech.cgi/org.eclipse.gmt/org.eclipse.gmt.tcs/syntaxes/LOTOS/Metamodel/LOTOS.km3?view=markup">KM3 metamodel</a>,
+ and <a href="http://dev.eclipse.org/viewcvs/indextech.cgi/org.eclipse.gmt/org.eclipse.gmt.tcs/syntaxes/LOTOS/Syntax/LOTOS.tcs?view=markup">TCS model</a>.
+ </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>Acknowledgement
+ </h4>
+
+ <table width="100%">
+ <COLGROUP>
+ <COL width="2%">
+ <COL width="98%">
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ The present work is being supported by the <a href="http://openembedd.inria.fr/home_html-en?set_language=en&cl=en" title="OpenEmbeDD project">OpenEmbeDD project</a>.
+ We would like to thank Marc Pantel (Toulouse) from the <a href="http://www.topcased.org/">TopCased</a> project,
+ and Christian Attiogbé from the <a href="http://www.sciences.univ-nantes.fr/info/perso/permanents/attiogbe/COLOSS/">COLOSS</a> team (Nantes) for their advice.
+ </td>
+ </tr>
+ </table>
+
+ </div>
+ </div>
+
+ <div id="rightcolumn">
+ <div class="sideitem">
+ <h6>General Information</h6>
+ <ul>
+ <li style="list-style:none">September 2007</li>
+ <li style="list-style:none">
+ By <a href="http://www.sciences.univ-nantes.fr/lina/atl/contrib/jouault">Frédéric Jouault</a> (INRIA <a href="http://www.sciences.univ-nantes.fr/lina/atl/">ATLAS</a>),
+ and <a href="http://www.inrialpes.fr/vasy/people/Frederic.Lang/">Frédéric Lang</a> (INRIA <a href="http://www.inrialpes.fr/vasy/">VASY</a>)
+ </li>
+ <li style="list-style:none"><br />Please, ask your questions on the <a href="news://news.eclipse.org/eclipse.modeling.m2m">M2M newsgroup</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/GenerateGraphicalViewForMetamodel/img/Sample.png b/usecases/GenerateGraphicalViewForMetamodel/img/Sample.png
new file mode 100644
index 0000000..3d6e55b
--- /dev/null
+++ b/usecases/GenerateGraphicalViewForMetamodel/img/Sample.png
Binary files differ
diff --git a/usecases/GenerateGraphicalViewForMetamodel/img/UseCaseOverview.png b/usecases/GenerateGraphicalViewForMetamodel/img/UseCaseOverview.png
new file mode 100644
index 0000000..14af885
--- /dev/null
+++ b/usecases/GenerateGraphicalViewForMetamodel/img/UseCaseOverview.png
Binary files differ
diff --git a/usecases/GenerateGraphicalViewForMetamodel/index.php b/usecases/GenerateGraphicalViewForMetamodel/index.php
new file mode 100644
index 0000000..7849d58
--- /dev/null
+++ b/usecases/GenerateGraphicalViewForMetamodel/index.php
@@ -0,0 +1,177 @@
+<?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.
+ $shortTitle = "Generate Graphical Representation for a Metamodel";
+ $pageTitle = "ATL Use Case - " . $shortTitle;
+ $pageKeywords = "Graphical, KM3, Metamodel, DOT";
+ $pageAuthor = "Freddy Allilaire";
+
+ # End: page-specific settings
+ #
+
+ # Paste your HTML content between the EOHTML markers!
+ $html = <<<EOHTML
+
+ <!-- Main part -->
+ <div id="midcolumn">
+ <h1>$pageTitle</h1>
+
+ <img align="right" src="../../resources/atlLogoSmall.png" valign="top" style="padding-left: 10px;" alt="ATL Logo" />
+ <blockquote>
+ <ul>
+ <li><a href="#keywords"><b>Keywords</b></a></li>
+ <li><a href="#overview"><b>Overview</b></a></li>
+ <li><a href="#relatedUseCases"><b>Related Use Cases</b></a></li>
+ <li><a href="#download"><b>Download</b></a></li>
+ <li><a href="#acknowledgement"><b>Acknowledgement</b></a></li>
+ </ul>
+ </blockquote>
+
+ <hr class="clearer" />
+
+ <div id="container>
+ <p align="justify">
+
+ </p>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;"><a name="keywords"></a>Keywords</h4>
+ <table width="100%">
+ <COLGROUP>
+ <COL width="2%" />
+ <COL width="98%" />
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ <p align="justify">
+ Visual presentation,
+ Graphical representation,
+ <a href="http://wiki.eclipse.org/index.php/KM3">KM3</a>,
+ Metamodel,
+ DOT
+ </p>
+ </td>
+ </tr>
+ </table>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;"><a name="overview"></a>Overview</h4>
+
+ <table width="100%">
+ <COLGROUP>
+ <COL width="2%" />
+ <COL width="98%" />
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ <p align="justify">
+ This use case describes the automatic generation of a visual presentation for a metamodel written in KM3.
+ KM3 (Kernel Meta Meta Model) is a textual concrete syntax to describe metamodels and to define Domain Specific Languages.
+ DOT is an automatic graph layout program from Graphviz. It can be used to create graphical files, such as PS, PNG, etc. out of its layout.
+ </p>
+ <p align="justify">
+ Having a graphical presentation of a metamodel can be sometimes enlightening in comparison with a textual presentation.
+ The aim of this case study is to generate a rough visualization in the form of a class diagram for a KM3 file.
+ A metamodel created with KM3 does not include any representation information. DOT, the Graphviz
+ tool, is used to compute the layout and generate the output picture. The overall approach is summarized in the following figure:
+ </p>
+ <p align="center">
+ <img src="img/UseCaseOverview.png" />
+ <br /><br />
+ <b>"$shortTitle" Use Case's Overview</b>
+ </p>
+ <p align="justify">
+ The Model-to-Model transformation phase was implemented by using ATL model-to-model transformations.
+ </p>
+ <p align="justify">
+ We provide below a set of screenshots showing the different input/output files provided/created with this use case:
+ </p>
+ <p align="center">
+ <img src="img/Sample.png" />
+ <br /><br />
+ <b>Screenshots of the input/outputs of the use case</b>
+ </p>
+ </td>
+ </tr>
+ </table>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;">
+ <a name="relatedUseCases"></a>Related Use Cases
+ </h4>
+ <table>
+ <COLGROUP>
+ <COL width="2%" />
+ <COL width="98%" />
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ <p align="justify">
+ None at the current time.
+ </p>
+ </td>
+ </tr>
+ </table>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;">
+ <a name="download">Download</a>
+ </h4>
+
+ <table width="100%">
+ <COLGROUP>
+ <COL width="25%">
+ <COL width="75%">
+ </COLGROUP>
+ <tr>
+ <td align="center"><a href="http://www.eclipse.org/atl/atlTransformations/#KM32DOT"><h3>Complete scenario</h3></a></td>
+ <td>Scenario available in the ATL transformation zoo (with source files).</td>
+ </tr>
+ <tr>
+ <td align="center"><a href="http://www.eclipse.org/gmt/am3/zoos/atlanticZoo/#KM3"><h3>KM3 Metamodel</h3></a></td>
+ <td>KM3 metamodel is expressed in the <a href="http://wiki.eclipse.org/index.php/KM3">KM3</a> textual format.</td>
+ </tr>
+ <tr>
+ <td align="center"><a href="http://www.eclipse.org/gmt/am3/zoos/atlanticZoo/#DOT"><h3>DOT Metamodel</h3></a></td>
+ <td>DOT metamodel is expressed in the <a href="http://wiki.eclipse.org/index.php/KM3">KM3</a> textual format.</td>
+ </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>Acknowledgement
+ </h4>
+
+ <table width="100%">
+ <COLGROUP>
+ <COL width="2%">
+ <COL width="98%">
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ The present work is being supported by the <a href="http://www.usine-logicielle.org">Usine Logicielle project of the System@tic Paris Region Cluster</a>.
+ </td>
+ </tr>
+ </table>
+
+ </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/GenerationSVGOfUMLClassDiagram/img/Sample.png b/usecases/GenerationSVGOfUMLClassDiagram/img/Sample.png
new file mode 100644
index 0000000..4e9a5c3
--- /dev/null
+++ b/usecases/GenerationSVGOfUMLClassDiagram/img/Sample.png
Binary files differ
diff --git a/usecases/GenerationSVGOfUMLClassDiagram/img/UseCaseOverview.png b/usecases/GenerationSVGOfUMLClassDiagram/img/UseCaseOverview.png
new file mode 100644
index 0000000..9d99813
--- /dev/null
+++ b/usecases/GenerationSVGOfUMLClassDiagram/img/UseCaseOverview.png
Binary files differ
diff --git a/usecases/GenerationSVGOfUMLClassDiagram/index.php b/usecases/GenerationSVGOfUMLClassDiagram/index.php
new file mode 100644
index 0000000..b3dc9e2
--- /dev/null
+++ b/usecases/GenerationSVGOfUMLClassDiagram/index.php
@@ -0,0 +1,197 @@
+<?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.
+ $shortTitle = "Generation of Vector Graphic (SVG) Representation of a UML Class Diagram";
+ $pageTitle = "ATL Use Case - " . $shortTitle;
+ $pageKeywords = "";
+ $pageAuthor = "Freddy Allilaire";
+
+ # End: page-specific settings
+ #
+
+ # Paste your HTML content between the EOHTML markers!
+ $html = <<<EOHTML
+
+ <!-- Main part -->
+ <div id="midcolumn">
+ <h1>$pageTitle</h1>
+
+ <img align="right" src="../../resources/atlLogoSmall.png" valign="top" style="padding-left: 10px;" alt="ATL Logo" />
+ <blockquote>
+ <ul>
+ <li><a href="#keywords"><b>Keywords</b></a></li>
+ <li><a href="#overview"><b>Overview</b></a></li>
+ <li><a href="#relatedUseCases"><b>Related Use Cases</b></a></li>
+ <li><a href="#download"><b>Download</b></a></li>
+ <li><a href="#acknowledgement"><b>Acknowledgement</b></a></li>
+ </ul>
+ </blockquote>
+
+ <hr class="clearer" />
+
+ <div>
+ <p align="justify">
+
+ </p>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;"><a name="keywords"></a>Keywords</h4>
+ <table width="100%">
+ <COLGROUP>
+ <COL width="2%" />
+ <COL width="98%" />
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ <p align="justify">
+ <a href="http://www.w3.org/TR/SVG11/">SVG</a>,
+ Graphical Representation,
+ <a href="http://www.omg.org/cgi-bin/doc?ptc/2003-09-01">UML Diagram Interchange</a>,
+ UML Class Diagram
+ </p>
+ </td>
+ </tr>
+ </table>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;"><a name="overview"></a>Overview</h4>
+
+ <table width="100%">
+ <COLGROUP>
+ <COL width="2%" />
+ <COL width="98%" />
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ <p align="justify">
+ This use case describes the automatic generation of a vector graphic representation for a UML class diagram.
+ This UML diagram has its presentation information according to the UML Diagram Interchange standard.
+
+ UML Diagram Interchange enables a smooth and seamless exchange of documents compliant to the UML standard (referred to as UML models) between different software tools.
+ While this certainly includes tools for developing UML models, it also includes tools such as whiteboard tools, code generators, word processing tools, and desktop
+ publishing tools. Special attention is given to the Internet as a medium for exchanging and presenting UML models.
+
+ From this diagram interchange data we generate another presentation using the W3C
+ standard SVG (Scalable Vector Graphics), an XML-based format. The SVG file may be exported towards another graphical format, or viewed as is.
+ Moreover, the SVG code in the created file shall be readable by a humanbeing, as opposed to the
+ exported XMI file from Poseidon. For instance that generates SVG files that are based on non abstract geometrical
+ forms (such as rectangle, line, circle, polygon, etc). This scenario shall create
+ logical structures using as many as possible abstract geometrical forms.
+
+ </p>
+ <p align="justify">
+ The overall approach is summarized in the following figure:
+ </p>
+ <p align="center">
+ <img src="img/UseCaseOverview.png" />
+ <br /><br />
+ <b>"$shortTitle" Use Case's Overview</b>
+ </p>
+ <p align="justify">
+ The Model-to-Model transformation phase was implemented by using ATL model-to-model transformations.
+ </p>
+ <p align="justify">
+ We provide below a set of screenshots showing the different input/output files provided/created with this use case:
+ </p>
+ <p align="center">
+ <img src="img/Sample.png" />
+ <br /><br />
+ <b>Screenshots of the input/outputs of the use case</b>
+ </p>
+ </td>
+ </tr>
+ </table>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;">
+ <a name="relatedUseCases"></a>Related Use Cases
+ </h4>
+ <table>
+ <COLGROUP>
+ <COL width="2%" />
+ <COL width="98%" />
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ <p align="justify">
+ None at the current time.
+ </p>
+ </td>
+ </tr>
+ </table>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;">
+ <a name="download">Download</a>
+ </h4>
+
+ <table width="100%">
+ <COLGROUP>
+ <COL width="25%">
+ <COL width="75%">
+ </COLGROUP>
+ <tr>
+ <td align="center"><a href="http://www.eclipse.org/atl/atlTransformations/#UMLDI2SVG"><h3>Complete scenario</h3></a></td>
+ <td>Scenario available in the ATL transformation zoo (with source files).</td>
+ </tr>
+ <tr>
+ <td align="center"><a href="http://www.eclipse.org/gmt/am3/zoos/atlanticZoo/#SVG"><h3>SVG Metamodel</h3></a></td>
+ <td>SVG metamodel is expressed in the <a href="http://wiki.eclipse.org/index.php/KM3">KM3</a> textual format.</td>
+ </tr>
+ <tr>
+ <td align="center"><a href="http://www.eclipse.org/gmt/am3/zoos/atlanticZoo/#XML"><h3>XML Metamodel</h3></a></td>
+ <td>XML metamodel is expressed in the <a href="http://wiki.eclipse.org/index.php/KM3">KM3</a> textual format.</td>
+ </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>Acknowledgement
+ </h4>
+
+ <table width="100%">
+ <COLGROUP>
+ <COL width="2%">
+ <COL width="98%">
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ The present work is being supported by the <a href="http://www.usine-logicielle.org">Usine Logicielle project of the System@tic Paris Region Cluster</a>.
+ </td>
+ </tr>
+ </table>
+
+ </div>
+ </div>
+
+ <div id="rightcolumn">
+ <div class="sideitem">
+ <h6>General Information</h6>
+ <ul>
+ <li style="list-style:none">March 2007</li>
+ <li style="list-style:none">
+ By <a href="http://www.sciences.univ-nantes.fr/lina/atl/contrib/allilaire">Freddy Allilaire</a> (INRIA)
+ </li>
+ <li style="list-style:none"><br />Please, ask your questions on the <a href="news://news.eclipse.org/eclipse.modeling.m2m">M2M newsgroup</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/MDL2GMF/.project b/usecases/MDL2GMF/.project
new file mode 100644
index 0000000..617e082
--- /dev/null
+++ b/usecases/MDL2GMF/.project
@@ -0,0 +1,11 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<projectDescription>
+ <name>MDL2GMF_WEB</name>
+ <comment></comment>
+ <projects>
+ </projects>
+ <buildSpec>
+ </buildSpec>
+ <natures>
+ </natures>
+</projectDescription>
diff --git a/usecases/MDL2GMF/img/ATLUseCase_large.png b/usecases/MDL2GMF/img/ATLUseCase_large.png
new file mode 100644
index 0000000..c4b5b68
--- /dev/null
+++ b/usecases/MDL2GMF/img/ATLUseCase_large.png
Binary files differ
diff --git a/usecases/MDL2GMF/img/ATLUseCase_medium.png b/usecases/MDL2GMF/img/ATLUseCase_medium.png
new file mode 100644
index 0000000..f1fc1f1
--- /dev/null
+++ b/usecases/MDL2GMF/img/ATLUseCase_medium.png
Binary files differ
diff --git a/usecases/MDL2GMF/img/Mdl_large.png b/usecases/MDL2GMF/img/Mdl_large.png
new file mode 100644
index 0000000..492d2a8
--- /dev/null
+++ b/usecases/MDL2GMF/img/Mdl_large.png
Binary files differ
diff --git a/usecases/MDL2GMF/img/Mdl_medium.png b/usecases/MDL2GMF/img/Mdl_medium.png
new file mode 100644
index 0000000..199714e
--- /dev/null
+++ b/usecases/MDL2GMF/img/Mdl_medium.png
Binary files differ
diff --git "a/usecases/MDL2GMF/img/QVTRelation\050ATL\051_large.png" "b/usecases/MDL2GMF/img/QVTRelation\050ATL\051_large.png"
new file mode 100644
index 0000000..6ac60e3
--- /dev/null
+++ "b/usecases/MDL2GMF/img/QVTRelation\050ATL\051_large.png"
Binary files differ
diff --git "a/usecases/MDL2GMF/img/QVTRelation\050ATL\051_medium.png" "b/usecases/MDL2GMF/img/QVTRelation\050ATL\051_medium.png"
new file mode 100644
index 0000000..1283f54
--- /dev/null
+++ "b/usecases/MDL2GMF/img/QVTRelation\050ATL\051_medium.png"
Binary files differ
diff --git "a/usecases/MDL2GMF/img/QVTRelation\050RSM\051.png" "b/usecases/MDL2GMF/img/QVTRelation\050RSM\051.png"
new file mode 100644
index 0000000..debc495
--- /dev/null
+++ "b/usecases/MDL2GMF/img/QVTRelation\050RSM\051.png"
Binary files differ
diff --git "a/usecases/MDL2GMF/img/QVTRelation\050RSM\051_medium.png" "b/usecases/MDL2GMF/img/QVTRelation\050RSM\051_medium.png"
new file mode 100644
index 0000000..8d16d92
--- /dev/null
+++ "b/usecases/MDL2GMF/img/QVTRelation\050RSM\051_medium.png"
Binary files differ
diff --git a/usecases/MDL2GMF/index.php b/usecases/MDL2GMF/index.php
new file mode 100644
index 0000000..b17fed2
--- /dev/null
+++ b/usecases/MDL2GMF/index.php
@@ -0,0 +1,289 @@
+<?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 = "ATL Use Case - Rational Rose to UML2 Tools";
+ $pageKeywords = "Rational Rose, MDL, GMF, UML2, UML2 Tools";
+ $pageAuthor = "Brahim Khalil LOUKIL";
+
+ # End: page-specific settings
+ #
+
+ # Paste your HTML content between the EOHTML markers!
+ $html = <<<EOHTML
+
+<!-- Main part -->
+ <div id="midcolumn">
+ <h1>$pageTitle</h1>
+
+ <img align="right" src="../../resources/atlLogoSmall.png" valign="top" style="padding-left: 10px;" alt="ATL Logo" />
+ <blockquote>
+ <ul>
+ <li><a href="#keywords"><b>Keywords</b></a></li>
+ <li><a href="#overview"><b>Overview</b></a></li>
+ <li><a href="#Screenshots"><b>Screenshots</b></a></li>
+ <li><a href="#AvailableFeatures"><b>Available features</b></a></li>
+ <li><a href="#PossibleExtensions"><b>Possible extensions</b></a></li>
+ <li><a href="#relatedUseCases"><b>Related Use Cases</b></a></li>
+ <li><a href="#download"><b>Download</b></a></li>
+
+ </ul>
+ </blockquote>
+
+ <hr class="clearer" />
+
+ <div>
+ <p align="justify">
+ This use case shows how we can reuse UML projects created with Rational Rose and import them in GMF (specifically in UML2 Tools) using ATL transformations.
+ In this use case, we only support UML class diagrams.
+ In practice, this use case was applied to the QVT metamodel available on the OMG site (<a href="http://www.omg.org/cgi-bin/doc?ad/2005-09-01">document ad/2005-09-01</a>). </p>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;"><a name="keywords"></a>Keywords</h4>
+ <table width="100%">
+ <COLGROUP>
+ <COL width="2%" />
+ <COL width="98%" />
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ <p align="justify">
+ <a href="http://en.wikipedia.org/wiki/Rational_Rose">Rational Rose</a>, MDL,
+ <a href="http://www.eclipse.org/gmf/">GMF</a>,
+ <a href="http://www.eclipse.org/modeling/mdt/?project=uml2#uml2">UML2</a>,
+ <a href="http://www.eclipse.org/modeling/mdt/?project=uml2tools#uml2tools">UML2 Tools</a> </p>
+ </td>
+ </tr>
+ </table>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;"><a name="overview"></a>Overview</h4>
+
+ <table width="100%">
+ <COLGROUP>
+ <COL width="2%" />
+ <COL width="98%" />
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ <p align="justify">
+ In this use case, we essentially have to deal with two problems. The first problem is that the UML Model created by Rational Rose conforms to a specific
+ grammar based on Petal syntax, and called MDL. This syntax is neither XML nor XMI, so we need a specific reader. The second problem is that the MDL model
+ contains more than one UML diagram, whereas each GMF diagram is a separate model. Therefore, we need to find out how we can generate n models using
+ the same ATL transformation. </p>
+ <p align="justify">
+ To deal with these problems, we start by developing the MDL reader using TCS. The MDL metamodel is depicted in Figure1. The whole project is available in the <a href="http://wiki.eclipse.org/TCS/Zoo">TCS Zoo</a>. </p>
+ <p align="center">
+ <a href="img/Mdl_large.png"><img src="img/Mdl_medium.png" width="826" height="317" border="0" /></a>
+ <br />
+ <br />
+ <b>Figure 1: The MDL metamodel</b> </p>
+
+ <p align="justify">
+ Once we can read the MDL model, the next step is to write the transformation to UML. In this transformation, we preserve the same structure of packages as in the MDL file. </p>
+ <p align="justify">
+ The second step is to write a transformation from MDL and UML to GMF diagrams. The MDL model is needed to gather the graphical information.
+ The UML model is necessary because some GMF elements points to UML elements. </p>
+ <p align="justify">
+ Finally, we create an ant script in order to assemble all these transformations into a single executable entity.
+ This script must additionally deal with the multi-diagram generation problem mentioned above. </p>
+ <p align="justify">
+ The full transformation scenario is depicted in Figure 2: </p>
+ <p align="center"><a href="img/ATLUseCase_large.png"><img src="img/ATLUseCase_medium.png" width="872" height="276" border="0" /></a><br />
+ <br />
+ <b>Figure 2: MDL to UML2.1 and GMF</b>
+ </p>
+ <p align="justify">
+ As we can see on the left, the input of this transformation is an MDL file, and the result on the right is a several GMF models which refer to an only one UML model.
+ </p>
+ <p align="justify">
+ In this transformation scenario, we needed to produce not only one GMF model but several models,
+ that it is why we used two ATL transformations instead of only one which could produce the UML and the GMF model in one shot. The important thing here is how we
+ can propagate the reference of uml elements generated by the first transformation to the second. The solution implemented is to generate with the first
+ transformation an annotation for each UML element which can hold the [MDL ID].</p>
+ </td>
+ </tr>
+ </table>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;">
+ <a name="Screenshots"></a>Screenshots
+ </h4>
+ <table>
+ <COLGROUP>
+ <COL width="2%" />
+ <COL width="98%" />
+ </COLGROUP>
+ <tr>
+ <td>
+ <p align="justify">
+ The first screenshot below shows an example of result which is a QVT relation diagram imported to UML2 tools using ATL. And the second shows how
+ the diagram looks like in Rational Rose (This tool is no longer available, so we used RSM).
+ </p>
+ <p align="justify">
+ As we can see, the positions and colors of nodes are preserved. Some features like: the state of compartments (collapsed or not), associations,
+ and dependencies are not supported in the diagram. The reason is that UML2 Tools do not provide full multi-diagram support.
+
+ </p>
+ <b>Imports results from Rational Rose to UML2 tools</b>
+ </td>
+ </tr>
+ <tr>
+ <td><p align="center"><a href="img/QVTRelation(ATL)_large.png"><img src="img/QVTRelation(ATL)_medium.png" height="827" width="1027" border="0" /></a>
+ <br/><b>UML2 Tools : QVT Relation diagram </b>
+ </p>
+ </td>
+ </tr>
+ <tr>
+ <td colspan="2"><br>
+ <b>Imports results from Rational Rose to RSM</b>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ <p align="center"><a href="img/QVTRelation(RSM).png"><img src="img/QVTRelation(RSM).png" width="675" height="517" border="0" /></a>
+ <br/>
+ <b>RSM: QVT Relation diagram </b>
+ </p>
+ </td>
+ </tr>
+ </table>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;">
+ <a name="AvailableFeatures"></a>Available features
+ </h4>
+ <table>
+ <COLGROUP>
+ <COL width="2%" />
+ <COL width="98%" />
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ <p align="justify">
+ <ul>
+ <li>Support of 14 UML elements.</li>
+ <li>Export the color and position of nodes.</li>
+ <li>Multi-diagrams support.</li>
+ </ul>
+ </p>
+ </td>
+ </tr>
+ </table>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;">
+ <a name="PossibleExtensions"></a>Possible extensions
+ </h4>
+ <table>
+ <COLGROUP>
+ <COL width="2%" />
+ <COL width="98%" />
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ <p align="justify">
+ <ul>
+ <li>Preserve the same bendpoints used in MDL file for links.</li>
+ <li>Produce shortcuts for associations (It is not possible with current UML2 tools).</li>
+ <li>Produce the state for compartments (It is not possible with current UML2 tools).</li>
+ <li>Test performance on emfvm (Actually, It is not possible because emfvm has not yet supported metamodel extension)</li>
+ <li>Tests and enhancements maybe needed for the MDL reader.</li>
+ <li>Resolve the problem of scale (Elements are relatively small compared to distances between them).</li>
+ <li>Resolve the problem of scale (Elements are relatively small compared to distances between them).</li>
+ <li>Complete class diagram (95% done)</li>
+ <li>Work on other diagrams.</li>
+
+ </ul>
+ </p>
+ </td>
+ </tr>
+ </table>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;">
+ <a name="relatedUseCases"></a>Related Use Cases
+ </h4>
+ <table>
+ <COLGROUP>
+ <COL width="2%" />
+ <COL width="98%" />
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ <p align="justify">
+ None at the current time.
+ </p>
+ </td>
+ </tr>
+ </table>
+
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;">
+ <a name="download">Download</a>
+ </h4>
+
+ <table width="100%">
+ <COLGROUP>
+ <COL width="25%">
+ <COL width="75%">
+ </COLGROUP>
+ <tr>
+ <td align="center"><a href="http://www.eclipse.org/atl/atlTransformations/MDL2GMF/org.eclipse.m2m.atl.mdl2gmf.zip"><h3>Complete scenario</h3></a></td>
+ <td>Scenario MDL to GMF available in the ATL transformation zoo (with source files).</td>
+ </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>Acknowledgement
+ </h4>
+
+ <table width="100%">
+ <COLGROUP>
+ <COL width="2%">
+ <COL width="98%">
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ The present work is being partially supported by the <a href="http://openembedd.inria.fr/home_html-en?set_language=en&cl=en" title="OpenEmbeDD project">OpenEmbeDD project</a>.
+ </td>
+ </tr>
+ </table>
+
+ </div>
+ </div>
+
+ <div id="rightcolumn">
+ <div class="sideitem">
+ <h6>General Information</h6>
+ <ul>
+ <li style="list-style:none">Januray 2008</li>
+ <li style="list-style:none">
+ By <a href="http://brlouk2008.teamsoftsuite.com">Brahim Khalil Loukil</a> and
+ <a href="http://www.sciences.univ-nantes.fr/lina/atl/contrib/jouault">Frédéric Jouault</a> (INRIA)
+ </li>
+ <li style="list-style:none"><br />Please, ask your questions on the <a href="news://news.eclipse.org/eclipse.modeling.m2m">M2M newsgroup</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/MMIndApproachtoDiffRep/img/MMD2ATL.jpg b/usecases/MMIndApproachtoDiffRep/img/MMD2ATL.jpg
new file mode 100644
index 0000000..f44fdcd
--- /dev/null
+++ b/usecases/MMIndApproachtoDiffRep/img/MMD2ATL.jpg
Binary files differ
diff --git a/usecases/MMIndApproachtoDiffRep/img/differenceAnimation.png b/usecases/MMIndApproachtoDiffRep/img/differenceAnimation.png
new file mode 100644
index 0000000..adc4df6
--- /dev/null
+++ b/usecases/MMIndApproachtoDiffRep/img/differenceAnimation.png
Binary files differ
diff --git a/usecases/MMIndApproachtoDiffRep/img/extendedUmlMetamodel.png b/usecases/MMIndApproachtoDiffRep/img/extendedUmlMetamodel.png
new file mode 100644
index 0000000..db66547
--- /dev/null
+++ b/usecases/MMIndApproachtoDiffRep/img/extendedUmlMetamodel.png
Binary files differ
diff --git a/usecases/MMIndApproachtoDiffRep/img/generalPicture.png b/usecases/MMIndApproachtoDiffRep/img/generalPicture.png
new file mode 100644
index 0000000..8af75c9
--- /dev/null
+++ b/usecases/MMIndApproachtoDiffRep/img/generalPicture.png
Binary files differ
diff --git a/usecases/MMIndApproachtoDiffRep/img/mail.jpg b/usecases/MMIndApproachtoDiffRep/img/mail.jpg
new file mode 100644
index 0000000..bc1e881
--- /dev/null
+++ b/usecases/MMIndApproachtoDiffRep/img/mail.jpg
Binary files differ
diff --git a/usecases/MMIndApproachtoDiffRep/img/mm2mmd.jpg b/usecases/MMIndApproachtoDiffRep/img/mm2mmd.jpg
new file mode 100644
index 0000000..a3bec9b
--- /dev/null
+++ b/usecases/MMIndApproachtoDiffRep/img/mm2mmd.jpg
Binary files differ
diff --git a/usecases/MMIndApproachtoDiffRep/img/umlMetamodel.png b/usecases/MMIndApproachtoDiffRep/img/umlMetamodel.png
new file mode 100644
index 0000000..53e2178
--- /dev/null
+++ b/usecases/MMIndApproachtoDiffRep/img/umlMetamodel.png
Binary files differ
diff --git a/usecases/MMIndApproachtoDiffRep/index.php b/usecases/MMIndApproachtoDiffRep/index.php
new file mode 100644
index 0000000..fa48e6d
--- /dev/null
+++ b/usecases/MMIndApproachtoDiffRep/index.php
@@ -0,0 +1,314 @@
+<?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.
+ $shortTitle = "A Metamodel Independent Approach to Difference Representation";
+ $pageTitle = "ATL Use Case - " . $shortTitle;
+ $pageKeywords = "";
+ $pageAuthor = "Freddy Allilaire";
+
+ # End: page-specific settings
+ #
+
+ # Paste your HTML content between the EOHTML markers!
+ $html = <<<EOHTML
+
+ <!-- Main part -->
+ <div id="midcolumn">
+ <h1>$pageTitle</h1>
+
+ <img align="right" src="../../resources/atlLogoSmall.png" valign="top" style="padding-left: 10px;" alt="ATL Logo" />
+ <blockquote>
+ <ul>
+ <li><a href="#keywords"><b>Keywords</b></a></li>
+ <li><a href="#overview"><b>Overview</b></a>
+ <ul>
+ <li><a href="#mmd">Difference Metamodel</a></li>
+ <li><a href="#animation">Difference Animation</a></li>
+ </ul>
+ </li>
+ <li><a href="#relatedUseCases"><b>Related Use Cases</b></a></li>
+ <li><a href="#references"><b>References</b></a></li>
+ <li><a href="#download"><b>Download</b></a></li>
+ </ul>
+ </blockquote>
+
+ <hr class="clearer" />
+
+ <div>
+ <p align="justify">
+ This document presents an ATL implementation of a metamodel independent approach to the representation of model differences which is agnostic of the calculation method. Given two models
+ being differenced which conform to a metamodel, their difference is conforming to another metamodel derived from the former by an automated transformation. Interestingly, difference
+ models are firstclass artifacts which in turn induce other transformations, such that they can be applied to one of the differenced models to automatically obtain the other one. All
+ the code for the transformations in ATL and for the metamodels in KM3 is available <a href="http://www.di.univaq.it/diruscio/atlDiff.php">here</a>.
+ </p>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;"><a name="keywords"></a>Keywords</h4>
+ <table width="100%">
+ <colgroup>
+ <col width="2%">
+ <col width="98%">
+ </colgroup>
+ <tr>
+ <td></td>
+ <td>
+ <p align="justify">
+ Metamodeling,
+ Model Difference,
+ Model Versioning and Evolution,
+ High-order tranformations
+ </p>
+ </td>
+ </tr>
+ </table>
+
+ <h4 style="border-bottom: 2px solid rgb(73, 69, 124); padding: 0pt; font-size: 10pt; background-position: left top;"><a name="overview"></a>Overview</h4>
+
+ <h5 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;">Difference Metamodel<a name="mmd"> </a></h5>
+
+ <table width="100%">
+ <colgroup>
+ <col width="2%">
+ <col width="98%">
+ </colgroup>
+ <tr>
+ <td></td>
+
+ <td>
+ <p align="justify">
+ Given two models being differenced and that conform to a given metamodel MM, their difference conforms to another metamodel MMD that can be automatically derived from MM.
+ In particular, the new metamodel has to provide with the constructs able to express the modifications that have to be performed on the initial version of a given model in
+ order to obtain the final one. The approach permits the representation of changes that can grouped as follows:
+ <ol>
+ <li>additions: new elements are added in the final model;</li>
+ <li>deletions: some of the existing elements in the initial model are deleted as a whole;</li>
+ <li>changes: a new version of the model can consist of some updates of already existing elements;</li>
+ </ol>
+ </p>
+
+ <br />
+ <p align="center">
+ <a href="img/generalPicture.png"><img src="img/generalPicture.png" width="70%" ></a>
+ <br />
+ <br />
+ <b>Figure 1: General Picture</b>
+ </p>
+
+ <p align="justify">
+ For instance, the metaclasses AddedClass, DeletedClass and ChangedClass in Figure 3
+ are derived by the metaclass Class depicted in the simplified UML metamodel depicted in Figure 2.
+ The resulting metamodel allows the representation of the differences among two distinct versions
+ of a UML model.
+ </p>
+
+ <p align="center">
+ <a href="img/umlMetamodel.png"><img src="img/umlMetamodel.png" width="60%"></a>
+ <br />
+ <br />
+ <b>Figure 2: Sample UML Metamodel</b>
+ </p>
+
+ <p align="justify">
+ Changes of already existing elements are represented through Changed elements as the class updates which are given by means of ChangedClass instances each of them
+ associated with a corresponding updatedElement class. The latter specifies how ChangedClass has to be modified in the new model version in terms of attributes and
+ associations. The Changed modification is kind of shortcut which groups simple modifications consisting of Added and Deleted only reducing the size of the overall
+ difference model. The features which are not represented in the ChangedClass instance will remain unchanged and will be simply copied in the new version of the given
+ element. Finally, the features specified both in the ChangedClass instance and in the associated updatedElement will be modified according to descriptions given in
+ the last one.
+ </p>
+
+ <p align="center">
+ <a href="img/extendedUmlMetamodel.png"><img src="img/extendedUmlMetamodel.png" width="60%"></a>
+ <br />
+ <br />
+ <b>Figure 3: Sample Generated UML Difference Metamodel</b>
+ </p>
+
+ <p align="justify">
+ According to the general picture in Figure 1, a model transformation <i>MM2MMD</i> is defined in order to produce the difference metamodel MMD associated with MM
+ and a fragment is reported in the following fragment:
+ </p>
+
+ <p align="center">
+ <a href="img/mm2mmd.jpg"><img src="img/mm2mmd.jpg" width="80%" ></a>
+ <br />
+ <br />
+ <b>Figure 4: Fragment of the MM2MMD transformation</b>
+ </p>
+ </td>
+ </tr>
+ </table>
+
+ <h5 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;">Difference Animation<a name="animation"></h5>
+ <table width="100%">
+ <colgroup>
+ <col width="2%">
+ <col width="98%">
+ </colgroup>
+ <tr>
+
+ <td></td>
+
+ <td>
+ <p align="justify">
+ A difference model can be executed to "reconstruct" a final model starting from the initial one. Unfortunately, this is intrinsically difficult and it requires a high-order
+ transformation. In particular, according to the lower side of Figure 5, the model transformation (<i>MMD_MM2MM</i>) can be applied to a model M1 in order to obtain a target
+ M2 with respect to the differences specified in a model MD. Such a model conforms to the metamodel MMD automatically obtained from MM as previously discussed.
+ </p>
+
+ <p align="center">
+ <a href="img/differenceAnimation.png"><img src="img/differenceAnimation.png" width="50%" ></a>
+ <br />
+ <br />
+ <b>Figure 5: Difference Animation</b>
+ </p>
+
+ <p align="justify">
+ The <i>MMD_MM2MM</i> transformation implements the rules to apply on a source model M1 the additions, deletions and changes specified in the model MD. More precisely,
+ considering the dashed part in Figure 1, for each metaclass MC in the metamodel MM, the transformation <i>MMD_MM2MM</i> contains the following rules:
+ <ol>
+ <li>
+ <i>AddedMC2MC</i>: it manages the elements in the difference model MD that conform to the AddedMC metaclass. For each element, the rule creates in M2 a new instance
+ of MC setting the corresponding structural features according to the specification of the AddedMC element;
+ </li>
+ <li>
+ <i>ChangedMC2MC</i>: it updates already existing elements in the initial model of type MC according to the modifications specified in MD through ChangedMC instances;
+ </li>
+ <li>
+ <i>UnchangedMC2MC</i>: it copies the unmodified instances of the metaclass MC which have to be the same both in M1 and M2. The source pattern of this rule has a
+ guard matching only the MC elements which have not been changed nor deleted.
+ </li>
+ </ol>
+ </p>
+
+ <p align="justify">
+ Concerning the management of DeletedMC instances, no rules are provided, since the guard in the source pattern of the UnchangedMC2MCrule guarantees that elements which have
+ been specified as deleted in the difference model are not matched during the transformation phase (hence, not copied in the target model M2).
+ </p>
+
+ <p align="justify">
+ An ATL implementation of this high-order transformation has been defined and it consists of three main rules (see Figure 6) that are AddedClass (lines 4-25), UnchangedClass
+ (lines 27-49), and ChangedClass (lines 51-70). They are dedicated to the generation of the three kinds of rules needed for the management of each metaclass specified in the
+ source difference model. Depending on the structural features of the matched metaclass, a number of helpers are created. Since such generations are quite complex and it is
+ difficult to specify them in a declarative way, ATL called rules and action blocks are used. For instance, the lines 21-24 in Figure 6 implements an action blocks where the
+ called rule CreateAddedHelper is invoked in order to generate the target helpers needed for the management of additions specified in a given model difference (see the lower
+ side of Figure 5)
+ </p>
+
+ <p align="center">
+ <a href="img/MMD2ATL.jpg"><img src="img/MMD2ATL.jpg" width="50%" ></a>
+ <br />
+ <br />
+ <b>Figure 6: Fragment of the MMD2ATL high-order transformation</b>
+ </p>
+
+ <p align="justify">
+ This work is a first attempt to support model versioning and evolution in a MDE setting. Further work will address the problem of conflict detection and resolution. When
+ software is developed in a distributed environment, parallel modifications can give place to conflicts which are usually detected by means of traditional lexical approaches
+ which lack of abstraction and can give place to false positive and negative issues.
+ </p>
+ </td>
+ </tr>
+ </table>
+
+ <h4 style="border-bottom: 2px solid rgb(73, 69, 124); padding: 0pt; font-size: 10pt; background-position: left top;"><a name="relatedUseCases"></a>Related Use Cases</h4>
+ <table>
+ <colgroup>
+ <col width="2%" />
+ <col width="98%" />
+ </colgroup>
+ <tr>
+ <td></td>
+ <td>
+ <p align="justify">
+ <a href="http://www.eclipse.org/gmt/amw/usecases/compare/">AMW Use Case - Metamodel comparison and model migration</a>
+ </p>
+ </td>
+ </tr>
+ </table>
+
+ <h4 style="border-bottom: 2px solid rgb(73, 69, 124); padding: 0pt; font-size: 10pt; background-position: left top;"><a name="references"></a>References</h4>
+ <table width="100%">
+ <tr valign="top">
+ <td>
+ <a href="http://www.di.univaq.it/diruscio/modelDifferenceTR.php">[1]</a>
+ </td>
+ <td>
+ A.Cicchetti, D.Di Ruscio, A. Pierantonio.
+ <em>A Metamodel Independent Approach to Difference Representation,</em>
+ Dipartimento di Informatica, Università degli Studi dell'Aquila, TRCS 005/2007, 2007
+ </td>
+ </tr>
+ </table>
+
+ <h4 style="border-bottom: 2px solid rgb(73, 69, 124); padding: 0pt; font-size: 10pt; background-position: left top;"><a name="download">Download</a></h4>
+ <table width="100%">
+ <colgroup>
+ <col width="25%" />
+ <col width="75%" />
+ </colgroup>
+ <tr>
+ <td align="center">
+ <a href="http://www.di.univaq.it/diruscio/atlDiff.php"><h3>Complete Approach</h3></a>
+ </td>
+ <td>
+ Current implementation of the approach, examples and documentation.
+ </td>
+ </tr>
+ <tr>
+ <td align="center">
+ <a href="http://www.di.univaq.it/diruscio/mm2mmd.php">
+ <h3>MM2MMD Transformation</h3>
+ </a>
+ </td>
+ <td>ATL transformation depicted in Figure 4.</td>
+ </tr>
+ <tr>
+ <td align="center">
+ <a href="http://www.di.univaq.it/diruscio/mmd2atl.php">
+ <h3>MMD2ATL Transformation</h3>
+ </a>
+ </td>
+ <td>
+ High-order ATL transformation depicted in Figure 6.
+ </td>
+ </tr>
+ </table>
+ </div>
+ </div>
+
+ <div id="rightcolumn">
+ <div class="sideitem">
+ <h6>General Information</h6>
+ <ul>
+ <li style="list-style-type: none; list-style-image: none; list-style-position: outside;">April 2007</li>
+ <li style="list-style-type: none; list-style-image: none; list-style-position: outside;">
+ By <a href="www.di.univaq.it/cicchetti">Antonio Cicchetti</a>,
+ <a href="www.di.univaq.it/diruscio">Davide Di Ruscio</a> and
+ <a href="www.di.univaq.it/alfonso">Alfonso Pierantonio</a> (Università dell'Aquila)
+ </li>
+ <li style="list-style-type: none; list-style-image: none; list-style-position: outside;"><br />
+ Please, ask your questions to <u>diruscio [at] di [dot] univaq [dot] it</u>
+ </li>
+ </ul>
+ </div>
+ </div>
+
+EOHTML;
+
+
+ # Generate the web page
+ $App->generatePage($theme, $Menu, $Nav, $pageAuthor, $pageKeywords, $pageTitle, $html);
+?>
diff --git a/usecases/Measuring_UML_models/img/UMLClassDiagram.PNG b/usecases/Measuring_UML_models/img/UMLClassDiagram.PNG
new file mode 100644
index 0000000..8e0e85e
--- /dev/null
+++ b/usecases/Measuring_UML_models/img/UMLClassDiagram.PNG
Binary files differ
diff --git a/usecases/Measuring_UML_models/img/actionMeasures.PNG b/usecases/Measuring_UML_models/img/actionMeasures.PNG
new file mode 100644
index 0000000..4926d60
--- /dev/null
+++ b/usecases/Measuring_UML_models/img/actionMeasures.PNG
Binary files differ
diff --git a/usecases/Measuring_UML_models/img/actionMeasures_small.PNG b/usecases/Measuring_UML_models/img/actionMeasures_small.PNG
new file mode 100644
index 0000000..7407339
--- /dev/null
+++ b/usecases/Measuring_UML_models/img/actionMeasures_small.PNG
Binary files differ
diff --git a/usecases/Measuring_UML_models/img/barChart.PNG b/usecases/Measuring_UML_models/img/barChart.PNG
new file mode 100644
index 0000000..0ed60e8
--- /dev/null
+++ b/usecases/Measuring_UML_models/img/barChart.PNG
Binary files differ
diff --git a/usecases/Measuring_UML_models/img/completeConfiguration.PNG b/usecases/Measuring_UML_models/img/completeConfiguration.PNG
new file mode 100644
index 0000000..dd783f3
--- /dev/null
+++ b/usecases/Measuring_UML_models/img/completeConfiguration.PNG
Binary files differ
diff --git a/usecases/Measuring_UML_models/img/configurationManager.PNG b/usecases/Measuring_UML_models/img/configurationManager.PNG
new file mode 100644
index 0000000..b2423cf
--- /dev/null
+++ b/usecases/Measuring_UML_models/img/configurationManager.PNG
Binary files differ
diff --git a/usecases/Measuring_UML_models/img/generatedFiles.PNG b/usecases/Measuring_UML_models/img/generatedFiles.PNG
new file mode 100644
index 0000000..bf73a18
--- /dev/null
+++ b/usecases/Measuring_UML_models/img/generatedFiles.PNG
Binary files differ
diff --git a/usecases/Measuring_UML_models/img/moduleSelection.PNG b/usecases/Measuring_UML_models/img/moduleSelection.PNG
new file mode 100644
index 0000000..7067136
--- /dev/null
+++ b/usecases/Measuring_UML_models/img/moduleSelection.PNG
Binary files differ
diff --git a/usecases/Measuring_UML_models/img/newConfiguration.PNG b/usecases/Measuring_UML_models/img/newConfiguration.PNG
new file mode 100644
index 0000000..92d2a7e
--- /dev/null
+++ b/usecases/Measuring_UML_models/img/newConfiguration.PNG
Binary files differ
diff --git a/usecases/Measuring_UML_models/img/pieChart.PNG b/usecases/Measuring_UML_models/img/pieChart.PNG
new file mode 100644
index 0000000..4595494
--- /dev/null
+++ b/usecases/Measuring_UML_models/img/pieChart.PNG
Binary files differ
diff --git a/usecases/Measuring_UML_models/img/pieChart_small.PNG b/usecases/Measuring_UML_models/img/pieChart_small.PNG
new file mode 100644
index 0000000..2ba5e3e
--- /dev/null
+++ b/usecases/Measuring_UML_models/img/pieChart_small.PNG
Binary files differ
diff --git a/usecases/Measuring_UML_models/img/run.PNG b/usecases/Measuring_UML_models/img/run.PNG
new file mode 100644
index 0000000..51d30fd
--- /dev/null
+++ b/usecases/Measuring_UML_models/img/run.PNG
Binary files differ
diff --git a/usecases/Measuring_UML_models/img/sourceModelSelection.PNG b/usecases/Measuring_UML_models/img/sourceModelSelection.PNG
new file mode 100644
index 0000000..c75deb9
--- /dev/null
+++ b/usecases/Measuring_UML_models/img/sourceModelSelection.PNG
Binary files differ
diff --git a/usecases/Measuring_UML_models/img/tabularHTML.PNG b/usecases/Measuring_UML_models/img/tabularHTML.PNG
new file mode 100644
index 0000000..34e97f6
--- /dev/null
+++ b/usecases/Measuring_UML_models/img/tabularHTML.PNG
Binary files differ
diff --git a/usecases/Measuring_UML_models/img/targetFolderSelection.PNG b/usecases/Measuring_UML_models/img/targetFolderSelection.PNG
new file mode 100644
index 0000000..252c121
--- /dev/null
+++ b/usecases/Measuring_UML_models/img/targetFolderSelection.PNG
Binary files differ
diff --git a/usecases/Measuring_UML_models/index.php b/usecases/Measuring_UML_models/index.php
new file mode 100644
index 0000000..1782c4c
--- /dev/null
+++ b/usecases/Measuring_UML_models/index.php
@@ -0,0 +1,218 @@
+<?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.
+ $shortTitle = "Measuring UML models";
+ $pageTitle = "ATL Use Case - " . $shortTitle;
+ $pageKeywords = "";
+ $pageAuthor = "Freddy Allilaire";
+
+ # End: page-specific settings
+ #
+
+ # Paste your HTML content between the EOHTML markers!
+ $html = <<<EOHTML
+
+ <!-- Main part -->
+ <div id="midcolumn">
+ <h1>$pageTitle</h1>
+
+ <img align="right" src="../../resources/atlLogoSmall.png" valign="top" style="padding-left: 10px;" alt="ATL Logo" />
+ <a href="http://www.papyrusuml.org/"><img align="right" src="../../resources/Papyrus_48x48.gif" valign="top" style="padding-left: 10px;" alt="Papyrus" /></a>
+ <blockquote>
+ <ul>
+ <li><a href="#keywords"><b>Keywords</b></a></li>
+ <li><a href="#overview"><b>Overview</b></a></li>
+ <li><a href="#relatedUseCases"><b>Related Use Cases</b></a></li>
+ <li><a href="#download"><b>Download</b></a></li>
+ <li><a href="#acknowledgement"><b>Acknowledgement</b></a></li>
+ </ul>
+ </blockquote>
+
+ <hr class="clearer" />
+
+ <div id="container>
+ <p align="justify">
+ This use case shows how to use and integrate a model transformation service in a UML Modeler to compute and generate quality measures on UML models.
+ </p>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;"><a name="keywords"></a>Keywords</h4>
+ <table width="100%">
+ <COLGROUP>
+ <COL width="2%" />
+ <COL width="98%" />
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ <p align="justify">
+ UML Modeler,
+ <a href="http://www.eclipse.org/modeling/mdt/?project=uml2">UML 2</a>,
+ Measures
+ </p>
+ </td>
+ </tr>
+ </table>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;"><a name="overview"></a>Overview</h4>
+
+ <table width="100%">
+ <COLGROUP>
+ <COL width="2%" />
+ <COL width="98%" />
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ <p align="justify">
+ This use case presents how the Papyrus UML Modeler could be used to compute and generate quality measures on UML models. <a href="http://www.papyrusuml.org/">Papyrus</a> is a
+ dedicated tool for UML2 graphical modelling developed mainly by <a href="http://www-list.cea.fr/">CEA LIST</a>.
+ This open source tool is based on the Eclipse environment.
+ </p>
+ <p align="justify">
+ The figure below presents an example of UML Class Diagram made with Papyrus. Measures will be generated and computed on this working example:
+ </p>
+ <p align="center">
+ <img src="img/UMLClassDiagram.PNG" />
+ <br /><br />
+ <b>Sample of UML 2 Class Diagram</b>
+ </p>
+ <p align="justify">
+ The generation of measures on a UML model allows to perform several investigations. For example measuring the various models may bring interesting insight into the
+ consideration of these models. Furthermore comparing similar measures applied to models of various origins may bring interesting observations.
+ </p>
+ <p align="justify">
+ From a UML Class Diagram, the following measures are available and will be computed when the ATL service <i>"Generate Measures"</i> will be executed:
+ <ul>
+ <li><b>Total Number of Packages:</b> TNP is the total number of packages in the model.<br /><br /></li>
+ <li><b>Total Number of Classes:</b> TNC is the total number of classes in a package or the model.<br /><br /></li>
+ <li><b>Total Number of Attributes:</b> TNA is the total number of attributes in a class, package or the model.<br /><br /></li>
+ <li><b>Depth Inheritance Tree:</b> In cases involving multiple inheritances, the DIT will be the maximum length from the node to the root of the tree.<br /><br /></li>
+ <li><b>Number of Children:</b> NOC is the number of immediate subclasses subordinated to a class in the class hierarchy.<br /><br /></li>
+ <li><b>Number of Attributes:</b> NA is defined as the total number of attributes in a class.<br /><br /></li>
+ <li><b>Number of Attributes Inherited:</b> NAI is defined as the total number of attributes inherited by a subclass.<br /><br /></li>
+ <li>
+ <b>Attribute Inheritance Factor:</b> The Attribute Inheritance Factor (AIF) is defined as a quotient between the sum of inherited attributes in all classes of the
+ system under consideration and the total number of available attributes (locally defined plus inherited) for all classes.
+ </li>
+ </ul>
+ </p>
+ <p align="justify">
+ Others and more complex measures could be easily added and implemented by modifying the corresponding ATL transformation.
+ To see how to configure and run the "Measuring UML models" ATL service, please take a look to the <a href="userGuide.php">User Guide</a>.
+ </p>
+ <p align="justify">
+ The computed metrics will be displayed in 3 different representations: <b>Tabular HTML</b>, <b>SVG Bar Chart</b>, and <b>SVG Pie Chart</b>. The figures below present the
+ sample results generated from our working example:
+ <ul>
+ <li>
+ <b>Tabular HTML</b><br />
+ <div align="center"><img src="img/tabularHTML.PNG" /></div>
+ <br /><br />
+ </li>
+ <li>
+ <b>SVG Bar Chart</b><br />
+ <div align="center"><img src="img/barChart.PNG" /></div>
+ <br /><br />
+ </li>
+ <li>
+ <b>SVG Pie Chart</b><br />
+ <div align="center"><a href="img/pieChart.PNG"><img src="img/pieChart_small.PNG" /></a></div>
+ <br /><br />
+ </li>
+ </ul>
+ </p>
+ </td>
+ </tr>
+ </table>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;">
+ <a name="relatedUseCases"></a>Related Use Cases
+ </h4>
+ <table>
+ <COLGROUP>
+ <COL width="2%" />
+ <COL width="98%" />
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ <p align="justify">
+ None at the current time.
+ </p>
+ </td>
+ </tr>
+ </table>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;">
+ <a name="download">Download</a>
+ </h4>
+
+ <table width="100%">
+ <COLGROUP>
+ <COL width="25%">
+ <COL width="75%">
+ </COLGROUP>
+ <tr>
+ <td align="center"><a href="http://www.papyrusuml.org/"><img src="../../resources/Papyrus_48x48.gif" /></a></td>
+ <td><a href="http://www.papyrusuml.org/"><b>Papyrus</b></a>, an open-source graphical modeler tool for UML2 and based on Eclipse</a>.</td>
+ </tr>
+ <tr>
+ <td align="center"><a href="http://www.papyrusuml.org/scripts/home/publigen/content/templates/show.asp?P=131&L=EN&ITEMID=10#4"><h3>ATL Service</h3></a></td>
+ <td>Papyrus add-in containing the implementation of this use case.</td>
+ </tr>
+ <tr>
+ <td align="center"><h3><a href="userGuide.php">User Guide</a></h3></td>
+ <td>This user guide explains how to configure and launch the ATL service in Papyrus.</td>
+ </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>Acknowledgement
+ </h4>
+
+ <table width="100%">
+ <COLGROUP>
+ <COL width="2%">
+ <COL width="98%">
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ The present work is being supported by the <a href="http://www.usine-logicielle.org">Usine Logicielle project of the System@tic Paris Region Cluster</a>.
+ </td>
+ </tr>
+ </table>
+
+ </div>
+ </div>
+
+ <div id="rightcolumn">
+ <div class="sideitem">
+ <h6>General Information</h6>
+ <ul>
+ <li style="list-style:none">May 2007</li>
+ <li style="list-style:none">By <a href="http://www.sciences.univ-nantes.fr/lina/atl/contrib/allilaire">Freddy Allilaire</a> (INRIA), Rémi Schnekenburger (CEA LIST)</li>
+ <li style="list-style:none"><br />Please, ask your questions on the <a href="news://news.eclipse.org/eclipse.modeling.m2m">M2M newsgroup</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/Measuring_UML_models/userGuide.php b/usecases/Measuring_UML_models/userGuide.php
new file mode 100644
index 0000000..0daaa46
--- /dev/null
+++ b/usecases/Measuring_UML_models/userGuide.php
@@ -0,0 +1,147 @@
+<?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 = "Measuring UML models - User Guide";
+ $pageKeywords = "";
+ $pageAuthor = "Freddy Allilaire";
+
+ # End: page-specific settings
+ #
+
+ # Paste your HTML content between the EOHTML markers!
+ $html = <<<EOHTML
+
+ <!-- Main part -->
+ <div id="midcolumn">
+ <h1>$pageTitle</h1>
+
+ <img align="right" src="../../resources/atlLogoSmall.png" valign="top" style="padding-left: 10px;" alt="ATL Logo" />
+ <a href="http://www.papyrusuml.org/"><img align="right" src="../../resources/Papyrus_48x48.gif" valign="top" style="padding-left: 10px;" alt="Papyrus" /></a>
+
+ <hr class="clearer" />
+
+ <div id="container>
+ <p align="justify">
+ <table border="3" width="100%" cellspacing="0" cellpadding="20">
+ <tr><td align="justify" bgcolor="#b0c8f4">
+ This user guide explains how to configure and launch the <a href="index.php">Measuring UML models</a> ATL service in Papyrus.
+ </td></tr>
+ </table>
+ </p>
+
+ <p align="justify">
+ First step is to create a new transformation configuration, using the <b>Run As</b> button.
+ </p>
+ <p align="center">
+ <img src="img/run.PNG" />
+ </p>
+ <p align="center">
+ <img src="img/configurationManager.PNG" />
+ </p>
+ <p align="justify">
+ Thanks to the pop-up menu available on Papyrus transformation, you can create a new transformation configuration. This transformation configuration will contain all
+ necessary parameters for your transformation.
+ </p>
+ <p align="center">
+ <img src="img/newConfiguration.PNG" />
+ </p>
+ <p align="justify">
+ Thanks to the <b>Browse...</b> button in the Module group, the transformation module can be selected against all transformation modules available for Papyrus. In this use case,
+ please select the <b>UML Measures</b> module.
+ </p>
+ <p align="center">
+ <img src="img/moduleSelection.PNG" />
+ </p>
+ <p align="justify">
+ The next step is to choose the uml file on which the transformation will run. The following window filters the proposed files using their extensions; you can only select
+ uml files.
+ </p>
+ <p align="center">
+ <img src="img/sourceModelSelection.PNG" />
+ </p>
+ <p align="justify">
+ The next step is the selection of the target folder. It is not possible to select a project yet. In fact, Papyrus transformations must be run into a folder (yellow folder
+ icons). This should be fixed in next versions of Papyrus tool. The selected folder will contain the results of the transformation.
+ </p>
+ <p align="center">
+ <img src="img/targetFolderSelection.PNG" />
+ </p>
+ <p align="justify">
+ The following snapshot gives an example of what you should have just before launching the transformation. The transformation is launched using the <b>Run</b> button.
+ </p>
+ <p align="center">
+ <img src="img/completeConfiguration.PNG" />
+ </p>
+ <p align="justify">
+ This transformation outputs 3 files: 1 html page with a table containing results, and 2 SVG files. These files are contained in the folder given in the configuration window.
+ </p>
+ <p align="justify">
+ <ul>
+ <li>
+ <b>Tabular HTML</b><br />
+ <div align="center"><img src="img/tabularHTML.PNG" /></div>
+ <br /><br />
+ </li>
+ <li>
+ <b>SVG Bar Chart</b><br />
+ <div align="center"><img src="img/barChart.PNG" /></div>
+ <br /><br />
+ </li>
+ <li>
+ <b>SVG Pie Chart</b><br />
+ <div align="center"><a href="img/pieChart.PNG"><img src="img/pieChart_small.PNG" /></a></div>
+ <br /><br />
+ </li>
+ </ul>
+ </p>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;">
+ <a name="acknowledgement"></a>Acknowledgement
+ </h4>
+
+ <table width="100%">
+ <COLGROUP>
+ <COL width="2%">
+ <COL width="98%">
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ The present work is being supported by the <a href="http://www.usine-logicielle.org">Usine Logicielle project of the System@tic Paris Region Cluster</a>.
+ </td>
+ </tr>
+ </table>
+
+ </div>
+ </div>
+
+ <div id="rightcolumn">
+ <div class="sideitem">
+ <h6>General Information</h6>
+ <ul>
+ <li style="list-style:none">May 2007</li>
+ <li style="list-style:none">By <a href="http://www.sciences.univ-nantes.fr/lina/atl/contrib/allilaire">Freddy Allilaire</a> (INRIA), Rémi Schnekenburger (CEA LIST)</li>
+ <li style="list-style:none"><br />Please, ask your questions on the <a href="news://news.eclipse.org/eclipse.modeling.m2m">M2M newsgroup</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/ModelAdaptation/AMLEdited_1024x720.htm b/usecases/ModelAdaptation/AMLEdited_1024x720.htm
new file mode 100644
index 0000000..f4c5a0a
--- /dev/null
+++ b/usecases/ModelAdaptation/AMLEdited_1024x720.htm
@@ -0,0 +1,15 @@
+<!-- saved from url=(0014)about:internet -->
+<HTML>
+<BODY>
+<center><OBJECT CLASSID="clsid:D27CDB6E-AE6D-11cf-96B8-444553540000" WIDTH="1024" HEIGHT="740" CODEBASE="http://active.macromedia.com/flash5/cabs/swflash.cab#version=7,0,0,0">
+<PARAM NAME=movie VALUE="AMLEdited_1024x720.swf">
+<PARAM NAME=play VALUE=true>
+<PARAM NAME=loop VALUE=false>
+<PARAM NAME=wmode VALUE=transparent>
+<PARAM NAME=quality VALUE=low>
+<EMBED SRC="AMLEdited_1024x720.swf" WIDTH=1024 HEIGHT=740 quality=low loop=false wmode=transparent TYPE="application/x-shockwave-flash" PLUGINSPAGE="http://www.macromedia.com/shockwave/download/index.cgi?P1_Prod_Version=ShockwaveFlash">
+</EMBED>
+</OBJECT></center>
+<SCRIPT src='AMLEdited_1024x720.js'></script>
+</BODY>
+</HTML>
diff --git a/usecases/ModelAdaptation/AMLEdited_1024x720.js b/usecases/ModelAdaptation/AMLEdited_1024x720.js
new file mode 100644
index 0000000..4cd18d7
--- /dev/null
+++ b/usecases/ModelAdaptation/AMLEdited_1024x720.js
@@ -0,0 +1,3 @@
+obj=document.getElementsByTagName('object');
+for (var i=0; i<obj.length; ++i)
+ obj[i].outerHTML=obj[i].outerHTML;
diff --git a/usecases/ModelAdaptation/AMLEdited_1024x720.swf b/usecases/ModelAdaptation/AMLEdited_1024x720.swf
new file mode 100644
index 0000000..f820ac5
--- /dev/null
+++ b/usecases/ModelAdaptation/AMLEdited_1024x720.swf
Binary files differ
diff --git a/usecases/ModelAdaptation/AMLStrategy.PNG b/usecases/ModelAdaptation/AMLStrategy.PNG
new file mode 100644
index 0000000..fe56266
--- /dev/null
+++ b/usecases/ModelAdaptation/AMLStrategy.PNG
Binary files differ
diff --git a/usecases/ModelAdaptation/aml-adaptation.psf b/usecases/ModelAdaptation/aml-adaptation.psf
new file mode 100644
index 0000000..a7c5330
--- /dev/null
+++ b/usecases/ModelAdaptation/aml-adaptation.psf
@@ -0,0 +1,6 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<psf version="2.0">
+<provider id="org.eclipse.team.cvs.core.cvsnature">
+<project reference="1.0,:pserver:dev.eclipse.org:/cvsroot/modeling,org.eclipse.m2m/org.eclipse.m2m.atl/usecases/org.eclipse.m2m.atl.research.aml/examples/Adaptation,Adaptation"/>
+</provider>
+</psf>
\ No newline at end of file
diff --git a/usecases/ModelAdaptation/conceptualLinkRule.PNG b/usecases/ModelAdaptation/conceptualLinkRule.PNG
new file mode 100644
index 0000000..b12ae39
--- /dev/null
+++ b/usecases/ModelAdaptation/conceptualLinkRule.PNG
Binary files differ
diff --git a/usecases/ModelAdaptation/index.php b/usecases/ModelAdaptation/index.php
new file mode 100644
index 0000000..6e4cafe
--- /dev/null
+++ b/usecases/ModelAdaptation/index.php
@@ -0,0 +1,414 @@
+<?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: Kelly Garces
+ # Date: 2009-11-09
+ #
+ # Description: model adaptation use case
+ #
+ #
+ #****************************************************************************
+
+ #
+ # Begin: page-specific settings. Change these.
+ $pageTitle = "ATL Use Case - Model Adaptation";
+ $pageKeywords = "Evolution, Adaptation, Model Transformation, Petrinet";
+ $pageAuthor = "Kelly Garces";
+
+ # End: page-specific settings
+ #
+
+ # Paste your HTML content between the EOHTML markers!
+ $html = <<<EOHTML
+
+ <!-- Main part -->
+ <div id="midcolumn">
+ <h1>$pageTitle</h1>
+
+ <img align="right" src="../../resources/atlLogoSmall.png" valign="top" style="padding-left: 10px;" alt="ATL Logo" />
+ <blockquote>
+ <ul>
+ <li><a href="#keywords"><b>Keywords</b></a></li>
+ <li><a href="#prerequisites"><b>Prerequisites</b></a></li>
+ <li><a href="#overview"><b>Overview</b></a></li>
+ <li><a href="#relatedUseCases"><b>Related Use Cases</b></a></li>
+ <li><a href="#references"><b>References</b></a></li>
+ <li><a href="#download"><b>Download</b></a></li>
+ <li><a href="#demo"><b>Demo</b></a></li>
+ <li><a href="#acknowledgement"><b>Acknowledgement</b></a></li>
+ </ul>
+ </blockquote>
+
+ <hr class="clearer" />
+
+ <div>
+ <p align="justify">
+ The evolution of a metamodel may render its related terminal models invalid.
+ This use case proposes a three-step solution that automatically adapts terminal models to their evolving metamodels.
+ The main contribution is the precise detection of metamodel changes by using the <a href="http://wiki.eclipse.org/AML">AtlanMod Matching Language (AML)</a>, a DSL built on top
+ of ATL and AMW. The running example is the Petrinet models.
+ </p>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;"><a name="prerequisites"></a>Prerequisites</h4>
+ <table width="100%">
+ <COLGROUP>
+ <COL width="2%" />
+ <COL width="98%" />
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ <a href="http://wiki.eclipse.org/AML">AML</a>, AMW, and ATL 3.0 are required to execute this use case.
+ </td>
+ </tr>
+ </table>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;"><a name="keywords"></a>Keywords</h4>
+ <table width="100%">
+ <COLGROUP>
+ <COL width="2%" />
+ <COL width="98%" />
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ <p align="justify">
+ Metamodel Evolution,
+ Model Adaptation,
+ Model Transformation,
+ Petrinet.
+ </p>
+ </td>
+ </tr>
+ </table>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;"><a name="overview"></a>Overview</h4>
+
+ <table width="100%">
+ <COLGROUP>
+ <COL width="2%" />
+ <COL width="98%" />
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ <p align="justify">
+ This use case presents a solution to the model adaptation problem. This solution has been presented in [1].
+ Figure 1 illustrates the problem: a metamodel <b>MM1</b> evolves into a metamodel <b>MM2</b> (see the dotted arrow). Our concern is to adapt any terminal model <b>M1</b> conforming to <b>MM1</b> to the new metamodel version <b>MM2</b> (see the dashed arrow).
+ </p>
+ <p align="center">
+ <img src="overviewEvolution.PNG" />
+ <br /><br />
+ <b>Figure 1. Metamodel evolution and model adaptation</b>
+ </p>
+ <p align="justify">
+ The use case proposes a three-step adaptation (see Figure 2). Firstly, an matching strategy computes the equivalences and changes between <b>MM1</b> and <b>MM2</b>. Secondly, a HOT derives an ATL transformation from the discovered equivalences and changes. Finally, this transformation brings <b>M1</b> into agreement with <b>MM2</b>, and persists the result in <b>M2</b>.
+ We implement the prototype on the AMMA platform. More specifically, we use the <a href="http://wiki.eclipse.org/AML">AtlanMod Matching Language (AML)</a> to specify the matching strategy, <a href="http://wiki.eclipse.org/AMW">AMW</a> to work with models of equivalences and changes, and <a href="http://wiki.eclipse.org/ATL">ATL</a> to implement the HOT. The HOT generates the adaptation transformation in ATL code too.
+ </p>
+ <p align="center">
+ <img src="overviewApproach.PNG" />
+ <br /><br />
+ <b>Figure 2. Approach Overview</b>
+ </p>
+ <p align="justify">
+ The bulk of this use case is devoted to the first step that discovers equivalences, as well as simple and complex changes. We explicitly distinguish two kinds of changes because complex changes need a more insightful adaptation that simple changes. Whereas a simple change describes the addition, deletion, or update of one metamodel concept, a complex change integrates a set of actions affecting multiple concepts. The reader interested on examples of simple and complex changes may consult [2].
+ </p>
+ <p align="justify">
+ The running example is based on the two versions of the Petri Net metamodel provided by [3]. Figure 3 illustrates versions 0 (<b>MM1</b>) and 2 (<b>MM2</b>). <b>MM1</b> represents simple Petri Nets. These nets may consist of any number of places and transitions. A transition has at least one input and one output place. <b>MM2</b> represents more complex Petri Nets.
+ The extraction of the reference <b>dst</b> illustrates a complex change named <b>Extract class</b>. This implies to add and remove a reference, add a class, and associate classes. In considering these actions as isolated simple changes, we may skip changes without migrating involved data from <b>M1</b> to <b>M2</b>. In contrast, when we distinguish the complex change, we infer (for instance) that the added property (e.g., <b>dst</b>), contained in the new class <b>PTArc</b>, actually corresponds to the property <b>dst</b> removed from the class <b>Place</b>. Since we know the relationship between the properties we can migrate the data. We thus need to explicitly distinguish complex changes in order to properly derive adaptation transformations.
+ </p>
+ <p align="center">
+ <img src="petrinetMM.PNG" />
+ <br /><br />
+ <b>Figure 3. Petrinet metamodels</b>
+ </p>
+
+ <p align="justify">
+ <h3>First step - Matching equivalences and changes</h3>
+
+ <h4>Model of equivalences and changes </h4>
+ Before describing the matching step, we explain how matching models represent equivalences and changes.
+ Such models conforms to the <b>Matching metamodel</b> (which extends the AMW core metamodel) illustrated in Figure 4.
+ The main concept is <b>Equal</b> which describes a mapping (or correspondence) between an element of <b>MM1</b> (<b>leftElement</b>) and an element of <b>MM2</b> (<b>rightElement</b>). <b>Equal</b> has a similarity value (between 0 and 1) that represents the plausibility of the correspondence. An equivalence with similarity value 1 represents that the <b>MM2</b> element is an identical copy of the <b>MM1</b> element. An equivalence with similarity value 0.7 describes that the <b>MM2</b> element is a copy of the <b>MM1</b> element including simple modifications. An equivalence with similarity value 0 link elements different to each other. Other basic concepts are <b>Added</b> and <b>Deleted</b> which mark a metamodel element as deleted/added from/into <b>MM1</b>.
+ </p>
+ <p align="center">
+ <img src="matchingMetamodel.PNG" />
+ <br /><br />
+ <b>Figure 4. Excerpt of the matching metamodel</b>
+ </p>
+ <p align="justify">
+ <h4>Matching step</h4>
+ Matching models are computed by AML strategies, i.e., processes that incrementally execute a set of ATL transformations.
+ Figure 5 shows an excerpt of the used AML strategy. This indicates how ATL transformations (generated by the AML compiler) interact each other to deliver the equivalences and changes.
+ <table width="100%">
+ <COLGROUP>
+ <COL width="2%" />
+ <COL width="98%" />
+ </COLGROUP>
+ <tr>
+ <td>*</td>
+ <td><b>TypeClass, TypeReference, and TypeAttribute</b> prepares three collections of equivalences by matching classes, references, and attributes of <b>MM1</b> and <b>MM2</b>.</td>
+ </tr>
+ <tr>
+ <td>*</td>
+ <td><b>Merge</b> combines the three collections into a single equal model.</td>
+ </tr>
+ <tr>
+ <td>*</td>
+ <td><b>Levenshtein</b> computes similarity values by comparing the edit distance of metamodel element names.</b>
+ </tr>
+ <tr>
+ <td>*</td>
+ <td><b>ThresholdMaxDelta</b> selects an equivalence when its similarity satisfies the range of tolerance [Threshold-Delta, Threshold].</b>
+ </tr>
+ <tr>
+ <td>*</td>
+ <td><b>Propagation, SF, and Normalization</b> instruments the Similarity Flooding algorithm [4].</td>
+ </tr>
+ <tr>
+ <td>*</td>
+ <td><b>WeightedAverage</b> aggregates the similarity values returned by Levenshtein and Normalization.</td>
+ </tr>
+ <tr>
+ <td>*</td>
+ <td><b>BothMaxSim</b>, in turn, selects a given equivalence if its similarity value is the highest among the values of equivalences of two sets (e.g., leftSet and rightSet). The leftSet contains all the equivalences linking a left concept, and the rightSet the equivalences linking a right concept.</td>
+ </tr>
+ <tr>
+ <td>*</td>
+ <td>Whereas <b>Differentiation</b> recognizes equivalences, additions, and deletions, <b>TypeDifferentiation</b> gives a type to them. The type indicates what kind of elements are linked on, for example, the type <b>EqualReference</b> indicates an equivalence between references. <b>Rewriting</b> reorganizes a given equal model to make it closer to transformations. <b>FlattenFeatures</b> copies <b>EqualAttribute</b> and <b>EqualReference</b> contained in <b>EqualClass</b> (e.g., matching class C) into every <b>EqualClass</b> matching a class that inherits directly or indirectly from C.</td>
+ </tr>
+ </table>
+ </p>
+ <p align="center">
+ <code><pre>modelsFlow {
+
+ tp = TypeClass[map2]
+ typeRef = TypeReference[map2]
+ typeAtt = TypeAttribute[map2]
+
+ merged = Merge[1.0:tp, 1.0:typeRef, 1.0:typeAtt]
+
+ nam = Name[merged]
+
+ filtered = ThresholdMaxDelta[nam]
+ prop = Propagation[filtered]
+ sf = SF[filtered](prop)
+ norm = Normalization[sf]
+
+ tmpresult = WeightedAverage[0.5 : norm, 0.5:nam]
+
+ result = BothMaxSim[tmpresult]
+
+ diff = Differentiation[result]
+ td = TypeDifferentiation[diff]
+ cl = ConceptualLink[td]
+ rw = Rewriting[cl]
+ flatt = FlattenFeatures[rw]
+}</pre></code>
+ <br /><br />
+ <b>Figure 5. AML strategy excerpt</b>
+ </p>
+ <p align="justify">
+ The transformations above are generic enough to be applied to many use cases. It is <b>ConceptualLink</b> the one that figures out complex changes, and therefore leverages the solution to the model adaptation problem.
+ For example, Figure 6 shows a rule that verifies if change <b>Extract Class</b> has happened.
+ The helper 'isExtractClass' evaluates if:
+ 1) there is a relation between the owner classes of the structural features referenced by <b>EqualStructuralFeature</b>
+ 2) the right class is a new class.
+ If the conditions are satisfied, the rule decorates a simple equivalence with the type <b>ExtractClass</b>.
+
+ </p>
+ <p align="center">
+ <img src="conceptualLinkRule.PNG" />
+ <br /><br />
+ <b>Figure 6. A conceptual link rule</b>
+ </p>
+ <p align="justify">
+ Note that our approach may need the user to refine the results. The refinement can happen at high-abstraction level, i.e.,
+ over final matching models, or at low-abstraction level, i.e., over generated adaptation transformations.
+ </p>
+ <p align="justify">
+ <h3>Second step - Translation to adaptation transformations</h3>
+ In this step, the equivalences and differences are translated into an ATL adaptation transformation via a HOT.
+
+ <table width="100%">
+ <COLGROUP>
+ <COL width="2%" />
+ <COL width="98%" />
+ </COLGROUP>
+ <tr>
+ <td>*</td>
+ <td>Yield a transformation rule for each <b>EqualClass</b> that links no abstract classes. The HOT takes referred left and right classes to yield input and output patterns.</td>
+ </tr>
+ <tr>
+ <td>*</td>
+ <td>Create a binding for each <b>EqualStructuralFeatures</b> attached to a <b>EqualClass</b>. The binding complexity depends on the <b>Equal</b> type. While a simple <b>EqualStructuralFeature</b> generates a simple binding, <b>EqualStructuralFeature</b> extensions (e.g., <b>ExtractClass</b>) generate more elaborated bindings. In general, sophisticated bindings instruments the code that adapt <b>M1</b> models to complex changes.</td>
+ </tr>
+ </table>
+ <br>
+ Figure 7 shows an ATL adaptation transformation which is generated by the HOT. This creates the transformation rule <b>Place2Place</b> (line 5) from the equivalence (<b>Place</b>, <b>Place</b>). The <b>from</b> part matches the elements conforming to <b>Place</b> (lines 7-9). The <b>to</b> part creates elements conforming to <b>Place</b>. The HOT moreover generates a complex binding (see lines 13-14) from the equivalence (<b>out</b>, <b>dst</b>). The binding calls a lazy rule (i.e., <b>PTArc</b>) to initialize <b>dst</b> and <b>src</b> of <b>PTArc</b> (lines 20-29) using the values <b>Transition</b> and <b>Place</b>.
+ </p>
+ <p align="center">
+ <img src="petrinetAdapTransf.PNG" />
+ <br /><br />
+ <b>Figure 7. Petrinet transformation excerpt</b>
+ </p>
+ <p align="justify">
+ <h3>Third step - Adaptation transformation execution</h3>
+ This step simply executes the generated adaptation transformation. The transformation takes any terminal model <b>M1</b> and generates a terminal model <b>M2</b>.
+ </p>
+ </td>
+ </tr>
+ </table>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;">
+ <a name="relatedUseCases"></a>Related Use Cases
+ </h4>
+ <table>
+ <COLGROUP>
+ <COL width="30%" />
+ <COL width="70%" />
+ </COLGROUP>
+ <tr>
+ <td>
+ <a href="../../../../gmt/amw/usecases/matching"><h3>Matching</h3></a>
+ </td>
+ <td>
+ This use case introduces the fundamentals behind AML strategies.
+ </td>
+ </tr>
+ <tr>
+ <td>
+ <a href="../../../../gmt/amw/usecases/compare"><h3>Metamodel Comparison and Model Migration</h3></a>
+ </td>
+ <td>
+ An application of matching to model migration. The difference between the model migration use case and
+ our use case is that the latter uses AML to automatically generate the ATL transformations.
+ </td>
+ </tr>
+ </table>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;">
+ <a name="references"></a>References
+ </h4>
+
+ <table width="100%">
+ <tr valign="top">
+ <td>
+
+ [1]
+
+ </td>
+ <td>
+ Garces, K., Jouault, F., Cointe, P., Bezivin, J.: Managing Model Adaptation by
+ Precise Detection of Metamodel Changes. In: In Proc. of ECMDA 2009, Enschede,
+ The Netherlands, Springer, 2009.
+ </td>
+ </tr>
+ <tr valign="top">
+ <td>
+
+ [2]
+
+ </td>
+ <td>
+ Garces K., Jouault F., Cointe P., Bezivin J., Practical Adaptation of Models to Evolving Metamodels,
+ Technical report, INRIA, 2008.
+ </td>
+ </tr>
+ <tr valign="top">
+ <td>
+
+ [3]
+
+ </td>
+ <td>
+ Wachsmuth G., Metamodel Adaptation and Model Co-adaptation, in E. Ernst (ed.), ECOOP 2007, Berlin, Germany, Proceedings,
+ vol. 4609 of Lecture Notes in Computer Science, Springer, 2007.
+ </td>
+ </tr>
+ <tr valign="top">
+ <td>
+
+ [4]
+
+ </td>
+ <td>
+ Melnik S., Garcia-Molina H., Rahm E., Similarity Flooding: A Versatile Graph Matching
+ Algorithm and ist Application to Schema Matching, Proc. 18th ICDE, San Jose, CA, 2002.
+ </td>
+ </tr>
+ </table>
+
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;">
+ <a name="download">Download</a>
+ </h4>
+
+ <table width="100%">
+ <COLGROUP>
+ <COL width="25%">
+ <COL width="75%">
+ </COLGROUP>
+ <tr>
+ <td align="center"><a href="aml-adaptation.psf"><h3>Complete scenario</h3></a></td>
+ <td>A psf file that points to the Adaptation AML project. Please download this file on your local disk, and then import the project in Eclipse using : File->Import->Team->Team Project Set. Besides the Adaptation project, you need the AMLLibrary project, find <a href=http://wiki.eclipse.org/AML#Install_AML_from_CVS>here</a> the instructions to download it. Finally, the file 'Readme.txt' contains all the instructions to execute the AML strategy.</td>
+ </tr>
+ </table>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;">
+ <a name="demo">Demo</a>
+ </h4>
+
+ <table width="100%">
+ <COLGROUP>
+ <COL width="25%">
+ <COL width="75%">
+ </COLGROUP>
+ <tr>
+ <td align="center"><a href="AMLEdited_1024x720.htm"><h3>Demo</h3></a></td>
+ <td>We encourage you to look at this demo which shows the main AML functionalities</td>
+ </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>Acknowledgement
+ </h4>
+
+ <table width="100%">
+ <COLGROUP>
+ <COL width="2%">
+ <COL width="98%">
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ This work has been partially funded by the <a href="http://flfs.emn.fr/">FLFS</a> ANR project (Families of Language for Families of Systems).
+ </td>
+ </tr>
+ </table>
+
+ </div>
+ </div>
+
+ <div id="rightcolumn">
+ <div class="sideitem">
+ <h6>General Information</h6>
+ <ul>
+ <li style="list-style:none">December 2009</li>
+ <li style="list-style:none">
+ By <a href="http://www.emn.fr/z-info/atlanmod/index.php/User:Garces">Kelly Garces</a> (Ecole des Mines de Nantes)
+ </li>
+ <li style="list-style:none"><br />Please, ask your questions on the <a href="news://news.eclipse.org/eclipse.modeling.m2m">M2M newsgroup</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/ModelAdaptation/matchingMetamodel.PNG b/usecases/ModelAdaptation/matchingMetamodel.PNG
new file mode 100644
index 0000000..c332c56
--- /dev/null
+++ b/usecases/ModelAdaptation/matchingMetamodel.PNG
Binary files differ
diff --git a/usecases/ModelAdaptation/overviewApproach.PNG b/usecases/ModelAdaptation/overviewApproach.PNG
new file mode 100644
index 0000000..fefc3a4
--- /dev/null
+++ b/usecases/ModelAdaptation/overviewApproach.PNG
Binary files differ
diff --git a/usecases/ModelAdaptation/overviewEvolution.PNG b/usecases/ModelAdaptation/overviewEvolution.PNG
new file mode 100644
index 0000000..28b11f6
--- /dev/null
+++ b/usecases/ModelAdaptation/overviewEvolution.PNG
Binary files differ
diff --git a/usecases/ModelAdaptation/petrinetAdapTransf.PNG b/usecases/ModelAdaptation/petrinetAdapTransf.PNG
new file mode 100644
index 0000000..a7e277c
--- /dev/null
+++ b/usecases/ModelAdaptation/petrinetAdapTransf.PNG
Binary files differ
diff --git a/usecases/ModelAdaptation/petrinetMM.PNG b/usecases/ModelAdaptation/petrinetMM.PNG
new file mode 100644
index 0000000..b37075b
--- /dev/null
+++ b/usecases/ModelAdaptation/petrinetMM.PNG
Binary files differ
diff --git a/usecases/ModelsMeasurement/img/XHTML_1.PNG b/usecases/ModelsMeasurement/img/XHTML_1.PNG
new file mode 100644
index 0000000..2696f45
--- /dev/null
+++ b/usecases/ModelsMeasurement/img/XHTML_1.PNG
Binary files differ
diff --git a/usecases/ModelsMeasurement/img/XHTML_2.PNG b/usecases/ModelsMeasurement/img/XHTML_2.PNG
new file mode 100644
index 0000000..7b41dbf
--- /dev/null
+++ b/usecases/ModelsMeasurement/img/XHTML_2.PNG
Binary files differ
diff --git a/usecases/ModelsMeasurement/img/barChart_1.PNG b/usecases/ModelsMeasurement/img/barChart_1.PNG
new file mode 100644
index 0000000..d160a1a
--- /dev/null
+++ b/usecases/ModelsMeasurement/img/barChart_1.PNG
Binary files differ
diff --git a/usecases/ModelsMeasurement/img/barChart_1Small.PNG b/usecases/ModelsMeasurement/img/barChart_1Small.PNG
new file mode 100644
index 0000000..4824244
--- /dev/null
+++ b/usecases/ModelsMeasurement/img/barChart_1Small.PNG
Binary files differ
diff --git a/usecases/ModelsMeasurement/img/barChart_2.PNG b/usecases/ModelsMeasurement/img/barChart_2.PNG
new file mode 100644
index 0000000..66a8b3b
--- /dev/null
+++ b/usecases/ModelsMeasurement/img/barChart_2.PNG
Binary files differ
diff --git a/usecases/ModelsMeasurement/img/barChart_2Small.PNG b/usecases/ModelsMeasurement/img/barChart_2Small.PNG
new file mode 100644
index 0000000..79cb3b8
--- /dev/null
+++ b/usecases/ModelsMeasurement/img/barChart_2Small.PNG
Binary files differ
diff --git a/usecases/ModelsMeasurement/img/pieChart_1.PNG b/usecases/ModelsMeasurement/img/pieChart_1.PNG
new file mode 100644
index 0000000..337696a
--- /dev/null
+++ b/usecases/ModelsMeasurement/img/pieChart_1.PNG
Binary files differ
diff --git a/usecases/ModelsMeasurement/img/pieChart_1Small.PNG b/usecases/ModelsMeasurement/img/pieChart_1Small.PNG
new file mode 100644
index 0000000..163d1e5
--- /dev/null
+++ b/usecases/ModelsMeasurement/img/pieChart_1Small.PNG
Binary files differ
diff --git a/usecases/ModelsMeasurement/img/pieChart_2.PNG b/usecases/ModelsMeasurement/img/pieChart_2.PNG
new file mode 100644
index 0000000..6d52697
--- /dev/null
+++ b/usecases/ModelsMeasurement/img/pieChart_2.PNG
Binary files differ
diff --git a/usecases/ModelsMeasurement/img/pieChart_2Small.PNG b/usecases/ModelsMeasurement/img/pieChart_2Small.PNG
new file mode 100644
index 0000000..f439514
--- /dev/null
+++ b/usecases/ModelsMeasurement/img/pieChart_2Small.PNG
Binary files differ
diff --git a/usecases/ModelsMeasurement/img/tabularHTML_1.PNG b/usecases/ModelsMeasurement/img/tabularHTML_1.PNG
new file mode 100644
index 0000000..c4d5522
--- /dev/null
+++ b/usecases/ModelsMeasurement/img/tabularHTML_1.PNG
Binary files differ
diff --git a/usecases/ModelsMeasurement/img/tabularHTML_1Small.PNG b/usecases/ModelsMeasurement/img/tabularHTML_1Small.PNG
new file mode 100644
index 0000000..fc8d0c8
--- /dev/null
+++ b/usecases/ModelsMeasurement/img/tabularHTML_1Small.PNG
Binary files differ
diff --git a/usecases/ModelsMeasurement/img/tabularHTML_2.PNG b/usecases/ModelsMeasurement/img/tabularHTML_2.PNG
new file mode 100644
index 0000000..9aa7e18
--- /dev/null
+++ b/usecases/ModelsMeasurement/img/tabularHTML_2.PNG
Binary files differ
diff --git a/usecases/ModelsMeasurement/img/tabularHTML_2Small.PNG b/usecases/ModelsMeasurement/img/tabularHTML_2Small.PNG
new file mode 100644
index 0000000..a6f0f65
--- /dev/null
+++ b/usecases/ModelsMeasurement/img/tabularHTML_2Small.PNG
Binary files differ
diff --git a/usecases/ModelsMeasurement/index.php b/usecases/ModelsMeasurement/index.php
new file mode 100644
index 0000000..52dae63
--- /dev/null
+++ b/usecases/ModelsMeasurement/index.php
@@ -0,0 +1,255 @@
+<?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.
+ $shortTitle = "Models Measurement";
+ $pageTitle = "ATL Use Case - " . $shortTitle;
+ $pageKeywords = "";
+ $pageAuthor = "Freddy Allilaire";
+
+ # End: page-specific settings
+ #
+
+ # Paste your HTML content between the EOHTML markers!
+ $html = <<<EOHTML
+
+ <!-- Main part -->
+ <div id="midcolumn">
+ <h1>$pageTitle</h1>
+
+ <img align="right" src="../../resources/atlLogoSmall.png" valign="top" style="padding-left: 10px;" alt="ATL Logo" />
+ <blockquote>
+ <ul>
+ <li><a href="#keywords"><b>Keywords</b></a></li>
+ <li><a href="#overview"><b>Overview</b></a></li>
+ <li><a href="#references"><b>References</b></a></li>
+ <li><a href="#relatedUseCases"><b>Related Use Cases</b></a></li>
+ <li><a href="#download"><b>Download</b></a></li>
+<!-- <li><a href="#acknowledgement"><b>Acknowledgement</b></a></li>-->
+ </ul>
+ </blockquote>
+
+ <hr class="clearer" />
+
+ <div>
+ <p align="justify">
+ This use case shows how to compute and generate measures on terminal models using ATL 2.0RC2. The measures can be processed on KM3
+ metamodels or UML models. And the measurement data can be represented with HTML, SVG or XHTML.
+ This work has been done in collaboration between <a href="http://www.sodius.com/">SODIUS</a> and the <a href="http://www.sciences.univ-nantes.fr/lina/atl/">ATLAS Group</a>.
+ </p>
+
+ <p align="justify">
+ As a complementary application to this contribution, an online service is provided at SODIUS's web site under the name "MC-Meter".
+ The application offers you to freely measure your models and get an interactive report on them, using the Open Source contribution.
+ The input models can be KM3 meta-models or UML models (in version 2.1), and the interactive report is sent back by email, using XHTML format with CSS.
+ Sample of inputs and interactive reports are available on the service page.
+ </p>
+
+ <p>
+ The online measurement service is available at: <a href="http://www.mdworkbench.com/measuring.php">http://www.mdworkbench.com/measuring.php</a>
+ </p>
+
+ <p>
+ A complete list of implemented metrics is available at: <a href="http://www.mdworkbench.com/measurement/metrics/definition.htm">
+ http://www.mdworkbench.com/measurement/metrics/definition.htm</a>
+ </p>
+
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;"><a name="keywords"></a>Keywords</h4>
+ <table width="100%">
+ <COLGROUP>
+ <COL width="2%" />
+ <COL width="98%" />
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ <p align="justify">
+ KM3, UML, Measures, HTML, XHTML, SVG, Pie Chart, Bar Chart
+ </p>
+ </td>
+ </tr>
+ </table>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;"><a name="overview"></a>Overview</h4>
+
+ <table width="100%">
+ <COLGROUP>
+ <COL width="2%" />
+ <COL width="98%" />
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ <p align="justify">
+ This use case shows how to compute and generate measures on KM3 meta-models or UML models, and how to display them in different way.
+ This use case is composed of two main parts.
+ </p>
+ <p align="justify">
+ The first step is the measurement process. Metrics are implemented for KM3 meta-model or UML models using metric sets found in the literature [1].
+ Each metric set is implemented as an ATL library. An ATL transformation is implemented for each kind of input terminal model and shows how to use the libraries of
+ metrics. A model of Measure is produced at the end of this step.
+ </p>
+ <p align="justify">
+ The second step is the presentation process. The computed metrics stored in the model of Measure can be displayed in four different representations: Tabular HTML,
+ SVG Bar Chart, SVG Pie Chart or interactive XHTML with CSS.
+ </p>
+ <p align="justify">
+ The figures below present the sample results generated for a KM3 metamodel and for a UML model:
+ </p>
+ <p align="center">
+ <a href="img/tabularHTML_1.PNG"><img src="img/tabularHTML_1Small.PNG" /></a>
+ <br /><br />
+ <b>Figure 1: Example of Tabular HTML presentation on a KM3 metamodel</b>
+ </p>
+ <p align="center">
+ <a href="img/barChart_1.PNG"><img src="img/barChart_1Small.PNG" /></a>
+ <br /><br />
+ <b>Figure 2: Example of SVG Bar Chart presentation on a KM3 metamodel</b>
+ </p>
+ <p align="center">
+ <a href="img/pieChart_1.PNG"><img src="img/pieChart_1Small.PNG" /></a>
+ <br /><br />
+ <b>Figure 3: Example of SVG Pie Chart presentation on a KM3 metamodel</b>
+ </p>
+ <p align="center">
+ <img src="img/XHTML_1.PNG" />
+ <br /><br />
+ <b>Figure 4: Example of interactive XHTML with CSS presentation on a KM3 metamodel</b>
+ </p>
+ <p align="center">
+ <a href="img/tabularHTML_2.PNG"><img src="img/tabularHTML_2Small.PNG" /></a>
+ <br /><br />
+ <b>Figure 5: Example of Tabular HTML presentation on a UML model</b>
+ </p>
+ <p align="center">
+ <a href="img/barChart_2.PNG"><img src="img/barChart_2Small.PNG" /></a>
+ <br /><br />
+ <b>Figure 6: Example of SVG Bar Chart presentation on a UML model</b>
+ </p>
+ <p align="center">
+ <a href="img/pieChart_2.PNG"><img src="img/pieChart_2Small.PNG" /></a>
+ <br /><br />
+ <b>Figure 7: Example of SVG Pie Chart presentation on a UML model</b>
+ </p>
+ <p align="center">
+ <img src="img/XHTML_2.PNG" />
+ <br /><br />
+ <b>Figure 8: Example of interactive XHTML with CSS presentation on a UML model</b>
+ </p>
+ </td>
+ </tr>
+ </table>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;">
+ <a name="references"></a>References
+ </h4>
+
+ <table width="100%">
+ <tr valign="top">
+ <td>
+ [1]
+ </td>
+ <td>
+ Baroni, A.L.: <em>Formal Definition of Object-Oriented Design Metrics</em>. Master Thesis, Vrije University, Brussel, Belgium, 2002.
+ </td>
+ </tr>
+ </table>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;">
+ <a name="relatedUseCases"></a>Related Use Cases
+ </h4>
+ <table>
+ <COLGROUP>
+ <COL width="2%" />
+ <COL width="98%" />
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ <p align="justify">
+ <a href="http://www.eclipse.org/atl/usecases/Measuring_UML_models/">Measuring UML models</a>
+ </p>
+ </td>
+ </tr>
+ </table>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;">
+ <a name="download">Download</a>
+ </h4>
+
+ <table width="100%">
+ <COLGROUP>
+ <COL width="25%">
+ <COL width="75%">
+ </COLGROUP>
+ <tr>
+ <td align="center"><a href="http://www.eclipse.org/atl/atlTransformations/#ModelMeasurement">Complete Scenario</a></td>
+ <td>Scenario <b>Models Measurement</b> available in the ATL transformation zoo (with source files).</td>
+ </tr>
+ <tr>
+ <td align="center"><a href="http://www.mdworkbench.com/measuring.php">Web Service</a></td>
+ <td>
+ Online measurement service
+ </td>
+ </tr>
+ <tr>
+ <td align="center"><a href="http://www.mdworkbench.com/measurement/metrics/definition.htm">Definition</a></td>
+ <td>Complete list of implemented metrics</td>
+ </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>Acknowledgement
+ </h4>
+
+ <table width="100%">
+ <COLGROUP>
+ <COL width="2%">
+ <COL width="98%">
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+
+ </td>
+ </tr>
+ </table>
+-->
+
+ </div>
+
+ <hr class="clearer" />
+
+ </div>
+
+ <div id="rightcolumn">
+ <div class="sideitem">
+ <h6>General Information</h6>
+ <ul>
+ <li style="list-style:none">July 2007</li>
+ <li style="list-style:none">By <a href="http://www.sciences.univ-nantes.fr/lina/atl/contrib/vepa">Éric Vépa</a> (<a href="http://www.sodius.com">SODIUS</a>)</li>
+ <li style="list-style:none"><br />Please, ask your questions on the <a href="news://news.eclipse.org/eclipse.modeling.m2m">M2M newsgroup</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/MonitorToSemaphore/img/CodeSample1.png b/usecases/MonitorToSemaphore/img/CodeSample1.png
new file mode 100644
index 0000000..285306c
--- /dev/null
+++ b/usecases/MonitorToSemaphore/img/CodeSample1.png
Binary files differ
diff --git a/usecases/MonitorToSemaphore/img/CodeSample2.png b/usecases/MonitorToSemaphore/img/CodeSample2.png
new file mode 100644
index 0000000..a05049f
--- /dev/null
+++ b/usecases/MonitorToSemaphore/img/CodeSample2.png
Binary files differ
diff --git a/usecases/MonitorToSemaphore/img/CodeSample3.png b/usecases/MonitorToSemaphore/img/CodeSample3.png
new file mode 100644
index 0000000..29c3a65
--- /dev/null
+++ b/usecases/MonitorToSemaphore/img/CodeSample3.png
Binary files differ
diff --git a/usecases/MonitorToSemaphore/img/CodeSample4.png b/usecases/MonitorToSemaphore/img/CodeSample4.png
new file mode 100644
index 0000000..258d9f8
--- /dev/null
+++ b/usecases/MonitorToSemaphore/img/CodeSample4.png
Binary files differ
diff --git a/usecases/MonitorToSemaphore/img/CodeSample5.png b/usecases/MonitorToSemaphore/img/CodeSample5.png
new file mode 100644
index 0000000..ac41b90
--- /dev/null
+++ b/usecases/MonitorToSemaphore/img/CodeSample5.png
Binary files differ
diff --git a/usecases/MonitorToSemaphore/img/CodeSample6.png b/usecases/MonitorToSemaphore/img/CodeSample6.png
new file mode 100644
index 0000000..e007840
--- /dev/null
+++ b/usecases/MonitorToSemaphore/img/CodeSample6.png
Binary files differ
diff --git a/usecases/MonitorToSemaphore/img/CodeSample7.png b/usecases/MonitorToSemaphore/img/CodeSample7.png
new file mode 100644
index 0000000..2f52c2f
--- /dev/null
+++ b/usecases/MonitorToSemaphore/img/CodeSample7.png
Binary files differ
diff --git a/usecases/MonitorToSemaphore/img/CodeSample8.png b/usecases/MonitorToSemaphore/img/CodeSample8.png
new file mode 100644
index 0000000..518588a
--- /dev/null
+++ b/usecases/MonitorToSemaphore/img/CodeSample8.png
Binary files differ
diff --git a/usecases/MonitorToSemaphore/img/Sample.png b/usecases/MonitorToSemaphore/img/Sample.png
new file mode 100644
index 0000000..6b69abd
--- /dev/null
+++ b/usecases/MonitorToSemaphore/img/Sample.png
Binary files differ
diff --git a/usecases/MonitorToSemaphore/img/UseCaseOverview.png b/usecases/MonitorToSemaphore/img/UseCaseOverview.png
new file mode 100644
index 0000000..55d3ba6
--- /dev/null
+++ b/usecases/MonitorToSemaphore/img/UseCaseOverview.png
Binary files differ
diff --git a/usecases/MonitorToSemaphore/index.php b/usecases/MonitorToSemaphore/index.php
new file mode 100644
index 0000000..a8574c0
--- /dev/null
+++ b/usecases/MonitorToSemaphore/index.php
@@ -0,0 +1,332 @@
+<?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.
+ $shortTitle = "From Hoare's Monitors to Dijkstra's Semaphores";
+ $pageTitle = "ATL Use Case - " . $shortTitle;
+ $pageKeywords = "";
+ $pageAuthor = "Freddy Allilaire";
+
+ # End: page-specific settings
+ #
+
+ # Paste your HTML content between the EOHTML markers!
+ $html = <<<EOHTML
+
+ <!-- Main part -->
+ <div id="midcolumn">
+ <h1>$pageTitle</h1>
+
+ <img align="right" src="../../resources/atlLogoSmall.png" valign="top" style="padding-left: 10px;" alt="ATL Logo" />
+ <blockquote>
+ <ul>
+ <li><a href="#keywords"><b>Keywords</b></a></li>
+ <li><a href="#overview"><b>Overview</b></a></li>
+ <li><a href="#relatedUseCases"><b>Related Use Cases</b></a></li>
+ <li><a href="#download"><b>Download</b></a></li>
+ <li><a href="#acknowledgement"><b>Acknowledgement</b></a></li>
+ </ul>
+ </blockquote>
+
+ <hr class="clearer" />
+
+ <div id="container>
+ <p align="justify">
+ This is a classic in synchronization. We propose an automatic translation from Hoare's monitors into Dijkstra's semaphores.
+ </p>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;"><a name="keywords"></a>Keywords</h4>
+ <table width="100%">
+ <COLGROUP>
+ <COL width="2%" />
+ <COL width="98%" />
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ <p align="justify">
+ Hoare's Monitor
+ Dijkstra's Semaphore,
+ <a href="http://en.wikipedia.org/wiki/Programming">Programming</a>
+ </p>
+ </td>
+ </tr>
+ </table>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;"><a name="overview"></a>Overview</h4>
+
+ <table width="100%">
+ <COLGROUP>
+ <COL width="2%" />
+ <COL width="98%" />
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ <p align="justify">
+ This is a classic in synchronization. We propose an automatic translation from Hoare's monitors as defined in <a href="#ref1">[1]</a> into Dijkstra's semaphores as initially introduced in <a href="#ref2">[2]</a>.
+ The ATL transformation code follows the rules given in <a href="#ref1">[1]</a>. A complete reprint of this paper is available at:
+ <a href="http://www.acm.org/classics/feb96/">http://www.acm.org/classics/feb96/</a>.
+ </p>
+ <p align="justify">
+ The overall approach is summarized in the following figure:
+ </p>
+ <p align="center">
+ <img src="img/UseCaseOverview.png" />
+ <br /><br />
+ <b>"$shortTitle" Use Case's Overview</b>
+ </p>
+ <p align="justify">
+ As a classical example, we can take the readers and writers problem:
+ </p>
+ <p align="justify">
+ <img src="img/CodeSample1.png" />
+ </p>
+ <p align="justify">
+ Another example is the bounded buffer presented at: <a href="http://www.acm.org/classics/feb96/bounded_buffer.html">http://www.acm.org/classics/feb96/bounded_buffer.html</a>.
+ </p>
+ <p align="justify">
+ In <a href="#ref1">[1]</a> a set of rules for translating from monitors to semaphores is given to prove that monitors can be implemented by semaphores. We reproduce below these rules that
+ may be found at: <a href="http://www.acm.org/classics/feb96/interpretation.html">http://www.acm.org/classics/feb96/interpretation.html</a>.
+ </p>
+ <p align="justify">
+ "Obviously, we shall require for each monitor a Boolean semaphore "mutex" to ensure that the bodies of the local procedures exclude each other. The semaphore is initialized
+ to 1; a P(mutex) must be executed on entry to each local procedure, and a V(mutex) must usually be executed on exit from it.
+ </p>
+ <p align="justify">
+ When a process signals a condition on which another process is waiting, the signaling process must wait until the resumed process permits it to proceed. We therefore
+ introduce for each monitor a second semaphore "urgent" (initialized to 0), on which signaling processes suspend themselves by the operation P(urgent). Before releasing
+ exclusion, each process must test whether any other process is waiting on urgent, and if so, must release it instead by a V(urgent) instruction We therefore need to count
+ the number of processes waiting on urgent, in an integer "urgentcount" (initially zero). Thus each exit from a procedure of a monitor should be coded:
+ </p>
+ <p align="justify">
+ <img src="img/CodeSample2.png" />
+ </p>
+ <p align="justify">
+ Finally, for each condition local to the monitor, we introduce a semaphore "condsem" (initialized to 0), on which a process desiring to wait suspends itself by a P(condsem)
+ operation. Since a process signaling this condition needs to know whether anybody is waiting, we also need a count of the number of waiting processes held in an integer
+ variable "condcount" (initially 0). The operation "cond.wait" may now be implemented as follows (recall that a waiting program must release exclusion before suspending
+ itself):
+ </p>
+ <p align="justify">
+ <img src="img/CodeSample3.png" />
+ </p>
+ <p align="justify">
+ The signal operation may be coded:
+ </p>
+ <p align="justify">
+ <img src="img/CodeSample4.png" />
+ </p>
+ <p align="justify">
+ In this implementation, possession of the monitor is regarded as a privilege which is explicitly passed from one process to another. Only when no one further wants the
+ privilege is mutex finally released.
+ </p>
+ <p align="justify">
+ This solution is not intended to correspond to recommended "style" in the use of semaphores. The concept of a condition-variable is intended as a substitute for semaphores,
+ and has its own style of usage, in the same way that while loops or coroutines are intended as a substitute for jumps.
+ </p>
+ <p align="justify">
+ In many cases, the generality of this solution is unnecessary, and a significant improvement in efficiency is possible.
+ </p>
+ <p align="justify">
+ <ol>
+ <li>When a procedure body in a monitor contains no wait or signal, exit from the body can be coded by a simple V(mutex) since urgentcount cannot have changed during the
+ execution of the body.</li>
+
+ <li>
+ If a cond.signal is the last operation of a procedure body, it can be combined with monitor exit as follows:
+ <p align="justify">
+ <img src="img/CodeSample5.png" />
+ </p>
+ </li>
+
+ <li>If there is no other wait or signal in the procedure body, the second line shown above can also be omitted.</li>
+
+ <li>
+ If every signal occurs as the last operation of its procedure body, the variables urgentcount and urgent can be omitted, together with all operations upon them.
+ This is such a simplification that O-J. Dahl suggests that signals should always be the last operation of a monitor procedure; in fact, this restriction is a very
+ natural one, which has been unwittingly observed in all examples of this paper.
+ </li>
+ </ol>
+ </p>
+ <p align="justify">
+ Significant improvements in efficiency may also be obtained by avoiding the use of semaphores, and by implementing conditions directly in hardware, or at the lowest and
+ most uninterruptible level of software (e.g. supervisor mode). In this case, the following optimizations are possible.
+ </p>
+ <p align="justify">
+ <ol>
+ <li>
+ urgentcount and condcount can be abolished, since the fact that someone is waiting can be established by examining the representation of the semaphore, which cannot
+ change surreptitiously within non interruptible mode.
+ </li>
+ <li>
+ Many monitors are very short and contain no calls to other monitors. Such monitors can be executed wholly in non interruptible mode, using, as it were, the common
+ exclusion mechanism provided by hardware. This will often involve less time in non interruptible mode than the establishment of separate exclusion for each monitor."
+ </li>
+ </ol>
+ </p>
+ <p align="justify">
+ In summary we take into consideration the following rules from above:
+ <ol>
+ <li>For each monitor M declare one semaphore (M_mutex), one counter (M_urgentcount) and one semaphore (M_urgent).</li>
+ <li>For each condition C inside a semaphore declare one counter (C_count) and one semaphore (C_sem).</li>
+ <li>For each method entry, perform the following code: M_mutex.P().</li>
+ <li>
+ For each method exit, perform the following code:
+ <p align="justify">
+ <img src="img/CodeSample6.png" />
+ </p>
+ </li>
+ <li>For each condition C.wait perform the following code:
+ <p align="justify">
+ <img src="img/CodeSample7.png" />
+ </p>
+ </li>
+ <li>
+ For each condition C.signal perform the following code:
+ <p align="justify">
+ <img src="img/CodeSample8.png" />
+ </p>
+ </li>
+ </ul>
+ </p>
+ <p align="justify">
+ <h5 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;">Why is this ATL transformation interesting?</h5>
+ For several reasons:
+ <ol class="midlist">
+ <li>
+ It show how a DSL (monitors) may be translated quite easily in practice into another DSL (Semaphores). Note that both DSLs are extensions of the same
+ pseudo-language.
+ </li>
+ <li>
+ It shows how model transformation may be useful in establishing the semantics of one DSL (monitors) in terms of the semantics of another DSL (Semaphores).
+ </li>
+ <li>
+ It give hints on how complex synchronization schemes may be transformed in basic schemes for example in basic java Threads.
+ </li>
+ </ol>
+ </p>
+ <p align="justify">
+ To conclude, we provide below a set of screenshots showing the different input/output files provided/created with this use case:
+ </p>
+ <p align="center">
+ <img src="img/Sample.png" />
+ <br /><br />
+ <b>Screenshots of the input/outputs of the use case</b>
+ </p>
+ </td>
+ </tr>
+ </table>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;">
+ <a name="relatedUseCases"></a>Related Use Cases
+ </h4>
+ <table>
+ <COLGROUP>
+ <COL width="2%" />
+ <COL width="98%" />
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ <p align="justify">
+ None at the current time.
+ </p>
+ </td>
+ </tr>
+ </table>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;">
+ <a name="references"></a>References
+ </h4>
+
+ <table width="100%">
+ <tr valign="top">
+ <td>
+ <a name="ref1">[1]</a>
+ </td>
+ <td>
+ Hoare, C.A.R Monitors: An Operating System Structuring Concept Communications of the ACM, Vol. 17, No. 10. October 1974, pp. 549-557
+ </td>
+ </tr>
+ <tr valign="top">
+ <td>
+ <a name="ref2">[2]</a>
+ </td>
+ <td>
+ Dijkstra, E. W. Cooperating Sequential Processes. In programming Languages (Ed. F. Genuys), Academic Press, New York.
+ </td>
+ </tr>
+ </table>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;">
+ <a name="download">Download</a>
+ </h4>
+
+ <table width="100%">
+ <COLGROUP>
+ <COL width="25%">
+ <COL width="75%">
+ </COLGROUP>
+ <tr>
+ <td align="center"><a href="http://www.eclipse.org/atl/atlTransformations/#Monitor2Semaphore"><h3>Complete scenario</h3></a></td>
+ <td>Scenario available in the ATL transformation zoo (with source files).</td>
+ </tr>
+ <tr>
+ <td align="center"><a href="http://www.eclipse.org/gmt/am3/zoos/atlanticZoo/#Program"><h3>Program Metamodel</h3></a></td>
+ <td>Program metamodel is expressed in the <a href="http://wiki.eclipse.org/index.php/KM3">KM3</a> textual format.</td>
+ </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>Acknowledgement
+ </h4>
+
+ <table width="100%">
+ <COLGROUP>
+ <COL width="2%">
+ <COL width="98%">
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ The present work is being supported by the <a href="http://www.usine-logicielle.org">Usine Logicielle project of the System@tic Paris Region Cluster</a>.
+ This work has also been supported by the Atlantic federation of labs.
+ </td>
+ </tr>
+ </table>
+
+ </div>
+ </div>
+
+ <div id="rightcolumn">
+ <div class="sideitem">
+ <h6>General Information</h6>
+ <ul>
+ <li style="list-style:none">March 2007</li>
+ <li style="list-style:none">
+ By <a href="http://www.sciences.univ-nantes.fr/lina/atl/contrib/allilaire">Freddy Allilaire</a> (INRIA)
+ </li>
+ <li style="list-style:none"><br />Please, ask your questions on the <a href="news://news.eclipse.org/eclipse.modeling.m2m">M2M newsgroup</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/ODMImplementation/img/MuseumOWL.PNG b/usecases/ODMImplementation/img/MuseumOWL.PNG
new file mode 100644
index 0000000..d196ccb
--- /dev/null
+++ b/usecases/ODMImplementation/img/MuseumOWL.PNG
Binary files differ
diff --git a/usecases/ODMImplementation/img/MuseumUML.png b/usecases/ODMImplementation/img/MuseumUML.png
new file mode 100644
index 0000000..16d7371
--- /dev/null
+++ b/usecases/ODMImplementation/img/MuseumUML.png
Binary files differ
diff --git a/usecases/ODMImplementation/img/OWL.png b/usecases/ODMImplementation/img/OWL.png
new file mode 100644
index 0000000..7cc388b
--- /dev/null
+++ b/usecases/ODMImplementation/img/OWL.png
Binary files differ
diff --git a/usecases/ODMImplementation/img/UML2OWL.png b/usecases/ODMImplementation/img/UML2OWL.png
new file mode 100644
index 0000000..fcd37e6
--- /dev/null
+++ b/usecases/ODMImplementation/img/UML2OWL.png
Binary files differ
diff --git a/usecases/ODMImplementation/img/UMLOWLBridge.png b/usecases/ODMImplementation/img/UMLOWLBridge.png
new file mode 100644
index 0000000..4ba4498
--- /dev/null
+++ b/usecases/ODMImplementation/img/UMLOWLBridge.png
Binary files differ
diff --git a/usecases/ODMImplementation/index.php b/usecases/ODMImplementation/index.php
new file mode 100644
index 0000000..8ef9cc5
--- /dev/null
+++ b/usecases/ODMImplementation/index.php
@@ -0,0 +1,247 @@
+<?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.
+ $shortTitle = "ODM Implementation (Bridging UML and OWL)";
+ $pageTitle = "ATL Use Case - " . $shortTitle;
+ $pageKeywords = "";
+ $pageAuthor = "Freddy Allilaire";
+
+ # End: page-specific settings
+ #
+
+ # Paste your HTML content between the EOHTML markers!
+ $html = <<<EOHTML
+
+ <!-- Main part -->
+ <div id="midcolumn">
+ <h1>$pageTitle</h1>
+
+ <img align="right" src="../../resources/atlLogoSmall.png" valign="top" style="padding-left: 10px;" alt="ATL Logo" />
+ <blockquote>
+ <ul>
+ <li><a href="#keywords"><b>Keywords</b></a></li>
+ <li><a href="#overview"><b>Overview</b></a></li>
+ <li><a href="#relatedUseCases"><b>Related Use Cases</b></a></li>
+ <li><a href="#download"><b>Download</b></a></li>
+ <li><a href="#acknowledgement"><b>Acknowledgement</b></a></li>
+ </ul>
+ </blockquote>
+
+ <hr class="clearer" />
+
+ <div id="container>
+ <p align="justify">
+ This work presents an implementation of the OMG ODM (Ontology Definition Metamodel) proposal using the ATL language. This work is made by the SIDo Group from the
+ <a href="http://www.univ-lr.fr/labo/l3i/site_statique/Index.html">L3I</a> lab in La Rochelle.
+ </p>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;"><a name="keywords"></a>Keywords</h4>
+ <table width="100%">
+ <COLGROUP>
+ <COL width="2%" />
+ <COL width="98%" />
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ <p align="justify">
+ Ontology,
+ <a href="http://www.uml.org">UML 2.0</a>,
+ <a href="http://www.w3.org/2004/OWL">OWL</a>,
+ <a href="http://www.omg.org/ontology">ODM</a>,
+ <a href="http://protege.stanford.edu/">Protégé</a>,
+ <a href="http://www.eclipse.org/modeling/mdt/?project=eodm">EODM</a>
+ </p>
+ </td>
+ </tr>
+ </table>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;"><a name="overview"></a>Overview</h4>
+
+ <table width="100%">
+ <COLGROUP>
+ <COL width="2%" />
+ <COL width="98%" />
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ <p align="justify">
+ This use case presents an implemented solution to the OMG Ontology Definition Metamodel (ODM) specification.
+ ODM offers a set of metamodels and mappings for bridging the metamodeling world and the ontologies. The present
+ solution supports the UML 2.0 metamodel and the OWL metamodel as defined in ODM.
+ </p>
+ <p align="justify">
+ The ODM is a recently adopted standard from the Object Management Group that supports ontology development and
+ conceptual modeling in several standard representation languages. It provides a coherent framework for ontology
+ creation based on MOF (Meta Object Facility) and UML (Unified Modeling Language). In this way it plays a central
+ role for bridging Model Driven Architecture based standards and Semantic Web technologies.
+ </p>
+ <p align="center">
+ <img src="img/UMLOWLBridge.png" />
+ <br /><br />
+ <b>ODM Overview</b>
+ </p>
+ <p align="justify">
+ <b>ODM</b> defines five metamodels (RDFS, OWL, Topic Maps, Common Logic and Description Logic), two UML Profiles
+ (RDFS/OWL Profile, Topic Maps Profile) and a set of QVT mappings from UML to OWL, Topic Maps to OWL and
+ RDFS/OWL to Common Logic. At this current time, we have implemented two of these metamodels, RDFS and OWL in
+ KM3 and the UML Profile for RDFS/OWL. We have also implemented the mapping between UML and OWL by using ATL.
+ </p>
+ <p align="justify">
+ <b>UML</b> is the most used and known language to model application structure, behaviour and architecture but also
+ business process and data structure. UML is an OMG specification currently in version 2.0. The UML metamodel used
+ in this case study is the one available under the UML eclipse project (eclipse.org/uml2). By using this metamodel
+ we insure that models used by our transformation can be created by different UML tools supporting current UML 2.0
+ specification.
+ </p>
+ <p align="justify">
+ <b>OWL</b> (Web Ontology language) is the most expressive language for representing and sharing ontologies over the Web.
+ OWL is designed for use by applications that need to process the content of information instead of just presenting
+ information. It facilitates greater machine interoperability of Web content than other description languages like
+ XML, RDF and RDF-S by providing additional vocabulary along with a formal semantics.
+ </p>
+ <p align="justify">
+ The OWL metamodel is implemented in by extending the RDFS metamodel. The figure below shows an excerpt of the class
+ hierarchy present in OWL. An OWL Class is a kind of RDFS Class, like OWL Property are kind of RDF
+ Property. OWL offers a richer semantic to express ontologies. With it we can define cardinalities on properties, defined classes with set operators like union, intersection, complement, etc.
+ The notion of Individual in OWL is used to represent resources, i.e. class instances. Each element is identified by a unique URI identifier.
+ <p align="center">
+ <img src="img/OWL.png" />
+ <br />
+ <br />
+ <b>OWL Metamodel: hierarchy concept excerpt</b>
+ </p>
+ </p>
+ <p align="justify">
+ The ATL transformation <b>UML2OWL</b> has been implemented according to the ODM specification, i.e. corresponding QVT
+ mapping. This transformation made possible the conversion of an arbitrary UML model into OWL ontology. The
+ complete scenario of this transformation is given in figure below.
+ </p>
+ <p align="center">
+ <a href="img/UML2OWL.png"><img src="img/UML2OWL.png" width="650" /></a>
+ <br />
+ <br />
+ <b>UML2OWL complete transformation scenario</b>
+ </p>
+ <p align="justify">
+ This scenario is composed of 2 ATL transformations: the core transformation UML2OWL takes has input a UML
+ model and produces an ontology conforms to the OWL metamodel. The second transformation is an XML extractor that
+ produces an XML document conforms to the OWL/XML syntax, as defined by the W3C specification. </p>
+ <p align="justify">The core transformation includes two distinct parts. The first part is dedicated to the mapping from UML model
+ to ontology, i.e. UML classes are mapped into OWL classes, attributes into datatype property, associations into object property, etc.
+ The second part of the transformation deals with instances. For simplicity and demonstration reason we choose to define instances in the same class diagram as the UML model. Those instances are converted into OWL individuals (OWL term for instances).
+ This method offers the possibility to manage UML instances and populate the ontology with corresponding knowledge. An improved method to deal with instances should be provide soon.</p>
+ <p>A UML model representing a museum is given below and serve as a running example for this use case. </p>
+ <p align="center">
+ <a href="img/MuseumUML.png"><img src="img/MuseumUML.png" width="650" /></a>
+ <br />
+ <br />
+ <b>Museum Model </b>
+ </p>
+ <p>The UML2OWL transformation can produce an OWL model in ecore format or an OWL document conform to the OWL/XML presentation syntax. To obtain this XML file, we have implemented an OWL/XML extractor that transforms a model conforms to the OWL metamodel into an owl document.This will let you use obtained OWL files under ontology tools like Protégé. An excerpt of the Museum ontology produced by the UML2OWL transformation from the Museum UML Model is given below. In this excerpt you should notice the presence of a class Painter and one of its Individual representing Picasso. </p>
+ <p align="center">
+ <a href="img/MuseumOWL.PNG"><img src="img/MuseumOWL.PNG" width="650" /></a>
+ <br />
+ <br />
+ <b>Museum ontology excerpt in OWL/XML format </b>
+ </p>
+ <p align="justify">
+ This use case demonstrates the feasibility to implement the ODM specification, especially the UML to OWL mapping by
+ using AMMA tools. This ATL scenario provides a solution for bridging modeling tools based on UML or MOF (e.g. MDA
+ Tools) and tools for the Semantic Web and ontology development.
+ </p>
+ </td>
+ </tr>
+ </table>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;">
+ <a name="relatedUseCases"></a>Related Use Cases
+ </h4>
+ <table>
+ <COLGROUP>
+ <COL width="2%" />
+ <COL width="98%" />
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ <p align="justify">
+ None at the current time.
+ </p>
+ </td>
+ </tr>
+ </table>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;">
+ <a name="download">Download</a>
+ </h4>
+
+ <table width="100%">
+ <COLGROUP>
+ <COL width="25%">
+ <COL width="75%">
+ </COLGROUP>
+ <tr>
+ <td align="center"><a href="http://www.eclipse.org/atl/atlTransformations/#UML2OWL"><h3>Complete scenario</h3></a></td>
+ <td>Scenario available in the ATL transformation zoo (with source files).</td>
+ </tr>
+ <tr>
+ <td align="center"><a href="http://www.eclipse.org/gmt/am3/zoos/atlanticZoo/#OWL"><h3>OWL Metamodel</h3></a></td>
+ <td>OWL metamodel is expressed in the <a href="http://wiki.eclipse.org/index.php/KM3">KM3</a> textual format.</td>
+ </tr>
+ <tr>
+ <td align="center"><a href="http://www.eclipse.org/uml2"><h3>UML 2.0</h3></a></td>
+ <td>The UML 2.0 Metamodel in Ecore XMI 2.0 format is available with the UML2 plugin.</td>
+ </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>Acknowledgement
+ </h4>
+
+ <table width="100%">
+ <COLGROUP>
+ <COL width="2%">
+ <COL width="98%">
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ This work is granted by the General Council of <a href="http://wwww.charente-maritime.fr/">Charente Maritime</a> (Conseil General de Charente Maritime).
+ </td>
+ </tr>
+ </table>
+
+ </div>
+ </div>
+
+ <div id="rightcolumn">
+ <div class="sideitem">
+ <h6>General Information</h6>
+ <ul>
+ <li style="list-style:none">February 2007</li>
+ <li style="list-style:none">By <a href="mailto:g <dot> hillairet <at> gmail <dot> com">Guillaume Hillairet</a> (L3I)</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/PRR2IRL/img/Code1.png b/usecases/PRR2IRL/img/Code1.png
new file mode 100644
index 0000000..618a214
--- /dev/null
+++ b/usecases/PRR2IRL/img/Code1.png
Binary files differ
diff --git a/usecases/PRR2IRL/img/Code2.png b/usecases/PRR2IRL/img/Code2.png
new file mode 100644
index 0000000..ecab369
--- /dev/null
+++ b/usecases/PRR2IRL/img/Code2.png
Binary files differ
diff --git a/usecases/PRR2IRL/img/Code3.png b/usecases/PRR2IRL/img/Code3.png
new file mode 100644
index 0000000..8698728
--- /dev/null
+++ b/usecases/PRR2IRL/img/Code3.png
Binary files differ
diff --git a/usecases/PRR2IRL/img/Code4.png b/usecases/PRR2IRL/img/Code4.png
new file mode 100644
index 0000000..58d2ed1
--- /dev/null
+++ b/usecases/PRR2IRL/img/Code4.png
Binary files differ
diff --git a/usecases/PRR2IRL/img/Code5.png b/usecases/PRR2IRL/img/Code5.png
new file mode 100644
index 0000000..8f7a384
--- /dev/null
+++ b/usecases/PRR2IRL/img/Code5.png
Binary files differ
diff --git a/usecases/PRR2IRL/img/prr2irl.png b/usecases/PRR2IRL/img/prr2irl.png
new file mode 100644
index 0000000..c31c7bc
--- /dev/null
+++ b/usecases/PRR2IRL/img/prr2irl.png
Binary files differ
diff --git a/usecases/PRR2IRL/index.php b/usecases/PRR2IRL/index.php
new file mode 100644
index 0000000..feb59a7
--- /dev/null
+++ b/usecases/PRR2IRL/index.php
@@ -0,0 +1,298 @@
+<?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.
+ $shortTitle = "Implementing two business rule languages: PRR and IRL";
+ $pageTitle = "ATL Use Case - " . $shortTitle;
+ $pageKeywords = "";
+ $pageAuthor = "Freddy Allilaire";
+
+ # End: page-specific settings
+ #
+
+ # Paste your HTML content between the EOHTML markers!
+ $html = <<<EOHTML
+
+ <!-- Main part -->
+ <div id="midcolumn">
+ <h1>$pageTitle</h1>
+
+ <img align="right" src="../../resources/atlLogoSmall.png" valign="top" style="padding-left: 10px;" alt="ATL Logo" />
+ <blockquote>
+ <ul>
+ <li><a href="#keywords"><b>Keywords</b></a></li>
+ <li><a href="#introduction"><b>Introduction</b></a></li>
+ <li><a href="#overview"><b>Overview</b></a></li>
+ <li><a href="#relatedUseCases"><b>Related Use Cases</b></a></li>
+ <li><a href="#download"><b>Download</b></a></li>
+ <li><a href="#acknowledgement"><b>Acknowledgement</b></a></li>
+ </ul>
+ </blockquote>
+
+ <hr class="clearer" />
+
+ <div id="container>
+ <p align="justify">
+ This work presents a case study of implementing two business rule languages: Production Rule Representation (PRR) and ILOG Rule Language (IRL). We show how a pivot language can be
+ translated into a concrete one with the help of model engineering. The outcome of this experiment also provides an interesting example of DSLs coordination. This work has been done
+ in collaboration between the <a href="http://www.sciences.univ-nantes.fr/lina/atl/">ATLAS Group</a> in Nantes and <a href="http://www.ilog.com/">ILOG</a>.
+ </a>
+ <p align="justify">
+ A <font color="red"><b>web service PRR to IRL</b></font> is available here: <a href="http://www.sciences.univ-nantes.fr/lina/atl/atldemo/prronline/">http://www.sciences.univ-nantes.fr/lina/atl/atldemo/prronline/</a>.
+ </p>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;"><a name="keywords"></a>Keywords</h4>
+ <table width="100%">
+ <COLGROUP>
+ <COL width="2%" />
+ <COL width="98%" />
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ <p align="justify">
+ <a href="http://en.wikipedia.org/wiki/Business_rules">Business Rule</a>,
+ <a href="http://www.omg.org/cgi-bin/doc?br/2003-9-3">PRR</a>,
+ IRL
+ </p>
+ </td>
+ </tr>
+ </table>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;"><a name="introduction"></a>Introduction</h4>
+
+ <table width="100%">
+ <COLGROUP>
+ <COL width="2%" />
+ <COL width="98%" />
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ <p align="justify">
+ In this work, we report on the experiment of building flexible Domain Specific Languages (DSLs) framework upon model driven engineering techniques. More specifically, we
+ are building a bridge between Production Rule Representation (PRR) and ILOG Rule Language (IRL) with the ATLAS Model Management Architecture (AMMA).
+ </p>
+ <p align="justify">
+ PRR is an object Management Architecture (OMG) standard designed within the Business Rule Working group, now part of the Business Modeling and Integration domain task
+ force. It addresses the requirement for a common production rule representation, as used in various vendors' rules engines with normative considerations and high level
+ modeling.
+ </p>
+ <p align="justify">
+ IRL is a formal rule language designed by ILOG with several implementations build on the top of very powerful and effective resolution engines.
+ </p>
+ </td>
+ </tr>
+ </table>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;"><a name="overview"></a>Overview</h4>
+
+ <table width="100%">
+ <COLGROUP>
+ <COL width="2%" />
+ <COL width="98%" />
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ <p align="justify">
+ In this use case, AMMA and three of its core DSLs (KM3, ATL, and TCS) will be used. AMMA is built on a model-based vision of DSLs and provides a set of core DSLs that may
+ be used to specify new DSLs.
+ </p>
+ <p align="justify">
+ PRR defines production rules for forward chaining, Rete-based inference and procedural processing. It also defines an interchangeable expression language for rule condition
+ and actions expressions, so that they can be replaced by alternative representations for vendor-specific usage or in other standards. Finally, it defines rulesets as
+ collections of rule for particular class of platform (procedural or inference rule engine).
+ </p>
+ <p align="center">
+ <img src="img/Code1.png" />
+ <br /><br />
+ <b>Simple PRR program</b>
+ </p>
+ <p align="justify">
+ The previous picture shows a simple PRR program. It says that for one shopping cart of a customer, there is at least one item in this shopping cart that is a best seller.
+ The abstract syntax is specified in KM3. The following picture shows an excerpt of the PRR metamodel.
+ </p>
+ <p align="center">
+ <img src="img/Code2.png" />
+ <br /><br />
+ <b>PRR Metamodel</b>
+ </p>
+ <p align="justify">
+ As we can see on this picture showing the core PRR metamodel, it uses an abstract OCL-based syntax for PRR expressions.
+ </p>
+ <p align="justify">
+ Concrete syntax of PRR has been implemented in TCS. A grammar is automatically derived from both the KM3 metamodel and the TCS model to parse PRR programs into PRR models.
+ </p>
+ <p align="justify">
+ The ILOG Rule Lanaguage (IRL) is the core language of the ILOG rule engine. The IRL is an executable rule language and all business rules of different rule languages are
+ translated into this language before parsing by the rule engine.
+ </p>
+ <p align="center">
+ <img src="img/Code3.png" />
+ <br /><br />
+ <b>Simple IRL program</b>
+ </p>
+ <p align="justify">
+ This figure shows the same rule as the previous one in PRR. It has exactly the same meaning but can be executed on the ILOG rule engine.
+ As for PRR, the IRL abstract syntax is defined in KM3. The following figure is an excerpt of the IRL metamodel.
+ </p>
+ <p align="center">
+ <img src="img/Code4.png" />
+ <br /><br />
+ <b>IRL Metamodel</b>
+ </p>
+ <p align="justify">
+ Concrete syntax of IRL has been implemented in TCS. The TCS model is used to extract IRL models to IRL program.
+ </p>
+ <p align="justify">
+ The transformation between PRR and IRL provides an implementation of PRR semantics by translating PRR concepts into their IRL equivalent. The following figure provides
+ an excerpt of this transformation:
+ </p>
+ <p align="center">
+ <img src="img/Code5.png" />
+ <br /><br />
+ <b>ATL Transformation PRR2IRL Excerpt</b>
+ </p>
+ <p align="justify">
+ The first two lines declares source and target models respectively conforming to PRR and IRL. Rule RuleSet transforms PRR RuleSet into IRL RuleSet while the rule Rule
+ transform a PRR Rule into IRL RuleDefinition.
+ </p>
+ <p align="center">
+ <img src="img/prr2irl.png" />
+ <br /><br />
+ <b>"$shortTitle" Use Case's Overview</b>
+ </p>
+ <p align="justify">
+ The sample input PRR program Sample.prr injected into Sample-PRR conforming to PRR metamodel thanks to the generated parser from the PRRÂ’s TCS model. It is then transformed
+ to Sample-IRL model conforming to IRL metamodel via an ATL transformation. The latter is then extracted into a IRL program Sample.irl using the TCS interpretation of the
+ TCS syntax definition of IRL. This full transformation scenario is available in the ATL transformation zoo.
+ </p>
+ <p align="justify">
+ This case study illustrates how AMMA core DSLs can be used to capture different facets of a DSL. KM3 is used to express Domain Definition MetaModels. Concrete syntaxes are
+ defined in TCS. Moreover, transformations from any DSLa to any DSLb can be implemented in ATL. This can, for instance, be used to implement the semantics of DSLa in terms
+ of the semantics of DSLb (e.g. from PRR to IRL). Such a transformation may then be used to translate programs expressed in DSLa into programs expressed in DSLb. Another use
+ of ATL is to implement concrete syntaxes of DSLs.
+ </p>
+ </td>
+ </tr>
+ </table>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;">
+ <a name="relatedUseCases"></a>Related Use Cases
+ </h4>
+ <table>
+ <COLGROUP>
+ <COL width="2%" />
+ <COL width="98%" />
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ <p align="justify">
+ None at the current time.
+ </p>
+ </td>
+ </tr>
+ </table>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;">
+ <a name="references"></a>References
+ </h4>
+
+ <table width="100%">
+ <tr valign="top">
+ <td>
+ PRR RFP
+ </td>
+ <td>
+ <a href="http://www.omg.org/cgi-bin/doc?br/2003-9-3">http://www.omg.org/cgi-bin/doc?br/2003-9-3</a>
+ </td>
+ </tr>
+ <tr valign="top">
+ <td>
+ PRR to IRL Web Service
+ </td>
+ <td>
+ <a href="http://www.sciences.univ-nantes.fr/lina/atl/atldemo/prronline/">http://www.sciences.univ-nantes.fr/lina/atl/atldemo/prronline/</a>
+ </td>
+ </tr>
+ </table>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;">
+ <a name="download">Download</a>
+ </h4>
+
+ <table width="100%">
+ <COLGROUP>
+ <COL width="25%">
+ <COL width="75%">
+ </COLGROUP>
+ <tr>
+ <td align="center"><h3>Complete scenario</h3></td>
+ <td>(This scenario will be available soon)</td>
+ </tr>
+ <tr>
+ <td align="center"><a href="http://www.eclipse.org/gmt/am3/zoos/atlanticZoo/#PRR%20(Production%20Rule%20Representation)"><h3>PRR Metamodel</h3></a></td>
+ <td>PRR metamodel is expressed in the <a href="http://wiki.eclipse.org/index.php/KM3">KM3</a> textual format.</td>
+ </tr>
+ <tr>
+ <td align="center"><a href="http://www.eclipse.org/gmt/am3/zoos/atlanticZoo/#IRL"><h3>IRL Metamodel</h3></a></td>
+ <td>IRL metamodel is expressed in the <a href="http://wiki.eclipse.org/index.php/KM3">KM3</a> textual format.</td>
+ </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>Acknowledgement
+ </h4>
+
+ <table width="100%">
+ <COLGROUP>
+ <COL width="2%">
+ <COL width="98%">
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ The present work is being supported by the FLFS ANRT project (Families of Language for Families of Systems),
+ and the <a href="http://www.usine-logicielle.org">Usine Logicielle project of the System@tic Paris Region Cluster</a>.
+ </td>
+ </tr>
+ </table>
+
+ </div>
+ </div>
+
+ <div id="rightcolumn">
+ <div class="sideitem">
+ <h6>General Information</h6>
+ <ul>
+ <li style="list-style:none">March 2007</li>
+ <li style="list-style:none">
+ By <a href="http://www.sciences.univ-nantes.fr/lina/atl/contrib/allilaire">Freddy Allilaire</a>,
+ <a href="http://www.sciences.univ-nantes.fr/lina/atl/contrib/mikael_barbero">Mikael Barbero</a> (INRIA), and
+ Anas Abouzahra (ILOG)
+ </li>
+ <li style="list-style:none"><br />Please, ask your questions on the <a href="news://news.eclipse.org/eclipse.modeling.m2m">M2M newsgroup</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/QVT2ATLVM/ATL-QVT interoperability.png b/usecases/QVT2ATLVM/ATL-QVT interoperability.png
new file mode 100644
index 0000000..7ce5bd8
--- /dev/null
+++ b/usecases/QVT2ATLVM/ATL-QVT interoperability.png
Binary files differ
diff --git a/usecases/QVT2ATLVM/index.php b/usecases/QVT2ATLVM/index.php
new file mode 100644
index 0000000..8e82776
--- /dev/null
+++ b/usecases/QVT2ATLVM/index.php
@@ -0,0 +1,204 @@
+<?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 = "ATL Use Case - QVT to ATL Virtual Machine Compiler";
+ $pageKeywords = "OMG, QVT, ATL, Virtual Machine, VM, Compiler";
+ $pageAuthor = "Frédéric Jouault";
+
+ # End: page-specific settings
+ #
+
+ # Paste your HTML content between the EOHTML markers!
+ $html = <<<EOHTML
+
+ <!-- Main part -->
+ <div id="midcolumn">
+ <h1>$pageTitle</h1>
+
+ <img align="right" src="../../resources/atlLogoSmall.png" valign="top" style="padding-left: 10px;" alt="ATL Logo" />
+ <blockquote>
+ <ul>
+ <li><a href="#keywords"><b>Keywords</b></a></li>
+ <li><a href="#overview"><b>Overview</b></a></li>
+ <li><a href="#relatedUseCases"><b>Related Use Cases</b></a></li>
+ <li><a href="#references"><b>References</b></a></li>
+ <li><a href="#download"><b>Download</b></a></li>
+ <li><a href="#acknowledgement"><b>Acknowledgement</b></a></li>
+ </ul>
+ </blockquote>
+
+ <hr class="clearer" />
+
+ <div>
+ <p align="justify">
+ This work provides a QVT compiler that targets the ATL Virtual Machine (ATL VM), and thus provides executability of QVT programs on top of the ATL VM.
+ The code generator is written in the ACG (<span style="font-variant: small-caps;">Atl</span> Code Generation) Domain-Specific Language (DSL).
+ It takes as input a QVT model (typically in XMI format) that may have been created by a QVT front-end (i.e., a parser and type checker) like <a href="http://www.eclipse.org/m2m/">Eclipse/modeling/m2m/</a>Procedural QVT, or <a href="http://smartqvt.elibel.tm.fr/">SmartQVT</a>.
+ The output of the code generator is a ".asm" file similar to the ones generated by the ATL compiler, or the ACG compiler (both also written in ACG).
+ </p>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;"><a name="keywords"></a>Keywords</h4>
+ <table width="100%">
+ <COLGROUP>
+ <COL width="2%" />
+ <COL width="98%" />
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ <p align="justify">
+ <a href="http://www.omg.org/">OMG</a>,
+ <a href="http://www.omg.org/technology/documents/modeling_spec_catalog.htm#MOF_QVT">QVT</a>,
+ <a href="http://en.wikipedia.org/wiki/Virtual_machine">Virtual Machine, VM</a>,
+ <a href="http://en.wikipedia.org/wiki/Compiler">Compiler</a>,
+ <a href="http://en.wikipedia.org/wiki/Code_generator">Code Generator</a>.
+ </p>
+ </td>
+ </tr>
+ </table>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;"><a name="overview"></a>Overview</h4>
+
+ <table width="100%">
+ <COLGROUP>
+ <COL width="2%" />
+ <COL width="98%" />
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ <p align="justify">
+ This work provides an implementation of one of the QVT-ATL interoperability bridges described in <a href="#[1]">[1]</a>: a QVT to ATL Virtual Machine compiler.
+ This corresponds to the <em>OM to VM</em> arrow on the following figure, taken from <a href="#[1]">[1]</a>.
+ </p>
+ <p align="center">
+ <img src="ATL-QVT interoperability.png" />
+ <br /><br />
+ <b>ATL-QVT interoperability through language transformation</b>
+ </p>
+ <p align="justify">
+ This use case relies on a QVT front-end (i.e., a parser and type checker) like <a href="http://www.eclipse.org/m2m/">Eclipse/modeling/m2m/</a>Procedural QVT, or <a href="http://smartqvt.elibel.tm.fr/">SmartQVT</a>.
+ This front-end generates a QVT model (typically in XMI format) from a QVT program.
+ Then, a code generator written in the ACG (<span style="font-variant: small-caps;">Atl</span> Code Generation) DSL transforms this model into ATL bytecode (i.e., a ".asm" file) that can run on the ATL VM.
+ The current version of this code generator is able to compile the Book2Publication QVT example, and has been tested using the SmartQVT front-end.
+ </p>
+ <p align="justify">
+ ACG is a domain-specific model transformation language.
+ Its domain is ATL VM bytecode generation (i.e., a fixed target metamodel).
+ </p>
+ </td>
+ </tr>
+ </table>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;">
+ <a name="relatedUseCases"></a>Related Use Cases
+ </h4>
+ <table>
+ <COLGROUP>
+ <COL width="2%" />
+ <COL width="98%" />
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ <p align="justify">
+ None at the current time.
+ </p>
+ </td>
+ </tr>
+ </table>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;">
+ <a name="references"></a>References
+ </h4>
+
+ <table width="100%">
+ <tr valign="top">
+ <td>
+ <a name="[1]" href="http://www.sciences.univ-nantes.fr/lina/atl/bibliography/SAC06a">
+ [1]
+ </a>
+ </td>
+ <td>
+ Jouault, F, and Kurtev, I:
+ <em>On the Architectural Alignment of ATL and QVT</em>.
+ In: Proceedings of the 2006 ACM Symposium on Applied Computing (SAC 06). ACM Press, Dijon, France, chapter Model transformation (MT 2006), pages 1188–1195. 2006.
+ </td>
+ </tr>
+ </table>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;">
+ <a name="download">Download</a>
+ </h4>
+
+ <table width="100%">
+ <COLGROUP>
+ <COL width="25%">
+ <COL width="75%">
+ </COLGROUP>
+ <tr>
+ <td align="center"><a href="http://www.eclipse.org/atl/atlTransformations/#QVT2ATLVM"><h3>Complete scenario</h3></a></td>
+ <td>Scenario QVT to ATL VM available in the ATL transformation zoo (with source files).</td>
+ </tr>
+ <tr>
+ <td align="center"><a href="http://www.eclipse.org/gmt/am3/zoos/atlanticZoo/#QVT"><h3>QVT metamodel</h3></a></td>
+ <td>Full QVT metamodel specified in KM3.</td>
+ </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>Acknowledgement
+ </h4>
+
+ <table width="100%">
+ <COLGROUP>
+ <COL width="2%">
+ <COL width="98%">
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ The present work is being supported by the <a href="http://www.modelplex-ist.org/">ModelPlex european project</a>,
+ the FLFS ANRT project (Families of Language for Families of Systems),
+ the <a href="http://openembedd.inria.fr/home_html-en?set_language=en&cl=en">OpenEmbeDD project</a>,
+ and the <a href="http://www.usine-logicielle.org">Usine Logicielle project of the System@tic Paris Region Cluster</a>.
+ </td>
+ </tr>
+ </table>
+
+ </div>
+ </div>
+
+ <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/jouault">Frédéric Jouault</a> (INRIA)
+ </li>
+ <li style="list-style:none"><br />Please, ask your questions on the <a href="news://news.eclipse.org/eclipse.modeling.m2m">M2M newsgroup</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/RSM2Topcased/img/Topcased.png b/usecases/RSM2Topcased/img/Topcased.png
new file mode 100644
index 0000000..61831ba
--- /dev/null
+++ b/usecases/RSM2Topcased/img/Topcased.png
Binary files differ
diff --git a/usecases/RSM2Topcased/img/TransformationProcess.png b/usecases/RSM2Topcased/img/TransformationProcess.png
new file mode 100644
index 0000000..9b82cde
--- /dev/null
+++ b/usecases/RSM2Topcased/img/TransformationProcess.png
Binary files differ
diff --git a/usecases/RSM2Topcased/img/UML2Import.png b/usecases/RSM2Topcased/img/UML2Import.png
new file mode 100644
index 0000000..bfa153a
--- /dev/null
+++ b/usecases/RSM2Topcased/img/UML2Import.png
Binary files differ
diff --git a/usecases/RSM2Topcased/img/rsmClassDiagram.png b/usecases/RSM2Topcased/img/rsmClassDiagram.png
new file mode 100644
index 0000000..48704a0
--- /dev/null
+++ b/usecases/RSM2Topcased/img/rsmClassDiagram.png
Binary files differ
diff --git a/usecases/RSM2Topcased/img/rsmSequenceDiagram.png b/usecases/RSM2Topcased/img/rsmSequenceDiagram.png
new file mode 100644
index 0000000..3fbdc8b
--- /dev/null
+++ b/usecases/RSM2Topcased/img/rsmSequenceDiagram.png
Binary files differ
diff --git a/usecases/RSM2Topcased/img/rsmUseCaseDiagram.png b/usecases/RSM2Topcased/img/rsmUseCaseDiagram.png
new file mode 100644
index 0000000..7fc71f9
--- /dev/null
+++ b/usecases/RSM2Topcased/img/rsmUseCaseDiagram.png
Binary files differ
diff --git a/usecases/RSM2Topcased/img/topcasedClassDiagram.png b/usecases/RSM2Topcased/img/topcasedClassDiagram.png
new file mode 100644
index 0000000..8a8961c
--- /dev/null
+++ b/usecases/RSM2Topcased/img/topcasedClassDiagram.png
Binary files differ
diff --git a/usecases/RSM2Topcased/img/topcasedSequenceDiagram.png b/usecases/RSM2Topcased/img/topcasedSequenceDiagram.png
new file mode 100644
index 0000000..ef76484
--- /dev/null
+++ b/usecases/RSM2Topcased/img/topcasedSequenceDiagram.png
Binary files differ
diff --git a/usecases/RSM2Topcased/img/topcasedUseCaseDiagram.png b/usecases/RSM2Topcased/img/topcasedUseCaseDiagram.png
new file mode 100644
index 0000000..01d6546
--- /dev/null
+++ b/usecases/RSM2Topcased/img/topcasedUseCaseDiagram.png
Binary files differ
diff --git a/usecases/RSM2Topcased/index.php b/usecases/RSM2Topcased/index.php
new file mode 100644
index 0000000..87d1fdb
--- /dev/null
+++ b/usecases/RSM2Topcased/index.php
@@ -0,0 +1,261 @@
+<?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.
+ $shortTitle = "RSM to Topcased UML2 Editor";
+ $pageTitle = "ATL Use Case - " . $shortTitle;
+ $pageKeywords = "";
+ $pageAuthor = "Freddy Allilaire";
+
+ # End: page-specific settings
+ #
+
+ # Paste your HTML content between the EOHTML markers!
+ $html = <<<EOHTML
+
+ <!-- Main part -->
+ <div id="midcolumn">
+ <h1>$pageTitle</h1>
+
+ <img align="right" src="../../resources/atlLogoSmall.png" valign="top" style="padding-left: 10px;" alt="ATL Logo" />
+ <blockquote>
+ <ul>
+ <li><a href="#keywords"><b>Keywords</b></a></li>
+ <li><a href="#overview"><b>Overview</b></a></li>
+ <li><a href="#relatedUseCases"><b>Related Use Cases</b></a></li>
+ <li><a href="#download"><b>Download</b></a></li>
+ <li><a href="#acknowledgement"><b>Acknowledgement</b></a></li>
+ </ul>
+ </blockquote>
+
+ <hr class="clearer" />
+
+ <div id="container>
+ <p align="justify">
+
+ </p>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;"><a name="keywords"></a>Keywords</h4>
+ <table width="100%">
+ <COLGROUP>
+ <COL width="2%" />
+ <COL width="98%" />
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ <p align="justify">
+ RSM, Topcased, Import, UML2, Class Diagram, Use Case Diagram, Sequence Diagram
+ </p>
+ </td>
+ </tr>
+ </table>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;"><a name="overview"></a>Overview</h4>
+
+ <table width="100%">
+ <COLGROUP>
+ <COL width="2%" />
+ <COL width="98%" />
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ <p align="justify">
+ <a href="http://www.topcased.org/">TOPCASED</a> currently uses the ATL model transformation toolkit. Model transformations have been mainly used in order to
+ access models defined using other editors than TOPCASED one's.
+ </p>
+ <p align="justify">
+ This use case presents an operational application of ATL to bridge RSM and TOPCASED. It was implemented by <a href="http://www.c-s.fr/">C-S</a> in the context of
+ the TOPCASED project.
+ </p>
+ <p align="justify">
+ <a href="http://www.topcased.org/">TOPCASED</a> is an open-source workshop based on an Eclipse platform. Several editors are available:
+ SAM, AADL, UML2, ECORE, and SYSML.
+ It integrate several transformation services, in particular RSM to TOPCASED. These services are all based on ATL language and tool. Other services around models are
+ available like OCL editor and checker, comparison, merging, etc.
+ </p>
+ <p align="justify">
+ In the TOPCASED UML2 Editor several diagrams are available:
+ <ul>
+ <li>Class diagram</li>
+ <li>Usecase diagram</li>
+ <li>Sequence diagram</li>
+ </ul>
+ </p>
+ <p align="center">
+ <img src="img/Topcased.png" />
+ <br /><br />
+ <b>Topcased UML2 Editor</b>
+ </p>
+ <p align="justify">
+ To display of diagram, the TOPCASED editor needs two kinds of files:
+ <ul>
+ <li>The model part (file with the UML2 extension)</li>
+ <li>The graphical information (file with the UML2DI extension)</li>
+ </ul>
+ </p>
+ <p align="justify">
+ In contrast with that, RSM file contains both model and graphical information. During the analysis, the border between these two sorts of information was determined.
+ </p>
+ <p align="justify">
+ The metamodel from a specific ROSE model is obtained by using the RSM plug-in provided by TOPCASED. This metamodel is required by the transformation.
+ The figure below summarizes the transformation process:
+ </p>
+ <p align="center">
+ <img src="img/TransformationProcess.png"/>
+ <br /><br />
+ <b>Transformation Process</b>
+ </p>
+ <p align="center">
+ <img src="img/UML2Import.png"/>
+ </p>
+ <p align="justify">
+ <b>Import results for a Class Diagram from RSM to TOPCASED UML2 Editor:</b>
+ </p>
+ <p align="center">
+ <img src="img/rsmClassDiagram.png" />
+ <br />
+ <b>RSM</b>
+ </p>
+ <p align="center">
+ <img src="img/topcasedClassDiagram.png" />
+ <br />
+ <b>Topcased</b>
+ </p>
+ <p align="justify">
+ <b>Import results for a Usecase Diagram from RSM to TOPCASED UML2 Editor:</b>
+ </p>
+ <p align="center">
+ <img src="img/rsmUseCaseDiagram.png" />
+ <br />
+ <b>RSM</b>
+ </p>
+ <p align="center">
+ <img src="img/topcasedUseCaseDiagram.png" />
+ <br />
+ <b>Topcased</b>
+
+ </p>
+ <p align="justify">
+ <b>Import results for a Sequence Diagram from RSM to TOPCASED UML2 Editor:</b>
+ </p>
+ <p align="center">
+ <img src="img/rsmSequenceDiagram.png" />
+ <br />
+ <b>RSM</b>
+ </p>
+ <p align="center">
+ <img src="img/topcasedSequenceDiagram.png" />
+ <br />
+ <b>Topcased</b>
+ </p>
+ </td>
+ </tr>
+ </table>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;">
+ <a name="relatedUseCases"></a>Related Use Cases
+ </h4>
+ <table>
+ <COLGROUP>
+ <COL width="2%" />
+ <COL width="98%" />
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ <p align="justify">
+ None at the current time.
+ </p>
+ </td>
+ </tr>
+ </table>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;">
+ <a name="references"></a>References
+ </h4>
+
+ <table width="100%">
+ <tr valign="top">
+ <td>
+ <a href="http://www.sciences.univ-nantes.fr/lina/atl/www/presentations/awme2/09%20-%20An%20operational%20application%20of%20ATL%20to%20bridge%20RSM%20and%20TopCased%20(Gabel).ppt">
+ [1]</a>
+ </td>
+ <td>
+ Sébastien Gabel, Agusti Canals, Christophe Le Camus:
+ <em>An operational application of ATL to bridge RSM and TopCased</em>.
+ In: 2nd AMMA/ATL Workshop on Model Engineering (AWME2), Wednesday 3rd and Thursday 4th May, 2006 University of Nantes, Nantes France
+ </td>
+ </tr>
+ </table>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;">
+ <a name="download">Download</a>
+ </h4>
+
+ <table width="100%">
+ <COLGROUP>
+ <COL width="25%">
+ <COL width="75%">
+ </COLGROUP>
+ <tr>
+ <td align="center"><a href="http://gforge.enseeiht.fr/frs/?group_id=7"><h3>Topcased Core</h3></a></td>
+ <td>Toolkit and SDK features.</td>
+ </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>Acknowledgement
+ </h4>
+
+ <table width="100%">
+ <COLGROUP>
+ <COL width="2%">
+ <COL width="98%">
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ The present work is being supported by the <a href="http://www.topcased.org/">Topcased Project</a>,
+ the <a href="http://www.usine-logicielle.org">Usine Logicielle project of the System@tic Paris Region Cluster</a>,
+ and the <a href="http://openembedd.inria.fr/home_html-en?set_language=en&cl=en">OpenEmbeDD project</a>.
+ </td>
+ </tr>
+ </table>
+
+ </div>
+ </div>
+
+ <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 Sébastien Gabel (<a href="http://www.c-s.fr/">C-S</a>), Agusti Canals (<a href="http://www.c-s.fr/">C-S</a>), Chistophe Le Camus (<a href="http://www.c-s.fr/">C-S</a>),
+ <a href="http://www.sciences.univ-nantes.fr/lina/atl/contrib/allilaire">Freddy Allilaire</a> (INRIA)
+ </li>
+ <li style="list-style:none"><br />Please, ask your questions on the <a href="news://news.eclipse.org/eclipse.modeling.m2m">M2M newsgroup</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/SharingRulesBetweenOCLUML_SWRLOWL/1. EnhancedOCL package.jpg b/usecases/SharingRulesBetweenOCLUML_SWRLOWL/1. EnhancedOCL package.jpg
new file mode 100644
index 0000000..48325b9
--- /dev/null
+++ b/usecases/SharingRulesBetweenOCLUML_SWRLOWL/1. EnhancedOCL package.jpg
Binary files differ
diff --git a/usecases/SharingRulesBetweenOCLUML_SWRLOWL/2. RDM.jpg b/usecases/SharingRulesBetweenOCLUML_SWRLOWL/2. RDM.jpg
new file mode 100644
index 0000000..ecd9c74
--- /dev/null
+++ b/usecases/SharingRulesBetweenOCLUML_SWRLOWL/2. RDM.jpg
Binary files differ
diff --git a/usecases/SharingRulesBetweenOCLUML_SWRLOWL/3. IntegrityRule.jpg b/usecases/SharingRulesBetweenOCLUML_SWRLOWL/3. IntegrityRule.jpg
new file mode 100644
index 0000000..b9ff9e7
--- /dev/null
+++ b/usecases/SharingRulesBetweenOCLUML_SWRLOWL/3. IntegrityRule.jpg
Binary files differ
diff --git a/usecases/SharingRulesBetweenOCLUML_SWRLOWL/4. Complete transformation scenario.jpg b/usecases/SharingRulesBetweenOCLUML_SWRLOWL/4. Complete transformation scenario.jpg
new file mode 100644
index 0000000..6a2b891
--- /dev/null
+++ b/usecases/SharingRulesBetweenOCLUML_SWRLOWL/4. Complete transformation scenario.jpg
Binary files differ
diff --git a/usecases/SharingRulesBetweenOCLUML_SWRLOWL/5. UML model.jpg b/usecases/SharingRulesBetweenOCLUML_SWRLOWL/5. UML model.jpg
new file mode 100644
index 0000000..68be5db
--- /dev/null
+++ b/usecases/SharingRulesBetweenOCLUML_SWRLOWL/5. UML model.jpg
Binary files differ
diff --git a/usecases/SharingRulesBetweenOCLUML_SWRLOWL/6. R2MLRule.jpg b/usecases/SharingRulesBetweenOCLUML_SWRLOWL/6. R2MLRule.jpg
new file mode 100644
index 0000000..5f66104
--- /dev/null
+++ b/usecases/SharingRulesBetweenOCLUML_SWRLOWL/6. R2MLRule.jpg
Binary files differ
diff --git a/usecases/SharingRulesBetweenOCLUML_SWRLOWL/7. SWRLRule.jpg b/usecases/SharingRulesBetweenOCLUML_SWRLOWL/7. SWRLRule.jpg
new file mode 100644
index 0000000..9fb1b6d
--- /dev/null
+++ b/usecases/SharingRulesBetweenOCLUML_SWRLOWL/7. SWRLRule.jpg
Binary files differ
diff --git a/usecases/SharingRulesBetweenOCLUML_SWRLOWL/index.php b/usecases/SharingRulesBetweenOCLUML_SWRLOWL/index.php
new file mode 100644
index 0000000..9ad22e9
--- /dev/null
+++ b/usecases/SharingRulesBetweenOCLUML_SWRLOWL/index.php
@@ -0,0 +1,338 @@
+<?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'
+
+ #*****************************************************************************
+ #
+ # index.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.
+ $shortTitle = "Sharing Rules Between OCL/UML and SWRL/OWL";
+ $pageTitle = "ATL Use Case - " . $shortTitle;
+ $pageKeywords = "";
+ $pageAuthor = "Milan Milanovic";
+
+ # End: page-specific settings
+ #
+
+ # Paste your HTML content between the EOHTML markers!
+ $html = <<<EOHTML
+
+ <!-- Main part -->
+ <div id="midcolumn">
+ <h1>$pageTitle</h1>
+
+ <img align="right" src="../../resources/atlLogoSmall.png" valign="top" style="padding-left: 10px;" alt="ATL Logo" />
+ <blockquote>
+ <ul>
+ <li><a href="#keywords"><b>Keywords</b></a></li>
+ <li><a href="#overview"><b>Overview</b></a></li>
+ <li><a href="#relatedUseCases"><b>Related Use Cases</b></a></li>
+ <li><a href="#references"><b>References</b></a></li>
+ <li><a href="#download"><b>Download</b></a></li>
+ <li><a href="#acknowledgement"><b>Acknowledgement</b></a></li>
+ </ul>
+ </blockquote>
+ <hr class="clearer" />
+
+ <div id="container>
+ <p align="justify">
+ This work presents an implementation of sharing rules between two rule languages from different domains: OCL (Object Constraint Language) together with UML and SWRL (Semantic Web Rule
+ Language) together with OWL. For this integration we used the R2ML (REWERSE I1 Rule Markup Language) metamodel as pivotal metamodel. The R2ML is a general Web rule markup language and
+ it can represent different rule types: integrity, reaction, derivation and production. This work has been done in collaboration between the <A href="http://goodoldai.org.yu/">GOOD OLD
+ AI Laboratory</A> at <a href="http://www.bg.ac.yu">University of Belgrade</a>, <A href="http://www.sfu.ca/siat" target="_self">School of Interactive Arts and Technology</A> at
+ <A href="http://www.surrey.sfu.ca" target="_self">Simon Fraser University Surrey</A> in Canada, <A href="http://scis.athabascau.ca/">School of Computing and Information Systems</A> at
+ <BR />
+ <A href="http://www.athabascau.ca/">Athabasca University</A> in Canada and <a href="http://oxygen.informatik.tu-cottbus.de/IT/">Chair of Internet Technology</a> at
+ <A href="http://www.tu-cottbus.de/">Brandenburg University of Technology at Cottbus</A> in Germany.
+ </p>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;"><a name="keywords"></a>Keywords</h4>
+ <table width="100%">
+ <COLGROUP>
+ <COL width="2%" />
+ <COL width="98%" />
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ <p align="justify">
+ <a href="http://oxygen.informatik.tu-cottbus.de/rewerse-i1/?q=node/6">R2ML</a>,
+ <a href="http://www.w3.org/Submission/SWRL/">SWRL</a>,
+ <a href="http://www.aifb.uni-karlsruhe.de/WBS/sbr/publications/owl-metamodeling.pdf">RDM</a>,
+ <a href="http://www.w3.org/2004/OWL/.">OWL</a>,
+ <a href="http://www.w3.org/TR/owl-xmlsyntax/">OWL XML Syntax</a>,
+ <a href="http://www.omg.org/cgi-bin/doc?formal/06-05-01">OCL</a>,
+ <a href="http://www.uml.org/">UML</a>,
+ Ontology,
+ Rules
+ </p>
+ </td>
+ </tr>
+ </table>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;"><a name="overview"></a>Overview</h4>
+
+ <table width="100%">
+ <COLGROUP>
+ <COL width="2%" />
+ <COL width="98%" />
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ <p align="justify">
+ In this use case, we present rules interchange between the Semantic Web Rule Language along with the Web Ontology Language (SWRL/OWL) and the Object Constraint
+ Language along with the UML (UML/OCL). The solution is based on the REWERSE I1 Rule Markup Language (R2ML), a MOF-defined general rule language, as a pivotal metamodel
+ and the bidirectional transformations between SWRL/OWL and R2ML and between OCL/UML and R2ML. We use the Rule Definition Metamodel (RDM) as metamodel for the SWRL language,
+ that is based on the Ontology Definition Metamodel (ODM).
+ </p>
+ <p align="justify">
+ <strong>OCL</strong> is a language that enables one to describe expressions and constraints on object-oriented (UML and MOF) models and other object modeling artifacts. An
+ expression is an indication or specification of a value. A constraint is a restriction on one or more values of (part of) an object-oriented model or system. The OCL
+ metamodel inerhits the UML metamodel. The <strong>UML</strong> is the most used and known language to model application structure, behaviour and architecture but also
+ business process and data structure. Since the standard specification of the OCL metamodel [1] does not contains support for OCL invariants, in our research, we introduced
+ the <em>EnhancedOCL </em>package is defined in order to fill this gap. This package contains the <em>Invariant</em> class, as a subclass of the <em>OclModuleElement</em>
+ class (see Figure 1). <em>OclModuleElement</em> represents a superclass for: OCL invariant elements (the <em>Invariant</em> class); OCL operations and properties, i.e.,
+ “def” elements (the abstract class <em>OclFeature</em>) that are represented with classes <em>OclOperation</em> and <em>OclProperty</em>, respectively; and OCL
+ derivation rules, i.e., "derive" elements (<em>DeriveOclModuleElement</em>). <em>OclModuleElement</em> contains a definition of an
+ invariant context that is represented with the <em>OclContextDefinition</em> class.
+ </p>
+ <p align="center">
+ <img src="1. EnhancedOCL package.jpg" alt="EnhancedOCL package" width="700" height="356">
+ </p>
+ <p align="center">
+ <strong>Figure 1. </strong>Elements of the EnhancedOCL package in the OCL metamodel
+ </p>
+ <p align="justify">
+ <strong>SWRL</strong> is a web rule language based on combination of the OWL DL and OWL Lite sublanguages of the OWL Web Ontology Language, with the Unary/Binary Datalog
+ RuleML sublanguages of the Rule Markup Language (RuleML). SWRL is based on classical first order logic and its rules are of the form of an implication between an
+ antecedent (body) and a consequent (head). The intended meaning can be read as "whenever the conditions specified in the antecedent hold, then the conditions
+ specified in the consequent must also hold". Both the antecedent (body) and consequent (head) consist of zero or more atoms. Multiple atoms are connected with the
+ conjuction operator. Rule Definition Metamodel (RDM) is a MOF-based meta-model for SWRL, and it is based on [2] (see Figure 2).
+ </p>
+ <p align="center">
+ <img src="2. RDM.jpg" alt="RDM" width="823" height="700">
+ </p>
+ <p align="center">
+ <strong>Figure 2. </strong>Main elements of the Rule Definiton Meta-model (RDM)
+ </p>
+ <p align="justify">
+ <strong>R2ML</strong> represents a general Web rule markup language that is defined by a metamodel that is specified by using the MOF metamodeling language, and it have
+ also a XML-based concrete syntax that is defined with XML Schema. The R2ML metamodel [3] consists of overlapping metamodels for the following types of rules: integrity,
+ derivation, reaction, and production rules. Furthermore, the R2ML XML schema, i.e., an R2ML concrete syntax, has been developed for encoding rules by domain experts.
+ Although OCL can represent both integrity constraints and derivation rules, we only describe R2ML integrity rules here. An <em>integrity rule</em>, also known as<em>
+ (integrity) constraint</em>, consists of a constraint assertion, which is a sentence in a logical language such as first-order predicate logic or OCL (see Figure 3).
+ The R2ML framework supports two kinds of integrity rules: the <em>alethic</em> and <em>deontic</em> ones. An alethic integrity rule can be expressed by a phrase, such
+ as “<em>it is necessarily the case that</em>” and a deontic one can be expressed by phrases, such as “<em>it is obligatory that</em>” or
+ “<em>it should be the case that</em>.”
+ </p>
+ <p align="center">
+ <img src="3. IntegrityRule.jpg" alt="IntegrityRule" width="300" height="131">
+ </p>
+ <p align="center">
+ <strong>Figure 3. </strong>The metamodel of integrity rules
+ </p>
+ <p align="justify">
+ Implemented solution of transforming OCL invariants into the SWRL rules via R2ML rules consists of five transformation steps. The first one (see Figure 4) is between
+ OCL rules (invariants) represented in the OCL concrete syntax (in the EBNF technical space) and models compliant with the OCL metamodel (in the MOF technical space).
+ This is done by using the EBNF injection (ATL feature) of OCL rules, that is, by instantiating the MOF-based OCL metamodel (i.e., creating OCL models) and by using the
+ OCL parser we created. Second, the MOF-based OCL rules obtained (OCL models) are transformed to R2ML models compliant with the R2ML metamodel. In the third step, R2ML
+ models are transformed into the RDM models (i.e., instances of the SWRL metamodel) by using R2ML2RDM.atl transformation. In the fourth step, RDM models are transformed
+ into the XML models (i.e., instances of the XML metamodel) by using transformations RDM2XML.atl transformation.
+ </p>
+ <p align="justify">
+ Five, such XML models (from the MOF technical space) are serialized into the SWRL XML format (complaint with the SWRL XML Schema) by using the ATL XML Extractor tool.
+ All of these transformations are based on the conceptual mappings that we have defined.
+ </p>
+ <p align="center">
+ <img src="4. Complete transformation scenario.jpg" alt="Scenario" width="800" height="250">
+ </p>
+ <p align="center">
+ <strong>Figure 4. </strong>The transformation scenario between the OCL and SWRL via R2ML
+ </p>
+ <p align="justify">
+ In addition, we have also defined transformations in opposite direction, so it is possible to translate SWRL rules into the OCL invariants via R2ML (remark: this side have
+ ceratin constraints).
+ </p>
+ <p align="justify">
+ A UML model which contains a UML class (<em>Customer</em>) and has an OCL invariant defined on that class: <em>if customer name is 'Jos senior' implies that is age is more
+ than 21</em>. is given in Figure 5. to serve as a running example for this use case.
+ </p>
+ <p align="center">
+ <img src="5. UML model.jpg" alt="UML model" width="400" height="97">
+ </p>
+ <p align="center">
+ <strong>Figure 5. </strong>OCL invariant and its corresponding UML class <em>Customer</em>
+ </p>
+ <p align="justify">
+ We first inject OCL code from Figure 5. into the OCL model by using the EBNF injector, (see Figure 4: EBNF injection), a part of the ATL toolkit, and the OCL Lexer and
+ Parser. We generated the OCL Parser and Lexer by using the TCS (Textual Concrete Syntax), i.e., by defining TCS for the OCL. When we got an OCL model we then transform
+ OCL metamodel elements into the R2ML metamodel elements (by using OCL2R2ML.atl transformations from Figure 4). As a result we get the R2ML model that can be serialized
+ into the R2ML XML format (see Figure 6.). More details about this serialization process you can find in [4].
+ </p>
+ <p align="center">
+ <img src="6. R2MLRule.jpg" alt="R2ML Rule" width="500" height="385">
+ </p>
+ <p align="center">
+ <strong>Figure 6. </strong>An R2ML (alethic) integrity rule equivalent to the OCL invariant from Figure 5
+ </p>
+ <p align="justify">
+ In the next step we transform attained R2ML model into the RDM model (instance of SWRL metamodel) by using R2ML2RDM.atl transformation from Figure 4. Such RDM model can be
+ serialized in the SWRL XML concrete syntax. In order to serialize the RDM model (from the MOF technical space) into the SWRL XML concrete syntax (i.e., to the XML technical
+ space), we first need to use the RDM2XML.atl transformation (see Figure 4) to get an XML model from RDM model.
+ </p>
+ <p align="justify">
+ When we got a XML model which conforms to the MOF-based XML metamodel we can extract such model extraction from the MOF technical space to the XML technical space (XML
+ extraction in Figure 4.) by using the XML extractor. A result of this transformations process for the RDM model attained in previous step is a SWRL rule in the SWRL XML
+ concrete syntax (see Figure 7).
+ </p>
+ <p align="center">
+ <img src="7. SWRLRule.jpg" alt="SWRLRule" width="520" height="283">
+ </p>
+ <p align="center">
+ <strong>Figure 7. </strong>SWRL rule of the transformed OCL invariant from Figure 5
+ </p>
+ <p align="justify">
+ This use case demonstrates how the AMMA tools can be used to share rules between different rule languages whose concrete syntaxes are defined in different technical spaces
+ (i.e., in the XML, MOF and EBNF technical spaces). This ATL scenario provides a solution for bridging SWRL/OWL and OCL/UML is based on the pivotal (R2ML) metamodel that
+ addresses the complexity of mappings between two rule languages, which contain many diverse concepts. More details about this scenario you can find in [5].
+ </p>
+ </td>
+ </tr>
+ </table>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;">
+ <a name="relatedUseCases"></a>Related Use Cases
+ </h4>
+ <table>
+ <COLGROUP>
+ <COL width="2%" />
+ <COL width="98%" />
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ <p align="justify">
+ None at the current time.
+ </p>
+ </td>
+ </tr>
+ </table>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;">
+ <a name="references"></a>References
+ </h4>
+
+ <table width="100%">
+ <tr valign="top">
+ <td width="4%">
+ <a href="http://www.omg.org/docs/formal/06-05-01.pdf">[1]</a>
+ </td>
+ <td width="96%">
+ Object Constraint Language (OCL), OMG Specification, Version 2.0, formal/06-05-01, 2006.
+ </td>
+ </tr>
+ <tr valign="top">
+ <td width="4%">
+ <a href="http://www.aifb.uni-karlsruhe.de/WBS/sbr/publications/owl-metamodeling.pdf">[2]</a>
+ </td>
+ <td width="96%">
+ Brockmans, S., Haase, P., "A Metamodel and UML Profile for Rule-extended OWL DL Ontologies - A Complete Reference", Universität Karlsruhe (TH) - Technical Report, 2006.
+ </td>
+ </tr>
+ <tr valign="top">
+ <td width="4%">
+ <a href="http://oxygen.informatik.tu-cottbus.de/rewerse-i1/?q=node/6">[3]</a>
+ </td>
+ <td width="96%">
+ R2ML (REWERSE I1 Rule Markup Language) metamodel in MOF/UML format.
+ </td>
+ </tr>
+ <tr valign="top">
+ <td>
+ [4]
+ </td>
+ <td>
+ Milanovic, M., Gaševic, D., Giurca, A., Wagner, G., Lukichev, S., Devedžic, V., "Bridging Concrete and Abstract Syntax of Web Rule Languages",
+ <b><i>The First International Conference on Web Reasoning and Rule Systems (RR2007)</i></b>, Innsbruck, Austria, 2007.
+ </td>
+ </tr>
+ <tr valign="top">
+ <td>
+ [5]
+ </td>
+ <td>
+ Milanovic, M., Gaševic, D., Giurca, A., Wagner, G., Devedžic, V., "Towards Sharing Rules Between OWL/SWRL and UML/OCL",
+ <b><i>Electronic Communications of the European Association of Software Science and Technology</i></b>, Volume 5, 2006.
+ </td>
+ </tr>
+ </table>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;">
+ <a name="download">Download</a>
+ </h4>
+
+ <table width="100%" height="52">
+ <COLGROUP>
+ <COL width="25%">
+ <COL width="75%">
+ </COLGROUP>
+ <tr>
+ <td align="center"><a href="http://www.eclipse.org/atl/atlTransformations/#OCL2SWRL"><h3>Complete scenario</h3></a></td>
+ <td>Scenario available in the ATL transformation zoo (with source files).</td>
+ </tr>
+ <tr>
+ <td align="center"><a href="http://www.eclipse.org/gmt/am3/zoos/atlanticZoo/#R2ML"><h3>R2ML metamodel</h3></a></td>
+ <td>R2ML metamodel is expressed in the <A href="http://wiki.eclipse.org/index.php/KM3">KM3</A> textual format.</td>
+ </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>Acknowledgement
+ </h4>
+
+ <table width="100%">
+ <COLGROUP>
+ <COL width="2%">
+ <COL width="98%">
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ The present work is being done in collaborative work with REWERSE I1 and LORNET Theme 1 projects.
+ </td>
+ </tr>
+ </table>
+
+ </div>
+ </div>
+
+ <div id="rightcolumn">
+ <div class="sideitem">
+ <h6>General Information</h6>
+ <ul>
+ <li style="list-style:none">March 2007</li>
+ <li style="list-style:none">
+ By <a href="http://milan.milanovic.org">Milan Milanovic</a> (GOOD OLD AI Laboratory)
+ </li>
+ <li style="list-style:none">
+ <br />Please, ask your questions by e-mail: <a href="mailto:milan [at] milanovic.org">milan [at] milanovic.org</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/Sildex2AADL/img/AADLEditor.PNG b/usecases/Sildex2AADL/img/AADLEditor.PNG
new file mode 100644
index 0000000..4c74908
--- /dev/null
+++ b/usecases/Sildex2AADL/img/AADLEditor.PNG
Binary files differ
diff --git a/usecases/Sildex2AADL/img/atlRules.PNG b/usecases/Sildex2AADL/img/atlRules.PNG
new file mode 100644
index 0000000..9ab3991
--- /dev/null
+++ b/usecases/Sildex2AADL/img/atlRules.PNG
Binary files differ
diff --git a/usecases/Sildex2AADL/img/diagram1.PNG b/usecases/Sildex2AADL/img/diagram1.PNG
new file mode 100644
index 0000000..470d13a
--- /dev/null
+++ b/usecases/Sildex2AADL/img/diagram1.PNG
Binary files differ
diff --git a/usecases/Sildex2AADL/img/diagram2.PNG b/usecases/Sildex2AADL/img/diagram2.PNG
new file mode 100644
index 0000000..0c79702
--- /dev/null
+++ b/usecases/Sildex2AADL/img/diagram2.PNG
Binary files differ
diff --git a/usecases/Sildex2AADL/img/sampleAADL.PNG b/usecases/Sildex2AADL/img/sampleAADL.PNG
new file mode 100644
index 0000000..5eddf72
--- /dev/null
+++ b/usecases/Sildex2AADL/img/sampleAADL.PNG
Binary files differ
diff --git a/usecases/Sildex2AADL/img/sampleAADL2.PNG b/usecases/Sildex2AADL/img/sampleAADL2.PNG
new file mode 100644
index 0000000..33185b5
--- /dev/null
+++ b/usecases/Sildex2AADL/img/sampleAADL2.PNG
Binary files differ
diff --git a/usecases/Sildex2AADL/img/sampleAADL2_model.PNG b/usecases/Sildex2AADL/img/sampleAADL2_model.PNG
new file mode 100644
index 0000000..0a95e23
--- /dev/null
+++ b/usecases/Sildex2AADL/img/sampleAADL2_model.PNG
Binary files differ
diff --git a/usecases/Sildex2AADL/index.php b/usecases/Sildex2AADL/index.php
new file mode 100644
index 0000000..db5c7a9
--- /dev/null
+++ b/usecases/Sildex2AADL/index.php
@@ -0,0 +1,247 @@
+<?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.
+ $shortTitle = "Sildex to Topcased AADL/COTRE";
+ $pageTitle = "ATL Use Case - " . $shortTitle;
+ $pageKeywords = "";
+ $pageAuthor = "Freddy Allilaire";
+
+ # End: page-specific settings
+ #
+
+ # Paste your HTML content between the EOHTML markers!
+ $html = <<<EOHTML
+
+ <!-- Main part -->
+ <div id="midcolumn">
+ <h1>$pageTitle</h1>
+
+ <img align="right" src="../../resources/atlLogoSmall.png" valign="top" style="padding-left: 10px;" alt="ATL Logo" />
+ <blockquote>
+ <ul>
+ <li><a href="#keywords"><b>Keywords</b></a></li>
+ <li><a href="#overview"><b>Overview</b></a></li>
+ <li><a href="#relatedUseCases"><b>Related Use Cases</b></a></li>
+ <li><a href="#download"><b>Download</b></a></li>
+ <li><a href="#acknowledgement"><b>Acknowledgement</b></a></li>
+ </ul>
+ </blockquote>
+
+ <hr class="clearer" />
+
+ <div id="container>
+ <p align="justify">
+
+ </p>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;"><a name="keywords"></a>Keywords</h4>
+ <table width="100%">
+ <COLGROUP>
+ <COL width="2%" />
+ <COL width="98%" />
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ <p align="justify">
+ TOPCASED, SILDEX, SIGNAL, AADL
+ </p>
+ </td>
+ </tr>
+ </table>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;"><a name="overview"></a>Overview</h4>
+
+ <table width="100%">
+ <COLGROUP>
+ <COL width="2%" />
+ <COL width="98%" />
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ <p align="justify">
+ This use case presents the import of SILDEX models (a synchronous language based graphical modelling formalism developed by
+ <a href="http://www.tni-software.com/">TNI</a> and currently in use at <a href="http://www.airbus.com/en/">AIRBUS</a>) in AADL/COTRE.
+ It was implemented in ATL by <a href="http://www.c-s.fr/">C-S</a> in the context of the TOPCASED project.
+ </p>
+ <p align="justify">
+ SILDEX is a CASE tool supporting SIGNAL synchronous languages. It provides graphical and SIGNAL code editing of each process and relevant dataflow; formal proof with
+ "synchronous compilation"; dynamic simulation; ADA, C and FORTRAN code generation, and documentation production. SILDEX was designed and tested in Smalltalk, then
+ translated into C code with TNI's OpenTalk compiler. SILDEX targets critical real-time software developments.
+ </p>
+ <p align="justify">
+ <a href="http://www.topcased.org/">TOPCASED</a> is an open-source workshop based on an Eclipse platform. Several editors are available:
+ SAM, AADL, UML2, ECORE, and SYSML.
+ It integrate several transformation services. These services are based on ATL language and toolkit. Model transformations have been mainly used in order to
+ access models defined using other editors than TOPCASED one's. Other services around models are available like OCL editor and checker, comparison, merging, etc.
+ </p>
+ <p align="justify">
+ <a href="http://gforge.enseeiht.fr/projects/topcased-aadl/">TOPCASED-AADL</a> is a subproject of the TOPCASED project. This subproject provides a set of modeling,
+ transforming and verifying tools around AADL (Architecture Analysis and Design Language). These tools are based on the AADL metamodel that has been developped by the
+ SEI for the <a href="http://www.aadl.info/">OSATE</a> project. AADL/COTRE is a language (including AADL) resulting from the
+ <a href="http://www.laas.fr/COTRE/work/output/cotre-erts.pdf">COTRE project</a>.
+ </p>
+ <p align="justify">
+ From the YACC grammar of AADL/COTRE, a metamodel has been defined. The following example shows an excerpt of the available grammar:
+ </p>
+ <p align="left">
+ <img src="img/sampleAADL.PNG" />
+ <br /><br />
+ <b></b>
+ </p>
+ <p align="justify">
+ This metamodeling process implies an iterative approach revealing new reductions with each iteration.
+ The following example shows the result of the metamodeling process:
+ </p>
+ <div align="center">
+ <table width="100%">
+ <tr>
+ <td align="center" valign="top"><img src="img/sampleAADL2.PNG" /></td>
+ <td align="center" valign="top"><img src="img/sampleAADL2_model.PNG" /></td>
+ </tr>
+ </table>
+ </div>
+ <p align="justify">
+ After the creation of the source metamodel SILDEX and the target metamodel AADL/COTRE, the TOPCASED process to make a transformation can be breakdown as follow:
+ <ul>
+ <li>first, the mapping of the concepts, </li>
+ <li>then the writing of the ATL transformation rules and the automatic transformation by rule execution (also with ATL),</li>
+ <li>at last, manual check of the result through the reading of the files obtained by the editors (in this use case TOPCASED AADL Editor).</li>
+ </ul>
+ </p>
+ <p align="center">
+ <img src="img/atlRules.PNG" />
+ <br /><br />
+ <b>Excerpt of the ATL transformation: Sildex to AADL</b>
+ </p>
+ <p align="justify">
+ Today the TOPCASED service to transform SILDEX models to AADL models is operational and used by the TOPCASED Project.
+ </p>
+ <p align="center">
+ <img src="img/AADLEditor.PNG" />
+ <br /><br />
+ <b>Screenshot of AADL Editor</b>
+ </p>
+ </td>
+ </tr>
+ </table>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;">
+ <a name="relatedUseCases"></a>Related Use Cases
+ </h4>
+ <table>
+ <COLGROUP>
+ <COL width="2%" />
+ <COL width="98%" />
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ <p align="justify">
+ None at the current time.
+ </p>
+ </td>
+ </tr>
+ </table>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;">
+ <a name="references"></a>References
+ </h4>
+
+ <table width="100%">
+ <tr valign="top">
+ <td>
+ [1]
+ </td>
+ <td>
+ Canals, A.; Le Camus, C.; Feau, M.; et al.:
+ <em>An Operational Use of ATL: Integration of Model and Meta Model Transformations in the TOPCASED Project</em>.
+ In: DASIA 2006 - Data Systems in Aerospace, Proceedings of the conference held 22-25 May, 2006 in Berlin, Germany.
+ Edited by L. Ouwehand. ESA SP-630. European Space Agency, 2006. Published on CDROM., p.40.1
+ </td>
+ </tr>
+ <tr valign="top">
+ <td>
+ <a name="[2]" href="http://www.sciences.univ-nantes.fr/lina/atl/www/papers/eTX2006/21-MarcPantel.pdf">
+ [2]
+ </a>
+ </td>
+ <td>
+ Patrick Farail, Pierre Gaufillet, Agusti Canals, Christophe Le Camus, David Sciamma, Pierre Michel, Xavier Crégut, Marc Pantel:
+ <em>The TOPCASED project: a Toolkit in Open source for Critical Aeronautic SystEms Design</em>.
+ In: Proceedings of the Eclipse Technology eXchange workshop (eTX) at ECOOP 2006.
+ </td>
+ </tr>
+ </table>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;">
+ <a name="download">Download</a>
+ </h4>
+
+ <table width="100%">
+ <COLGROUP>
+ <COL width="25%">
+ <COL width="75%">
+ </COLGROUP>
+ <tr>
+ <td align="center"><a href="http://gforge.enseeiht.fr/frs/?group_id=7"><h3>Topcased Core</h3></a></td>
+ <td>Toolkit and SDK features.</td>
+ </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>Acknowledgement
+ </h4>
+
+ <table width="100%">
+ <COLGROUP>
+ <COL width="2%">
+ <COL width="98%">
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ The present work is being supported by the <a href="http://www.topcased.org/">Topcased Project</a>,
+ the <a href="http://www.usine-logicielle.org">Usine Logicielle project of the System@tic Paris Region Cluster</a>,
+ and the <a href="http://openembedd.inria.fr/home_html-en?set_language=en&cl=en">OpenEmbeDD project</a>.
+ </td>
+ </tr>
+ </table>
+
+ </div>
+ </div>
+
+ <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 Agusti Canals (<a href="http://www.c-s.fr/">C-S</a>), Chistophe Le Camus (<a href="http://www.c-s.fr/">C-S</a>),
+ <a href="http://www.sciences.univ-nantes.fr/lina/atl/contrib/allilaire">Freddy Allilaire</a> (INRIA)
+ </li>
+ <li style="list-style:none"><br />Please, ask your questions on the <a href="news://news.eclipse.org/eclipse.modeling.m2m">M2M newsgroup</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/Sildex2SAM/img/MMSAM.PNG b/usecases/Sildex2SAM/img/MMSAM.PNG
new file mode 100644
index 0000000..ad4ab30
--- /dev/null
+++ b/usecases/Sildex2SAM/img/MMSAM.PNG
Binary files differ
diff --git a/usecases/Sildex2SAM/img/SAMEditor.PNG b/usecases/Sildex2SAM/img/SAMEditor.PNG
new file mode 100644
index 0000000..fad0f35
--- /dev/null
+++ b/usecases/Sildex2SAM/img/SAMEditor.PNG
Binary files differ
diff --git a/usecases/Sildex2SAM/img/atlRules.PNG b/usecases/Sildex2SAM/img/atlRules.PNG
new file mode 100644
index 0000000..ea2ab62
--- /dev/null
+++ b/usecases/Sildex2SAM/img/atlRules.PNG
Binary files differ
diff --git a/usecases/Sildex2SAM/img/example.PNG b/usecases/Sildex2SAM/img/example.PNG
new file mode 100644
index 0000000..dacc99e
--- /dev/null
+++ b/usecases/Sildex2SAM/img/example.PNG
Binary files differ
diff --git a/usecases/Sildex2SAM/index.php b/usecases/Sildex2SAM/index.php
new file mode 100644
index 0000000..56f12a4
--- /dev/null
+++ b/usecases/Sildex2SAM/index.php
@@ -0,0 +1,248 @@
+<?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.
+ $shortTitle = "Sildex to Topcased SAM";
+ $pageTitle = "ATL Use Case - " . $shortTitle;
+ $pageKeywords = "";
+ $pageAuthor = "Freddy Allilaire";
+
+ # End: page-specific settings
+ #
+
+ # Paste your HTML content between the EOHTML markers!
+ $html = <<<EOHTML
+
+ <!-- Main part -->
+ <div id="midcolumn">
+ <h1>$pageTitle</h1>
+
+ <img align="right" src="../../resources/atlLogoSmall.png" valign="top" style="padding-left: 10px;" alt="ATL Logo" />
+ <blockquote>
+ <ul>
+ <li><a href="#keywords"><b>Keywords</b></a></li>
+ <li><a href="#overview"><b>Overview</b></a></li>
+ <li><a href="#relatedUseCases"><b>Related Use Cases</b></a></li>
+ <li><a href="#download"><b>Download</b></a></li>
+ <li><a href="#acknowledgement"><b>Acknowledgement</b></a></li>
+ </ul>
+ </blockquote>
+
+ <hr class="clearer" />
+
+ <div id="container>
+ <p align="justify">
+
+ </p>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;"><a name="keywords"></a>Keywords</h4>
+ <table width="100%">
+ <COLGROUP>
+ <COL width="2%" />
+ <COL width="98%" />
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ <p align="justify">
+ TOPCASED, SAM, SILDEX, SIGNAL
+ </p>
+ </td>
+ </tr>
+ </table>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;"><a name="overview"></a>Overview</h4>
+
+ <table width="100%">
+ <COLGROUP>
+ <COL width="2%" />
+ <COL width="98%" />
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ <p align="justify">
+ This use case presents the import of SILDEX models (a synchronous language based graphical modelling formalism developed by
+ <a href="http://www.tni-software.com/">TNI</a> and currently in use at <a href="http://www.airbus.com/en/">AIRBUS</a>) in the TOPCASED SAM modelling language.
+ It was implemented in ATL by <a href="http://www.c-s.fr/">C-S</a> in the context of the TOPCASED project.
+ </p>
+ <p align="justify">
+ SILDEX is a CASE tool supporting SIGNAL synchronous languages. It provides graphical and SIGNAL code editing of each process and relevant dataflow; formal proof with
+ "synchronous compilation"; dynamic simulation; ADA, C and FORTRAN code generation, and documentation production. SILDEX was designed and tested in Smalltalk, then
+ translated into C code with TNI's OpenTalk compiler. SILDEX targets critical real-time software developments.
+ </p>
+ <p align="justify">
+ <a href="http://www.topcased.org/">TOPCASED</a> is an open-source workshop based on an Eclipse platform. Several editors are available:
+ SAM, AADL, UML2, ECORE, and SYSML.
+ It integrate several transformation services. These services are based on ATL language and toolkit. Model transformations have been mainly used in order to
+ access models defined using other editors than TOPCASED one's. Other services around models are available like OCL editor and checker, comparison, merging, etc.
+ </p>
+ <p align="justify">
+ <a href="http://gforge.enseeiht.fr/projects/topcased-sam/">TOPCASED-SAM</a> is a subproject of the TOPCASED project. This subproject provides a set of modeling,
+ transforming and verifying tools for functional structured analysis.
+ </p>
+ <p align="justify">
+ A metamodel for SILDEX defining all the concepts that can be handled in TOPCASED SAM formalism has been defined. The SILDEX example below
+ illustrates the communication of two sub-systems named "Producer" and "Consumer" via data flows and control flows connected on ports (not visible
+ on the sub system "Consumer").
+ </p>
+ <p align="center">
+ <img src="img/example.PNG" />
+ <br /><br />
+ <b>An example of communication between two sub-systems</b>
+ </p>
+ <p align="justify">
+ This example illustrates the following notions: System, Data flows prefixed by FD_, Control flows prefixed by FC_, Ports that we specialised depending
+ on their nature and their direction. To precise some relations, a system can contain sub systems, and a flow is linked by ports. The confrontation of the
+ analysis of other examples allowed to extend the SAM metamodel whose simplified view is proposed in the following figure.
+ </p>
+ <p align="center">
+ <img src="img/MMSAM.PNG" />
+ <br /><br />
+ <b>A simplified view of the SAM metamodel</b>
+ </p>
+ <p align="justify">
+ SAM represents the new TOPCASED business metamodel for functional and automaton parts of SILDEX.
+ </p>
+ <p align="justify">
+ After the creation of the source metamodel SILDEX and the target metamodel SAM, the TOPCASED process to make a transformation can be breakdown as follow:
+ <ul>
+ <li>first, the mapping of the concepts, </li>
+ <li>then the writing of the ATL transformation rules and the automatic transformation by rule execution (also with ATL),</li>
+ <li>at last, manual check of the result through the reading of the files obtained by the editors (in this use case TOPCASED SAM Editor).</li>
+ </ul>
+ </p>
+ <p align="center">
+ <img src="img/atlRules.PNG" />
+ <br /><br />
+ <b>Excerpt of the ATL transformation: Sildex to SAM</b>
+ </p>
+ <p align="justify">
+ Today the TOPCASED service to transform SILDEX models to SAM models is operational and used by AIRBUS France. More information on this work can be found in [1].
+ </p>
+ <p align="center">
+ <img src="img/SAMEditor.PNG" />
+ <br /><br />
+ <b>Screenshot of SAM Editor</b>
+ </p>
+ </td>
+ </tr>
+ </table>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;">
+ <a name="relatedUseCases"></a>Related Use Cases
+ </h4>
+ <table>
+ <COLGROUP>
+ <COL width="2%" />
+ <COL width="98%" />
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ <p align="justify">
+ None at the current time.
+ </p>
+ </td>
+ </tr>
+ </table>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;">
+ <a name="references"></a>References
+ </h4>
+
+ <table width="100%">
+ <tr valign="top">
+ <td>
+ [1]
+ </td>
+ <td>
+ Canals, A.; Le Camus, C.; Feau, M.; et al.:
+ <em>An Operational Use of ATL: Integration of Model and Meta Model Transformations in the TOPCASED Project</em>.
+ In: DASIA 2006 - Data Systems in Aerospace, Proceedings of the conference held 22-25 May, 2006 in Berlin, Germany.
+ Edited by L. Ouwehand. ESA SP-630. European Space Agency, 2006. Published on CDROM., p.40.1
+ </td>
+ </tr>
+ <tr valign="top">
+ <td>
+ <a name="[2]" href="http://www.sciences.univ-nantes.fr/lina/atl/www/papers/eTX2006/21-MarcPantel.pdf">
+ [2]
+ </a>
+ </td>
+ <td>
+ Patrick Farail, Pierre Gaufillet, Agusti Canals, Christophe Le Camus, David Sciamma, Pierre Michel, Xavier Crégut, Marc Pantel:
+ <em>The TOPCASED project: a Toolkit in Open source for Critical Aeronautic SystEms Design</em>.
+ In: Proceedings of the Eclipse Technology eXchange workshop (eTX) at ECOOP 2006.
+ </td>
+ </tr>
+ </table>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;">
+ <a name="download">Download</a>
+ </h4>
+
+ <table width="100%">
+ <COLGROUP>
+ <COL width="25%">
+ <COL width="75%">
+ </COLGROUP>
+ <tr>
+ <td align="center"><a href="http://gforge.enseeiht.fr/frs/?group_id=7"><h3>Topcased Core</h3></a></td>
+ <td>Toolkit and SDK features.</td>
+ </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>Acknowledgement
+ </h4>
+
+ <table width="100%">
+ <COLGROUP>
+ <COL width="2%">
+ <COL width="98%">
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ The present work is being supported by the <a href="http://www.topcased.org/">Topcased Project</a>,
+ the <a href="http://www.usine-logicielle.org">Usine Logicielle project of the System@tic Paris Region Cluster</a>,
+ and the <a href="http://openembedd.inria.fr/home_html-en?set_language=en&cl=en">OpenEmbeDD project</a>.
+ </td>
+ </tr>
+ </table>
+
+ </div>
+ </div>
+
+ <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 Agusti Canals (<a href="http://www.c-s.fr/">C-S</a>), Chistophe Le Camus (<a href="http://www.c-s.fr/">C-S</a>),
+ <a href="http://www.sciences.univ-nantes.fr/lina/atl/contrib/allilaire">Freddy Allilaire</a> (INRIA)
+ </li>
+ <li style="list-style:none"><br />Please, ask your questions on the <a href="news://news.eclipse.org/eclipse.modeling.m2m">M2M newsgroup</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/SimplePDL2Tina/img/PetriNet.png b/usecases/SimplePDL2Tina/img/PetriNet.png
new file mode 100644
index 0000000..335d00e
--- /dev/null
+++ b/usecases/SimplePDL2Tina/img/PetriNet.png
Binary files differ
diff --git a/usecases/SimplePDL2Tina/img/SimplePDL.png b/usecases/SimplePDL2Tina/img/SimplePDL.png
new file mode 100644
index 0000000..14abc3a
--- /dev/null
+++ b/usecases/SimplePDL2Tina/img/SimplePDL.png
Binary files differ
diff --git a/usecases/SimplePDL2Tina/img/SimplePDL2PetriNetconceptual.png b/usecases/SimplePDL2Tina/img/SimplePDL2PetriNetconceptual.png
new file mode 100644
index 0000000..10794db
--- /dev/null
+++ b/usecases/SimplePDL2Tina/img/SimplePDL2PetriNetconceptual.png
Binary files differ
diff --git a/usecases/SimplePDL2Tina/img/checkmodel.png b/usecases/SimplePDL2Tina/img/checkmodel.png
new file mode 100644
index 0000000..a3bb70b
--- /dev/null
+++ b/usecases/SimplePDL2Tina/img/checkmodel.png
Binary files differ
diff --git a/usecases/SimplePDL2Tina/img/checktransfo.png b/usecases/SimplePDL2Tina/img/checktransfo.png
new file mode 100644
index 0000000..0273dea
--- /dev/null
+++ b/usecases/SimplePDL2Tina/img/checktransfo.png
Binary files differ
diff --git a/usecases/SimplePDL2Tina/img/mapping.png b/usecases/SimplePDL2Tina/img/mapping.png
new file mode 100644
index 0000000..c71f4d3
--- /dev/null
+++ b/usecases/SimplePDL2Tina/img/mapping.png
Binary files differ
diff --git a/usecases/SimplePDL2Tina/img/pdl2pn.atl.png b/usecases/SimplePDL2Tina/img/pdl2pn.atl.png
new file mode 100644
index 0000000..4e78eba
--- /dev/null
+++ b/usecases/SimplePDL2Tina/img/pdl2pn.atl.png
Binary files differ
diff --git a/usecases/SimplePDL2Tina/img/pdl2pnR.atl.png b/usecases/SimplePDL2Tina/img/pdl2pnR.atl.png
new file mode 100644
index 0000000..ee6545e
--- /dev/null
+++ b/usecases/SimplePDL2Tina/img/pdl2pnR.atl.png
Binary files differ
diff --git a/usecases/SimplePDL2Tina/img/pn2tina.atl.png b/usecases/SimplePDL2Tina/img/pn2tina.atl.png
new file mode 100644
index 0000000..64af143
--- /dev/null
+++ b/usecases/SimplePDL2Tina/img/pn2tina.atl.png
Binary files differ
diff --git a/usecases/SimplePDL2Tina/img/temporalPN1.png b/usecases/SimplePDL2Tina/img/temporalPN1.png
new file mode 100644
index 0000000..529fde8
--- /dev/null
+++ b/usecases/SimplePDL2Tina/img/temporalPN1.png
Binary files differ
diff --git a/usecases/SimplePDL2Tina/index.php b/usecases/SimplePDL2Tina/index.php
new file mode 100644
index 0000000..fc32b7b
--- /dev/null
+++ b/usecases/SimplePDL2Tina/index.php
@@ -0,0 +1,408 @@
+<?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.
+ $shortTitle = "Models Validation through Petri nets: The SimplePDL to TINA Case Study";
+ $pageTitle = "ATL Use Case - " . $shortTitle;
+ $pageKeywords = "";
+ $pageAuthor = "Freddy Allilaire";
+
+ # End: page-specific settings
+ #
+
+ # Paste your HTML content between the EOHTML markers!
+ $html = <<<EOHTML
+
+ <!-- Main part -->
+ <div id="midcolumn">
+ <h1>$pageTitle</h1>
+
+ <img align="right" src="../../resources/atlLogoSmall.png" valign="top" style="padding-left: 10px;" alt="ATL Logo" />
+ <blockquote>
+ <ul>
+ <li><a href="#keywords"><b>Keywords</b></a></li>
+ <li><a href="#overview"><b>Overview</b></a>
+ <ul>
+ <li><a href="#elements">Building blocs</a></li>
+ <li><a href="#transfo">The translation schema from a SimplePDL model into Petri nets</a></li>
+ <li><a href="#prop">Properties generation for process model validation</a></li>
+
+ </ul>
+ </li>
+ <li><a href="#relatedUseCases"><b>Related Use Cases</b></a></li>
+ <li><a href="#references"><b>References</b></a></li>
+ <li><a href="#download"><b>Download</b></a></li>
+ <li><a href="#acknowledgement"><b>Acknowledgement</b></a></li>
+ </ul>
+ </blockquote>
+
+ <hr class="clearer" />
+
+ <div id="container>
+ <p align="justify">
+ This work presents a use case of model transformation using ATL rules to validate MDD's models.
+ This use case considers a simplified process description language, SimplePDL. It then presents a property-driven approach
+ in which SimplePDL process models are translated into Petri nets. SimplePDL behavioral properties
+ are expressed on corresponding Petri nets in LTL (<i>Linear Temporal Logic</i>).
+ The Tina toolkit and, in particular, its model-checker, are used to validate process models by checking the expressed properties.
+ All the code for the transformations in ATL and for the metamodels in KM3 is available from the <a href="http://www.eclipse.org/gmt/am3/zoos/">Zoos</a>.
+ <br/>
+ This work has been done in collaboration between <a href="http://www.irit.fr">IRIT</a> and <a href="http://www.laas.fr/">LAAS</a> labs in Toulouse, France.
+ </p>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;"><a name="keywords"></a>Keywords</h4>
+ <table width="100%">
+ <COLGROUP>
+ <COL width="2%" />
+ <COL width="98%" />
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ <p align="justify">
+ DSL's Translational Semantics,
+ Verification,
+ Process Engineering,
+ <a href="http://acadie.enseeiht.fr/topcased/tutorial">SimplePDL</a>,
+ <a href="http://en.wikipedia.org/wiki/Petri_net">Petri nets</a>,
+ <a href="http://www.laas.fr/tina/">Tina</a>.
+ </p>
+ </td>
+ </tr>
+ </table>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;"><a name="overview"></a>Overview</h4>
+
+ <table width="100%">
+ <COLGROUP>
+ <COL width="2%" />
+ <COL width="98%" />
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ <h5 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;"><a name="elements"></a>Building blocs</h5>
+
+ <p align="justify">
+ This use case is introduced through a modeling language example on which we would like to express a set of properties that
+ have to be verified on all possible models. Our DSL is a simple process description language: SimplePDL.
+ </p>
+ <p align="justify">
+ <b><a href="http://combemale.perso.enseeiht.fr/atluc/pdl.km3">SimplePDL</a></b> is an experimental language for specifying processes.
+ The SPEM standard (<i>Software Process Engineering Metamodel</i>) proposed by the OMG inspired our work,
+ but we also took ideas from the UMA metamodel (<i>Unified Method Architecture</i>) used in the <a href="http://www.eclipse.org/epf/">EPF Eclipse plug-in</a>
+ (<i>Eclipse Process Framework</i>), dedicated to process modeling. SimplePDL is simplified to keep the presentation simple.
+ <br />
+ Its metamodel is given in the figure 1.
+ It defines the process concept (<i>Process</i>) composed of a set of
+ work definitions (<i>WorkDefinition</i>) representing the activities to be performed during the development.
+ One workdefinition may depend upon another
+ (<i>WorkSequence</i>). In such a case, an ordering constraint (<i>linkType</i>) on the second workdefinition is specified, using the
+ enumeration <i>WorkSequenceType</i>. For example, linking two workdefinitions <i>wd1</i> and <i>wd2</i>
+
+ by a precedence relation of kind <i>finishToStart</i> means that <i>wd2</i>
+ can be started only if <i>wd1</i> is finished (and respectively for
+ <i>startToStart</i>, <i>startToFinish</i> and <i>finishToFinish</i>).
+ SimplePDL does also allow to explicitly represent resources
+ (<i>Resource</i>) that are needed in order to perform one workdefinition (designer,
+ computer, server...) and also time constraints (<i>min_time</i> and <i>max_time</i> on
+
+ <i>WorkDefinition</i> and <i>Process</i>) to specify the minimum
+ (resp. maximum) time allowed to perform the workdefinition or the whole process.
+ <br />
+ One can remark that, for the sake of brevity, some concepts are not presented here such as products
+ (<i>WorkProduct</i>) that workdefinitions handle, or roles (<i>Role</i>) that can be assimilated to resources.
+ <br />
+ In order to create process models conformed to SimplePDL, the Topcased project allows to generate graphical editors under the Eclipse framework.
+ A complete tutorial on how to construct a SimplePDL modeling tool is available <a href="http://acadie.enseeiht.fr/topcased/tutorial/">here</a> (in french).
+ </p>
+
+ <p align="center">
+ <a href="img/SimplePDL.png"><img width="50%" src="img/SimplePDL.png" /></a>
+ <br /><br />
+ <b>1. SimplePDL metamodel in Ecore</b>
+ </p>
+
+ <p align="justify">
+ The <b><a href="http://combemale.perso.enseeiht.fr/atluc/PetriNet.km3">PetriNet</a></b> metamodel is given in the figure 2. A Petri net (<i>PetriNet</i>) is composed of
+ nodes (<i>Node</i>) that denote places (<i>Place</i>) or transitions (<i>Transition</i>). Nodes are linked together by arcs (<i>Arc</i>).
+ Arcs can be normal ones or read-arcs (<i>ArcKind</i>).
+ The number attached to an arc specifies the number of tokens that are consumed in the source place or produced in the target one
+ (in case of a read-arc, it is only used to check whether the source place contains more tokens than the specified number).
+ Petri nets markings are defined by the <i>tokensNb</i> attributes of places.
+ Finally, we can express a time interval on transitions. A transition can only be started between min and maw time.
+ <br />
+ Beware! Such metamodel allows to build invalid models.
+ For example, one can put a link between two places or two transitions. One solution is to complete the model with OCL constraints to restrict models to valid instances.
+ </p>
+
+ <p align="center">
+ <a href="img/PetriNet.png"><img width="33%" src="img/PetriNet.png" /></a>
+ <br /><br />
+ <b>2. PetriNet metamodel in Ecore</b>
+ </p>
+
+ <p align="justify">
+ <a href="http://www.laas.fr/tina">Tina</a></b> (TIme Petri Net Analyser) is a software environment
+ to edit and analyse Petri nets and temporal nets.
+ The different tools constituting the environment can be used alone or together.
+ Some of these tools will be used in this study:
+ <ul>
+ <li>
+ nd (NetDraw): is an editing tool for automatae and temporal networks,
+ under a textual or graphical form. It integrates a simulator ``step by step'' (graphical or textual)
+ for the temporal networks and allows to call other tools without leaving the editor.
+ </li>
+ <li>
+ tina: this tool builds the state space of a Petri net, temporal or not.
+ Tina can perform classical constructs (marking graphs, covering trees) and also allows abstract state
+ space construction, based on partial order techniques.
+ Tina proposes, for temporal networks, all quotient graph constructions discussed in.
+ </li>
+ <li>
+ selt: usually, it is necessary to check more specific properties than the ones dedicated to general accessibility alone,
+ such as boundedness, deadlocks, pseudo liveness and liveness already checked by tina.
+ The selt tool is a model-checker for formulae of an extension of temporal logic
+ seltl (State/Event LTL) of.
+ In case of non satisfiability, selt is able to build a readable counter-example sequence or in
+ a more compressed form usable by the Tina simulator, in order to execute it step by step.
+ </li>
+ </ul>
+ </p>
+
+ <h5 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;">
+ <a name="transfo"></a>The translation schema from a SimplePDL model into Petri nets</h5>
+
+ <p align="justify">
+ The <b>translation schema</b> that transforms a process model into a Petri nets model is
+ given in the next figures. Each work definition is translated into four places characterising the
+ state (<i>NotStarted</i>, <i>Started</i>,
+ <i>InProgress</i> and <i>Finished</i>) in order to translate each
+ <i>WorkSequence</i> by a <i>read-arc</i> between one source work definition place and the target work definition transition.
+ We can remark that the state <i>Started</i> allows to memorise that one work definiton has already been started.
+
+ We also add five places that will define a local clock. The clock will be in state <i>TooEarly</i> when the workdefinition ends
+ before <i>min_time</i> and in the state <i>TooLate</i> when the work definition ends after <i>max_time</i>.
+
+ The transformation is defined using three ATL rules (see the next listing). The first expresses one
+ work definition in terms of places and transitions. The second translates a work sequence into a
+ read-arc between the adequate place of the source work definition and the
+ appropriate transition of the target work definition. The ATL resolveTemp operation is necessary because multiple places and transitions
+ have been created for each <i>WorkDefinition</i>.
+ Finally the last rule considers the whole process and builds the associated Petri net.
+ </p>
+
+ <p align="center">
+ <a href="img/mapping.png"><img width="45%" src="img/mapping.png" /></a>
+ <br /><br />
+ <a href="img/SimplePDL2PetriNetconceptual.png"><img width="45%" src="img/SimplePDL2PetriNetconceptual.png" /></a>
+ <br /><br />
+ <a href="img/pdl2pn.atl.png"><img src="img/pdl2pn.atl.png" /></a>
+ </p>
+
+ <p align="justify">
+ We illustrate the SimplePDL2Petrinet transformation on simplified meta-models in order to keep the presentation simple. Other elements such as ressources, time and
+ the fact that one activity can be split into multiple sub-activities have been modeled. The next figure shows the translation from one temporal WorkDefinition using
+ resources. The next listing gives rules for consider <i>Resource</i>.
+ </p>
+
+ <p align="center">
+ <a href="img/temporalPN1.png"><img width="50%" src="img/temporalPN1.png" /></a>
+ <br /><br />
+ <a href="img/pdl2pnR.atl.png"><img src="img/pdl2pnR.atl.png" /></a>
+ </p>
+
+ <p align="justify">
+ In order to manipulate the obtained Petri net inside a dedicated tool such as <i>Tina</i>, we have composed the preceding transformation
+ with a query
+ <i>PetriNet2Tina</i> that translates the Petri net as a model of <i>PetriNet</i> into a textual form (.net)
+ conforming to the concrete textual syntax of the <i>Tina</i> tool.
+ </p>
+
+ <p align="center">
+ <a href="img/pn2tina.atl.png"><img src="img/pn2tina.atl.png" /></a>
+ </p>
+
+ <h5 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;"><a name="prop"></a>
+ Properties generation for process model validation</h5>
+
+ <p align="justify">
+ After expressing process models into Petri nets models, we want to <b>check the properties associated to SimplePDL models</b> using the Tina toolkit.
+ The main principle is to generate LTL properties using ATL queries.
+ We generate LTL formulas in textual form.
+ Therefore, we have to be aware of the translation shema from SimplePDL to PetriNet and Tina to ensure the consistency of the properties expression.
+ Working directly on PetriNet level would have require to formalize the LTL metamodel which seems to be irrelevant in such case.
+ <br/>
+ We express below the kind of properties that we target to check in the current use case.
+ </p>
+ <p align="justify">
+ <b>Model consistency verification</b>:
+ When the user elaborates his process model, he describes the constraints that will drive his process.
+ They can be causality relationships, like when a work definition is able to start only if some others are finished.
+ They can express the necessity to be able to use a certain amount of resources or even temporal constraints.
+ Once all such constraints are expressed, the user must be able to check whether his process is satisfiable. In other words, does one execution exists
+ that satisfies all causality constraints while respecting ressource usage and temporal restrictions?
+
+ Model-checking technics allows to reach this goal.
+ A process satisfying all such constraints is valid for us if it can terminates, i.e. it can reach a state where all its work definitions are in their finished state.
+ Other alternatives can be considered. This notion of termination must be defined at the SimplePDL level.
+ The macro-proposition <it>finished</it> is automatically generated during the translation of the SimplePDL model (cf. listing below).
+ </p>
+
+ <p align="center">
+ <a href="img/checkmodel.png"><img src="img/checkmodel.png" /></a>
+ </p>
+
+ <p align="justify">
+ <b>Transformation soundness</b>:
+ Even if the translation is expressed in ATL at an adequate abstraction layer, it is still important to ensure transformation consistency. The resulting
+ Petri net model must be revelant with respect to the SimplePDL specification. But its complexity makes the analysis difficult.
+
+ To facilitate the definition of the ATL translation et to ensure the conformance of the resulting Petri net, we automatically
+ generate a set of LTL formulae which have to be satisfied by the Petri net translation of the initial SimplePDL process model.
+
+ These formulae are able to express that differents states modeled by a single value in the SimplePDL model have to be mutually exclusive in the Petri net one.
+ The following listing gives an example.
+
+ The set of these properties can be seen a <emph>proof obligations</emph>. They are generated during the translation phase and depend on
+ the naming convention used for places and transitions in the SimplePDL2PetriNet mapping.
+ </p>
+
+ <p align="center">
+ <a href="img/checktransfo.png"><img src="img/checktransfo.png" /></a>
+ </p>
+
+ </td>
+ </tr>
+ </table>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;">
+ <a name="relatedUseCases"></a>Related Use Cases
+ </h4>
+ <table>
+ <COLGROUP>
+ <COL width="2%" />
+ <COL width="98%" />
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ <p align="justify">
+ None at the current time.
+ </p>
+ </td>
+ </tr>
+ </table>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;">
+ <a name="references"></a>References
+ </h4>
+
+ <table width="100%">
+
+ <tr valign="top">
+ <td>
+ [1]
+ </td>
+ <td>
+ Combemale, B, Garoche P-L, Crégut, X, Thirioux, X:
+ <em>Towards a Formal Verification of Process Model's Properties -- SimplePDL and TOCL Case Study</em>.
+ In: Proceedings of the 9th International Conference on Enterprise Information Systems (ICEIS), 12-16, June 2007, Funchal, Madeira - Portugal.
+ </td>
+
+ </tr>
+ <tr valign="top">
+ <td>
+ [2]
+ </td>
+ <td>
+ (article in french) Combemale, B, Crégut, X, Berthomieu, B, and Vernadat, F:
+ <em>SimplePDL2Tina : Mise en oeuvre d'une Validation de Modèles de Processus</em>.
+ In: Proceedings of the 3ieme journées sur l'Ingénierie Dirigée par les Modèles (IDM), March 23th, Toulouse, France. 2007.
+ </td>
+
+ </tr>
+ <tr valign="top">
+ <td>
+ <a href="http://www.combemale.fr/wiki/doku.php?id=private:enseignement:metamodeling">[3]</a>
+ </td>
+ <td>
+ (tutorial in french) Pantel, M, Crégut, X, and Combemale, B:
+ <em>La Méta-modélisation et la Transformation de Modèles</em> (2007).
+ </td>
+
+ </tr>
+ </table>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;">
+ <a name="download">Download</a>
+ </h4>
+
+ <table width="100%">
+ <COLGROUP>
+ <COL width="25%">
+ <COL width="75%">
+ </COLGROUP>
+ <tr>
+ <td align="center"><a href="http://www.eclipse.org/atl/atlTransformations/#SimplePDL2Tina"><h3>Complete scenario</h3></a></td>
+ <td>Scenario SimplePDL to Tina available in the ATL transformation zoo (with source files).</td>
+ </tr>
+ <tr>
+ <td align="center"><a href="http://combemale.perso.enseeiht.fr/atluc/pdl.km3"><h3>SimplePDL metamodel</h3></a></td>
+
+ <td>Full SimplePDL metamodel specified in KM3.</td>
+ </tr>
+ <tr>
+ <td align="center"><a href="http://combemale.perso.enseeiht.fr/atluc/PetriNet.km3"><h3>PetriNet metamodel</h3></a></td>
+ <td>Full PetriNet metamodel specified in KM3.</td>
+ </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>Acknowledgement
+ </h4>
+
+ <table width="100%">
+ <COLGROUP>
+ <COL width="2%">
+ <COL width="98%">
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ The present work is being supported by the <a href="http://www.topcased.org/">Topcased project</a>.
+ </td>
+ </tr>
+ </table>
+
+ </div>
+ </div>
+
+ <div id="rightcolumn">
+ <div class="sideitem">
+ <h6>General Information</h6>
+ <ul>
+ <li style="list-style:none">February 2007</li>
+ <li style="list-style:none">By <a href="http://combemale.perso.enseeiht.fr/">Benoit Combemale</a> (IRIT)</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/SoftwareQualityControlToolsInteroperability/img/BugzillaSampleFile.png b/usecases/SoftwareQualityControlToolsInteroperability/img/BugzillaSampleFile.png
new file mode 100644
index 0000000..fa04c8b
--- /dev/null
+++ b/usecases/SoftwareQualityControlToolsInteroperability/img/BugzillaSampleFile.png
Binary files differ
diff --git a/usecases/SoftwareQualityControlToolsInteroperability/img/Excel2BugzillaAndmantisOverview.png b/usecases/SoftwareQualityControlToolsInteroperability/img/Excel2BugzillaAndmantisOverview.png
new file mode 100644
index 0000000..dcf048a
--- /dev/null
+++ b/usecases/SoftwareQualityControlToolsInteroperability/img/Excel2BugzillaAndmantisOverview.png
Binary files differ
diff --git a/usecases/SoftwareQualityControlToolsInteroperability/img/ExcelSampleFile.png b/usecases/SoftwareQualityControlToolsInteroperability/img/ExcelSampleFile.png
new file mode 100644
index 0000000..f79eb1d
--- /dev/null
+++ b/usecases/SoftwareQualityControlToolsInteroperability/img/ExcelSampleFile.png
Binary files differ
diff --git a/usecases/SoftwareQualityControlToolsInteroperability/img/MantisSampleFile.png b/usecases/SoftwareQualityControlToolsInteroperability/img/MantisSampleFile.png
new file mode 100644
index 0000000..8b93b34
--- /dev/null
+++ b/usecases/SoftwareQualityControlToolsInteroperability/img/MantisSampleFile.png
Binary files differ
diff --git a/usecases/SoftwareQualityControlToolsInteroperability/img/modelEngineeringApproachSchema.png b/usecases/SoftwareQualityControlToolsInteroperability/img/modelEngineeringApproachSchema.png
new file mode 100644
index 0000000..857a3b7
--- /dev/null
+++ b/usecases/SoftwareQualityControlToolsInteroperability/img/modelEngineeringApproachSchema.png
Binary files differ
diff --git a/usecases/SoftwareQualityControlToolsInteroperability/index.php b/usecases/SoftwareQualityControlToolsInteroperability/index.php
new file mode 100644
index 0000000..9fca489
--- /dev/null
+++ b/usecases/SoftwareQualityControlToolsInteroperability/index.php
@@ -0,0 +1,249 @@
+<?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 = "ATL Use Case - Software Quality Control Tools Interoperability (Bugzilla, Mantis, Excel)";
+ $pageKeywords = "Tool Interoperability, Software Quality Control, Excel, Bugzilla, Mantis, Bug-Tracking";
+ $pageAuthor = "Freddy Allilaire";
+
+ # End: page-specific settings
+ #
+
+ # Paste your HTML content between the EOHTML markers!
+ $html = <<<EOHTML
+
+ <!-- Main part -->
+ <div id="midcolumn">
+ <h1>$pageTitle</h1>
+
+ <img align="right" src="../../resources/atlLogoSmall.png" valign="top" style="padding-left: 10px;" alt="ATL Logo" />
+ <blockquote>
+ <ul>
+ <li><a href="#keywords"><b>Keywords</b></a></li>
+ <li><a href="#overview"><b>Overview</b></a></li>
+ <li><a href="#relatedUseCases"><b>Related Use Cases</b></a></li>
+ <li><a href="#references"><b>References</b></a></li>
+ <li><a href="#download"><b>Download</b></a></li>
+ <li><a href="#acknowledgement"><b>Acknowledgement</b></a></li>
+ </ul>
+ </blockquote>
+
+ <hr class="clearer" />
+
+ <div id="container>
+ <p align="justify">
+ </p>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;"><a name="keywords"></a>Keywords</h4>
+ <table width="100%">
+ <COLGROUP>
+ <COL width="2%" />
+ <COL width="98%" />
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ <p align="justify">
+ Tool Interoperability,
+ Software Quality Control,
+ Bug-Tracking,
+ <a href="http://office.microsoft.com/excel">Excel</a>,
+ <a href="http://www.bugzilla.org/">Bugzilla</a>,
+ <a href="http://www.mantisbt.org/">Mantis</a>
+ </p>
+ </td>
+ </tr>
+ </table>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;"><a name="overview"></a>Overview</h4>
+
+ <table width="100%">
+ <COLGROUP>
+ <COL width="2%" />
+ <COL width="98%" />
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ <p align="justify">
+ Problems of tools interoperability can be found in various domains. Software quality control is one of these.
+ This use case presents an implementation of bridges between different bug tracking tools like Bugzilla, and Mantis.
+ We also consider that bug tracking information may be handled in a generic tool like Excel.
+ </p>
+ <p align="justify">
+ We take an example of "bug-tracking" in the case of a software product development.
+ Assume that three teams are currently working on the same product at the same time but on different modules of this product.
+ Teams may be geographically distributed, may have different levels of maturity of the used development process, may have different experience for the team members,
+ and may consequently use different tools. The global situation may be described as follows:
+ <ul>
+ <li>
+ Team A is developing the first module by using an Excel workbook with a specific format to track or trace bugs;<br /><br />
+ <div align="center"><a href="img/ExcelSampleFile.png"><img src="img/ExcelSampleFile.png" height="500" /></a></div>
+ <hr />
+ </li>
+ <li>
+ Team B is working on the second module and uses Bugzilla which is a free bug-tracking system;<br /><br />
+ <div align="center"><a href="img/BugzillaSampleFile.png"><img src="img/BugzillaSampleFile.png" height="500" /></a></div>
+ <hr />
+ </li>
+ <li>
+ Team C is developing the third module and uses Mantis Bug Tracker which is another free bug tracking system;<br /><br />
+ <div align="center"><a href="img/MantisSampleFile.png"><img src="img/MantisSampleFile.png" height="500" /></a></div>
+ <hr />
+ </li>
+ </ul>
+ A fourth team (that we name Team D) must integrate the various modules developed by these three teams into a complete software solution. It also has to deal with all
+ the bugs that have been detected but not yet resolved for each module.
+ </p>
+ <p align="justify">
+ The problem is that each team has used a different tool for keeping track of bugs. So in that case, how to succeed in centralizing bug-tracking, i.e. how to be able to
+ interoperate from a tool to another without losing critical information about detected bugs? Furthermore the level of maturity of each team may dynamically evolve, each
+ one learning from the global project. A given team may thus upgrade at some point in time its practices to those used by another one.
+ </p>
+ <p align="justify">
+ The general overview of our approach is presented in the following figure.
+ </p>
+ <p align="center">
+ <img src="img/modelEngineeringApproachSchema.png" />
+ <br /><br />
+ <b>Overview of our model engineering approach to interoperability</b>
+ </p>
+ <p align="justify">
+ In this approach, each different "bug-tracking" tool is described by a metamodel.
+ Each tool's metamodel is linked to others by the "logical" pivot: transformations based on these metamodels to the pivot and from the pivot to the metamodels are implemented.
+ This pivot is also a metamodel. It abstracts a certain number of general concepts about "bug-tracking".
+ </p>
+ <p align="justify">
+ Microsoft Excel, Bugzilla, and Mantis (and a lot of tools in general) do not natively use XMI (the OMG standard for serializing and exchanging models and metamodels).
+ Instead they use a general XML format to import/export data.
+ It is thus necessary to define an XML metamodel in order to be able to inject the content of XML files into models and to extract the content of these
+ models into other XML files.
+ </p>
+ <p align="justify">
+ We use ATL to implement bridges between the different tools which are Microsoft Excel, Bugzilla and Mantis. Several bridges are possible and interesting
+ to implement. We have experimented with "Excel-to-Bugzilla" and "Excel-to-Mantis" bridges for this use case. These bridges are implemented as chains of model
+ transformations. The following figure presents both bridges.
+ </p>
+ <p align="center">
+ <img src="img/Excel2BugzillaAndmantisOverview.png" />
+ <br /><br />
+ <b>"Excel-to-Bugzilla" and "Excel-to-Mantis" Bridges</b>
+ </p>
+ <p align="justify">
+ In fact we do not implement direct bridges between these tools. We use the logical metamodel <b>SoftwareQualityControl</b> as a pivot and therefore
+ every model used in one of the tools is transformed to an intermediary model conforming to the logical pivot.
+ We can see that an Excel file in XML is the entry point of the two bridges. This file has to be injected into an XML model before being transformed into an Excel
+ (SpreadsheetML) model and a SoftwareQualityControl model. Then, this Software-QualityControl model can be transformed into Bugzilla and Mantis models. Finally, these two
+ models have to be transformed into XML models in order to be extracted into well-formed XML documents. These files are the exit points of the two bridges.
+ </p>
+ </td>
+ </tr>
+ </table>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;">
+ <a name="relatedUseCases"></a>Related Use Cases
+ </h4>
+ <table>
+ <COLGROUP>
+ <COL width="2%" />
+ <COL width="98%" />
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ <p align="justify">
+ <a href="http://www.eclipse.org/gmt/modisco/useCases/BugzillaMetrics/">MoDisco Use Case - Bugzilla Metrics</a>
+ </p>
+ </td>
+ </tr>
+ </table>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;">
+ <a name="references"></a>References
+ </h4>
+
+ <table width="100%">
+ <tr valign="top">
+ <td>
+ <a href="http://www.sciences.univ-nantes.fr/lina/atl/bibliography/WiSME05_1">
+ [1]
+ </a>
+ </td>
+ <td>
+ Bezivin, J, Bruneliere, H, Jouault, J, and Kurtev, I:
+ <em> Model Engineering Support for Tool Interoperability</em>.
+ In: Proceedings of the 4th Workshop in Software Model Engineering (WiSME 2005), Montego Bay, Jamaica.
+ </td>
+ </tr>
+ </table>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;">
+ <a name="download">Download</a>
+ </h4>
+
+ <table width="100%">
+ <COLGROUP>
+ <COL width="25%">
+ <COL width="75%">
+ </COLGROUP>
+ <tr>
+ <td align="center"><a href="scenario.php"><h3>Complete scenario</h3></a></td>
+ <td>Scenario available in the ATL transformation zoo (with source files).</td>
+ </tr>
+ <tr>
+ <td align="center"><a href="metamodels.php"><h3>Metamodels</h3></a></td>
+ <td>All the provided metamodels are expressed in the Ecore format and also in the <a href="http://wiki.eclipse.org/index.php/KM3">KM3</a> textual format.</td>
+ </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>Acknowledgement
+ </h4>
+
+ <table width="100%">
+ <COLGROUP>
+ <COL width="2%">
+ <COL width="98%">
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ The present work is being supported by the <a href="http://openembedd.inria.fr/home_html-en?set_language=en&cl=en">OpenEmbeDD project</a>,
+ and the <a href="http://www.usine-logicielle.org">Usine Logicielle project of the System@tic Paris Region Cluster</a>.
+ </td>
+ </tr>
+ </table>
+
+ </div>
+ </div>
+
+ <div id="rightcolumn">
+ <div class="sideitem">
+ <h6>General Information</h6>
+ <ul>
+ <li style="list-style:none">February 2007</li>
+ <li style="list-style:none">By <a href="http://www.sciences.univ-nantes.fr/lina/atl/contrib/allilaire">Freddy Allilaire</a>, <a href="http://www.sciences.univ-nantes.fr/lina/atl/contrib/jouault">Frédéric Jouault</a> (INRIA)</li>
+ <li style="list-style:none"><br />Please, ask your questions on the <a href="news://news.eclipse.org/eclipse.modeling.m2m">M2M newsgroup</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/SoftwareQualityControlToolsInteroperability/metamodels.php b/usecases/SoftwareQualityControlToolsInteroperability/metamodels.php
new file mode 100644
index 0000000..3011b06
--- /dev/null
+++ b/usecases/SoftwareQualityControlToolsInteroperability/metamodels.php
@@ -0,0 +1,129 @@
+<?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-05
+ #
+ # Description: Type your page comments here - these are not sent to the browser
+ #
+ #
+ #****************************************************************************
+
+ #
+ # Begin: page-specific settings. Change these.
+ $pageTitle = "ATL Use Case - Software Quality Control Tools Interoperability (Bugzilla, Mantis, Excel): Used Metamodels";
+ $pageKeywords = "";
+ $pageAuthor = "Freddy Allilaire";
+
+ # End: page-specific settings
+ #
+
+ # Paste your HTML content between the EOHTML markers!
+ $html = <<<EOHTML
+
+ <!-- Main part -->
+ <div id="midcolumn">
+ <h1>$pageTitle</h1>
+
+ <img align="right" src="../../resources/atlLogoSmall.png" valign="top" style="padding-left: 10px;" alt="ATL Logo" />
+ <p>
+ We provide here the links to all the metamodels which have been developped and/or used within this use case.
+ These metamodels are available resources that may be used within other use cases, in other different contexts or for other purposes.
+ Each of them is provided in the Eclipse Ecore standard format and also in the <a href="http://wiki.eclipse.org/index.php/KM3">KM3</a> textual format.
+ </p>
+
+ <hr class="clearer" />
+
+ <div id="container>
+ <table>
+ <COLGROUP>
+ <COL width="2%">
+ <COL width="98%">
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;">Metamodels</h4>
+
+ <table border="1" frame="lhs" width="80%">
+ <COLGROUP>
+ <COL width="50%">
+ <COL width="50%">
+ </COLGROUP>
+ <tr>
+ <td align="center">
+ <b><font size="3"><i>Ecore</i> format</font></b>
+ </td>
+ <td align="center">
+ <b><font size="3"><i>KM3</i> format</font></b>
+ </td>
+ </tr>
+
+ <tr>
+ <td align="center">
+ <a href="http://www.eclipse.org/gmt/am3/zoos/atlantEcoreZoo/#XML">XML</a>
+ </td>
+ <td align="center">
+ <a href="http://www.eclipse.org/gmt/am3/zoos/atlanticZoo/#XML">XML</a>
+ </td>
+ </tr>
+
+ <tr>
+ <td align="center">
+ <a href="http://www.eclipse.org/gmt/am3/zoos/atlantEcoreZoo/#SpreadsheetMLSimplified">MS Office Excel SpreadsheetML</a>
+ </td>
+ <td align="center">
+ <a href="http://www.eclipse.org/gmt/am3/zoos/atlanticZoo/#SpreadsheetMLSimplified">MS Office Excel SpreadsheetML</a>
+ </td>
+ </tr>
+
+ <tr>
+ <td align="center">
+ <a href="http://www.eclipse.org/gmt/am3/zoos/atlantEcoreZoo/#Software%20Quality%20Control">Software Quality Control</a>
+ </td>
+ <td align="center">
+ <a href="http://www.eclipse.org/gmt/am3/zoos/atlanticZoo/#Software%20Quality%20Control">Software Quality Control</a>
+ </td>
+ </tr>
+
+ <tr>
+ <td align="center">
+ <a href="http://www.eclipse.org/gmt/am3/zoos/atlantEcoreZoo/#Bugzilla">Bugzilla</a>
+ </td>
+ <td align="center">
+ <a href="http://www.eclipse.org/gmt/am3/zoos/atlanticZoo/#Bugzilla">Bugzilla</a>
+ </td>
+ </tr>
+
+ <tr>
+ <td align="center">
+ <a href="http://www.eclipse.org/gmt/am3/zoos/atlantEcoreZoo/#Mantis">Mantis</a>
+ </td>
+ <td align="center">
+ <a href="http://www.eclipse.org/gmt/am3/zoos/atlanticZoo/#Mantis">Mantis</a>
+ </td>
+ </tr>
+
+ </table>
+ </td>
+ </tr>
+ </table>
+ </div>
+
+ <hr class="clearer" />
+ <br />
+ <a href="index.php">Back to the "Software Quality Control Tools Interoperability (Bugzilla, Mantis, Excel)" use case main page »</a>
+ <hr class="clearer" />
+ </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/SoftwareQualityControlToolsInteroperability/scenario.php b/usecases/SoftwareQualityControlToolsInteroperability/scenario.php
new file mode 100644
index 0000000..5acb2d2
--- /dev/null
+++ b/usecases/SoftwareQualityControlToolsInteroperability/scenario.php
@@ -0,0 +1,101 @@
+<?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-05
+ #
+ # Description: Type your page comments here - these are not sent to the browser
+ #
+ #
+ #****************************************************************************
+
+ #
+ # Begin: page-specific settings. Change these.
+ $pageTitle = "ATL Use Case - Software Quality Control Tools Interoperability (Bugzilla, Mantis, Excel): Complete Scenario";
+ $pageKeywords = "";
+ $pageAuthor = "Freddy Allilaire";
+
+ # End: page-specific settings
+ #
+
+ # Paste your HTML content between the EOHTML markers!
+ $html = <<<EOHTML
+
+ <!-- Main part -->
+ <div id="midcolumn">
+ <h1>$pageTitle</h1>
+
+ <img align="right" src="../../resources/atlLogoSmall.png" valign="top" style="padding-left: 10px;" alt="ATL Logo" />
+ <p>
+ We provide here the links to the different scenarios which have been used to create this complete use case.
+ These scenarios are available from the <a href="http://www.eclipse.org/atl/atlTransformations/">ATL Transformation Zoo</a>.
+ Each of them may be used within other use cases, in other different contexts or for other purposes.
+ </p>
+
+ <hr class="clearer" />
+
+ <div id="container>
+ <table>
+ <COLGROUP>
+ <COL width="2%">
+ <COL width="98%">
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;">List of scenarios used in this use case</h4>
+
+ <table border="1" frame="lhs" width="80%">
+ <tr>
+ <td align="center">
+ <b><font size="3">ATL Scenario</font></b>
+ </td>
+ </tr>
+
+ <tr>
+ <td align="center">
+ <a href="http://www.eclipse.org/atl/atlTransformations/#MSOfficeExcelInjector">Microsoft Office Excel SpreadsheetML Injector</a>
+ </td>
+ </tr>
+
+ <tr>
+ <td align="center">
+ <a href="http://www.eclipse.org/atl/atlTransformations/#MSOfficeExcel2SoftwareQualityControl">Microsoft Office Excel SpreadsheetML to Software Quality Control</a>
+ </td>
+ </tr>
+
+ <tr>
+ <td align="center">
+ <a href="http://www.eclipse.org/atl/atlTransformations/#SoftwareQualityControl2Bugzilla">Software Quality Control to Bugzilla</a>
+ </td>
+ </tr>
+
+ <tr>
+ <td align="center">
+ <a href="http://www.eclipse.org/atl/atlTransformations/#SoftwareQualityControl2MantisBT">Software Quality Control to Mantis</a>
+ </td>
+ </tr>
+
+ </table>
+ </td>
+ </tr>
+ </table>
+ </div>
+
+ <hr class="clearer" />
+ <br />
+ <a href="index.php">Back to the "Software Quality Control Tools Interoperability (Bugzilla, Mantis, Excel)" use case main page »</a>
+ <hr class="clearer" />
+ </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/Syntax2SBVR2UML/RunningExample-SBVR.png b/usecases/Syntax2SBVR2UML/RunningExample-SBVR.png
new file mode 100644
index 0000000..45b2f61
--- /dev/null
+++ b/usecases/Syntax2SBVR2UML/RunningExample-SBVR.png
Binary files differ
diff --git a/usecases/Syntax2SBVR2UML/RunningExample-Syntax.png b/usecases/Syntax2SBVR2UML/RunningExample-Syntax.png
new file mode 100644
index 0000000..949a5c0
--- /dev/null
+++ b/usecases/Syntax2SBVR2UML/RunningExample-Syntax.png
Binary files differ
diff --git a/usecases/Syntax2SBVR2UML/RunningExample-UML.png b/usecases/Syntax2SBVR2UML/RunningExample-UML.png
new file mode 100644
index 0000000..1a0665c
--- /dev/null
+++ b/usecases/Syntax2SBVR2UML/RunningExample-UML.png
Binary files differ
diff --git a/usecases/Syntax2SBVR2UML/SBVR-LogicalFormulation.png b/usecases/Syntax2SBVR2UML/SBVR-LogicalFormulation.png
new file mode 100644
index 0000000..cfbaf2e
--- /dev/null
+++ b/usecases/Syntax2SBVR2UML/SBVR-LogicalFormulation.png
Binary files differ
diff --git a/usecases/Syntax2SBVR2UML/SBVR-Meaning.PNG b/usecases/Syntax2SBVR2UML/SBVR-Meaning.PNG
new file mode 100644
index 0000000..7fd6475
--- /dev/null
+++ b/usecases/Syntax2SBVR2UML/SBVR-Meaning.PNG
Binary files differ
diff --git a/usecases/Syntax2SBVR2UML/Syntax.png b/usecases/Syntax2SBVR2UML/Syntax.png
new file mode 100644
index 0000000..7d3346b
--- /dev/null
+++ b/usecases/Syntax2SBVR2UML/Syntax.png
Binary files differ
diff --git a/usecases/Syntax2SBVR2UML/index.php b/usecases/Syntax2SBVR2UML/index.php
new file mode 100644
index 0000000..5350651
--- /dev/null
+++ b/usecases/Syntax2SBVR2UML/index.php
@@ -0,0 +1,209 @@
+<?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 = "ATL Use Case - Production of UML class diagrams from syntactical models of english text or SBVR models";
+ $pageKeywords = "UML, SBVR, syntactical analysis, parsing";
+ $pageAuthor = "Mathias Kleiner";
+
+ # End: page-specific settings
+ #
+
+ # Paste your HTML content between the EOHTML markers!
+ $html = <<<EOHTML
+
+ <!-- Main part -->
+ <div id="midcolumn">
+ <h1>$pageTitle</h1>
+
+ <img align="right" src="../../resources/atlLogoSmall.png" valign="top" style="padding-left: 10px;" alt="ATL Logo" />
+ <blockquote>
+ <ul>
+ <li><a href="#keywords"><b>Keywords</b></a></li>
+ <li><a href="#overview"><b>Overview</b></a></li>
+ <li><a href="#relatedUseCases"><b>Related Use Cases</b></a></li>
+ <li><a href="#download"><b>Download</b></a></li>
+ </ul>
+ </blockquote>
+
+ <hr class="clearer" />
+
+ <div>
+ <p align="justify">
+ This work presents a case study of obtaining a UML class diagram from a syntactical analysis of a text using SBVR as an intermediate layer. We show how it is possible, with the help of model engineering, to realize two transformations:
+ from a syntactical model into a SBVR model, and from a SBVR model into a UML model.
+ This work has been done in collaboration between the <a href="http://www.emn.fr/x-info/atlanmod">ATLANMOD team</a>
+ in Nantes and the <a href="http://www.ilog.fr/">ILOG company</a>.
+ </p>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;"><a name="keywords"></a>Keywords</h4>
+ <table width="100%">
+ <COLGROUP>
+ <COL width="2%" />
+ <COL width="98%" />
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ <p align="justify">
+ Syntactical analysis, parsing,
+ <a href="http://www.omg.org/spec/SBVR/1.0/">SBVR</a>,
+ <a href="http://www.omg.org/technology/documents/formal/uml.htm">UML class diagrams</a>.
+ </p>
+ </td>
+ </tr>
+ </table>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;"><a name="overview"></a>Overview</h4>
+
+ <table width="100%">
+ <COLGROUP>
+ <COL width="2%" />
+ <COL width="98%" />
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ <p align="justify">
+ In this usecase, we present a scenario for producing conceptual schemas in UML class diagrams out of a syntactically analyzed english text.
+ The usecase chains two transformations and uses three metamodels (two of them from existing OMG's specifications).
+ The first transformation produces SBVR models from Syntax models, where Syntax is an originally proposed metamodel for capturing syntax, grammatical dependencies and semantics of english sentences.
+ The second transformation produces UML models from SBVR models.
+ Each transformation can be used separately or chained depending on the scenario.
+ These transformations have been successfully used in an application that first generates a syntax model from plain english text using constraint-based parsing techniques.
+ The automatic syntactical analysis is however outside the scope of this usecase. The Syntax models can be either created manually or obtained using any language parsing technique.
+ The packaged Eclipse project contains the three metamodels in KM3 and ECORE format, the two transformations in ATL format, and example models in XMI format.
+ </p>
+ <p align="justify">
+ In the following, we present an overview of the three metamodels, as well as a scenario example through terminal models corresponding to the sentence "Each company sells at least one product". This example is one of the scenarios included in the packaged Eclipse project.
+ </p>
+ <p align="justify">
+ Figure 1 presents an excerpt of the Syntax metamodel. The main class is "Cat", which represents a syntactical category. Categories can be either terminal (i.e with an associated word), or non-terminal (i.e containing other categories, a group of words).
+ The main non-terminal categories are "SentenceCat" (sentences), "NPCat" (noun phrases), "VPCat" (verb phrases).
+ The main terminal categories are "NCat" (nouns), "VCat" (verbs), "DCat" (determiners).
+ Categories are related by grammatical dependencies, such as "subject" from verbs to noun phrases.
+ Categories may also express an SBVR semantic through the "expresses" optional association.
+ </p>
+ <p align="center">
+ <a href="Syntax.png"><img src="Syntax.png" width="600" /></a>
+ <br /><br />
+ <b>Figure 1: Excerpt of the Syntax metamodel</b>
+ </p>
+ <p align="justify">
+ Figure 2 presents a fragment of a Syntax model for the sentence "Each company sells at least one product".
+ </p>
+ <p align="center">
+ <a href="RunningExample-Syntax.png"><img src="RunningExample-Syntax.png" width="600" /></a>
+ <br /><br />
+ <b>Figure 2: Fragment of a Syntax model for our running example</b>
+ </p>
+ <p align="justify">
+ Figures 3 and 4 present an excerpt of the SBVR metamodel, mainly the taxonomy of concepts "Representation", "Meaning" and "LogicalFormulation".
+ </p>
+ <p align="center">
+ <a href="SBVR-Meaning.PNG"><img src="SBVR-Meaning.PNG" width="600" /></a>
+ <br /><br />
+ <b>Figure 3: Excerpt of the SBVR metamodel: meanings</b>
+ </p>
+ <p align="center">
+ <a href="SBVR-LogicalFormulation.png"><img src="SBVR-LogicalFormulation.png" width="600" /></a>
+ <br /><br />
+ <b>Figure 4: Excerpt of the SBVR metamodel: logical formulations</b>
+ </p>
+ <p align="justify">
+ Figure 5 presents a fragment of the SBVR model obtained with the transformation "Syntax2SBVR" from the previously shown Syntax model.
+ </p>
+ <p align="center">
+ <a href="RunningExample-SBVR.png"><img src="RunningExample-SBVR.png" width="600" /></a>
+ <br /><br />
+ <b>Figure 5: Fragment of a SBVR model for our running example</b>
+ </p>
+ <p align="justify">
+ Figure 6 presents a fragment of the UML model obtained with the transformation "SBVR2UML" from the previously shown SBVR model.
+ </p>
+ <p align="center">
+ <a href="RunningExample-UML.png"><img src="RunningExample-UML.png" width="600" /></a>
+ <br /><br />
+ <b>Figure 6: Fragment of a UML model for our running example</b>
+ </p>
+ </td>
+ </tr>
+ </table>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;">
+ <a name="relatedUseCases"></a>Related Use Cases
+ </h4>
+ <table>
+ <COLGROUP>
+ <COL width="2%" />
+ <COL width="98%" />
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ <p align="justify">
+ None at the current time.
+ </p>
+ </td>
+ </tr>
+ </table>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;">
+ <a name="download">Download</a>
+ </h4>
+
+ <table width="100%">
+ <COLGROUP>
+ <COL width="25%">
+ <COL width="75%">
+ </COLGROUP>
+ <tr>
+ <td align="center"><a href="http://www.eclipse.org/atl/atlTransformations/#Syntax2SBVR2UML"><h3>Packaged Eclipse project</h3></a></td>
+ <td>The packaged Eclipse project, available in the ATL transformation zoo (with source files), contains the three metamodels in KM3 and ECORE format, the two ATL transformations, and a set of model samples as XMI files.</td>
+ </tr>
+ </table>
+
+ </div>
+ </div>
+
+ <div id="rightcolumn">
+ <div class="sideitem">
+ <h6>General Information</h6>
+ <ul>
+ <li style="list-style:none">April 2009</li>
+ <li style="list-style:none">
+ By <a href="mailto:mathias.kleiner@inria.fr">Mathias Kleiner</a> (INRIA)
+ </li>
+ <li style="list-style:none"><br />For any information, please contact the author directly.</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/UML2AnyLogic/img/CreateOrderActionProperties.PNG b/usecases/UML2AnyLogic/img/CreateOrderActionProperties.PNG
new file mode 100644
index 0000000..5671fa8
--- /dev/null
+++ b/usecases/UML2AnyLogic/img/CreateOrderActionProperties.PNG
Binary files differ
diff --git a/usecases/UML2AnyLogic/img/OverallTransformationProcess.PNG b/usecases/UML2AnyLogic/img/OverallTransformationProcess.PNG
new file mode 100644
index 0000000..ef9182a
--- /dev/null
+++ b/usecases/UML2AnyLogic/img/OverallTransformationProcess.PNG
Binary files differ
diff --git a/usecases/UML2AnyLogic/img/PizzaOrdering-UML2ActivityDiagram.PNG b/usecases/UML2AnyLogic/img/PizzaOrdering-UML2ActivityDiagram.PNG
new file mode 100644
index 0000000..3578a14
--- /dev/null
+++ b/usecases/UML2AnyLogic/img/PizzaOrdering-UML2ActivityDiagram.PNG
Binary files differ
diff --git a/usecases/UML2AnyLogic/img/RunningAnyLogicSimulation.PNG b/usecases/UML2AnyLogic/img/RunningAnyLogicSimulation.PNG
new file mode 100644
index 0000000..7bee569
--- /dev/null
+++ b/usecases/UML2AnyLogic/img/RunningAnyLogicSimulation.PNG
Binary files differ
diff --git a/usecases/UML2AnyLogic/index.php b/usecases/UML2AnyLogic/index.php
new file mode 100644
index 0000000..ef6d5fe
--- /dev/null
+++ b/usecases/UML2AnyLogic/index.php
@@ -0,0 +1,213 @@
+<?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.
+ $shortTitle = "Model Driven Performance Engineering: From UML/SPT to AnyLogic";
+ $pageTitle = "ATL Use Case - " . $shortTitle;
+ $pageKeywords = "";
+ $pageAuthor = "Hugo Bruneliere";
+
+ # End: page-specific settings
+ #
+
+ # Paste your HTML content between the EOHTML markers!
+ $html = <<<EOHTML
+
+ <!-- Main part -->
+ <div id="midcolumn">
+ <h1>$pageTitle</h1>
+
+ <img align="right" src="../../resources/atlLogoSmall.png" valign="top" style="padding-left: 10px;" alt="ATL Logo" />
+ <blockquote>
+ <ul>
+ <li><a href="#keywords"><b>Keywords</b></a></li>
+ <li><a href="#overview"><b>Overview</b></a></li>
+ <li><a href="#relatedUseCases"><b>Related Use Cases</b></a></li>
+ <li><a href="#download"><b>Download</b></a></li>
+ <li><a href="#acknowledgement"><b>Acknowledgement</b></a></li>
+ </ul>
+ </blockquote>
+
+ <hr class="clearer" />
+
+ <div id="container>
+ <p align="justify">
+ This use case presents a transformation from annotated UML2 activity diagrams to AnyLogic simulation models.
+ </p>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;"><a name="keywords"></a>Keywords</h4>
+ <table width="100%">
+ <COLGROUP>
+ <COL width="2%" />
+ <COL width="98%" />
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ <p align="justify">
+ <a href="http://www.eclipse.org/modeling/mdt/?project=uml2">UML2</a>,
+ Simulation,
+ Model Driven Performance Engineering,
+ SPT
+ </p>
+ </td>
+ </tr>
+ </table>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;"><a name="overview"></a>Overview</h4>
+
+ <table width="100%">
+ <COLGROUP>
+ <COL width="2%" />
+ <COL width="98%" />
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ <p align="justify">
+ In this case study we present a transformation from annotated UML activity diagrams to AnyLogic simulation models.
+ The actions and control flows in activity diagrams are annotated with performance information utilizing the UML profile for schedulability, performance, and timing (SPT).
+ This information is used to generate a simulation model that can be executed by the <a href="http://www.xjtek.com/anylogic">AnyLogic simulation tool</a> from XJ Technologies.
+ Such simulations can help to identify performance issues early in a software design process.
+ </p>
+ <p align="justify">
+ When designing software, system behavior can be modeled using UML by utilizing, for instance, activity diagrams. To lower costs and risks, it is desirable to run analysis on the modeled system before it is actually implemented.<br/>
+ However, in order to execute useful analysis, certain performance information has to be available. For instance, approximations of the time it would take to perform certain actions. Such information could be derived from knowledge and experience.<br/>
+ Annotating performance information on UML models has been standardized in the <a href="http://www.omg.org/docs/formal/03-09-01.pdf">SPT profile</a> and its successor the MARTE profile. In this use case, we use a simplified version of SPT that includes the parts of the specification required here.<br/>
+ As an example, we consider a high level description of an online pizza ordering process illustrated below.
+ </p>
+ <p align="center">
+ <img src="img/PizzaOrdering-UML2ActivityDiagram.PNG" />
+ <br /><br />
+ <b>The pizza ordering process as activity diagram</b>
+ </p>
+ <p align="justify">
+ In the diagram, several elements are stereotyped with the <i>PStep</i> stereotype. It is defined in the SPT profile and identifies one processing step that has performance properties. It defines a set of stereotype attributes that can be used to set concrete performance parameters. The values set for the <i>CreateOrder</i> action are shown below.
+ </p>
+ <p align="center">
+ <img src="img/CreateOrderActionProperties.PNG" />
+ <br /><br />
+ <b>Performance attributes of the CreateOrder action</b>
+ </p>
+ <p align="justify">
+ Two of the properties are set to meaningful values here: the <i>Host Execution Demand</i> and the <i>Repetition</i>.<br/>
+ The <i>Host Execution Demand</i> is set for every action in the diagram. It depicts the time required to perform the action. It is also indicated that the value is a mean (<i>mean</i>) value, which is assumed (<i>asmd</i>).<br/>
+ The <i>Repetition</i> attribute is utilized to set arrival rates. It is set for actions succeeding an initial node.<br/>
+ Not illustrated, but also utilized, is the <i>Probability</i> attribute. It is set on control flows that originate in decision nodes. It depicts the probability that a certain path is chosen by the decision.<br/>
+ Annotated UML activity diagrams act as input to the transformation. The output of the transformation is an AnyLogic simulation model. AnyLogic is a simulation engine that can run simulations to analyze systems and provides visual representation of the running simulation. The latter supports the understanding of problem sources, especially in early system design.<br/>
+ In AnyLogic, one can define libraries of elements that participate in simulations. Instances of these library elements can interact through messages that are passed through ports and connectors. We have created such a library containing elements known from activity diagrams. For these elements, we have defined the simulation semantics and visual representations.<br/>
+ The result of the transformation is a simulation using elements from the activity diagram library, configuring and connecting them according to the information obtained from the input activity diagram. Below, a snapshot of the running simulation is presented.<br/>
+ </p>
+ <p align="center">
+ <img src="img/RunningAnyLogicSimulation.PNG" />
+ <br /><br />
+ <b>Running simulation in AnyLogic</b>
+ </p>
+ <p align="justify">
+ The figure shows the status of a system after a certain running time. Green coloring indicates that an action is currently active. In front of the actions, red bars show the amount of requests waiting for processing. In the figure, one notices the fairly high amount of waiting requests at the <i>PhoneNumberCheck</i> action. This hints at a possible bottleneck in the design.<br/>
+ In order to have an appropriate visual representation in AnyLogic, we not only take the abstract syntax of an activity (i.e., the UML model) but also the concrete syntax (i.e., the UML diagram) as input for the transformation.<br/>
+ As UML modeling tool, we used <a href="http://www.topcased.org">TOPCASED</a>, which stores the concrete syntax of models as diagram interchange models. Thus, the concrete syntax information is technically another model and we therefore have two input models for the transformation: One containing the actual model (conformant to the UML2 metamodel) and one containing the concrete diagram syntax (conformant to TOPCASED diagram interchange metamodel).<br/>
+ The transformation result is a simulation model conforming to a simplified AnyLogic metamodel. Another trivial transformation together with ATL XML extractor is used to transform the model into the proprietary XML format of AnyLogic, which can then be opened, compiled, and run by the simulation engine. The figure below illustrates the transformation process with the models and metamodels involved.
+ </p>
+ <p align="center">
+ <img src="img/OverallTransformationProcess.PNG" width="100%"/>
+ <br /><br />
+ <b>Overall Transformation Process</b>
+ </p>
+ <p align="justify">
+ In order to execute the use case, Eclipse UML2 and TOPCASED should be installed in an Eclipse environment. This will automatically make the UML2 and TOPCASED DI metamodels available to the transformation. Because the TOPCASED DI metamodel introduces some specific primitive types, an extended model handler is required for DI models. It can be found in the download section below and can be installed by putting it into the Eclipse plugin folder. All other metamodels and the example are contained in the scenario package.
+ </p>
+ </td>
+ </tr>
+ </table>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;">
+ <a name="relatedUseCases"></a>Related Use Cases
+ </h4>
+ <table>
+ <COLGROUP>
+ <COL width="2%" />
+ <COL width="98%" />
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ <p align="justify">
+ None at the current time.
+ </p>
+ </td>
+ </tr>
+ </table>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;">
+ <a name="download">Download</a>
+ </h4>
+
+ <table width="100%">
+ <COLGROUP>
+ <COL width="25%">
+ <COL width="75%">
+ </COLGROUP>
+ <tr>
+ <td align="center"><a href="http://www.eclipse.org/atl/atlTransformations/UML2AnyLogic/UML2AnyLogic.zip"><h3>Complete Scenario</h3></a></td>
+ <td>ATL project containing all the resources allowing running the whole transformation scenario</td>
+ </tr>
+ <tr>
+ <td align="center"><a href="http://www.eclipse.org/atl/atlTransformations/UML2AnyLogic/TUDEMFModelHandler.zip"><h3>Extended EMF Model Handler For ATL</h3></a></td>
+ <td>Extended EMF model handler for ATL permitting dealing with non-standard primitive types</td>
+ </tr>
+ <tr>
+ <td align="center"><a href="http://www.eclipse.org/gmt/am3/zoos/atlantEcoreZoo/#AnyLogic"><h3>AnyLogic Metamodel</h3></a></td>
+ <td>Metamodel for creating AnyLogic simulation models</td>
+ </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>Acknowledgement
+ </h4>
+
+ <table width="100%">
+ <COLGROUP>
+ <COL width="2%">
+ <COL width="98%">
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ The present work is being supported by the <a href="http://www.modelplex-ist.org">IST European MODELPLEX project</a> (MODELing solution for comPLEX software systems, FP6-IP 34081).
+ </td>
+ </tr>
+ </table>
+
+ </div>
+ </div>
+
+ <div id="rightcolumn">
+ <div class="sideitem">
+ <h6>General Information</h6>
+ <ul>
+ <li style="list-style:none">January 2008</li>
+ <li style="list-style:none">By <a href="http://jjohannes.de/">Jendrik Johannes</a> (<a href="http://tu-dresden.de/">TU Dresden</a>)</li>
+ <li style="list-style:none"><br />Please, ask your questions on the <a href="news://news.eclipse.org/eclipse.modeling.m2m">M2M newsgroup</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/UML2MOF/img/ATLServices.PNG b/usecases/UML2MOF/img/ATLServices.PNG
new file mode 100644
index 0000000..69edb27
--- /dev/null
+++ b/usecases/UML2MOF/img/ATLServices.PNG
Binary files differ
diff --git a/usecases/UML2MOF/img/ATLServices_small.PNG b/usecases/UML2MOF/img/ATLServices_small.PNG
new file mode 100644
index 0000000..fe90317
--- /dev/null
+++ b/usecases/UML2MOF/img/ATLServices_small.PNG
Binary files differ
diff --git a/usecases/UML2MOF/img/Ecore.PNG b/usecases/UML2MOF/img/Ecore.PNG
new file mode 100644
index 0000000..215cc48
--- /dev/null
+++ b/usecases/UML2MOF/img/Ecore.PNG
Binary files differ
diff --git a/usecases/UML2MOF/img/KM3File.PNG b/usecases/UML2MOF/img/KM3File.PNG
new file mode 100644
index 0000000..d92fba0
--- /dev/null
+++ b/usecases/UML2MOF/img/KM3File.PNG
Binary files differ
diff --git a/usecases/UML2MOF/img/MOF1_4.PNG b/usecases/UML2MOF/img/MOF1_4.PNG
new file mode 100644
index 0000000..c893bab
--- /dev/null
+++ b/usecases/UML2MOF/img/MOF1_4.PNG
Binary files differ
diff --git a/usecases/UML2MOF/img/UMLClassDiagram.PNG b/usecases/UML2MOF/img/UMLClassDiagram.PNG
new file mode 100644
index 0000000..8e0e85e
--- /dev/null
+++ b/usecases/UML2MOF/img/UMLClassDiagram.PNG
Binary files differ
diff --git a/usecases/UML2MOF/img/book-Ecore.PNG b/usecases/UML2MOF/img/book-Ecore.PNG
new file mode 100644
index 0000000..3bb7dfb
--- /dev/null
+++ b/usecases/UML2MOF/img/book-Ecore.PNG
Binary files differ
diff --git a/usecases/UML2MOF/img/completeConfiguration.PNG b/usecases/UML2MOF/img/completeConfiguration.PNG
new file mode 100644
index 0000000..39d35ca
--- /dev/null
+++ b/usecases/UML2MOF/img/completeConfiguration.PNG
Binary files differ
diff --git a/usecases/UML2MOF/img/configurationManager.PNG b/usecases/UML2MOF/img/configurationManager.PNG
new file mode 100644
index 0000000..b2423cf
--- /dev/null
+++ b/usecases/UML2MOF/img/configurationManager.PNG
Binary files differ
diff --git a/usecases/UML2MOF/img/moduleSelection.PNG b/usecases/UML2MOF/img/moduleSelection.PNG
new file mode 100644
index 0000000..f072a21
--- /dev/null
+++ b/usecases/UML2MOF/img/moduleSelection.PNG
Binary files differ
diff --git a/usecases/UML2MOF/img/newConfiguration.PNG b/usecases/UML2MOF/img/newConfiguration.PNG
new file mode 100644
index 0000000..eb52e8e
--- /dev/null
+++ b/usecases/UML2MOF/img/newConfiguration.PNG
Binary files differ
diff --git a/usecases/UML2MOF/img/run.PNG b/usecases/UML2MOF/img/run.PNG
new file mode 100644
index 0000000..51d30fd
--- /dev/null
+++ b/usecases/UML2MOF/img/run.PNG
Binary files differ
diff --git a/usecases/UML2MOF/index.php b/usecases/UML2MOF/index.php
new file mode 100644
index 0000000..101982b
--- /dev/null
+++ b/usecases/UML2MOF/index.php
@@ -0,0 +1,229 @@
+<?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.
+ $shortTitle = "Using a UML modeler to generate metamodels";
+ $pageTitle = "ATL Use Case - " . $shortTitle;
+ $pageKeywords = "";
+ $pageAuthor = "Freddy Allilaire";
+
+ # End: page-specific settings
+ #
+
+ # Paste your HTML content between the EOHTML markers!
+ $html = <<<EOHTML
+
+ <!-- Main part -->
+ <div id="midcolumn">
+ <h1>$pageTitle</h1>
+
+ <img align="right" src="../../resources/atlLogoSmall.png" valign="top" style="padding-left: 10px;" alt="ATL Logo" />
+ <a href="http://www.papyrusuml.org/"><img align="right" src="../../resources/Papyrus_48x48.gif" valign="top" style="padding-left: 10px;" alt="Papyrus" /></a>
+ <blockquote>
+ <ul>
+ <li><a href="#keywords"><b>Keywords</b></a></li>
+ <li><a href="#overview"><b>Overview</b></a></li>
+ <li><a href="#relatedUseCases"><b>Related Use Cases</b></a></li>
+ <li><a href="#download"><b>Download</b></a></li>
+ <li><a href="#acknowledgement"><b>Acknowledgement</b></a></li>
+ </ul>
+ </blockquote>
+
+ <hr class="clearer" />
+
+ <div id="container>
+ <p align="justify">
+ This use case shows how to use and integrate a model transformation service in a UML Modeler to generate metamodels conforming to KM3, MOF 1.4, and Ecore.
+ </p>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;"><a name="keywords"></a>Keywords</h4>
+ <table width="100%">
+ <COLGROUP>
+ <COL width="2%" />
+ <COL width="98%" />
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ <p align="justify">
+ UML Modeler,
+ <a href="http://www.eclipse.org/modeling/mdt/?project=uml2">UML 2</a>,
+ Metamodels,
+ Ecore,
+ MOF 1.4,
+ <a href="http://wiki.eclipse.org/index.php/KM3">KM3</a>
+ </p>
+ </td>
+ </tr>
+ </table>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;"><a name="overview"></a>Overview</h4>
+
+ <table width="100%">
+ <COLGROUP>
+ <COL width="2%" />
+ <COL width="98%" />
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ <p align="justify">
+ This use case presents how the Papyrus UML Modeler could be used to generate metamodels. <a href="http://www.papyrusuml.org/">Papyrus</a> is a dedicated tool
+ for modelling within UML2 developed by <a href="http://www-list.cea.fr/">CEA LIST</a>.
+ This open source tool is based on the Eclipse environment.
+ </p>
+ <p align="justify">
+ <table border="3" width = "100%" cellspacing="0" cellpadding="20">
+ <td align="justify" bgcolor="#b0c8f4">
+ <b>Metamodel definition</b><br /><br />
+ A metamodel is a model that defines the concepts and relationships that may be created in a model.
+ A model always conforms to a metamodel. This relation is called conformance. The conformance relation has a different nature than the representation relation
+ between a model and its system. A metamodel does not represent a model (that could be considered a system), but only the concepts and relationships that may be
+ created. A metamodel conforms to a metametamodel.
+ </td>
+ </table>
+ </p>
+ <p align="justify">
+ The metamodel will be generated from its description done via a UML 2 Class Diagram produced with Papyrus (an open-source graphical modeler tool for UML2 and based on Eclipse).
+ UML 2 Class Diagrams are the mainstay of object-oriented analysis and design. They show the classes of the system, their interrelationships (including
+ inheritance, aggregation, and association), and the operations and attributes of the classes. Class diagrams are used for a wide variety of purposes, including both
+ conceptual/domain modeling and detailed design modeling. The figure below presents an example of UML Class Diagram made with Papyrus.
+ </p>
+ <p align="center">
+ <img src="img/UMLClassDiagram.PNG" />
+ <br /><br />
+ <b>Sample of UML 2 Class Diagram</b>
+ </p>
+ <p align="justify">
+ From a UML Class Diagram, there is the possibility to generate a metamodel in the following formats:
+ <ul>
+ <li>
+ <b><a href="http://wiki.eclipse.org/index.php/KM3">KM3</a></b>: KM3 (Kernel Meta Meta Model) is a neutral language to write metamodels and to define Domain Specific
+ Languages.
+ </li>
+ <li>
+ <b>EMF XMI 2.0, conforming to Ecore</b>: Ecore is the metametamodel used by EMF. The <a href="http://www.eclipse.org/modeling/emf/">EMF</a> project is a modeling
+ framework and code generation facility for building tools and other applications based on a structured data model.
+ </li>
+ <li>
+ <b>MDR XMI 1.2, conforming to MOF 1.4</b>: <a href="http://www.omg.org/mof/">MOF (Meta Object Facility)</a> is an OMG standard enabling to describe metamodels through common semantics.
+ </li>
+ </ul>
+ </p>
+ <p align="justify">
+ To see how to configure and run the "Generate Metamodel" ATL service, please take a look to the <a href="userGuide.php">User Guide</a>.
+ </p>
+ <p align="justify">
+ Each action (e.g. "Generate metamodel in Ecore") will execute a corresponding ATL model transformation (e.g. "UML 2.0 to Ecore"). Both following figures present
+ samples of generated metamodels in <b>EMF XMI 2.0</b> and <b>KM3</b> formats.
+ </p>
+ <div align="center">
+ <table>
+ <tr>
+ <td><img src="img/Ecore.PNG" /></td>
+ <td><img src="img/KM3File.PNG" /></td>
+ </tr>
+ </table>
+ </div>
+ </td>
+ </tr>
+ </table>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;">
+ <a name="relatedUseCases"></a>Related Use Cases
+ </h4>
+ <table>
+ <COLGROUP>
+ <COL width="2%" />
+ <COL width="98%" />
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ <p align="justify">
+ None at the current time.
+ </p>
+ </td>
+ </tr>
+ </table>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;">
+ <a name="download">Download</a>
+ </h4>
+
+ <table width="100%">
+ <COLGROUP>
+ <COL width="25%">
+ <COL width="75%">
+ </COLGROUP>
+ <tr>
+ <td align="center"><a href="http://www.papyrusuml.org/"><img src="../../resources/Papyrus_48x48.gif" /></a></td>
+ <td><a href="http://www.papyrusuml.org/"><b>Papyrus</b></a>, an open-source graphical modeler tool for UML2 and based on Eclipse</a>.</td>
+ </tr>
+ <tr>
+ <td align="center"><a href="http://wiki.eclipse.org/index.php/KM3"><h3>KM3</h3></a></td>
+ <td>KM3 is a neutral language to write metamodels and to define DSL.</td>
+ </tr>
+ <tr>
+ <td align="center"><a href="http://www.papyrusuml.org/scripts/home/publigen/content/templates/show.asp?P=131&L=EN&ITEMID=10#4"><h3>ATL Service</h3></a></td>
+ <td>Papyrus add-in containing the implementation of this use case.</td>
+ </tr>
+ <tr>
+ <td align="center"><h3><a href="userGuide.php">User Guide</a></h3></td>
+ <td>This user guide explains how to configure and launch the ATL service in Papyrus.</td>
+ </tr>
+ <tr>
+ <td align="center"><h3><a href="http://www.eclipse.org/atl/atlTransformations/UML2KM3/UML2KM3.zip">Source code</a></h3></td>
+ <td>Source code of the ATL scenario used in this use case.</td>
+ </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>Acknowledgement
+ </h4>
+
+ <table width="100%">
+ <COLGROUP>
+ <COL width="2%">
+ <COL width="98%">
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ The present work is being supported by the <a href="http://www.usine-logicielle.org">Usine Logicielle project of the System@tic Paris Region Cluster</a>.
+ </td>
+ </tr>
+ </table>
+
+ </div>
+ </div>
+
+ <div id="rightcolumn">
+ <div class="sideitem">
+ <h6>General Information</h6>
+ <ul>
+ <li style="list-style:none">May 2007</li>
+ <li style="list-style:none">By <a href="http://www.sciences.univ-nantes.fr/lina/atl/contrib/allilaire">Freddy Allilaire</a> (INRIA), Rémi Schnekenburger (CEA LIST)</li>
+ <li style="list-style:none"><br />Please, ask your questions on the <a href="news://news.eclipse.org/eclipse.modeling.m2m">M2M newsgroup</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/UML2MOF/userGuide.php b/usecases/UML2MOF/userGuide.php
new file mode 100644
index 0000000..f4f8bff
--- /dev/null
+++ b/usecases/UML2MOF/userGuide.php
@@ -0,0 +1,136 @@
+<?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 = "Using a UML modeler to generate metamodels - User Guide";
+ $pageKeywords = "";
+ $pageAuthor = "Freddy Allilaire";
+
+ # End: page-specific settings
+ #
+
+ # Paste your HTML content between the EOHTML markers!
+ $html = <<<EOHTML
+
+ <!-- Main part -->
+ <div id="midcolumn">
+ <h1>$pageTitle</h1>
+
+ <img align="right" src="../../resources/atlLogoSmall.png" valign="top" style="padding-left: 10px;" alt="ATL Logo" />
+ <a href="http://www.papyrusuml.org/"><img align="right" src="../../resources/Papyrus_48x48.gif" valign="top" style="padding-left: 10px;" alt="Papyrus" /></a>
+
+ <hr class="clearer" />
+
+ <div id="container>
+ <p align="justify">
+ <table border="3" width="100%" cellspacing="0" cellpadding="20">
+ <tr><td align="justify" bgcolor="#b0c8f4">
+ This user guide explains how to configure and launch the <a href="index.php">Using a UML modeler to generate metamodels</a> ATL service in Papyrus.
+ </td></tr>
+ </table>
+ </p>
+
+ <p align="justify">
+ First step is to create a new transformation configuration, using the <b>Run As</b> button.
+ </p>
+ <p align="center">
+ <img src="img/run.PNG" />
+ </p>
+ <p align="center">
+ <img src="img/configurationManager.PNG" />
+ </p>
+ <p align="justify">
+ Thanks to the pop-up menu available on Papyrus transformation, you can create a new transformation configuration. This transformation configuration will contain all
+ necessary parameters for your transformation.
+ </p>
+ <p align="center">
+ <img src="img/newConfiguration.PNG" />
+ </p>
+ <p align="justify">
+ Thanks to the <b>Browse...</b> button in the Module group, the transformation module can be selected against all transformation modules available for Papyrus. In this use case,
+ please select the <b>UML to Ecore</b> module or <b>UML to KM3</b> module .
+ </p>
+ <p align="center">
+ <img src="img/moduleSelection.PNG" />
+ </p>
+ <p align="justify">
+ The next step is to choose the uml file on which the transformation will run. The following window filters the proposed files using their extensions; you can only select
+ uml files.
+ </p>
+ <p align="center">
+ <img src="img/sourceModelSelection.PNG" />
+ </p>
+ <p align="justify">
+ The next step is the selection of the target folder. It is not possible to select a project yet. In fact, Papyrus transformations must be run into a folder (yellow folder
+ icons). This should be fixed in next versions of Papyrus tool. The selected folder will contain the results of the transformation.
+ </p>
+ <p align="center">
+ <img src="img/targetFolderSelection.PNG" />
+ </p>
+ <p align="justify">
+ The following snapshot gives an example of what you should have just before launching the transformation. The transformation is launched using the <b>Run</b> button.
+ </p>
+ <p align="center">
+ <img src="img/completeConfiguration.PNG" />
+ </p>
+ <p align="justify">
+ With this example, this transformation outputs <b>Book.ecore</b> or <b>Book.km3</b> (according to the selected module).
+ </p>
+ <div align="center">
+ <table>
+ <tr>
+ <td><img src="img/Ecore.PNG" /></td>
+ <td><img src="img/KM3File.PNG" /></td>
+ </tr>
+ </table>
+ </div>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;">
+ <a name="acknowledgement"></a>Acknowledgement
+ </h4>
+
+ <table width="100%">
+ <COLGROUP>
+ <COL width="2%">
+ <COL width="98%">
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ The present work is being supported by the <a href="http://www.usine-logicielle.org">Usine Logicielle project of the System@tic Paris Region Cluster</a>.
+ </td>
+ </tr>
+ </table>
+
+ </div>
+ </div>
+
+ <div id="rightcolumn">
+ <div class="sideitem">
+ <h6>General Information</h6>
+ <ul>
+ <li style="list-style:none">May 2007</li>
+ <li style="list-style:none">By <a href="http://www.sciences.univ-nantes.fr/lina/atl/contrib/allilaire">Freddy Allilaire</a> (INRIA), Rémi Schnekenburger (CEA LIST)</li>
+ <li style="list-style:none"><br />Please, ask your questions on the <a href="news://news.eclipse.org/eclipse.modeling.m2m">M2M newsgroup</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/UML2MsProject/img/Sample.png b/usecases/UML2MsProject/img/Sample.png
new file mode 100644
index 0000000..90cdf37
--- /dev/null
+++ b/usecases/UML2MsProject/img/Sample.png
Binary files differ
diff --git a/usecases/UML2MsProject/img/UseCaseOverview.png b/usecases/UML2MsProject/img/UseCaseOverview.png
new file mode 100644
index 0000000..3e4a391
--- /dev/null
+++ b/usecases/UML2MsProject/img/UseCaseOverview.png
Binary files differ
diff --git a/usecases/UML2MsProject/index.php b/usecases/UML2MsProject/index.php
new file mode 100644
index 0000000..619fe46
--- /dev/null
+++ b/usecases/UML2MsProject/index.php
@@ -0,0 +1,201 @@
+<?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.
+ $shortTitle = "From UML Activity Diagram to Project Management Software";
+ $pageTitle = "ATL Use Case - " . $shortTitle;
+ $pageKeywords = "";
+ $pageAuthor = "Freddy Allilaire";
+
+ # End: page-specific settings
+ #
+
+ # Paste your HTML content between the EOHTML markers!
+ $html = <<<EOHTML
+
+ <!-- Main part -->
+ <div id="midcolumn">
+ <h1>$pageTitle</h1>
+
+ <img align="right" src="../../resources/atlLogoSmall.png" valign="top" style="padding-left: 10px;" alt="ATL Logo" />
+ <blockquote>
+ <ul>
+ <li><a href="#keywords"><b>Keywords</b></a></li>
+ <li><a href="#overview"><b>Overview</b></a></li>
+ <li><a href="#relatedUseCases"><b>Related Use Cases</b></a></li>
+ <li><a href="#download"><b>Download</b></a></li>
+ <li><a href="#acknowledgement"><b>Acknowledgement</b></a></li>
+ </ul>
+ </blockquote>
+
+ <hr class="clearer" />
+
+ <div id="container>
+ <p align="justify">
+ This use case shows how to translate between UML Activity Diagrams and MSProject. All transformations code in ATL and metamodels code in KM3 is available from the
+ <a href="http://www.eclipse.org/gmt/am3/zoos/">zoos</a>.
+ </p>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;"><a name="keywords"></a>Keywords</h4>
+ <table width="100%">
+ <COLGROUP>
+ <COL width="2%" />
+ <COL width="98%" />
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ <p align="justify">
+ <a href="http://www.agilemodeling.com/artifacts/activityDiagram.htm">UML Activity Diagrams</a>,
+ <a href="http://office.microsoft.com/project">MsProject</a>,
+ <a href="http://en.wikipedia.org/wiki/Project_management_software">Project Management Software</a>
+ </p>
+ </td>
+ </tr>
+ </table>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;"><a name="overview"></a>Overview</h4>
+
+ <table width="100%">
+ <COLGROUP>
+ <COL width="2%" />
+ <COL width="98%" />
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ <p align="justify">
+ This use case shows the possibility to have interoperability between an UML activity diagram and a project management software like MsProject.
+ </p>
+ <p align="justify">
+ UML Activity Diagrams are typically used for business process modeling, for modeling the logic captured by a single use case or usage scenario, or for modeling the
+ detailed logic of a business rule. Although UML activity diagrams could potentially model the internal logic of a complex operation it would be far better to simply
+ rewrite the operation so that it is simple enough that you don't require an activity diagram. In many ways UML activity diagrams are the object-oriented equivalent of
+ flow charts and data flow diagrams (DFDs) from structured development.
+ </p>
+ <p align="justify">
+ Project management software is a term covering many types of software, including scheduling, resource allocation, collaboration
+ software, communication and documentation systems, which are used to deal with the complexity of large projects.
+ One of the most common tasks is to schedule a series of events, and the complexity of this task can vary considerably depending on how the tool is used.
+ </p>
+ <p align="justify">
+ Microsoft Project is a project management software program developed by Microsoft which is designed to assist project managers in developing plans, assigning resources to
+ tasks, tracking progress, managing budgets and analyzing workloads.
+ </p>
+
+ <p align="justify">
+ The aim of this case study is to generate an MSProject project from a UML Activity Diagram.
+ The overall approach is summarized in the following figure:
+ </p>
+ <p align="center">
+ <img src="img/UseCaseOverview.png" />
+ <br /><br />
+ <b>"$shortTitle" Use Case's Overview</b>
+ </p>
+ <p align="justify">
+ The XML extraction phase was done by using XML projector available from the AM3 and ATL toolkit. The Model-to-Model transformation phase was implemented by using
+ ATL model-to-model transformations. Metamodels was created by using KM3 syntax and toolkit. All the metamodels mentioned in the previous schema (and so used within
+ this use case) are available at the <a href="#download">Download section</a>.
+ </p>
+ <p align="justify">
+ We provide below a set of screenshots showing the different input/output files provided/created with this use case:
+ </p>
+ <p align="center">
+ <img src="img/Sample.png" />
+ <br /><br />
+ <b>Screenshots of the input/outputs of the use case</b>
+ </p>
+ </td>
+ </tr>
+ </table>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;">
+ <a name="relatedUseCases"></a>Related Use Cases
+ </h4>
+ <table>
+ <COLGROUP>
+ <COL width="2%" />
+ <COL width="98%" />
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ <p align="justify">
+ None at the current time.
+ </p>
+ </td>
+ </tr>
+ </table>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;">
+ <a name="download">Download</a>
+ </h4>
+
+ <table width="100%">
+ <COLGROUP>
+ <COL width="25%">
+ <COL width="75%">
+ </COLGROUP>
+ <tr>
+ <td align="center"><a href="http://www.eclipse.org/atl/atlTransformations/#UMLActivityDiagram2MSProject"><h3>Complete scenario</h3></a></td>
+ <td>Scenario available in the ATL transformation zoo (with source files).</td>
+ </tr>
+ <tr>
+ <td align="center"><a href="http://www.eclipse.org/gmt/am3/zoos/atlantMOF_MDRZoo/#UMLDI"><h3>UML Metamodel</h3></a></td>
+ <td>UML metamodel in MDR XMI 1.2, conforming to MOF 1.4.</td>
+ </tr>
+ <tr>
+ <td align="center"><a href="http://www.eclipse.org/gmt/am3/zoos/atlanticZoo/#MSProject"><h3>MsProject Metamodel</h3></a></td>
+ <td>MsProject metamodel is expressed in the <a href="http://wiki.eclipse.org/index.php/KM3">KM3</a> textual format.</td>
+ </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>Acknowledgement
+ </h4>
+
+ <table width="100%">
+ <COLGROUP>
+ <COL width="2%">
+ <COL width="98%">
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ The present work is being supported by the <a href="http://www.usine-logicielle.org">Usine Logicielle project of the System@tic Paris Region Cluster</a>.
+ </td>
+ </tr>
+ </table>
+
+ </div>
+ </div>
+
+ <div id="rightcolumn">
+ <div class="sideitem">
+ <h6>General Information</h6>
+ <ul>
+ <li style="list-style:none">March 2007</li>
+ <li style="list-style:none">By <a href="http://www.sciences.univ-nantes.fr/lina/atl/contrib/allilaire">Freddy Allilaire</a> (INRIA)</li>
+ <li style="list-style:none"><br />Please, ask your questions on the <a href="news://news.eclipse.org/eclipse.modeling.m2m">M2M newsgroup</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/Verifying_UML_profiled_models/SampleProject4Verification.zip b/usecases/Verifying_UML_profiled_models/SampleProject4Verification.zip
new file mode 100644
index 0000000..8b4b338
--- /dev/null
+++ b/usecases/Verifying_UML_profiled_models/SampleProject4Verification.zip
Binary files differ
diff --git a/usecases/Verifying_UML_profiled_models/img/action.PNG b/usecases/Verifying_UML_profiled_models/img/action.PNG
new file mode 100644
index 0000000..c3542bc
--- /dev/null
+++ b/usecases/Verifying_UML_profiled_models/img/action.PNG
Binary files differ
diff --git a/usecases/Verifying_UML_profiled_models/img/completeConfiguration.PNG b/usecases/Verifying_UML_profiled_models/img/completeConfiguration.PNG
new file mode 100644
index 0000000..c44e183
--- /dev/null
+++ b/usecases/Verifying_UML_profiled_models/img/completeConfiguration.PNG
Binary files differ
diff --git a/usecases/Verifying_UML_profiled_models/img/configurationManager.PNG b/usecases/Verifying_UML_profiled_models/img/configurationManager.PNG
new file mode 100644
index 0000000..b2423cf
--- /dev/null
+++ b/usecases/Verifying_UML_profiled_models/img/configurationManager.PNG
Binary files differ
diff --git a/usecases/Verifying_UML_profiled_models/img/errorsReporting.PNG b/usecases/Verifying_UML_profiled_models/img/errorsReporting.PNG
new file mode 100644
index 0000000..620d12a
--- /dev/null
+++ b/usecases/Verifying_UML_profiled_models/img/errorsReporting.PNG
Binary files differ
diff --git a/usecases/Verifying_UML_profiled_models/img/errorsReporting_small.PNG b/usecases/Verifying_UML_profiled_models/img/errorsReporting_small.PNG
new file mode 100644
index 0000000..295a4d0
--- /dev/null
+++ b/usecases/Verifying_UML_profiled_models/img/errorsReporting_small.PNG
Binary files differ
diff --git a/usecases/Verifying_UML_profiled_models/img/moduleSelection.PNG b/usecases/Verifying_UML_profiled_models/img/moduleSelection.PNG
new file mode 100644
index 0000000..b501862
--- /dev/null
+++ b/usecases/Verifying_UML_profiled_models/img/moduleSelection.PNG
Binary files differ
diff --git a/usecases/Verifying_UML_profiled_models/img/newConfiguration.PNG b/usecases/Verifying_UML_profiled_models/img/newConfiguration.PNG
new file mode 100644
index 0000000..b44e829
--- /dev/null
+++ b/usecases/Verifying_UML_profiled_models/img/newConfiguration.PNG
Binary files differ
diff --git a/usecases/Verifying_UML_profiled_models/img/rule1.PNG b/usecases/Verifying_UML_profiled_models/img/rule1.PNG
new file mode 100644
index 0000000..e43addb
--- /dev/null
+++ b/usecases/Verifying_UML_profiled_models/img/rule1.PNG
Binary files differ
diff --git a/usecases/Verifying_UML_profiled_models/img/rule2.PNG b/usecases/Verifying_UML_profiled_models/img/rule2.PNG
new file mode 100644
index 0000000..95bf368
--- /dev/null
+++ b/usecases/Verifying_UML_profiled_models/img/rule2.PNG
Binary files differ
diff --git a/usecases/Verifying_UML_profiled_models/img/run.PNG b/usecases/Verifying_UML_profiled_models/img/run.PNG
new file mode 100644
index 0000000..51d30fd
--- /dev/null
+++ b/usecases/Verifying_UML_profiled_models/img/run.PNG
Binary files differ
diff --git a/usecases/Verifying_UML_profiled_models/img/sampleModel.PNG b/usecases/Verifying_UML_profiled_models/img/sampleModel.PNG
new file mode 100644
index 0000000..fe0375b
--- /dev/null
+++ b/usecases/Verifying_UML_profiled_models/img/sampleModel.PNG
Binary files differ
diff --git a/usecases/Verifying_UML_profiled_models/img/sampleProfile.PNG b/usecases/Verifying_UML_profiled_models/img/sampleProfile.PNG
new file mode 100644
index 0000000..4605019
--- /dev/null
+++ b/usecases/Verifying_UML_profiled_models/img/sampleProfile.PNG
Binary files differ
diff --git a/usecases/Verifying_UML_profiled_models/img/sourceModelSelection.PNG b/usecases/Verifying_UML_profiled_models/img/sourceModelSelection.PNG
new file mode 100644
index 0000000..d910854
--- /dev/null
+++ b/usecases/Verifying_UML_profiled_models/img/sourceModelSelection.PNG
Binary files differ
diff --git a/usecases/Verifying_UML_profiled_models/img/targetFolderSelection.PNG b/usecases/Verifying_UML_profiled_models/img/targetFolderSelection.PNG
new file mode 100644
index 0000000..439176f
--- /dev/null
+++ b/usecases/Verifying_UML_profiled_models/img/targetFolderSelection.PNG
Binary files differ
diff --git a/usecases/Verifying_UML_profiled_models/index.php b/usecases/Verifying_UML_profiled_models/index.php
new file mode 100644
index 0000000..3880aa0
--- /dev/null
+++ b/usecases/Verifying_UML_profiled_models/index.php
@@ -0,0 +1,220 @@
+<?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.
+ $shortTitle = "Verifying UML profiled models";
+ $pageTitle = "ATL Use Case - " . $shortTitle;
+ $pageKeywords = "";
+ $pageAuthor = "Freddy Allilaire";
+
+ # End: page-specific settings
+ #
+
+ # Paste your HTML content between the EOHTML markers!
+ $html = <<<EOHTML
+
+ <!-- Main part -->
+ <div id="midcolumn">
+ <h1>$pageTitle</h1>
+
+ <img align="right" src="../../resources/atlLogoSmall.png" valign="top" style="padding-left: 10px;" alt="ATL Logo" />
+ <a href="http://www.papyrusuml.org/"><img align="right" src="../../resources/Papyrus_48x48.gif" valign="top" style="padding-left: 10px;" alt="Papyrus" /></a>
+ <blockquote>
+ <ul>
+ <li><a href="#keywords"><b>Keywords</b></a></li>
+ <li><a href="#overview"><b>Overview</b></a></li>
+ <li><a href="#relatedUseCases"><b>Related Use Cases</b></a></li>
+ <li><a href="#download"><b>Download</b></a></li>
+ <li><a href="#acknowledgement"><b>Acknowledgement</b></a></li>
+ </ul>
+ </blockquote>
+
+ <hr class="clearer" />
+
+ <div id="container>
+ <p align="justify">
+ This use case shows how to integrate a model transformation service in a UML Modeler to verify a UML profiled model.
+ </p>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;"><a name="keywords"></a>Keywords</h4>
+ <table width="100%">
+ <COLGROUP>
+ <COL width="2%" />
+ <COL width="98%" />
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ <p align="justify">
+ UML Modeler,
+ <a href="http://www.eclipse.org/modeling/mdt/?project=uml2">UML 2</a>,
+ UML Profile,
+ Verification,
+ Naming convention,
+ Error reporting
+ </p>
+ </td>
+ </tr>
+ </table>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;"><a name="overview"></a>Overview</h4>
+
+ <table width="100%">
+ <COLGROUP>
+ <COL width="2%" />
+ <COL width="98%" />
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ <p align="justify">
+ <a href="http://www.papyrusuml.org/">Papyrus</a> is a dedicated tool for UML2 graphical modelling mainly developed by <a href="http://www-list.cea.fr/">CEA LIST</a>.
+ It integrates the ATL engine. This use case shows how the coupling of ATL and Papyrus may allow to verify UML profiled models.
+ </p>
+ <p align="justify">
+ In the context of this use case, a sample UML profile and a sample UML model applying this profile have been modeled with Papyrus. For this UML profiled model, we provide a service that
+ will check if the UML model complies to some conventions. The conventions are defined by the ATL transformation "SampleUMLProfile to Problem".
+ The figures below present the profile and the UML model used here:
+ </p>
+ <div align="center">
+ <table width="100%">
+ <tr valign="top">
+ <td align="center" width="50%">
+ <img src="img/sampleProfile.PNG" />
+ <br /><br />
+ <b>Sample profile</b>
+ </td>
+ <td align="center" width="50%">
+ <img src="img/sampleModel.PNG" />
+ <br /><br />
+ <b>Sample UML model using the Sample profile</b>
+ </td>
+ </tr>
+ </table>
+ </div>
+ <p align="justify">
+ For all the models using the sample profile, we want to check some properties (e.g. naming convention).
+ To do this, we will define an ATL model transformation to check these conventions associated to the Sample profile.
+ If an element of a UML model does not respect a convention, a problem element (e.g. warning, error) will be created.
+ For example, if we want to forbid the value "value1" for the property "myProperty" this could be done by the following ATL code:
+ </p>
+ <p align="justify">
+ <img src="img/rule1.PNG" />
+ </p>
+ <p align="justify">
+ The following ATL rule will verify if all the classes with stereotype MyStereotype have a name starting by 'Sample_'.
+ If not, a warning problem will be created with the following text "Class name should start with Sample_ to respect sample convention".
+ </p>
+ <p align="justify">
+ <img src="img/rule2.PNG" />
+ </p>
+ <p align="justify">
+ To see how to configure and run the "Verification UML Profiled Model" ATL service, please take a look to the <a href="userGuide.php">User Guide</a>.
+ </p>
+ <p align="justify">
+ This resulting model contains all the problems of the UML model.
+ So, if this model is not empty (i.e. there are problems in the UML model) the problems will be displayed in the Eclipse Problems view.
+ </p>
+ <p align="center">
+ <a href="img/errorsReporting.PNG" ><img src="img/errorsReporting_small.PNG" /></a>
+ <br /><br />
+ <b>Result of error reporting</b>
+ </p>
+ </td>
+ </tr>
+ </table>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;">
+ <a name="relatedUseCases"></a>Related Use Cases
+ </h4>
+ <table>
+ <COLGROUP>
+ <COL width="2%" />
+ <COL width="98%" />
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ <p align="justify">
+ None at the current time.
+ </p>
+ </td>
+ </tr>
+ </table>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;">
+ <a name="download">Download</a>
+ </h4>
+
+ <table width="100%">
+ <COLGROUP>
+ <COL width="25%">
+ <COL width="75%">
+ </COLGROUP>
+ <tr>
+ <td align="center"><a href="http://www.papyrusuml.org/"><img src="../../resources/Papyrus_48x48.gif" /></a></td>
+ <td><a href="http://www.papyrusuml.org/"><b>Papyrus</b></a>, an open-source graphical modeler tool for UML2 and based on Eclipse</a>.</td>
+ </tr>
+ <tr>
+ <td align="center"><a href="http://www.papyrusuml.org/scripts/home/publigen/content/templates/show.asp?P=131&L=EN&ITEMID=10#4"><h3>ATL Service</h3></a></td>
+ <td>Papyrus add-in containing the implementation of this use case.</td>
+ </tr>
+ <tr>
+ <td align="center"><h3><a href="userGuide.php">User Guide</a></h3></td>
+ <td>This user guide explains how to configure and launch the ATL service in Papyrus.</td>
+ </tr>
+ <tr>
+ <td align="center"><h3><a href="SampleProject4Verification.zip">Sample Project</a></h3></td>
+ <td>Sample project with a UML profile and a UML model applying this profile to test the implementation of this use case in Papyrus.</td>
+ </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>Acknowledgement
+ </h4>
+
+ <table width="100%">
+ <COLGROUP>
+ <COL width="2%">
+ <COL width="98%">
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ The present work is being supported by the <a href="http://www.usine-logicielle.org">Usine Logicielle project of the System@tic Paris Region Cluster</a>.
+ </td>
+ </tr>
+ </table>
+
+ </div>
+ </div>
+
+ <div id="rightcolumn">
+ <div class="sideitem">
+ <h6>General Information</h6>
+ <ul>
+ <li style="list-style:none">May 2007</li>
+ <li style="list-style:none">By <a href="http://www.sciences.univ-nantes.fr/lina/atl/contrib/allilaire">Freddy Allilaire</a> (INRIA), Rémi Schnekenburger (CEA LIST)</li>
+ <li style="list-style:none"><br />Please, ask your questions on the <a href="news://news.eclipse.org/eclipse.modeling.m2m">M2M newsgroup</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/Verifying_UML_profiled_models/userGuide.php b/usecases/Verifying_UML_profiled_models/userGuide.php
new file mode 100644
index 0000000..a0de64e
--- /dev/null
+++ b/usecases/Verifying_UML_profiled_models/userGuide.php
@@ -0,0 +1,136 @@
+<?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 = "Verifying UML profiled models - User Guide";
+ $pageKeywords = "";
+ $pageAuthor = "Freddy Allilaire";
+
+ # End: page-specific settings
+ #
+
+ # Paste your HTML content between the EOHTML markers!
+ $html = <<<EOHTML
+
+ <!-- Main part -->
+ <div id="midcolumn">
+ <h1>$pageTitle</h1>
+
+ <img align="right" src="../../resources/atlLogoSmall.png" valign="top" style="padding-left: 10px;" alt="ATL Logo" />
+ <a href="http://www.papyrusuml.org/"><img align="right" src="../../resources/Papyrus_48x48.gif" valign="top" style="padding-left: 10px;" alt="Papyrus" /></a>
+
+ <hr class="clearer" />
+
+ <div id="container>
+ <p align="justify">
+ <table border="3" width="100%" cellspacing="0" cellpadding="20">
+ <tr><td align="justify" bgcolor="#b0c8f4">
+ This user guide explains how to configure and launch the <a href="index.php">Verifying UML profiled models</a> ATL service in Papyrus.
+ </td></tr>
+ </table>
+ </p>
+
+ <p align="justify">
+ The following procedure will configure and launch the transformation that validates the model against previously defined rules.
+ </p>
+ <p align="center">
+ <img src="img/run.PNG" />
+ </p>
+ <p align="justify">
+ First step is to create a new transformation configuration, using the <b>Run As</b> button.
+ </p>
+ <p align="center">
+ <img src="img/configurationManager.PNG" />
+ </p>
+ <p align="justify">
+ Thanks to the pop-up menu available on Papyrus transformation, you can create a new transformation configuration. This transformation configuration will contain all
+ necessary parameters for your transformation.
+ </p>
+ <p align="center">
+ <img src="img/newConfiguration.PNG" />
+ </p>
+ <p align="justify">
+ Thanks to the <b>Browse...</b> button in the Module group, the transformation module can be selected against all transformation modules available for Papyrus. In this use case,
+ please select the UML measures module.
+ </p>
+ <p align="center">
+ <img src="img/moduleSelection.PNG" />
+ </p>
+ <p align="justify">
+ The next step is to choose the uml file on which the transformation will run. The following window filters the proposed files using their extensions; you can only select
+ uml files.
+ </p>
+ <p align="center">
+ <img src="img/sourceModelSelection.PNG" />
+ </p>
+ <p align="justify">
+ The next step is the selection of the target folder. It is not possible to select a project yet. In fact, Papyrus transformations must be run into a folder (yellow folder
+ icons). This should be fixed in next versions of Papyrus tool. The selected folder will contain the results of the transformation. In this case, no result is expected, as
+ the markers are directly added to the uml file. Whatever, you have to choose a valid folder.
+ </p>
+ <p align="center">
+ <img src="img/targetFolderSelection.PNG" />
+ </p>
+ <p align="justify">
+ The following snapshot gives an example of what you should have just before launching the transformation. The transformation is launched using the <b>Run</b> button.
+ </p>
+ <p align="center">
+ <img src="img/completeConfiguration.PNG" />
+ </p>
+ <p align="justify">
+ This resulting model contains all the problems of the UML model.
+ So, if this model is not empty (i.e. there are problems in the UML model) the problems will be displayed in the Eclipse Problems view.
+ </p>
+ <p align="center">
+ <a href="img/errorsReporting.PNG" ><img src="img/errorsReporting_small.PNG" /></a>
+ </p>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;">
+ <a name="acknowledgement"></a>Acknowledgement
+ </h4>
+
+ <table width="100%">
+ <COLGROUP>
+ <COL width="2%">
+ <COL width="98%">
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ The present work is being supported by the <a href="http://www.usine-logicielle.org">Usine Logicielle project of the System@tic Paris Region Cluster</a>.
+ </td>
+ </tr>
+ </table>
+
+ </div>
+ </div>
+
+ <div id="rightcolumn">
+ <div class="sideitem">
+ <h6>General Information</h6>
+ <ul>
+ <li style="list-style:none">May 2007</li>
+ <li style="list-style:none">By <a href="http://www.sciences.univ-nantes.fr/lina/atl/contrib/allilaire">Freddy Allilaire</a> (INRIA), Rémi Schnekenburger (CEA LIST)</li>
+ <li style="list-style:none"><br />Please, ask your questions on the <a href="news://news.eclipse.org/eclipse.modeling.m2m">M2M newsgroup</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/VisualRepCodeClone/Simian_sample_Form1.svg b/usecases/VisualRepCodeClone/Simian_sample_Form1.svg
new file mode 100644
index 0000000..5f6f908
--- /dev/null
+++ b/usecases/VisualRepCodeClone/Simian_sample_Form1.svg
@@ -0,0 +1,232 @@
+<?xml version = '1.0' encoding = 'ISO-8859-1' ?>
+<svg xmlns = 'http://www.w3.org/2000/svg' version = '1.1' width = '1000' height = '4280' standalone = 'no'>
+ <g transform = 'translate(0,0)'>
+ <text x = '220' y = '20' font-size = '16' font-family = 'Arial Black'>Code Clone Analysis Result by Simian</text>
+ </g>
+ <g transform = 'translate(0,0)'>
+ <text x = '20' y = '45' font-size = '16' fill = 'blue' font-family = 'Arial'>Clone Group 1</text>
+ <g transform = 'translate(0,0)'>
+ <text x = '25' y = '75' font-size = '12' fill = 'blue' font-family = 'Arial'>E:\Test\simian-2.2.17\bin\CtField.java (Total Lines: 1304)</text>
+ <rect x = '20' y = '80' width = '775' height = '60' fill = 'yellow' rx = '10' ry = '10' stroke-width = '3' stroke = 'blue' opacity = '0.5' title = 'E:\Test\simian-2.2.17\bin\CtField.java'/>
+ <rect x = '243' y = '83' width = '10' height = '54' fill = 'red' opacity = '0.75' title = 'Line 376 to 393 (18 lines)'/>
+ </g>
+ <g transform = 'translate(0,90)'>
+ <text x = '25' y = '75' font-size = '12' fill = 'blue' font-family = 'Arial'>E:\Test\simian-2.2.17\bin\CtBehavior.java (Total Lines: 1022)</text>
+ <rect x = '20' y = '80' width = '607' height = '60' fill = 'yellow' rx = '10' ry = '10' stroke-width = '3' stroke = 'blue' opacity = '0.5' title = 'E:\Test\simian-2.2.17\bin\CtBehavior.java'/>
+ <rect x = '266' y = '83' width = '10' height = '54' fill = 'red' opacity = '0.75' title = 'Line 414 to 431 (18 lines)'/>
+ </g>
+ <rect x = '1' y = '50' width = '998' height = '205' fill = 'none' rx = '10' ry = '10' stroke-width = '2' stroke = 'blue'/>
+ </g>
+ <g transform = 'translate(0,260)'>
+ <text x = '20' y = '45' font-size = '16' fill = 'blue' font-family = 'Arial'>Clone Group 2</text>
+ <g transform = 'translate(0,0)'>
+ <text x = '25' y = '75' font-size = '12' fill = 'blue' font-family = 'Arial'>E:\Test\simian-2.2.17\bin\CtBehavior.java (Total Lines: 1022)</text>
+ <rect x = '20' y = '80' width = '607' height = '60' fill = 'yellow' rx = '10' ry = '10' stroke-width = '3' stroke = 'blue' opacity = '0.5' title = 'E:\Test\simian-2.2.17\bin\CtBehavior.java'/>
+ <rect x = '550' y = '83' width = '4' height = '54' fill = 'red' opacity = '0.75' title = 'Line 891 to 898 (8 lines)'/>
+ </g>
+ <g transform = 'translate(0,90)'>
+ <text x = '25' y = '75' font-size = '12' fill = 'blue' font-family = 'Arial'>E:\Test\simian-2.2.17\bin\CtBehavior.java (Total Lines: 1022)</text>
+ <rect x = '20' y = '80' width = '607' height = '60' fill = 'yellow' rx = '10' ry = '10' stroke-width = '3' stroke = 'blue' opacity = '0.5' title = 'E:\Test\simian-2.2.17\bin\CtBehavior.java'/>
+ <rect x = '371' y = '83' width = '4' height = '54' fill = 'red' opacity = '0.75' title = 'Line 591 to 598 (8 lines)'/>
+ </g>
+ <rect x = '1' y = '50' width = '998' height = '205' fill = 'none' rx = '10' ry = '10' stroke-width = '2' stroke = 'blue'/>
+ </g>
+ <g transform = 'translate(0,520)'>
+ <text x = '20' y = '45' font-size = '16' fill = 'blue' font-family = 'Arial'>Clone Group 3</text>
+ <g transform = 'translate(0,0)'>
+ <text x = '25' y = '75' font-size = '12' fill = 'blue' font-family = 'Arial'>E:\Test\simian-2.2.17\bin\CtClassType.java (Total Lines: 1597)</text>
+ <rect x = '20' y = '80' width = '949' height = '60' fill = 'yellow' rx = '10' ry = '10' stroke-width = '3' stroke = 'blue' opacity = '0.5' title = 'E:\Test\simian-2.2.17\bin\CtClassType.java'/>
+ <rect x = '335' y = '83' width = '4' height = '54' fill = 'red' opacity = '0.75' title = 'Line 531 to 538 (8 lines)'/>
+ </g>
+ <g transform = 'translate(0,90)'>
+ <text x = '25' y = '75' font-size = '12' fill = 'blue' font-family = 'Arial'>E:\Test\simian-2.2.17\bin\CtClassType.java (Total Lines: 1597)</text>
+ <rect x = '20' y = '80' width = '949' height = '60' fill = 'yellow' rx = '10' ry = '10' stroke-width = '3' stroke = 'blue' opacity = '0.5' title = 'E:\Test\simian-2.2.17\bin\CtClassType.java'/>
+ <rect x = '296' y = '83' width = '4' height = '54' fill = 'red' opacity = '0.75' title = 'Line 465 to 472 (8 lines)'/>
+ </g>
+ <rect x = '1' y = '50' width = '998' height = '205' fill = 'none' rx = '10' ry = '10' stroke-width = '2' stroke = 'blue'/>
+ </g>
+ <g transform = 'translate(0,780)'>
+ <text x = '20' y = '45' font-size = '16' fill = 'blue' font-family = 'Arial'>Clone Group 4</text>
+ <g transform = 'translate(0,0)'>
+ <text x = '25' y = '75' font-size = '12' fill = 'blue' font-family = 'Arial'>E:\Test\simian-2.2.17\bin\CtClassType.java (Total Lines: 1597)</text>
+ <rect x = '20' y = '80' width = '949' height = '60' fill = 'yellow' rx = '10' ry = '10' stroke-width = '3' stroke = 'blue' opacity = '0.5' title = 'E:\Test\simian-2.2.17\bin\CtClassType.java'/>
+ <rect x = '606' y = '83' width = '3' height = '54' fill = 'red' opacity = '0.75' title = 'Line 986 to 992 (7 lines)'/>
+ </g>
+ <g transform = 'translate(0,90)'>
+ <text x = '25' y = '75' font-size = '12' fill = 'blue' font-family = 'Arial'>E:\Test\simian-2.2.17\bin\CtClassType.java (Total Lines: 1597)</text>
+ <rect x = '20' y = '80' width = '949' height = '60' fill = 'yellow' rx = '10' ry = '10' stroke-width = '3' stroke = 'blue' opacity = '0.5' title = 'E:\Test\simian-2.2.17\bin\CtClassType.java'/>
+ <rect x = '580' y = '83' width = '3' height = '54' fill = 'red' opacity = '0.75' title = 'Line 943 to 949 (7 lines)'/>
+ </g>
+ <rect x = '1' y = '50' width = '998' height = '205' fill = 'none' rx = '10' ry = '10' stroke-width = '2' stroke = 'blue'/>
+ </g>
+ <g transform = 'translate(0,1040)'>
+ <text x = '20' y = '45' font-size = '16' fill = 'blue' font-family = 'Arial'>Clone Group 5</text>
+ <g transform = 'translate(0,0)'>
+ <text x = '25' y = '75' font-size = '12' fill = 'blue' font-family = 'Arial'>E:\Test\simian-2.2.17\bin\CtConstructor.java (Total Lines: 398)</text>
+ <rect x = '20' y = '80' width = '236' height = '60' fill = 'yellow' rx = '10' ry = '10' stroke-width = '3' stroke = 'blue' opacity = '0.5' title = 'E:\Test\simian-2.2.17\bin\CtConstructor.java'/>
+ <rect x = '179' y = '83' width = '4' height = '54' fill = 'red' opacity = '0.75' title = 'Line 268 to 275 (8 lines)'/>
+ </g>
+ <g transform = 'translate(0,90)'>
+ <text x = '25' y = '75' font-size = '12' fill = 'blue' font-family = 'Arial'>E:\Test\simian-2.2.17\bin\CtBehavior.java (Total Lines: 1022)</text>
+ <rect x = '20' y = '80' width = '607' height = '60' fill = 'yellow' rx = '10' ry = '10' stroke-width = '3' stroke = 'blue' opacity = '0.5' title = 'E:\Test\simian-2.2.17\bin\CtBehavior.java'/>
+ <rect x = '622' y = '83' width = '4' height = '54' fill = 'red' opacity = '0.75' title = 'Line 1012 to 1019 (8 lines)'/>
+ </g>
+ <g transform = 'translate(0,180)'>
+ <text x = '25' y = '75' font-size = '12' fill = 'blue' font-family = 'Arial'>E:\Test\simian-2.2.17\bin\CtBehavior.java (Total Lines: 1022)</text>
+ <rect x = '20' y = '80' width = '607' height = '60' fill = 'yellow' rx = '10' ry = '10' stroke-width = '3' stroke = 'blue' opacity = '0.5' title = 'E:\Test\simian-2.2.17\bin\CtBehavior.java'/>
+ <rect x = '559' y = '83' width = '3' height = '54' fill = 'red' opacity = '0.75' title = 'Line 907 to 913 (7 lines)'/>
+ </g>
+ <g transform = 'translate(0,270)'>
+ <text x = '25' y = '75' font-size = '12' fill = 'blue' font-family = 'Arial'>E:\Test\simian-2.2.17\bin\CtBehavior.java (Total Lines: 1022)</text>
+ <rect x = '20' y = '80' width = '607' height = '60' fill = 'yellow' rx = '10' ry = '10' stroke-width = '3' stroke = 'blue' opacity = '0.5' title = 'E:\Test\simian-2.2.17\bin\CtBehavior.java'/>
+ <rect x = '435' y = '83' width = '4' height = '54' fill = 'red' opacity = '0.75' title = 'Line 699 to 706 (8 lines)'/>
+ </g>
+ <g transform = 'translate(0,360)'>
+ <text x = '25' y = '75' font-size = '12' fill = 'blue' font-family = 'Arial'>E:\Test\simian-2.2.17\bin\CtBehavior.java (Total Lines: 1022)</text>
+ <rect x = '20' y = '80' width = '607' height = '60' fill = 'yellow' rx = '10' ry = '10' stroke-width = '3' stroke = 'blue' opacity = '0.5' title = 'E:\Test\simian-2.2.17\bin\CtBehavior.java'/>
+ <rect x = '379' y = '83' width = '4' height = '54' fill = 'red' opacity = '0.75' title = 'Line 605 to 612 (8 lines)'/>
+ </g>
+ <rect x = '1' y = '50' width = '998' height = '475' fill = 'none' rx = '10' ry = '10' stroke-width = '2' stroke = 'blue'/>
+ </g>
+ <g transform = 'translate(0,1570)'>
+ <text x = '20' y = '45' font-size = '16' fill = 'blue' font-family = 'Arial'>Clone Group 6</text>
+ <g transform = 'translate(0,0)'>
+ <text x = '25' y = '75' font-size = '12' fill = 'blue' font-family = 'Arial'>E:\Test\simian-2.2.17\bin\CtField.java (Total Lines: 1304)</text>
+ <rect x = '20' y = '80' width = '775' height = '60' fill = 'yellow' rx = '10' ry = '10' stroke-width = '3' stroke = 'blue' opacity = '0.5' title = 'E:\Test\simian-2.2.17\bin\CtField.java'/>
+ <rect x = '168' y = '83' width = '10' height = '54' fill = 'red' opacity = '0.75' title = 'Line 250 to 267 (18 lines)'/>
+ </g>
+ <g transform = 'translate(0,90)'>
+ <text x = '25' y = '75' font-size = '12' fill = 'blue' font-family = 'Arial'>E:\Test\simian-2.2.17\bin\CtClassType.java (Total Lines: 1597)</text>
+ <rect x = '20' y = '80' width = '949' height = '60' fill = 'yellow' rx = '10' ry = '10' stroke-width = '3' stroke = 'blue' opacity = '0.5' title = 'E:\Test\simian-2.2.17\bin\CtClassType.java'/>
+ <rect x = '279' y = '83' width = '4' height = '54' fill = 'red' opacity = '0.75' title = 'Line 437 to 445 (9 lines)'/>
+ </g>
+ <g transform = 'translate(0,180)'>
+ <text x = '25' y = '75' font-size = '12' fill = 'blue' font-family = 'Arial'>E:\Test\simian-2.2.17\bin\CtBehavior.java (Total Lines: 1022)</text>
+ <rect x = '20' y = '80' width = '607' height = '60' fill = 'yellow' rx = '10' ry = '10' stroke-width = '3' stroke = 'blue' opacity = '0.5' title = 'E:\Test\simian-2.2.17\bin\CtBehavior.java'/>
+ <rect x = '112' y = '83' width = '10' height = '54' fill = 'red' opacity = '0.75' title = 'Line 155 to 172 (18 lines)'/>
+ </g>
+ <rect x = '1' y = '50' width = '998' height = '295' fill = 'none' rx = '10' ry = '10' stroke-width = '2' stroke = 'blue'/>
+ </g>
+ <g transform = 'translate(0,1920)'>
+ <text x = '20' y = '45' font-size = '16' fill = 'blue' font-family = 'Arial'>Clone Group 7</text>
+ <g transform = 'translate(0,0)'>
+ <text x = '25' y = '75' font-size = '12' fill = 'blue' font-family = 'Arial'>E:\Test\simian-2.2.17\bin\CtClassType.java (Total Lines: 1597)</text>
+ <rect x = '20' y = '80' width = '949' height = '60' fill = 'yellow' rx = '10' ry = '10' stroke-width = '3' stroke = 'blue' opacity = '0.5' title = 'E:\Test\simian-2.2.17\bin\CtClassType.java'/>
+ <rect x = '643' y = '83' width = '3' height = '54' fill = 'red' opacity = '0.75' title = 'Line 1048 to 1054 (7 lines)'/>
+ </g>
+ <g transform = 'translate(0,90)'>
+ <text x = '25' y = '75' font-size = '12' fill = 'blue' font-family = 'Arial'>E:\Test\simian-2.2.17\bin\CtClassType.java (Total Lines: 1597)</text>
+ <rect x = '20' y = '80' width = '949' height = '60' fill = 'yellow' rx = '10' ry = '10' stroke-width = '3' stroke = 'blue' opacity = '0.5' title = 'E:\Test\simian-2.2.17\bin\CtClassType.java'/>
+ <rect x = '627' y = '83' width = '3' height = '54' fill = 'red' opacity = '0.75' title = 'Line 1022 to 1028 (7 lines)'/>
+ </g>
+ <rect x = '1' y = '50' width = '998' height = '205' fill = 'none' rx = '10' ry = '10' stroke-width = '2' stroke = 'blue'/>
+ </g>
+ <g transform = 'translate(0,2180)'>
+ <text x = '20' y = '45' font-size = '16' fill = 'blue' font-family = 'Arial'>Clone Group 8</text>
+ <g transform = 'translate(0,0)'>
+ <text x = '25' y = '75' font-size = '12' fill = 'blue' font-family = 'Arial'>E:\Test\simian-2.2.17\bin\CtClassType.java (Total Lines: 1597)</text>
+ <rect x = '20' y = '80' width = '949' height = '60' fill = 'yellow' rx = '10' ry = '10' stroke-width = '3' stroke = 'blue' opacity = '0.5' title = 'E:\Test\simian-2.2.17\bin\CtClassType.java'/>
+ <rect x = '561' y = '83' width = '4' height = '54' fill = 'red' opacity = '0.75' title = 'Line 910 to 917 (8 lines)'/>
+ </g>
+ <g transform = 'translate(0,90)'>
+ <text x = '25' y = '75' font-size = '12' fill = 'blue' font-family = 'Arial'>E:\Test\simian-2.2.17\bin\CtClassType.java (Total Lines: 1597)</text>
+ <rect x = '20' y = '80' width = '949' height = '60' fill = 'yellow' rx = '10' ry = '10' stroke-width = '3' stroke = 'blue' opacity = '0.5' title = 'E:\Test\simian-2.2.17\bin\CtClassType.java'/>
+ <rect x = '590' y = '83' width = '4' height = '54' fill = 'red' opacity = '0.75' title = 'Line 959 to 966 (8 lines)'/>
+ </g>
+ <rect x = '1' y = '50' width = '998' height = '205' fill = 'none' rx = '10' ry = '10' stroke-width = '2' stroke = 'blue'/>
+ </g>
+ <g transform = 'translate(0,2440)'>
+ <text x = '20' y = '45' font-size = '16' fill = 'blue' font-family = 'Arial'>Clone Group 9</text>
+ <g transform = 'translate(0,0)'>
+ <text x = '25' y = '75' font-size = '12' fill = 'blue' font-family = 'Arial'>E:\Test\simian-2.2.17\bin\CtBehavior.java (Total Lines: 1022)</text>
+ <rect x = '20' y = '80' width = '607' height = '60' fill = 'yellow' rx = '10' ry = '10' stroke-width = '3' stroke = 'blue' opacity = '0.5' title = 'E:\Test\simian-2.2.17\bin\CtBehavior.java'/>
+ <rect x = '378' y = '83' width = '5' height = '54' fill = 'red' opacity = '0.75' title = 'Line 603 to 612 (10 lines)'/>
+ </g>
+ <g transform = 'translate(0,90)'>
+ <text x = '25' y = '75' font-size = '12' fill = 'blue' font-family = 'Arial'>E:\Test\simian-2.2.17\bin\CtBehavior.java (Total Lines: 1022)</text>
+ <rect x = '20' y = '80' width = '607' height = '60' fill = 'yellow' rx = '10' ry = '10' stroke-width = '3' stroke = 'blue' opacity = '0.5' title = 'E:\Test\simian-2.2.17\bin\CtBehavior.java'/>
+ <rect x = '434' y = '83' width = '5' height = '54' fill = 'red' opacity = '0.75' title = 'Line 697 to 706 (10 lines)'/>
+ </g>
+ <g transform = 'translate(0,180)'>
+ <text x = '25' y = '75' font-size = '12' fill = 'blue' font-family = 'Arial'>E:\Test\simian-2.2.17\bin\CtBehavior.java (Total Lines: 1022)</text>
+ <rect x = '20' y = '80' width = '607' height = '60' fill = 'yellow' rx = '10' ry = '10' stroke-width = '3' stroke = 'blue' opacity = '0.5' title = 'E:\Test\simian-2.2.17\bin\CtBehavior.java'/>
+ <rect x = '558' y = '83' width = '4' height = '54' fill = 'red' opacity = '0.75' title = 'Line 905 to 913 (9 lines)'/>
+ </g>
+ <g transform = 'translate(0,270)'>
+ <text x = '25' y = '75' font-size = '12' fill = 'blue' font-family = 'Arial'>E:\Test\simian-2.2.17\bin\CtConstructor.java (Total Lines: 398)</text>
+ <rect x = '20' y = '80' width = '236' height = '60' fill = 'yellow' rx = '10' ry = '10' stroke-width = '3' stroke = 'blue' opacity = '0.5' title = 'E:\Test\simian-2.2.17\bin\CtConstructor.java'/>
+ <rect x = '178' y = '83' width = '5' height = '54' fill = 'red' opacity = '0.75' title = 'Line 266 to 275 (10 lines)'/>
+ </g>
+ <rect x = '1' y = '50' width = '998' height = '385' fill = 'none' rx = '10' ry = '10' stroke-width = '2' stroke = 'blue'/>
+ </g>
+ <g transform = 'translate(0,2880)'>
+ <text x = '20' y = '45' font-size = '16' fill = 'blue' font-family = 'Arial'>Clone Group 10</text>
+ <g transform = 'translate(0,0)'>
+ <text x = '25' y = '75' font-size = '12' fill = 'blue' font-family = 'Arial'>E:\Test\simian-2.2.17\bin\CtClassType.java (Total Lines: 1597)</text>
+ <rect x = '20' y = '80' width = '949' height = '60' fill = 'yellow' rx = '10' ry = '10' stroke-width = '3' stroke = 'blue' opacity = '0.5' title = 'E:\Test\simian-2.2.17\bin\CtClassType.java'/>
+ <rect x = '566' y = '83' width = '4' height = '54' fill = 'red' opacity = '0.75' title = 'Line 919 to 927 (9 lines)'/>
+ </g>
+ <g transform = 'translate(0,90)'>
+ <text x = '25' y = '75' font-size = '12' fill = 'blue' font-family = 'Arial'>E:\Test\simian-2.2.17\bin\CtClassType.java (Total Lines: 1597)</text>
+ <rect x = '20' y = '80' width = '949' height = '60' fill = 'yellow' rx = '10' ry = '10' stroke-width = '3' stroke = 'blue' opacity = '0.5' title = 'E:\Test\simian-2.2.17\bin\CtClassType.java'/>
+ <rect x = '596' y = '83' width = '4' height = '54' fill = 'red' opacity = '0.75' title = 'Line 969 to 977 (9 lines)'/>
+ </g>
+ <rect x = '1' y = '50' width = '998' height = '205' fill = 'none' rx = '10' ry = '10' stroke-width = '2' stroke = 'blue'/>
+ </g>
+ <g transform = 'translate(0,3140)'>
+ <text x = '20' y = '45' font-size = '16' fill = 'blue' font-family = 'Arial'>Clone Group 11</text>
+ <g transform = 'translate(0,0)'>
+ <text x = '25' y = '75' font-size = '12' fill = 'blue' font-family = 'Arial'>E:\Test\simian-2.2.17\bin\CtBehavior.java (Total Lines: 1022)</text>
+ <rect x = '20' y = '80' width = '607' height = '60' fill = 'yellow' rx = '10' ry = '10' stroke-width = '3' stroke = 'blue' opacity = '0.5' title = 'E:\Test\simian-2.2.17\bin\CtBehavior.java'/>
+ <rect x = '112' y = '83' width = '10' height = '54' fill = 'red' opacity = '0.75' title = 'Line 155 to 173 (19 lines)'/>
+ </g>
+ <g transform = 'translate(0,90)'>
+ <text x = '25' y = '75' font-size = '12' fill = 'blue' font-family = 'Arial'>E:\Test\simian-2.2.17\bin\CtField.java (Total Lines: 1304)</text>
+ <rect x = '20' y = '80' width = '775' height = '60' fill = 'yellow' rx = '10' ry = '10' stroke-width = '3' stroke = 'blue' opacity = '0.5' title = 'E:\Test\simian-2.2.17\bin\CtField.java'/>
+ <rect x = '168' y = '83' width = '10' height = '54' fill = 'red' opacity = '0.75' title = 'Line 250 to 268 (19 lines)'/>
+ </g>
+ <rect x = '1' y = '50' width = '998' height = '205' fill = 'none' rx = '10' ry = '10' stroke-width = '2' stroke = 'blue'/>
+ </g>
+ <g transform = 'translate(0,3400)'>
+ <text x = '20' y = '45' font-size = '16' fill = 'blue' font-family = 'Arial'>Clone Group 12</text>
+ <g transform = 'translate(0,0)'>
+ <text x = '25' y = '75' font-size = '12' fill = 'blue' font-family = 'Arial'>E:\Test\simian-2.2.17\bin\CtConstructor.java (Total Lines: 398)</text>
+ <rect x = '20' y = '80' width = '236' height = '60' fill = 'yellow' rx = '10' ry = '10' stroke-width = '3' stroke = 'blue' opacity = '0.5' title = 'E:\Test\simian-2.2.17\bin\CtConstructor.java'/>
+ <rect x = '178' y = '83' width = '9' height = '54' fill = 'red' opacity = '0.75' title = 'Line 266 to 282 (17 lines)'/>
+ </g>
+ <g transform = 'translate(0,90)'>
+ <text x = '25' y = '75' font-size = '12' fill = 'blue' font-family = 'Arial'>E:\Test\simian-2.2.17\bin\CtBehavior.java (Total Lines: 1022)</text>
+ <rect x = '20' y = '80' width = '607' height = '60' fill = 'yellow' rx = '10' ry = '10' stroke-width = '3' stroke = 'blue' opacity = '0.5' title = 'E:\Test\simian-2.2.17\bin\CtBehavior.java'/>
+ <rect x = '558' y = '83' width = '8' height = '54' fill = 'red' opacity = '0.75' title = 'Line 905 to 919 (15 lines)'/>
+ </g>
+ <rect x = '1' y = '50' width = '998' height = '205' fill = 'none' rx = '10' ry = '10' stroke-width = '2' stroke = 'blue'/>
+ </g>
+ <g transform = 'translate(0,3660)'>
+ <text x = '20' y = '45' font-size = '16' fill = 'blue' font-family = 'Arial'>Clone Group 13</text>
+ <g transform = 'translate(0,0)'>
+ <text x = '25' y = '75' font-size = '12' fill = 'blue' font-family = 'Arial'>E:\Test\simian-2.2.17\bin\CtClassType.java (Total Lines: 1597)</text>
+ <rect x = '20' y = '80' width = '949' height = '60' fill = 'yellow' rx = '10' ry = '10' stroke-width = '3' stroke = 'blue' opacity = '0.5' title = 'E:\Test\simian-2.2.17\bin\CtClassType.java'/>
+ <rect x = '757' y = '83' width = '4' height = '54' fill = 'red' opacity = '0.75' title = 'Line 1240 to 1248 (9 lines)'/>
+ </g>
+ <g transform = 'translate(0,90)'>
+ <text x = '25' y = '75' font-size = '12' fill = 'blue' font-family = 'Arial'>E:\Test\simian-2.2.17\bin\CtClassType.java (Total Lines: 1597)</text>
+ <rect x = '20' y = '80' width = '949' height = '60' fill = 'yellow' rx = '10' ry = '10' stroke-width = '3' stroke = 'blue' opacity = '0.5' title = 'E:\Test\simian-2.2.17\bin\CtClassType.java'/>
+ <rect x = '743' y = '83' width = '4' height = '54' fill = 'red' opacity = '0.75' title = 'Line 1217 to 1225 (9 lines)'/>
+ </g>
+ <rect x = '1' y = '50' width = '998' height = '205' fill = 'none' rx = '10' ry = '10' stroke-width = '2' stroke = 'blue'/>
+ </g>
+ <g transform = 'translate(0,3920)'>
+ <text x = '20' y = '45' font-size = '16' fill = 'blue' font-family = 'Arial'>Clone Group 14</text>
+ <g transform = 'translate(0,0)'>
+ <text x = '25' y = '75' font-size = '12' fill = 'blue' font-family = 'Arial'>E:\Test\simian-2.2.17\bin\CtField.java (Total Lines: 1304)</text>
+ <rect x = '20' y = '80' width = '775' height = '60' fill = 'yellow' rx = '10' ry = '10' stroke-width = '3' stroke = 'blue' opacity = '0.5' title = 'E:\Test\simian-2.2.17\bin\CtField.java'/>
+ <rect x = '720' y = '83' width = '12' height = '54' fill = 'red' opacity = '0.75' title = 'Line 1177 to 1198 (22 lines)'/>
+ </g>
+ <g transform = 'translate(0,90)'>
+ <text x = '25' y = '75' font-size = '12' fill = 'blue' font-family = 'Arial'>E:\Test\simian-2.2.17\bin\CtField.java (Total Lines: 1304)</text>
+ <rect x = '20' y = '80' width = '775' height = '60' fill = 'yellow' rx = '10' ry = '10' stroke-width = '3' stroke = 'blue' opacity = '0.5' title = 'E:\Test\simian-2.2.17\bin\CtField.java'/>
+ <rect x = '698' y = '83' width = '12' height = '54' fill = 'red' opacity = '0.75' title = 'Line 1141 to 1162 (22 lines)'/>
+ </g>
+ <rect x = '1' y = '50' width = '998' height = '205' fill = 'none' rx = '10' ry = '10' stroke-width = '2' stroke = 'blue'/>
+ </g>
+</svg>
diff --git a/usecases/VisualRepCodeClone/Simian_sample_Form2.svg b/usecases/VisualRepCodeClone/Simian_sample_Form2.svg
new file mode 100644
index 0000000..e4df2f5
--- /dev/null
+++ b/usecases/VisualRepCodeClone/Simian_sample_Form2.svg
@@ -0,0 +1,116 @@
+<?xml version = '1.0' encoding = 'ISO-8859-1' ?>
+<svg xmlns = 'http://www.w3.org/2000/svg' version = '1.1' width = '1000' height = '460' standalone = 'no'>
+ <g transform = 'translate(0,0)'>
+ <text x = '220' y = '20' font-size = '16' font-family = 'Arial Black'>Code Clone Analysis Result by Simian</text>
+ </g>
+ <g transform = 'translate(0,0)'>
+ <text x = '25' y = '75' font-size = '12' fill = 'blue' font-family = 'Arial'>E:\Test\simian-2.2.17\bin\CtField.java (Total Lines: 1304)</text>
+ <rect x = '20' y = '80' width = '775' height = '60' fill = 'white' rx = '10' ry = '10' stroke-width = '3' stroke = 'brown' opacity = '0.8' title = 'E:\Test\simian-2.2.17\bin\CtField.javaTest Test again'/>
+ <rect x = '243' y = '83' width = '10' height = '54' fill = 'red' rx = '0' ry = '0' opacity = '0.75' title = 'Line 376 to 393 (18 lines)'/>
+ </g>
+ <g transform = 'translate(0,90)'>
+ <text x = '25' y = '75' font-size = '12' fill = 'blue' font-family = 'Arial'>E:\Test\simian-2.2.17\bin\CtBehavior.java (Total Lines: 1022)</text>
+ <rect x = '20' y = '80' width = '607' height = '60' fill = 'white' rx = '10' ry = '10' stroke-width = '3' stroke = 'brown' opacity = '0.8' title = 'E:\Test\simian-2.2.17\bin\CtBehavior.javaTest Test again'/>
+ <rect x = '266' y = '83' width = '10' height = '54' fill = 'red' rx = '0' ry = '0' opacity = '0.75' title = 'Line 414 to 431 (18 lines)'/>
+ </g>
+ <g transform = 'translate(0,90)'>
+ <rect x = '550' y = '83' width = '4' height = '54' fill = 'green' rx = '0' ry = '0' opacity = '0.75' title = 'Line 891 to 898 (8 lines)'/>
+ </g>
+ <g transform = 'translate(0,90)'>
+ <rect x = '371' y = '83' width = '4' height = '54' fill = 'green' rx = '0' ry = '0' opacity = '0.75' title = 'Line 591 to 598 (8 lines)'/>
+ </g>
+ <g transform = 'translate(0,180)'>
+ <text x = '25' y = '75' font-size = '12' fill = 'blue' font-family = 'Arial'>E:\Test\simian-2.2.17\bin\CtClassType.java (Total Lines: 1597)</text>
+ <rect x = '20' y = '80' width = '949' height = '60' fill = 'white' rx = '10' ry = '10' stroke-width = '3' stroke = 'brown' opacity = '0.8' title = 'E:\Test\simian-2.2.17\bin\CtClassType.javaTest Test again'/>
+ <rect x = '335' y = '83' width = '4' height = '54' fill = 'blue' rx = '0' ry = '0' opacity = '0.75' title = 'Line 531 to 538 (8 lines)'/>
+ </g>
+ <g transform = 'translate(0,180)'>
+ <rect x = '296' y = '83' width = '4' height = '54' fill = 'blue' rx = '0' ry = '0' opacity = '0.75' title = 'Line 465 to 472 (8 lines)'/>
+ </g>
+ <g transform = 'translate(0,180)'>
+ <rect x = '606' y = '83' width = '3' height = '54' fill = 'yellow' rx = '0' ry = '0' opacity = '0.75' title = 'Line 986 to 992 (7 lines)'/>
+ </g>
+ <g transform = 'translate(0,180)'>
+ <rect x = '580' y = '83' width = '3' height = '54' fill = 'yellow' rx = '0' ry = '0' opacity = '0.75' title = 'Line 943 to 949 (7 lines)'/>
+ </g>
+ <g transform = 'translate(0,270)'>
+ <text x = '25' y = '75' font-size = '12' fill = 'blue' font-family = 'Arial'>E:\Test\simian-2.2.17\bin\CtConstructor.java (Total Lines: 398)</text>
+ <rect x = '20' y = '80' width = '236' height = '60' fill = 'white' rx = '10' ry = '10' stroke-width = '3' stroke = 'brown' opacity = '0.8' title = 'E:\Test\simian-2.2.17\bin\CtConstructor.javaTest Test again'/>
+ <rect x = '179' y = '83' width = '4' height = '54' fill = 'pink' rx = '0' ry = '0' opacity = '0.75' title = 'Line 268 to 275 (8 lines)'/>
+ </g>
+ <g transform = 'translate(0,90)'>
+ <rect x = '622' y = '83' width = '4' height = '54' fill = 'pink' rx = '0' ry = '0' opacity = '0.75' title = 'Line 1012 to 1019 (8 lines)'/>
+ </g>
+ <g transform = 'translate(0,90)'>
+ <rect x = '559' y = '83' width = '3' height = '54' fill = 'pink' rx = '0' ry = '0' opacity = '0.75' title = 'Line 907 to 913 (7 lines)'/>
+ </g>
+ <g transform = 'translate(0,90)'>
+ <rect x = '435' y = '83' width = '4' height = '54' fill = 'pink' rx = '0' ry = '0' opacity = '0.75' title = 'Line 699 to 706 (8 lines)'/>
+ </g>
+ <g transform = 'translate(0,90)'>
+ <rect x = '379' y = '83' width = '4' height = '54' fill = 'pink' rx = '0' ry = '0' opacity = '0.75' title = 'Line 605 to 612 (8 lines)'/>
+ </g>
+ <g transform = 'translate(0,0)'>
+ <rect x = '168' y = '83' width = '10' height = '54' fill = 'gold' rx = '0' ry = '0' opacity = '0.75' title = 'Line 250 to 267 (18 lines)'/>
+ </g>
+ <g transform = 'translate(0,180)'>
+ <rect x = '279' y = '83' width = '4' height = '54' fill = 'gold' rx = '0' ry = '0' opacity = '0.75' title = 'Line 437 to 445 (9 lines)'/>
+ </g>
+ <g transform = 'translate(0,90)'>
+ <rect x = '112' y = '83' width = '10' height = '54' fill = 'gold' rx = '0' ry = '0' opacity = '0.75' title = 'Line 155 to 172 (18 lines)'/>
+ </g>
+ <g transform = 'translate(0,180)'>
+ <rect x = '643' y = '83' width = '3' height = '54' fill = 'brown' rx = '0' ry = '0' opacity = '0.75' title = 'Line 1048 to 1054 (7 lines)'/>
+ </g>
+ <g transform = 'translate(0,180)'>
+ <rect x = '627' y = '83' width = '3' height = '54' fill = 'brown' rx = '0' ry = '0' opacity = '0.75' title = 'Line 1022 to 1028 (7 lines)'/>
+ </g>
+ <g transform = 'translate(0,180)'>
+ <rect x = '561' y = '83' width = '4' height = '54' fill = 'cyan' rx = '0' ry = '0' opacity = '0.75' title = 'Line 910 to 917 (8 lines)'/>
+ </g>
+ <g transform = 'translate(0,180)'>
+ <rect x = '590' y = '83' width = '4' height = '54' fill = 'cyan' rx = '0' ry = '0' opacity = '0.75' title = 'Line 959 to 966 (8 lines)'/>
+ </g>
+ <g transform = 'translate(0,90)'>
+ <rect x = '378' y = '83' width = '5' height = '54' fill = 'honeydew' rx = '0' ry = '0' opacity = '0.75' title = 'Line 603 to 612 (10 lines)'/>
+ </g>
+ <g transform = 'translate(0,90)'>
+ <rect x = '434' y = '83' width = '5' height = '54' fill = 'honeydew' rx = '0' ry = '0' opacity = '0.75' title = 'Line 697 to 706 (10 lines)'/>
+ </g>
+ <g transform = 'translate(0,90)'>
+ <rect x = '558' y = '83' width = '4' height = '54' fill = 'honeydew' rx = '0' ry = '0' opacity = '0.75' title = 'Line 905 to 913 (9 lines)'/>
+ </g>
+ <g transform = 'translate(0,270)'>
+ <rect x = '178' y = '83' width = '5' height = '54' fill = 'honeydew' rx = '0' ry = '0' opacity = '0.75' title = 'Line 266 to 275 (10 lines)'/>
+ </g>
+ <g transform = 'translate(0,180)'>
+ <rect x = '566' y = '83' width = '4' height = '54' fill = 'lime' rx = '0' ry = '0' opacity = '0.75' title = 'Line 919 to 927 (9 lines)'/>
+ </g>
+ <g transform = 'translate(0,180)'>
+ <rect x = '596' y = '83' width = '4' height = '54' fill = 'lime' rx = '0' ry = '0' opacity = '0.75' title = 'Line 969 to 977 (9 lines)'/>
+ </g>
+ <g transform = 'translate(0,90)'>
+ <rect x = '112' y = '83' width = '10' height = '54' fill = 'purple' rx = '0' ry = '0' opacity = '0.75' title = 'Line 155 to 173 (19 lines)'/>
+ </g>
+ <g transform = 'translate(0,0)'>
+ <rect x = '168' y = '83' width = '10' height = '54' fill = 'purple' rx = '0' ry = '0' opacity = '0.75' title = 'Line 250 to 268 (19 lines)'/>
+ </g>
+ <g transform = 'translate(0,270)'>
+ <rect x = '178' y = '83' width = '9' height = '54' fill = 'sienna' rx = '0' ry = '0' opacity = '0.75' title = 'Line 266 to 282 (17 lines)'/>
+ </g>
+ <g transform = 'translate(0,90)'>
+ <rect x = '558' y = '83' width = '8' height = '54' fill = 'sienna' rx = '0' ry = '0' opacity = '0.75' title = 'Line 905 to 919 (15 lines)'/>
+ </g>
+ <g transform = 'translate(0,180)'>
+ <rect x = '757' y = '83' width = '4' height = '54' fill = 'springgreen' rx = '0' ry = '0' opacity = '0.75' title = 'Line 1240 to 1248 (9 lines)'/>
+ </g>
+ <g transform = 'translate(0,180)'>
+ <rect x = '743' y = '83' width = '4' height = '54' fill = 'springgreen' rx = '0' ry = '0' opacity = '0.75' title = 'Line 1217 to 1225 (9 lines)'/>
+ </g>
+ <g transform = 'translate(0,0)'>
+ <rect x = '720' y = '83' width = '12' height = '54' fill = 'black' rx = '0' ry = '0' opacity = '0.75' title = 'Line 1177 to 1198 (22 lines)'/>
+ </g>
+ <g transform = 'translate(0,0)'>
+ <rect x = '698' y = '83' width = '12' height = '54' fill = 'black' rx = '0' ry = '0' opacity = '0.75' title = 'Line 1141 to 1162 (22 lines)'/>
+ </g>
+</svg>
diff --git a/usecases/VisualRepCodeClone/codeclone2svg.PNG b/usecases/VisualRepCodeClone/codeclone2svg.PNG
new file mode 100644
index 0000000..80786ac
--- /dev/null
+++ b/usecases/VisualRepCodeClone/codeclone2svg.PNG
Binary files differ
diff --git a/usecases/VisualRepCodeClone/example.PNG b/usecases/VisualRepCodeClone/example.PNG
new file mode 100644
index 0000000..5946575
--- /dev/null
+++ b/usecases/VisualRepCodeClone/example.PNG
Binary files differ
diff --git a/usecases/VisualRepCodeClone/example2.PNG b/usecases/VisualRepCodeClone/example2.PNG
new file mode 100644
index 0000000..68b6644
--- /dev/null
+++ b/usecases/VisualRepCodeClone/example2.PNG
Binary files differ
diff --git a/usecases/VisualRepCodeClone/fileinfosrc.PNG b/usecases/VisualRepCodeClone/fileinfosrc.PNG
new file mode 100644
index 0000000..ac677fd
--- /dev/null
+++ b/usecases/VisualRepCodeClone/fileinfosrc.PNG
Binary files differ
diff --git a/usecases/VisualRepCodeClone/fullscenario.PNG b/usecases/VisualRepCodeClone/fullscenario.PNG
new file mode 100644
index 0000000..0cbb447
--- /dev/null
+++ b/usecases/VisualRepCodeClone/fullscenario.PNG
Binary files differ
diff --git a/usecases/VisualRepCodeClone/gdslmetamodel.PNG b/usecases/VisualRepCodeClone/gdslmetamodel.PNG
new file mode 100644
index 0000000..84977c5
--- /dev/null
+++ b/usecases/VisualRepCodeClone/gdslmetamodel.PNG
Binary files differ
diff --git a/usecases/VisualRepCodeClone/index.php b/usecases/VisualRepCodeClone/index.php
new file mode 100644
index 0000000..391e10b
--- /dev/null
+++ b/usecases/VisualRepCodeClone/index.php
@@ -0,0 +1,317 @@
+<?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: Yu Sun, Frédéric Jouault
+ # Date: 2007-12-11
+ #
+ # Description: This is the ATL contribution page for the project: Visual Representation for Code Clone Tools
+ #
+ #
+ #****************************************************************************
+
+ #
+ # Begin: page-specific settings. Change these.
+ $pageTitle = "ATL Use Case - Visual Representation for Code Clone Tools";
+ $pageKeywords = "Code Clone Tools, SVG, XML";
+ $pageAuthor = "Yu Sun";
+
+ # End: page-specific settings
+ #
+
+ # Paste your HTML content between the EOHTML markers!
+ $html = <<<EOHTML
+
+ <!-- Main part -->
+ <div id="midcolumn">
+ <h1>$pageTitle</h1>
+
+ <img align="right" src="../../resources/atlLogoSmall.png" valign="top" style="padding-left: 10px;" alt="ATL Logo" />
+ <blockquote>
+ <ul>
+ <li><a href="#keywords"><b>Keywords</b></a></li>
+ <li><a href="#overview"><b>Overview</b></a></li>
+ <li><a href="#relatedUseCases"><b>Related Use Cases</b></a></li>
+ <li><a href="#references"><b>References</b></a></li>
+ <li><a href="#download"><b>Download</b></a></li>
+ <li><a href="#acknowledgement"><b>Acknowledgement</b></a></li>
+ </ul>
+ </blockquote>
+
+ <hr class="clearer" />
+
+ <div>
+ <p align="justify">
+ The aim of this project is to realize a uniform visual representation for different code clone detection tools.
+ Different analysis results provided by different code clone detection tools can be injected into models. These models will be transformed to a generic Code Clone DSL model,
+ and then into SVG model. Finally, the SVG code can be automatically extracted from SVG model.
+ </p>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;"><a name="keywords"></a>Keywords</h4>
+ <table width="100%">
+ <COLGROUP>
+ <COL width="2%" />
+ <COL width="98%" />
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ <p align="justify">
+ <a href="http://sel.ics.es.osaka-u.ac.jp/cdtools/index-e.html">Code Clone</a>,
+ <a href="http://en.wikipedia.org/wiki/Scalable_Vector_Graphics">SVG</a>,
+ <a href="http://en.wikipedia.org/wiki/Xml">XML</a>.
+ </p>
+ </td>
+ </tr>
+ </table>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;"><a name="overview"></a>Overview</h4>
+
+ <table width="100%">
+ <COLGROUP>
+ <COL width="2%" />
+ <COL width="98%" />
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ <p align="justify">
+ A number of code clone detection tools have been developed to aid the detection of code clones in sources files. However, most of the tools ouput the analysis results in different formats,
+ and nearly all of them are based on text, which makes it difficult to compare and incorporate these results.
+ In this work, we first difined specific DSLs for different code clone detection tools (Simian, SimScan, CloneDr) and a generic DSL for code clone.
+ Then, specific DSL models can be transformed to the generic DSL for code clone, which will be continuely transformed to SVG model and finally generate the SVG code.
+ </p>
+ <p align="justify">
+ Code clone detection and SVG(two-dimensional graphics and graphical applications in XML) are the two main domains in this project.
+ </p>
+ <p align="justify">
+ In this use case, <a href="http://wiki.eclipse.org/AMMA">AMMA</a> and three of its core DSLs:
+ <a href="http://wiki.eclipse.org/KM3">KM3</a>, <a href="http://wiki.eclipse.org/ATL">ATL</a>, and <a href="http://wiki.eclipse.org/TCS">TCS</a> will be used.
+ AMMA is built on a model-based vision of DSLs. AMMA provides a set of core DSLs that may be used to specify new DSLs.
+ </p>
+ <p align="justify">
+ <b>Code Clone Detection Tools</b> can be used to analyze the source programs and find the same or similar parts in these programs. A text result is often generated
+ after the analysis process, which reports the location of the code clones and other related information such as the length of clones, and similarity, etc.
+ Three tools have been supported by our work. They are <a href="http://www.redhillconsulting.com.au/products/simian/index.html">Simian</a>, <a href="http://www.blue-edge.bg/download.html">SimScan</a>, and <a href="http://www.semdesigns.com/Products/Clone/">CloneDr</a>. The following is is an excerpt of the result outputed by Simian.
+ </p>
+ <p align="center">
+ <img src="simiansrc.PNG" />
+ <br /><br />
+ <b>Code clone analysis result by Simian</b>
+ </p>
+
+ <p align="justify">
+ The output contains some clone groups. In each group, the specific locations of the clones in each file are given.
+ The abstract syntax is specified in KM3. The following figure is an excerpt of the Simian metamodel.
+ </p>
+ <p align="center">
+ <img src="simianmetamodel.PNG" />
+ <br /><br />
+ <b>Simian metamodel excerpt</b>
+ </p>
+ <p align="justify">
+ Concrete syntax of Simian has been implemented in TCS. A grammar is automatically derived from both the KM3 metamodel and the TCS model to parse Simian output file into Simian models.
+ </p>
+ <p align="justify">
+ <b>FileInfo DSL</b> is defined to record the total number of lines in each source file. This number is not available in the output result, but necessary for the visual representation.
+ So we defined such a domain and make it as a part of the input together with Simian. As for Simian, the metamodel of FileInfo is defined by KM3, and the concrete syntax is defined by TCS.
+ </p>
+ <p align="center">
+ <img src="fileinfosrc.PNG" />
+ <br /><br />
+ <b>FileInfo source excerpt</b>
+ </p>
+ <p align="justify">
+ <b>Generic DSL for Code Clone</b> is the uniform model to which specific DSL models can be transformed. Most of the concepts in this DSL are very similiar with the ones in specific DSLs,
+ because they are in the same domain. The following is an excerpt of the generic DSL metamodel.
+ </p>
+ <p align="center">
+ <img src="gdslmetamodel.PNG" />
+ <br /><br />
+ <b>Generic DSL for code clone metamodel excerpt</b>
+ </p>
+ <p align="justify">
+ A transformation from specific DSL model to generic DSL model can be implemented by Simian2CodeClone.atl.
+ </p>
+ <p align="center">
+ <img src="simian2codeclone.PNG" />
+ <br /><br />
+ <b>Simian to CodeClone transformation excerpt, written in ATL</b>
+ </p>
+ <p align="justify">
+ Then, after defining SVG and XML metamodels in KM3, a second transformation from generic Code Clone DSL to SVG can be completed.
+ </p>
+ <p align="center">
+ <img src="codeclone2svg.PNG"/>
+ <br /><br />
+ <b>Generic DSL for Code Clone to SVG transformation excerpt, written in ATL</b>
+ </p>
+ <p align="justify">
+ Finally, the SVG model is transformed to XML model by SVG2XML.atl so that the SVG code can be extracted automatically. The following is an excerpt of the generated SVG code.
+ </p>
+ <p align="center">
+ <img src="svgcode.PNG"/>
+ <br /><br />
+ <b>Generated SVG code excerpt</b>
+ </p>
+ <p align="justify">
+ And two kinds of visual representations are shown in the following.
+ </p>
+ <p align="center">
+ <a href="Simian_sample_Form1.svg"><img src="example.PNG"/></a>
+ <br /><br />
+ <b>Visual representation Form 1</b>
+ </p>
+ <p align="center">
+ <a href="Simian_sample_Form2.svg"><img src="example2.PNG"/></a>
+ <br /><br />
+ <b>Visual representation Form 2</b>
+ </p>
+
+ <p align="justify">
+ The following picture better demonstrates the full scenario of this project.
+ </p>
+ <p align="center">
+ <a href="fullscenario.PNG"><img src="fullscenario.PNG" width="700"/></a>
+ <br />
+ <b>Full transformation scenario</b>
+ </p>
+
+
+ </td>
+ </tr>
+ </table>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;">
+ <a name="relatedUseCases"></a>Related Use Cases
+ </h4>
+ <table>
+ <COLGROUP>
+ <COL width="2%" />
+ <COL width="98%" />
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ <p align="justify">
+ None at the current time.
+ </p>
+ </td>
+ </tr>
+ </table>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;">
+ <a name="references"></a>References
+ </h4>
+
+ <table width="100%">
+ <tr valign="top">
+ <td>
+ <a href="http://www.sciences.univ-nantes.fr/lina/atl/www/papers/DSLBuildingFrameworks_PRELIMINARY_VERSION.pdf">
+ [1]
+ </a>
+ </td>
+ <td>
+ Kurtev, I, Bézivin, J, Jouault, F, and Valduriez, P :
+ <em>Model-based DSL Frameworks</em>.
+ In: Companion to the 21st Annual ACM SIGPLAN Conference on Object-Oriented Programming, Systems, Languages, and Applications, OOPSLA 2006, October 22-26, 2006, Portland, OR, USA. ACM, pages 602--616. 2006.
+ </td>
+ </tr>
+ <tr valign="top">
+ <td>
+ <a href="http://www.sciences.univ-nantes.fr/lina/atl/www/papers/KM3-FMOODS06.pdf">
+ [2]
+ </a>
+ </td>
+ <td>
+ Jouault, F, and Bézivin, J :
+ <em>KM3: a DSL for Metamodel Specification</em>,
+ In: Proceedings of 8th IFIP International Conference on Formal Methods for Open Object-Based Distributed Systems, LNCS 4037, Bologna, Italy, pages 171--185.
+ </td>
+ </tr>
+ <tr valign="top">
+ <td>
+ <a href="http://sosym.dcs.kcl.ac.uk/events/mtip/submissions/jouault_kurtev__transforming_models_with_atl.pdf">
+ [3]
+ </a>
+ </td>
+ <td>
+ Jouault, F, and Kurtev, I :
+ <em>Transforming Models with ATL</em>,
+ In: Proceedings of the Model Transformations in Practice Workshop at MoDELS 2005, Montego Bay, Jamaica.
+ </td>
+ </tr>
+ <tr valign="top">
+ <td>
+ <a href="http://www.sciences.univ-nantes.fr/lina/atl/www/papers/TCS_PRELIMINARY_VERSION.pdf">
+ [4]
+ </a>
+ </td>
+ <td>
+ Jouault, F, Bézivin, J, and Kurtev, I :
+ <em>TCS: a DSL for the Specification of Textual Concrete Syntaxes in Model Engineering</em>,
+ In: GPCE'06: Proceedings of the fifth international conference on Generative programming and Component Engineering, Portland, Oregon, USA, pages 249--254. 2006.
+ </td>
+ </tr>
+
+ </table>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;">
+ <a name="download">Download</a>
+ </h4>
+
+ <table width="100%">
+ <COLGROUP>
+ <COL width="25%">
+ <COL width="75%">
+ </COLGROUP>
+ <tr>
+ <td align="center"><a href="http://www.eclipse.org/atl/atlTransformations/#CodeCloneTools2SVG"><h3>Complete scenario</h3></a></td>
+ <td>Scenario Code Clone to SVG available in the ATL transformation zoo (with source files).</td>
+ </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>Acknowledgement
+ </h4>
+
+ <table width="100%">
+ <COLGROUP>
+ <COL width="2%">
+ <COL width="98%">
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ We want to thank my adviser <a href="http://www.gray-area.org">Dr. Jeff Gray</a>.
+ He offered the precious chance and great encouragement for us to do the research and project in this area. Also, we really appreciate our colleague <a href="http://www.cis.uab.edu/tairasr/">Robert Tairas</a>.
+ He is doing his Ph.D research in the area of code clone, and he provided indispensable resources of code clone tools and related samples.
+ The present work is being partially supported by the <a href="http://openembedd.inria.fr/home_html-en?set_language=en&cl=en" title="OpenEmbeDD project">OpenEmbeDD project</a>.
+ </td>
+ </tr>
+ </table>
+
+ </div>
+ </div>
+
+ <div id="rightcolumn">
+ <div class="sideitem">
+ <h6>General Information</h6>
+ <ul>
+ <li style="list-style:none">December 2007</li>
+ <li style="list-style:none">
+ By <a href="http://www.cis.uab.edu/yusun">Yu Sun</a>, <a href="http://www.sciences.univ-nantes.fr/lina/atl/contrib/jouault">Frédéric Jouault</a>
+ </li>
+ <li style="list-style:none"><br />Please, ask your questions on the <a href="news://news.eclipse.org/eclipse.modeling.m2m">M2M newsgroup</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/VisualRepCodeClone/simian2codeclone.PNG b/usecases/VisualRepCodeClone/simian2codeclone.PNG
new file mode 100644
index 0000000..cfce4f8
--- /dev/null
+++ b/usecases/VisualRepCodeClone/simian2codeclone.PNG
Binary files differ
diff --git a/usecases/VisualRepCodeClone/simianmetamodel.PNG b/usecases/VisualRepCodeClone/simianmetamodel.PNG
new file mode 100644
index 0000000..f8fc12b
--- /dev/null
+++ b/usecases/VisualRepCodeClone/simianmetamodel.PNG
Binary files differ
diff --git a/usecases/VisualRepCodeClone/simiansrc.PNG b/usecases/VisualRepCodeClone/simiansrc.PNG
new file mode 100644
index 0000000..88f3772
--- /dev/null
+++ b/usecases/VisualRepCodeClone/simiansrc.PNG
Binary files differ
diff --git a/usecases/VisualRepCodeClone/svgcode.PNG b/usecases/VisualRepCodeClone/svgcode.PNG
new file mode 100644
index 0000000..0319563
--- /dev/null
+++ b/usecases/VisualRepCodeClone/svgcode.PNG
Binary files differ
diff --git a/usecases/WebSyndicationInteroperability/img/Sample.png b/usecases/WebSyndicationInteroperability/img/Sample.png
new file mode 100644
index 0000000..f6dee9f
--- /dev/null
+++ b/usecases/WebSyndicationInteroperability/img/Sample.png
Binary files differ
diff --git a/usecases/WebSyndicationInteroperability/img/UseCaseOverview.png b/usecases/WebSyndicationInteroperability/img/UseCaseOverview.png
new file mode 100644
index 0000000..7402c32
--- /dev/null
+++ b/usecases/WebSyndicationInteroperability/img/UseCaseOverview.png
Binary files differ
diff --git a/usecases/WebSyndicationInteroperability/index.php b/usecases/WebSyndicationInteroperability/index.php
new file mode 100644
index 0000000..6b6a75b
--- /dev/null
+++ b/usecases/WebSyndicationInteroperability/index.php
@@ -0,0 +1,200 @@
+<?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.
+ $shortTitle = "Web Syndication Interoperability (RSS and Atom)";
+ $pageTitle = "ATL Use Case - " . $shortTitle;
+ $pageKeywords = "";
+ $pageAuthor = "Freddy Allilaire";
+
+ # End: page-specific settings
+ #
+
+ # Paste your HTML content between the EOHTML markers!
+ $html = <<<EOHTML
+
+ <!-- Main part -->
+ <div id="midcolumn">
+ <h1>$pageTitle</h1>
+
+ <img align="right" src="../../resources/atlLogoSmall.png" valign="top" style="padding-left: 10px;" alt="ATL Logo" />
+ <blockquote>
+ <ul>
+ <li><a href="#keywords"><b>Keywords</b></a></li>
+ <li><a href="#overview"><b>Overview</b></a></li>
+ <li><a href="#relatedUseCases"><b>Related Use Cases</b></a></li>
+ <li><a href="#download"><b>Download</b></a></li>
+ <li><a href="#acknowledgement"><b>Acknowledgement</b></a></li>
+ </ul>
+ </blockquote>
+
+ <hr class="clearer" />
+
+ <div id="container>
+ <p align="justify">
+ This use case shows how to translate between Atom and RSS formats. All transformations code in ATL and metamodels code in KM3 is available from the
+ <a href="http://www.eclipse.org/gmt/am3/zoos/">zoos</a>.
+ </p>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;"><a name="keywords"></a>Keywords</h4>
+ <table width="100%">
+ <COLGROUP>
+ <COL width="2%" />
+ <COL width="98%" />
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ <p align="justify">
+ <a href="http://en.wikipedia.org/wiki/Web_feed">Web Feed Format</a>,
+ <a href="http://en.wikipedia.org/wiki/Wikipedia:Syndication">Syndication</a>,
+ Interoperability,
+ <a href="http://en.wikipedia.org/wiki/RSS_(file_format)">RSS</a>,
+ <a href="http://en.wikipedia.org/wiki/Atom_%28standard%29">Atom</a>,
+ XML
+ </p>
+ </td>
+ </tr>
+ </table>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;"><a name="overview"></a>Overview</h4>
+
+ <table width="100%">
+ <COLGROUP>
+ <COL width="2%" />
+ <COL width="98%" />
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ <img align="right" src="http://upload.wikimedia.org/wikipedia/commons/thumb/4/43/Feed-icon.svg/100px-Feed-icon.svg.png" valign="top" style="padding-left: 10px;" alt="A typical web feed logo" />
+ <p align="justify">
+ A web feed is a data format used for serving users frequently updated content. Content distributors syndicate a web feed,
+ thereby allowing users to subscribe to it. Making a collection of web feeds accessible in one spot is known as aggregation. Web feeds are operated by many news web sites,
+ weblogs, schools, and podcasters. Web feeds allow software programs to check for updates published on a web site.
+ People who generate web syndication feeds have a choice of formats. Today, the two most likely candidates are RSS 2.0 and Atom 1.0.
+ The main motivation for the development of Atom was dissatisfaction with RSS.
+ Each of the various web syndication feed formats has attracted large groups of supporters who remain satisfied by the specification and capabilities of their
+ respective formats.
+ </p>
+ <p align="justify">
+ The goal of this case study is to provide a bridge between the most popular web feed formats. This bridge proposes a light and flexible interoperability solution.
+ The overall approach is summarized in the following figure:
+ </p>
+ <p align="center">
+ <img src="img/UseCaseOverview.png" />
+ <br /><br />
+ <b>"$shortTitle" Use Case's Overview</b>
+ </p>
+ <p align="justify">
+ The XML injection and extraction phase was done by using XML projector available from the AM3 and ATL toolkit.
+ The Model-to-Model transformation phase was implemented by using ATL model-to-model transformations.
+ Metamodels was created by using KM3 syntax and toolkit.
+ All the metamodels mentioned in the previous schema (and so used within this use case) are available at the <a href="#download">Download section</a>.
+ </p>
+ <p align="justify">
+ We provide below a set of screenshots showing the different input/output files provided/created with this use case:
+ </p>
+ <p align="center">
+ <img src="img/Sample.png" />
+ <br /><br />
+ <b>Screenshots of the input/outputs of the use case</b>
+ </p>
+ </td>
+ </tr>
+ </table>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;">
+ <a name="relatedUseCases"></a>Related Use Cases
+ </h4>
+ <table>
+ <COLGROUP>
+ <COL width="2%" />
+ <COL width="98%" />
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ <p align="justify">
+ None at the current time.
+ </p>
+ </td>
+ </tr>
+ </table>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;">
+ <a name="download">Download</a>
+ </h4>
+
+ <table width="100%">
+ <COLGROUP>
+ <COL width="25%">
+ <COL width="75%">
+ </COLGROUP>
+ <tr>
+ <td align="center"><a href="http://www.eclipse.org/atl/atlTransformations/#RSS2ATOM"><h3>Complete scenario</h3></a></td>
+ <td>Scenario available in the ATL transformation zoo (with source files).</td>
+ </tr>
+ <tr>
+ <td align="center"><a href="http://www.eclipse.org/gmt/am3/zoos/atlanticZoo/#RSS-2.0"><h3>RSS-2.0 Metamodel</h3></a></td>
+ <td>RSS-2.0 metamodel is expressed in the <a href="http://wiki.eclipse.org/index.php/KM3">KM3</a> textual format.</td>
+ </tr>
+ <tr>
+ <td align="center"><a href="http://www.eclipse.org/gmt/am3/zoos/atlanticZoo/#ATOM"><h3>Atom Metamodel</h3></a></td>
+ <td>Atom metamodel is expressed in the <a href="http://wiki.eclipse.org/index.php/KM3">KM3</a> textual format.</td>
+ </tr>
+ <tr>
+ <td align="center"><a href="http://www.eclipse.org/gmt/am3/zoos/atlanticZoo/#XML"><h3>XML Metamodel</h3></a></td>
+ <td>XML metamodel is expressed in the <a href="http://wiki.eclipse.org/index.php/KM3">KM3</a> textual format.</td>
+ </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>Acknowledgement
+ </h4>
+
+ <table width="100%">
+ <COLGROUP>
+ <COL width="2%">
+ <COL width="98%">
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ The present work is being supported by the <a href="http://www.usine-logicielle.org">Usine Logicielle project of the System@tic Paris Region Cluster</a>.
+ </td>
+ </tr>
+ </table>
+
+ </div>
+ </div>
+
+ <div id="rightcolumn">
+ <div class="sideitem">
+ <h6>General Information</h6>
+ <ul>
+ <li style="list-style:none">February 2007</li>
+ <li style="list-style:none">By <a href="http://www.sciences.univ-nantes.fr/lina/atl/contrib/allilaire">Freddy Allilaire</a> (INRIA)</li>
+ <li style="list-style:none"><br />Please, ask your questions on the <a href="news://news.eclipse.org/eclipse.modeling.m2m">M2M newsgroup</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/index.php b/usecases/index.php
new file mode 100644
index 0000000..94e8ad8
--- /dev/null
+++ b/usecases/index.php
@@ -0,0 +1,542 @@
+<?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 = "ATL Use Cases";
+ $pageKeywords = "";
+ $pageAuthor = "Freddy Allilaire";
+
+ # End: page-specific settings
+ #
+
+
+ # Paste your HTML content between the EOHTML markers!
+ $html = <<<EOHTML
+
+ <!-- Main part -->
+ <div id="midcolumn">
+ <h1><font color='#280882'>ATL</font> Use Cases</h1>
+
+ <a name="goals"></a>
+
+ <p align="justify">
+ This section provides a set of ATL model transformation use cases covering different domains of application. These use cases are concrete examples of how model to model transformation (M2M)
+ can be applied. Some of these use cases will be simple ones, some others will be more elaborated and will reuse basic use cases or parts of other ones.
+ </p>
+
+ <p align="justify">
+ Other Eclipse projects have use case section as well for example <a href="http://www.eclipse.org/gmt/amw/usecases/">AMW</a> or
+ <a href="http://www.eclipse.org/gmt/modisco/useCases/">MoDisco</a> (GMT components).
+ </p>
+
+ <p align="justify">
+ A general description is given for each of these use cases, as well as some more precise documentations. For many of them, prototypes have already been implemented and are directly
+ downloadable from this website.
+ </p>
+
+ <p align="justify">
+ The general status of each of the provided use cases is indicated by one of the following icon:
+ <table width="100%">
+ <tr>
+ <td align="center"><img src="../../../gmt/resources/images/specification.png" /> <b>Specification Only</b></td>
+ <td align="center"><img src="../../../gmt/resources/images/implementation.png" /> <b>Partially Implemented</b></td>
+ <td align="center"><img src="../../../gmt/resources/images/completion.png" /> <b>Reaching Completion</b></td>
+ </tr>
+ </table>
+ </p>
+
+ <hr class="clearer" />
+
+ <div class="homeitem3col" >
+ <h3>List of use cases</h3>
+ <ul>
+ <li style="list-style:none">
+ <table width="100%">
+ <tr>
+ <td width="30%" valign="middle">
+ <h2> <a href="DSLsTelephony/">DSLs coordination for Telephony</a> </h2>
+ </td>
+ <td width="60%" align="justify">
+ This work presents a case study of implementing two telephony languages: SPL and CPL. They are partially based on similar vocabularies.
+ However they are very different and have been designed to be used by different people.
+ The use case shows how M2M transformations may be used to map programs conforming to SPL or CPL at different abstraction levels.
+ </td>
+ <td width="10%" valign="middle" align="right">
+ <img src="../../../gmt/resources/images/completion.png" />
+ </td>
+ </tr>
+ </table>
+ </li>
+ <li style="list-style:none">
+ <table width="100%">
+ <tr>
+ <td width="30%" valign="middle">
+ <h2> <a href="ModelAdaptation/">Model Adaptation</a> </h2>
+ </td>
+ <td width="60%" align="justify">
+ The evolution of a metamodel may render its related terminal models invalid.
+ This use case proposes a three-step solution that automatically adapts terminal models to their evolving metamodels.
+ The main contribution is the precise detection of metamodel changes by using the <a href="http://wiki.eclipse.org/AML">AtlanMod Matching Language (AML)</a>, a DSL built on top
+ of ATL and AMW. The running example is the Petrinet models.
+ </td>
+ <td width="10%" valign="middle" align="right">
+ <img src="../../../gmt/resources/images/completion.png" />
+ </td>
+ </tr>
+ </table>
+ </li>
+ <li style="list-style:none">
+ <table width="100%">
+ <tr>
+ <td width="30%" valign="middle">
+ <h2> <a href="SimplePDL2Tina/">Models Validation through Petri nets</a> </h2>
+ </td>
+ <td width="60%" align="justify">
+ This work presents a use case of model transformation using ATL rules to validate MDD's models.
+ This use case considers a simplified process description language, SimplePDL. It then presents a property-driven approach
+ in which SimplePDL process models are translated into Petri nets. SimplePDL behavioral properties
+ are expressed on corresponding Petri nets in LTL (<i>Linear Temporal Logic</i>).
+ The Tina toolkit and, in particular, its model-checker, are used to validate process models by checking the expressed properties.
+ This use case has been done by <a href="http://combemale.perso.enseeiht.fr/">Benoit Combemale</a> (<a href="http://www.irit.fr">IRIT</a>). This is a collaboration between
+ <a href="http://www.irit.fr">IRIT</a> and <a href="http://www.laas.fr/">LAAS</a> labs in Toulouse, France.
+ </td>
+ <td width="10%" valign="middle" align="right">
+ <img src="../../../gmt/resources/images/completion.png" />
+ </td>
+ </tr>
+ </table>
+ </li>
+ <li style="list-style:none">
+ <table width="100%">
+ <tr>
+ <td width="30%" valign="middle">
+ <h2> <a href="SharingRulesBetweenOCLUML_SWRLOWL/">Sharing Rules Between OCL/UML and SWRL/OWL</a> </h2>
+ </td>
+ <td width="60%" align="justify">
+ This work presents an implementation of sharing rules between two rule languages from different domains: OCL (Object Constraint Language) together with UML and SWRL
+ (Semantic Web Rule Language) together with OWL. For this integration we used the R2ML (REWERSE I1 Rule Markup Language) metamodel as pivotal metamodel. The R2ML is a
+ general Web rule markup language and it can represent different rule types: integrity, reaction, derivation and production. This work has been done by
+ <a href="http://milan.milanovic.org">Milan Milanovic</a> in collaboration
+ between the <a href="http://goodoldai.org.yu/">GOOD OLD AI Laboratory</a> at <a href="http://www.bg.ac.yu">University of Belgrade</a>,
+ <a href="http://www.sfu.ca/siat" target="_self">School of Interactive Arts and Technology</a> at
+ <a href="http://www.surrey.sfu.ca" target="_self">Simon Fraser University Surrey</a> in Canada and
+ <a href="http://oxygen.informatik.tu-cottbus.de/IT/">Chair of Internet Technology</a> at
+ <a href="http://www.tu-cottbus.de/">Brandenburg University of Technology at Cottbus</a> in Germany.
+ </td>
+ <td width="10%" valign="middle" align="right">
+ <img src="../../../gmt/resources/images/completion.png" />
+ </td>
+ </tr>
+ </table>
+ </li>
+ <li style="list-style:none">
+ <table width="100%">
+ <tr>
+ <td width="30%" valign="middle">
+ <h2> <a href="FIACRE2LOTOS/">Compiling a new formal verification language to LOTOS (ISO 8807)</a> </h2>
+ </td>
+ <td width="60%" align="justify">
+ In this use case, we translate <a href="http://www-sop.inria.fr/oasis/fiacre/">FIACRE</a> programs into
+ <a href="http://www.inrialpes.fr/vasy/cadp/">LOTOS</a> (<a href="http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=16258">ISO 8807</a>) programs, which can then be verified using the <a href="http://www.inrialpes.fr/vasy/cadp/">CADP</a> toolbox.
+ This work is the result of the cooperation of two INRIA teams: <a href="http://www.sciences.univ-nantes.fr/lina/atl/">ATLAS</a> (Nantes), and <a href="http://www.inrialpes.fr/vasy/">VASY</a> (Grenoble),
+ in the context of the <a href="http://openembedd.inria.fr/">OpenEmbeDD</a> project.
+ </td>
+ <td width="10%" valign="middle" align="right">
+ <img src="../../../gmt/resources/images/completion.png" />
+ </td>
+ </tr>
+ </table>
+ </li>
+ <li style="list-style:none">
+ <table width="100%">
+ <tr>
+ <td width="30%" valign="middle">
+ <h2> <a href="ModelsMeasurement/">Models Measurement</a> </h2>
+ </td>
+ <td width="60%" align="justify">
+ This use case shows how to compute and generate measures on KM3 metamodels or UML2 models, and how to display them in different way (HTML, and SVG).
+ This work has been done in collaboration between <a href="http://www.sodius.com">SODIUS</a> and the
+ <a href="http://www.sciences.univ-nantes.fr/lina/atl/">ATLAS Group</a>. As a complementary application to this contribution, an online service is provided at SODIUS's web site under the name "MC-Meter".
+ The online measurement service is available at: <a href="http://www.mdworkbench.com/measuring.php">http://www.mdworkbench.com/measuring.php</a>
+ </td>
+ <td width="10%" valign="middle" align="right">
+ <img src="../../../gmt/resources/images/completion.png" />
+ </td>
+ </tr>
+ </table>
+ </li>
+ <li style="list-style:none">
+ <table width="100%">
+ <tr>
+ <td width="30%" valign="middle">
+ <h2> <a href="webapp.modeling/">Modeling Web applications</a> </h2>
+ </td>
+ <td width="60%" align="justify">
+ This use case shows how model weaving is used to help in the development of model transformations. In some cases, the gap between the input and output metamodels
+ makes it difficult to develop a model transformation that works for every input model. In such cases a weaving model can be used to enrich the input model by
+ <b>annotation</b>. This process can be thought of as a way to <i>parameterize</i> the model transformation.
+ </td>
+ <td width="10%" valign="middle" align="right">
+ <img src="../../../gmt/resources/images/completion.png" />
+ </td>
+ </tr>
+ </table>
+ </li>
+ <li style="list-style:none">
+ <table width="100%">
+ <tr>
+ <td width="30%" valign="middle">
+ <h2> <a href="VisualRepCodeClone/">Visual Representation for Code Clone Tools</a> </h2>
+ </td>
+ <td width="60%" align="justify">
+ The aim of this use case is to realize a uniform visual representation for different code clone detection tools.
+ Different analysis results provided by different code clone detection tools can be injected into models. These models will be transformed to a generic Code Clone DSL model,
+ and then into SVG model. Finally, the SVG code can be automatically extracted from SVG model.
+ </td>
+ <td width="10%" valign="middle" align="right">
+ <img src="../../../gmt/resources/images/completion.png" />
+ </td>
+ </tr>
+ </table>
+ </li>
+ <li style="list-style:none">
+ <table width="100%">
+ <tr>
+ <td width="30%" valign="middle">
+ <h2> <a href="MDL2GMF/">Rational Rose to UML2 Tools</a> </h2>
+ </td>
+ <td width="60%" align="justify">
+ This use case shows how we can reuse UML projects created with Rational Rose and import them in GMF (specifically in UML2 Tools) using ATL transformations.
+ In this use case, we only support UML class diagrams. In practice, this use case was applied to the QVT metamodel available on the OMG site.
+ </td>
+ <td width="10%" valign="middle" align="right">
+ <img src="../../../gmt/resources/images/completion.png" />
+ </td>
+ </tr>
+ </table>
+ </li>
+ <li style="list-style:none">
+ <table width="100%">
+ <tr>
+ <td width="30%" valign="middle">
+ <h2> <a href="UML2AnyLogic/">Model Driven Performance Engineering: From UML/SPT to AnyLogic</a> </h2>
+ </td>
+ <td width="60%" align="justify">
+ This use case presents a transformation from annotated UML activity diagrams to AnyLogic simulation models.
+ The actions and control flows in activity diagrams are annotated with performance information utilizing the UML profile for schedulability, performance, and timing (SPT).
+ This information is used to generate a simulation model that can be executed by the AnyLogic simulation tool from XJ Technologies.
+ Such simulations can help to identify performance issues early in a software design process.
+ This use case has been done by <a href="http://jjohannes.de/">Jendrik Johannes</a> (<a href="http://tu-dresden.de/">TU Dresden</a>) and its development has been supported by the <a href="http://www.modelplex-ist.org">IST European MODELPLEX project</a> (MODELing solution for comPLEX software systems, FP6-IP 34081).
+ </td>
+ <td width="10%" valign="middle" align="right">
+ <img src="../../../gmt/resources/images/completion.png" />
+ </td>
+ </tr>
+ </table>
+ </li>
+ <li style="list-style:none">
+ <table width="100%">
+ <tr>
+ <td width="30%" valign="middle">
+ <h2> <a href="Syntax2SBVR2UML/">Production of UML class diagrams from syntactical models of english text or SBVR models</a> </h2>
+ </td>
+ <td width="60%" align="justify">
+ This work presents a case study of obtaining a UML class diagram from a syntactical analysis of a text using SBVR as an intermediate layer. We show how it is
+ possible, with the help of model engineering, to realize two transformations: from a syntactical model into a SBVR model, and from a SBVR model into a UML model.
+ This work has been done in collaboration between the ATLANMOD team in Nantes and the ILOG company.
+ </td>
+ <td width="10%" valign="middle" align="right">
+ <img src="../../../gmt/resources/images/completion.png" />
+ </td>
+ </tr>
+ </table>
+ </li>
+ <li style="list-style:none">
+ <table width="100%">
+ <tr>
+ <td width="30%" valign="middle">
+ <h2> <a href="QVT2ATLVM/">QVT to ATL Virtual Machine Compiler</a> </h2>
+ </td>
+ <td width="60%" align="justify">
+ This work provides a QVT compiler that targets the ATL Virtual Machine (ATL VM), and thus provides executability of QVT programs on top of the ATL VM.
+ The code generator is written in the ACG (<span style="font-variant: small-caps;">Atl</span> Code Generation) Domain-Specific Language (DSL).
+ It takes as input a QVT model (typically in XMI format) that may have been created by a QVT front-end (i.e., a parser and type checker) like <a href="http://www.eclipse.org/m2m/">Eclipse/modeling/m2m/</a>Procedural QVT, or <a href="http://smartqvt.elibel.tm.fr/">SmartQVT</a>.
+ The output of the code generator is a ".asm" file similar to the ones generated by the ATL compiler, or the ACG compiler (both also written in ACG).
+ </td>
+ <td width="10%" valign="middle" align="right">
+ <img src="../../../gmt/resources/images/implementation.png" />
+ </td>
+ </tr>
+ </table>
+ </li>
+ <li style="list-style:none">
+ <table width="100%">
+ <tr>
+ <td width="30%" valign="middle">
+ <h2> <a href="MMIndApproachtoDiffRep/">A Metamodel Independent Approach to Difference Representation</a> </h2>
+ </td>
+ <td width="60%" align="justify">
+ This work presents an ATL implementation of a metamodel independent approach to the representation of model differences which is agnostic of
+ the calculation method. Given two models being differenced which conform to a metamodel, their difference is conforming to another metamodel
+ derived from the former by an automated transformation. Interestingly, difference models are first-class artifacts which in turn induce other
+ transformations, such that they can be applied to one of the differenced models to automatically obtain the other one.
+ This work has been done by <a href="http://www.di.univaq.it/~cicchetti">Antonio Cicchetti</a>,
+ <a href="http://www.di.univaq.it/~diruscio">Davide Di Ruscio</a> and
+ <a href="http://www.di.univaq.it/~alfonso">Alfonso Pierantonio</a> (Università dell'Aquila).
+ </td>
+ <td width="10%" valign="middle" align="right">
+ <img src="../../../gmt/resources/images/implementation.png" />
+ </td>
+ </tr>
+ </table>
+ </li>
+ <li style="list-style:none">
+ <table width="100%">
+ <tr>
+ <td width="30%" valign="middle">
+ <h2> <a href="SoftwareQualityControlToolsInteroperability/">Software Quality Control Tools Interoperability (Bugzilla, Mantis, Excel)</a> </h2>
+ </td>
+ <td width="60%" align="justify">
+ Problems of tools interoperability can be found in various domains. Software quality control is one of these.
+ This use case presents an implementation of bridges between different bug tracking tools like Bugzilla, and Mantis.
+ We also consider that bug tracking information may be handled in a generic tool like Excel.
+ </td>
+ <td width="10%" valign="middle" align="right">
+ <img src="../../../gmt/resources/images/implementation.png" />
+ </td>
+ </tr>
+ </table>
+ </li>
+ <li style="list-style:none">
+ <table width="100%">
+ <tr>
+ <td width="30%" valign="middle">
+ <h2> <a href="BridgeBetweenBuildTools/">Software Build Tools Interoperability (Make, Ant, Maven)</a> </h2>
+ </td>
+ <td width="60%" align="justify">
+ <i>Make</i> is one of the most common build tool. It remains widely used but essentially in Unix-based platforms. Many problems have surfaced with scaling <i>Make</i> to work
+ with modern, large software projects. So, it is interesting to provide some bridges from <i>Make</i> to other build tools like <i>Ant</i> (which is popular for Java development
+ and uses an XML file format) and <i>Maven</i> (a Java tool for management project and automated software build).
+ </td>
+ <td width="10%" valign="middle" align="right">
+ <img src="../../../gmt/resources/images/implementation.png" />
+ </td>
+ </tr>
+ </table>
+ </li>
+ <li style="list-style:none">
+ <table width="100%">
+ <tr>
+ <td width="30%" valign="middle">
+ <h2> <a href="WebSyndicationInteroperability/">Web Syndication Interoperability (RSS and Atom)</a> </h2>
+ </td>
+ <td width="60%" align="justify">
+ People who generate web syndication feeds have a choice of formats. Today, the two most likely candidates are RSS 2.0 and Atom 1.0.
+ The goal of this case study is to provide a bridge between both formats by using a light and flexible interoperability solution.
+ </td>
+ <td width="10%" valign="middle" align="right">
+ <img src="../../../gmt/resources/images/implementation.png" />
+ </td>
+ </tr>
+ </table>
+ </li>
+ <li style="list-style:none">
+ <table width="100%">
+ <tr>
+ <td width="30%" valign="middle">
+ <h2> <a href="ODMImplementation/">ODM Implementation (Bridging UML and OWL)</a> </h2>
+ </td>
+ <td width="60%" align="justify">
+ This use case presents an implemented solution to the OMG Ontology Definition Metamodel (ODM) specification.
+ ODM offers a set of metamodels and mappings for bridging the metamodeling world and the ontologies. The present
+ solution supports the UML 2.0 metamodel and the OWL metamodel as defined in ODM.
+ This work is made by the SIDo Group from the <a href="http://www.univ-lr.fr/labo/l3i/site_statique/Index.html">L3I</a> lab in La Rochelle.
+ </td>
+ <td width="10%" valign="middle" align="right">
+ <img src="../../../gmt/resources/images/implementation.png" />
+ </td>
+ </tr>
+ </table>
+ </li>
+ <li style="list-style:none">
+ <table width="100%">
+ <tr>
+ <td width="30%" valign="middle">
+ <h2> <a href="PRR2IRL/">Implementing two business rule languages: PRR and IRL</a> </h2>
+ </td>
+ <td width="60%" align="justify">
+ This work presents a case study of implementing two business rule languages: Production Rule Representation (PRR) and ILOG Rule Language (IRL). We show how a pivot
+ language can be translated into a concrete one with the help of model engineering. The outcome of this experiment also provides an interesting example of DSLs coordination.
+ This work has been done in collaboration between the <a href="http://www.sciences.univ-nantes.fr/lina/atl/">ATLAS Group</a> in Nantes and <a href="http://www.ilog.com/">ILOG</a>.
+ A <b>web service PRR to IRL</b> is available here: <a href="http://www.sciences.univ-nantes.fr/lina/atl/atldemo/prronline/">http://www.sciences.univ-nantes.fr/lina/atl/atldemo/prronline/</a>.
+ </td>
+ <td width="10%" valign="middle" align="right">
+ <img src="../../../gmt/resources/images/implementation.png" />
+ </td>
+ </tr>
+ </table>
+ </li>
+ <li style="list-style:none">
+ <table width="100%">
+ <tr>
+ <td width="30%" valign="middle">
+ <h2> <a href="MonitorToSemaphore/">From Hoare's Monitors to Dijkstra's Semaphores</a> </h2>
+ </td>
+ <td width="60%" align="justify">
+ This is a classic in synchronization. We propose an automatic translation from Hoare's monitors as defined in <a href="http://www.eclipse.org/atl/usecases/MonitorToSemaphore/#ref1">[1]</a> into Dijkstra's semaphores as
+ initially introduced in <a href="http://www.eclipse.org/atl/usecases/MonitorToSemaphore/#ref2">[2]</a>.
+ The ATL transformation code follows the rules given in <a href="http://www.eclipse.org/atl/usecases/MonitorToSemaphore/#ref1">[1]</a>. A complete reprint of this paper is available at:
+ <a href="http://www.acm.org/classics/feb96/">http://www.acm.org/classics/feb96/</a>.
+ </td>
+ <td width="10%" valign="middle" align="right">
+ <img src="../../../gmt/resources/images/implementation.png" />
+ </td>
+ </tr>
+ </table>
+ </li>
+ <li style="list-style:none">
+ <table width="100%">
+ <tr>
+ <td width="30%" valign="middle">
+ <h2> <a href="UML2MsProject/">From UML Activity Diagram to Project Management Software</a> </h2>
+ </td>
+ <td width="60%" align="justify">
+ This use case shows the possibility to have interoperability between an UML activity diagram and a project management software like MsProject.
+ UML Activity Diagrams are typically used for business process modeling, for modeling the logic captured by a single use case or usage scenario, or for modeling the
+ detailed logic of a business rule. Microsoft Project is a project management software program developed by Microsoft.
+ </td>
+ <td width="10%" valign="middle" align="right">
+ <img src="../../../gmt/resources/images/implementation.png" />
+ </td>
+ </tr>
+ </table>
+ </li>
+ <li style="list-style:none">
+ <table width="100%">
+ <tr>
+ <td width="30%" valign="middle">
+ <h2> <a href="UML2MOF/">Using a UML modeler to generate metamodels</a> </h2>
+ </td>
+ <td width="60%" align="justify">
+ This use case shows how to use and integrate a model transformation service in a UML Modeler to generate metamodels conforming to KM3, MOF 1.4, and Ecore.
+ The used UML Modeler is <a href="http://www.papyrusuml.org/">Papyrus</a> (<a href="http://www-list.cea.fr/">CEA LIST</a>).
+ </td>
+ <td width="10%" valign="middle" align="right">
+ <img src="../../../gmt/resources/images/specification.png" />
+ </td>
+ </tr>
+ </table>
+ </li>
+ <li style="list-style:none">
+ <table width="100%">
+ <tr>
+ <td width="30%" valign="middle">
+ <h2> <a href="Measuring_UML_models/">Measuring UML models</a> </h2>
+ </td>
+ <td width="60%" align="justify">
+ This use case shows how to use and integrate a model transformation service in a UML Modeler to compute and generate quality measures on UML models.
+ The used UML Modeler is <a href="http://www.papyrusuml.org/">Papyrus</a> (<a href="http://www-list.cea.fr/">CEA LIST</a>).
+ </td>
+ <td width="10%" valign="middle" align="right">
+ <img src="../../../gmt/resources/images/specification.png" />
+ </td>
+ </tr>
+ </table>
+ </li>
+ <li style="list-style:none">
+ <table width="100%">
+ <tr>
+ <td width="30%" valign="middle">
+ <h2> <a href="Verifying_UML_profiled_models/">Verifying UML profiled models</a> </h2>
+ </td>
+ <td width="60%" align="justify">
+ This use case shows how to use and integrate a model transformation service in a UML Modeler to verify a UML profiled model.
+ The used UML Modeler is <a href="http://www.papyrusuml.org/">Papyrus</a> (<a href="http://www-list.cea.fr/">CEA LIST</a>).
+ </td>
+ <td width="10%" valign="middle" align="right">
+ <img src="../../../gmt/resources/images/specification.png" />
+ </td>
+ </tr>
+ </table>
+ </li>
+ <li style="list-style:none">
+ <table width="100%">
+ <tr>
+ <td width="30%" valign="middle">
+ <h2> <a href="RSM2Topcased/">RSM to Topcased UML2 Editor</a> </h2>
+ </td>
+ <td width="60%" align="justify">
+ <a href="http://www.topcased.org/">TOPCASED</a> currently relies on the ATL model transformation toolkit. Model transformations have been mainly used in order to
+ access models defined using other editors than TOPCASED one's. This use case presents an operational application of ATL to bridge RSM and TOPCASED.
+ </p>
+ </td>
+ <td width="10%" valign="middle" align="right">
+ <img src="../../../gmt/resources/images/specification.png" />
+ </td>
+ </tr>
+ </table>
+ </li>
+ <li style="list-style:none">
+ <table width="100%">
+ <tr>
+ <td width="30%" valign="middle">
+ <h2> <a href="Sildex2SAM/">Sildex to Topcased SAM</a> </h2>
+ </td>
+ <td width="60%" align="justify">
+ This use case presents the import of SILDEX models (a synchronous language based graphical modelling formalism developed by
+ <a href="http://www.tni-software.com/">TNI</a> and currently in use at <a href="http://www.airbus.com/en/">AIRBUS</a>) in the TOPCASED SAM modelling language.
+ SAM represents the new TOPCASED business metamodel for functional and automaton parts of SILDEX.
+ This use case was implemented by <a href="http://www.c-s.fr/">C-S</a> in the context of the TOPCASED project.
+ </p>
+ </td>
+ <td width="10%" valign="middle" align="right">
+ <img src="../../../gmt/resources/images/specification.png" />
+ </td>
+ </tr>
+ </table>
+ </li>
+ <li style="list-style:none">
+ <table width="100%">
+ <tr>
+ <td width="30%" valign="middle">
+ <h2> <a href="Sildex2AADL/">Sildex to Topcased AADL/COTRE</a> </h2>
+ </td>
+ <td width="60%" align="justify">
+ This use case presents the import of SILDEX models (a synchronous language based graphical modelling formalism developed by
+ <a href="http://www.tni-software.com/">TNI</a> and currently in use at <a href="http://www.airbus.com/en/">AIRBUS</a>) in AADL/COTRE.
+ It was implemented by <a href="http://www.c-s.fr/">C-S</a> in the context of the TOPCASED project.
+ </p>
+ </td>
+ <td width="10%" valign="middle" align="right">
+ <img src="../../../gmt/resources/images/specification.png" />
+ </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);
+?>
diff --git a/usecases/tmp.php b/usecases/tmp.php
new file mode 100644
index 0000000..7302460
--- /dev/null
+++ b/usecases/tmp.php
@@ -0,0 +1,115 @@
+<?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 = "ATL Use Cases";
+ $pageKeywords = "";
+ $pageAuthor = "Freddy Allilaire";
+
+ # End: page-specific settings
+ #
+
+
+ # Paste your HTML content between the EOHTML markers!
+ $html = <<<EOHTML
+
+ <!-- Main part -->
+ <div id="midcolumn">
+ <h1><font color='#280882'>ATL</font> Use Cases</h1>
+
+
+ <div class="homeitem3col" >
+ <h3>List of use cases</h3>
+ <ul>
+ <li style="list-style:none">
+ <table width="100%">
+ <tr>
+ <td width="30%" valign="middle">
+ <h2> <a href="GenerateGraphicalViewForMetamodel/">Generate Graphical View For a Metamodel</a> </h2>
+ </td>
+ <td width="60%" align="justify">
+ Having a graphical presentation of a metamodel can be sometimes enlightening in comparison with a textual presentation.
+ KM3 is a textual concrete syntax to describe metamodels and to define Domain Specific Languages.
+ A metamodel created with KM3 does not include any representation information.
+ This use case describes the automatic generation of a visual presentation for a metamodel written in KM3.
+ </td>
+ <td width="10%" valign="middle" align="right">
+ <img src="../../../gmt/resources/images/implementation.png" />
+ </td>
+ </tr>
+ </table>
+ </li>
+ <li style="list-style:none">
+ <table width="100%">
+ <tr>
+ <td width="30%" valign="middle">
+ <h2> <a href="GenerationSVGOfUMLClassDiagram/">Generation of Vector Graphic (SVG) Representation of UML Class Diagram</a> </h2>
+ </td>
+ <td width="60%" align="justify">
+ This use case describes the automatic generation of a vector graphic representation for a UML class diagram. This UML diagram has its presentation information according
+ to the UML Diagram Interchange standard, to its presentation using the W3C standard SVG (Scalable Vector Graphics), an XMLbased format. The SVG file may be exported
+ towards another graphical format, or viewed as is.
+ </td>
+ <td width="10%" valign="middle" align="right">
+ <img src="../../../gmt/resources/images/implementation.png" />
+ </td>
+ </tr>
+ </table>
+ </li>
+ <li style="list-style:none">
+ <table width="100%">
+ <tr>
+ <td width="30%" valign="middle">
+ <h2> <a href="BridgeRDBSchemaToMetamodel/">Bridge between Relational Database Schema and Metamodel</a> </h2>
+ </td>
+ <td width="60%" align="justify">
+ This use case aims to demonstrate the possibility to translate data structure description from the <i>RDBMS world</i> to the modeling technical space.
+ </td>
+ <td width="10%" valign="middle" align="right">
+ <img src="../../../gmt/resources/images/implementation.png" />
+ </td>
+ </tr>
+ </table>
+ </li>
+ <li style="list-style:none">
+ <table width="100%">
+ <tr>
+ <td width="30%" valign="middle">
+ <h2> <a href="BridgingGrafcetPetrinetPNML/">Bridging Grafcet, Petrinet, and PNML</a> </h2>
+ </td>
+ <td width="60%" align="justify">
+
+ </td>
+ <td width="10%" valign="middle" align="right">
+ <img src="../../../gmt/resources/images/implementation.png" />
+ </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);
+?>
diff --git a/usecases/webapp.modeling/description.php b/usecases/webapp.modeling/description.php
new file mode 100644
index 0000000..12b8a8d
--- /dev/null
+++ b/usecases/webapp.modeling/description.php
@@ -0,0 +1,173 @@
+<?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'
+
+ #*****************************************************************************
+ #
+ # description.php
+ #
+ # Author: Juan M. Vara
+ # Date: 2007-08-24
+ #
+ # Description: Type your page comments here - these are not sent to the browser
+ #
+ #
+ #****************************************************************************
+
+ #
+ # Begin: page-specific settings. Change these.
+ $pageTitle = "Modeling Web applications - Detailed description";
+ $pageKeywords = "";
+ $pageAuthor = "Juan M. Vara Mesa";
+
+ # 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 document explains how model annotation has been applied in this Use Case.
+ It gives a description of the models implied and the context in which they are developed.
+ For a more detailed explanation on this as well as on how to execute the <a href="resources/SOD-M.zip">example provided</a>,
+ see the <a href="resources/User.Guide.pdf">User Guide</a>.
+
+ <blockquote>
+ <ul>
+ <li><a href="#context"><b>Application Context</b></a></li>
+ <li><a href="#models"><b>The Models</b></a></li>
+ <li><a href="#model.annotation"><b>Model Annotation</b></a></li>
+ <li><a href="#using.model.annotation"><b>Using model annotation in model transformations</b></a></li>
+ <li><a href="#references"><b>References</b></a></li>
+ </ul>
+ </blockquote>
+
+
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;">
+ <a name="context">Application Context</a></h4>
+
+ <p align="justify">
+
+ Service-Oriented Computing [<a href="#ref.1">1</a>] is a new paradigm for application development whose main proposal is the use of
+ services as fundamental elements. Services usually range from quite simple ones, like buying a book or renting a car to more complex ones involving complex processes
+ such as obtaining sales ratings or participating in public auctions.
+ <p align="justify"/>
+ Nevertheless, although the design and implementation of web services can be apparently easy,
+ the implementation of business processes using web services is not so effortless.
+ Languages for the implementation of business processes have many limitations when
+ they are used in the early stages of the development process [<a href="#ref.2">2</a>].
+ This occurs mainly because the transformation from high-level business models to a
+ composition language that implements those business processes with web services is not a trivial issue.
+ <p align="justify"/>
+ Attending to these facts we have defined a model driven method for service-oriented web applications development (SOD-M [<a href="#ref.3">3</a>]).
+ It starts from a high level business model and allows obtaining a service composition model that simplify the
+ mapping to a specific web service technology. This way, the method defines new Platform Independent Models (PIMs) and the
+ mappings between them. The process is summarized in the figure below. In this Use Case we focus in the mapping from the
+ Extended Use Case Model to the Service Process Model.
+
+ <p align="center">
+ <img src="images/SOD-M.Behavioral.Modeling.png"/>
+ <br />
+ <b>Behavioral Modeling process in SOD-M</b>
+ </p>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;">
+ <a name="models">The Models</a></h4>
+
+ <p align="justify">
+To illustrate this work we use the models from a conference management system we have developed.
+The Extended Use Case model is a Use Case model representing the different services offered by a Web Information System, as well as the
+functionalities required to carry out each service. In our example, the conference management system offers three different services:
+Submit an Article, Show the submitted articles and Edit the data of an author. In order to provide with this complex services, some
+basic services are needed, as the Log-In or the Register ones. To model the relation between the different Use Cases two types of associations are used: <i><<include>></i> and <i><<extend>></i>. The former implies that the behaviour of the included Use Case is inserted in the including Use Case, while the later specifies how and when the behaviour defined in the extending use case can be inserted into the behaviour defined in the extended use case.
+<p/>
+On the other hand, in the Service Process model each complex service identified in the previous model is mapped to an activity and the basic
+services that it uses are represented as service activities. This way, back to the example we have three different activities that use
+a set of service activities. For instance the Log-In one is used by the three activities.
+
+ <p align="center">
+ <img src="images/WebConference.Models.png"/>
+ <br />
+ <b>Use Case Overview</b>
+ </p>
+<p/>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;">
+ <a name="model.annotation">Model Annotation</a></h4>
+
+ <p align="justify">
+ To generate a Service Process model, it is needed some information not included in the Extended Use Case model. For instance, if a Use Case
+ includes two or more Use Cases, the order in which they should be executed in the including Use Case should be specified, since the mapping rule for <i><<include>></i> relationships gives the two options shown in the picture below.
+
+ <p align="center">
+ <img src="images/Include.Mapping.Rule.png"/>
+ <br />
+ <b>Include Relationships Mapping Rule</b>
+ </p>
+
+ <p align="justify">
+ To handle this information, that can be interpreted as parameters to execute the transformation, we use a weaving model that conforms to a new extension of the <a href="http://www.eclipse.org/gmt/amw/zoo/#AMW%20core">core weaving metamodel</a>. It is based on the <a href="http://dev.eclipse.org/viewcvs/indextech.cgi/*checkout*/org.eclipse.gmt/AMW/org.eclipse.gmt.amw.zoo/extensions/mmw_annotation.km3">
+ the annotation extension</a> metamodel. The next figure show an excerpt of the extension that can be found on the <a href="resources/SOD-M.zip">example</a> file
+
+ <p align="center">
+ <img src="images/Annotation.Extension.png"/>
+ <br />
+ <b>Excerpt of the annotation weaving metamodel</b>
+ </p>
+
+ <p align="justify">
+ Thus, a weaving model conforming to this metamodel includes two different types of WLinks (in fact, of annotations): <i>ActivityComposition</i> and
+ <i>IncludeOrder</i>. The former serves to identify which of the Use Cases from the Extened Use Case model correspond to a Service provided by the sytem, as well as the entry and exit points to carry out the service. The later helps to solve the problem about the mapping of several include relationships attached to the same Use Case. In the example we define the annotation model shown in the figure below.
+<p/>
+
+
+ <p align="center">
+ <img src="images/Annotating.Model.png"/>
+ <br />
+ <b>Annotating of the the Extended Use Case model</b>
+ </p>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;">
+ <a name="using.model.annotation">Using model annotation in model transformations</a></h4>
+
+<p align="justify">
+ The annotation of the source model allows to add the missing data we need to execute the transformation. In order to use this information, we just have to code some ATL helpers. For instance, to map every <i>include</i> object we have to know if it is related with other <i>include</i> objects (remember the ambiguity about the mapping of include relationships). Thus, we define a helper that navigates the weaving model (the annotation model) looking for <i>IncludeOrder</i> annotations referring to the given <i>include</i> object. The helper checks if there is an annotation whose <i>former</i> element is the one that was being mapped when it was invoked.
+
+ <p align="center">
+ <img src="images/ATL.Excerpt.Include.Helper.png"/>
+ <br />
+ </p>
+
+<p align="justify">
+ Then we define two different rules for mapping include objects and we include a guard in one of them to distinguish which one should be used in each specific case. The guard invokes the helper we have just shown.
+
+ <p align="center">
+ <img src="images/ATL.Excerpt.Simple.Include.Rule.png"/>
+ <br />
+ </p>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;">
+ <a name="references">References</a></h4>
+
+ <p align="justify">
+
+<a name="ref.1"></a>[1] Papazoglou, M.P., Georgakopoulos, D.: Serviced-Oriented Computing. Communications of ACM Vol. 46, N. 10 (2003) 25-28.<br/>
+<a name="ref.2"></a>[2] Verner, L.: BPM: The Promise and the Challenge. Queue of ACM Vol. 2, N. 4 (2004) 82-91.<br/>
+<a name="ref.3"></a>[3] De Castro, V., Vara, J.M., Marcos, E. Model Transformation for Service-Oriented Web Applications Development. Workshop Proceedings of 7th International Conference on Web Engineering. July 2007, pp. 284-198.<br/>
+<p> </p>
+
+ </div>
+
+EOHTML;
+
+
+ # Generate the web page
+ $App->generatePage($theme, $Menu, $Nav, $pageAuthor, $pageKeywords, $pageTitle, $html);
+?>
diff --git a/usecases/webapp.modeling/images/ATL.Excerpt.Include.Helper.png b/usecases/webapp.modeling/images/ATL.Excerpt.Include.Helper.png
new file mode 100644
index 0000000..845d189
--- /dev/null
+++ b/usecases/webapp.modeling/images/ATL.Excerpt.Include.Helper.png
Binary files differ
diff --git a/usecases/webapp.modeling/images/ATL.Excerpt.Simple.Include.Rule.png b/usecases/webapp.modeling/images/ATL.Excerpt.Simple.Include.Rule.png
new file mode 100644
index 0000000..fd1d2ab
--- /dev/null
+++ b/usecases/webapp.modeling/images/ATL.Excerpt.Simple.Include.Rule.png
Binary files differ
diff --git a/usecases/webapp.modeling/images/Adding.Weaving.Links.bmp b/usecases/webapp.modeling/images/Adding.Weaving.Links.bmp
new file mode 100644
index 0000000..7522e0f
--- /dev/null
+++ b/usecases/webapp.modeling/images/Adding.Weaving.Links.bmp
Binary files differ
diff --git a/usecases/webapp.modeling/images/Annotating.Model.Test.png b/usecases/webapp.modeling/images/Annotating.Model.Test.png
new file mode 100644
index 0000000..8ae22f9
--- /dev/null
+++ b/usecases/webapp.modeling/images/Annotating.Model.Test.png
Binary files differ
diff --git a/usecases/webapp.modeling/images/Annotating.Model.png b/usecases/webapp.modeling/images/Annotating.Model.png
new file mode 100644
index 0000000..551b1c3
--- /dev/null
+++ b/usecases/webapp.modeling/images/Annotating.Model.png
Binary files differ
diff --git a/usecases/webapp.modeling/images/Annotation.Extension.png b/usecases/webapp.modeling/images/Annotation.Extension.png
new file mode 100644
index 0000000..6af7f4a
--- /dev/null
+++ b/usecases/webapp.modeling/images/Annotation.Extension.png
Binary files differ
diff --git a/usecases/webapp.modeling/images/Include.Mapping.Rule.png b/usecases/webapp.modeling/images/Include.Mapping.Rule.png
new file mode 100644
index 0000000..64a689f
--- /dev/null
+++ b/usecases/webapp.modeling/images/Include.Mapping.Rule.png
Binary files differ
diff --git a/usecases/webapp.modeling/images/SOD-M.Behavioral.Modeling.png b/usecases/webapp.modeling/images/SOD-M.Behavioral.Modeling.png
new file mode 100644
index 0000000..3b527ec
--- /dev/null
+++ b/usecases/webapp.modeling/images/SOD-M.Behavioral.Modeling.png
Binary files differ
diff --git a/usecases/webapp.modeling/images/UseCase.Overview.png b/usecases/webapp.modeling/images/UseCase.Overview.png
new file mode 100644
index 0000000..e6b6b19
--- /dev/null
+++ b/usecases/webapp.modeling/images/UseCase.Overview.png
Binary files differ
diff --git a/usecases/webapp.modeling/images/WebConference.Models.png b/usecases/webapp.modeling/images/WebConference.Models.png
new file mode 100644
index 0000000..ba90d28
--- /dev/null
+++ b/usecases/webapp.modeling/images/WebConference.Models.png
Binary files differ
diff --git a/usecases/webapp.modeling/index.php b/usecases/webapp.modeling/index.php
new file mode 100644
index 0000000..599e5dc
--- /dev/null
+++ b/usecases/webapp.modeling/index.php
@@ -0,0 +1,225 @@
+<?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 = "ATL Use Case - Modeling Web applications";
+ $pageKeywords = "Metamodel comparison, model weaving, transformations, ATL, AMW, AMMA";
+ $pageAuthor = "Juan M. Vara Mesa";
+
+ # End: page-specific settings
+ #
+
+ # Paste your HTML content between the EOHTML markers!
+ $html = <<<EOHTML
+
+ <!-- Main part -->
+ <div id="midcolumn">
+ <h1>$pageTitle</h1>
+
+ <a name="goals"></a>
+ <img align="right" src="../../resources/atlLogoSmall.png" valign="top" style="padding-left: 10px;" alt="ATL Logo" />
+ <blockquote>
+ <ul>
+ <li><a href="#overview"><b>Overview</b></a></li>
+ <li><a href="#howto"><b>Additional Information and Download</b></a></li>
+ <li><a href="#related"><b>Related use cases</b></a></li>
+ <li><a href="#acknowledgement"><b>Acknowledgement</b></a></li>
+ </ul>
+ </blockquote>
+
+ <hr class="clearer" />
+
+ <table>
+ <COLGROUP>
+ <COL width="2%">
+ <COL width="98%">
+ <tr>
+ <td></td>
+ <td align="justify">
+ <p/>
+
+ In this Use Case we show how the AMMA tools have been used to implement part of a method for Web Applications development.
+ More specifically we use KM3 to define a pair of DSLs based on the behavioral modeling elements of UML 2.0
+ and the ATL language to implement the mappings between them.
+ The gap between those DSLs makes it very complex to obtain directly an ATL transformation that works for any input
+ model. More information is needed in order to automatize the mappings. In a real MDE context, this additional input should take the shape
+ of a model. Here we show how a model weaving can be used to <i>parameterize</i> model transformations by defining an <b>annotation</b> model.
+
+ <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">
+
+ The aim of this Use Case was to implement a set of mappings previously defined using the ATL language.
+ Once we started to code the ATL program, we realised that some
+ information needed to generate the target model was not included in the source model.
+ For each execution of the transformation some <i>extra</i> data was needed. In some sense, these extra data can be shown as
+ a way of parameterizing the transformation.
+ <p/>
+ In this context, the first option was to extend the source metamodel in order to support the modeling of these extra data.
+ However this meant polluting the metamodel with concepts not relevant for the domain that it represented.
+ We needed a diferent way to collect these extra data that was related with the source model but not included in it.
+ Finally, since this information or <i>parameters</i> had to be available from the ATL program and considering
+ that we were in a MDE context, the best option was to use another model (and thus to define a new metamodel).
+ <p/>
+ However, a metamodel is intended to represent a new domain and we needed not to be able to model a new set of concepts. In fact we just needed
+ to provide with some extra information about the elements of some existing models. Since there already existed a base metamodel for
+ modeling relations between model elements (the <a href="http://www.eclipse.org/gmt/amw/zoo/#AMW%20core">core weaving metamodel</a>),
+ and even better, there was a base metamodel for annotating a model
+ (the <a href="http://dev.eclipse.org/viewcvs/indextech.cgi/*checkout*/org.eclipse.gmt/AMW/org.eclipse.gmt.amw.zoo/extensions/mmw_annotation.km3">
+ the Annotation extension</a>), we decided to use them in order to define a new weaving metamodel.
+
+ The process followed is summarized in the figure below.
+
+ <p align="center">
+ <img src="images/UseCase.Overview.png"/>
+ <br />
+ <b>Use Case Overview</b>
+ </p>
+
+ <p/>
+ For each execution of the ATL program, i.e., for each source model, we define a weaving model that conforms to an
+ annotation extension of the core weaving metamodel.
+ The weaving model contains a set of annotations that represent the information needed to execute the transformation, that is, the <i>parameters</i>
+ using by some of the rules of the ATL program. So, both, the source and the weaving model are taking as
+ inputs to generate the output model.
+ </p>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C;
+ background-position: top left; background-repeat; repeat-x;">
+ <a name="howto">Additional Information and Download</a></h4>
+
+ <table>
+ <COLGROUP>
+
+ <COL width="25%">
+ <COL width="75%">
+
+ <tr>
+ <td align="center">
+ <h3><a href="description.php">Using model annotations for<br/>Web applications modeling</a></h3><!--</a>-->
+ </td>
+ <td>
+ This document provides more detail about how model annotations are used in this Use Case.
+ It contains a complete description of the models considered and the context in which they are defined.
+ </td>
+ </tr>
+
+ <tr>
+ <td align="center">
+ <h3><a href="resources/User.Guide.pdf">Detailed description <br/>and User Guide</a></h3><!--</a>-->
+ </td>
+ <td>
+ A complete description of this Use Case.
+ It describes the content of the example provided and it details how to execute it.
+ It also provides with general information about how to
+ define annotation models and how to use ANT tasks to execute ATL transformations.
+ </td>
+ </tr>
+
+ <tr>
+ <td align="center">
+ <h3><a href="resources/SOD-M.zip">Example</a></h3>
+ </td>
+ <td>
+ An ATL project containing both a simplified scenary and a complete one.
+ </td>
+ </tr>
+
+ <tr>
+ <td align="center">
+ <h3><a href="resources/org.eclipse.gmt.weaver.kybele.EUC.Annotation_1.0.0.zip">AMW Extension</a></h3>
+ </td>
+ <td>
+ This plug-in that extends the AMW plug-in. When the weaver wizard for creating weaving models is launched, it shows
+ the defined extension of the core weaving metamodel.
+ This way, it is not needed to load it by hand.
+ </td>
+ </tr>
+
+ </table>
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C;
+ background-position: top left; background-repeat; repeat-x;">
+
+ <a name="related">Related use cases</a></h4>
+
+ <table>
+ <COLGROUP>
+ <COL width="25%">
+ <COL width="68%">
+ <tr>
+
+ <td align="center">
+ <a href="http://www.eclipse.org/gmt/amw/usecases/annotation/"><h3>Model annotations in Java 1.4</h3></a>
+ </td>
+ <td>
+ This use case shows how weaving models are used to annotate Java 1.4 metamodels.
+ </td>
+ </tr>
+ <tr>
+
+ <td align="center">
+ <a href="http://www.eclipse.org/gmt/amw/usecases/oamusecase/"><h3>Metamodel Annotation for Ontology Design</h3></a>
+ </td>
+ <td>
+ This use case presents a Model Driven solution for annotating models in order to obtain ontologies.
+ </td>
+ </tr>
+
+ </table>
+ <p/>
+
+ <h4 STYLE="font-size: 10pt; padding: 0; border-bottom: 2px solid #49457C; background-position: top left; background-repeat; repeat-x;">
+ <a name="acknowledgement"></a>Acknowledgement
+ </h4>
+
+ <table width="100%">
+ <COLGROUP>
+ <COL width="2%">
+ <COL width="98%">
+ </COLGROUP>
+ <tr>
+ <td></td>
+ <td>
+ The present work is been supported by the GOLD project financed by the Spanish Ministry of Education and Science (TIN2005-00010)
+ and the FoMDAs project (URJC-CM-2006-CET-0387)
+ cofinanced by the <a href="www.urjc.es">Rey Juan Carlos university
+ </a> and the Regional Government of Madrid.
+ </td>
+ </tr>
+ </table>
+
+ </table>
+ <p/>
+ </div>
+
+ <div id="rightcolumn">
+ <div class="sideitem">
+ <h6>General Information</h6>
+ <ul>
+ <li style="list-style:none">October 2007</li>
+ <li style="list-style:none">By <a href="http://kybele.escet.urjc.es/members/jmvara/">Juan M. Vara Mesa</a></li>
+ </ul>
+ </div>
+ </div>
+
+
+
+EOHTML;
+
+
+ # Generate the web page
+ $App->generatePage($theme, $Menu, $Nav, $pageAuthor, $pageKeywords, $pageTitle, $html);
+?>
diff --git a/usecases/webapp.modeling/resources/SOD-M.zip b/usecases/webapp.modeling/resources/SOD-M.zip
new file mode 100644
index 0000000..be301f0
--- /dev/null
+++ b/usecases/webapp.modeling/resources/SOD-M.zip
Binary files differ
diff --git a/usecases/webapp.modeling/resources/User.Guide.pdf b/usecases/webapp.modeling/resources/User.Guide.pdf
new file mode 100644
index 0000000..8d3c8d7
--- /dev/null
+++ b/usecases/webapp.modeling/resources/User.Guide.pdf
Binary files differ
diff --git a/usecases/webapp.modeling/resources/org.eclipse.gmt.weaver.kybele.EUC.Annotation_1.0.0.zip b/usecases/webapp.modeling/resources/org.eclipse.gmt.weaver.kybele.EUC.Annotation_1.0.0.zip
new file mode 100644
index 0000000..d80c677
--- /dev/null
+++ b/usecases/webapp.modeling/resources/org.eclipse.gmt.weaver.kybele.EUC.Annotation_1.0.0.zip
Binary files differ
