-
Notifications
You must be signed in to change notification settings - Fork 8
Home
The purpose of this repository is to concentrate all documents with respect to the Sub-System Requierement Specification in one single place.
You will also find meeting agendas and other precedureal documents in this place.
Meeting: March 28, 2013 at Charleroi
Meeting: April 24, 2013 at UIC Paris
Workshop: May 24th - 27th 2013, Munich
##Upcoming Events:
We want to organize our next working session, to adress the following topics:
- which WP´s (Subtasks) are in the scope of the SSRS,
The next meetings will be place at the UIC Paris
1st day (2nd of July) 13:00 .- 17:00 (right after the ITEA rehearsal) Room 205
2nd day (3rd of July) 09:00 - 12:00 (before the official ITEA report) Room 203
##Useful Documents:
Here is an overview of documents used in this task.
Subset 26 Chapter 7 XML Model [Here] (https://github.com/openETCS/validation/tree/master/Artifacts)
##MoM Weekly Telco SSRS 2013.08.01:
Topics:
- Backlog of the SSRS https://github.com/openETCS/SSRS/wiki/Backlog-SSRS
- How to create a SSRS artifact https://github.com/openETCS/SSRS/wiki/How-to-create-a-SSRS-artifact
- Issues deriving from the SSRS definition https://github.com/openETCS/SSRS/issues?state=open
- Issues on resources https://github.com/openETCS/SSRS/issues?state=open
MoM:
- Presentation of the issues on Git Hub, the SSRS Backlog and how to create a SSRS artifact
- Asking for volunteers/resources
- Jan Welte (TUB) will try to work on this to create a SSRS document that will be picked up from the backlog
1st SSRS Sprint: 04.08.2018 - 18.08.2013
##Backlog for the 1st SSRS Sprint (04.08.2018 - 18.08.2013) :
-
Management of Radio Communication § 3.5
-
Check linking consistency Check linking consistency § 3.16.2.3 § 3.4.4 Responsible: Jan Welvaarts, Lloyds Register (in progress)
-
Check Balise Group Message Consistency if linking consistency is Checked, Check Balise Group Message Consistency if linking consistency is checked § 3.16.2.4.1 § 3.16.2.4.3 Responsible:
-
Check Unlinked Balise Group Message Consistency Check Unlinked Balise Group Message Consistency § 3.16.2.5 Responsible:
-
Check correctness of radio messages Check correctness of radio messages § 3.16.3.1.1 Responsible:
-
Check radio sequence Check radio sequence § 3.16.3.3 Responsible:
-
Check safe radio connection (only level 2/3) Check safe radio connection (only level 2/3) § 3.16.3.4 Responsible:
-
Determine Train Speed and Position: Determine Train Speed and Position: (no §, it is a general topic) Respnsible:
-
Determine train position referenced to LRBG Determine train position referenced to LRBG § 3.6.1 § 3.6.4 Responsible: Baseliyos Jacob, Deutsche Bahn, (in progress)
-
Picking up a requirement from the Backlog
-
Downloading the Template for the SSRS document (Reference document on Determine train location referenced to LRBG)[here] (https://github.com/openETCS/SSRS/blob/master/Modelling/3.16.2.3_3.4.4_Determine.xls)
-
Collect the other documents (Subsets xxx) from the Repository “Useful Documents” Here
- There you will find a list with priorities for the Data Dicitionary
- The collection of the Subset 26
- The collection of the additional Subsets xx
-
Collect the interface document for determine of the interaction of the requirements with another functions/interfaces.
-
Follow by the Reference [excel sheet] (https://github.com/openETCS/SSRS/blob/master/Modelling/3.16.2.3_3.4.4_Determine.xls) on the
1st Rider (ERA Requirements) by discussion and how to realize it 2nd Rider (ERA defined variables) check the [interface document] (https://github.com/openETCS/SSRS/tree/master/Interface-Document) to determine the interfaces to this function and check the other relevant subsets xx 3rd Rider (Additional variables) if there are variable outside from the SRS 26 – 7 (ERTMS/ETCS language), for example Subset 34 or a new defined variable, notice this variable with all references. 4th Rider (SSRS) Define the requirements in functions 5th Rider (National Rules) will be defined by the operators. -
How to deal with issues? Each issue you will define please put it on the issue tracker.
-
Set the document on the Repository Modelling. So everybody can review it.