2009
DOI: 10.1007/978-3-642-10619-4_31
|View full text |Cite
|
Sign up to set email alerts
|

Execution Traces: A New Domain That Requires the Creation of a Standard Metamodel

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1
1

Citation Types

0
5
0

Year Published

2010
2010
2022
2022

Publication Types

Select...
3
2
1

Relationship

2
4

Authors

Journals

citations
Cited by 6 publications
(5 citation statements)
references
References 18 publications
0
5
0
Order By: Relevance
“…The content of traces depends on the degree of abstraction required by the desired dynamic V&V technique and the runtime concepts provided by the languages as well. Alawneh and Hamou-Lhadj [2] have categorized traces of code-centric systems into statementlevel traces, routine call traces, inter-process traces, and system call level traces. In the case of executable models, execution traces may contain different kinds of information depending on the considered executable modeling language.…”
Section: Model Execution Tracesmentioning
confidence: 99%
“…The content of traces depends on the degree of abstraction required by the desired dynamic V&V technique and the runtime concepts provided by the languages as well. Alawneh and Hamou-Lhadj [2] have categorized traces of code-centric systems into statementlevel traces, routine call traces, inter-process traces, and system call level traces. In the case of executable models, execution traces may contain different kinds of information depending on the considered executable modeling language.…”
Section: Model Execution Tracesmentioning
confidence: 99%
“…Alawneh and Hamou-Lhadj [31] have categorized traces of code-centric systems into statement-level traces, routine call traces, inter-process traces, and system call level traces. In the case of executable models, execution traces may contain different type of information depending on the executable modeling language.…”
Section: Model Execution Tracesmentioning
confidence: 99%
“…Considerable effort has been made to design generic trace formats to represent traces of programs or models conforming to any possible language [1,8,10,7]. However, while they may have interesting characteristics (modeling of logical time, handling of distributed systems, etc.…”
Section: From Generic To Rich Domain-specific Trace Metamodelsmentioning
confidence: 99%