-
I have various errors when opening the generated `*.reqif`-files of the subset-26.
1. _Chapter 1_ causes the entire tool to freeze.
![chapter1_heapspace](https://cloud.githubusercontent.com/assets…
-
@UweSteinkeFromSiemens , @MatthieuPERIN , @JonasHelming
Dear Partner,
our current Eclipse project structure covers SCADE, REQIF and SysML:
![image](https://f.cloud.github.com/assets/3288918/2418849/…
-
# Traceability: Handle Traces between Requirements
The objective of this tool is to allow requirement work by establishing traces (incl. Meta Data) to start working with Subset-26 requirements. The t…
-
@astante suggested, as a temporary solution to prevent corruption due to merging, to block this. He is not sure, but there may be a .gitattributes file that does this.
I suggest to ask Lukasz to do …
-
# Design Spec: Subset-26 conversion to ProR
The objective of this tool is to convert the MS Word-based Subset-26 to the ProR-based ReqIF format. Important is the ability to do subsequent updates wit…
-
I have strange behavior in openETCS, which, unfortunately, cannot be reproduced reliably.
Symtom: ProR is not always showing the same outline. Sometimes it is showing additional platform and pathmap…
-
Please include the execution of the Tracing JUnit tests as part of the Jenkins build.
-
I just created the stub of the model project (#226). Please add the .reqif files for subset-26, if you think that this makes sense.
-
Please find a problem description for traceability between ProR requirements and SysML, as well as a suggestion for implementation that could be provided fairly quickly (less than 2 weeks): ([Traceab…
-
The subset 026 (and possibly other subsets as well) comes with identifiers for each requirement (i.e. `3.8.5.1.2` is requirement of chapter 3 dealing with infill MAs). This works reasonably well as lo…