Intland Software's codeBeamer ALM is a scalable Agile Application Lifecycle Management platform that focuses on traceability and compliance. codeBeamer ALM supports both Agile and Waterfall, and offers a scalable solution for both small and large organisations to develop better products faster. The vendor says their customers think about the benefits of codeBeamer ALM in terms of higher efficiency and effectiveness along the lifecycle, with the goal of cutting development time and…
N/A
IBM Engineering Lifecycle Management
Score 7.0 out of 10
N/A
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
Pricing
codeBeamer ALM
IBM Engineering Lifecycle Management
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
codeBeamer ALM
IBM Engineering Lifecycle Management
Free Trial
Yes
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
Optional
No setup fee
Additional Details
Perpetual and rented licenses available. Named users & floating license types can be combined.
In my opinion codeBeamer is well suited for any activity where detailed tracking is needed with teams involved. It can be less suited for small projects which do not last long, or are not continuous, etc
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.
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.
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
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.
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.
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.
