Sparx Systems Enterprise Architect Reviews

Architecture Design (component, deployment), Reference Architecture (enterprise, technology) and Solution Management (external artifacts) accessible globally to all of IT via AWS cloud.

Improved cross-functional team collaboration. Dynamic visual activity models improved communication and understanding with the business. Shared repository enabled reuse of model elements by users. Established a well-defined structure to manage whole solutions. Ability to ingest external document artifacts became a viable alternative to SharePoint. UML based modeling enable model-first approach in lieu of document-first approach to solutioning (alternative to Microsoft Office - Word, Excel, Visio, Powerpoint) 

Version 14 menu organization is much better. Ability to ingest external artifacts with added metadata coupled with UML based modeling is moving the organization to a more digital way of working while preserving legacy artifacts.

A better deployment model for the enterprise without relying on HKEY_CURRENT_USER in the registry.

Very stable. Rarely a crash.

In general, performance and scalability is solid. There are times when communication to the shared repository in AWS would be inconsistent, but I think that was due to the corporate network connection

Customer service / technical support is via email only so is constrained to 24 hour turnaround. Otherwise good responses. 

The Solution Architect team used a combination of Visio (UML), Word (Document Templates), Excel (Requirements) and SharePoint (Repository). Sparx replaced all of this while retaining all of the prior tool features and enabled cross-functional team collaboration for solutioning.

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.

Implementation using in-house team.

We gained 10 - 20 percent improvement to productivity (measured by time to complete solution) and improved quality (measured by reviews)

Setup a shared RDBMS repository (SQL, Oracle, etc.), acquire shared license keys and deploy using MSI scripts.

Considered Visio Professional (has a repository), ArchiMate (too high-level), Rational (too costly)

Establish best practices for solutioning including standardized stereotypes. Drive adoption using a hybrid approach of modeling and ingesting external documents since not everyone will learn to model equally using UML.

I have used the solution to manage software architecture.

The solution offers different types of models and features apart from diagrams. It also supports giant patterns for software systems with a high level of extraction independent from implementation networks. 

The solution's interface is very complex. Its usability could be easy. Also, its layout could be improved regarding quality control and making recommendations.

It is a stable solution.

Around five executives used the solution actively in my previous company. It is scalable for larger projects.

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

The solution is quite expensive.

I advise others to understand the project requirements while making purchase decisions. If you have an extensive and complex software development project, go for Sparx Systems. But, if it's a small project, look for other tools.

I rate the solution an eight out of ten.

The solution is used for Modeling enterprise architecture artifacts, and also for project delivery artifacts as well. So solution architectures, designs. Sometimes I've used it for requirement gathering for functional and non- functional.

Working with the solution being right around keeping an asset repository that various projects and programs can utilize. So it's about reusability of assets and making sure that a baseline can be achieved against which a target can be models. So it allows the baseline to be models and maintained well.

Sparx has got a range of modeling features, and I am comfortable with all its offering. I've used a lot of tools over the phone. I found EA Spark, probably the most feature rich product all in all compared to other products. The solution is very cost-effective and that is its best feature. It's a very good delivery architecture tool, which also has enterprise architecture capabilities, and it's got full life cycle processes and software development. So for me, it's a pretty comprehensive tool

The Portfolio Management features can be added in the next release. As it helps you to manage more portfolio of projects and architectures of cost projects on a portfolio level. This would be an important feature in the next release.

I have been using the solution for fifteen years. 

It is a stable solution.

It is a scalable solution. I have used it for large organisations.

The technical support team is good. 

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.

Enterprise licensing is competitive. What would be helpful if they load the pricing for consultants, you know, people who are consultants for clients. So the license is fine for end-user organizations. Still, they should consider lowering the license to support this adoption, particularly for people who are consultants like myself.

The solution is a very intuitive product for me. It has a lot of capabilities and covers enterprise and solutions architecture. It also has a lot of ability to integrate with third-party products, which is good, and they focus it on being a modelling tool, which is very helpful. It has a very adaptable and usable tool tool tool within enterprises.

I would advice people to use the trial versions and assess its functionality, and then from that, decide on the suitable adoption model and embedding model in the organisation depending on the requirements.

I rate the overall solution an eight out of ten

We use Sparx to design the whole enterprise architecture, from the highest level down to the physical level, and to generate those XML messages. Also, we generate the DDL for the database to support DevOps. 

In the beginning, I didn't have any training. I just wanted to try, but I spent two hours and I couldn't do anything. I clicked here, then clicked there—it didn't work. Eventually, I learned how to use it, but in the beginning, it wasn't very straightforward. Usually, because of my computer experience, I can do things by intuition. So if you do not get training, read the user manual, or Google how to use it, then it's hard to do anything. With some other tools, you can immediately do something, but I had to take some time with this one.

I like Sparx's BPM features and the way it lets you create the diagram.

I check the Gartner report pretty regularly and I see that Sparx keeps on going down in the rating. The Sparx EA needs to catch up. I believe the one reason is the strategic architecture. Also, other tools might work better for those high-level executives for whom the quality of the diagram is very important. Sometimes these little differences set a product apart. 

