IBM Engineering Lifecycle Management vs. Rapise

The software is robust enough to handle highly complex software development or other product development and can be used well beyond the range to do what a client needs. However, because of the inability to hold its users to proper best practices, things can get wildly out of hand and cascade over the years, creating unnecessary technical debt. The system has a lot of usable features, but they don't funnel users toward the correct processes and practices.

Incentivized

The appropriate scenario to use Rapise is when we have a project that is considered from medium onwards, since Rapise will help us to define, develop and implement the testing phase in a reliable and efficient way. Also with Rapise we will not have to worry about the platform that we are using since it has great versatility and flexibility.

Incentivized

• Open Services supporting Lifecycle Collaboration (OSLC).
• Required definition management and managed capabilities enabling.
• Rational DOORS Web Access for local on the test field presence.
• On-sites established reporting system.
• Approved linking requirements to test plans
• Engineering Requirements Management DOORS traces requirements thereby eliminates manually processes and spreadsheets, for improved productivity.
• Returns the investment efficiently.

Incentivized

• Simple recording front-end and easily captures UI objects for later interaction
• Flexible programming interface provides a multitude of manners in which to interact with learned UI objects
• Javascript based IDE is easy to learn

• I feel like it is too heavy sometimes and updating is not very straight forward. For example, if I want to change an incident ticket (IN) to a service request (SR) and add some comment for the change, I have to first change the IN to SR, then click refresh which takes a few seconds, then add a comment. If I forget the refresh step, my comment will be discarded without warning like my ticket is not in the latest status. This also happens when somebody else changes the ticket during my edit as I can not lock the ticket exclusively.

Incentivized

• For tests that require specific approaches it is necessary to have advanced knowledge of programming in javascrip, which sometimes the QA team does not have experience
• Sometimes I have noticed that when using object dragging errors occur intermittently
• The integration with some tools (Dynamics) is only with the basic functions from my point of view

Incentivized

At the moment we are required by contract to continue to use the IBM DOORS software for our current client. Given that it can be expensive, if we were to use it after our current client's needs were met, we would have to secure other projects in order to justify the continued use of the software.

Incentivized

The UI is terrible and not intuitive. Users need training in order to complete tasks. Much like SAP, it's not the clearest tool. The tracing feature is especially complicated because you must write the scripts yourself. There is a learning curve. Also, even the setup, installation, and logging in each time takes a considerable amount of time.

Incentivized

It does a basic job and has the potential to complete some robust reporting tasks, however, it really is a clunky piece of software with a terrible user interface that makes using it routinely quite unpleasant. Many of our legacy and maintenance projects still use DOORS but our department and company use many alternatives and are looking for better tools.

Incentivized

No problems

Incentivized

It was easier to do all the change management-related activities, even configurations were handled very effectively. New process definitions and initiatives made it easier for better project deliverables. Effective resource allocations and better reporting and defect management. The overall cost of the tool is great too and well within budget.

Incentivized

Mmuch better from a flexibility perspective

• It's part of CLM suite so it can be used to manage the whole lifecycle with tight integration with development module (Rational Team Concert) and quality module (Rational Quality Manager).
• Comprehensive reports and dashboards provide better visibility.
• License cost is on higher side.

Incentivized

• The primary objective of the institution is a service to the public, so everything that improves response times to the public helps us to achieve it.
• As a department in charge of the development of systems and applications, our objective is fulfilled by delivering quality products and tools such as Rapise help us greatly
• The return on investment can be more than justified by fulfilling the primary objectives

Incentivized