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 5.1 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
Yes
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
The software is robust enough to handle highly complex software development or other product development and can be used well beyond the range to do what a client needs. However, because of the inability to hold its users to proper best practices, things can get wildly out of hand and cascade over the years, creating unnecessary technical debt. The system has a lot of usable features, but they don't funnel users toward the correct processes and practices.
I feel like it is too heavy sometimes and updating is not very straight forward. For example, if I want to change an incident ticket (IN) to a service request (SR) and add some comment for the change, I have to first change the IN to SR, then click refresh which takes a few seconds, then add a comment. If I forget the refresh step, my comment will be discarded without warning like my ticket is not in the latest status. This also happens when somebody else changes the ticket during my edit as I can not lock the ticket exclusively.
At the moment we are required by contract to continue to use the IBM DOORS software for our current client. Given that it can be expensive, if we were to use it after our current client's needs were met, we would have to secure other projects in order to justify the continued use of the software.
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.
It was easier to do all the change management-related activities, even configurations were handled very effectively. New process definitions and initiatives made it easier for better project deliverables. Effective resource allocations and better reporting and defect management. The overall cost of the tool is great too and well within budget.
It's part of CLM suite so it can be used to manage the whole lifecycle with tight integration with development module (Rational Team Concert) and quality module (Rational Quality Manager).
Comprehensive reports and dashboards provide better visibility.