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 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."
"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."
"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."
"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."
"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 modeling is a game-changer."
"The optimization technique helps in giving us the minimum number of test cases with maximum coverage."
"The solution helps a lot with scrums."
"The most valuable feature is that it has different APIs available, with good services, and it is completely by the books."
"The most valuable features in Jira are the dashboard, reports, and boards that help us to control the advancement of the project."
"We use it for capacity planning. We need to gauge and assess whatever is coming to our pipeline and then everything comes to the pipeline, appears as a pic, and then based on that, we create the story points and we take it from there."
"It was easy to use. The consultants that we had on board were familiar with it. So, obviously, having a community that had used it before or was familiar with it was a positive thing."
"The solution provides users with clarity in terms of the scope of work in a given timeframe."
"We do not have a lot of time for investigating new things, but Jira has saved us a great deal of time. It has a nice user interface and we can do a lot of things with it."
"Perfect for keeping track of large amounts of bugs, tasks queries and releases for fixes."
"A valuable feature from my side would be the comparison corporization."
"We worked with the web interface."
"The solution is especially great for organizing folders effectively."
"My company mainly utilizes the product for documenting internal standards, guidelines, and requirements. Currently, we're focusing on using it for internal purposes, but the vision is to expand its usage to include contract requirements and tracking functionalities. While we're not there yet, it has proven effective for managing our internal documentation needs."
"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."
"Polarion Requirements' most valuable features are link tracing, book entry, and sequence training features."
"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."
"Its flexibility and APIs are the most valuable."
"I think it's already coming, but it needs more automation aspects. There is a tab for Automation, but I think it's not robust. I think that it's going to be a crucial element of the tool."
"They do not have an engine to house test scripts to really pull together the testing pieces of it."
"Integration with Agile management tools can be improved, i.e., mainly test case maintenance and linking test cases to the automation script."
"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 be more user-friendly. For example, attachments could be icon-based to make it easier for the user to notice them."
"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."
"Needs improvement in aligning models so they look clear and readable without having to move boxes around."
"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."
"Jira could provide more insight into sprints such as how did we perform in the last sprint compared to other sprints. It would be helpful to have metrics and a dashboard feature for others to see."
"Jira could be more, for example, like Micro Focus, which is what I mostly work with currently."
"A more organized hierarchy is important. Reporting and JQL create issues for me. They do not completely cover the reporting part that I need to report in terms of my capacity to plan. In the same token, there is no record at this very moment to provide me with one export with epics story points, tasks, or issues and their sub-tasks at the same time."
"I don't know if it's the way it's deployed in the organization, but the interface we are provided is not as customizable as other tools. The multi-language report is not enabled in our installation. I don't really know if it's something related to the tool or our installation."
"It is not capturing the number of hours for which each person has worked on certain things. We use many add-ons to let resources enter the time in the user story itself. We use an add-on called Tempo, but it is kind of a lousy add-on. It is not straightforward. Rather than helping us, it creates a lot of confusion. So, instead of looking out for the additional add-on, I would prefer to have the timesheet entered as a part of Jira itself. They are anyways capturing every information they could for each user story, and then we are able to break down all the task lists. For each task, we're also assigning a resource. So, while we're doing it, why can't they allow the users to enter the time that can be created as a report? Right now, we need to acquire the add-on, and the add-on is not great. It is not helping. The add-on is also not free."
"The tool should improve its pricing."
"Jira lacks easy capacity calculation compared to TFS, making it harder to know how much work to allocate to each specialist."
"The way to configure it can definitely be improved. It is very difficult and complex to configure. Its configuration should be simplified."
"If we have more than one thousand work items in one live-book then it becomes almost unusable."
"The risk assessment functionality needs improvement, like FMEA risk management."
"Polarion Requirement needs to have a feature where we can track changes and compare documents. Currently, we do it manually."
"It is stable enough but if you would like to work with more requirement objects, then you will get timeouts."
"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."
"The usability of the solution should also be improved."
"Integration can be a little tricky if you're not aware of basic computer science or programming language."
"It is not a stable solution, as we had issues with shared licenses."
More Broadcom Agile Requirements Designer Pricing and Cost Advice →