openETCS / validation

WP4: Validation and verification strategy
8 stars 22 forks source link

Verification of Dynamic Test Modell - Use Case Amsterdam - Utrecht #299

Open janWelte opened 9 years ago

janWelte commented 9 years ago

Reference to https://github.com/openETCS/modeling/issues/674 (Verification handover)

basis for #283 implementation

Within the design working package (WP3) the Funcitonal Requirement Specificaiton is defined by User Stories. These User Stories are based on the application at the Amsterdam - Utrecht ETCS L2 track. To provide the track data for the ETCS OBU model a dynamic track model has been build, which in cooperation with a train movement model allows to simulate a run on the track. The issue documentes the verification for this dynamic track model.

Title Content
Object Dynamic Test Modell - Use Case Amsterdam - Utrecht
Definition Verify correct and consitent implementation of the trak model to simulate the Amsterdam - Utrecht ETCS Level 2 track (against track construction plans and JRU lock test run on track)
Link to DAS2V https://github.com/openETCS/modeling/tree/master/model/Scade/System/TracksideDynamicModel/TestTracks/UtrechtAmsterdam_oETCS
Link to Documentation https://github.com/openETCS/modeling/tree/master/model/Scade/System/TracksideDynamicModel/TestTracks/UtrechtAmsterdam_Documentation
Name of Function Dynamic Track Model
WP3 Issues WP3 Verification issue and WP3 main task issue
Related to Specificatoin track construction plans and JRU lock test by NS
Test Specification tbd
Restult of Tests tbd
Verification Report Design Verification Report Trackside Modell

Please use #299 inside a commit message when your contribution is related to this user story.

janWelte commented 9 years ago

The first version of the Trackside report has been finished covering the design verification.