[ The Types Forum (announcements only),
     http://lists.seas.upenn.edu/mailman/listinfo/types-announce ]

RV'23 paper submission deadline extended to June 4, 2023!

Website: 
https://urldefense.com/v3/__https://rv23.csd.auth.gr/__;!!IBzWLUs!SemGMjKvBh7j_VXBQERg0TOEfdNcZy1bOKQLo-Oj67wodJ3MpVG46oDgEpf6cfQc-OkVRqrVoqRbeDrHUfm0JnQD78QIDoKJSko$
 

We are pleased to invite you to submit papers for the 23rd International 
Conference on Runtime Verification (RV'23), which will take place in 
Thessaloniki, Greece on October 3-6, 2023.

Important Dates
Paper submission:               15 May 2023 4 June 2023
Notification:                   30 June 2023 7 July 2023
Camera-ready:           30 July  2023
Conference:                     3-6 October 2023

Objectives and 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.

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
systems with learning-enabled components
dynamic type checking and assurance cases
runtime verification for autonomy and runtime assurance

Application areas of runtime verification include cyber-physical systems, 
autonomous systems, safety/mission critical systems, enterprise and systems 
software, cloud systems, reactive control systems, health management and 
diagnosis systems, and system security and privacy.

Papers

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, 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 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.

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

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.

Special Journal Issue!  The Program Committee of RV 2023 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).

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: 
https://urldefense.com/v3/__https://www.springer.com/gp/computer-science/lncs/conference-proceedings-guidelines__;!!IBzWLUs!SemGMjKvBh7j_VXBQERg0TOEfdNcZy1bOKQLo-Oj67wodJ3MpVG46oDgEpf6cfQc-OkVRqrVoqRbeDrHUfm0JnQD78QIdo4Qx5A$
 . Springer encourages authors to include their ORCIDs 
<https://urldefense.com/v3/__https://www.springer.com/gp/authors-editors/orcid__;!!IBzWLUs!SemGMjKvBh7j_VXBQERg0TOEfdNcZy1bOKQLo-Oj67wodJ3MpVG46oDgEpf6cfQc-OkVRqrVoqRbeDrHUfm0JnQD78QIHTP_kyc$
 > in their papers. The volume is currently scheduled to appear in the LNCS 
“Formal Methods” subline 
<https://urldefense.com/v3/__https://www.springer.com/gp/computer-science/lncs/societies-and-lncs/formal-methods-/10627874__;!!IBzWLUs!SemGMjKvBh7j_VXBQERg0TOEfdNcZy1bOKQLo-Oj67wodJ3MpVG46oDgEpf6cfQc-OkVRqrVoqRbeDrHUfm0JnQD78QIetk1Ejs$
 >.

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://urldefense.com/v3/__https://easychair.org/conferences/?conf=rv2023__;!!IBzWLUs!SemGMjKvBh7j_VXBQERg0TOEfdNcZy1bOKQLo-Oj67wodJ3MpVG46oDgEpf6cfQc-OkVRqrVoqRbeDrHUfm0JnQD78QIgNgmqN0$
 

The page limitations 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.

Reply via email to