New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Traceability: Visibility on Papyrus Part #358
Comments
I've added these specification in the following commit 3956ef6 to the ReqIF_Specs created by Michael. This is documented in #349. (Please assign this to Michael, as I'm not able to do so. Thanks) |
Well Done. |
I don't think so, as this is at least assigned properly |
cecilebraun
modified the milestones:
Toolspint 12 (Ends 6-June-2014),
ToolSprint 11 (ends 23-May-14)
May 22, 2014
cecilebraun
modified the milestones:
Toolspint 13 (Ends 20-June-2014),
Toolspint 12 (Ends 6-June-2014)
Jun 11, 2014
|
cecilebraun
modified the milestones:
Toolspint 14 (Ends 05-July-2014),
Toolspint 13 (Ends 20-June-2014)
Jun 24, 2014
cecilebraun
modified the milestones:
Tool Sprint 15 (Ends 18-07-14),
Toolspint 14 (Ends 05-July-2014)
Jul 3, 2014
work started, need further instruction to continue ! see at: #380 |
cecilebraun
modified the milestones:
Toolspint 16 (Ends 08-August-2014),
Tool Sprint 15 (Ends 18-07-14)
Jul 22, 2014
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The current implementation of the openETCS Traceabilty function is only visible on ProR side.
With this extension two new sub-features are requested:
@janWelte : Do we already have some specification for these requirements?
@jastram : Do you need an additional specification of the requirement?
br
Bernd
The text was updated successfully, but these errors were encountered: