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 Mar 30, 2025

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
19
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 May 2025, in the Application Lifecycle Management (ALM) Suites category, the mindshare of IBM Engineering Lifecycle Management (ELM) is 3.3%, up from 1.8% compared to the previous year. The mindshare of OpenText ALM / Quality Center is 5.6%, up from 5.5% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Application Lifecycle Management (ALM) Suites
 

Featured Reviews

Juergen Albrecht - PeerSpot reviewer
Combining tools for effective data analysis while customization and integration need improvement
The most valuable feature is how IBM Engineering Lifecycle Management (ELM) ( /products/ibm-engineering-lifecycle-management-elm-reviews ) allows me to present to the customer what the actual software, even hardware, will do. It helps them gain an impression of the complexity of the functionality and find an easier way to decide whether to implement it. A picture says more than one thousand words, which is why I work with the combination of ELM and the specification of DOORS. The automation capabilities I built use column-based scripts for analysis to search, fetch, and transfer information. When I open modules, it automatically analyzes the changes since the last opening by me.
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

"Everyone in a team can work on the same platform and share the same information."
"I would rate the stability of this product a nine out of ten."
"The tools for requirement capture we have found very useful."
"IBM Rational ALM is a very good tool. I like the management and traceability features and the test management tool. The latter is not linked with the stories and fixed management. It is really useful, and we can create test plans. We can also test some metrics related to QA."
"The planning feature is rich with Scrum concepts: Sprint, Sprint retrospective, the rules in the Scrum framework."
"The word emulation and importing is good."
"The integration with Git works well."
"The transition to a SaaS-based solution is a distinct advantage."
"You can plan ahead with all the requirements and the test lab set it up as a library, then go do multiple testing times, recording the default that's in the system."
"What's most valuable in Micro Focus ALM Quality Center is that it's useful for these activities: test designing, test planning, and test execution."
"Ability to customize modules, particularly Defect Tracking module on company specific needs"
"Running automated tests against back-level versions in certain environments is possible, and newer versions can be tested as well."
"I would rate the product a seven out of ten."
"As a stand-alone test management tool, it's a good tool."
"With test execution, you have an option to create custom fields. It is also really user-friendly. With other tools, we only have restricted fields and we cannot customize or add new columns or fields that users can make use of while testing. ALM is very flexible for creating new fields. It is easy for users to understand the application."
"I love linking/associating the requirements to a test case. That's where I get to know my requirement coverage, which helps a lot at a practical level. So, we use the traceability and visibility features a lot. This helps us to understand if there are any requirements not linked to any test case, thus not getting tested at all. That missing link is always very visible, which helps us to create our requirement traceability matrix and maintain it in a dynamic way. Even with changing requirements, we can keep on changing or updating the tool."
 

Cons

"There is not enough beginner support material in the form of FAQs or simple training to help you get started."
"The features should be more intuitive. If I'm looking for something, its location should be easy to locate."
"The interconnectivity between packages is a major support problem and can be improved."
"One of the complaints from users is that they have to click buttons too many times for just a simple task. Changing this would lead to a better user experience."
"Improvement is needed in bridging DNG and Rhapsody and vice versa for better data exchange from both sides with some trigger technologies."
"IBM Rational ALM should remove the features not used by the customers and keep this product as lightweight as possible."
"The stability of IBM Rational ALM could be improved."
"Some improvements to the user interface (UI) would be helpful, such as exposing more services to make it easier to customize to the needs of each customer."
"The UI is very dated. Most applications these days have a light UI that can be accessed by pretty much any browser; QC still uses a UI which has a look almost the same for the past 20 years."
"Micro Focus ALM Quality Center could improve how the automation process works. Addiotnlally, the parallel execution needs to be optimized. For example, if multiple users, which are two or more users, are doing an execution, while we execute the cases, I have seen some issues in the progress."
"Client-side ActiveX with patch upgrades"
"Recently, I faced some issues while using the product on Mac-based machines, as I was unable to upload test cases."
"Micro Focus is an expensive tool."
"The integration could be improved because with Agile technology you are working more quickly than with a top-down methodology."
"Requirements management could be improved as the use is very limited. E.g., they have always stated that, "You can monitor and create requirements," but it has its limitations. That's why companies will choose another requirements management solution and import data from that source system into Quality Center. Micro Focus has also invested in an adapter between Dimensions RM and ALM via Micro Focus Connect. However, I see room for improvements in this rather outdated tool. I feel what Micro Focus did is say, "Our strategy is not to improve these parts within the tool itself, but search for supported integrations within our own tool set." This has not been helpful."
"We operate in Sweden, and there are not so many Swedish people that know the product."
 

Pricing and Cost Advice

"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."
"The solution is not cheap."
"We have a contract, but I am not aware of the details."
"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."
"It is an expensive tool. I think one needs to pay 10,000 USD towards the perpetual licensing model."
"It's a perpetual license."
"The cost of licensing depends on the number of VMs that you are running test cases on and it is not cheap."
"I've never been in the procurement process for it. I don't think it is cheap. Some of the features can be quite expensive."
"We pay around $30,000 for thirty users, translating to approximately $6,000 to $10,000 per user, which is high."
"Micro Focus ALM Quality Center is very expensive. The price is approximately £2,000 per person, they are too expensive to corner the market."
"Pricing is managed by our headquarters. I am able to get from them for very cheap. The market price is horribly expensive."
"ALM Quality Center is a little bit costly."
report
Use our free recommendation engine to learn which Application Lifecycle Management (ALM) Suites solutions are best for your needs.
849,686 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Manufacturing Company
26%
Computer Software Company
11%
Government
9%
Healthcare Company
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: April 2025.
849,686 professionals have used our research since 2012.