-
Notifications
You must be signed in to change notification settings - Fork 22
Project Management
- Verification:
- The first draft results to the verified Artifacts can be found on github concerning: The API Specification from Alstom and a XML-Design for packet layout from Siemens.
- The evaluation criteria on Verification & Validation are currently in work (not yet released).
- Validation:
-
- Safety/ Process:
- The evaluation criteria on safety are currently in work (not yet released).
Agenda Friday SCRUM- Telco:
- Short sum up of result of API top level verification
- Collection on questions/ open points on the API
- Status of evaluation criteria
- In preparation of the workshops coming up:
- Pre- qualification of V&V model
- Which model to take from the model evaluation for the V&V process qualification
- Preparing the first V&V phase coming up
- Collection of aspects for modularization of the model
- preparing the SSRS kick-off at the 24th of April
- Information, expectations, input
- Verification:
- There are already two design artifacts which can be verified: The API Specification from Alstom and a XML-Design for packet layout from Siemens
- The Evaluation criteria as a preliminary version has been discussed, please find a first draft attached.
- Validation:
-
- Safety/ Process:
- The ownership of the QA document is handed over to SQS
- Workshop on Safety in Charleroi on the 29th and 30th of May 2013.
- Telephone Conference on V&V Process Synchronization on the 26th of May 2013.
Meeting minutes of the openETCS Workshop on API, Requirements and Safety Strategy taken place in Paris from 2013-03-11 to 2013-03-13 can be found on github.
- There you can find decisions taken as well as detailed questions and answers for each day of the workshop.
- Please be sure to read the refined project priorities concluded in the last timeslot of the 2013-03-12 meeting minutes.
- The review on the meeting minutes will be open until 2013-04-11 – shortly before the Munich workshop. Please contribute directly to github or send me an e-mail.
Meeting minutes for the Telephone Conference on V&V Process Synchronization from 26.03.2013 can be found on github and as LaTeX source for review
- Please not that at this meeting it was identified that Subset-026 does not only cover on-board parts but also trackside parts.
- The need of a trackside data-preparation-model was identified.
Agenda Friday SCRUM- Telco:
- Results from Telephone Conference on V&V Process Synchronization
- Results from the workshop on safety in Charleroi
- In preparation of the workshops coming up:
- V&V Evaluation Criteria (See proposal attached)
- Evaluation Criteria on Safety
- Concept for design verification:
- Verification approach of the API
- Verification approach of the XML-Design
-
Verification:
-
At this week’s un-conference intelligent formal V&V tools and approaches were shown e.g.:
- FRAMA-C showing its capacity for code verification on
- Abstract interpretation for value analysis
- Deductive Verification e.g. · Theorem proving · Programming by contract · Loop termination
- SCADE with its modelling capabilities including an open source architecture tool based on papyrus
- FRAMA-C showing its capacity for code verification on
-
Validation:
-
As outcome from the SSRS Kick-off: The SSRS will be validated for business/ operational aspects – this will be led by SNCF
-
Safety/ Process:
-
A ‘Tool-Artifacts-Matrix’ has been reviewed and filled out for the following tools:
- RT-Tester
- SCADE
- Papyrus
- Rodin
- Atelier-B
-
Agenda Friday SCRUM- Telco:
-
VnV and Safety relevant results as outcome from the 24th of April the SSRS Kick-off in Paris
- SSRS experts group
-
As a result of the workshops in Munich the different topics will be discussed:
- Which Methodology and Tool can be taken for Verification
- Which are the important criteria for first preliminary process qualification