14
supported by: openETCS: An evolution to formalized specification for non-interpretable application Istanbul, 01-03.04.2014 Klaus-Rüdiger Hase openETCS@ITEA2 Project

Supported by: openETCS openETCS: An evolution to formalized specification for non-interpretable application Istanbul, 01-03.04.2014 Klaus-Rüdiger Hase

Embed Size (px)

Citation preview

Page 1: Supported by: openETCS openETCS: An evolution to formalized specification for non-interpretable application Istanbul, 01-03.04.2014 Klaus-Rüdiger Hase

supported by:

openETCS: An evolution to formalized specification for non-interpretable application

Istanbul, 01-03.04.2014

Klaus-Rüdiger Hase

openETCS@ITEA2 Project

Page 2: Supported by: openETCS openETCS: An evolution to formalized specification for non-interpretable application Istanbul, 01-03.04.2014 Klaus-Rüdiger Hase

Objectives

Objectives and major expected Outcomes

Formal Specification

Model based Development Framework

Set of

Reference Unit

ToolsSoftware Tools

1

2 32014: openETCS Open License Terms apply

Page 3: Supported by: openETCS openETCS: An evolution to formalized specification for non-interpretable application Istanbul, 01-03.04.2014 Klaus-Rüdiger Hase

EVC

Vehicle Equipment 2

Human Factor

EVC

Vehicle Equipment 3

Human Factor

EVC

Vehicle Equipment 4

Human Factor

EVC

Vehicle Equipment 1

Human Factor

ETCS SRS“Prosa”

Open Formal SpecificationopenETCS

Linus’ Law: “Many eyes make all bugs shallow”

2014: openETCS Open License Terms apply

Page 4: Supported by: openETCS openETCS: An evolution to formalized specification for non-interpretable application Istanbul, 01-03.04.2014 Klaus-Rüdiger Hase

Organization

Basics

Implemen-tation

I (2011) II (2012-2013) III (2014-2015)Phases VI (2016-2020)

openETCS@ITEA2-Projekt

Prepare Project Management / Governance

„Track Use Cases“

SW Tools

openETCS Option Call

M1 M5 M6M2 M3 M4

Interfaces: STI / API

(semi) Formal Specification

TCSim Prototype

openETCS Reference OBU

openETCS Foundation e.V.ITEA2Project

openETCS @ ITEA2 Project

Funded by:

2014: openETCS Open License Terms apply

Page 5: Supported by: openETCS openETCS: An evolution to formalized specification for non-interpretable application Istanbul, 01-03.04.2014 Klaus-Rüdiger Hase

https://github.com/openETCShttp://www.openETCS.org

2014: openETCS Open License Terms apply

Page 6: Supported by: openETCS openETCS: An evolution to formalized specification for non-interpretable application Istanbul, 01-03.04.2014 Klaus-Rüdiger Hase

Tools Chain

Results

D7.1 Results

2014: openETCS Open License Terms apply

Page 7: Supported by: openETCS openETCS: An evolution to formalized specification for non-interpretable application Istanbul, 01-03.04.2014 Klaus-Rüdiger Hase

git on GitHub

Eclipse Modeling Framework

ProR

SysML + Papyrus

semi-formal specification & modelling

Artefacts “openETCS Open License Terms”

Key results: openETCS Tools Chain (1)

2014: openETCS Open License Terms apply

Page 8: Supported by: openETCS openETCS: An evolution to formalized specification for non-interpretable application Istanbul, 01-03.04.2014 Klaus-Rüdiger Hase

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

Key results: openETCS Tools Chain (2)

2014: openETCS Open License Terms apply

Page 9: Supported by: openETCS openETCS: An evolution to formalized specification for non-interpretable application Istanbul, 01-03.04.2014 Klaus-Rüdiger Hase

Very Long Term Support

?

Members of the Eclipse FoundationTOPCASED sustainability thanks OSSLong Term Availability of Software Tools?German ATP System (PZB): 1934 … 2050 ?

>100

Years78 YearsAverage Life Time for

Closed Tools: ~ 10 Y !

2014: openETCS Open License Terms apply

Page 10: Supported by: openETCS openETCS: An evolution to formalized specification for non-interpretable application Istanbul, 01-03.04.2014 Klaus-Rüdiger Hase

SCRUM

Sprint2 … 4 WeeksProcess

Innovation

CENELEC EN 50128 V Model & Role Model

SIL 4 Software Development

SRCUM

Incremental step by step development in 2-4 weeks sprints by self-managed teams.

ETCS OBU SW

~45% probability of projects failing

Phase Models

2014: openETCS Open License Terms apply

Agile vs. Waterfall & V-Model:

30% … 80% R&D

Savings

Page 11: Supported by: openETCS openETCS: An evolution to formalized specification for non-interpretable application Istanbul, 01-03.04.2014 Klaus-Rüdiger Hase

- 23 - EN 50128:2011

Classic CENELEC V Model Agile V

2014: openETCS Open License Terms apply

Design Rules

Project Initialization & Monitoring

Model

Tools

SRS: Sprint Back Log

Sprint2 … 4 Weeks

Page 12: Supported by: openETCS openETCS: An evolution to formalized specification for non-interpretable application Istanbul, 01-03.04.2014 Klaus-Rüdiger Hase

OutlookopenETCS

SW building blocks:ETCSETCS+ETCS+ETCS+(Corridor Package)

PZB PZB+ATB PZB+ATB+SCMT

EVC

Vehicle Equipment

FFFIS

API

HW

Parameters

“openIT4SR” Follow-up Project

PZB

SCM

TAT

B

openETCS + open Corridor Legacy Systems

openSTM

otherclassB

2014: openETCS Open License Terms apply

Page 13: Supported by: openETCS openETCS: An evolution to formalized specification for non-interpretable application Istanbul, 01-03.04.2014 Klaus-Rüdiger Hase

openETCS Project Schedule Overview

Organization

Basics

Implemen-tation

openETCS@ITEA2-Projekt

I (2011) II (2012-2013) III (2014-2015)Phases

Prepare Project Management / Governance

„Track Use Cases“ Adoption ERTMS Users Gr.

SW Tools

ERA, EUG, Railways

openETCS Option Call

M1 M5 M6M2 M3 M4 M9M7 M8

VI (2016-2018)

Commercializing

Goal: New Industrial Standard

openETCS Foundation e.V.

Interfaces: STI / API

(semi) Formal Specification

Commercializing

Commercializing TCSim Prototype

openETCS Reference OBU+openSTM2014: openETCS Open License Terms apply

Page 14: Supported by: openETCS openETCS: An evolution to formalized specification for non-interpretable application Istanbul, 01-03.04.2014 Klaus-Rüdiger Hase

That was it …

Thank you very much for your attention.

If you are interested in our work …

It’s open!

You can join at any time!www.openETCS.org

[email protected]

2014: openETCS Open License Terms apply