RV 2016

16th International Conference on Runtime Verification

September 23-30, Madrid, Spain


http://rv2016.imag.fr

Scope

Runtime verification is concerned with monitoring and analysis of software and hardware system executions. Runtime verification techniques are crucial for system correctness, reliability, and robustness; they are significantly more powerful and versatile than conventional testing, and 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:

- specification languages
- specification mining
- program instrumentation
- monitor construction techniques
- logging, recording, and replay
- runtime enforcement, fault detection, localization, containment, recovery and repair
- program steering and adaptation
- metrics and statistical information gathering
- combination of static and dynamic analyses
- program execution visualization
- monitoring techniques for safety/mission-critical systems
- monitoring distributed systems, cloud services, and big data applications
- monitoring security and privacy policies

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.

Invited Speakers

The program of RV 2016 will feature invited talks from:

Overview

RV 2016 will be held September 23-30 in Madrid, Spain. RV 2016 will feature the first summer school on Runtime Verification (September 23-25), two workshop days (September 26-25), and three conference days (September 28-30).

General Information on Submissions

All papers and tutorials will appear in the conference proceedings in an LNCS volume. Submitted papers and tutorials must use the LNCS/Springer style. At least one author of each accepted paper and tutorial must attend RV 2016 to present the paper. Papers must be written in English and submitted electronically (in PDF format) using the EasyChair system. The below page limitations 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.

Research Papers Track

Research papers can be submitted in two categories: regular and short papers. Papers in both categories will be reviewed by at least 3 members of the Program Committee.

Tool Papers Track

The aim of the RV 2016 tool track is to provide an opportunity for researchers and practitioners to show and to discuss the latest advances, experiences and challenges in devising and developing reliable software tools for runtime verification. All tool papers will be reviewed by at least 3 members of the Tool Committee. An author of each accepted tool paper should give a 15-20 minutes demonstration during the conference.

All tool papers 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.
We encourage tool papers to include a script in an appendix (not included in the page count) describing how the demo will be conducted during the conference presentation with screenshots presenting step-by-step the tool’s capabilities, highlighting the main characteristics and the usage.

Tool papers can be submitted into two categories:

Tutorial Track

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.

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 a biography of the presenter. The proposal must not exceed 2 pages. Tutorial proposals will be reviewed by the Program Committee.

Important Dates

Research and tool papers as well as tutorials will follow the following timeline:

Committees

Program Committee Chairs


Tool Committee Chair


Local Organization Chair


Program Committee


Tool Committee