conferences.computer.science

All conferences / RV / 2021

RV 2021

21st International Conference on Runtime Verification

Held11–14 Oct 2021 WhereOnline RankCORE B Website www.cs.bgu.ac.il/~rv21/ ↗
Closed

Submission closed on 31 May 2021, after an extension of 11 days.

Submission timeline

  • 24 May 2021 Abstract registration 13 May 2021 → 24 May 2021 +11 days
  • 31 May 2021 Full paper 20 May 2021 → 31 May 2021 +11 days
  • 19 Jul 2021 Notification 12 Jul 2021 → 19 Jul 2021 +7 days
  • 11 Oct 2021 Conference opens

What to submit

Format
regular (16 pages LNCS + references) / short (8 pages) / tool demonstration (8 pages)
Proceedings
Springer LNCS — Paywalled, for-profit

The Program Committee of RV 2021 will give a Springer-sponsored Best Paper Award to one eligible regular paper. The Program Committee of RV 2021 will invite a selection of accepted papers to submit extended versions to a special issue of the International Journal on Software Tools for Technology Transfer (STTT).

Call for papers

The call, as published

Reproduced verbatim from the organisers’ announcement, after a deadline extension. The conference’s own page is at www.cs.bgu.ac.il/~rv21/.

CFP for RV'21 (21ST INTERNATIONAL CONFERENCE ON RUNTIME VERIFICATION)


Important Dates
*Abstract submission: May 24, 2021*
*Paper submission: May 31, 2021*
Author notification: July 19, 2021
Camera-ready version: Aug 2, 2021
Conference date: Oct 11-14, 2021 (Location: online due to COVID19)

Website: https://www.cs.bgu.ac.il/~rv21/


Scope
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:
- 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, recovery and repair
- dynamic type checking and assurance cases
- runtime verification for autonomy and runtime assurance
- Application areas of runtime verification include cyber-physical systems,
safety/mission critical systems, enterprise and systems software, cloud
systems, autonomous and reactive control systems, health management and
diagnosis systems, and system security and privacy, among others.


Note: RV is currently being re-evaluated for an upgrade in its CORE ranking
and we expect the new ranking to become official by the end of the month.


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
detailed here:
http://www.springer.de/comp/lncs/authors.html
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 here:
https://easychair.org/conferences/?conf=rv21
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 register and
attend RV 2021 to present.


Papers
There are four categories of papers which can be submitted: regular, short,
tool demo, and benchmark papers. Papers in each category will be reviewed by
at least 3 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, 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 benchmark 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 with rigorous
arguments for correctness of these verdicts, and benchmarks that are
demonstrably ch!
 allenging 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.

The Program Committee of RV 2021 will give a Springer-sponsored Best Paper
Award to one eligible regular paper.

Special Journal Issue! The Program Committee of RV 2021 will invite a
selection of accepted papers to submit extended versions to a special issue of
the International Journal on Software Tools for Technology Transfer (STTT).

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
biographies of the presenters. The proposal must not exceed 2 pages.

Program Chairs:
Lu Feng, University of Virginia
Dana Fisman, Ben Gurion University

Local Chair:
Jyotirmoy Deshmukh, University of Southern California

Program committee
Houssam Abbas, Oregon State University
Wolfgang Ahrendt, Chalmers University of Technology
Domenico Bianculli, SnT Centre - University of Luxembourg
Borzoo Bonakdarpour, Michigan State University
Radu Calinescu, University of York
Chih-Hong Cheng, DENSO AUTOMOTIVE Deutschland GmbH
Jyotirmoy Deshmukh, University of Southern California
Georgios Fainekos, Arizona State University
Yliès Falcone, University of Grenoble Alpes, CNRS
Chuchu Fan, MIT
Thomas Ferrère, Imagination Technologies
Bernd Finkbeiner, CISPA Helmholtz Center for Information Security
Adrian Francalanza, University of Malta
Sylvain Hallé, Université du Québec à Chicoutimi
Klaus Havelund, Jet Propulsion Laboratory
Bettina Könighofer, Technical University of Graz
Morteza Lahijanian, University of Colorado, Boulder
Axel Legay, UCLouvain
Martin Leucker, University of Luebeck
Chung-Wei Lin, National Taiwan University
David Lo, Singapore Management University
Leonardo Mariani, University of Milano Bicocca
Nicolas Markey, IRISA, CNRS & INRIA & University of Rennes
Laura Nenzi, University of Trieste
Dejan Nickovic, Austrian Institute of Technology
Gordon Pace, University of Malta
Nicola Paoletti, University of London
Dave Parker, University of Birmingham
Doron Peled, Bar Ilan University
Violet Ka Pun, Western Norway University of Applied Sciences
Giles Reger, The University of Manchester
Cesar Sanchez, IMDEA Software Institute
Gerardo Schneider, Chalmers University of Gothenburg
Julien Signoles, CEA LIST
Oleg Sokolsky, University of Pennsylvania
Stefano Tonetta, FBK-irst
Hazem Torfah, University of California, Berkeley
Dmitriy Traytel, University of Copenhagen

Data entirely hand-typed, one call for papers at a time. There is no scraper behind any of this: I read the announcement and type the dates in, in the gaps between other work, and with the hope it is useful to others. Organisers then move deadlines without telling anyone, calls get edited in place, and now and then the typing is simply wrong. Treat this as a well-meaning notebook rather than an authority, and check the conference’s own page before you submit anything you care about.