Broadcom Agile Requirements Designer Overview

Broadcom Agile Requirements Designer is the #1 ranked solution in our list of top Test Design Automation tools. It is most often compared to Cognizant ADPART: Broadcom Agile Requirements Designer vs Cognizant ADPART

What is Broadcom Agile Requirements Designer?
CA Agile Requirements Designer is an end-to-end requirements gathering, test automation and test case design tool which drastically reduces manual testing effort and enables organizations to deliver quality software to market earlier and at less cost. The optimal set of manual or automated tests can be derived automatically from requirements modeled as unambiguous flowcharts and are linked to the right data and expected results. These tests are updated automatically when the requirements change, allowing organizations to deliver quality software which reflects changing user needs.

Broadcom Agile Requirements Designer is also known as Grid Tools Agile Designer, CA ARD, CA Agile Requirements Designer .

Broadcom Agile Requirements Designer Customers

Williams, Rabobank

Broadcom Agile Requirements Designer Video

Pricing Advice

What users are saying about Broadcom Agile Requirements Designer pricing:
  • "Recommendation is to go with concurrent licenses as oppose to seat license; this gives more flexibility."

Broadcom Agile Requirements Designer Reviews

Filter by:
Filter Reviews
Industry
Loading...
Filter Unavailable
Company Size
Loading...
Filter Unavailable
Job Level
Loading...
Filter Unavailable
Rating
Loading...
Filter Unavailable
Considered
Loading...
Filter Unavailable
Order by:
Loading...
  • Date
  • Highest Rating
  • Lowest Rating
  • Review Length
Search:
Showingreviews based on the current filters. Reset all filters
Lana Rousakovski
Senior Leader in Software Testing and Process Improvement at a tech company with 10,001+ employees
Consultant
Top 10Leaderboard
Feb 4, 2021
Eliminates requirements gaps early in the development process & make test design process more efficient

What is our primary use case?

Creating models for requirements definition and alignment, starting with high-level requirements definition and expanding models into detailed requirements to test models (manual testing). Also, creating models and analyzing and selecting appropriate test scope/coverage.

Pros and Cons

  • "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 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 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."
  • "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."
  • "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."

What other advice do I have?

It is important to ensure that people first understand modeling concepts and the organization's defined modeling best practices before jumping into tool implementation. It is critical to get management support, as for some people test modeling is a very new way of thinking and they would find many reasons to push back. Check CA's videos on modeling available on CA's Youtube channel, before starting to implement the tool itself.