What is our primary use case?
We picked it as we wanted something that included all of the shapes represented in the software architecture solutions of our company. We created near 2,000 products that we have in the company. We used this product to represent the software architecture of our solutions and the mapping within the processes of the company.
We tried to map a set of fields and we have and combined it with the processes of the company.
What is most valuable?
The main feature that we like the most is the ability to have a unique repository where all the architects can interact and play together with the shapes of different architecture solutions. They have a unified repository where users can share the developments they're working on.
Its availability is very good.
We've had some internal changes in the company. It allows us to start with an initiative that will accumulate new architecture solutions. At this moment, the initiative works with specifically with HOPEX and we are able to adapt it to our new company direction.
What needs improvement?
I can't speak to which features are missing. I don't have any information on that and don't really have any input.
The solution is quite expensive.
For how long have I used the solution?
We've been using the solution since before the pandemic. We started using it around 2019.
Which solution did I use previously and why did I switch?
We use Sparx Systems as well as MEGA HOPEX. Our organization bought both solutions.
What's my experience with pricing, setup cost, and licensing?
I found that the solution is very expensive for what it does. We are integrated with both HOPEX and Sparx solutions, however, Sparx Systems we work with on a set of licenses that we had previously, in 2018. We find it a bit less expensive.
Which other solutions did I evaluate?
Since we use both HOPEX and Sparx, it's easy to compare the two.
For example, if you compare the price of MEGA HOPEX with Sparx Systems Enterprise Architect, Sparx is cheaper. Our company is looking at pricing and it's an important factor we are taking into account. However, Sparx can be a bit slow. If you are trying to design software architecture, sometimes we run into issues and need to refresh. HOPEX also occasionally needs to be refreshed as well, actually.
We find Sparx to be more useable as well.
What other advice do I have?
We are customers and end-users. We don't have a business relationship with the company.
I'd rate the solution at a seven out of ten. If the architecture was a bit better, I might rate it higher.
Which deployment model are you using for this solution?
Find out what your peers are saying about MEGA International, Sparx Systems, Orbus Software and others in Architecture Management. Updated: August 2021.
534,057 professionals have used our research since 2012.