IBM DOORS Reviews

We want to use it for requirement management.

The images are not clear. We have to use them as OLE objects. And in the testing part, I'm not sure how to link it with it. This is my main concern.

In future releases, I would like to see importing features. Like can we link it to PLM? And can we link it with Windchill? I found some difficulties when I imported to DOORS. It's easy to explore, but when I import, sometimes it lags, and sometimes the numbering is weird.

I have been using this solution for six months. 

It is a stable solution. 

It is a scalable solution. We have about 15 end users. We are planning to increase the usage and procure more licenses. 

The customer service and support are good. There is room for improvement in speed of response. 

Neutral

The setup was not easy.

Our IT team handled the deployment. It took them one and a half months. But we have only one working license for now. 

The product is easy to use after we deploy it. We took a training call on it. So I think now it's clear for most of them, but maybe not indeed, but it's enough for users to start working.

The pricing is quite high. We didn't pay for additional support. We didn't need it. They helped us without any cost in the installation part. 

We have PTC Windchill. But we need an extra license. Moreover, I want to know the difference between them because some people have knowledge of DOORS, and some people have knowledge of Windchill. And we need to decide which one we buy more licenses for and go with.

We are satisfied with IBM Rational DOORS, but since we have another choice, which is Windchill, we are not sure if we should go with DOORS now or we go with Windchill.

Just to start working on it because I think it will simplify life.

Overall, I would rate the solution an eight out of ten. 

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)

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.

Getting started with DOORS Administration, how to setup a project, how to maintain it, and how to get started with DXL are all areas that need quite a bit of experience to master. I highly recommend finding someone certified in being an IBM Rational DOORS v9 deployment specialist and better yet using him/her as a mentor as you learn yourself. Skipping the all important project architecture workshop is going to cause you a lot of frustration throughout the lifecycle of your project.

I have been using DOORS for 15 years, 1st two as a software developer that looked up the requirements for the GUI he was assigned to develop, the latter 13 for everything from writing DXL to meeting with clients, being a technical lead for a distributed set of DXL developers = lots of fun.

Not having the right people bought in at all levels of management to have a smooth flowing process for deployment, it takes the work of quite a few individuals to make it all work, IT, software, systems, configuration management, quality - getting everyone on the same page and the training they need just in time is quite a challenge.

By placing the DXL we've developed under heavy levels of scrutiny with code reviews, configuration control, change control boards and frequent interactions with the actual users of the solution we've been able to avoid the typical pitfalls that might come with developing customizations.

Developing skilled & experienced specialists that know how to setup DOORS projects and help existing ones adopt best practices takes time and the only way to get real experience is to do it, hard to find the people distributed across the geographical boundaries to fill these roles over prolonged periods of time.

it's gotten considerably better since the early years of the Telelogic acquisition, once you submit a few tickets you get the hang of it. It would be nice the same person answering all your questions all the time so you get the rapport, but that might be asking too much.

Once you get into the advanced use cases of using your own DXL, most of the time the support can be handled in house.

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

It was quite complicated, luckily for me I learned from the best and was able to continue to network and continue learning from the brightest minds in the industry. Combining this with my own experiences and the many clients I have worked with have equated to superb amount of real like challenged faced and overcome.

Have had vendor in house for very select engagements, mostly self created solutions based on many in house meetings and sound software development.

A good question... lots of time & money saved.

I've been able to bypass this question for the most part in my line of work and focus more on the client experience once the DOORS server & licenses are available.

I absolutely believe for any company to be successful with DOORS they must invest in an in-house support team of architects & trainers who's full time job it is to deploy DOORS and help programs learn how to use it effectively.

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.

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.

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.

When the requirements increase within a single model in IBM Rational DOORS, it takes time to save. The requirements are associated with an absolute number in DOORS. For instance, they possess creation dates, modification dates, and information about the creator of each requirement. One specific attribute is absolute number.'The DOORS database automatically generates this absolute number and remains unmodifiable through the API. Therefore, it is not feasible when migrating data from one DOORS system to another or attempting to alter the absolute number through the API. The database generates this absolute number, which is unchangeable. DOORS cannot control or modify these auto-generated absolute numbers.

I have been using IBM Rational DOORS for a couple of years. We are using both V9.5 and V9.7 of the solution.

The product is stable.

I rate the solution’s stability a nine out of ten.

10-15 users are using this solution. Four to five users are using this solution every day.

I rate the solution’s scalability a seven to eight out of ten.

Both technical support and documentation are really helpful.

Neutral

The initial setup is simple and takes only half an hour to complete. For deployment, you need to click, provide some inputs, and execute fairly simple actions.

I rate the initial setup a seven to eight out of ten, where one is difficult and ten is easy.

We did the installation by ourselves. One person is enough to do the deployment, depending on the knowledge of software and administration.

There is no maintenance required until your license needs fixing. However, it is entirely maintainable. You don't have to handle any maintenance until you upgrade to the next version of DOORS, and even then, the process remains straightforward.

