I like its ability to automate tasks using DXL and Java scripting languages is powerful. DOORS Next Generation also offers improved IP integration through JAPI.

While managing requirements, I like the ability to track changes within documents and compare different versions of requirements.

The traceability matrix in DOORS improved our project outcomes.

It helps ensure coverage of requirements at different levels, from user requirements to software requirements to test requirements.

The product creates an ID for each requirement update. It is very detailed. The product enables users to divide the requirements and export them. So, I need not give my customers access to my database. They can review it and send it back. The next-generation features are good.

I would say that the best feature of the solution is that since everything is in one place, and if you make any changes, then they are recorded or tracked. Also, it is very good to have the totality between different levels. Being able to pull up the information from different modules, especially from one of those that you want the information to be presented, basically keeps everything clear and quite well-presented. The only downside of the solution is its performance, which is quite low sometimes. But in terms of the best thing about the solution, I can say that it gives you confidence. If you enter the solution and let it stay like it is, there are not going to be any issues or any loss of information for these companies.

It's a very interesting tool. I like that it's simple. You have to create your document, add your templates, and have your headings and definitions, and it's done. You must attribute the discipline and fill out the comment field for requirements. It also provides you with unique IDs for each requirement. I like that it never duplicates IDs.

The most valuable feature of this solution is traceability.  We can trace every requirement, including what the stakeholder must do and component-level requirements. We can trace them easily, which is very beneficial.

It is easy to use. You can use it easily. 

It is similar to an improved Excel spreadsheet. It is also simple to use for a newly graduated engineer.

One of the most valuable aspects of IBM Rational DOORS is how it structures data. When working on multiple projects, you'll find that each project contains various models. These models are akin to Word but offer additional functionalities. DOORS Security provides capabilities that Word lacks.

Under each module, you can organize requirements hierarchically and trace the requirements via internal and external links. Unlike Microsoft Word, DOORS enables versioning, allowing you to baseline your requirements and effectively freeze them when necessary. These functionalities make the tool highly useful and stand out among similar tools.

The data logs are ver conveneint. 

The setup is very easy.

It is user-friendly. 

• Centralised location for better team collaboration
• Scalable access control
• Traceability by linking items on the global requirement life cycle
• Integrations (modelling tools)
• Full customization using DXL
• Wide user community
• Available as a web based solution

By far and away the most useful feature of IBM Rational DOORS is the Dynamic Extension Language (DXL) syntax & manual that it comes with (then again I must be biased having been coding in DXL for 13 years and counting). With each new release going back to when I started with DOORS 4.1 the vendor (used to be Telelogic, until IBM bought them out) provides a DXL Reference Manual as part of the product which is free to anyone using DOORS - explaining which functions the IBM development team is using themselves to extend the DOORS client functionality (and inviting all software developers to take their crack at customizing the DOORS client to better suit the needs of their company)

I like the user interface with regard to creating links between requirements and tracing links to requirements.

I like the DXL Wizard, in particular, to build custom views that I save.

I am a fan of the DOORS Change Proposal System, although a lot of people where I'm working have their own homegrown system. I continue to push them to migrate to the DOORS CPS.

The solution uses a custom object-oriented scripting language called DOORS Extension Language or DXL. It allows you to manipulate the software to your liking. It's very customizable and can be as powerful as you want it to be. User management is pretty straightforward and I generally enjoy using the solution. As the administrator for the program, it's very quick and easy to add a user, change permissions, rights, things like that within the software.

This solution is the Cadillac of similar solutions. I liked that we could export to Excel and Word. We could also link to other off-shelf tools.

Compared to other tools that I have used over the past 20 years, DOORS is the best of the best. It's expensive. It's a heavy-duty tool. 

The most valuable feature is the verification requirements for peer reviews.

It has a user-friendly interface.

When you install DOORS locally, you have the flexibility to do what you want with the solution. You can add functionality and do many things that you can't do with other tools or do well enough to satisfy your users' requirements. For example, you can save linked versions when you do baselines, and then I can handle linked changes between different baselines. You can't do this with other tools, or it's hard to do.

The most valuable feature for me is the ability to enter data into one table, or context, and link it across modules.

We use DOORS to document system requirements and inherit customer equirement maintain standard and conformity. It helps in traceability of requirements and restricts changes to requirements by anyone. In order to make changes to the requirements, one needs RCR (Requirements change request) which would be reviewed and approved before applying changes. It would help in impact analysis and version tracking.

It is a great tool for requirement gathering and elicitation. It brings all the business analysts in a team on the same page as everyone has the same understanding on requirements.The traceability to system requirements, customer requirement and test cases helps all teams to reference each other's work in an easier manner.

I like being able to sort and categorize the requirements and the exporting functions.

What I like about DOORS is baselines, it's easy and I use the capability of multiple users. The traceability or links between different levels are very nice. Additionally, it is used by all of our suppliers, which brings us commonality.

The most valuable feature of IBM Rational DOORS is the full requirements development and testing.

The DOORS Application provides object to object traceability, with user flexibility to build their own traceability reports without requiring administrator coding in DXL, XML, java or any other scripting language. In addition, out of the box features for generating baseline to baseline redlines is efficient when reviewing changes.

The most valuable features were the structural flexibility of the documents and ability to specify the type of link between them. It was possible to organize a group of collections within a project, a group of modules together in a collection and a group of artifacts together in a module or a variation of that. Additionally, it was easy to design links to any of the previously mentioned entities in a variety of defined relationships.

