System Engineer at a tech services company with 10,001+ employees
Real User
Top 5
2024-04-12T16:13:40Z
Apr 12, 2024
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.
Project System Engineer at a aerospace/defense firm with 10,001+ employees
Real User
2022-12-13T15:04:27Z
Dec 13, 2022
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.
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.
System Engineering Manager at a wholesaler/distributor with 10,001+ employees
Real User
2022-08-18T20:26:02Z
Aug 18, 2022
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.
Technical Sales Specialist at a computer software company with 1,001-5,000 employees
Real User
2022-01-04T21:37:00Z
Jan 4, 2022
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.
Software Engineering Consultant at a manufacturing company with 1,001-5,000 employees
Consultant
2020-06-18T05:17:47Z
Jun 18, 2020
I am a consultant and this is one of the products that I use for my clients. They use DOORS Next Generation mainly for requirements management, in conjunction with other tools such as RTC for change management, and RQM for quality management. Together, these are all part of the software life cycle.
Associate Director Systems Engineering & Safety Assurance at AECOM Technology Corporation
Real User
2020-04-02T07:00:10Z
Apr 2, 2020
Used on major rail projects for requirements management. Used to manage multiple design packages and contract requirements, technical requirements, and derived requirements. We're a customer of IBM and I'm a casual user of the product. We're looking at it possibly for another project.
CEO at a manufacturing company with 10,001+ employees
Real User
2019-12-04T05:40:00Z
Dec 4, 2019
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.
CIO at a comms service provider with 501-1,000 employees
Real User
2019-08-12T05:55:00Z
Aug 12, 2019
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
IBM Engineering Requirements Management DOORS Next (DOORS Next) is a requirements management (RM) software designed to help organizations manage engineering project requirements throughout the development lifecycle. It offers a central location for capturing, defining, and organizing project requirements, facilitating collaboration among stakeholders like engineers, system designers, and customers. Key features include requirements traceability, version control, and impact analysis. DOORS...
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.
I use IBM Rational DOORS Next Generation as a requirement management tool for software development.
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.
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.
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.
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.
I am a consultant and this is one of the products that I use for my clients. They use DOORS Next Generation mainly for requirements management, in conjunction with other tools such as RTC for change management, and RQM for quality management. Together, these are all part of the software life cycle.
Used on major rail projects for requirements management. Used to manage multiple design packages and contract requirements, technical requirements, and derived requirements. We're a customer of IBM and I'm a casual user of the product. We're looking at it possibly for another project.
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.
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