IBM Rational DOORS is highly useful for project requirement management. I strongly recommend utilizing DOORS for requirement management and offer flexibility.

DOORS is a valuable tool, and it has attracted numerous customers. Many organizations, including Fortune 500 companies, use DOORS for their operations.

Overall, I rate the solution an eight out of ten.

• 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

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.

DOORS weakness is in the interface with the outside world, as the database is not standard, data cannot be easily managed by other tools. Import/export capabilities have huge room for improvement though importing a Word or Excel document is simple. There are no simple extensions available to generate good synthetic documents (RPE not being user friendly). Another item that is needed in any requirements management tool is the capability to manage the requirements data model at project/database level, attributes/types definitions in particular.

I've been using it for around 10 years since 2006. I was responsible for deploying it, including defining data models, training teams, and administrating the database for two different organisations. Both organisations are worldwide, and In the second, the user community was over 400 people worldwide.

As stated earlier, the missing ability of the tool to globally manage data model often leads to inconsistencies in the deployment phase, as processes are often being defined while deploying the tool. It's difficult to retrofit an incorrect implementation once started.

It's low. Since IBM acquired Rational. The support is basic and limited to the tools usage which is not what experienced users need. Experienced users need support for advanced features and DXL usage, which is somehow mandatory for any organization who wants to take full advantage of the tools capabilities.

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.

We used Telelogic support to train the teams and initiate the datamodel construction

We used a benchmark study in which 10 other tools were rated, including Reqtify (which is not a real REQM tool), Requisite Pro, Caliber, and Cradle.

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

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

None as IBM have left v9.5 as the extant version and now moved it into DOORS Next Generation.

I've used Rational DOORS since 2009, and v9.56 for 18 months.

No issues encountered.

It is the most stable platform, and did not crash once unlike v9.3.03 version that we had previously.

We used it on one programme to start with, but when I left the company, we were using it on five separate programmes.

We were using IBM directly, and they were 10/10.

10/10 - IBM take real pride in their technical support activity with customers.

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

It installed really well, and it has a straightforward license key operation.

It was done in-house, but our engineers had guidance and support from IBM, which was excellent.

It's massive, as it's a contract requirement. DOORS v9.5 enabled us to satisfy all our customer demands with relative ease. Can't quantify the ROI in financial terms though.

DOORS rules are that you have licences per company which give access to the software according to the users who need access at a particular time. Most businesses would probably find it too expensive to have a single licence per every DOORS user.

No other solutions were looked at due to contractual requirements.

Use DOORS Next Generation or later versions of DOORS v9.X

We are mainly using IBM Rational DOORS for managing requirements.

IBM Rational DOORS keeps everything organized.

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

It has a user-friendly interface.

Some of the search queries could be improved. The interface needs an area to be able to type your query and actually be able to find them.

It could be more stable.

In the next release, they could scale it down a little bit and make it more stable.

I used this product up until three months ago. I have been with this company since February.

If I have left it open for too long, there are times where we experience a session timeout, and we have to stop or force-close it to restart the application.

From the time that I have been using it, it's been pretty good. Like anything that has been left open, you will experience a timeout.

IBM Rational DOORS is scalable.

We have approximately 300 users within the region.

I have not contacted technical support.

The initial setup was straightforward.

We have our computer management who instructed me to download IBM Rational DOORS.

It was simple to download and get started.

We may have used a retailer to help us with the deployment.

We are currently using IBM Rational DOORS on-premises but we are trying to migrate everything over to a Cloud service.

IBM Rational DOORS is good for privacy, it's good for the management of software requirements, and also for keeping everything organized. It does a pretty good job.

I would rate IBM Rational DOORS an eight out of ten.

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

The data logs are ver conveneint. 

The setup is very easy.

It is user-friendly. 

The speed lags based on the server and the remote connection.

They need to provide users with information on what options would be best for their setup. 

The export of the requirements does not allow me to see the linking of the requirements. I'd like to see some sort of visualization or flow chart so we would have an overview from a system perspective.

I've been using the solution for four years. 

You can request licenses if you need more access from more users. 

I've never contacted technical support. The setup is done, and we have cleared the requirements. We've never had any technical difficulties that needed us to reach out.

You can create a whole server inside the project. It's easy to set up. 

I wasn't directly involved with the deployment and do not know how long it takes. 

You do have to pay for a license per person. 

It is worth the money given the market options. There's good compatibility between you and your clients that makes it valuable. 

We are a customer and end-user. 

We have a server-based deployment. 

The solution has some of the most advanced features on offer, which is why we chose the solution.

I'd rate the solution seven out of ten. It can meet the needs of any developer. However, it does lag a bit. 

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

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

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.  

What could make sense for this product is to improve is to develop a more efficient way to import and export documents from Office 365 like Excel, or Word and the other applications in this suite. Maybe, if possible, add a PDF document export or something like that. There are quite a few single steps that you have to take separately at the moment to make this happen. The parts are already implemented, but there could be a much more unified and efficient way to get that done. Again this is a repeated request from users and nothing has been done to implement it.  

