-
Notifications
You must be signed in to change notification settings - Fork 3
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
Enable Traceability #17
Comments
This task should be done by group 2; So the assignment of @mbaniasad was a mistake. |
@mmueller301, @A0b10, any news regarding this issue? If you're stuck somewhere, try asking @tim284 and @patrickmuessig for help. This issue needs to be closed as soon as possible. Here's an example of what the G3 has done so far. |
Hi all, is this done? Please close it. |
@mmueller301 some content should be added. So the issue remains opened. |
Open TODOs:
|
The to-be scenarios in the requirements document should be traceable to your system functions.
So you might add a row in the table of the to-be-scenario:
Refined in system functions: SF_C1, SF_C3
In the SF function table you should have two row like:
Used in To-be-Scenarios: TBS_1, TBS_4
Implemented in Components: Gui, BusPosition
The text was updated successfully, but these errors were encountered: