I would say the only additional feature would be if it had dynamic linking to other MBSE tool sets or industry-leading tools. That way you could have that link and not have to do a manual insert or translate the data to an Excel-based product and then use the Excel to load into DOORs. 

The user interface of IBM Rational DOORS Next Generation needs to be improved, there is a lot of scope with this. Even though there have been improvements from versions five, six and seven, the UI still has a lot of bugs. 

There is room for improvement in the APIs that they have exposed for integration. The solution relies on OSLC for integration APIs, but those APIs do not support all the capabilities.

IBM Rational DOORS Next Generation is not a very user-friendly product. From an improvement perspective, IBM Rational DOORS Next Generation needs to be made a very user-friendly product.

It does have a tendency to condense the requirements. It kind of puts them in a tree format. Sometimes those trees are a little difficult. Unless you're used to using it daily, how it truncates everything and kind of rolls things up can be a little bit challenging. That said, I don't know if there's an easier way to do that. 

An area that could be improved is user interface which is not very intuitive. Product is also Java based and we have a lot of issues with performance (at beginning). Resolution of all problems takes a lot of time. ALso upgrades of product are from our experience very painful.

This solution is currently having some performance issues because they changed the data storage in the back between version 6 and version 7, so it needs some performance improvement.

The data storage is the relational database in the background, and it has changed and needs performance improvement. Performance is a very big thing that is needed when people are writing requirements. They have to wait too long for the page to return and then they don't like it. They are looking for different ways to do and complete their work. Good performance is very essential in this tool, same for DOORS Classic.

There is also a lot of possibilities to improve reporting.

The tool is quite new, so it may not be a mature product, but I haven't spent enough time with it to have a list of improvements that it needs.

When you are in JIRA or Confluence, you have some freedom in how you type in the text. That's also a weakness of Confluence, however, as it opens the doors to sloppy work. In DOS Next Generation, the text is very rigorous, but it might be difficult for people who don't have the discipline. Having a way to quickly enter requirements could help. It might already be in there, but I don't know. I don't have enough experience with the tool yet.

IBM Rational DOORS Next Generation has room for improvement compared to other tools like Polaris and Jama Connect. These tools offer more flexibility and options for developers, which IBM Rational DOORS Next Generation lacks. For example, you can define your link rules in Jama Connect, but you can't do that in IBM Rational DOORS Next Generation. 

The problems with DNG are legion and make using the tool very frustrating.

There's ongoing stability issues with the browser UI. Some cases of illogical restrictions on artifact views, RFEs, have been submitted to the vendor and are currently pending review by the development team.

It offers a bad user experience and the usability is poor. A lot of engineers do not use it, primarily for two reasons. First, it is very abstract and hard to understand. Second, the operation seems to be very complex. For example, the setting is distributed in a lot of section and it is not easy to find where to configure it.

The baseline is not as good as it is in DOORS because you can't create a baseline for a module. Rather, you can only create on for the project.

The speed of technical support needs to be improved.

The DOORS Web Access (DWA) is not stable.

• Import/export
• Stability