Object-oriented design pattern for DSL program monitoring

Drey, Zoé; Teodorov, Ciprian

doi:10.1145/2997364.2997373

Cited by 4 publications

(2 citation statements)

References 25 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Closer to our work, Drey et al [DT16] propose a design pattern for integrating runtime monitors with the execution semantics of xDSLs. In contrast with our approach, a monitoring semantics must be provided, whereas our approach comes with a monitoring semantics of its own.…”

Section: Related Workmentioning

confidence: 99%

Runtime Monitoring for Executable DSLs.

LeRoy¹,

Jeanjean²,

Bousse³

et al. 2020

JOT

View full text Add to dashboard Cite

Runtime monitoring is a fundamental technique used throughout the lifecycle of a system for many purposes, such as debugging, testing, or live analytics. While runtime monitoring for general purpose programming languages has seen a great amount of research, developing such complex facilities for any executable Domain Specific Language (DSL) remains a challenging, reoccurring and error prone task. A generic solution must both support a wide range of executable DSLs (xDSLs) and induce as little execution time overhead as possible. Our contribution is a fully generic approach based on a temporal property language with a semantics tailored for runtime verification. Properties can be compiled to efficient runtime monitors that can be attached to any kind of executable discrete event model within an integrated development environment. Efficiency is bolstered using a novel combination of structural model queries and complex event processing. Our evaluation on 3 xDSLs shows that the approach is applicable with an execution time overhead of 121% (on executions shorter than 1s), to 79% (on executions shorter than 20s) making it suitable for model testing and debugging.

show abstract

Section: Related Workmentioning

confidence: 99%

Runtime Monitoring for Executable DSLs.

LeRoy¹,

Jeanjean²,

Bousse³

et al. 2020

JOT

View full text Add to dashboard Cite

show abstract

“…Drey and Teodorov [59] propose an object-oriented design pattern for defining monitoring services (i.e., runtime services) for an executable DSL. This pattern can be used to define runtime monitors for operational semantics based on a visitor design pattern.This is accomplished by subtyping classes of the abstract syntax and of the operational semantics, which implies that a monitor is always specific to the considered executable DSL.…”

Section: Integration Of Runtime Servicesmentioning

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