Transcript openETCS
openETCS: An evolution to formalized
specification for non-interpretable application
supported by:
openETCS@ITEA2 Project
Klaus-Rüdiger Hase
Istanbul, 01-03.04.2014
Objectives and major expected Outcomes
1
Model based
Development Framework
Software Tools
Set of Tools
Objectives
2
Formal
Specification
2014: openETCS Open License Terms apply
3
Reference Unit
ETCS
SRS
“Prosa”
Open Formal
openETCS
Specification
Human
Factor
Human
Factor
Human
Factor
Human
Factor
“Many eyes
make all bugs shallow”
Linus’ Law:
EVC
EVC
EVC
EVC
Vehicle
Equipment 1
Vehicle
Equipment 2
Vehicle
Equipment 3
Vehicle
Equipment 4
2014: openETCS Open License Terms apply
openETCS @ ITEA2 Project
Phases
I (2011)
II (2012-2013)
III (2014-2015)
ITEA2
Project
Prepare
Project Management / Governance
Funded by:
Organization
VI (2016-2020)
openETCS
Option Call
openETCS Foundation e.V.
M1
M2
M3
M4
M5
M6
SW Tools
Basics
(semi) Formal Specification
Interfaces: STI / API
openETCS Reference OBU
Implementation
„Track Use Cases“
TCSim Prototype
openETCS@ITEA2-Projekt
2014: openETCS Open License Terms apply
http://www.openETCS.org
https://github.com/openETCS
2014: openETCS Open License Terms apply
D7.1
ToolsResults
Chain
Results
2014: openETCS Open License Terms apply
Key results: openETCS Tools Chain (1)
git on GitHub
Eclipse Modeling Framework
ProR
SysML + Papyrus
semi-formal specification & modelling
Artefacts “openETCS Open License Terms”
2014: openETCS Open License Terms apply
Key results: openETCS Tools Chain (2)
Result of our OSS Tools “Market” research:
SysML- compatible strict formal Tools not yet in OSS
“Formal Spec.” & “Ref. OBU SW” cannot wait !
Start with
SCADE
input from Papyrus
• Certified for CENELEC EN50128 SIL 4 development
• Widely accepted in industry (avionics, rail, process control)
• “Lustre”: Synchronous data flow programming language
Migration plan CSS OSS via
2014: openETCS Open License Terms apply
Long
German
Term
ATP
Availability
System
(PZB):
of Software
1934 …Tools?
2050 ?
Members
of
the
Eclipse
Foundation
TOPCASED sustainability thanks OSS
Very Long Term
Support
Years
Years
?
2014: openETCS Open License Terms apply
SW
SCRUMModels
Phase
CENELEC
EN 50128 V Model &ETCS
RoleOBU
Model
SRCUM
SIL 4 Software Development
Sprint
Agile
vs.
2…4
Process
Waterfall & V-Model:
30% … 80% R&D
Innovation
Savings
Weeks
Incremental step by
step development in
2-4 weeks sprints by
self-managed teams.
~45% probability of projects failing
2014: openETCS Open License Terms apply
Classic CENELEC V Model Agile V
EN 50128:2011
- 23 -
Model
Project
InitializationSprint
& Monitoring
SRS: Sprint
Back Log
2…4
Design Rules
Weeks
Tools
2014: openETCS Open License Terms apply
“openIT4SR” Follow-up Project
openETCS + open Corridor Legacy Systems
Parameters
other
open
class
B
ETCS
PZB
ATB
SCMT
SW building blocks:
ETCS
ETCS+PZB
ETCS+PZB+ATB
ETCS+PZB+ATB+SCMT
(Corridor Package)
Outlook
FFFIS
openSTM
EVC
Vehicle Equipment
2014: openETCS Open License Terms apply
API
HW
openETCS Project Schedule Overview
Phases
I (2011)
Prepare
II (2012-2013)
III (2014-2015)
VI (2016-2018)
Project Management / Governance
Organization
openETCS Foundation e.V.
openETCS
Option Call
M1
M2
M3
M4
M5
M6
(semi) Formal Specification
openETCS Reference OBU
ERA, EUG, Railways
Commercializing
„Track Use Cases“ Adoption ERTMS Users Gr.
TCSim Prototype
openETCS@ITEA2-Projekt
2014: openETCS Open License Terms apply
M9
Goal: New Industrial Standard
Interfaces: STI / API
Implementation
M8
Commercializing
SW Tools
Basics
M7
Commercializing
That
If
youwas
are itinterested
…
in our work …
It’s open!
Thank you very much
Youfor
can
join
at
any
time!
your attention.
www.openETCS.org
[email protected]
2014: openETCS Open License Terms apply