Almost about 10 years, I think. Yeah.

Sparx is very reliable. And it's integrated with ServiceNow via the cloud, so you can share info and store everything inside the Sparx EA. 

When many users are accessing the system at the same time, Sparx slows down. It can't easily support a large team. I'm a contractor and for my latest contract, there are 30 architects and 20 business analysts.

Sparx support isn't very responsive. 

The Sparx setup wasn't complex.

The license I use is on-premise. We haven't gone to the cloud where we have to pay monthly or something like that. Sparx is cheaper than most similar tools. 

I rate Sparx Systems Enterprise Architect nine out of 10. I recommend it, and I also go to other organizations and train their employees how to use it.

Sparx Systems Enterprise Architect is used by our architects to put out artifacts, collaborate, work together, and share those artifacts. The product is used to maintain the versions of architectural diagrams, use case diagrams, etc.

I'd like Sparx Systems Enterprise Architect to be more stable, and have a more improved performance. It should also have a sharing feature and allow us to easily share artifacts with our business partners, rather than requiring them to install the product on their site first. If people who don't have licenses could also view what we're sharing, that would be great.

I've used Sparx Systems Enterprise Architect for the past 10 years.

This product should be more stable.

The cloud version of Sparx Systems Enterprise Architect is scalable, without a doubt.

I'm satisfied with the technical support for Sparx Systems Enterprise Architect.

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.

We pay for the license of Sparx Systems Enterprise Architect, and it is a yearly subscription.

I evaluated Visio. I use it in parallel with Sparx Systems Enterprise Architect.

I used Sparx Systems Enterprise Architect on-premises at the start, then later on for other clients, I used it on cloud. I used the latest version on cloud, but for the on-premises deployment, I used an earlier version, but I don't remember the version number.

There is a learning curve with Sparx Systems Enterprise Architect, e.g. to be comfortable and to start using it full-fledged. It took me a month of practice.

On average, we have 50 users of this product, and 20 technical people in charge of its deployment.

I can recommend Sparx Systems Enterprise Architect to other people who may want to start implementing it.

My rating for Sparx Systems Enterprise Architect is eight out of ten.

My company is a leading software team. I tend to get brought in early stages for understanding and identifying problems. I look through what the customers are actually doing and I tend to move on into the system's analysis and architecture to see whether there are opportunities for interventions and gaps.

The features I find most valuable is the ability to create a document and then put it into a OneCare artifact. This feature allows me to share the visual I bring about with other communities that are not system analysts because not everyone can afford to have a copy of Enterprise Architect. 

Additionally, the solution operates well as a whole and has very comprehensive capabilities.

The areas of improvement should be focused on utility service such as producing better graphics, perhaps having a wider image library set and producing better models for working directly with customers. The solution does not provide things like shadow effect and 3D computer graphics instead of 2D.

More polishing on the presentation should be included in the next release. 

I have been using this on a regular basis for the last four years. For the additional six years, I have used the solution in intervals as I needed.

Initially, I found the stability of this solution reliable until there was an unexpected access crash leaving an LDB that prevented me from accessing my database, even after deleting the LDB file.  I had to use the previous version to solve the problem which I had to work on for two days.

I find the solution very configurable. I could go in and change the format for export. I brought products into the ArchiMate from EA and the other way around. They seemed to work because they store them as common components.

The support team have been very good at responding and coming back quickly with a query.

I previously used to work on Salamander but it did not add on what I already know. I was also recently teaching Visual Paradigm and ArchiMate.

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 licence has a costly upfront fee which gets you access. You have to pay an annual maintenance fee, which is less.

I think the pricing is justified because I use it very often. 

I would certainly recommend this solution if you are a serious business or a system architect, who are modelling complex systems. You will already be aware of the product and you will know what it could do for you.

I rate Sparx Systems Enterprise Architect an eight out of ten. 

We're still investigating it on the structural side. Our primary focus is on CCML and UML, the creation of documents, and requirement management. After that, we will teach our company about how we're going to use the product. I am using its latest version. It is deployed on-premises on the company cloud.

It is a very flexible product. It can do a lot. It is also a reliable product. 

I would like it to be less of a general tool. Currently, it is not a Swiss army knife that can do everything. It is not specialized for our purposes. We are a civil engineering company. We build things. We work mostly in what is known as Infra world in the Netherlands, which comprises objects such as bridges, locks, and water management. We would like to see more focus on such types of projects. It would be nice if it has more specializations. At the moment, it is very generic, and you have to create everything yourself. 

Our focus is more on user requirement management, which is currently very basic. I would like to see a lot more functionality in this area. Its basic functions for adding user requirements are perfect, but we need more features. Currently, it has limited possibilities for our requirements. I would also like to see better contract management and have it managed in a certain way. 

I have been using this solution for a year.

It is very stable. I've had no problems or issues.

I'm using a database-based client of Enterprise Architect, and it is very scalable. 

We are testing it at the moment. I am working with four or five people in that area. After we have enough confidence in the product and we have a new project, we would most likely roll it out to a hundred plus people. There are two projects that are currently using Enterprise Architect within the company. One of them already has more than 100 users. The company I work for has 30,000 employees. It will be used by quite a lot of people.

