caml-list - the Caml user's mailing list
 help / Atom feed
From: Bernd Finkbeiner <finkbeiner@cs.uni-saarland.de>
To: Bernd Finkbeiner <finkbeiner@cs.uni-saarland.de>
Subject: [Caml-list] CFP: 19th International Conference on Runtime Verification
Date: Thu, 7 Feb 2019 09:19:29 +0100
Message-ID: <3E0D6541-246A-41BC-A8C3-43E79F3EA910@cs.uni-saarland.de> (raw)

Call for Papers

RV 2019

19th International Conference on Runtime Verification
Porto, Portugal
8-11 October 2019

https://www.react.uni-saarland.de/rv2019/

# 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

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.

An overview of previous RV conferences and earlier workshops can be found at: http://www.runtime-verification.org.

# 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=rv19

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 2018 to present.

# Papers

There are three categories of papers which can be submitted: regular, short and tool demo 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 2019 will give a best paper award, and a selection of accepted regular papers will be invited to appear in a special journal issue.

# 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

# Website

https://www.react.uni-saarland.de/rv2019/

# Important Dates

Abstract deadline:                April 25, 2019
Paper and tutorial deadline: 	  April, 30, 2019
Paper and tutorial notification:  June, 14, 2019 
Camera-ready deadline:  	  July, 14, 2019
Conference: 	                  October, 8 - 11, 2019


-- 
Caml-list mailing list.  Subscription management and archives:
https://sympa.inria.fr/sympa/arc/caml-list https://inbox.ocaml.org/caml-list
Forum: https://discuss.ocaml.org/
Bug reports: http://caml.inria.fr/bin/caml-bugs

                 reply index

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publically to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3E0D6541-246A-41BC-A8C3-43E79F3EA910@cs.uni-saarland.de \
    --to=finkbeiner@cs.uni-saarland.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

caml-list - the Caml user's mailing list

Archives are clonable: git clone --mirror https://inbox.ocaml.org/caml-list

AGPL code for this site: git clone https://public-inbox.org/ public-inbox