Defining and validating transformations of uml models

09-Dec-2019 03:23 by 3 Comments

Defining and validating transformations of uml models - david deangelo interviews with dating gurus david shade newest

Following to this idea the Model Transformation Tool is able to create a class containing a main-method that exactly doing all of this for you. For this there is also an entry in the AAL Suite Eclipse menu, but this is doing nothing more then to create and run a configuration to start the main-method of the created class (if there is someone).If you are using the Ontology Project Wizard you need to make sure that the check-button like shown below is selected: Then after performing a transformation from UML to Java there will be also a class available called like "" in the "creator" package of your ontology root.

NOTICE: The XML file should be contained under the same folder and use the same name with the OWL file that will be transformed in order be recognized by the parser of the tool.

The model transformation tool makes its functionality available through menus in the AAL Studio.

When a transformation have been selected from a menu, it will start working in the background.

Before the transformation takes place, an XML validator checks the provided XML file against the defined XSD Schema and proceeds to the transformation, including the additional information of the XML file. Additionally, samples of OWL and XML files for tests and/or understanding the structure of the files as well as how this tool actually works, are available here.

The generated UML file can be opened (or edited) by the Eclipse in order all the necessary Classes, Associations, Properties, Enumerations etc.

The role of the Model Transformation Tool is to be a common component for all model transformations in AAL Studio.

Currently only one transformation is available on UML files, namely the Ontology to Java transformation The purpose of this AAL Studio tool is to make it easy to generate implementation resources (such as Java source code) from models created in UML or EMF, and to give a good integration with the Eclipse development work.

The alternative for the user would usually be to hand-code the implementation based on the model or some equivalent design.

The modelling and transformation approach also have the benefit that maintenance is simplified.

E.g., if there are changes in the target platform (e.g.

the Java representation of the ontologies), then correct code can quickly be re-generated once the transformation have been updated.

The supported format and the expected output is compatible with Protege 3.x that uses the Protege OWL-API (Stanford).