Requirement traceability question
I am trying to use QC as a Requirements Management tool along with Test Management. I understand that QC has some limitations as a Requirements Management tool but wanted to throw this question out anyway to see if there is a way around this issue that I am facing.
I am creating high level functional requirements in the Requirements module under the root Requirements folder. Then I am creating children Design requirements under this parent functional requirement. I was under the impression that the children requirements will automatically be traced back up to the parent. However, that does not seem to be happening. I have to manually add a trace from up to the parent. Is there an easier way to accomplish this?
Any guidance will be much appreciated.
Re: Requirement traceability question
Ok. Sorry for the premature question!
I noticed that the children requirements DO show in the Impact Analysis tab under the parent.
However, they DO NOT show up in the relationships tab.
Is there any difference between these two traceabilities?
I am planning to writing an XML script to derive the RTM report and as long as the traces are recorded in the DB in some way, I should be ok.