In the Netherlands, the support for this solution is very limited. You have to rely on some consultants, but at the moment, the knowledge of these consultants is also quite limited. They quote a quite high price for their knowledge, but the impression that we get is that they're learning on the job. They call themselves specialists, but they're not really specialists. When I look at other countries, particularly the United States, the consultants are a lot more knowledgeable, and they know more about the product. We don't have that in the Netherlands.

I have tried different packages. VCL is a very well-known package, which can also generate code to a certain extent and create documents, but it is limited. I have used a number of open-source tools, such as Star UML. There are a lot of different packages that are good in a certain area, but you can't combine things very easily. They require a lot of work and a lot of people to collect the information by using Excel tables or databases.

We are also looking at another tool that is very much focused on CCML, which makes it limited. It is certainly not as flexible as Enterprise Architect. We also have to look at the knowledge of the engineers working on the project, and most of them are not software engineers. They have a background in civil engineering. Enterprise Architect is certainly a product with potential, and we would like to introduce it, but it is very difficult to implement it in our project. Most likely, a few users will use Enterprise Architect. The remaining users would continue to use Word or Office products to create their documents, and a few will add the required information to the model.

Overall, I would rate Sparx Systems Enterprise Architect an eight out of ten. If I was rating it specifically for our business, I would rate it a five out of ten. It is very difficult to use it in our company. It is a good product, but it is difficult to implement in a non-software company.

My job is about helping the organization to create a functional solution. I build models for the organization at the business layer, application layer, etc. It also involves integration with other tools, such as erwin, for data modeling.

Its traversability is most valuable. I can use ArchiMate, and I can create a UML model. ArchiMate is for logical enterprise architecture, UML is for software engineering, and BPMN is for business processes. I can build it to have multiple models, and they are also traversable, which is not something that every tool allows. If there is a huge organization, you can segment it and have separate models for business technology or internal resource management system. You don't need to keep them in one model, and you can decide to segregate them.

Its model-centric approach makes it very easy to create documentation based on a template. Every company says that maintaining documentation is a very tedious task, and it usually requires subject matter experts. That's why companies rarely maintain documentation, but when you maintain the model, and you have the right processes and the right roles assigned, it can be naturally maintained. You can just simply produce a document by selecting whatever you need and in a format that you need. It is a very powerful feature.

From a practical point of view, we need speed and reliability for creating a model and doing some really meaningful tasks such as application landscape, refactoring, etc. These are two primary criteria. Sometimes, when you import something, it creates the object duplicates, or it allows you to do something that you're not supposed to do. For example, validation is missing. This could be frustrating because when you work at a high speed, you need to come back and start fixing things that the tool allowed you to go with, which is not quite good. So, there should probably be some internal mechanisms to advise you about what you're doing and what is probably not the best idea.

For example, you can do many things with ArchiMate, which is modeling language, but people can interpret many things incorrectly. They start modeling and then realize that it is not a good idea. So, it is not the tool itself. It is probably a combination of the modeling language and the tool that validates it. It would be very good if validation mechanics are embedded in the tool to, at least, advise people that a particular thing is allowed to be done in this way, but doing it would also mean something else that you may not want. The languages themselves are not perfect. In a large company, you have many people doing the modeling. If they interpret things differently and the tool allows them to do that, then you would have to do some rework.

I have been in and out. I have probably been using this solution for seven or eight years.

When I use it, it is stable. I do not have any problems. I really love the tool, and I have friends who work with this. They simply admire it. So, it is very popular in this area.

I didn't use their tech support much.

I tried to build a design with another solution two or three years ago, but there was something wrong and it was very slow. It was called Business Design. So, basically, I just said that I cannot use it for the scale of the task that I have. I simply cannot use that tool. They could maybe tune it up. I'm not blaming the tool itself, but my experience with it was really negative. I expect that the Sparx program will be faster.

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.

I use my own license. So, I just bought the professional version, which costs $800 or something like that. 

In the company where I am working, we have floating licenses. They are probably more expensive. Its licensing is affordable, but we are talking about a large organization, and there could be modelers or viewers of the models. We don't know how much that would cost us.

Currently, I am using a different tool, which is open-source, because the company didn't want to pay. It looks like they have changed their mind, and I have now started looking into the tool. I will also be looking at other cloud-based tools, including Sparx. We haven't yet made a decision. We will compare all the options, and Sparx has very good chances. We are quite positive about it, but there is also competition.

My task right now is to create a model for the entire organization with thousands of NMLs and tens of thousands of relationships. It is very big, so the speed of the process in it is very important. My superiors are thinking about a cloud version because they don't really want to maintain it. They're talking about something like DevOps so that in the development, they have the continuous promotion of the code, automated testing, etc. We are not building the executable code. If you look into a modeling language, it is a language. It is not a programming language, but it comes under the same category as the programming language. For many people, it is much easier to understand than Enterprise Architect. They try to stay away because of the complexity.

I would rate Sparx Systems Enterprise Architect an eight out of 10. My experience is a little bit outdated, but I was very pleased with it.