Runtime verification is concerned with the monitoring and analysis of the runtime behaviour 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.
Topics of interest to the conference include, but are not limited to:
monitor construction techniques
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
statistical model checking
metrics and statistical information gathering
program/system execution visualization
fault localization, containment, recovery and repair
integrated vehicle health management (IVHM)
Application areas of runtime verification include cyber-physical systems, safety/mission-critical systems, enterprise and systems software, autonomous and reactive control systems, health management and diagnosis systems, and system security and privacy.
We welcome contributions exploring the combination of runtime verification techniques with machine learning and static analysis. Whilst these are highlight topics, papers falling into these categories will not be treated differently from other contributions.
The page limitations mentioned below 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 attend RV 2017 to present.
There are three categories of papers which can be submitted: regular, short or tool papers. Papers in each category will be reviewed by at least 3 members of the Program Committee.
Regular Papers (up to 15 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 6 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, 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.
The Program Committee of RV 2017 will give a best paper award, and a selection of accepted regular papers will be invited to appear in a special issue of the Springer Journal on Formal Methods in System Design.
Tutorials are two-to-three-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, not including references.
A proposal for a tutorial must contain the subject of the tutorial, a brief abstract, a proposed format and timelines (of different parts), a note on the relevance to RV, a note on previous similar tutorials (if applicable) and the differences to this incarnation, and a brief biography of the presenter. The proposal should not exceed 2 pages.
RV-CuBES: A Workshop Replacement for the Competition
The Runtime Verification Competition will not be running in 2017. In its place a Workshop is being organised to discuss the future of the competition and showcase existing Runtime Verification tools. Please see the relevant page on the conference website for details.