Try our new research platform with insights from 80,000+ expert users

IBM Engineering Lifecycle Management (ELM) vs OpenText ALM / Quality Center comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Dec 23, 2024

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

IBM Engineering Lifecycle M...
Ranking in Application Lifecycle Management (ALM) Suites
13th
Average Rating
7.2
Reviews Sentiment
6.2
Number of Reviews
18
Ranking in other categories
No ranking in other categories
OpenText ALM / Quality Center
Ranking in Application Lifecycle Management (ALM) Suites
4th
Average Rating
8.0
Reviews Sentiment
6.6
Number of Reviews
207
Ranking in other categories
Test Management Tools (1st)
 

Mindshare comparison

As of March 2025, in the Application Lifecycle Management (ALM) Suites category, the mindshare of IBM Engineering Lifecycle Management (ELM) is 2.9%, up from 1.7% compared to the previous year. The mindshare of OpenText ALM / Quality Center is 5.7%, up from 5.6% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Application Lifecycle Management (ALM) Suites
 

Featured Reviews

Harold Pogue - PeerSpot reviewer
A complex deployment that is not stable, but is cloud-based
The team of 15 to 20 software engineers uses IBM Rational ALM and Jira for testing. They coupled different online packages together because the Duration Enterprise was impossible to use IBM Rational ALM did not help the organization and we ended up moving to another solution. The most valuable…
Paul Grossman - PeerSpot reviewer
Range of supported technology expands, but odd IDE design still leave newbies and pro users alike disappointed.
There are always new features and more support for new and legacy technology architectures with each release. But the bad news is a growing list of long-standing issues with the product rarely gets addressed. While I have a larger list of issues that make day to day work harder than it needs to be, these are the Top Five that I do wish would capture someone's attention in upcoming releases. All hit the tool's ROI pretty hard. #1) Jump To Source - The Silent Code Killer: In older QTP versions a double-click on any function in the Toolbox window would take the developer to the function's source code, while a drag from the Toolbox would add it to the code window. Since 12.0 a double-click on a function in UFT's Toolbox window now ADDS the function (same as drag) to the Code window - to whatever random location the cursor happens to be at - even if it is off screen, and it will replace sections of code if it is highlighted. We are not sure what the intention was, but our Best Practice is to avoid the Toolbox window entirely to avoid the real danger of losing days of work and needless bug hunts. Now Jump to Source is not all bad. A right-click on any function called from a Script takes us to the code source, which is great! But it only half works: in a Library, only for functions declared within the same library. Our advance designs have well over twelve libs so a whole lot of extra time is spent searching the entire project for a function's source on a daily basis. Lastly, while we can add custom methods to object, a Jump To Source from these methods is long overdue. So again our only option is to search the entire project. #2) Object Spy: It needs to have multiple instances so that you can compare multiple object properties side-by-side. It lacks a Refresh button, so that automation engineers can quickly identify the property changes of visible and invisible objects. Or HP could skip to option #3... #3) Add RegEx integer support for .Height or .Width object properties when retrieving object collections. If this were possible, our framework could return collections that contain only visible objects that have a .height property greater that zero. (Side Note: the .Visible property has not returned a False value for us in nearly five years - a recent developer decision, not a product issue) Eliminating the need to separate the non-visible objects from visible ones would decrease execution time dramatically. (Another side note: Our experiments to RegEx integer-based .Height properties found that we could get a collection of just invisible objects. Exactly the opposite of what we needed.) #4) The shortcut to a treasure trove of sample code in the latest release 14.0 has been inexplicably removed. This impeeds new users from having an easy time learning the tool's advanced capability. In fact the only users daring enough to go find it now will be you who is reading this review. #5) Forced Return to Script Code. This again is a no-brainer design flaw. Let's say we run a script and throw an error somewhere deep in our function library. Hey it happens. In prior QTP versions when the Stop button would be clicked the tool would leave you right there at the point where the error occurred to fix. Now in recent releases, UFT always takes us back to the main Script, far from that code area that needed immediate attention.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"It's easy to use."
"The planning feature is rich with Scrum concepts: Sprint, Sprint retrospective, the rules in the Scrum framework."
"The integration with Git works well."
"I would rate the stability of this product a nine out of ten."
"The tools for requirement capture we have found very useful."
"It is relatively easy to use and user-friendly once the setup is complete."
"It helped us contain critical things, like source code and several documents, which is very important to us."
"The word emulation and importing is good."
"We can create a requirement for stability metrics with the test cases to ensure all requirements are covered."
"Templates: Allows us to standardize fields, workflows throughout hundreds of HPE ALM projects."
"Business process management is the most valuable feature of the solution."
"The most valuable features of OpenText ALM include its integration with the automation landscape, the ability to capture requirements and map them to test cases, and the capability to schedule runs through ALM."
"The setup is pretty straightforward."
"As a system administrator, HPE ALM can be flexibly configured so that it can accommodate a variety of defined project lifecycles and test methodologies."
"It is a tool, and it works. It has got good linkage and good traceability between the test cases and the defects. It has got lots of features for testing."
"Cross project customization through template really helps to maintain standards with respect to fields, workflows throughout the available projects."
 

Cons

"The GUI is a little bit outdated."
"The features should be more intuitive. If I'm looking for something, its location should be easy to locate."
"The user interface requires significant improvement as it is overly complex."
"The interconnectivity between packages is a major support problem and can be improved."
"The solution can improve in the development area and the customized applications."
"There is not enough beginner support material in the form of FAQs or simple training to help you get started."
"The stability of this solution can be improved."
"In the next release, we expect a traceability metrics configuration where we can configure the user stories. We also expect them to improve or simplify the query process."
"The performance could be faster."
"Currently, what's missing in the solution is the ability for users to see the ongoing scenarios and the status of those scenarios versus the requirements. As for the management tools, they also need to be improved so users can have a better idea of what's going on in just one look, so they can manage testing activities better."
"It needs Pure-FTPd WebUI and single sign-on."
"Certain applications within this solution are not really compatible with certain applications like ERP. The problem is when we're trying to use these applications or devices, the solution itself doesn't scale."
"I'd like to see the concept of teams put into it."
"The extract format is not ideal, splitting expected results into three line items, making interpretation difficult."
"HPE ALM’s out-of-the-box reporting can be perceived as rigid and limited, to an extent."
"Costing is an area that needs improvement."
 

Pricing and Cost Advice

"The solution is not cheap."
"The price of the solution could be reduced. Many of our customers are not using all the features and this could be why our clients feel the price is too high."
"This product is a little expensive and we had to pay extra to have them set it up for us."
"IBM Rational ALM has both monthly and yearly licensing options."
"We have a contract, but I am not aware of the details."
"I'd rate the pricing as 3/10 as it's very expensive."
"Compared to the market, the price is high."
"It's a perpetual license."
"If you have more than five users, a concurrent licensing model should be considered."
"Quality Center is pricey, but cheaper is not always less expensive."
"We pay around $30,000 for thirty users, translating to approximately $6,000 to $10,000 per user, which is high."
"Most vendors offer the same pricing, though some vendors offer a cheaper price for their cloud/SaaS solution versus their on-premise. However, cloud/SaaS solutions result in a loss of freedom. E.g., if you want to make a change, most of the time it needs to be validated by the vendor, then you're being charged an addition fee. Sometimes, even if you are rejected, you are charged because it's a risk to the entire environment."
"HPE has one of the most rigid, inflexible, and super expensive license models."
report
Use our free recommendation engine to learn which Application Lifecycle Management (ALM) Suites solutions are best for your needs.
842,296 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Manufacturing Company
24%
Computer Software Company
13%
Financial Services Firm
7%
Government
7%
Educational Organization
68%
Financial Services Firm
6%
Manufacturing Company
5%
Computer Software Company
4%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

What needs improvement with IBM Rational ALM?
The user interface requires significant improvement as it is overly complex. For business users with no experience in IT, it can be particularly challenging to understand the UI and create test cas...
What is your primary use case for IBM Rational ALM?
We use IBM Rational ALM as part of our overall application suite for our manufacturing company. It is used by our engineering team to capture requirements, perform testing, and manage defects. Spec...
What do you like most about Micro Focus ALM Quality Center?
The most valuable feature is the ST Add-In. It's a Microsoft add-in that makes it much easier to upload test cases into Quality Center.
What is your experience regarding pricing and costs for Micro Focus ALM Quality Center?
The on-premises setup tends to be on the expensive side. It would be cheaper to use a cloud model with a pay-per-use licensing model.
What needs improvement with Micro Focus ALM Quality Center?
We work with Jira now, and there are some very good workflows. There could be more configurable workflows regarding test case creation approval. I see a stable tool that remains relevant in the mar...
 

Also Known As

IBM Engineering Rhapsody, Rational ALM, MKS
Micro Focus ALM Quality Center, HPE ALM, Quality Center, Quality Center, Micro Focus ALM
 

Overview

 

Sample Customers

Tennis Australia, WeCloud AB, Port Otago Limited, Logicalis US, Valmer, The Chevrolet Volt, Ashurst
Airbus Defense and Space, Vodafone, JTI, Xellia, and Banco de Creìdito e Inversiones (Bci)
Find out what your peers are saying about IBM Engineering Lifecycle Management (ELM) vs. OpenText ALM / Quality Center and other solutions. Updated: February 2025.
842,296 professionals have used our research since 2012.