RQM:Why some source columns of requrirement section in testplan show Local instead of DOORS?
RQM4.0.1 integrate with DOORS 9.3 through RQMI.
After exporting the view from DOORS to RQM and confirmed they are completed, if then clear test plan association, sometimes the requirements imported into RQM in TestPlan will be removed(which is expected) but sometime it will remain there and the source will show as Local instead of normal DOORS. The questions are: why some of them show Local and is not gone? Would these "Local" sourced requirements mean any fundamental problems and how to avoid them? Appreciate if anyone can shed some lights on this. Thanks |
One answer
Paul Slauenwhite (8.4k●1●2)
| answered May 20 '14, 7:26 a.m.
FORUM MODERATOR / JAZZ DEVELOPER edited May 20 '14, 7:29 a.m.
Would Allow RQM to remove the relationship to requirements imported from DOORs and RQMI. (56818) apply in your case?
Comments Thanks Paul for the info. The RFE does not seem to apply to this user's case. they can delete the "Local" sourced requirements from within RQM. but once it becomes Local sourced requirements, even though they are deleted in RQM, the correspondent requirements in DOORS will never be able to be exported to the same test plan even though they are in different view in DOORS. I am escalating this issue now for further investigation. We'll investigate in the escalation.
|
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.
Comments
Don, is this a new DOORS/RQM integration or was RQM upgraded from 3.x, configured with the RQMI-style of DOORS/RQM integration?
Thanks Paul.
Yes, this is upgraded from RQM3.0.1.x+DOORS v9.3(RQMI). Would that make any difference for the behavior in RQM4.0.1(that is, clear test plan association won't let the requirements go but remain in RQM as LOCAL sourced.)