What advice do you have for others considering 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.

I would recommend this solution for those who work in diverse environments and need a versatile tool. I rate it a seven.

I would definitely recommend using this solution for its modeling features. Improvements are always welcome in any tool. We're looking forward to a web browser version, among other enhancements. There's always room for improvement. For me, it is a ten out of ten.

I recommend Sparx Systems Enterprise Architect and rate it a nine out of ten.

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

The tool fits best within the IT realm vs Business. I would advise against using the tool when deployed within a collaborative environment with business users.

When using this product in a shared environment, in terms of multiple different aspects of the business, it's not really tied together well at the top or out of the box. It takes some configuration. So, you need to understand how to use shared resources to build architecture so that if you are doing architecture on one object inside the enterprise, somebody else should be able to recreate it independently. What you do should be available to those who need to model it. I would rate it a seven out of ten.

I'm currently using the latest version of the solution at this time. I can't speak to the exact version number, however. I would definitively recommend the solution to any IT department as it's very cheap and very powerful. However, it is not very user-friendly. It's a modeling tool, and modeling is not very popular typically. That said, you can scale it to fit the requisite departments.

I rate the solution seven out of 10.

We are customers and end-users. We don't have a business relationship with the company. I'd rate the solution at a nine out of ten. We are very happy with the product overall.

I would recommend this solution to others. I rate Sparx Systems Enterprise Architect a seven out of ten.

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.

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.

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.

Be realistic about what you team can achieve. In a single use situation there is little advise needed but if you are intending to deliver it into an organisation, ensure that * The way it will change how you work is possible (considering people and processes) * The cost is reasonable * The competition has been assessed using a POC not marketing ware (e.g. Orbus) * The training impact is understood (The tool is not trival to use) * The business view is not ignored. In my experience this tool does not remove the need to render information for a business audience separately and neither does tools like Orbus.

I'm not sure about which version of Sparx Systems Enterprise Architect I'm using. My company has a corporate license, and I get updates, but I don't know which version I have at the moment. I currently have a desktop version of Sparx Systems Enterprise Architect, but there are two or three other people who have the server version, and a repository was supposed to be set up for sharing among myself and the others, but there isn't much success with that. I believe the tool is deployed on-premises, but I don't know what the repository is, because I have a standalone version that runs on my Windows desktop. There are five users of Sparx Systems Enterprise Architect in my company, and they're into enterprise architecture. For deployment and maintenance of the tool, only one person is required because of the small volume of users. Personally, I don't have plans of increasing usage of Sparx Systems Enterprise Architect because it's not the tool for me. I'm not a person who likes UML, but I do know that my company is looking to build a server-based version of the tool and extend its use. My company is looking at other tools as well, such as LeanIX, Visio, and Lucidchart. My advice to others looking into using Sparx Systems Enterprise Architect is to make sure it meets all their requirements, and that it has all the capabilities they need. I would recommend looking at some training, because the tool is not very intuitive for data modeling. My rating for Sparx Systems Enterprise Architect is a five out of ten. It's an average solution, so it's a five for me. It's in the middle. What would make it a ten out of ten for me is if they improve their data modeling capability because I do data modeling and Sparx Systems Enterprise Architect is not a very good data modeling tool.

My advice to others is to get off to the right start by choosing the correct template. That's very important, otherwise, you will be lost. I rate Sparx Systems Enterprise Architect a nine out of ten.

I would rate this solution 9 out of 10. That tool is still alive. We recognize that 10 years back, it was the same product, and at the moment it seems to be still alive. That means the background of the product is okay, and it can be in life for the next 10 years.

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.

Sparx is a good tool for extended usage such as modeling or automated testing. It allows you to do good testing upfront. If the only intention is to use it for architecture modeling and visuals, it may not be the best solution. I would rate this solution a seven out of ten.

I would not recommend this solution to others. I rate Sparx Systems Enterprise Architect a five out of ten.

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.

I would recommend this solution. I would rate it a six out of 10.

Go for it. Whichever team in your company that will integrate the tool into your Enterprise Architecture Management toolchain should read the books from Thomas Kilian (leanpub.com)

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.

I am about to do testing of interoperability between EA, System Architect, and a few other things. I'll be really interested to see how the ins and outs of sharing artifacts between those two capabilities work. I would advise others who are looking into implementing EA to get training. I learned it the hard way. I'm hardheaded, and I just went at it myself, but getting training is going to be a helpful thing on what to do and how to do it correctly. I would learn how to do what you're trying to do before buying a tool to do it. Data modeling is not just about the tool, it is about the actual data modeling itself. So, if you're going to do enterprise architecture, you have to take enterprise architecture training from The FEAC Institute or another institute. Instead of just going right in and using the tool, it is better to be trained. I train my people in what they're doing and not just the tool. They do it way better when I give them the tool. I would rate Sparx Systems Enterprise Architect an eight out of 10. We do a lot of things with it, and it is a great tool, but no one is a 10.

I would recommend this solution to others. Just make sure to hire an expert to get you started. Overall, on a scale from one to ten, I would give this solution a rating of eight.

In Poland, it's a very popular tool, and I recommended it. It's not ideal, but they are very good tools. On a scale from one to ten, I would give Sparx Systems Enterprise Architect a nine.

