VLDB 2026 Research / reviewers in the wild / expert
Cristina Stratan
dblp:377/3520
· DBLP profile ↗
1ranked-venue papers
1as first author
1since 2021 · last 2026
0000-0001-5155-1142ORCID · reported
Domains — the database's venue-derived domains; a paper can count in several
Software engineering, systems software and programming languages · 1 · 1 first-author · 1 since 2021
Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.
| Software engineering, system software, and programming languages
1 paper |
Program verification · 56% Program analysis · 44% |
Topics — the 2 heaviest of 3, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Program analysis
data flow analysis |
1.0 | 1 | 2026 | Diagnosing Violations of State-Based Specifications in iCFTL · IEEE Trans. Software Eng. 2026 |
Program verification › dynamic verification
runtime verification |
1.0 | 1 | 2026 | Diagnosing Violations of State-Based Specifications in iCFTL · IEEE Trans. Software Eng. 2026 |
Methods — techniques the papers use, named apart from their topics
instrumentation · 1.0
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2026 | Diagnosing Violations of State-Based Specifications in iCFTLabstractAs modern software systems grow in complexity and operate in dynamic environments, the need for runtime analysis techniques becomes a more critical part of the verification and validation process. Runtime verification monitors the runtime system behaviour by checking whether an execution trace— a sequence of recorded events—satisfies a given specification, yielding a Boolean or quantitative verdict. However, when a specification is violated, such a verdict is often insufficient to understand why the violation happened. To fill this gap,diagnosticsapproaches aim to produce more informative verdicts. In this paper, we address the problem of generating informative verdicts for violated Inter-procedural Control-Flow Temporal Logic (iCFTL) specifications that express constraints over program variable values. We propose a diagnostic approach based on backward data-flow analysis to statically determine the relevant statements contributing to the specification violation. Using this analysis, we instrument the program to produce enriched execution traces. Using the enriched execution traces, we perform the runtime analysis and identify the statements whose execution led to the specification violation. We implemented our approach in a prototype tool,iCFTLdiagnostics, and evaluated it on 112 specifications across 10 software projects. Our tool achieves 90% precision in identifying relevant statements for 100 of the 112 specifications. It reduces the number of lines that have to be inspected for diagnosing a violation by at least 90%. In terms of computational cost, our experiments show thatiCFTLdiagnosticsgenerates a diagnosis within 7 min, and requires no more than 25MB of memory. The instrumentation required to support diagnostics incurs an execution time overhead of less than 30% and a memory overhead below 20%. Cristina Stratan, Claudio Mandrioli, Domenico Bianculli |
IEEE Trans. Software Eng. | 1 |