We performed a comparison between Broadcom Agile Requirements Designer and Jira based on real PeerSpot user reviews.
Find out in this report how the two Application Requirements Management solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."In terms of meeting business challenges, it helped to shorten the dev/testing cycle by identifying requirements gaps early in the process, by having models shared within the development team. It helped increase test coverage and reduce the number of issues experienced by clients/customers."
"The modeling is a game-changer."
"Technical support is excellent. They provide solutions quickly for issues encountered."
"The scale possibilities are endless, especially when combined with all the other products that CA has to offer."
"The ability to create models/diagrams at multiple levels (nest/embed them) helps in taking models from high-level business requirements and building them into detailed requirements models and test models. Plus, it helps reuse lower level models. It also allows maintaining models at appropriate levels, even for very complex systems/solutions."
"Helps the communication between the testing organization and the requirements group. It helps us to simplify the work. Instead of dealing with individual test cases, you're working with a model."
"The support that we get from Broadcom is great."
"It takes away all the time to construct test cases, so it is all automatic now, but it also levels the playing field."
"The UI is good. It's simple and not very complicated. It's very good for tracking."
"I like the test cases in Jira. The orange dash items view was great, and I like the features and layout of the data. It's quite different, and people are now getting their items so quickly."
"In terms of the general way that the tool functions, it seems like it's a pretty good fit-for-purpose for what we're trying to do. We've never thought about replacing it with another technology."
"The board has been a very valuable feature because it can be very simple for teams that are not technical. It can also be highly technical and have lots of data for teams that are technical. So we use it for both instances."
"The user interface is simple."
"When we run the Jenkins pipeline, the build is already automatically connected to Jira. We've been able to integrate the ecosystem we created using this automation tool."
"The configurable workflows and boards make it easy for us to execute and oversee our own unique process."
"The most valuable feature of this solution is the source linking on the commit level to git."
"The solution could improve security and authentication."
"Needs improvement in aligning models so they look clear and readable without having to move boxes around."
"It would help if it would save different subsets of test cases, use cases, etc., of a given diagram, for different purposes and provide an easy way to name those subsets."
"They do not have an engine to house test scripts to really pull together the testing pieces of it."
"Broadcom Agile Requirements Designer could improve the UI. Other solutions have a much better UI. The new UI should have a new modern framework."
"A template in App Test should be created in advance. This has proven to be time consuming. The process is not fully automated, because there is a lot of manual intervention is required."
"CA ARD doesn't provide integration with Tosca. The possibility of creating a test case and exporting it into Tosca is not available. Integration with end-to-end automation tools, like Worksoft or Tosca, is not provided by CA ARD as of now."
"At present, there is no option for test data parameters from ARD for virtual databases. We have to create them in TDM and push them as well. Virtual database connectivity needs to be improved. They need to come up with some areas where they can create synthetic data parameters easily from the test cases that have been designed."
"They can maybe dumb down the directions for building the automation a little bit because to be able to build out the automation, I had to play around with it and learn what all the fields meant and what they were referencing. I don't have an IT background originally. My background is in biology, and I got into project management by chance. I am good at it, but I haven't really worked with coding languages. In terms of writing automation, it is easier for devs because they intuitively know what they're being asked, but as a PM who originally didn't have IT experience, it was a little bit daunting at first. It could also have an extra hierarchy to be able to allow tasks under stories. It could be the way it is set up at our organization, but currently, under stories, you can have sub-tasks, but you can't create a task. Being able to customize your hierarchy a little bit more would be beneficial because sometimes, the devs would say, "Well, here's a story, and now we need sub-tasks," but as we were building out the sub-tasks, sometimes we had to go a step lower to dig in a little bit more, and we couldn't do that."
"The integration of Jira could improve. The solution should be able to integrate easily with other solutions, such as ERPs. There are times the solution can be slow and we have to reset it over and over again."
"There is a difference between their cloud and their server versions. The next-gen project, which is an advanced feature that allows you to visualize the road map of your delivery over multiple products and over time, is not available yet for the sever version. It appears there in the list, but it's still not right. I've tried to use it many times and I am watching the device show their tracker, but it seems they intentionally want this to increase the utilization of the cloud instead of the server. It is really a nice feature and it's a shame that we don't have it."
"There needs to be a way to export a user story."
"I want Jira to have more plug-ins, which will allow for more free plug-ins that help with the area of reporting."
"There are no fields to search or to filter by, mainly the ones which use a data around a date and time when something changes."
"When we use the plugin in Jira so, there are two different systems which we are working on, Jira and the X-ray plugin. The X-ray plugin should be incorporated into Jira because we have to fetch two reports. One report is faxed through Jira, and one can be faxed through X-ray. So there needs to be clarity about which the Jira team should reflect."
"The release of a MailServer feature within Jira would be beneficial."
More Broadcom Agile Requirements Designer Pricing and Cost Advice →
Broadcom Agile Requirements Designer is ranked 8th in Application Requirements Management with 20 reviews while Jira is ranked 2nd in Application Requirements Management with 266 reviews. Broadcom Agile Requirements Designer is rated 8.0, while Jira is rated 8.2. The top reviewer of Broadcom Agile Requirements Designer writes "Easy to use, beneficial test case visibility, and effective support". On the other hand, the top reviewer of Jira writes "A great centralized tool that has a good agile framework and is useful for day-to-day planning, task management, and work log efficacy". Broadcom Agile Requirements Designer is most compared with Tricentis Tosca, Adaptavist Test Management for Jira and Sealights, whereas Jira is most compared with Microsoft Azure DevOps, IBM Rational DOORS, OpenText ALM Octane, Rally Software and Polarion ALM. See our Broadcom Agile Requirements Designer vs. Jira report.
See our list of best Application Requirements Management vendors.
We monitor all Application Requirements Management reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.
