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 the case of a big epic, we are able to create it. Then, based on backlog creation, we will be able to create the user stories under that particular feature.

Also, defects can be traced in the solution.

The most valuable features of this solution are the ease for creating test cases and the automation of the test cases from the user workflows.

It will enhance and make the automation part for the testers a lot easier.

We are satisfied with the solution. 

I can't speak to a particular feature, however, in terms of the way the UI and the response of the tool are set up, including the hierarchy breakdown of the requirements and how they appear on the tool is great. I like how we could navigate from one breakdown to another. It makes the solution very user-friendly which is the main USP of the tool.

With the way we are using the Broadcom ARD tool, the solution provides us with everything we need. 

The support that we get from Broadcom is great. 

The product scales well.

We have found the solution to be stable. 

• Model building: Creating business process flows
• Test case generation: Manual or automated
• Automation script creation and management

Test data management is coming at the end of March. That will be one of the biggest new leaps for us. We are very excited about adding TDM to the suite.

The new release CA Agile Requirements Designer 2.4 offers more flexibility when exploiting the APIs of test and defect management tools. CA has addressed this concern with release 2.4.

I like the way Broadcom ARD inserts test cases in execution mode. Also, ARD can be used apart from Broadcom TDM. It's an add-on through which you supply data through ARD test cases when there is a need for extra data.

1. Now, we get automated test cases, where before we did not. It cuts out the construction time of testing, about 75%, is what we found. 
2. It is a store that we keep all of our requirements in where, before projects would come in and we would not have a place where we keep the past requirements so there was always a fight between development, testing, and the business writers because they can't remember how functionality works. Now, there is a black and white copy of how the processes are flowing through the system, so there is not a fight anymore about what is happening and what is not happening.

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 above features also help to avoid redundancy and use appropriate level models for different levels/phases of testing and/or communicating to different audiences.

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. 

Measuring test coverage helps in one of the most challenging tasks. It has logic that can help to select the right set of scenarios and know what coverage it will provide.

Handling loops in models was one of the challenges that we came across in our previous tool. ARD seems to have better control and logic over handling loops in models.

I like the optimization, because it gives me an idea of the minimum number of test cases. It also gives me an idea of coverage.

The integrations with other tools is very important for our continuous testing process.

The most valuable feature for us is the automatic creation of the test cases, based on the models. And the impact analyzer that shows you where your change is impacting your test cases, and the ability to export that to our TFS Instance.

It removes ambiguity in requirements, meaning that there are fewer demands for clarifications afterwards. We are using it to improve communication between business, tests and development.

For testing, it gives a very good view of the test cases and shows priorities of action so that the most important things are tested first. This helps us to save time as well.

1. The co-monitorial modeling. It lets us reduce the amount of scripts that we need to execute to get complete coverage. That is really important to us. 
2. Traceability from requirements through test cases.

One of the best features is that you can actually develop some of the business designs in the application and transfer that into scenarios if you don't go out of the detail level. And you can see the coverage. You can get your test cases automatically done for you.

There are tons of really valuable features. First of all, it's a model-based testing tool and the market of model-based testing is pretty narrow, and there are few offerings. I did extensive research in this area and at the moment CA Agile Requirements Designer is probably one of the best tools in the market. It allows you to utilize the full power of model-based testing using a simple method to build a workflow, which is more familiar to most software and test engineers than to business analysts or product managers.

It has a native engine that allows you to configure test coverage for your application model, and you can analyze this coverage by applying different optimizations. This really helps to make informed decisions when you're choosing the right amount of testing you need to apply. How not to over-test your application from one point of view, and from other point of view, how to guarantee 100% functional coverage in your testing. This is really crucial. Another great feature is that it can be integrated with test automation tools. This tool is agnostic can be integrated with a number of different products.

Another useful feature is the ability to integrate with a test data manager. For example, in my array, I don't have large databases from which I can get enough data for my testing. But other companies do have large data sets and they can integrate their testing tools with the databases to do sub-setting and masking. CA can also build synthetic data for testing. These are very powerful features that you can't find in other products. In this way, CA is in a unique position, because they offer these unique products with unique feature sets.

• Business flow creation
• Test case optimization and generation
• Risk-based testing
• Automation test script creation
• Test Data Manager integration

The product reduces the efforts required in documenting requirements, test case creation, and automation script generation. Test Case Review was quick and easy, by visually going over the flow. We were able to standardize the automation scripts.

Modeling how the application works, and then getting every use case we can test. Designing the right tests, what are the most critical tests we must do.

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. That is something we can actually do from CA ARD.

The modeling, without question. The modeling is a game-changer.

The ability to provide developers information on how to design the request.

This tool improves our speed and automates our processes.