caml-list - the Caml user's mailing list
 help / Atom feed
From: Virgile Prevosto <virgile.prevosto@m4x.org>
To: undisclosed-recipients:;
Subject: [Caml-list] 3d Call for Papers F-IDE Workshop 2019 (Extended Deadlines)
Date: Thu, 20 Jun 2019 11:38:05 +0200
Message-ID: <CA+yPOVi7387WUhCfGCUqcOAQ4cUVn67nh6v16mEaff3EShFeLw@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 5651 bytes --]

F-IDE - 5th Workshop on Formal Integrated Development Environments

https://fideworkshop2019.inesctec.pt

part of FM Week 2019 (http://formalmethods2019.inesctec.pt/?page_id=84)

# News

We are happy to announce that Wolfgang Ahrendt (Chalmers University)
accepted to give the opening keynote at F-IDE 2019.

# Important Dates

- Abstract submission: July 2, 2019 (extended)
- Paper submission: June 9, 2019 (extended)
- Notification: August 20, 2019
- Camera-ready version: September 3, 2019
- Workshop date: October 7, 2019

# About F-IDE

High levels of safety, security and also 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/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.

# Submission Guidelines

Submitted papers should follow EPTCS 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

Two kinds of submissions will be considered: normal paper (15 pages
including bibliography), and shorter papers describing work in progress
and preliminary results (6 pages including bibliography). Submissions
will be made through EasyChair at:

https://easychair.org/conferences/?conf=fide2019.

All papers will be peer-reviewed by at least two members of the program
committee. They must describe original contributions whose main results
and conclusions have not been published or submitted elsewhere.
Preliminary proceedings, including all the papers selected for the
workshop, will be available electronically at the workshop. Post
proceedings will be proposed for publication with Electronic Proceedings
in Theoretical Computer Science (EPTCS).

# List of 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 automatic 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

# Committees
## PC Co-Chairs

    Rosemary Monahan, Maynooth University, rosemary (dot) monahan (at)
nuim (dot) ie
    Virgile Prevosto, Institut List, CEA Tech, Université Paris-Saclay,
virgile (dot) prevosto (at) cea (dot) fr
    José Proença, HASLab/INESC-TEC and Universidade do Minho, jose (dot)
p (dot) proenca (at) inesctec (dot) pt

## Steering Committee

    Catherine Dubois, Samovar / ENSIIE, catherine (dot) dubois (at)
ensiie (dot) fr
    Paolo Masci, HASLab/INESC-TEC and Universidade do Minho, paolo (dot)
masci (at) inesctec (dot) pt
    Dominique Méry, LORIA / Université de Lorraine, dominique (dot) mery
(at) loria (dot) fr

## Program Committee

    Cinzia Bernardeschi (University of Pisa)
    José Creissac Campos (University of Minho)
    Paul Curzon (Queen Mary University of London)
    Damien Doligez (INRIA)
    Andrea Domenici (University of Pisa)
    Carlo A. Furia (Chalmers University of Technology)
    Kenneth Lausdahl (Aarhus University)
    Stephan Merz (Inria Nancy)
    Stefan Mitsch (Carnegie Mellon University)
    Yannick Moy (Adacore)
    César Muñoz (NASA Langley)
    Andrei Paskevich (Université Paris-Sud, LRI)
    François Pessaux (ENSTA ParisTech)
    James Power (Maynooth University)
    Steve Reeves (University of Waikato)
    Bernhard Rumpe (RWTH Aachen University)
    Claudio Sacerdoti-Cohen (University of Bologna)
    Silvia Lizeth Tapia Tarifa (University of Oslo)
    Mattias Ulbricht (Karlsruhe Institute of Technology)
    Laurent Voisin (Systerel)
    Makarius Wenzel (sketis.net)
    Yi Zhang (U.S. Food and Drug Administration)

# Venue

The conference will be held in Porto (Portugal), as part of FM Week 2019

# Contact

All questions about submissions should be emailed to the PC co-chairs
(see contact information above).

-- 
E tutto per oggi, a la prossima volta
Virgile

[-- Attachment #2: Type: text/html, Size: 7480 bytes --]

                 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=CA+yPOVi7387WUhCfGCUqcOAQ4cUVn67nh6v16mEaff3EShFeLw@mail.gmail.com \
    --to=virgile.prevosto@m4x.org \
    /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