Sparx Systems Enterprise Architect Reviews

Our customers are using Sparx Systems Enterprise Architect for enterprise architecture modeling, where interrelationship among different enterprise entities.

Sparx Systems Enterprise Architect is very flexible and it is simple to define the metamodel. Additionally, it is lightweight on resources.

The solution could improve by having more aggressive working sessions with other product vendors. It would be a benefit to have demo sessions where users of the solution can ask questions to product experts and receive answers. For example, people who are struggling with the initial setup.

The team setup is very crucial for the success of a tool like this. I don't know if we looked into it properly. However, if some part of it, such as user setup can be automated, then it would be great for adoption.

In a future release, they should improve portfolio planning.

I have been using Sparx Systems Enterprise Architect for approximately eight years.

The solution is stable.

The scalability is fairly good. However, I do not have, for example, 100 users to be able to fully determine the scalability.

In my organization, we have the chief, enterprise, architect, infrastructure, and security architect that are supposed to use the solution. However, only one or two people are using it at this time.

We are pushing for evolving tools but I am not sure if we are going to increase the usage.

I have never used technical support.

We were using other solutions and we switched to Sparx Systems Enterprise Architect because it is lightweight, simple to use, and inexpensive.

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.

We do not have a separate team that manages the solution. We all manage the solution.

Sparx Systems Enterprise Architect is priced well. The price we pay is approximately $20 per month. Other solutions I have found to be much more expensive.

We evaluated other solutions before choosing Sparx Systems Enterprise Architect. Most of the other solutions had very big footprints and were very heavy tools. Our use cases were mostly related to EA modeling. For that, this tool was good.

The customer that is using this solution has not implemented it in the right way, but they are expected to. It's not fully utilized. If you start putting the model together, it's definitely a great thing to improve the overall ecosystem. If you put tools, such as Sparx Systems Enterprise Architect everything is always up to date.

If we will have this fully implemented, our productivity will increase. Since I work as an architect, most of the time we spend understanding as-is state and current state. If somebody is utilizing this solution, you don't need to spend a lot of time. You will always have an up-to-date depiction of the current state.

I rate Sparx Systems Enterprise Architect a seven out of ten.

There are other use cases that cover enterprise architecture, which is not part of the tools. This tool does what it is built for, which is modeling the enterprise architecture. I gave the seven ratings based on the overall ecosystem which is required.

We put the solution on all of our systems. We've got about 200 systems on it, however, it's not all documented yet. We have about a third of all of our systems covered. There are likely 5,000 users that need to be covered.

The pricing of the solution is pretty good. It's reasonable. 

Overall, It works pretty well.

It's easy to create all diagrams.

It's easy to search within the solution. 

It's very good software. 

There was some sort of glitch within the last version. Everything is in French and I tried to use English. It didn't work so well.

The window froze for five or ten seconds. You can click and click again and it takes a second to come up. It might have been specific to a version. 

I've used the solution for about two years at this point. It's been a while. 

We have a team of about 20 that work with this product.

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

The solution is reasonably priced and not overly expensive.

I haven't had a chance to compare this solution to other products. For us, it works pretty well and we haven't had to look elsewhere for similar solutions. 

I'm a functional architect.

I'm not sure whether or not our company has a business relationship with Sparx or if we are just customers. 

We don't use the product for generic cogeneration. We don't use it yet for that, however, in the future, we might.

I'd rate the solution at an eight out of ten. We're mostly satisfied with the capabilities of the product.

Our primary use case is as a UML tool, a diagramming tool that also enables you to build an inventory of different objects and different entities. We are a customer of Sparx and I am an enterprise architect.

The most valuable feature is the ability to keep an inventory of reusable blocks, and use them in different diagrams with views of various templates that are also available. It also has the ability to work as an add-on with Zachman Framework and a variety of other frameworks adapted to this product. It's a good UML tool. 

I think the solution could be improved visually. It's not as visually appealing as other solutions. There is a difference between being focused on a technical audience or a business audience. A business audience requires a greater effort and good visuals. Integrations with SharePoint, for example, could be beneficial. If you are using on-premise installation, the sharing of your artifacts with people that don't have a license, can be somewhat complicated.

