Presentation is loading. Please wait.

Presentation is loading. Please wait.

Thank you Mr. Chairman, Ladies and gentlemen,

Similar presentations


Presentation on theme: "Thank you Mr. Chairman, Ladies and gentlemen,"— Presentation transcript:

1 openETCS: An evolution to formalized specification for non-interpretable application
Thank you Mr. Chairman, Ladies and gentlemen, My today’s talk is about: “openETCS: An evolution to formalized specification for non-interpretable application” Last Conference in Stockholm I had the opportunity first time to present this idea of an openETCS project, while we were still waiting for funding. This time we are right in the middle of a European project under the ITEA2 frame work and I am pleased for this opportunity to present the actual status. Project Klaus-Rüdiger Hase Istanbul,

2 Objectives and major expected Outcomes
1 Objectives Model based Development Framework Set of Tools Software Tools 2 3 Lets do a quick recap to remind The major goals and expected results are: A Model based Development Frame work, With a set of tools. Software tools of cause Instead of a prose spec, we want to create a formal specification, that can be modelled, with the modelling Framework. And from the formal spec, using the Tools from the Framework, we want to create a reference Software in a reference unit, like the original meter or kilogram. We do this, to come to true interoperability and get the cost down, especially for software production. Formal Specification Reference Unit 2014: openETCS Open License Terms apply

3 Linus’ Law: “Many eyes make all bugs shallow”
ETCS SRS “Prosa” openETCS Open Formal Specification EVC Vehicle Equipment 1 Human Factor EVC Vehicle Equipment 2 Human Factor EVC Vehicle Equipment 3 Human Factor EVC Vehicle Equipment 4 Human Factor Linus’ Law: “Many eyes make all bugs shallow” As we said, the SRS cannot be taken as a product design specification directly. Experts in each company are needed to create such product design specification, what they do independently today. We want to have these experts, to better work together. Create a common formal specification for the software, which keeps the functionality. And from that, all manufacturer can use their own design. 2014: openETCS Open License Terms apply

4 openETCS @ ITEA2 Project
Organization Basics Implemen-tation I (2011) II ( ) III ( ) Phases VI ( ) Prepare Project Management / Governance Funded by: openETCS Foundation e.V. openETCS Option Call M1 M2 M3 M4 M5 M6 SW Tools (semi) Formal Specification Interfaces: STI / API This is our openETCS consortium. These are the contries with participating partners. This is our project information sheet: It started in July 2012 and is scheduled for June 2015 to end. We have about 150 man years and about 19 million in our budget. The project is funded by France, Germany, Belgium and Spain. Looking at our time-line: On the organizational level we have the project organization and the IPR will the be taken over by the openETCS Foundation, a not-for-profit organization, all stake holders can be represented in. The Basic R&D activities are for tools, formal specification / modelling and interfaces The next layer takes care of implementation openETCS Reference OBU „Track Use Cases“ TCSim Prototype 2014: openETCS Open License Terms apply openETCS Open License Terms apply, 6/26/2013

5 openETCS openETCS https://github.com/openETCS http://www.openETCS.org
This is our Web-Site. It is our work bench. It’s not a beauty, but quite efficient. Just get to “projects” From there to “Tools Chain” 2014: openETCS Open License Terms apply openETCS Open License Terms apply, 6/26/2013

6 Results D7.1 Results Tools Chain
That brings us to results; one of our first big mile stones. On this repository you can find that “Report on the final Primary Toolchain” Why we are talking about “Tool CHAIN”? Since we have to go through several steps, it is important that the results from step one can be directly used as input for step 2 and so forth. 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” These are our Key Results on the openETCS Tools Chain: We are working with Git on GitHub an absolutely state of the art distributed version control system, it is open source, We are using the Eclipse Modeling Framework, from the largest professional open source community, ProR is our speciation and traceability tool, open source, and compliant with ReqIF for interchange with other tools e.g. DOORS and others. Modelling language SysML and will be used with Papyrus tool, again open source, basically a French development This allows us to do semi-formal specification and modelling All Artefacts are licensed under the “openETCS Open License Terms, a combination from CC-By-SA and EUPL v1.1. So that was the good news. 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 Unfortunately there is a little sad news: The results of our research could not find a SysML- compatible strictly formal Tool in open source software. Yes there are OSS tools out there, which can handle strict syntax as well as strict semantics, but they are either very special or they cover only a very limited part of the over-all functionality, or they do not find wide acceptance, or in almost all cases, they were not compatible with SysML. However: Work on “Formal Specification” and “Reference OnBoard Unit” could not wait any longer. Therefore we have decided to start with a partly Closed Source Tool, that is SCADE SUITE, which works together with Papyrus, is actually using Papyrus and provides at least open Formats for all Artefacts. It comes with excellent visualization features and has a certified code generator. The good news is: SCADE SUITE is certified for CENELEC SIL 4 development. So we have a high quality tools chain – no compromise with the quality and well accepted in the industry. The Lustre language is an open synchronous data flow programming language, good for reactive systems, what ETCS OBU really is. SCADE then provides a graphical interface. So then: What about the “open Proofs”?: For the Very-Long-Term SW-Support we have decided to go with PolarSys. A CCS to OSS tools migration together with PolarSys, a special working group for open source tools. 2014: openETCS Open License Terms apply

9 TOPCASED sustainability thanks OSS
Long Term Availability of Software Tools? German ATP System (PZB): 1934 … 2050 ? Members of the Eclipse Foundation TOPCASED sustainability thanks OSS >100 Years Very Long Term Support ? 78 Years Average Life Time for Closed Tools: ~ 10 Y ! Looking at our German legacy ATP system, the PZB. It started in 1934 and we expect an end of life in around 2050. That is more than 100 years. Same problems with avionics There it is a about 78 years. But looking at the tools life-cycle, we see an average of 10 years. However an open source approach can deal with it. 2014: openETCS Open License Terms apply

