DOORS facilitates the adoption of a chain toward DevOps architectures. Using all the IBM Rational tools, we can trace all activities related to a project, from beginning to design to development. 

For example, we use Rational Rhapsody to design models, incorporate requirements, and then generate software from those models. We also use Rational Team Concert to plan tests and Jenkins for continuous delivery.

We use the solution internally in our organization.

The solution is used to meet the requirements of system design from the user level to the supplier level, let's say. So it is used to have all the requirements integrated into only one database and link them with the different suppliers or stakeholders. So that's the main use, and we use it for those databases, basically.

We want to use it for requirement management.

We use IBM Rational DOORS to migrate from DOORS to other systems like MagicDraw. Additionally, we can accept data from these systems and migrate it for storage. This process involves syncing data between various applications.

We capture the requirements of the clients and gain acceptance. We can also review the requirements and adjust further developments as necessary. 

We use IBM Rational DOORS for listing requirements. It's a very powerful software for that. All of the specifications for the project are put inside, and then you can link them to all the documents, architecture, and disciplines.

My primary use case is for the development and management of requirements, traceability of requirements up and down the architecture chain, and verification.

We use DOORS for aerospace applications. I'm a systems engineer and we are customers of IBM. 

We used DOORS to elicit and gather user needs and then document them. We would then document these needs with diagrams and pictures that could be used to implement products and tests. We also used it for traceability purposes.

System engineers, software requirements engineers, software development engineers, software manual test engineers, software automated test engineers, software DevOps teams — these were the people who mainly used this solution.

We are mainly using IBM Rational DOORS for managing requirements.

I use DOORS to support my customers, who are heavy users of the tool. I try to figure out what's wrong whenever they have some issues. For example, if they need some help, I use the tool to recreate my customers' environments and work with it to find solutions for them. About 10 people in my company do the same thing as me.

There are numerous projects that we are using with IBM Rational DOORS. They are isolated from each other and then we receive requirements from outside sources, load them into DOORS, and use them to do traceability into architectures developed in MagicDraw.

I am using IBM Rational DOORS for managing engineering requirements.

IBM Rational DOORS is used as a requirements management tool. It enables you to do full requirements development and testing.

We use it to manage requirements. For the defense projects, we basically do a waterfall design methodology. So, we input the customer's requirements at the top level, and we flow down through all of the design requirements and the testing requirements. We keep it all managed through DOORS.

We primarily use the solution for giving requirements, both mechanical and electric.

Requirements management, however could be customized to track tests and even change requests through customization.

Our primary use for DOORS is that we implement this product for our customers and build-out customized components.  

I run my own engineering office in Switzerland for training companies on a freelance basis. I have used the most recent version for several projects.

We had a large number of requirements coming in as a federal contractor and we put them in DOORS. We did exports from that to map those requirements to what we were doing and the architecture that we were building. We did that in MagicDraw, which we attempted to integrate with DOORS.

I use Rational DOORS to define requirements during the software development process and share databases with our suppliers.

Our primary use case of this solution is mainly to manage all of the requirements, from the user requirements to the system requirements to the sub-system requirements. Also to manage traceability, the baseline, and the different baselines of the requirement. 

We primarily use the solution for governmental management.

The primary use for the product is requirements management. That is essentially prioritizing and planning product delivery.  

I am a consultant and this is one of the solutions that my company uses to help our clients.

Rational DOORS is used to help our customers with system engineering. I use it to design complex systems like trains and cars. DOORS is used to collect all of the requirements for these big systems and then we try to organize the requirements. We make sure that the system functions in compliance with the requirements. 

I use DOORS for capturing a system requirement and subsystem requirement. I also use it for recording a system of architecture.

I am within the automotive electronics industry. The requirements management widely used in my field for change management is the key to delivering your product without any hitches. It is hard to manage requirements in a big project, therefore having a traceability feature is great.