How to link requirements and source code and get traceability matrices

hey Oskar

Think this is not yet supported in DNG. Cannot find the work item where the enhancement is written down...

Thanks Steven and Bas.

Provided that the feature mentioned by Steven is available, that would solve the traceability issue at file level.

Is there anything else that would help to achieve a more fine grained traceability, let's say to procedure/function or even statement level?

Thanks and regards
Oskar

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.

I hope this helps

Richard
Offering Manager, DOORS Next Generation