How to link requirements and source code and get traceability matrices
|
4 answers
hey Oskar
If you're in 6.0.4, and turn on GC, you'll be able to link from files in RTC to requirements, as well as to other files. Important to note that this is in the context of a global configuration (GC).
So - that establishes the connection from the file to the requirement.
The only way I see to get to the information is via the API. I'd love it if I'm wrong.
|
Think this is not yet supported in DNG. Cannot find the work item where the enhancement is written down...
|
Thanks Steven and Bas.
|
It is true that some standards such as DO178C describe a regulation that organisations must manage a relationship from each line of source code back to the requirement that specified it. If there is no requirement for code then the code is not needed. Managing such a scale of traceability is not realistic to maintain individual links from source to requirement but there are more standard techniques that allow you to meet this requirement. If you place your source code under change control each time you change the code you create a task or change set in order to gather sets of changes together to manage as a single entity. If the task or change set is linked with the originating requirement then it becomes possible to demonstrate that for every version of the requirement there is a distinct set of code changes that provided the implementation. Some tools such as the combination of RTC and DNG can enforce that a Change Set and task is required for every code and requirement change.
Comments
Oskar Berreteaga
commented Jun 28 '17, 11:17 a.m.
Hi Richard,
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.