We performed a comparison between Broadcom Agile Requirements Designer, Jira, and Polarion Requirements based on real PeerSpot user reviews.
Find out what your peers are saying about IBM, Atlassian, Siemens and others in Application Requirements Management.
"The most valuable features of Broadcom Agile Requirements Designer are ease of use, saving time for the team who builds test cases, and visibility of test cases."
"It helped us to move from manual testing to automation testing."
"Defects can be traced in the solution."
"CA ARD has some beautiful features which I haven't found anywhere else. For example, when designing or creating our test cases and doing scenarios, we are able to restrict our flows. If we take a data link between two processes, we can actually restrict it, so that, in production, if our functionality breaks down, we can restrict that and all the flows related to it will be removed from the test data set."
"The support that we get from Broadcom is great."
"Technical support is excellent. They provide solutions quickly for issues encountered."
"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."
"It takes away all the time to construct test cases, so it is all automatic now, but it also levels the playing field."
"The burndown charts help track projects."
"The product provides high flexibility to create new workflows quickly."
"The agile framework works well, and I pretty much live by that. Everything, such as sprint management, is laid out."
"You no longer need to email people. You can mention them right in Jira and have conversations there."
"The most valuable feature is managing software development."
"The most valuable features of Jira are all the integrations with other systems. It's not the best in any specific area but it has lots of plug-ins and integrations."
"We have found the structure, functionality, and how Jira handles the tickets most valuable."
"I have experience with Jira's bulk tracking and issue management. We use it to add new features to our product, fix bugs, and address customer feedback."
"I would say there is value in how powerful, configurable, and user-friendly it is."
"Its flexibility and APIs are the most valuable."
"We can easily customize it because of the web services and open APIs. Also, the APIs are available. We integrated Polarion with one of Siemens' products, Teamcenter, which is especially useful for automotive industries. There is an open API for integration with Jira as well, so for me, customization is a strong point."
"The biggest improvement would be in the transparency we have now. We have very complex products. We make whole systems with difficult and diverse areas such as hardware, software, mechanical and printing, etc. To get the overview of all the requirements into a system, at that sizing, is the main advantage we have in the organization now."
"The solution is especially great for organizing folders effectively."
"A valuable feature from my side would be the comparison corporization."
"It is easier to produce documents using the platform."
"We worked with the web interface."
"The solution could be more user-friendly. For example, attachments could be icon-based to make it easier for the user to notice them."
"They do not have an engine to house test scripts to really pull together the testing pieces of it."
"The solution could improve security and authentication."
"Needs improvement in aligning models so they look clear and readable without having to move boxes around."
"Broadcom Agile Requirements Designer could improve the UI. Other solutions have a much better UI. The new UI should have a new modern framework."
"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."
"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."
"Once a story is closed, all the records, versions, and documentation associated with it are gone. We lose the traceability of what was done."
"The pricing is quite high."
"I'd like to see better notetaking capabilities so every user can get notes when someone provides comments on a Jira ticket. So if they don't want to provide the comments on the Jira ticket, they can get the personal notes in a Jira tool for every profile."
"The integration could be better in Jira."
"It would be very practical if you can more freely reach the information that is already inside the system. Currently, we have to buy add-ons for it. There is a lot of information in the Jira system that you can handle only through add-ons. You cannot reach such information on your own. If you want to use this information, which is already in the system, you have to buy some add-on to use. For example, information about how much time an assignee is spending on a ticket is there in the system, but you cannot access it without an add-on. JQL is a very good way to reach the data inside Jira. If we can reach more objects, even through JQL, it would be great."
"Not very intuitive for project admins."
"The thing I don't like is that it is hard to decide which dropdown options should be selected. When we try and submit it, it will state that there are certain mandates in place. It won't allow us to submit the form unless we fill out all the details."
"There needs to be easier integration with third-parties — personally, this is the biggest issue for me."
"The one thing I would mention is the license policy is a little bit difficult. For different roles, you will need different license models. That seems a little bit difficult for us. Especially when you introduce such a complex system, you want to know the right way is to do licensing. It's not clear what that best way would be. The solution will be here for a long time, and I just think it could be more clear."
"One thing to consider is increased flexibility in terms of workflow configuration."
"The platform's review process for the documents could be better."
"The risk assessment functionality needs improvement, like FMEA risk management."
"Integration can be a little tricky if you're not aware of basic computer science or programming language."
"If we have more than one thousand work items in one live-book then it becomes almost unusable."
"We encountered numerous challenges, such as issues with requirements, project management, timing, and planning. The main problem with Polarion at the outset, I believe, was our limited understanding of the planning phase. During that time, we were more focused on change management related to requirements. Recognizing the importance of planning has been a key realization for us. Another mistake we made was not comprehending the need to document these requirements to manage all the work items effectively. Now, we understand the significance of this documentation. As a result of these insights, we have started to see a growing number of competitors from Polarion in this field. One potential improvement could be enabling Polarion to export work items not just to Microsoft Office but also to other office tools."
"Polarion Requirement needs to have a feature where we can track changes and compare documents. Currently, we do it manually."
More Broadcom Agile Requirements Designer Pricing and Cost Advice →
