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
One of the bigger quests of openETCS is the identification of issues within the SRS and between SRS and railway operators local rules.
We need a process to collect findings, find a common understanding in our group of experts and adress issues with ERA.
The procedure is based on interfaces of DB into ERA.
I see three aspects of this issue:
1.: Give some guidance in the quality assurance plan on the procedure
(Clearly a part of the QA Plan) @idelatorre
2. The description of the procedure and
3. The implementation of the procedure including follow-up of responses from ERA
I plan to take care on the procedural aspect. It is related to issue: openETCS/validation#52 in validation.
The text was updated successfully, but these errors were encountered:
I strongly support this proposal. During my modelling of "Start of Mission" I found several issues. Some of them can probably easily be solved by an expert (however, they still imply an incomplete specification) while others may be more serious problems. For now I decided to set up a document in the respective V&V user story directory of WP4 (not yet online) to document the findings.
I like the idea you try to demonstrate with this picture, but 've to admid there are some aspects, where I would like to get more information. Where (in which document) can I find this picture?
Dear Baseliyos,
pictures are basis for a good understanding.
I will scan our SSRS material as a basis - and we somehow have already a process running on SSRS for findings.
Your and @JanWelvaarts help are needed to get a good story out of it.
One of the bigger quests of openETCS is the identification of issues within the SRS and between SRS and railway operators local rules.
We need a process to collect findings, find a common understanding in our group of experts and adress issues with ERA.
The procedure is based on interfaces of DB into ERA.
I see three aspects of this issue:
1.: Give some guidance in the quality assurance plan on the procedure
(Clearly a part of the QA Plan) @idelatorre
2. The description of the procedure and
3. The implementation of the procedure including follow-up of responses from ERA
I plan to take care on the procedural aspect. It is related to issue: openETCS/validation#52 in validation.
The text was updated successfully, but these errors were encountered: