2016
DOI: 10.1007/s11219-015-9304-4
|View full text |Cite
|
Sign up to set email alerts
|

Efficient and scalable omniscient debugging for model transformations

Abstract: This paper discusses a technique for supporting omniscient debugging for model transformations, which are used to define core operations on software and system models. Similar to software systems developed using general-purpose languages, model transformations are also subject to human error and may possess defects. Existing modeldriven engineering tools provide stepwise execution to aid developers in locating and removing defects. In this paper, we describe our investigation into a technique and associated al… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
2
1

Citation Types

0
14
0

Year Published

2017
2017
2023
2023

Publication Types

Select...
4
2

Relationship

2
4

Authors

Journals

citations
Cited by 10 publications
(14 citation statements)
references
References 33 publications
(36 reference statements)
0
14
0
Order By: Relevance
“…A particular case of debugging is omniscient debugging (back-in-time or reversible debuggers) proposed by several studies in the context of model interpretation. Omniscient debugging replays the execution of systems using the recorded traces, and provides step-by-step execution in both forward and backward modes, and variable view (e.g., [13,21]). Corley et al [20,22] explore this approach to the debugging of model transformations in AToMPM [79].…”
Section: Model-level Debugging Via Interpretationmentioning
confidence: 99%
See 1 more Smart Citation
“…A particular case of debugging is omniscient debugging (back-in-time or reversible debuggers) proposed by several studies in the context of model interpretation. Omniscient debugging replays the execution of systems using the recorded traces, and provides step-by-step execution in both forward and backward modes, and variable view (e.g., [13,21]). Corley et al [20,22] explore this approach to the debugging of model transformations in AToMPM [79].…”
Section: Model-level Debugging Via Interpretationmentioning
confidence: 99%
“…Omniscient debugging replays the execution of systems using the recorded traces, and provides step-by-step execution in both forward and backward modes, and variable view (e.g., [13,21]). Corley et al [20,22] explore this approach to the debugging of model transformations in AToMPM [79]. Their implementation records each change at the end of a transformation step, and provides support to step back to the previous states.…”
Section: Model-level Debugging Via Interpretationmentioning
confidence: 99%
“…Despite omniscient debugging's advantages, there are severe performance limitations. First, omniscient debugging is plagued with memory issues (Bousse, Corley, Combemale, Gray, and Baudry 2015, Pothier, Tanter, and Piquer 2007, Corley, Eddy, Syriani, and Gray 2017. Storing the complete simulation trace eventually leads to memory exhaustion, as trace size only increases.…”
Section: Problems With Omniscient Debuggingmentioning
confidence: 99%
“…Omniscient debugging techniques have been explored in the context of modelling languages. Corley et al have implemented omniscient debugging for model transformations and analysed its efficiency Gray 2014, Corley, Eddy, Syriani, andGray 2017). Since model transformations are nondeterministic, their implementation logs each change at the end of a transformation step.…”
Section: Related Workmentioning
confidence: 99%
“…The impact with regards to performance and scalability associated with incorporating the omniscient features has been reported in a previous work [11], the raw data has been made available online 1 . The prototype and a step-wise debugger implemented in AToMPM were both used to run a Petri-net simulator over various size models and the performance metrics were recorded.…”
Section: Quantifying the Impact Of Omniscient Debuggingmentioning
confidence: 99%