sideburner wrote:

Hi RQM team,
I'm currently at the end of my knowledge.
We have teams that defined requirements that others have to test.
Whats the designed flow to create a due date when a requirement has to
be verified?
We currently spend a lot of time and creativity to get some kind of
projected vs actual chart out of the data rqm provides.

As I said, we have about 150 requirements and all have to be verified
on a specific date. The req. are covered within several test plans.

Whats the proposed way to get this information into the tool?

Thanks in advance for any hints or comments.

In addition, if we define milestones within the testplan, is it
possible somehow to link specific test cases to milestones?


Thanks!

I think the way to drive to a date is to use the milestones in the test

plan.

Yes in a test case you create a Test Execution Record (TER). You
associate it with a test plan and a milestone within the containing test
plan. A test case can be shared across multiple test plans and when you
create a TER you associate it with a test plan and then only the
milestones available with that test plan will be available. It is
somewhat tedious to create TERs but it allows you to track progress on
your test plan. BTW requirements are also linked to test cases as well
as test plans. You can use the requirements traceability report to
guarantee all your requirements are covered by test plans and test
cases. We use that feature extensively.

sideburner wrote:

Dave,

thanks for this information.
Is it possible then to create a report that shows me a number of
requirements (e.g. with a specific tag), the matching test plan, test
case, test execution record(s) and its result(s)?

because basically this would be what we need. 1 Report that summarizes
this information.

you can do the first piece pretty easily under the traceability report -

it will show the requirements and which test plan or test case covers
it. You can get execution reports that will show results in various
forms, but I think you probably need to use RCR or Insight to build a
custom report to combine them together. It should not be too difficult
to use.

We tend to use the traceability report during a test plan
creation/review/approval cycle, then after that is complete we focus on
the execution reports. We know we have the requirements are covered in
the first cycle and in the execution phase we focus on running and
successfully completing the TERs. If we complete that then we know all
the requirements have been tested. We are not focused on when the
requirements are test but that they are tested.