Call for Papers

We are pleased to invite you to submit papers for the 25th International Conference on Runtime Verification (RV25), which will take place in Graz, Austria from September 15 to September 19, 2025.

Dates

• Paper submission: 30 May, 2025
• Notification: 11 July, 2025
• Camera-ready: 27 July, 2025
• Conference: 15-19 September 2025

Objectives and Scope

Runtime verification is concerned with the monitoring and analysis of the runtime behavior of software and hardware systems. Runtime verification techniques are crucial for system correctness, reliability, and robustness; they provide an additional level of rigor and effectiveness compared to conventional testing and are generally more practical than exhaustive formal verification. Runtime verification can be used prior to deployment, for testing, verification, and debugging purposes, and after deployment for ensuring reliability, safety, and security and for providing fault containment and recovery as well as online system repair.

The topics of the conference include, but are not limited to:

• specification languages for monitoring
• monitor construction techniques
• program instrumentation
• logging, recording, and replay
• combination of static and dynamic analysis
• specification mining and machine learning over runtime traces
• monitoring techniques for concurrent and distributed systems
• runtime checking of privacy and security policies
• metrics and statistical information gathering
• program/system execution visualization
• fault localization, containment, resilience, recovery, and repair
• monitoring systems with learning-enabled components
• dynamic type checking 
• runtime verification for autonomy and runtime assurance
• out-of-distribution and anomaly detection in ML-based systems
• safe reinforcement learning

Paper Categories

There are four categories of papers that can be submitted: regular, short, tool demo, and benchmark papers. Papers in each category will be reviewed by at least three members of the Program Committee.

• Regular Papers (up to 16 pages, not including references) should present original unpublished results. We welcome theoretical papers, system papers, papers describing domain-specific variants of RV, and case studies on runtime verification.
• Short Papers (up to 8 pages, not including references) may present novel but not necessarily thoroughly worked out ideas, for example emerging runtime verification techniques and applications, or techniques and applications that establish relationships between runtime verification and other domains.
• Tool Demonstration Papers (up to 8 pages, not including references) should present a new tool, a new tool component, or novel extensions to existing tools supporting runtime verification. The paper must include information on tool availability, maturity, and selected experimental results and it should provide a link to a website containing the theoretical background and user guide. Furthermore, we strongly encourage authors to make their tools and benchmarks available with their submission.
• Benchmark Papers (up to 8 pages, not including references) should describe a benchmark, suite of benchmarks, or benchmark generator useful for evaluating RV tools. Papers should include information as to what the benchmark consists of and its purpose (what is the domain), how to obtain and use the benchmark, an argument for the usefulness of the benchmark to the broader RV community and may include any existing results produced using the benchmark. We are interested in both benchmarks pertaining to real-world scenarios and those containing synthetic data designed to achieve interesting properties. Broader definitions of benchmarks e.g. for generating specifications from data or diagnosing faults are within scope. We encourage benchmarks that are tool-agnostic, especially if they have been used to evaluate multiple tools. We also welcome benchmarks that contain verdict labels and rigorous arguments for the correctness of these verdicts, and benchmarks that are demonstrably challenging with respect to the state-of-the-art tools. Benchmark papers must be accompanied by an easily accessible and usable benchmark submission. Papers will be evaluated by a separate benchmark evaluation panel who will assess the benchmarks’ relevance, clarity, and utility as communicated by the submitted paper.

Tutorial track

Tutorials are up-to-two-hour presentations on a selected topic. Additionally, tutorial presenters will be offered to publish a paper of up to 20 pages in the LNCS conference proceedings. A proposal for a tutorial must contain the subject of the tutorial, a proposed timeline, a note on previous similar tutorials (if applicable) and the differences to this incarnation, and biographies of the presenters. The proposal must not exceed 2 pages. The deadline for tutorial proposals is the same as for regular papers.

Submission Instructions

Submitted papers and tutorials must use the LNCS/Springer style, which is detailed here.

Papers must be original work and not be submitted for publication elsewhere. Papers must be written in English and submitted electronically (in PDF format) using the EasyChair submission page. The EasyChair link will be provided soon.

The page limits mentioned above include all text and figures but exclude references. Additional details omitted due to space limitations may be included in a clearly marked appendix, that will be reviewed at the discretion of reviewers, but not included in the proceedings.

At least one author of each accepted paper and tutorial must register and present the contribution at RV 2025.

Program Committee

Organizing committee

General Chair:

• Ezio Bartocci, TU Wien, Austria

Program Chairs:

• Bettina Könighofer, Graz University of Technology, Austria
• Hazem Torfah, Chalmers University of Technology, Sweden

Local Chair:

• Roderick Bloem, Graz University of Technology, Austria

Publicity Chair:

• Martin Tappler, TU Wien, Austria