"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."
"Integration with automation is one of the reasons we started to consider moving to this tool from our original tool for implementing test modeling. ARD appears to have better integration with Selenium. It also has the ability to record scripts/flows using Selenium Builder and import them into ARD, which will then create and optimize a model based on that."
"The support that we get from Broadcom is great."
"Measuring test coverage helps in one of the most challenging tasks. It has logic that can help to select the right set of scenarios and know what coverage it will provide."
"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."
"Integration with TDM, test data management tool, provides the ability to generate data or use identified (preset or parametrized) test data. It allows significant expansion of test coverage and flexibility, without creating new tests and needing to maintain them."
"I like that all of the team members on an agile team can use it. No one is in a separate application."
"The most valuable features in Jira are the dashboard, reports, and boards that help us to control the advancement of the project."
"The solution offers up great transparency that makes it possible for everyone inside the departmental organization to see what's happening."
"It's an open-sourced product that is easy to customize."
"Jira is flexible and accessible for the end-user. It lets users track their requests. The look and feel are good for our purposes."
"Workflow administration is an easy process, especially with respect to defects."
"The agile framework works well, and I pretty much live by that. Everything, such as sprint management, is laid out."
"The initial setup isn't too complicated."
"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."
"The solution could improve security and authentication."
"A lot of the user interface could be updated."
"I would like our clients' IT group to be able to have oversight without setting up agents. We're managing tickets, and I'd like their IT group to see everything we're doing without having to set them up as agents. There should be a better way of managing their users. I've got such requests, but Jira is expensive, and it is difficult to pay an agent fee for somebody else to view these tickets. Currently, the only way in which I can do that is by setting a user up as an agent, and it becomes cost-prohibitive. They need to do a better job on ticket viewers."
"I'd like some more features around software testing. I'd like to see some more stuff done around data testing. That's what I'm most interested in."
"I have to go through a lot of processes to consider it done. I have to log in then change the logins and make it interesting. It's not so good for testing."
"Lacks field-level permission in the cloud version."
"Lacks some common building block approaches to certain things."
"In general, although we use JIRA, we never really learned how to use it properly. The learning curve of the solution is high. It has a lot of power, and yet we don't understand its capabilities."
"Something I do not like about the new version is that there is a need to browse all the way back to the beginning, should a person click on a task that is specifically for his group and wish to go back and look at the other portfolios or people."
More Broadcom Agile Requirements Designer Pricing and Cost Advice →
Broadcom Agile Requirements Designer is ranked 4th in Application Requirements Management with 2 reviews while Jira is ranked 1st in Application Requirements Management with 135 reviews. Broadcom Agile Requirements Designer is rated 8.0, while Jira is rated 8.0. The top reviewer of Broadcom Agile Requirements Designer writes "User-friendly with great UI but could offer an easier setup". On the other hand, the top reviewer of Jira writes "Great for collaboration, very stable, and extracting data is straightforward". Broadcom Agile Requirements Designer is most compared with Cognizant ADPART, Tricentis Tosca, Micro Focus ALM Quality Center, IBM Rational DOORS and TFS, whereas Jira is most compared with Microsoft Azure DevOps, Micro Focus ALM Octane, TFS, IBM Rational DOORS and Rally Software. 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.
