Testing Telco: Agenda and Results

This page provides an overview for the testing activities mainly covered during the testing telco of the openETCS WP 4 Validation and Verification workpackage.

Weekly Testing Telco 31.07.2013

This telco addressed the V&V plan

• The first version of the plan will be finalised for review tomorrow (01 August)
• DLR: (Hardi) will htrow out editorial remarks, edit Ch 4 (Strategy)and 5.1 (Verification Overview)
• TUBS: Add the safety aspect
• DB (Baseliyos): Suggest how to describe operator requirements
• AEBT (Merlin): Proposal for definition of V&V documents needed for certification
• TWT, UHB, SIE: Planned verification activities in the first level (6.1.3.1, 6.1.4)
• DLR (Marc): Schedule, Validation environment, interfaces
• Volunteers (not assigned): Revision of Ch. 3, Sec. 5.3, 5.4, 5.5

Weekly Testing Telco 24.07.2013

This telco mainly addressed the V&V plan

• Main contributions from SQS and U Bremen
• Part of the SQS material for Ch. 6 fits better in Ch.5. Ainhoa, Izaskun and Hardi will clarify this
• U Bremen: Detailed plans for more input to Ch. 6
• DLR: Add simulation environment description (for validation purposes)
• DLR: Add sections to Ch. 6 for partner contributions
• SQS: Further material in preparation
• all partners active in V&V: Detail Ch. 6
• DLR: Make the text more accessible by spelling out abbreviations

Other issues:

• U Bremen needs urgently a description of the track simulation interface

Weekly Testing Telco 10.07.2013

Participants	Company
Ainhoa Gracia	SQS
Alexander Nitsch	Uni-Rostock
Benjamiin Beichler	Uni-Rostock
Cecile Braunschtein	Uni - Bremen
Cyril Cornu	All4Tec
Izaskun de la Torre	SQS
Jens Gerlach	Fraunhofer
Marielle Petit-Doche	Systerel
Stefan Rieger	TWT
Uwe Steinke	Siemens

Follow up of last week

The following topics were identified last week to be addressed:

• Parameters concerning the functions to be integrated into tests
• Environment model
• Train dynamic behavior model (Validation)
  • Needed for generating dynamic/ static speed profile for test cases

Agenda this week’s Wednesday Testing Telco

The following point were identified for this weeks meeting: • VnV activities for 1st level VnV + Test Setup + Test Environment + Test Interfaces + Parameters concerning the functions to be integrated into tests • Environment model • Train dynamic behavior model (Validation) • Needed for generating dynamic/ static speed profile for test cases

• Coordination on the following models and parameters is identified:
  • Identify the messages/ radio primitives within the model to be used for testing (Uwe+Marc)
  • Identify what to test within braking curves (Benjamin + Stefan + Marc)
  • Identify what to test on the DMI (Marielle will come back on this)
  • work on demonstrator (Cyril+Alexandre+Matieu)
  • Deliver SSRS input for testing and coordinate CH3.5 contribution, initialte implementation with Patrick (Basileyios)

Next Steps:

• Further details on which parameter to use for testing are to be identified
• Test environment and models should be made fit for testing

The following issues were postponed for 2nd level VnV

• Environment model
• Train dynamic behavior model (Validation)
  • Needed for generating dynamic/ static speed profile for test cases

Weekly Testing Telco 10.07.2013

Participants	Company
Alexander Nitsch	Uni-Rostock
Bernd Hekele	DB
Benjamin Beichler	Uni-Rostock
Cecile Braunstein	Uni-Bremen
Frank Golatowski	Uni-Rostock
Hardi Hungar	DLR
Jan Welte	TU-BS
Jens Gerlach	Fraunhofer
Marielle-Petit Doche	Systerel
Marc Behrens	DLR
Uwe Steinke	Siemens

Follow up of last week

• Telco was held in parallel of the ITEA2 review meeting in Paris.

  • The Issues concerning the VnV plan were taken up

• Results of the WP 7 workshop concerning testing: The priority of the 1st VnV level has been identified:

  • WP4 will do complete run through the full VnV process.
    • This includes all activities concerning verification for at least a few functional properties.
    • This includes preparing activities concerning validation for at last the setup of the operational scenarios.
  • The overall Verification and Validation process shall be reached in three steps:
    1. Goal: full artifacts traceability, common meta-formats
    2. Goal: test and proof coverage
    3. Goal: Complete VnV level 1 process

The Verification and Validation artifacts have to be developed to cover these three steps.

Agenda this week’s Wednesday Testing Telco

1. Status of writing the VnV plan.

Please contribute directly to github using the following links:

• Verification & Validation Plan: LaTeX-Source

• Verification & Validation Plan: PDF-Document

Hardi explains the Verification User Story as described within the VnV plan. The contributions is coordinated via the GITHUB issue tracker. The VnV plan differentiates between the verification and validation of the complete development described in chapter 5 and the verification and vlaidation carried out within the openETCS project detailed within chapter 6. In chapter 5 all questions according to FLOSS should be adressed, like >'how open is your tool?' whereas in chapter 6 the question how you will apply the tool should be adressed.

2. Results from the 4.7.2013 WP7 Workshop

• 3 principles for integrating artifacts into the verification level 1 see slides:

  1. Transformation-/constraints- proof
  2. Using the same artifact as input & having integrable outputs
  3. Common Message Based Tests

• Definition of DAS2V - Design Artifacts Subject to Verification: All relevant artifacts that are part of the development and subject to verification.

3. Preparing VnV level 1

Models:

SysML model Papyrus by CEA and All4tec

Fraunhofer

[Scade model by Siemens] (https://github.com/openETCS/model-evaluation/tree/master/model/SCADE_Siemens/Subset_026_Chapt_3.5_ManagementOfRadioCommunication/Generated_C_Code)

• Priorities concerning the VnV artifacts and the needed tools (secondary tool chain decision)

• Process and artifacts Based on the VnV decision presented on the WP7 workshop last week in Paris, the verification activities shall be applied on the SysML and the SCADE models.

Proposed process:

1. Functionality from Subset-026 Table 4-5 (Relevant for VnV and SSRS input) A SSRS description for these functionalities is needed for the verificatoin. Possible functionality agreed on during the telco:

The following functionalities were identified as possible relevant vor VnV level1.

           a.	Manage Communication Session (Subset-026-3.5)

           b.	Speed and Distance Monitoring based on MRSP (Subset026-3.13)

           c.	Determine ERTMS/ETCS Mode (Subset-026-4.6.2.1)
                    Coming from SB using the transition conditions: 1, 10, 5, 6, 50

           d.	Procedure Onsight (Subset-026-5.9)

2. Defining system requirement relevant for VnV

3. Idetnify I/Os (Part of the SSRS work)

4. Select method and tool to test, check or proof on every development artifact (high level model, low level model, source code)

5. Demonstrate traceability from functionality up to validation of property

6. Generate tests and test functionality

7. Evaluate verdict

8. Write/ generate report

4. Other issues

Next Steps:

• Parameters concerning the functions to be integrated into tests
• Environment model
• Train dynamic behavior model (Validation)
  • Needed for generating dynamic/ static speed profile for test cases

Verification activities will work according to the first VnV level plan and use the SysML Papyrus and the SCADE models to apply and further develop the openETCS verification process