Sparx Systems Enterprise Architect Reviews

• Easy drag and drop
• Reuse the old copy
• Quick changes with minimal efforts
• Anyone can work on the same file
• File is small in size.

Large diagrams for hardware infrastructure, HA environments, Integrated Solution view, etc all help different teams to understand the scope of projects.

Should be on the cloud so that its flexible for making changes and managing different versions. Anyone from a team can work on a copy with project shared user for quick delivery, but there are license limitations that should be based on the number of running threads and not on a per-user basis.

We've used it for the last 10 years.

Installation will be challenge for quick and one time use, some time the code not sync due to some issues,

There have been no issues with the stability.

We have had no issues with scaling it for our needs.

I haven't had to contact technical support.

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

Westraightforward, but too much configuration is required with SVN or local code.

If the project life cycle is delivered through some standard ICONIC process E2E then Sparx will help a lot for artifacts.

The business process management of Sparx is valuable.

We've improved overall to some extent due to Sparx.

UML analysis needs to improved.

We've been using it for three years.

There's a lack of diagrams available during deployment.

We had no issues with the stability.

We have been able to scale it to our needs.

We haven't had to contact tech support.

We previously used MAP.

It was straightforward.

We used a vendor team.

Development for simplifications, host tutorial and case studies.

Solution architecture and design, however the database management area really was not usable. I could not even send in a DDL to reverse engineer it. Also, adding referential integrity to existing fields from a reverse engineered database resulted in duplication of keys. 

Not really.

Unfortunately, only one of our solution architects was using this in the end, as the others resorted to Vision because it was more user-friendly. I ended up buying an Idera licence for ER/Studio and using that instead.

I struggled with most of the features for this tool, as did the rest of our architecture team.

The database part needs to be more like ERwin or ER/Studio. 

It really did not work for logical modeling. The look is very old-fashioned. You can't make the diagrams easy on the eye, so we ended up drawing them again in Visio anyhow.