The initial setup for Sparx Systems Enterprise Architect was okay. I downloaded it from the internet, and I had to put a key in. The tool was really easy to set up. On a scale of one to five, the initial setup is a five for me, particularly once I got the key in. Deployment took twenty minutes once I got the key.

I would rate my experience with the initial setup a ten out of ten, with ten being very easy to set up. It is very easy. 

However, setting up a common repository requires additional steps, or you need to place it in a dedicated SQL server. For instance, using an SQL server would make it easier to integrate creating a database or analytics script directly into Enterprise Architect. 

Because no (as far as I remember), there's a need to run scripts to download them from your page and run them separately. It should be integrated into the wizard to create a remote repository. 

So basic installations are rather easy, in my opinion. However, more complicated setups for groups and people need some technical skills and experience.

It is simple to build the first model for the solution.

The initial setup is easy because you could use it in a single license on a desktop, or you can get the server license SaaS solution, which is equally as good, but it's a it's a very simple and easy product to adopt for embedding. I have used the Client Data Environment for deployment. The deployment takes a couple of week's time. Depending on who supports it and how the service operating model is, it's  easy to maintain the support.

The Sparx setup wasn't complex.

The initial setup was straightforward to run as a single user on a single machine. There might have been an issue around installing access to the image library on the cloud environment. I think it was just a patch version that I needed to get to fix the issue.

The initial setup is not really easy. Especially if you use the cloud server. You need to set up a licensed server, and, if you work on a relational database (which is recommended for large repositories and necessary if you want to collaborate on models), you need to have some DB knowledge (DBMS Based Repositories For Enterprise Architect | Sparx Systems)

I am asking my IT to install version 15 on my laptop. I have submitted a request, and I want to have it set up and then try it. I will play with this a little bit and figure it out.

Its initial setup was straightforward. In terms of the implementation strategy, our organization doesn't have a lot of architects. This is the beginning of doing this the proper way. There is not really a plan in place. We have just put the software in place, and I have started to collect information and put it into the tool.

I've installed it on a local machine. We could also install it on the server. It has fairly low complexity. It comes with the binary. You just install it.

The initial setup was very straightforward; very easy. It took a very short amount of time, and we were able to have things up and running in less than a day.

It is usually very simple and straightforward. The real work is setting the standard for collaborative work between teams and projects.

There was a learning curve to deployment constrained by needing to install as the user until we figured out how to deploy using MSI scripts, elevated privileges and a standard REGEDIT file containing a Sparx configuration.

I wasn't part of the initial implementation. I can't speak to how difficult or complex the setup actually was.

The initial setup for this product was slightly complicated. It was complicated for the business users, the non-IT teams, and the non-technical teams, but I was able to do the setup myself.

My understanding is that setup is easier than MagicDraw.

The initial setup is easy to do. However, with the implementation, people struggle with how multiple people can work in a collaborative structure. That doesn't come easily. You have to define many things. There is room for improvement because people do not understand the solution.

The solution is not fully deployed but individual people are using it. The beauty of enterprise modeling tools is to collaborate into a single workspace. A single workspace means a single model where everything is interrelated. People have traceability.

If you are using Sparx Systems Enterprise Architect as an individual contributor, then it's not a great choice. It's not implemented in the current organization effectively. If Sparx Systems Enterprise Architect can provide demonstrations or a checklist it would be very useful.

One of my colleagues did that. I am not familiar with the setup, but I know it is pretty elaborate because, like anything, you got to configure it the way you want. The more robust the tool, the more configuration it usually needs.

Installation was straightforward for all components and configurations.

I wasn't a part of the initial setup.  

The initial setup is okay.

The initial setup of the Sparx Systems Enterprise Architect It's very complicated. It's very difficult to start with the right templates because there are many possibilities. The deployment took approximately two days.

I would rate the ease of implementation of Sparx Systems Enterprise Architect one out of five.

The initial setup isn't easy, but it's not hard either — it's in between. 

If you are talking about Enterprise Architects, the initial setup is quite simple.

We want to keep all of the information inside our own infrastructure. We have our own data centers and for now, we would like for it not to go into cloud deployment.

The initial setup is straightforward. It is very easy to install.

It is easy to install. You just execute an MSF file, and it is implemented quickly. It took a maximum of three minutes.

The initial setup is straightforward and it's a simple implementation. 

