Sentence examples for model transformation that from inspiring English sources

It builds on SysML metamodeling and Triple Grammar Graph based model transformation that takes in the descriptive architecture model and outputs the corresponding TRNSYS model in a standardized fashion, thus greatly reducing the potential of heuristic modeling uncertainty.

To achieve this goal, a key idea is to define a model transformation that takes as input some "design-oriented" model of the component assembly and produces as a result an "analysis-oriented" model that lends itself to the application of some analysis methodology.

In previous work we showed how the design and implementation of a single-rate DRTS which should behave in a virtually synchronous way can be drastically simplified by the PALS model transformation that generates the DRTS from a much simpler synchronous model.

Then, such architectural model is used as an input for a model transformation that collects the set of environment connections, extracting the data type, and creating one respective output state transition for each one of them.

This work presents a formal specification of PALS as a formal model transformation that maps a synchronous design, together with a set of performance bounds of the underlying infrastructure, to a formal DRTS specification that is semantically equivalent to the synchronous design.

We propose a generic migration approach based on model transformations that includes normalisation of legacy architectures before their actual transformation.

In this work, we present extensions to the SystemC library and automatable model transformations that enable efficient system-level fault simulation in SystemC.

As with design patterns (which can be considered a special kind of model transformation), there are often many variants on model transformations that are possible, and some of these are also described.

In particular, we present a model-to-model transformation that allows us to obtain navigational models of the Web engineering method OOWS from a requirements model.

Therefore, mechanisms to ensure model correctness become crucial, specially when applying MDE to the development of software, where software is the result of a chain of (semi automatic model transformations that refine initial abstract models to lower level ones from which the final code is eventually generated.

This aspect allows us to define model-to-model transformations that not only provide a software artifact of lower abstraction (as model-to-model transformations usually do) but also to provide feedback about how they are applied.