caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: geoff@cs.miami.edu
To: <caml-list@inria.fr>
Subject: [Caml-list] FMCAD 2017: CALL FOR PARTICIPATION
Date: Mon, 28 Aug 2017 09:42:09 -0400 (EDT)	[thread overview]
Message-ID: <20170828134209.280581700F04@cs.miami.edu> (raw)

FMCAD 2017: CALL FOR PARTICIPATION

International Conference on
Formal Methods in Computer-Aided Design (FMCAD)
TU Wien, Vienna, Austria, October 2-6, 2017

http://www.fmcad.org/FMCAD17

FMCAD Tutorial Day:             October 2, 2017
FMCAD Regular Program:          October 3-6, 2017

Part of the FMCAD 2017 program:
- FMCAD Student Forum
- Hardware Model Checking Competition 2017
- Symposium in memoriam of Helmut Veith

Co-located event: MEMOCODE 2017 (http://memocode.irisa.fr/2017/)

CONFERENCE SCOPE

FMCAD 2017 is the seventeenth in a series of conferences on the theory and
applications of formal methods in hardware and system verification. FMCAD
provides a leading forum to researchers in academia and industry for
presenting and discussing ground-breaking methods, technologies, theoretical
results, and tools for reasoning formally about computing systems. FMCAD
covers formal aspects of computer-aided system design including
verification,
specification, synthesis, and testing.

REGISTRATION

Early Registration Deadline: September 02, 2017
Registration Deadline: September 29, 2017

Registration details are available on
http://fmcad.org/FMCAD17/registration

TECHNICAL PROGRAM

The program comprises presentations of 25 regular papers and 4 tool
papers, 3 tutorials and 2 keynotes, a student forum, the Hardware
Model Checking Competition, and a symposium in memoriam Helmut Veith.
Details are available on the web-site: http://fmcad.org/FMCAD17

KEYNOTES

- Byron Cook (Amazon, University College London)
  "Formal Verification, Model Checking, and Constraints
   for Security of the Cloud"

- Wilfried Steiner (TTTech)
  "Formal Methods in Industrial Dependable Systems Design"

TUTORIALS

- Shin'ichiro Matsuo (MIT Media Lab/CELLOS Consortium/BSafe.network)
  "How Formal Methods and Analysis Helps Security of Entire
   Blockchain-based Systems"

- Cas Cremers (Oxford University)
  "Symbolic Security Analysis using the Tamarin Prover"

- Jade Alglave (Microsoft Research, University College London)
  "Consistency Properties of Parallel/Distributed Programs in cat"

STUDENT FORUM AND HELMUT VEITH SYMPOSIUM

The FMCAD student forum consists of short presentations and posters
of doctoral students presenting their work-in-progress.

The Symposium in memoriam Helmut Veith features talks on
model checking, synthesis, distributed algorithms, and security,
as well as a LogicLounge on Teaching Logic in Computer Science.

SPONSORS

- Sponsored by FMCAD, Inc.
- Technical Co-sponsor: IEEE
- In-cooperation with: ACM SIGPLAN/SIGSOFT

- Financial support: Amazon, ARM, BMVIT, Centaur Technology, DiffBlue,
  Galois, Microsoft, NSF, Oski Technology, Real Intent, Synopsys,
  TTTech, WWTF


                 reply	other threads:[~2017-08-28 14:59 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=20170828134209.280581700F04@cs.miami.edu \
    --to=geoff@cs.miami.edu \
    --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).