It's a very good starting point and a very affordable solution with a lot of features. I would rate it at nine on a scale from one to ten.

To implement this solution, you need experienced people who know about enterprise architecture. I would rate Sparx Systems Enterprise Architect an eight out of ten.

We have been quite happy for a number of years, but it has several drawbacks. We are considering an alternative. We are not looking to get rid of this solution but use another product and use them both for a while. I would rate Sparx System Enterprise Architects a seven out of ten.

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.

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.

It can do so many things. Because of this, sometimes, it can be a bit difficult to find what you need, which is logical and expected in every tool with a lot of features. It is kind of a project in itself to learn to work with it. It is quite easy when you work with it for some time. It is a very good solution. Before you start, I would recommend considering the following: * How will you use it? * Do you need a central database or does everything work separately? * Do you need a lot of exports and imports for other things? There could be challenges in terms of the integrations of the models and when there are a lot of people working on it. You need to think about who is given what rights, and you shouldn't let everyone work on everything because it could become a mess. You need to think carefully about how to organize your work before you start working with it. I would rate Sparx Systems Enterprise Architect an eight out of ten.

I'm a customer. The product is a standalone application on my site. It's licensed from the cloud. I'm not sure if I would recommend the product. This tool has so many features. It depends on what a person needs to use. Generally, I've experienced some limitations from all the solutions that I've found - including this one. It's too complicated of a software solution to definitively recommend. Overall, I would rate the solution at an eight out of ten.

It is really good if you want to develop workflows. It is not good for data modeling. For data modeling, Visual Paradigm is better. I would rate Enterprise Architect a seven out of ten.

To my knowledge, we plan to continue the usage of this solution. It is the decision of the company and they have decided to continue using this product for specific purposes. My recommendation for this product really depends on the purpose. I am more on the business side, and for business purposes, this product has some limitations. The user experience and presenting it is challenging. This solution is not fancy, as in other products. However, it is a useful tool for IT people who need to design their solution architecture. It depends on the purpose and orientation of the designer. If the designer is IT, it's good because I have heard it from many people with an IT background that this is a kind of baseline that they need to use for UML design, and also for details and for architecture, is good. This is also good for Enterprise Architecture because it has ArchiMate. While there are many good features, there are better ones available in the market. I have only read about them, so I cannot accurately compare. It is difficult to rate this product, as everything has a purpose. If for example, I was in IT, I would rate it a nine out of ten, but from the business side, for me, I would rate it a four out of ten. As an overall general rating, I would rate this solution a six out of ten.

Other than the manual steps we have to take, the product is pretty fancy and gives you a lot of options. I would rate this solution a seven out of ten.

Hang around in the user's community to gain a perspective of what others do and don't do.

It supports a variety of databases - if you have more than say 5 do not use access. Maybe it is better now but it did cause us problems when 30 devs were using it. Access DB is ideal for the single user or very small team because its a file-based repo which is easy to back up as part of the project back up at my home-based office I use both Access and MSSQL repos - you can migrate - but its not a simple exercise. I guess if you did it a lot you would have a well-documeted process - i.e picking the wrong driver is/was possible and it will give you an incomplete/corrupt migration. That being said I do do it because I like to get at the SQL repo directly.

The advice that I would give is that you should be willing and able to spend a lot of time outside regular working hours to get to know the tool because it's difficult to just pick it up and if you've got no mentors or tutorials that are so specific as to cover what you're trying to do, you have to dig it out. It's difficult. I would rate it a nine out of ten.

My advice would be to do a lot of training beforehand. We have invested a lot of money in terms of training because we didn't do it before, so it's a little bit difficult. In the next release, I would like to see more integration with other tools like Microsoft Azure. That's really important to us. I would rate it a nine out of ten.

We're just a customer. We don't have a business relationship with Sparx. The solution is deployed through the application installed on a Windows 10 machine and I do everything on the machine, not on the Cloud. I stay away from the Cloud. We're not that big, basically a two-man shop. The advice that I would give other users is that you better be willing and able to spend a lot of time outside of regular working hours to get to know the tool because it's difficult to just pick it up. If you've got no mentors, or if you've got no tutorials that are so specific as to cover what you're trying to do, you have to dig it out. It's difficult. That said, the solution is as good as they come. I'd rate the solution nine out of ten. If it offered more tutorials, I might give it full marks. At the end of the day, the solution is only as good as the person using it.

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.

Watch out for fraudulent consultants who spout jargon but know nothing about modeling. Make someone show you the real stuff they have done.

My advice for anybody who is implementing this solution is to take advantage of the good webinars that they have. Go through the example tutorials because they have a lot of them, before embarking on your own. I don't know how their courses are because I did not feel the need to use them. However, because I have used a lot of UML and modeling tools, I may not be the typical user. I would rate this solution a nine out of ten.

I would rate Sparx Systems Enterprise Architect an eight out of ten. It's pretty good, but it's not that intuitive for the beginner user.

My advice for somebody implementing this solution is to make sure that they utilize it to its full capacity so that they can draw the greatest value out of it. This product can provide the user with a number of solutions, so one has to make sure that they exploit all of the benefits. I would rate this solution an eight out of ten.

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.