From: Alexander Romanovsky <alexander.romanovsky@newcastle.ac.uk>
To: Alexander Romanovsky <alexander.romanovsky@newcastle.ac.uk>
Subject: [Caml-list] CfPart: Int. Conference on Reliability, Safety and Security of Railway Systems
Date: Fri, 25 Mar 2016 09:33:33 +0000 [thread overview]
Message-ID: <E37F21AA-1805-43E8-89BA-06387F4EA8DB@newcastle.ac.uk> (raw)
International Conference on
Reliability, Safety and Security of Railway Systems:
Modelling, Analysis, Verification and Certification
http://conferences.ncl.ac.uk/rssrail/
28-30 June 2016
Espace du Centenaire, Maison de la RATP, Paris, France
Call for Participation
Conference Aims:
* to bring together researchers and developers
* to ensure that advances in research are driven by the real needs of the railway
* to help develop technology that is usable, scalable and deployable
* to support the provision and utilisation of advanced methods and tools
* to present novel methods for modelling, analysis, verification and validation
* to identify mechanisms and procedures which support evidence cases
that standards are being met
Challenges:
* to improve railway system safety, security and reliability
* to reduce production cost, time to market and running costs
* to increase system capacity and reduce carbon emissions
Context:
* integration of railway systems into larger multi-mode transport networks
* dramatic increases in the complexity of railway applications
* ever higher degree of automation
The conference will feature three invited keynote talks, from eminent
and experienced investigators:
Robin Bloomfield, Adelard LLP and City University London (UK)
The risk assessment of ERTMS based railway systems from a cyber perspective:
methodology and lessons learnt
Denis Sabatier, ClearSy (France)
Using formal proof and B method at system level for industrial projects
Jan Peleska, University of Bremen and Verified Systems (Germany)
A novel approach to HW/SW integration testing of route-based interlocking
system controllers
And the invited presentation by Claude Andlauer, Head of Rail Transport for RATP (France)
Formal methods as part of RATP’s DNA
Specific topics to be presented at RSSRail 2016 will include:
* failure analysis,
* interlocking verification,
* formal system specification and refinement,
* security analysis of ERTMS,
* safety verification,
* formalisation of requirements,
* proof automation,
* operational security,
* railway system reliability,
* risk assessment for ERTMS,
* verification of EN-50128 safety requirements.
For more details on the keynote talks, and on the individual papers to be presented,
please visit the website: http://conferences.ncl.ac.uk/rssrail/programme/
The proceedings are published by Springer.
There is still an opportunity to submit a poster - closing date: 1 May 2016. The conference
will include a selected poster and vendor exhibition.
Registration: http://conferences.ncl.ac.uk/rssrail/registration/
next reply other threads:[~2016-03-25 9:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-25 9:33 Alexander Romanovsky [this message]
2016-04-12 21:15 Alexander Romanovsky
2016-05-10 13:22 Alexander Romanovsky
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=E37F21AA-1805-43E8-89BA-06387F4EA8DB@newcastle.ac.uk \
--to=alexander.romanovsky@newcastle.ac.uk \
/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