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. In this transformation scenario, we needed to produce not only one GMF model but several models,
The full transformation scenario is depicted in Figure 2:Īs 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. This script must additionally deal with the multi-diagram generation problem mentioned above.
The UML model is necessary because some GMF elements points to UML elements.įinally, we create an ant script in order to assemble all these transformations into a single executable entity. The MDL model is needed to gather the graphical information. The second step is to write a transformation from MDL and UML to GMF diagrams. In this transformation, we preserve the same structure of packages as in the MDL file. Once we can read the MDL model, the next step is to write the transformation to UML. The whole project is available in the TCS Zoo. The MDL metamodel is depicted in Figure1. To deal with these problems, we start by developing the MDL reader using TCS. Therefore, we need to find out how we can generate n models using The second problem is that the MDL modelĬontains more than one UML diagram, whereas each GMF diagram is a separate model. This syntax is neither XML nor XMI, so we need a specific reader. Grammar based on Petal syntax, and called MDL. The first problem is that the UML Model created by Rational Rose conforms to a specific In this use case, we essentially have to deal with two problems. In practice, this use case was applied to the QVT metamodel available on the OMG site ( document ad/). In this use case, we only support UML class diagrams. 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.