It handles large-scale requirements analyses including traceability and impact, but in addition also has its own accessible scripting language, DOORS Extension Language (DXL), which allows users to tailor the tool to suit their more specific needs and processes. Extensions built through DXL have offered a much greater ability to tailor Rational DOORS for a variety of specific processes and needs.
Improvements to My Organization:
I use it to support a variety of customers. Using it, I have been able to quickly and accurately perform holistic analyses of data. I am able to create a traceability and impact analysis report of a set of 20+ documents in minutes, and then use the tool to help verify that the data is accurate.
Room for Improvement:
"Out of the box" Rational DOORS, in most cases, will not have many desired features for specific needs. DXL allows a user to customize it to fit many of those specific needs, but such extensions require lots of training and time. Therefore, while the rooms for improvement can be filled, it requires a trained expert user - or users - to access the full Rational DOORS functionality. It is not friendly to new users, and has a steep learning curve.
Use of Solution:
I’ve used it for one year.
I have not had any performance issues between a Rational DOORS database of 100 requirements vs. one with 10,000+, beyond an expected increase in processing time for dealing with more objects. Even with 100 to 10,000 requirements, processing time for common tasks only goes from a few seconds to a few minutes.
In most cases with clients, initial set-up involved importing a document corpus into Rational DOORS, then verifying that it was imported successfully. Regardless of the format of the original documents, I have not had trouble configuring documents then importing them into Rational DOORS, which supports imports of CSV, ReqIF, rich and plain text, FrameMaker files, and several others. Rational DOORS 9.6 also supports importing documents/spreadsheets to update current data.