Skip to main content
TrustRadius
IBM Engineering Lifecycle Management

IBM Engineering Lifecycle Management

Overview

What is IBM Engineering Lifecycle Management?

IBM Engineering Lifecycle Management (ELM) is an end-to-end engineering solution used to manage system requirements to design, workflow, and test management, extending the functionality of ALM tools for better complex-systems development.

Read more
Recent Reviews
Read all reviews

Awards

Products that are considered exceptional by their customers based on a variety of criteria win TrustRadius awards. Learn more about the types of TrustRadius awards to make the best purchase decision. More about TrustRadius Awards

Return to navigation

Pricing

View all pricing
N/A
Unavailable

What is IBM Engineering Lifecycle Management?

IBM Engineering Lifecycle Management (ELM) is an end-to-end engineering solution used to manage system requirements to design, workflow, and test management, extending the functionality of ALM tools for better complex-systems development.

Entry-level set up fee?

  • No setup fee

Offerings

  • Free Trial
  • Free/Freemium Version
  • Premium Consulting/Integration Services

Would you like us to let the vendor know that you want pricing?

23 people also want pricing

Alternatives Pricing

What is Jira Software?

JIRA Software is an application lifecycle management solution for software development teams. It allows users to create, prioritize and track the progress of tasks across multiple team members, and offers a wide range of integrations. It is offered via the cloud and local servers.

What is iRise?

iRise offers a prototyping and design platform for software development.

Return to navigation

Product Demos

Using IBM Rational Team Concert and IBM Rational Rhapsody for Android development

YouTube

How to integrate JIRA with IBM Rational Team Concert (RTC)

YouTube
Return to navigation

Product Details

What is IBM Engineering Lifecycle Management?

IBM Engineering Lifecycle Management (ELM) is an end-to-end engineering solution used to manage system requirements to design, workflow, and test management, extending the functionality of ALM tools for better complex-systems development.

IBM Engineering Lifecycle Management Competitors

IBM Engineering Lifecycle Management Technical Details

Operating SystemsUnspecified
Mobile ApplicationNo

Frequently Asked Questions

IBM Engineering Lifecycle Management (ELM) is an end-to-end engineering solution used to manage system requirements to design, workflow, and test management, extending the functionality of ALM tools for better complex-systems development.

Rally Software are common alternatives for IBM Engineering Lifecycle Management.

Reviewers rate Support Rating highest, with a score of 5.

The most common users of IBM Engineering Lifecycle Management are from Enterprises (1,001+ employees).
Return to navigation

Comparisons

View all alternatives
Return to navigation

Reviews and Ratings

(57)

Attribute Ratings

Reviews

(1-4 of 4)
Companies can't remove reviews or game the system. Here's why
Score 7 out of 10
Vetted Review
Verified User
Incentivized
DOORS is our tool of choice on large programs with a large number of requirements to manage at various levels of integration.
  • Parent to child requirement traceability
  • Auto tracking of all changes made to an object
  • Ability to create a toolkit to generate documents straight from DOORS
  • Linking between DOORS modules using DXL
  • Not web based
  • Better interface with other tools
  • Ability to track requirements approval and sell off
DOORS works well for requirements management. It's better than using MS Excel especially for a large number of requirements at different levels.
  • Easy tracking of requirements
  • Common to multiple programs
  • Home grown toolkit available
  • Ability to generate document straight from DOORS is a big plus.
  • Ability to track all changes is a big plus when doing multiple iterations or updates to requirements.
  • Need wider use of DOORS by all stakeholders.
DOORS is the legacy and leading tool for requirements management. It is widely used by the Aerospace industry.
Internal to our company we have several experts who have extended DOORS functionality to include some great features. And these folks are well regarded by IBM as DOORS experts in the industry.
It's easy to use and learn. Not too complex and functionality can be extended by learning DXL.
October 16, 2020

Powerful but Clunky

Kathy Ding | TrustRadius Reviewer
Score 5 out of 10
Vetted Review
Verified User
Incentivized
We use DOORS as a requirements repository for the product and software. We use it to track, edit, and trace requirements coverage. It's used all across the business group I'm a part of amongst many roles. It is robust and large enough for all of our products both current and legacy.
  • Stores requirements
  • Compatible with HP ALM
  • Filters well and is customizable
  • Terrible UI and not intuitive
  • Too slow to connect to, launch and run
  • Scripts to use the features are way too complicated to write and maintain.
It is quite powerful and robust as a tool for all of our requirements. It is also compatible with HP ALM, our formal test management tool so that we are able to export comprehensive trace matrices for reporting purposes. However, it is a clunky, difficult, and extremely slow tool that is not well adapted to agile software development.
  • Wastes time to get access, connect.
  • Many other tools are faster and easier to use.
DOORS is not a suite nor an integrated tool like HP ALM or Rally. It only does one thing and cannot hold defects or accommodate sprint planning. It is older, takes longer to connect and load, and has an inconvenient timeout. It does do a basic job and can be customized to show a clear picture of requirements coverage but it takes some training to use.
Jira Software, Rally Software (formerly CA Agile Central)
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.
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.
Score 9 out of 10
Vetted Review
Verified User
Incentivized
Rational Team Concert - RTC, is being used by a project team to facilitate software development. We define user stories, fill a backlog with epics and stories. We then prioritize and rank the backlog, and groom the stories to match our working velocity for the sprint. Rational Team Concert facilitates the requirements documentation, the sizing of the stories, and tracks our progress when used consistently.
  • Easy to use
  • Traceability
  • Generation of Reports
  • Customization to match your implementation
  • Can be self documenting and recording of history
  • Most reports and queries just display data graphically for trending. It would be nice to be able to easily build tabular reports.
  • The application is logistically complex, meaning there are many moving pieces to keep track of. One needs to work with the application learn it. Some people have trouble with this when they are new to RTC and have tight developmental time lines.
  • Running the RTC in house requires trained, dedicated staff. Upgrades are difficult and require expert level knowledge.
It is more suited to an Agile development methodology. However, it is not a replacement for or crutch to be used instead of a strong, disciplined Agile development staff. The software facilitates your existing process. It would be highly recommended to mature your Agile methodology before software acquisition. The software in a less mature environment, can allow bad habits to impact the Agile methodology discipline.
  • Better organization of requirements
  • Effective assignment of priorities
  • When estimating the size of stories and tasks become predictable, it facilitates sprint planning.
  • There is a very positive ROI when a disciplined, mature development team use use the software.
This product had many of the same features, was easier to use, which would result in less training, and had a lower price tag. Logic and reason do not always figure prominently in a decision. Sometimes there are intangible characteristics that alter the flow. In my observation, there was a pending reorganization and a major shift in development methodology that were to come. It was believed that alignment with IBM's Rational Team Concert, we would have better overall support from a pre and post sales perspective, as well as any required responses to "break-fix" activity via their customer support line. IBM also has a fairly large user community at Jazz.net, so that forum is also available for research. These types of items were less developed in other vendor offerings.
4
Training either in house or away from the office was not possible, thus the skill set of the individuals required in part, that they were interested enough to explore RTC and figure out the behaviors. We instituted a weekly meeting, where the administrators would meet and discuss the issues and new found/understood features. We used our own internal WIKI to document the features we discovered.
The software had become so ingrained, that one should not further fragment the software requirements, the test plans/test cases, and the results. We chose a path to implement a centralized repository structure. Additionally, since this requires an expert staff, and there is a hosting service employed, this is really easy to use. It would create much discourse if a whole new direction were taken,and the artifacts (requirements, test plans, test cases, test results, etc) were again.
  • Professional services company
CloudOne was used. They managed the installs, upgrades, and patching, as well as the hosting services. They have the expertise to keep the environment up and available, and even create a "go to" environment, as a prelude to upgrades, and port your data over. They typically see the upgrades and patches multiple times, as they work through their client list. Thus, they know the processes extremely well, and are fast and efficient. CloudOne service was found to be more economical and reliable than using our own hardware and IBM professional services.
There are a number of pieces to Rational Team Concert, though, with honest time working with the software, it can be easily learned while using the software on the job. While I have been an administrator for the software, and have conducted training, it is business software. It is not intended to be enjoyable as in playing a game, though it is perfectly reasonable and acceptable for the intended tasks.
Srivardhan Dingari | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User
Incentivized
The whole team uses IBM Rational Team Concert. The main focus is to write change requests which includes implementation work tickets, reviews etc.
  • Dead Lines are clearly assigned through change requests
  • Tracking the assignments (Implementation Work Tickets)
  • Process
  • GUI can be implemented much more efficiently with clarity. I personally feel the current IBM Rational Team Concert is little clumsy.
  • Increased employee efficiency is definitely a point to be considered when all the employees are resolving the change requests in a timely manner.
It is easy for the organization to identify what kind of problems there are in the project and how many change requests have been resolved and how many are pending. Thereby the employer can pro-actively arrange the meetings and address the issues to the team members.
50
Automotive
5
There are people who train us. Also the dedicated team which helps when IBM - RTC is non functional
  • Change Requests
  • Ballets
  • Work Tickets
  • Change Requests
  • Tracking the project
As I am using the latest version of IBM-RTC I hope I am happy with it. If the advanced version comes with more features, I would definitely like to use it.
No
  • Product Usability
  • Product Reputation
  • Prior Experience with the Product
As the tool has the facility to use in web mode as well as desktop level, I feel it is very convenient.
Checkout criteria
No problems
  • Implemented in-house
No
Change management was minimal
  • None
As I have no issues so far with IBM Rational Team Concert I recommend the team / Employer to go with it
Not Available
Yes
The tool was not showing the required tabs. There was an issue and was fixed by my supporting team
As said earlier, I was unable to view my project and all the required tabs in the tool. I struggled a lot to fix the issue. Finally it was resolved by the support team by correcting the code.
As I am using it.
  • Ballets, CRs
  • Traceability
Return to navigation