DNG Requirements Change Management Licensing
I understand that RTC can be used a a requirements change management engine from this previous thread
Would RTC licenses and deployment be required in order to implement this solution? I presume yes.
I am thinking a simpler approach would be to just have the stakeholder requirements under access control and manage changes manually through a DNG 'change request' artifact (with a DNG workflow) linked to the system requirements that are requesting the change and to the stakeholder requirements that will be changed if the request is approved.
That would keep the whole solution inside DNG and would be more flexible.
Did anybody use this alternative approach?
Accepted answer
2 other answers
DNG includes requirements change management, and RQM includes defect management, both of which are accomplished through integration with RTC. Thus, RTC is included in every cloud provisioned environment. The license loaded in the cloud hosted environment constrains usage to only that functionality included in the subscription.
^Thanks for the info and links guys.
(The link was broken but I managed to edit it manually so here it is updated)
I am also wondering about environment provisioning.
If the customer has a cloud environment for DNG then they don't have control over the server to install RTC as well as DNG.
So does IBM SaaS cloud provisioning allow access to the RTC product as well as DNG at no extra cost if the customer has bought a DNG cloud environment?
