We are using Broadcom Agile Requirements Designer for DevOps. For example,  you might draw the diagram within Broadcom Agile Requirements Designer and it will turn these requirements into test cases automatically before you build the code. It all can be done with ease.

I work in the insurance and tax domains. The purpose of my using the tool is for user story creation and to have a traceability matrix for our development team and testing team.

We have a lot of quality assurance projects which are running. We normally validate the requirements and make sure the requirement scoping or the requirement validations are being done properly. We put the requirement breakdown and requirement scoping into Agile Requirements Designer (ARD). We plan our test cases so that the business user community can actually log into the ARD tool for their project and validate their requirements to see if they have passed the set of quality controls or not.

We use CA ARD to accelerate our testing. Currently, we write manual test scripts, and if you bring new people onboard, they have a learning curve because they do not know the products as well as experienced people. So, one of the primary things that we use the ARD for is to erase that SME knowledge versus newbie mentality. Once you put the requirements into the model diagram, the tool does all the test cases for you. It takes away all the time to construct test cases, so it is all automatic now, but it also levels the playing field. 

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.

We are trying to create models, then get the maximum number of test coverage by getting the minimum number of tests. That is what we are looking for: Getting the minimum amount of test cases which provide the maximum coverage. We want to test the minimum amount of cases. 

As of now, we do not have a tool which can tell us this. We might end up overtesting, but we have no way of knowing. For this purpose, we use other tools as well, to show how well it integrates and contributes to the continuous testing process.

We use it primarily to model our applications to automatically generate test cases.

It's great. It's preformed very well. It's very useful.

Primarily, we use it to convert our test process to model-based. It has actually changed our entire process from script-based to model-based.

We use CA Agile Requirements Designer for model-based testing, and also automate test case creation and generate test automation scripts.

Because we have a lot of applications, we test ARD on three use cases at the same time. I don't remember exactly, it was a Java-oriented application for our agency in Africa.

The added value is testing design. Also, it's very useful when you're working with the Agile methodology. It's a great tool within the CA catalog. 

Our primary use case for this tool is designing our manual test cases.

CA ARD is a shift-left tool for us, toward BA, business analysts, where we actually create our requirements. We use it for creating our test cases and QC. Once we get the requirements from a client, we design our flowcharts in CA ARD and then it automatically creates our test cases and QC, because there's an integration in between CA ARD and QC.