The biggest improvement for me is definitely the ability to use DOORS in a web environment through Rational DOORS Next Generation. Integrating with Rational Team Concert via the web interface has also been beneficial. 

However, not all Rational Team Concert operations are available from the web client. Certain operations, like creating streams or components, still require using the desktop application. They're not accessible through the web interface.

And in my opinion, this limitation should be removed.

Creating streams, components, etc. We still need the desktop app for those.

DOORS has enabled flexibility in mapping requirements to the software. Tracking changes over time due to team meetings and other factors is important. 

Additionally, I've been using DOORS Next Generation, the web-based tool, especially in the last year.

IBM Rational DOORS is quite stable and useful, especially regarding gathering requirements, addressing them, and linking them. The user interface (UI) is simpler, cleaner, and stable.

We used it to implement a requirement management process in a CMMI evaluation. DOORS improved the way requirements were shared across the organization, and helped implement reuse strategy. It also improved the way the requirements concept was perceived in the organization, in that way it had also an impact on validation activities.

By learning how to write reusable DXL, I've been able to write a single script that can then be plugged into all DOORS clients at my company, meaning if I can save one person 1 hour we can then multiply that by hundreds (if not thousands) of system engineers which equates to quite a lot of time & money saved.

We went from an ad hoc Word document to a table-driven model that could be reviewed without submitting any documents. That was a big help.

IBM Rational DOORS keeps everything organized.

IBM DOORS has helped in keeping requirements wording and structure standard across all customer documents. It's export functionality helps in producing quality requirements with ease within short time frame. This helped in supporting multiple clients at the same time with lesser chances of errors.

It has improved our ability to do traceability back to our initial requirements. The traceability allows us to be able to rapidly advise our sponsors.

IBM Rational DOORS has helped our organization because of the sense of configuration baseline. That is key for us. With it, we can create and freeze baselines, put them on the configuration control,  and then use it as evidence. 

The documentation of history is automated, making the generation of reports for the change review board simple. I can extract redlines using Baseline Compare between the last approved baseline, and the ‘current’ module, which collates all of this history into a single redline report making change reviews a breeze.

This product improved the amount and accessibility of formalized documentation surrounding business processes. It also helped bridge the gap between business and technical documentation requirements which was a priority when trying to rebuild our CRM system using vendors in several different time zones.

Many of our defense customers give us the requirements in a DOOR file, so we can instantly import it. Nobody has to sit there playing with spreadsheets or anything else. In minutes, we have the requirements, and we can begin the flow down to the various levels of the design as we work on it. The thing that we like about it is the fact that it's compatible with what our defense and also space customers use.

Requirements management is a key activity in any software development process and especially so in safety-conscious industries, i.e. where incorrect software can kill you, e.g. automotive, aviation, medical devices, etc. In these industries DOORS (any requirements management tool) shouldn’t be thought of as an improvement, but more as a key tool for doing your job, like a compiler or defect tracker.

As the product development lifecycle progresses, DOORS helps to maintain the traceability as requirements change (base-lining), and as new requirements emerge.

This product improved our organization because it has given us a means for improving the way we proceed through solution development.  

Having clear requirements is essential in delivering the right product.

It is important to understand that DOORS is just a tool that should help you to manage the requirements, or better documents that needs to trace to other documents in a controllable way providing history of changes and details of the change that do not need to be reported but they need to be stored. It is important to understand also that the first thing before managing, is that a process needs to be in place that identifies what it has to be done and the way that it will be done described in a simple and clear manner. Then DOORS can be customised to support that process and ensure that the process has been followed. In that way DOORS can ease the burden on the user to follow cumbersome steps of process as there is no alternative. This way the quality can be improved and audits become easier. DOORS is heavily used in aerospace, space, automotive (especially safe critical or mission critical systems) as this way can ensure a full history and lifecycle of the requirements it can be combined with change management tools to control and track the changes and only allow changes to happen when there is a need. Also allows through traceability to identify the effect of the proposed change to the system down to the component (hardware or software). Furthermore it can be customised that way to record the verification and reports can be produced at all levels to identify that requirements have been validated and verified and the system performs as expected. In the organisations that I worked for and I’m still working DOORS has made a lot of things possible that reduce the development and verification time.

Previously we were not using any requirements management tools, or maintaining different types of requirements (i.e. customer, system, software, test cases) in our process defined templates. It gets a bit tricky for organizations divided over time zones if you're not using any proper management tools like DOORS. It helps us to standardize the way our globally distributed teams are now collaborating and managing the different artifacts.

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.

It supports the capture, management and development of requirements, thereby reducing defects at the earliest stage of a project.

It's saved us time, as much as 35% when compared to v9.3.03.

It enables us to manage our customers' requirements effectively and efficiently.

IBM Rational DOORS allows requirements to be efficiently and effectively tracked, traced, and managed throughout the project lifecycle. Managing requirements in documents, e-mails, spreadsheets etc. becomes unwieldy. Anybody that has attempted this will find IBM Rational DOORS a godsend.

• Doing Impact analysis
• Producing documents
• Rich-text editing

Using this solution will streamline processes and generally improve the quality of them.

It helps us to manage and track requirements for complex products. This allows for quick and easy safety certification.

Requirements development, and doing everything from functional requirements to system requirements, means we can verify that there are no orphan or childless requirements, which ensure full traceability in a short amount of time using the available tools.

The product was used to better track and structure requirements we were developing for a new product that was to be integrated into an existing system with its own requirements. It was a way for us to track new requirements and its impact on existing ones.

Traceability on requirements for a huge project in an organization is a big gain.