A runtime model for fUML

Mayerhofer, Tanja; Langer, Philip; Kappel, Gerti

doi:10.1145/2422518.2422527

Cited by 30 publications

(31 citation statements)

References 9 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…These tools (e.g., [26]) are extremely useful when fUML is used to specify behavior of user models. However, when fUML is used as a VM, techniques similar to those used for asm.js [27] may be used to increase performance: definition of a simpler subset of fUML, and ahead-of-time compilation to machine code.…”

Section: Resultsmentioning

confidence: 99%

fUML as an Assembly Language for Model Transformation

Tisi

Jouault

Delatour

et al. 2014

Software Language Engineering

View full text Add to dashboard Cite

International audienceWithin a given modeling platform, modeling tools, such as model editors and transformation engines, interoperate efficiently. They are generally written in the same general-purpose language, and use a single modeling framework (i.e., an API to access models). However, interoperability between tools from different modeling platforms is much more problematic.In this paper, we propose to leverage fUML in order to address this issue by providing a common execution language. Modeling frameworks can then be abstracted into generic actions that perform elementary operations on models. Not only can user models benefit from a unified execution semantics, but modeling tools can too.We support this proposal by showing how it can apply to a model transformation engine. To this end, a prototype compiler from ATL to fUML has been built, and is described. Finally, we conclude that fUML has some useful properties as candidate common execution language for MDE, but lacks some features

show abstract

Section: Resultsmentioning

confidence: 99%

fUML as an Assembly Language for Model Transformation

Tisi

Jouault

Delatour

et al. 2014

Software Language Engineering

View full text Add to dashboard Cite

show abstract

“…The next step is the automatic generation of model execution tools for DSML. In previous work [10], we created the basis for enabling the (semi-)automatic generation of execution tools, such as debuggers and testing environments. We enhanced the reference implementation of the fUML virtual machine in terms of a dedicated trace model, an event model, and a command API, thus enabling the runtime analysis, observation and control of the execution of fUML models.…”

Section: Discussionmentioning

confidence: 99%

“…To enable this layer to be notified whenever such a place holder activity is called and to allow for pausing the execution until the external library responds to the forwarded call, we make use of an event mechanism and a command API that we integrated into the standardized fUML virtual machine (cf. [10]). The developed event mechanism notifies listeners about the state of the fUML model execution; for instance, it indicates that a specific activity has been entered.…”

Section: Importing External Libraries For Importing the Interfacesmentioning

confidence: 99%

xMOF: Executable DSMLs Based on fUML

Mayerhofer

Langer

Wimmer

et al. 2013

Software Language Engineering

Self Cite

View full text Add to dashboard Cite

When defining a domain-specific modeling language (DSML), the two key components that have to be specified are its syntax and semantics. For specifying a modeling languages' abstract syntax, metamodels are the standard means. MOF provides a standardized, well established, and widely accepted metamodeling language enabling the definition of metamodels and the generation of accompanying modeling facilities. However, no such standard means exist for specifying the behavioral semantics of a DSML. This hampers the efficient development of model execution facilities, such as debugging, simulation, and verification. To overcome this limitation, we propose to integrate fUML with MOF to enable the specification of the behavioral semantics for DSMLs in terms of fUML activities. We discuss alternatives how this integration can be achieved and show by-example how to specify the semantics of a DSML using fUML. To reuse existing runtime infrastructures, we further demonstrate the usage of external libraries in fUML-based specifications.

show abstract

“…Mayerhofer et al [38] extended the standard fUML operational semantics in order to support debugging of fUML models. This includes the definition of a control API to pause or execute single steps, and an observer pattern to follow model changes.…”

Section: Standard Debugging For Executable Dslsmentioning

confidence: 99%

Omniscient debugging for executable DSLs

Bousse

LeRoy²,

Combemale

et al. 2018

Journal of Systems and Software

View full text Add to dashboard Cite

Omniscient debugging is a promising technique that relies on execution traces to enable free traversal of the states reached by a model (or program) during an execution. While a few General-Purpose Languages (GPLs) already have support for omniscient debugging, developing such a complex tool for any executable Domain Specific Language (DSL) remains a challenging and error prone task. A generic solution must: support a wide range of executable DSLs independently of the metaprogramming approaches used for implementing their semantics; be efficient for good responsiveness. Our contribution relies on a generic omniscient debugger supported by efficient generic trace management facilities. To support a wide range of executable DSLs, the debugger provides a common set of debugging facilities, and is based on a pattern to define runtime services independently of metaprogramming approaches. Results show that our debugger can be used with various executable DSLs implemented with different metaprogramming approaches. As compared to a solution that copies the model at each step, it is on average six times more efficient in memory, and at least 2.2 faster when exploring past execution states, while only slowing down the execution 1.6 times on average.Keywords: Software Language Engineering; Domain-Specific Languages; Executable DSL; Omniscient debugging; Execution trace IntroductionA large amount of Domain-Specific Languages (DSLs) have been proposed and used to describe the dynamic aspects of systems [1,2,3,4,5]. In that context, early dynamic verification and validation (V&V) techniques, such as testing [6], semantic differencing [7] or runtime verification [8], are necessary to ensure that such executable models (or programs 1 ) are correct. These techniques require models to be executable, which can be achieved by defining the * Corresponding author Email addresses: erwan.bousse@tuwien.ac.at (Erwan Bousse), dorian.leroy@jku.at (Dorian Leroy), benoit.combemale@irit.fr (Benoit Combemale), wimmer@big.tuwien.ac.at (Manuel Wimmer), baudry@kth.se (Benoit Baudry)1 We arbitrarily use the term executable model since this work focuses on metamodel-based DSLs, but the term program can be used interchangeably.

show abstract

A runtime model for fUML

Cited by 30 publications

References 9 publications

fUML as an Assembly Language for Model Transformation

fUML as an Assembly Language for Model Transformation

xMOF: Executable DSMLs Based on fUML

Omniscient debugging for executable DSLs

Contact Info

Product

Resources

About