Verification of User Story 4: Transmitting information Train->Track and Track -> Train

[MarcBehrens]

Within the design working package (WP3) the Funcitonal Requirement Specificaiton is defined by User Stories. To synchronize with new functionality the verification is linked to the User Stories.

Title	Content
User Story Title	Train is reading track information - Train is sending information to the track
User Story Definition	"As the End User (WP1) i want to see a demonstration of reading of track information from the Euroradio or Eurobalise. Furthermore i want to see a demontration of sending of information from the train to the track (Euroradio)" modeling/issue#69
Link to DAS2V	model\Scade\System\ObuFunctions\ManageLocationRelatedInformation\BaliseGroup\Receive_TrackSide_Msg\Receive_TrackSide_Msg.etp ?
Name of Function	Receive_TrackSide_Msg_Pkg::Receive_TrackSide_Msg/ function to send message train --> track is in development
WP3 Issues	WP3 User Story 4
Related to Specificatoin	SUBSET-026 v3.3 Chapter
Test Specification
Restult of Tests

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

[MarcBehrens]

• [ ] The need for an Interface update is identified for the testmodel: https://github.com/openETCS/validation/tree/master/VnVUserStories/VnVUserStoryTUBS/05-Work/Check_US4_Am_Ut according to the latest SCADE EVC interface changes
• [ ] The need for an architectural verification between the API defined inside the technical appendix for the requirements https://github.com/openETCS/requirements/tree/master/D2.7-Technical_Appendix and the SCADE train to track interface is identified (reduced to Balise and Radio)