IBM Rational DOORS Next Generation OverviewUNIXBusinessApplication

IBM Rational DOORS Next Generation is the #6 ranked solution in our list of top Application Requirements Management tools. It is most often compared to IBM Rational DOORS: IBM Rational DOORS Next Generation vs IBM Rational DOORS

What is IBM Rational DOORS Next Generation?
IBM Rational DOORS Next Generation offers a smarter way to manage your requirements that can help your teams reduce development costs by up to 57%, accelerate time to market by up to 20%, and lower cost of quality by up to 69%. Designed for collaboration, Rational DOORS Next Generation provides a single platform for managing requirements so that your teams can work more effectively across disciplines, time zones and supply chains.

IBM Rational DOORS Next Generation is also known as RDNG, Rational Requirements Composer and IBM RRC.

Buyer's Guide

Download the Application Requirements Management Buyer's Guide including reviews and more. Updated: September 2021

IBM Rational DOORS Next Generation Customers
Major health insurer
IBM Rational DOORS Next Generation Video

Filter Archived Reviews (More than two years old)

Filter by:
Filter Reviews
Industry
Loading...
Filter Unavailable
Company Size
Loading...
Filter Unavailable
Job Level
Loading...
Filter Unavailable
Rating
Loading...
Filter Unavailable
Considered
Loading...
Filter Unavailable
Order by:
Loading...
  • Date
  • Highest Rating
  • Lowest Rating
  • Review Length
Search:
Showingreviews based on the current filters. Reset all filters
AntonKavcic
CIO at a comms service provider with 501-1,000 employees
Real User
Simplified our requirement process, helping with requirement creation and reuse

What is our primary use case?

The primary use case of this solution and tool is to completely manage and also reuse requirements. We produce many different products which have a lot of reused requirements (for example for protocols etc.). Before we were writing big documents describing requirements and many parts of such requirement documents overlapped. We loose a lot of time reading such documents (R&D, VV, product management) so we want to make improvements. We use IBM Rational Doors tightly integrated with Quality Management for testing requirements- WIth such combination we slightly improve our product development… more »

Pros and Cons

  • "The most valuable features are the versioning of requirements and the possibility to reuse them."
  • "When you are not working on it every day it is not very intuitive."

What other advice do I have?

I would suggest finding someone, who already has experience with implementing this solution, to help you with the implementation. It will be easier and you will have fewer problems, as product and configuration is quite complex. What we have learned from our experience is that upgrades should be done with the help of the external IBM partners of IBM services team. You can think also to have solution in cloud, but from price perspective the price in cloud is not attractive, specially in case as our when we use floating licences. The user interface could be improved, it is quite heavy and…
ITCS user
Requirements Engineer at Visteon Corporation
Real User
There are limits to the number of artifacts a server can handle

What is our primary use case?

Requirements management as part of the Jazz Platform CLM integrated tool chain. The only reason to use DNG is as a part of the IBM tool chain.

Pros and Cons

  • "The "Link by Attribute" feature is useful for making links without needing to use the web interface manually."
  • "I have come to the conclusion that if you are considering migrating from DOORS to DNG, don't! Instead of spending 100's to 1000's of hours doing migrations, invest those hours in a DXL programmer to make DOORS do what it isn't doing for you now."
  • "Be very careful how you load your DNG server. There are limits to the number of artifacts a server can handle."
  • "As a web tool, DNG can be difficult to use if the server is loaded or your network connection to it is saturated."

What other advice do I have?

Migrating from DOORS and a constellation of other tools to the IBM Jazz Platform CLM integrated tool chain seems like a no-brainer at first. I do not know a lot about the other tools in that chain, but I can tell you DNG is the weak link. I have come to the conclusion that if you are considering migrating from DOORS to DNG, don't! Instead of spending 100s to 1000s of hours doing migrations, invest those hours in a DXL programmer to make DOORS do what it isn't doing for you now.
Find out what your peers are saying about IBM, Jama, Atlassian and others in Application Requirements Management. Updated: September 2021.
534,299 professionals have used our research since 2012.
it_user321231
Marketing and Sales at a computer software company with 51-200 employees
Vendor
It provides us with collaboration between several development teams such as design, development, and testing, although its stability could use improvement.

What is most valuable?

It provides us with integration throughout the complete product development process.

How has it helped my organization?

With it, we have easy collaboration between several development teams such as design, development, and testing.

What needs improvement?

Import/export Stability

For how long have I used the solution?

I've used it for three years.

What was my experience with deployment of the solution?

No issues encountered.

What do I think about the stability of the solution?

There were some issues.

What do I think about the scalability of the solution?

No issues encountered.

Which solution did I use previously and why did I switch?

No previous solution was used.

How was the initial setup?

It was easy.

What

ITCS user
Sr. Solution Architect at a tech services company with 51-200 employees
Consultant
It gives our team better visibility across life-cycle artifacts, but deploying the RRC add-in for browsers can be a real headache.

What other advice do I have?

Try staying close to out-of-the-box in the initial usage, grow into more complex configurations and usage models if possible. If committing to a complex SDLC and automated life-cycle tools, then invest in education for all users. Do not waste the investment by assuming that the solution will be utilized by all without training.