What I would like to see is in the product is that eventually, IBM will implement additional software solutions for integration. There is one that I know of that used to have the name RPE. It stands for Rational Publishing Engine. I think it is a tool that should be implemented in DOORS because it belongs to IBM after they purchased Rational Software. With this integration, we would have a much better way to actually import and export between Word or other Office documents.  

On another side, it would be good to also see them integrate the GC (Garbage Collector) trace tool. It is a logical requirements engineering tool that would enhance some capabilities. It could be a specialty add-on but the integration needs to be there. This product is owned by IBM because formerly it belonged to Telelogic as well. It would be good for IBM and the users of these tools to have these solutions implemented in DOORS.  

I have been working with this product since Version 0.1. More than 20 years.  

The stability is quite nice at this point. After these last few major versions, they have made significant improvement and it is very stable.  

From my side, scalability is okay so far. I have not had any bad experiences in our own use or with clients.  

Our clients who use IBM Rational DOORS are usually large, enterprise companies, like airline industry companies, like Siemens, we work with Audi, Mercedes, and BMW. So we are not usually talking about small companies. But they are not all alike and we have clients of all sizes.   

In the past, I had a reason to contact IBM technical support, but I wasn't impressed. It was a lousy service. There is no question the technical support can be improved. It might not be a bad idea. The funny thing is that since IBM took over Telelogic and some of the guys from Telelogic have been moved over to IBM. If you get the ones who still work for Telelogic, you get fine and proper service and resolutions. But if you do not have the luck to reach one of the Telelogic people and you reach one of the ordinary IBM people, it is the worst case and you probably will not get what you need.  

Positive

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

The initial setup is easy. The deployment usually takes a couple of weeks.  

In the deployment process, there are between three to seven people involved depending on the project.  

It is not simple to answer how many people are involved in the maintenance because we have decided to divide the way we look at supporting clients and products into different levels. Our support services have three levels now because all these different levels need different information about the tool in-depth to be able to use it properly for their purposes. If we do not provide them the information about the tool in-depth, we would not be providing proper support. In general, we have about six people providing the maintenance services.  

We do all of our own implementations.  

All my clients are running under a special agreement using a client-server version of the DOORS product where they get a discount on the product and then only pay maintenance. They pay the maintenance on a yearly basis. They are mostly huge companies and this is partly how they were able to get this special agreement. It works well for them because we have informed the clients how they could reduce their maintenance costs.  

Our evaluations are ongoing. As an independent requirement engineer and system engineer, I'm running my own engineering office. From time-to-time, I have a client that asks me for information about other tools. But most of them still use DOORS or some other classic tool which has grown up through the .Net generation. So we do the research, but the research is more often to propose something to our customers if they are interested in doing something different and more modern.  

We do not have any shortlist of other possible solutions at this stage because it may require changing operating systems. It's quite different if you compare both DOS and the next generation. I am still trying to figure out what is the best way to move forward. At the moment, I'm not really satisfied with the technology that is working with DOS next generation.  

I get the idea behind the viewpoint from IBM, especially if you understand the focus on the newer, improved platform. It makes sense. But for established companies that have hundreds or thousands of documents in a classic DOS database, it is not as simple as the IBM company thought to populate the next generation. Especially in a technical company, we need one more serious tool and with some evolved features. When that happens, it will be okay. But a total switch from what they were doing is not what most companies are looking for. In my impression, it is not important to have a lot of tools for the same discipline. I think it would be more worthwhile to get one nice mature tool which suits all the interests and at the end of the day. So far it does not exist.  

But by the same token, what we have to take in account is it doesn't matter if a product is made by a company called IBM or whichever company it is, we have to take care about the philosophy as it is only by having better tools that we have better success in a project. I'm not an engineer who is against all new technologies, but at the moment my impression about the American leadership and about the software technology — the current direction is frightening.  

I think it is now time to think more about what direction the American software companies are taking us in. It may not be the right way or the best way to see the future of the computing world. I have heard managing directors say, "We have to find other solutions at the moment. This software we get is from America and we are not willing to accept this leadership and direction at the moment.  

What we actually have learned — or even maybe accepted and are comfortable with is now — is that for the user projects work best and most efficiently, it is absolutely nicer to work in a more structured way. This product helps order our projects. Because of what the tool does, we have a way to document the bare base engineering. What we did in the past, before DOORS, we all used Word and maybe Excel in our offices to set up our specifications for the product. In DOORS, we can now work in a different way. There are very nice features that help to structure your documents, to link your documents, and make a different analysis, test your approach and see it better. There were no tools like this in Word and Excel.  

You also have the possibility to re-use things. It is quite nice to use a tool that allows you to use all your experience from a technical point of view and create the solutions in one data source and one tool and use components you create for various other projects as well.  

On a scale from one to ten where one is the worst and ten is the best, I would rate IBM Rational DOORS as an eight-out-of-ten.