Modeling future solutions and using BPMN or use cases. So, in general, creating direct accounts.
We use it On the analyst level. So, analysts create specifications or storage using this tool.
Sparx helped us facilitate better system modeling and design in our organization.
I personally find the tool quite powerful tool and benefical, especially given its modeling features and traceability. However, I rarely use this tool now due to my management position.
In general, we now have a problem with Sparx Enterprise Architect because many analysts think it's too complicated to use in a giant environment. So, two years ago, it was used very, very often, and it was a basic tool in the organization. Now, there's a discussion. Is it worth using Enterprise Architect in the company? We need a better, lighter tool to create, for instance, user storage. So, our company is at a specific stage in our product development or software development, where there are some people who want to use it in connection with something like Papyrus, for instance.
For engineering, it's not a good description because it's complicated and for analysts in a dry environment. In the agile environment, the analyst focuses on use cases or creating user stories for support. It's not user-friendly for them.
It is not not user-friendly. But in general, it's complicated for very simple activities. For example, when we know and use Enterprise Architect well, and we can use all these features for such analysts, it's no problem to use it.
But new analysts, modern analysts who work in a giant environment, don't want to learn how to use Enterprise Architect in the environment because they think it's too complicated and has too many functions.
There should be ways to find what you need easily and use only the functions relevant to our project. For example, if we're just analyzing a small project, we don't necessarily need tracing or tons of diagrams.
We've also had issues installing the Proof of Concept (POC) for Sparx Prolaborate. Many people found it overly complicated and needed improvement. Overall, user-friendliness is a major pain point for Sparx in my company.
So, Sparx could look at similar products with a more user-friendly interface in the industry.
There are people who use Enterprise Architect religiously, and there are others who prefer simpler tools like point UML for just drawing diagrams. It depends on the needs of the project.
Another point for improvement would be enhancing the versioning of models. Although there's a way to establish timelines, it's not as powerful as it could be.
We use it in our company. I have been using it for ten years.
The stability has been good and satisfactory. I would rate the stability a ten out of ten.
Since each team uses its repository, the need to scale hasn't arisen. There are around 20 to 30 end users using this solution.
However, a web browser version would be advantageous, considering current trends towards cloud-based solutions. The desktop version is somewhat limiting.
While we've attempted to use it for integration purposes, such as contract creation, there are challenges, especially with unique hardware integrations. It often proves simpler to use external tools for software development.
In general, we don't need support since we have an internal team in our company that maintains the queries related to this solution.
I'm not well-versed in many other tools of this scale, though I've seen Visual Paradigm, which seems nice. However, Sparx Systems Enterprise Architect has been used by our company for many years, making it a staple tool for us.
Despite some thinking it's complicated for modern development, its utility for those familiar with it is undeniable. I would recommend it, as we don't consider replacing it due to any significant shortcomings.
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's reasonably priced for large organizations, though it may be perceived as expensive for individual users.
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.
