blackfire.io vs. IBM Engineering Lifecycle Management

blackfire.io is best suited for any company that has a development team managing code releases into different environments. This tool is crucial in cases where there are codebase changes or upgrades and it really helps in load testing and code validity. With every new codebase release there could be a risk of how it affects the infrastructure supporting it so blackfire.io helps report on those metrics.

Incentivized

IBM Engineering Requirements Management DOORS former IBM Rational DOORS profits very much from the mighty market position it had till today. It had been the most favored requirement engineering tools suite with the highest investments in the infrastructure concerning hardware, software, and knowledge sources. It was embedded in knowledge sources of test stands, hardware labs, and knowledge database servers. It allowed for some of the highest profit changes and made the fame with it. But the paradigms of requirements engineering change. If not were superseded by completely different approaches for the target solution worlds. The foremost position in the selling tables is unstable if changes are not solved or coped with by the strategist at IBM and their customers. Since the highly successful alternative suits are already at the market, and some are from IBM already the lifecycle for IBM Engineering Requirements Management DOORS is at the later highs. But the suite is still at the very top and very popular. There are still many problems unsolved and many wishes at the customers to make the use more comfortable and efficient at the overall level. If the time of setting up the software package is passed the adoption get more extended and complicated. There is a lot of work at the stage around and the expertise will be required for a long time from now.

Incentivized

• Provide details on processes eating up valuable server resources
• Alert against bottlenecks and find bottlenecks
• Performs load tests in code before moving to production environments

Incentivized

• 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.

Incentivized

• They count same API endpoint AND same method (e.g. POST, OPTIONS, GET etc) as different profiles
• Customer service needs a lot of improvement
• The documentation can be a bit more detailed to remove any scope of doubts

Incentivized

• 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.

Incentivized

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

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

The pricing offered by blackfire.io was highly competitive and customisable as we opted for pay per use pricing model. Initial setup was very easy. The support team provided us with the detailed demo of the product and helped with the initial integration and setup. We already had tried our free version as well and the results looked good. So opted for blackfire.io

Incentivized

Unfortunately, this IBM ELM installation predates my tenure, and the project and client have become entrenched in it with no viable way to move off of it. There are better products capable of doing individual workflows well. ELM's attraction is that it does a lot of things OK.

Incentivized

• Reduce in bugs by 50%, more happy customers
• 2x decrease in load time for the website
• 100% performance validation before production release

Incentivized

• 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.

Incentivized