Main Page/Resources/MTB/MTB

From Atenea

< Main Page | Resources | MTB
Revision as of 15:54, 21 July 2014 by Javiertroya (Talk | contribs)
(diff) ←Older revision | Current revision (diff) | Newer revision→ (diff)
Jump to: navigation, search

Contents

MatchingTablesBuilder Executable

On this website you can find our executable for obtaining the matching tables. First of all and as explained in [1], let us recall the input files needed for this approach:

  • Source metamodel (Ecore format)
  • Target metamodel (Ecore format)
  • ATL transformation
  • Text file with OCL constraints (the so-called Tracts)

The execution process is divided in two steps, and so in two executables. The first executable extract the types of the ATL transformation. The second executable uses as input the output of the first one to eventually produce the similarity tables.

ATL Transformation Types Extractor

The first executable is available from here. This program generates a file with the types of every rule in the ATL transformation. The inputs for this executable are:

  • Source metamodel (Ecore format)
  • Target metamodel (Ecore format)
  • ATL transformation

The output is:

  • A file (*.xmi) with the types extracted from the ATL transformation. The name of this file is the name of the ATL transformation concatenated with Types.xmi.

There are two folders and one executable file in the zipped file:

  • ATLTransformationTypesExtractor.jar. This is the executable file.
  • Properties folder. This is a folder that can be ignored by the user.
  • MTs folder. This folder contains a set of model transformations, most of them taken from the ATL zoo. The user can choose any of these transformations, or different ones, to try out this tool. There is also a folder called ZTRAFOResults, where several files with the types extraction of many ATL transformations are available.

The user interface of the tool is very intuitive, as it can be see in the image below.

Once the three files and the directory for the output file have been specified, the Get ATL Transformation Types button can be clicked. If everything goes ok, the file with the types extracted is generated in the folder specified by the user. The state of the tool after execution should be similar to the one shown in the following figure. If there is any error during the execution, it is shown in the panel on the right.

NOTE: This program works with most ATL model transformations.

Image:ATLTEAfterExecution.png

NOTE for Windows 7 Users: If there is a problem with the classpath when executing the tool by double-clicking the SimilarityMatrix.jar, please execute it with the console. Follow this steps:

  • Open the console. For that, type cmd.exe in run
  • Navigate until the folder where the zip file has been unzipped
  • Let us suposse the zip file was unzipped in C:\Users\mine\Documents\SM. Then, once you are in such folder, type SimilarityMatrix.jar -Duser.dir = C:\Users\mine\Documents\SM
  • The program should be launched and work properly

Matching Tables Calculator

The second executable is available from here. This program calculates the three matching tables and writes them in a csv file. The inputs for this executable are:

  • Source metamodel (Ecore format and having only one package).
  • Target metamodel (Ecore format and having only one package).
  • Textual files with the OCL constraints (txt extension and having one constraint per line).
  • ATL transformation types (*Types.xmi generated by first executable).
  • The threshold value.

The output is:

  • A csv file with the matching tables.
  • A report where for every constraint provides the list of ATL rules ordered according the chances they have of being the guilty rule.

The user interface of the tool can be see in the image below:

Image:MTBUserInterface.png

In order to run the Matching Tables Builder it is needed to unzip the above mention file without modifying the file and folder structure and run MatchingTablesBuilder.jar. The folder Examples contains the required input files by the program for several examples.

References

[1] Loli Burgueño, Javier Troya, Manuel Wimmer, Antonio Vallecillo. Static Fault Localization in Model Transformations. Submitted for Publication. 2013

Personal tools