I rate Broadcom Agile Requirements Designer as 8 out of 10. It will be very nice if Broadcom has questions or comments related to my review and can reach me via email to clarify something. I want to be a reference for Broadcom. I don't have any information regarding the visual modeling function specifically. I'm not dealing with modeling requirements or generating optimized test cases in Broadcom Agile Requirements Designer. Broadcom takes a lot of information from us as end-users, and they provide fixes within two to five days maximum. My team has raised many enhancement requests and discussed them with Broadcom, and they are adding some of these features to the product itself. I look forward to receiving an email regarding these reviews, and I can add anything later if I forgot something, earning some points for this contribution on the website.
From an integration standpoint, it is well-suited for integration into the DevOps or platform engineering pipeline. I rate Broadcom Agile Requirements Designer an eight out of ten.
Overall, I would rate Broadcom Agile Requirements Designer at eight out of ten because there are better tools available in the market that create test cases in such a way that parameters come out easily. Tools such as Tricentis interact well with virtual data warehouses and are able to get at the parameters. However, if you already have Broadcom TDM, then Broadcom ARD may be a good fit for you.
Test Engineer Senior Analyst at a tech services company with 10,001+ employees
Real User
Jan 24, 2019
I have to become more familiar with the automation part of CA ARD, and then maybe I'll come to the point of saying that it is a good tool which enables you to take your automation, the testing and development, from deployment and designing of your test case, to pushing them into your testing module - whatever tool you are using; that it is an end-to-end solution. I would rate this solution at six out of ten. I'm working on Tosca, which is also an end-to-end solution for testing, and I see Tosca as a better option to use, except that Tosca is very costly compared to CA ARD. There are other tools as well, like RPA for process automation. CA ARD is lagging in competing with these tools. As an automation tool, it might not be the strongest.
For us, the process of implementing it starts with getting in touch with one of our internal teams and giving a business case for why we are going to use this tool and what the users' rights will be: for example, edit or delete or whatever functionalities we require. They will register us for the solution. Once this is completed, it will trigger an email so we can start using the tool. First, we create the backlog. I work on it from a business analyst perspective and I help the project management team to understand what all the backlogs are that we are maintaining for the upcoming versions. As a business analyst, I note the requirements for the respective backlogs, based on business priorities. Then we pull them into the particular sprints. It will then move to the development team to start looking at each of the user stories. They will divide these user stories into particular, technical tasks. From the testing team point of view, they create, under the same user story, their tasks and start giving their descriptions, including the defects. Once it is completed, we have a UAT done and we update the status of each of these user stories as completed, or in progress, whichever is applicable. Deployment depends on the complexity of the application. We have 25 to 30 people using it in the current project. In my previous organizations, the same tool was used by more than 125 to 130 people. There are different types of users. Business people are also involved, as well as technical testing people, project managers, etc. Different stakeholders are involved. We are implementing it in many projects now. It was not being used as much, in practice, in the organization where I am working, but we are now scaling it up to multiple teams, so that everyone will get the benefits. To scale up to different teams may take another year. There are different service lines in the organization and each of them has to adopt this technology. They are slowly picking it up.
Learn what your peers think about Broadcom Agile Requirements Designer. Get advice and tips from experienced pros sharing their opinions. Updated: December 2025.
I would advise to use this product, because it is a good way to create models and establish model-based process testing. The optimization technique with integrations is seamless, and a very good tool. It gives us an idea of creating the visual diagrams, which are quite easy to use. It is helpful in creating our business processes. The optimization technique helps in giving us the minimum number of test cases with maximum coverage.
If you are looking to implement model-based testing, reduce the effort required for documenting the requirements, test case creation, automation script generation, maintenance of test cases, and automation scripts, then go for it. It will bring great savings to your organisation.
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.
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...
I rate Broadcom Agile Requirements Designer as 8 out of 10. It will be very nice if Broadcom has questions or comments related to my review and can reach me via email to clarify something. I want to be a reference for Broadcom. I don't have any information regarding the visual modeling function specifically. I'm not dealing with modeling requirements or generating optimized test cases in Broadcom Agile Requirements Designer. Broadcom takes a lot of information from us as end-users, and they provide fixes within two to five days maximum. My team has raised many enhancement requests and discussed them with Broadcom, and they are adding some of these features to the product itself. I look forward to receiving an email regarding these reviews, and I can add anything later if I forgot something, earning some points for this contribution on the website.
From an integration standpoint, it is well-suited for integration into the DevOps or platform engineering pipeline. I rate Broadcom Agile Requirements Designer an eight out of ten.
Overall, I would rate Broadcom Agile Requirements Designer at eight out of ten because there are better tools available in the market that create test cases in such a way that parameters come out easily. Tools such as Tricentis interact well with virtual data warehouses and are able to get at the parameters. However, if you already have Broadcom TDM, then Broadcom ARD may be a good fit for you.
We're a Broadcom partner. I'd rate the solution at a seven out of ten.
I have to become more familiar with the automation part of CA ARD, and then maybe I'll come to the point of saying that it is a good tool which enables you to take your automation, the testing and development, from deployment and designing of your test case, to pushing them into your testing module - whatever tool you are using; that it is an end-to-end solution. I would rate this solution at six out of ten. I'm working on Tosca, which is also an end-to-end solution for testing, and I see Tosca as a better option to use, except that Tosca is very costly compared to CA ARD. There are other tools as well, like RPA for process automation. CA ARD is lagging in competing with these tools. As an automation tool, it might not be the strongest.
For us, the process of implementing it starts with getting in touch with one of our internal teams and giving a business case for why we are going to use this tool and what the users' rights will be: for example, edit or delete or whatever functionalities we require. They will register us for the solution. Once this is completed, it will trigger an email so we can start using the tool. First, we create the backlog. I work on it from a business analyst perspective and I help the project management team to understand what all the backlogs are that we are maintaining for the upcoming versions. As a business analyst, I note the requirements for the respective backlogs, based on business priorities. Then we pull them into the particular sprints. It will then move to the development team to start looking at each of the user stories. They will divide these user stories into particular, technical tasks. From the testing team point of view, they create, under the same user story, their tasks and start giving their descriptions, including the defects. Once it is completed, we have a UAT done and we update the status of each of these user stories as completed, or in progress, whichever is applicable. Deployment depends on the complexity of the application. We have 25 to 30 people using it in the current project. In my previous organizations, the same tool was used by more than 125 to 130 people. There are different types of users. Business people are also involved, as well as technical testing people, project managers, etc. Different stakeholders are involved. We are implementing it in many projects now. It was not being used as much, in practice, in the organization where I am working, but we are now scaling it up to multiple teams, so that everyone will get the benefits. To scale up to different teams may take another year. There are different service lines in the organization and each of them has to adopt this technology. They are slowly picking it up.
I would advise to use this product, because it is a good way to create models and establish model-based process testing. The optimization technique with integrations is seamless, and a very good tool. It gives us an idea of creating the visual diagrams, which are quite easy to use. It is helpful in creating our business processes. The optimization technique helps in giving us the minimum number of test cases with maximum coverage.
If you are looking to implement model-based testing, reduce the effort required for documenting the requirements, test case creation, automation script generation, maintenance of test cases, and automation scripts, then go for it. It will bring great savings to your organisation.
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.