Open janWelte opened 11 years ago
Meeting at the 26.08.2014
Safety Tool Use Case Coordination
Participants: @vallee @jensgerlach @UweSteinkeFromSiemens @vgontier @MariellePetitDoche @janWelte
Objective: The meeting shall serve to identify use cases for provided safety analysis tools analyzing the SysML and SCADE models of openETCS. The resulting task shall be combined to a consistent work plan to analyze hazardous events, derive resulting safety properties and check models with respect to these safety properties.
Agenda:
This is not a specific All4tec activity. Contributions from all partners are organized in the global testing work scheduled managed by @MarcBehrens and @cecilebraun
Further coordination in WP 4 Wednesday meetings, when Cecile is back (End of September)
Operational validation with Matelo Matelo tool used to design usage models for validation. Depending on the facilities to generate random scenarios offered by the testing environment this method will be more or less representative of the operational life of the system.
[ ] Coordination with @MarcBehrens and @Nicolas-VanLandeghem how Matelo could be integrated
Further coordination shall be done in the general WP 4 Validation activities and in discussions with WP5.
Goal is to derive safety properties by an FMEA analysis with Safety Architect, which afterwards can be checked in the SCADE model by S3.
Next Steps
Further steps (planned to be performed after the follow-up meeting)
The meeting to propose and coordinate use case for safety analysis tools will be held Mo 15.09.2014 14:00 – 15:00 on go2meeting
Agenda:
a list of safety relevant requirements is needed for the design
relates to openETCS/product-backlog#31
grooming needed here @janwelte @fvallee @abdelnasirmohamed
a new SUBSET-091 has been released, see http://www.era.europa.eu/Document-Register/Pages/Set-2-Safety-Requirements-fo-the-Technical-Interoperability-of-ETCS-in-Levels-1-2.aspx
put on hold until October to focus on functional verification
Task: Development of Safety Requirements and Properties for Model VnV
Related to the following overall tasks:
6
Workscope:
Tasks to be done
System structure breackdown:
System functional breakdown:
Requirements for Functional Decomposition according to safety analysis
This shall be done for the following examples:
Examples of Kernel Hazards (from Subset-88 Part 3) a. KERNEL-6 Manage communication session failure (Related to model of Subset 26 §3.5.3 Establishing a communication session)
Detailed tasks in #44 and #50
b. KERNEL-9 Speed calculation underestimates train speed (Related to model of Subset 26 §3.13 Braking curves)
Detailed tasks in #45 and #49
c. KERNEL-19 Failure of train trip supervision in OS, LS and FS (Related to model of Subset 26 §5.9 Procedure On-Sight)
Detailed tasks in #46 and #51
Additional task to be done:
For the functional components:
@MerlinPokam @cyrilcornu @janwelte