The initial setup was very easy. After that, by following the best practices from the Sparx website, it is easy to organize the whole modeling process with versioning. You have the ability to reuse existing elements/projects and create customized project templates.

I always compare EA with a lovely beast. It seems very complex at the beginning, because it provides you with all options in all places, but once you realized that you don't have to use it all, and you know your workflow, it just works perfectly.

It's a very easy installation.

It is straightforward.

We found the initial setup to be very straightforward and simple. It's not complex at all. A company shouldn't have any trouble with the deployment process.

It was straightforward for single use, but for collaborative use it is slightly more complicated.

The first setup was 14 years ago, and therefore it has been a long time. However, it is very easy and not overly difficult. 

The maintenance involved is all about the database. We moved from an old database to a newer one. However, that's it. There is no maintenance, events, or tasks to schedule regularly.

Straightforward.

It was in fact straightforward, which was one of the determinants for selecting it.

The installation was very easy.

It starts just like everything but before people become productive they have to do several things. I performed the setup in a virtual environment and there was no problem with it. Sometimes, license key management is a pain, but I think that is the case with many products. Especially with these so-called "floating key management" systems. 

It's very easy and straight forward to setup, and so are the updates.

EA is extremely easy to set up and use once you know what you're doing. You really do need to have some kind of an overview from someone to get it started. They have good online tutorials, so you can get going. It is pretty easy to get going.

The setup was straightforward.

Very straightforward – download executable, select repository type, apply the license, and go to work.

It was straightforward. It involved connecting to the license server and deploying the solution. 

It was deployed within two weeks.

I didn't have any problem with the initial setup. It took over an hour to set up. It doesn't take long on the install. It's longer to configure it for the part of the project you want to use it for. It's got such a massive footprint as far as what you could use it for in a project, but if you're a one or two-man shop, you're just going reach and get it. It's got to be done real quick and it's difficult to do that because it's such a massive tool.

I didn't have any problem with the original setup at all. I wouldn't say it is complex. It's pretty straightforward.

Deployment takes probably over an hour due to the fact that, once you get it installed, it takes a while to configure it for the part of the project you want to use it for. It's got such a massive footprint as far as what you could use it for in a project, that if you're a one or two-man shop, it takes a while. With such a massive tool, there's just a lot of man-hours to get everything as you need it.

We don't really have the bandwidth to have a specific person to maintain the solution; we do that ourselves.

Very straightforward.

No - install, run and if you want a repository run a db script.

YOu need to know how to run a database script.

The initial setup is simple. There are some advanced options related to source control and WAN optimization/cloud service (HTTP connectivity; not Sparx in the cloud).

However, the most complex consideration when setting Sparx up is how to structure the model to address your business requirements. This is key because the tool has no out-of-the-box model structure. You need to define it.

It was straightforward.

It was straightforward. It was very easy to setup a new repository from scratch. The tool offers sufficient flexibility to alter the structure.

Very straight forward.

The initial setup was not complex. It was a pretty straightforward task. 

The deployment was quick and we had it up and running in 50 minutes or so.

Initial setup was not complex. As mentioned, people installing the database server version (the only one that makes sense for us) can have some difficulties.

The setup was quite easy. The installation instructions and database setup is straight forward.

It was easy for me. The EA Example project was very useful. However, when I encountered a specific question it was difficult to find the right answer on the Sparx website.

It was straightforward.

I did not take part of the deployment but I am also not aware of any significant challenges

Straightforward - Caveat: I did not take part of the deployment but I am also not aware of any significant challenges

Very easy.

It was straightforward.

It's very easy to set-up. A shared repository with floating licences takes more effort but is not complex.

It was straightforward as support had been requested for installation, and users had been registered for a short term classes.

It's very easy.

The setup topology was - central repository, shared keys, version control system, domain controlled users.

I found the setup to be simple, but it may be because I am used to the environment. It was implemented as a turn-key project over approximately six months, with the total project being about a year in length.

The initial installation is complex. However, there are some very good tutorials online that we have been using.

Easy, because it was local. Network setup more difficult and costly.

The setup was straightforward.

The initial setup of Sparx Systems Enterprise Architect for the inexperienced user is non-intuitive.

Complex, because we used a profile.

It's straightforward, but too much configuration is required with SVN or local code.

It was straightforward.

Easy.