Rational DNG, not a mature platform to mage requirement
February 09, 2018

Rational DNG, not a mature platform to mage requirement

Giovanni Scioti | TrustRadius Reviewer
Score 2 out of 10
Vetted Review
Verified User
Review Source

Overall Satisfaction with IBM Rational DOORS Next Generation

Rational Doors Next Generation (DNG) has been used by the application division of my customer company, and specifically by several functional analysts. The tool appears to have really specific features that allow managing artifacts like embedded documents and stores them in a central repository, and then is able to track with a strict connection the work items and codes. It shows to be a not really easy tool to use. Surely it can give really good benefits enabling the business requirements of the CR and coding activity, but to provide a consistent connection you must always work on the embedded artifact and this scenario is really not so user-friendly.

Plus if you decide to extract the artifact in a Word document after you have modified it, it is not convenient to modify the external document and then import it again because it will not override the previous one with the document versioning. It means that even if there is an import feature it is not easy to repeatedly import the same document in a different session. The graphical design features provided are not very stable. I think that it would be a better choice if the artifacts could be implemented in HTML form and not embedded as an artifact.
  • Good feature of tracking artifacts with work items
  • Interesting graphics viewer for the mapping relationship
  • Interesting concept and technical solutions for the module
  • Versioning feautures of the artifacts revision
  • Transform the artifact in HTML in form template
  • Improve the import feature, because often it crashes the procedure
  • Improve the managing of the folder structure
  • The application teams were not able to provide a specific team to be able to work completely on the tool because most of the artifacts and documents were produced by the business division that creates sub-standard documents that are easy to import.
  • The approach to defining standard artifacts and ability to store them in a central repository was well understood but the way DNG works was considered really too complicated and not user-friendly.
  • Polaion and CodeBeamer
I found [them] to be more flexible and with the possibility to create [an HTML format].
I think that in cases where there is a skilled functional analyst team that is well trained in the use of the tools and completely dismisses the use of Word documents to collect the requirements, it is a good fit. It seems that a good solution to improve efficiency to collect the specification is to use the module. If you need to build more accurate artifacts containing even fields and not just free text this is not possible. It would be helpful to store the specific value in metadata, and it would be interesting to compile artifacts with predefined fields that could be queried.