We used to use both Microsoft Word and Excel. We created tables and wrote everything inside. We switched because of trustability, versioning, and processability. In Excel, I am the only one who can modify it, or no one will be able to trace it.

No other solution was used before. Some other departments in the company were using a custom system based on MS Word with macros and reqtif.

I started my career with DOORS & DXL and have not looked back. I have helped programs go from SLATE to DOORS.

We have used this same solution from the start.

I have used HP Quality Center but DOORS provides better standardization and maintainability of requirements.

We are using Siemens Teamcenter for the same usage as IBM Rational DOORS, but for different databases, they are not interconnected.

I have used Excel spreadsheets prior to using IBM Rational DOORS.

Prior to DOORS, over 17 years ago, we used a custom Lotus Notes database, but it did not provide traceability or easy reporting.

No previous solution was used.

DOORS is the only system we've used for this purpose. In other cases, we create massive spreadsheets that have links in them and are completely unmanageable, but they do the work.

It's actually the other way around: it is a natural progression to migrate from DOORS to DOORS Next Generation (DNG) on the Jazz Platform. However I argue that DOORS is the superior tool and that organizations should not migrate to DNG.

Prior to IBM Rational DOORS, I've used a SLATE database to track requirements. It wasn't as user-friendly and at the time we switched to DOORS, the decision was based on what our customers were using to track their requirements. DOORS was the better choice and is still the most recognized tool for requirement traceability.

Before we used IBM Rational DOORS, we just used Word and Excel to create our solutions.  

When I started using DOORS, there were several other relational management tools in use at Boeing (where I worked then). We set DOORS as our standard. Now, I work for another Large US Aerospace Company, and DOORS is our standard.

No, not any kind of requirements management solution. We were managing requirements in the form of our own Microsoft Word defined templates. Management of requirements for our globally distributed teams in a centralized location was a prime driving force for the change.

I've not used a previous solution, but today, I'm investigating the Eclipse Requirements Management Framework (RMF) for small entities/teams that cannot afford a power tool like Rational DOORS.

Before using this solution I did everything in Microsoft Word.

No we didn't, as we were under contract to use DOORS.

No previous solution was in place.

I have used other tools such as RDD-100, CaliberRM and in-house developed solutions.In all cases I have simply moved into new roles in other organisations with the opportunity to use IBM Rational DOORS.

We previously used a different solution, but the change was the company's choice.

I've tried many of them, and found that this one is the best.

I have also used REQTIFY. 

We used Interleaf and other tools, but they don't allow for easily readable trace and control.

No previous solution was used.