How long does RQM hold onto a DOORS license?
If we are using DOORS 9.5.1 and RQM 4.0.3 does RQM acquire a license when interacting with DOORS (user looks at rich hover of requirement links)? If yes then when does RQM release the license? It seems like we could tie-up a lot of DOORS licenses if we switch to OSLC? Thanks!
|
Accepted answer
Unless you navigate to the requirement in DOORS (where the full UI of DWA is shown) a license is not checked out.
So, when you do the following no license is checked out for DOORS:
- Rich hover that will show you object details (if you do not have an active session, you'll need to login to view the info - this will not consume a DOORS license).
- Select an object/view/module for link creation
Thanks,
Sudarshan
Paul Spalitta selected this answer as the correct answer
|
One other answer
For the OSLC integration, RQM doesn't acquire any DOORS license.
when user rich hover the Requirement links, it will pop up a dialog to ask the user to login as the DOORS user, if the user who can log in the DOORS, the user can get the DOORS detail inforamtion. Comments
Paul Spalitta
commented May 27 '13, 10:40 a.m.
Lei, thanks for the reply. I understand that the user is asked to login to get rich hover. And that is where my question is focused. After logging-in to DOORS (from with-in RQM), does RQM hold a DOORS license for that user? If yes then for how long? |
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.