I like the way we can simply link requirements with one another and with test descriptions and then automatically produce reports that are required to show compliance to our customers. It is a combination of requirements management and reporting that I like, but I really have very little to do with the reporting part of it. I don't know how easy or hard it is to create those reports.

The shell scripting is the solution's most valuable aspect.

The ease in which one can link requirements is very important to the general user since traceability is a core task in requirements management.

As an admin and developer, the DXL scripting language allows me to customize and extend DOORS in (almost) any way imaginable. (DXL is the scripting language used to customize and extend DOORS.)

The ability to link objects is most valuable, because this provides the traceability from the customer requirements to our product requirements, and ultimately our test results.

One of the most valuable features of the program is the usability. It is really simple to use and its logic, look and feel are familiar to most customers. Let's say it is more of an old-fashioned interface design. If you look at the software, you will notice that the layout is similar to the old Microsoft Windows Explorer. This is helpful to customers who have long-term experience because the look and feel is something they remember from the structure of Explorer and they find it familiar when they go to use DOORS.  

There are several other features in the product that are valuable to users and to us. These features would have to do with the traceability and the possibilities for customization of the RP (Relying Party). This is important because several of our clients run an awful lot of customizations.  

In the past, we communicated customization needs to Telelogic and IBM through huge customer meetings like conventions, but nothing happened. That was when we added our engineering offices and started our business using customization tools. The clients who can't find what they need come to me now and ask if we could please develop tools like so-and-so (whatever company and functionality). We make it for them and we make it better with customizations — specific to their purposes. As a tiny, small engineering office we often get called for special solutions, for special company needs, which formerly Telelogic and now IBM was not willing to do for the customer. This is a big reason why DOORS is valuable for us and has helped us make our business.  

• Traceability
• Baselines
• Ability to customize using DXL

The most valuable feature is the management verification and login.

DOORS is a customizable requirements management tool. The main feature that DOORS is used for is the traceability, which through it you can perform an analysis on the requirements how they decompose down to the lowest level. Also you can perform an impact analysis on the proposed changes and see the cost of your change. History of changes in DOORS is also important, as a lot of time there is a need to find out who performed the change as in a large team with people moving from place to place sometimes is needed to trace to the originator and understand the reason.

The way that new attributes can be created and the access management in all level is also another feature that is very useful in DOORS as with distributed teams and external contractors there is always the need to manage the data that users are allowed to access and modify.

Of course with the use of DXL all those things can be automated and be reported. DXL is very dynamic and came a long way from 5.4 and earlier. And as a lot of development and effort has been put into it, companies are reluctant to move to DOORS NG as this feature does not exist (or anything similar to it).

We are using DOORS together with IBM Rational Publishing Engine for reporting that makes everything a bit easier instead of using DXL to export the reports to Word.

The traceability matrix along with the linking of software design with requirements. We are also using it for test management, so it provides bi-directional linking between requirements, design, and test cases.

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.

It is process agnostic, i.e. it can be tailored to serve any life-cycle process flow. It also integrates with the largest number of software and systems engineering tools in the marketplace.

This solution is very simple to use.

I really like the customization that can be done using the DOORS Extension Language (DXL). I have developed a lot of tools and it is quite nice. For example, I have a tool that I wrote that can perform a trace analysis for automatic reporting. It only works on classic DOORS because it would have to be reprogrammed in JavaScript or another language.

The UML editing and reporting features are good.

Being able to track changes to requirements and being able to export is the solution's most valuable aspect.

Starting to use the solution is pretty straightforward. There isn't too much of a learning curve.

The DXL Library DXL script routines/algorithms and the DOORS importer.

Rational DOORS' most valuable feature is that you can write any kind of requirement you want.

Traceability is the most valuable feature of this solution. I like that is has the capacity to manage traceability from one level of requirement to another.

• Configuration management
• Requirements linking
• Access control
• DXL5

• Traceability
• Impact analysis
• History
• Baseline sets
• DXL scripting
• Publication with Rational Publishing Engine (separate product)

We have different generations of all products. It lets us select and see unique attributes for each release or generation. You can use attributes to define a selection area to see which equipments are for the old versions and which ones are for the new versions. This inbuilt view is what I like in IBM Rational DOORS. So, for a database and a set of requirements, it will select and show unique attributes for a release or a generation.

The recommendation aspects of the solution are good.

What I like the most is probably requirement traceability in configuration management.  

• Traceability
• Audit trail
• Configuration Management for Requirements

The most important feature is that it is able to manage a lot of requirements.

It helps to maintain global compliance during all of the stages of development. When you specify the functionality of the system, it is able to show that the system is compliant with the needs. Moreover, it is easy to maintain compliance based on the design.

This solution is able to manage a lot of data.

It is very customizable and easy to scale.

The features that I've found most valuable are organization, trace, connection to other products via external links, and DXL.

• Traceability
• VRTMs

The most valuable features include:

• Traceability (the ability to link between different items)
• Configuration Management (ability to baseline things and create new views)
• User Access (to control who does what to different items)

The product was being used for developing and tracking new requirements for a system we were working on. There wasn't one specific feature that comes to mind, as it was approximately 12 months ago that I was using the product to develop requirements.

• Traceability
• The ability to use any type of document in any format.

These features make our job easier in requirements management.