You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Picture 8 reduces the "formalization" to the vehicle side SSRS only. The FPP V.2.2, approve by ITEA2, as well the updated version of the FPP V.3.02 (being in the process of a official change request) are requesting a formalization of the entire "System Requirement Specification" (and not just a subset as described in this document at many places), therefore the tools chain and processes in question should cover the entire SRS and additional requirements needed to define a complete System, covering at least ERTMS Subset026 and supporting Subsets. Therefore this picture needs to be changed: The "box" described with "Sub-System Requirement Specification (SSRS)" needs to be renamed as "Extended System Requirement Specification (ESRS)" in order to express that additional ERTMS Subsets and further information (from operational rules, supplier's and operator's experience) need to be considered in order to create a working model.
In the further course of this document all remarks that limit the tools chain and processes to the vehicle related Sub-System Requirement Specification SSRS need to be eliminated, since also the the way-side related SSRS elements need to be covered. The (formal or semi-formal) model needs to cover especially interaction between vehicle and wayside equipment, while the focus of code generation in this project is on the vehicle side. Never the less, also way side code needs to be generated in order to cover the driving simulator (TCSim) software part for being able to operate the TCSim within the "proof of concept" with industrial use cases (track side).
Proposal: All wordings with "SSRS" or "Sub-System Requirement Specification" should be substituted by "ESRS" or "Extended System Requirement Specification"
New Figure 1. openETCS Process
This is considered a bug, since limiting the tools chain to the vehicle side SSRS is not justifiable by the openETCS FPP as approved by ITEA2. Also ERA, as one of the major stake holders represented in the openETCS Advisory Board, has indicated that it has special interest in modeling of real-time interaction between vehicle OBU and infrastructure communication. This cannot be demonstrated by limiting the model to the vehicle SSRS only.
The text was updated successfully, but these errors were encountered:
Picture 8 reduces the "formalization" to the vehicle side SSRS only. The FPP V.2.2, approve by ITEA2, as well the updated version of the FPP V.3.02 (being in the process of a official change request) are requesting a formalization of the entire "System Requirement Specification" (and not just a subset as described in this document at many places), therefore the tools chain and processes in question should cover the entire SRS and additional requirements needed to define a complete System, covering at least ERTMS Subset026 and supporting Subsets. Therefore this picture needs to be changed: The "box" described with "Sub-System Requirement Specification (SSRS)" needs to be renamed as "Extended System Requirement Specification (ESRS)" in order to express that additional ERTMS Subsets and further information (from operational rules, supplier's and operator's experience) need to be considered in order to create a working model.
In the further course of this document all remarks that limit the tools chain and processes to the vehicle related Sub-System Requirement Specification SSRS need to be eliminated, since also the the way-side related SSRS elements need to be covered. The (formal or semi-formal) model needs to cover especially interaction between vehicle and wayside equipment, while the focus of code generation in this project is on the vehicle side. Never the less, also way side code needs to be generated in order to cover the driving simulator (TCSim) software part for being able to operate the TCSim within the "proof of concept" with industrial use cases (track side).
Proposal: All wordings with "SSRS" or "Sub-System Requirement Specification" should be substituted by "ESRS" or "Extended System Requirement Specification"
New Figure 1. openETCS Process
This is considered a bug, since limiting the tools chain to the vehicle side SSRS is not justifiable by the openETCS FPP as approved by ITEA2. Also ERA, as one of the major stake holders represented in the openETCS Advisory Board, has indicated that it has special interest in modeling of real-time interaction between vehicle OBU and infrastructure communication. This cannot be demonstrated by limiting the model to the vehicle SSRS only.
The text was updated successfully, but these errors were encountered: