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.
N/A
Polarion ALM
Score 9.8 out of 10
N/A
Polarion ALM is an application requirement management software platform now owned and supported by Siemens since the 2015 acquisition. It is available on the cloud (Polarion X) and on-premise. Polarion connect teams and projects to improve application development processes with
a single, unified solution for requirements, coding, testing and release.
While working on a complex project it is important all the needed change requests are handled in an effective manner, this tool helps us do exactly the same, it had great features to manage those change management tickets, making sure to merge the change with existing workflow, prioritize the requests centrally so there are no duplicates. Easy to collaborate across different teams and colleagues across the aisle.
Polarion ALM shines where it is intended to be used: Application Lifecycle Management. It fits well with agile development concepts, but the extensive customization abilities allow it to adapt to other concepts, too. It is suitable as an all-in-one solution, which is capable of giving transparency over all related areas, be it Requirement Management, Test Management, Release Management, Defect Management, etc., to the involved stakeholders.
There are a couple of areas where IBM Rational DOORS is quite strong. First, it is part of the IBM CLM solution so the artifacts developed in this module can be easily available for other functions like development and QA. They can link with their stories and test cases and team leads and managers can use traceability matrix to find out where there are gaps in coverage.
Comprehensive configuration management functionality (concept of multiple streams and global configuration) is available, which can be helpful if you need to implement configuration management scenarios for your product or project. For example, a certain version of a requirement can be linked with one story and another version of same requirement can be linked with another story. This is the unique feature which other current tools in the market don't provide.
It's highly customizable so you can configure the project areas based on your need. You can have your own requirement types, and you can define templates to speed up the process. Comprehensive review functionality is there as well.
Requirement management in Polarion is extremely effective, with a simple but powerful authoring environment, simple approval process management, seamless traceability and advanced reuse capabilities
Test management capabilities allow to link together the requirements with the validation process, and let the user define, plan, execute and record tests across the whole development process
Day bay day management of development is easy to track, with out of the box support for agile methodologies, live planning reports and integration with Git, SVN and CI/CD tools.
Too complex for projects or businesses that don't really need the detail. It is basically overkill.
If you are new to IBM Rational tools, it may be a medium learning curve. You'd also need lots of training from your people, since, as usual, this tool shouldn't be managed alone.
It may seem old fashion compared to Jira and the current control tools used in IT industry.
One of the downsides for us was the capabilities of the native build tools were lacking. The project management and work item tracking capabilities are great and I would recommend the tool to anyone. There is a definite learning curve with RTC as a source control system, and the streams are a concept unique to the product
There is too much at stake to go into a new system. But with everything else being promised as far as newer more innovative products, the justification to not renew is a huge risk so that is not a concern
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.
Polarion ALM can be used individually and what I do with Polarion ALM is decided by my configuration. Lesson-learned, operational risk management, product, system or software development or customer management .... doesn't matter at all. I decide with my configuration what I will do with Polarion ALM. Of course, you can also use Polarion ALM out-of-the-box for your development because it comes with a large set of project templates.For this reason, I would also recommend not to just get started. A suitable consultant will show you the right templates and customize them according to your needs. Having Polarion ALM is like having a car. You know exactly how to operate the car. You've done it a thousand times before. The details are in the configuration: did I have a navigation system installed or not? Do I have a lane departure warning system or not? Do I have cruise control or not? Unlike when buying a vehicle, almost all functions are already available and can be used, usually at no extra cost. However, if something is missing, it can be obtained via the manufacturer's extension portal. Individual extensions are subject to a charge. Polarion ALM - easy to deploy and easy to use.
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 established experience contained in most IBM Rational DOORS installations is only compensated by the high flexibility of Atlassian JIRA. The markets state that Jira is less expensive in the setup. There are many manufacturers that support IBM Rational DOORS to have the big tiers as their customers. Jira has problems in that growth. Jira has more features compared to IBM Rational DOORS. For example in cloud support, IBM Rational DOORS relies on improved external services while Jira abstracts in the most modern way. Jira experts have a different professional background compared to that of IBM Rational DOORS. They are indeed from different engineering generations. There is little interchange in personal and ideas.
Some tool suites look cheaper at first, but the hidden costs make it expensive in the end. This also applies to the operation of the application or, in the case of some manufacturers, I would have to speak of stitched applications. Regardless, with all tools it becomes critical at some point. We have found for ourselves that when safety and/or security come into play, things get tricky with most applications. Ultimately, it is and remains a matter of taste and the food should be based on the requirements and not on personal sensitivities. I hope everyone makes the right decision for themselves and the company.
RTC helps automate incident management workflow which improves our work efficiency. With the integration with Geneos and GSD, we can one click create RTC incident tickets from Geneos with most of the information copied from Geneos automatically and then link the details to GSD for privilege account management if needed.
RTC provides a holistic view on ad hoc production activities. We use RTC for production management. Whoever needs to get access to production due to non-planned activities (planned change is managed in GSD) has to raise an incident ticket or service request ticket in RTC so as to get production privilege accounts.
RTC is also being used to review and approve the usage of privilege account which help us to meet audit requirements. For example, if a user made some database change using privilege account under incident number xxx, an entry will be added in RTC and sent to account owner or production support manager to review and approve.
The traceability features in Polarion ALM help identify and address issues early in the development cycle
Polarion ALM provides real-time dashboards and reporting, offering stakeholders visibility into project status, progress, and quality metrics.
The initial implementation of Polarion ALM may require time and effort. Some organizations may face challenges in adapting to the tool, and there might be a learning curve for users, especially those new to ALM solutions.