10 Agile vs. Waterfall & V-Model: 30% … 80% R&D Savings
SRCUM Phase Models CENELEC EN V Model & Role Model SCRUM ETCS OBU SW Process Innovation Sprint 2 … 4 Weeks Agile vs. Waterfall & V-Model: 30% … 80% R&D Savings SIL 4 Software Development Incremental step by step development in 2-4 weeks sprints by self-managed teams. In order to get Software Cost down, we need “Process Innovation”. Today almost all Software for ETCS is written according to CENELEC EM50128 recommendation following the V-Model, which is just a wrapped-up “Waterfall”. Research, done by the Standish Group showed, that, “Waterfall”, beginning in the 80th, has not a good track record when comes to project risks, especially for larger software projects. Projects in the order of function points – that is where we are with ETCS OBU software – have risk of total failure of almost 50%, running over budget and time is even higher. We all know this. Already in 1986 an article “The New New Product Development Game” in the Harvard Business Review, by Professor Takeuchi and Nonaka, demonstrated that things can be different. They showed that traditional sequentially working – first making a big plan, then doing all the specification, then designing, then testing - not only takes longer, but due to lack of communication between these phases, quality is bad and failure risk is high. Even small overlap improves the situation, but higher flexibility with the specification phase and so on makes it even better. They recommended the so called “Rugby” solution, a team based agile approach, which later was called SCRUM. This is a team-oriented incremental approach, which is based on self managed teams that works in fixed time units, called “Sprints” mostly of 2 to 4 weeks. Every sprint another increment of the software is produced that is ready to use, and is presented to the end customer. They feed back is essential for the next Sprint. Today we know that this SCRUM approach can not only increase productivity by 30% to 80% or even higher, but also reduces risk of failure and improves quality, simply because of better communication and self-determination, away from traditional management. BUT: How to apply that to CENELEC? ~45% probability of projects failing  2014: openETCS Open License Terms apply

11 Classic CENELEC V Model  Agile V
Project Initialization & Monitoring Model - 23 - EN 50128:2011 SRS: Sprint Back Log Sprint 2 … 4 Weeks Design Rules Tools If we want certification, we need to map the CENELEC heavy V-Model to an agile process, we call it “Agile-V”. Looking at the upper part of the “V”: We first identify activities that can be done outside the sprints. Maintenance can be taken out at all, since just continuing this process takes care for continues maintenance. So that is something that we can do upfront or beside the sprint cycles. Looking at the lower part of the “V”: All those items can be covered by the code generating tools of the openETCS Tools Chain. Some activities in the middle can also be taken care I some design rules. Then the specification and software validation phase, that is also covered by our openETCS Modelling tools and the Model as well. Makes it a handsome Agile-V that can be worked within for tools supported incremental design an verification and validation for each increment. Documents? No problem if they are considered like any other deliverable for each cycle. Now we also see that this is perfect for maintenance. 2014: openETCS Open License Terms apply

12 Outlook HW SCMT other classB open ETCS PZB ATB Parameters API FFFIS
“openIT4SR” Follow-up Project openETCS + open Corridor Legacy Systems Outlook Parameters PZB PZB+ATB PZB+ATB+SCMT SW building blocks: ETCS ETCS+ (Corridor Package) other classB open ETCS PZB ATB SCMT API HW EVC Vehicle Equipment Giving an Outlook After 2015 we want to continue commercialize our results, that also means not just a demonstrator, but completing the ETCS OBU functionality to version 3.5 or 3.6 or whatever it will be. However we also want to apply the same methodology and principles to some selected class B systems. Doing it with PZB, ATB and SCMT would make it a “Corridor Package” that covers all needs along Corridor 1 (former A). But you could leave away the ETCS functionality and get an – what we call “openSTM” that could be connected to any ETCS OBU on the market and would eliminate the market barriers still in place due to legacy technology and legacy closed market understanding. FFFIS openSTM 2014: openETCS Open License Terms apply

13 openETCS Project Schedule Overview
Phases I (2011) II ( ) III ( ) M7 VI ( ) Organization Prepare Project Management / Governance openETCS Foundation e.V. openETCS Option Call M8 M9 M1 M2 M3 M4 M5 M6 Basics SW Tools Commercializing (semi) Formal Specification  ERA, EUG, Railways Interfaces: STI / API Goal:  New Industrial Standard Implemen-tation That is what our Schedule looks like. We want to use the following 2 to 2 and a half years to further develop the consortium into a real open source “Eco-System” and commercialize the results from the first phase. Then we add the openSTM features, using same tools, processes and methods developed in the first phase. The Tools activities are planned cooperate with the POLARSYS working group in Eclipse, to team up with tools producers from aviation, automotive and so on and take care for the rail sector. We offered those ideas to Shift to Rail, but still waiting for a positive response. BUT ANYWAY …. openETCS Reference OBU Commercializing +openSTM „Track Use Cases“ Adoption ERTMS Users Gr. TCSim Prototype Commercializing 2014: openETCS Open License Terms apply openETCS Open License Terms apply, 6/26/2013

14 If you are interested in our work …
That was it … If you are interested in our work … It’s open! You can join at any time! Thank you very much for your attention. If you are interested in our work … It’s open! You can join at any time! go to : Or write us: ----- That is all for today … Thank you for your attention. 2014: openETCS Open License Terms apply openETCS Open License Terms apply, 6/26/2013


Download ppt "Thank you Mr. Chairman, Ladies and gentlemen,"

Similar presentations


Ads by Google