I've been using this solution for eight years. 

This is a stable solution. 

This solution is scalable.

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

Although we use an on-prem version, they've now moved over to cloud so the sharing is much easier and has improved the solution overall. 

I would rate this solution a nine out of 10. 

Automated document generation is a real time saver , no more cut and paste, no more keeping track of which diagrams are in which reports, no more last minute update panics. Just click a mouse and you've got an up to date report.

Customized profiles allow you to create entities that are custom engineered to your organization. Do you want to separate non-functional requirements into two types, say high and low priority, with each one having custom tags such as owner, why needed, history, date needed and authorizer for the high priority you can have it all built in to a tool set.

In one organization, it allowed teams and team members all over the world to collaborate and sync up on specific detailed parts of the solution or model easily with a minimum of fuss by sharing the repository instead of having to e-mail diagrams or search through SharePoint to find the right diagram. Its easy to bookmark a diagram in a repo so someone else can open their EA client and quickly find and even modify it directly, if appropriate

Sparx EA has always had one strong negative that has kept it from dominating the market ( not counting the fact that the big guns can out market Sparx).

Its best features are not intuitive or easy to learn. Most companies I have worked with, when I see what they are doing with it , are not using more than 5% of what they could and should be doing with it.

I've even seen reviews of the product by people who worked with it in which they complain that it can't do things that it most definitely can do(e.g. I've seen it referred to as an exclusively single user tool).

Yes there are courses available but it's counter productive to teach everyone everything, don't confuse a business analysts by teaching him about class diagrams and document templates, don't teach a programmer how to create BPMN diagrams.

The webinars and videos help , there has been big improvement in the reference material that Sparx has made available.

Six years

No

Very very rarely.

No.

Very good.

Very good although there is no phone support.

I actually used a tool called TCC, Together Control Centre many years back which was very similar. It was created by Peter Coad of the (Coad-Yourdon methodology).

Unfortunately, some ruthless venture capitalist got control of the companies and tore it to pieces trying to make it a do all be all tool ("It's a floor wax - its a dessert topping").

Straightforward.

In-house ( mostly myself)

Always hard to say because it depends how you measure it but 20% or more is quite feasible.

Use floating licenses strategically.

Power Designer, Corso, Rational,BIZZDesign

Take the time to learn the features well - it will pay off.

I have been using it for six years and I am still learning new ways to leverage its features - not because of new versions but because of gaining an even greater understanding of the tool and how it works.

The number one recommendation I have about using this tool is to invest some time to understand how to use it properly.

Most people will use MSWord or Excel by just diving right in and using it and learning as they go, tinkering here and there and that approach works fine.

Do not use this approach with Sparx EA, you will end up using it as a fancy version of Visio which is like buying a Porsche to use for storage space.

Also focus your learning on what you will be doing with the tool ( i.e. if you will be creating requirements models don't waste time learning how to auto generate documents).

We're doing enterprise architecture work primarily. In one case we're looking at enterprise data modeling. In another case is mostly business architecture.

We haven't used the solution long enough to make any observations in terms of the product improving our company's functions. It's too soon to tell.

For us, the solution is evolving still.

I find it performs as well as other solutions that I've used, like QualiWare's Rational System Architect. It performs quite well.

For the most part, we find that it is remarkable how inexpensive it is.

Overall, the solution offers very good packages.

The initial setup is easy.

The presentation graphics need to be improved in future builds. It's primarily an architecture tool. Therefore, it's using certain formulas, and they aren't really very useful in terms of presentation graphics for executives. It's an ongoing issue. You do some kind of diagram, you then have to convert it into a Microsoft PowerPoint in order to get a certain look and feel. Otherwise, the design is just too obscure for executives to understand.

The product needs better tools for defining report templates. Sparx will generate automated reports based on whatever you select from the repository. It has this templating tool that's very flexible, however, I can't get the damn thing to work properly. It's just not very user-friendly. It's almost like a programming language. That's the thing that we keep coming back to tech support with to say, "What are we doing wrong?" If they offered a better report generating front end that will let someone quickly and easily configure what they want in their reports, that would be very useful.

I'm pretty new to the solution. I've used the solution for a little under a year at this point. It's likely been ten or 11 months so far.

While the solution has crashed a few times in the past year, I wouldn't describe it as unstable. There aren't really bugs or glitches on it. Mostly, it's fine.

I can't speak to the level of scalability of the product. The user community for our purposes is quite small. We haven't tested scaling it with larger user groups. However, it's not the type of tool you would role out to a larger community anyway. Therefore, from a performance scalability perspective, it's hard for me to comment.

That said, from a functional scalability perspective, it's packed with all kinds of features. Your enterprise architecture approach could certainly scale up to accommodate more and more of the types of analysis you'd want to perform.

We have two teams that use the solution. In one case, there are three people using it, and in another case there are seven.

We've used technical support in the past.

We've needed them for a few little obscure things and things just that are quite annoying to figure out. They've always been there and they're quite good.

We're quite satisfied with the level of assistance we receive. I would rate them at a perfect ten out of ten.

Personally, I've used a lot of different solutions, and a lot of different kinds of case tools. However, in both my client environments that we are presently using, we presently implemented Sparx and they had nothing like this before. This is really an eye-opener to them and a new kind of field for them to go into.

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.

The pricing is excellent. It's very inexpensive.

We're just a customer and an end-user.

We're using the latest version of the solution.

We use different deployment models, including cloud and on-premises.

It's an excellent entry-level tool. I say entry level as case tools are typically a very expensive proposition to bring into a business, and not necessarily because of their licensing costs or their implementation costs. It is more the training costs of the individuals to start working and thinking in an architectural way and then using tools like this in a consistent and productive manner. You need a methodology investment and you need training investment, and then you need a setup investment for the actual enterprise architecture program or practice that you're going to work with.

The tool itself is comparable to a bunch of others. However, it's not as expensive as most. It's in fact so cheap that last year, due to delays related to the COVID lockdown, I ended up buying a license for myself. It's that inexpensive. It cost less than Microsoft Word. It's an excellent way for a company to start or an organization to start using an enterprise architecture discipline. However, it's not an end-to-end solution. It could be an end-to-end solution. It just involves training of resources and change management for different processes and for governance and all this. A lot of companies just either don't realize that at all or aren't prepared to make the investment outside of the cheap license.

I would rate the solution eight out of ten.

It offers a comprehensive toolkit that it provides very good capabilities. The kinds of coverage that it gives to enterprise architecture tasks are great. The diagrammatic flexibility that it has, the methodological flexibility, and diagrammatic flexibility are also very helpful. It can support lots of different metamodels that will allow you to implement different enterprise architecture methods. It'll diagram them all. It does a very good job of allowing you to structure your environment so that you can support lots of different kinds of analysis across domains of enterprise architecture. It's very flexible in that sense. For these reasons, I give it fairly high marks.

I was using this solution to document a Business Architecture, and including BPMN 2.0 Process Models that were then used to create Process Design documents. We were running V13.0 in an internal network with the then third-party product, and Prolaborate. The implementation of Prolaborate was in a test environment and this became an increasingly frustrating problem.

We were able to produce a range of Process-based reports that were published to Confluence reports, as well as our Business and Processes Architectures, for use by a large internal program. The Business end-users and external vendors seemed happy with the outcomes, although some members of the program management team struggled to understand the importance of these documents. 

The most valuable features are the flexibility and adaptability of Sparx Enterprise Architect. However, these aspects come at a cost of complexity in configuration and management of customization. 

Using EA involves a steep learning curve if you want to understand its capabilities and functionality.

Providing more detailed information about how to configure and adapt EA for consumption by users with less technical knowledge or experience would be helpful. Plus, provide online training that covers the basics of as well as more advanced topics. An introduction on how to do the basic configuration for the non-technical users would also be of benefit.

I was employed on contract by this company, but I had previously used Orbus iServer for Process modeling and developing Business and Enterprise Architecture artifacts. This company had previously used Visio. 

You can search for Business and Process Architects, who have limited technical expertise, and that can be a challenge. In that sense, we were very lucky to have a fantastic team of consultants, who had vast experience and knowledge in how to configure and adapt to meet our needs. They were also able to give us guidance when we were going down the wrong path.

In terms of cost, Sparx EA is probably one of the cheapest tools I have ever used. However, study the most important versions of EA before you buy it. I'd also recommend that you buy the edition up from the version you think you need, as we found that was an issue in our early days.

I wasn't involved in the selection and acquisition process. Since I began in this role, I have been working with SaaS products, such as Signavo's suite of products. In my view, these products are far more usable than client-server products, in terms of getting projects underway and using them in workshops. However, I think that they are not as versatile and functional as products such as EA, although they are rapidly catching up with desktop products.

Creating diagrams and sets of reusable artifacts using UML, Arhimate and other notations.

Using diagrams and artifacts to generate documentation.

We adopted Sparx EA more than six years ago. Before that, all models were created in MS Visio and were maintained independently without any tractability. That led to insufficient incomplete impact analysis and incomplete solutions. With Sparx EA, models became a maintainable and reusable asset of the corporation. Correct impact analysis became a matter of minutes. As a result the quality of solutions drastically improved. Not mentioning that all employees in any department can now clearly understand business processes with all related applications and infrastructure at any level.

• Great adaptability to modeling needs of all organization departments: Business, Architecture, Software Development, and Systems Support.
• Kind of all-in-one solution (in a good meaning of it), through support for many standard modeling notations used in most of domains of the IT/IS. The list of supported notation grows constantly.
• Effective for Enterprise, Solution, and Software architectures.
• Ability to maintain cross-references for all models in all levels - great tractability.
• Versioning for all elements.
• Very attractive pricing and simple licensing model.
• Good set of the add-ons that grow and improve.

The elements of the modeling sets can have better customization and visual representation. It would be great to have a mobile version.

We did not encounter any issues with stability.

With very large projects, the loading time can become a bit longer, although not to the extent of becoming a great concern.

I would rate the level of technical support as "not bad". But I did not need to use technical support too much.

MS Visio was used for tractability and maintenance, and many other concerns, were the reasons that we switched.

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.

In my opinion, there is a great ROI on a product like this.

Pricing and licensing is very attractive, simple, and straightforward.

We evaluated other options such as Rational Software Architect, Visual Paradigm, and Altova UModel.

Plan and organize your elements and models using the best practices from the beginning and create customized project templates. That will benefit you greatly afterwards.

We are building it right now. We first have to build a repository and the tool, and then we have to develop the training for different types of users. We are using its latest version.

Its ease of use and the breadth of the toolkit are most valuable. It has an incredible repository of artifacts to work with, and they're all cross-referenced. 

It works with a whole bunch of different standards. It works with BPMN, which is Business Process Modeling Notation, and it also works with something called TOGAF, which is the Open Group Architecture Foundation. There are different layers when you're dealing with architecture. There is the user interface, application, data, data servers, and all that kind of stuff. You have the infrastructure, hardware, and software layers, and then you have the application and business capability layers. You can model a business process and decompose it into all of the applications, data, and hardware to support it.

They should make the Save button easier to find. 

A simplified user interface for a lighter user would probably be useful. I am not sure if such an interface is already there.

I have been using this solution for six months.

It is very stable.

It is scalable. Right now, we've only got a hundred books, but we want to have hundreds of thousands of books. There are only three of us using it in our architecture group, and then there are probably 30 other architects in other parts of the company who are using it.

My colleague is dealing with technical support. 

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.

In terms of the software solution, it doesn't take a lot of maintenance. It is like building out a library.

I would advise others to understand their needs and find a tool that really meets their needs.

I would rate Sparx Systems Enterprise Architect an eight out of ten. It is a very strong tool, but I don't have enough comparison points to give it a higher rating.