caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Andrei Paskevich <andrei@lri.fr>
To: caml-list@inria.fr
Subject: [Caml-list] F-IDE 2021 - Call for Papers
Date: Mon, 19 Oct 2020 19:11:08 +0200	[thread overview]
Message-ID: <20201019171108.GA1329691@tikki.lri.fr> (raw)

******************************************************************
F-IDE 2021: 6th Workshop on Formal Integrated Development Environment

Affiliated with NASA Formal Methods 2021
May 24-28, 2021 -- held online
https://cister-labs.pt/f-ide2021
******************************************************************

Important Dates

  * Abstract submission:  Mon, Feb 22, 2021
  * Full paper submission:  Mon, Mar 1, 2021
  * Notification:  Mon, Apr 19, 2021
  * Camera-ready:  Mon, May 3, 2021
  * Workshop:  May 24-28, 2021

Overview

  High levels of safety, security, and privacy standards require the use
  of formal methods to specify and develop compliant software
  (sub)systems. Any standard comes with an assessment process, which
  requires a complete documentation of the application to ease the
  justification of design choices and the review of code and proofs.

  Ideally, an F-IDE dedicated to such developments should comply with
  several requirements. The first one is to associate a logical theory
  with a programming language, in a way that facilitates the tightly
  coupled handling of specification properties and program constructs.
  The second is to offer a language and/or an environment simple enough
  to be usable by most developers, even if they are not fully acquainted
  with higher-order logics or set theory, in particular by making
  development of proofs as easy as possible. The third is to offer
  automated management of application documentation. It may also be
  expected that developments done with such an F-IDE are reusable and
  modular. Tools for testing and static analysis may be embedded within
  F-IDEs to support the assessment process.

Topics

  The workshop is open to contributions on all aspects of a system
  development process, including specification, design, implementation,
  analysis, and documentation. It welcomes the presentation of tools,
  methods, techniques, and experiments. Topics of interest include, but
  are not limited to, the following:

  * F-IDE building: design and integration of languages, development of
    user-friendly front-ends
  * How to make high-level logical and programming concepts palatable to
    industrial developers
  * Integration of object-oriented and modularity features
  * Integration of static analyzers
  * Integration of automated proof tools, theorem provers, and testing tools
  * Documentation tools
  * Impact of tools on certification
  * Experience reports on developing F-IDEs
  * Experience reports on using F-IDEs
  * Experience reports on formal methods-based assessments in industrial
    applications

Submission Guidelines

  We accept both long (15 pages) and short (6 pages) paper submissions.
  The page limit does not include the bibliography. Submitted papers
  must present original contributions whose main results and conclusions
  have not been published or submitted elsewhere. Each submission will
  be reviewed by at least three members of the Program Committee. We
  expect that one author of every accepted paper will present their work
  at the workshop.

  Submitted papers must be written in English and follow the EPTCS LaTeX
  format (http://style.eptcs.org). Authors are invited to submit the
  following types of contributions:

  * Research papers providing new concepts and results
  * Experience reports
  * Position papers and research perspectives
  * Tool presentations

  Papers should be submitted via EasyChair at F-IDE 2021's workshop page:
  https://easychair.org/conferences/?conf=f-ide2021. Preliminary
  proceedings will be made available in electronic form at the workshop.
  Post-proceedings will be published in the Electronic Proceedings in
  Theoretical Computer Science (EPTCS).

Program Committee

  * Andrew Reynolds, University of Iowa, USA
  * Bernhard Rumpe, RWTH Aachen University, Germany
  * Carlo A. Furia, Chalmers University of Technology, Sweden
  * César Muñoz, NASA Langley, USA
  * Cinzia Bernardeschi, University of Pisa, Italy
  * Claudio Sacerdoti Coen, University of Bologna, Italy
  * Enrico Tassi, Inria, France
  * François Pessaux, ENSTA ParisTech, France
  * José Creissac Campos, University of Minho, Portugal
  * Kenneth Lausdahl, Aarhus University, Denmark
  * Laurent Voisin, Systerel, France
  * Lucas Wagner, Collins Aerospace, USA
  * Makarius Wenzel, sketis.net
  * Markus A. Kuppe, Microsoft Research, USA
  * Mattias Ulbrich, Karlsruhe Institute of Technology, Germany
  * Pierre-Yves Strub, LIX, École Polytechnique, France
  * Rosemary Monahan, Maynooth University, Ireland
  * Silvia Lizeth Tapia Tarifa, University of Oslo, Norway
  * Simão Melo de Sousa, Universidade Beira Interior, Portugal
  * Stefan Mitsch, Carnegie Mellon University, USA
  * Stephan Merz, Inria, France
  * Virgile Prevosto, Institut List, CEA Tech, Université Paris-Saclay, France
  * Yannick Moy, AdaCore, France
  * Yi Zhang, Massachusetts General Hospital, USA

PC Chairs

  * Andrei Paskevich, Université Paris-Saclay, France
  * José Proença, CISTER/ISEP, Portugal

Steering Committee

  * Catherine Dubois, Samovar, ENSIIE, France
  * Paolo Masci, US National Institute of Aerospace (NIA), USA
  * Dominique Méry, LORIA, Université de Lorraine, France

                 reply	other threads:[~2020-10-19 17:11 UTC|newest]

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

Reply instructions:

You may reply publicly 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=20201019171108.GA1329691@tikki.lri.fr \
    --to=andrei@lri.fr \
    --cc=caml-list@inria.fr \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).