| || |
Traceability in RequisitePro
Can anybody explain a good system for deciding whether you should trace requirements "to" or "from" other requirements?
I have a very vague idea about it and I know it should be consistent but I'm having a hard time coming up with a solid principle for business analysts to follow.
Re: Traceability in RequisitePro
I think it figured it out:
when you're looking at a "trace suspicion hierarchy" the requirement at the "top" should only have traces running from it. The ones at the "bottom" should only have traces "to" other requirements. That way the suspect traces fall "down" like a cascade if it's set up right.
Unless my reasoning is totally wrong.