It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×12,010
×10,958

question asked: Mar 30 '17, 8:30 a.m.
question was seen: 1,574 times
last updated: Apr 06 '17, 8:16 a.m.

Related questions

Tracing in between RQM and Doors

0
Ed Schrader (11●1●5) | asked Mar 30 '17, 8:30 a.m.
edited Mar 30 '17, 8:39 a.m.

 Hi


I'm looking for information pertaining to the typical method that is used for tracing DOORs Requirements to RQM Test Artifacts.

I can see that you can link Test Case Artifacts to DOORs Requirements but I don't see a method to link Test Case Result Artifacts to DOORs Requirements. The workflow I have used in the past is to trace to test results and not the test specifications (cases).

Curious to know what others are doing to show their traceability..Is it report/view created in RQM? Or an extension brought out within DOORs from the linked Test Case? Do you find issues tracing a Test Case and not the Test Result?

RQM version = 6.0.2

Doors version = 9.6



One answer

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
Georg Kellner (840●4●81●109) | answered Apr 06 '17, 8:16 a.m.

Hi Ed,

we're using RQM and DOORS in some projects, linking requirements against test cases.
It's working fine for us.

AFAIK you are using one DOORS view to create the basic configuration both tools.
If you use this view from DOORS, you may find an additional menu "RQM" in DOORS with some reports.
If I remember correct, there is a report displaying the last result of the linked test case.

One of our DOORS specialist did some DXL scripting to add more infos from RQM into DOORS.

Greetings Georg.

Your answer

Register or to post 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.