1 / 14

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

openETCS : An evolution to formalized specification for non-interpretable application. openETCS@ITEA2 Project. Klaus-Rüdiger Hase. Istanbul, 01-03.04.2014. Objectives and major expected Outcomes. 1. Objectives. Model based Development F ramework. Software Tools. Set of. Tools. 2. 3.

glenda
Download Presentation

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

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

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

  2. Objectives and major expected Outcomes 1 Objectives Model based Development Framework Software Tools Set of Tools 2 3 Formal Specification Reference Unit 2014: openETCS Open License Terms apply

  3. ETCS EVC EVC EVC Vehicle Equipment 2 Vehicle Equipment 4 Vehicle Equipment 1 SRS “Prosa” Open Formal Specification openETCS Human Factor Human Factor Human Factor Human Factor Linus’ Law: “Many eyes make all bugs shallow” EVC Vehicle Equipment 3 2014: openETCS Open License Terms apply

  4. Prepare Project Management / Governance openETCS @ ITEA2 Project ITEA2Project Phases I (2011) II (2012-2013) III (2014-2015) VI (2016-2020) Organization Fundedby: openETCS Foundation e.V. openETCS Option Call M1 M2 M3 M4 M5 M6 Basics SW Tools (semi) Formal Specification Interfaces: STI / API Implemen-tation openETCS Reference OBU „Track Use Cases“ TCSim Prototype openETCS@ITEA2-Projekt 2014: openETCS Open License Terms apply

  5. https://github.com/openETCS http://www.openETCS.org openETCS openETCS 2014: openETCS Open License Terms apply

  6. Results D7.1 Results Tools Chain 2014: openETCS Open License Terms apply

  7. 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

  8. 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

  9. Long Term Availability of Software Tools? German ATP System (PZB): 1934 … 2050 ? TOPCASED sustainability thanks OSS Members of the Eclipse Foundation >100Years Very Long Term Support ? 78 Years Average Life Time forClosed Tools: ~ 10 Y ! 2014: openETCS Open License Terms apply

  10. ProcessInnovation SRCUM SCRUM CENELEC EN 50128 V Model & Role Model Phase Models ETCS OBU SW SIL 4 Software Development Agile vs. Waterfall & V-Model: 30% … 80% R&D Savings Sprint2 … 4 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

  11. Classic CENELEC V Model  Agile V Project Initialization & Monitoring Model EN 50128:2011 - 23 - SRS: Sprint Back Log Sprint2 … 4 Weeks Design Rules Tools 2014: openETCS Open License Terms apply

  12. HW EVC Vehicle Equipment “openIT4SR” Follow-up Project Outlook openETCS + open Corridor Legacy Systems Parameters • SW building blocks: • ETCS • ETCS+ • ETCS+ • ETCS+ • (Corridor Package) • PZB • PZB+ATB • PZB+ATB+SCMT PZB SCMT ATB otherclassB openETCS API FFFIS openSTM 2014: openETCS Open License Terms apply

  13. Prepare Project Management / Governance M7 M8 M9 openETCS Project Schedule Overview Phases I (2011) II (2012-2013) III (2014-2015) VI (2016-2018) Organization openETCS Foundation e.V. openETCS Option Call M1 M2 M3 M4 M5 M6 Basics Commercializing SW Tools (semi) Formal Specification  ERA, EUG, Railways Interfaces: STI / API Goal:  New Industrial Standard Implemen-tation openETCS Reference OBU Commercializing +openSTM „Track Use Cases“ Adoption ERTMS Users Gr. Commercializing TCSim Prototype openETCS@ITEA2-Projekt 2014: openETCS Open License Terms apply

  14. That was it … If you are interested in our work … • It’s open! • You can join at any time! • www.openETCS.org • ProjectOffice@openETCS.org • Thank you very much for your attention. 2014: openETCS Open License Terms apply

More Related