IBM DOORS Next Reviews

The way system engineering typically works is that your use cases are developed in what we call an MBSE, which is a model-based system engineering tool. Let's say your MBSE tool is MagicDraw. First, you would get and develop a system spec from your customer requirement specifications. Then your requirements engineers would further derive the system spec and set it up in your DOORS environment. Then your architects would start architecting and modeling from that system spec and develop use cases and logic flow diagrams. Then, as those use cases mature, they turn into performance requirements or constraints to help establish your sequence diagrams. The use cases aren't managed in DOORS, they're managed in an MBSE tool, but like I said, the use cases derive requirements that get put into DOORS.

The biggest thing is that it shows cradle to grave traceability between the initial parent requirement and the lowest level, or what we call a CID, a critical item development spec. You can establish your verification plans in DOORS, and then as you get test results, you can put them in DOORS as a link or as a pointer to where that specific test resides on a company database. Then you can also write compliance rationale and add a column for coding, like pass, fail, green, yellow, red, meets, does not meet, partially meets, or whatever scoring criteria you want to use. Like I said, the best thing about it is that it provides you that visibility of your verification, allowing you to know how close you are to your pre-production activities, prototyping, go ahead, or whatever it is.

I use IBM Rational DOORS Next Generation as a requirement management tool for software development.

IBM Rational DOORS Next Generation helps reduce missed requirements, especially since we have started using it as a requirement management tool. Multiple teams within an organization can work together on the same tool and follow standard or best practices to test the benefits and results they experience from reduced defects and more standard, on-time delivery of work.

IBM Rational DOORS Next Generation is the master for capturing requirements. The solution does have other use cases, however, most of our customers are using DOORS as a requirement capturing software. High-level requirements or stakeholder requirements are captured mainly in DOORS.

There are many good features with DOORS. The solution has a concept of streams and baselines, as well as a concept of components. A component is a subproject inside a project.

IBM Rational DOORS Next Generation has the capability to extend or add extensions to the data model.

Another valuable feature would be the ease to add custom attributes and new objects with DOORS.

IBM Rational DOORS Next Generation is a web-based tool, based on relational databases such as BP2 or MSS cloud, so it's a different approach to work with it, to work over the web. We have all functionality over the web. There's no decline for it, so it's a completely remote working tool.

We have the data on the server with a sizable use case. Now at 47 under two, it is getting better.

IBM Rational DOORS Next Generation is easier to expand to build a backend with several servers, so you can also use it to scale up to several hundreds of users without major problems.

We use DOORS, which is a module of Rational. I've only used the DOORS product. 

I've never used the Rational Robot. I know what it does, yet I haven't used it personally.

We really use it for maintaining our requirements documents. We use it for maintaining and updating all of our requirements docs that Rational uses today. There are probably other capabilities that it does. I'm just not familiar with them. Mainly we use it for managing requirements documents so that when they do have testing, they can use those to test against.

The ability to make updates to requirements is probably a nice feature to have. It still takes some training to do. If I'm away from it for a while, since we'll do maybe one update or whatnot, or I may review them once in a while, I'll have to re-remember things. Sometimes it can be a little cumbersome since I don't use it frequently, and I have to retrain myself.

As far as maintaining our requirements so that we can have copies of them, it's good. I can print it out if necessary.

We have another person here, an engineer here, that's kind of the manager of the whole Rational tool. She probably has more experience than I do. I just use it just to be able to reference back to those documents so whenever we have updates, we can go back to those docs.

The solution is stable. 

The product can handle quite sizable documents.

It offers an improved search experience. 

I use the tool as a PLM solution. We use it for linking requirements, flexibility between requirements and test cases, third-party models, and software architecture. We link everything together—the evolution of requirements alongside test cases and generation. We use it for everything in our projects.

The solution offers good control and configuration management with global and local configurations. This allows for collaborative work and delivery of changes to different streams or configurations.

The tool's most valuable feature is displaying requirements in a tabular format. This means you can see everything laid out in columns and rows. It is more aesthetic compared to other tools. The traceability matrix helps to view things better. It comes with different linking rules. 

The primary use case of this solution and tool is to completely manage and also reuse requirements. We produce many different products which have a lot of reused requirements (for example for protocols etc.). Before we were writing big documents describing requirements and many parts of such requirement documents overlapped. We loose a lot of time reading such documents (R&D, VV, product management) so we want to make improvements.

 We use IBM Rational Doors tightly integrated with Quality Management for testing requirements- WIth such combination we slightly improve our product development process and support for this process

We were producing huge documents where we describe our requirements using  The problem was that while we were producing many different products with similar protocols, the documents consisted of more than one hundred pages with a lot of syncs that overlapped with other documents for similar products. This was difficult to manage, as people hated having to read all of the pages.

It is much easier because we put all requirements in IBM Rational Doors, and from this, we get the specification that can be used with different products. We don't have to write these huge documents with functional specifications anymore. Everything is well organized and easy to find in this tool. 

We primarily use the solution for system engineering. 

Typically, we receive a user requirement to produce or engineer specific equipment. From there, we derive requirements, system and sub-system specifications, and also design or create a test plan with a rationale quality manager, which is in the same suite as DOS next generation. There's full coverage provided, from building requirements to testing.

I'm impressed by the tool because the tool comes from DOS, and DOS was the legacy tool. The legacy tool had some problems and actually this version resolves a lot of those. 

It's web-based, so you don't have anything to install. 

One of the most advanced aspects of the tool is its integration capabilities.