VIATRA

The VIATRA (VIsual Automated model TRAnsformations) framework is the core of a transformation-based verification and validation environment for improving the quality of systems designed using the Unified Modeling Language by automatically checking consistency, completeness, and dependability requirements.

Target application domains

VIATRA2 primarily aims at designing model transformations to support the precise model-based systems development with the help of invisible formal methods. Invisible formal methods are hidden by automated model transformations projecting system models into various mathematical domains (and, preferably, vice versa). In this way, VIATRA2 nicely complements other model transformation tools within the www.eclipse.org/gmt initiative.

The most traditional application area for VIATRA2 – started as early as 1998 – is to support the transformation-based dependability analysis of system models taken from various application areas (safety-critical and/or embedded systems, robust e-business applications, middleware, service oriented architecture) described using various modeling languages (BPM, UML, etc.) during a model-driven systems engineering process. Such a model (and transformation)-based dependability analysis typically also includes the verification and validation, the testing, the safety and security analysis as well as the early assessment non-functional characteristics (such as reliability, availability, responsiveness, throughput, etc.) of the system under design. In addition, model transformations for specification, design, deployment, optimization or code generation in traditional model-driven systems engineering are also focal areas for VIATRA2.

Approach

Since precise model-based systems development is the primary application area of VIATRA2, it necessitates that (i) the model transformations are specified in a mathematically precise way, and (ii) these transformations are automated so that the target mathematical models can be derived fully automatically. For this purpose, VIATRA2 have chosen to integrate two popular, intuitive, yet mathematically precise rule-based specification formalisms, namely, graph transformation (GT) and Abstract State Machines (ASM) to manipulate graph based models.

The basic concept in defining model transformations within VIATRA2 is the (graph) pattern. A pattern is a collection of model elements arranged into a certain structure fulfilling additional constraints (as defined by attribute conditions or other patterns). Patterns can be matched on certain model instances, and upon successful pattern matching, elementary model manipulation is specified by graph transformation rules. Like OCL, graph transformation rules describe pre- and postconditions to the transformations, but graph transformation rules are guaranteed to be executable, which is a main conceptual difference. Graph transformation rules are assembled into complex model transformations by abstract state machine rules, which provide a set of commonly used imperative control structures with precise semantics.

Models and modeling languages and transformations are all stored uniformly in the so-called VPM model space, which provides a very flexible and general way for capturing languages and models on different meta-levels and from various domains (or technological spaces). Generic and meta-transformations (type parameters, rules manipulating other rules) for providing reuse of transformations are a unique specification feature of VIATRA2 (up to our knowledge) at least among tools based on graph transformation.

While on the one hand, the underlying modeling and transformation concepts of VIATRA2 are nonstandard (i.e. the VPM metamodeling core is more expressive than MOF, and the transformation language is not QVT), on the other hand, VIATRA2 plans to support these related standards by offering (i) powerful and extensible model importers and exporters and (ii) domain specific languages integrated to the framework as VIATRA2 (and thus Eclipse) plug-ins. For instance, the QVT standard is intended to be supported by translating QVT descriptions into ASM and GT rules. Model importers accepting the XMI-based models of the state-of-the-art UML modeling tools (such as IBM Rational Software Architect) will be part of the initial contribution, and importers for additional tools will be added later on.

Target audience and end users

The VIATRA2 framework currently serves as the underlying model transformation technology of the ongoing DECOS European IP in the field of dependable embedded systems. Moreover, VIATRA2 will serve as a key underlying model transformation technology for several additional projects on the European level which will start in the upcoming 6 months.

In this way, academic and industrial partners in these projects would become the first end users of the framework, and they would highly benefit from an open source initiative. These projects would provide noticeable international visibility to VIATRA2 as well as the entire GMT project. Moreover, many interesting directions for future developments have already been evolved (and will continuously evolve) using the feedbacks from partners.

gollark: Setting whatnow?
gollark: See, this is great\* and not\*\* horribly cursed.
gollark: ```makefilestyles: ./node_modules/.bin/sass -s compressed src/style.sass:dist/style.cssscripts: ./node_modules/.bin/esbuild --bundle --target=es6 --outfile=dist/out.js src/index.js cp src/index.html dist/index.htmldevserver: cd dist && python3 -m http.server 7401build: styles scriptswatch: make devserver & while inotifywait src -e create -e modify -e moved_to; do make -j4 build; done```
gollark: JS→JS build tools mostly just transpile to older syntax and do bundling.
gollark: No, compile JS to JS, obviously.

See also
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.