Caliber by Micro Focus (formerly Borland Caliber), is an application requirement management offering. It has been discontinued, but similar capabilities are supplied by Micro Focus by Dimensions RM.
N/A
OpenText ALM/Quality Center
Score 7.7 out of 10
N/A
OpenText™ ALM/Quality Center, formerly from Micro Focus, serves as the single pane of glass for software quality management. It helps users to govern application lifecycle management activities and implement rigorous, auditable lifecycle processes.
I personally would prefer other products on the market right now such as Microsoft Team Foundation Server and Test Manager. I think having a product like Caliber that can only do requirements without integrating with a another system makes things a little more time consuming.
For an organisation that has completely adopted SAFe structure including naming terminology, it is less appropriate and apart from that. It can suit any organisation out there, and it can solve all your problems one way or another by customising it. It is a robust and highly scalable solution to support all the business needs. It improves a lot of productivity and visibility.
Borland Caliber tracks functional and non-functional requirements pretty easily. You can easily add a requirement and attach a spreadsheet or a picture if needed.
Moving the hierarchy of requirements is fairly easy by just dragging and dropping.
Assigning users to approve requirements is simple by the fields included when adding a requirement and then submitting for review.
If you have a mix of automation & manual test suites, HPALM is the best tool to manage that. It definitely integrates very well with HP automation tools like HP Unified Functional Testing and HP LoadRunner. Automated Suites can be executed, reports can be maintained automatically. It also classifies which test suites are manual & which are automated & managers can see the progress happening in moving from manual to automated suites. In HPA ALM all the functional test suites, performance test suites, security suites can be defined, managed & tracked in one place.
It is a wonderful tool for test management. Whether you want to create test cases, or import it, from execution to snapshot capturing, it supports all activities very well. The linking of defects to test runs is excellent. Any changes in mandatory fields or status of the defect triggers an e-mail and sent automatically to the user that the defect is assigned to.
It also supports devops implementation by interacting with development tool sets such as Jenkins & GIT. It also bring in team collaboration by supporting collaboration tools like Slack and Hubot.
This tool can integrate to any environment, any source control management tool bringing in changes and creates that trace-ability and links between source control changes to requirements to tests across the sdlc life-cycle.
I think Borland Caliber visually needs to be updated. It looks very out of date compared to other products on the market. The text box has a notepad feel to it and it's hard to make it visually catching.
Borland Caliber needs to be easier to integrate with other testing and development products on the market.
Having fields more related to URS and FRS would be helpful to auto-link to a document. So enter in a URS or FRS document ID at the beginning of a project in Caliber and then auto-assigning requirement IDs to link to pieces of code or test cases and having the user be able to decide a naming convention.
Borland Caliber needs a specific table for linking to a document ID and then each requirement could auto-generate a sub ID for each requirement to make the process of filling in User Requirements and Functional Requirements more efficient. Then the user should be able to modify the sub ID if the naming convention needed to be different.
The requirements module is not as user friendly as other applications, such as Blue Bird. Managing requirements is usually done in another tool. However, having the requirements in ALM is important to ensure traceability to tests and defects.
Reporting across multiple ALM repositories is not supported within the tool. Only graphs are included within ALM functionality. Due to size considerations, one or two projects is not a good solution. Alternatively, we have started leveraging the template functionality within ALM and are integrating with a third party reporting tool to work around this issue.
NET (not Octane) requires a package for deployment to machines without administrative rights. Every time there is a change, a new package must be created, which increases the time to deploy. It also forces us to wait until multiple patches have been provided before updating production.
Because it lets me track the test cases with detailed scenarios and is clearly separated in folders. Also the defect filter helps me filter only the ones that have been assigned to a particular area of interest. The availability of reports lets me see the essentials fields which I might be missing the data on and helps me to work on these instead of having to go through everything.
It is a great tool, however, it got this rating because there is a lot of learning that takes a lot longer than other tools. There are no mobile versions of ALM even with just a project summary view. I believe ALM is well capable of integration with other analytics tools that can help business solutions prediction based on current and past project data. This is Data held in ALM but with no other use apart from human reading and project progress. ALM looks like a steady platform that I believe can handle more dynamic functionality. You could add an internal communication platform that is not a third party. Limit that communication tool to specific project members.
I think Borland Caliber is better than Atlassian Confluence and has way more options for ease of use and reporting. Team Foundation Server is my personal choice as it comes as a package for developers to link to requirements easily and link to test cases. Borland Caliber is visually the least attractive of the three systems I have used. If you need just a requirement manager for tracking and reporting then Borland Caliber is a great choice.
We have other tools in our organization like Atlassian JIRA and Microsoft Team Foundation Server, which are very capable tools but very narrow in their approach and feature set and does not come even close to the some of the core capabilities of HP ALM. HP ALM is the "System of Record" in our organization. It gives visibility for an artifact throughout the delivery chain, which cut downs unnecessary bottlenecks and noise during releases.
