The setup of Broadcom Agile Requirements Designer is simple. You do not need a guide to do it.

The initial setup is straightforward. It usually takes two people to deploy. They work as administrators or on the development team. There will be one or two administrators on the client's side to maintain it.

It's easy to setup and get the license. Applying it to the different organizations that is the challenging part.

Initially, we struggled with the solution. We didn't just use ARD. We were using a lot of tools from Broadcom. Due to this, initially, there were hiccups in terms of how we would be deploying the tool into the on-premise environment, et cetera. Gradually there was very positive support from Broadcom and the Broadcom team as well. It all sorted out well. 

From the company level, we had to make sure that the tool process, all the architectural conformance checks, and integration of security were in place. Those sort of checks we normally do internally before deploying any new tools. All of this took time. That was not the fault of Broadcom. It was just the process side from our end that went long. 

The setup is not hard at all. It is very simple, like any other desktop-type software installation.

The initial setup is straightforward, and I would rate it at five out of five.

The initial setup was straightforward.

However, we are still not tapping into the full potential of the tool. We have only had the tool in-house for a year now, and we are getting ready to acquire or purchase more to make it a full scale rollout. I really think that the tool is getting ready to grow and to really expand its base at the company, so I am looking forward to growing with it.

For the standalone option it was easy, since we are familiar with modeling approaches, in general. For the repository option and connection to other tools, it required more work (as any integration would).

The initial setup was quite straightforward.

Everything but the licensing was straightforward. The licensing is extremely complex. It needs work. That's probably the biggest issue. I know they are redesigning the licensing model, but that was a royal pain, to be honest.

I was involved in the setup and there were some security issues which proved to be complications because we are running it with VMware and there are some difficulties with offline registration and license revalidation.

I was involved in the initial setup. What is good is there were some consulting services to make the complex a little more simple. We have some real talented guys on our team that were more instrumental in that rollout than I was. So, it was not that difficult. One of the more difficult things is just getting people to think in terms of drawing models instead of writing scripts. Changing that mindset was something that we had to do, but CA helped us through that as well.

The initial setup was straightforward. Installation was quick. Then, we needed to activate the license by following the instruction provided.

Technically, it was very simple. But the difficulty in starting to use it was more inside our company than a CA or a technical issue.

The initial setup depends on the kind of scenario you are working on. But I found it straightforward. I took about one-and-a-half weeks to study the tool and I'm fine working on it.

Deployment for our clients takes around 30 minutes. It's relatively quick. It generally takes one to two people for deployment. Once the system is up and running it takes two or three people to maintain it.

We have four to five people using the solution. We have an automation team of around 11 people. About half the team is using this tool.

It's a client install and we got it packaged very well within our company. So, I didn't have any problems at all with installing the client.

Moving the software between computers is challenging. We tend to get new PCs, or people leave our company and the migration to a new PC is not easy.

I was involved in the installation, which wasn’t so complex. Educating people is more of the problem. The education process is complex.