What is our primary use case?
I use Pro Cloud for just connecting my Enterprise Architect on-premise to the Prolaborate; it's a technical usage, not a functional one. What I use functionally is Prolaborate, not Pro Cloud.
We use the solution for different activities. This is for enterprise and solution architecture, so it's all about the TOGAF continuum documentation with application mapping services, objects on cities that we are manipulating internally. This is also used on projects, and I'm the project manager for a big IT transformation project. Enterprise Architect is my main repository for design. I've got all my, let's say, requirements, data entity, data transformation, and REST API documentation also there.
What is most valuable?
Why I use Pro Cloud is to use Prolaborate. To use Prolaborate, you need Pro Cloud, and Pro Cloud has a more user-friendly interface. Sharing my diagrams with a large community of people is easy, as it's user-friendly on the web.
You can collaborate and see comments and discussions around diagrams. We have introduced Prolaborate to extend the usage within the organization.
The solution can scale well.
We have found the technical support to be helpful.
The pricing is reasonable.
What needs improvement?
The user-friendliness could be even better.
I've been looking at some alternative solutions, as it's very difficult to document in an Enterprise Architect model, a data model that's NoSQL. It's a very old-fashioned relational database. If you want to document a diagram, it's very good. If you are working on a relational database model it's fine for a primary key or foreign key kind of thing. That said, today we work on a NoSQL database, Triplestore, RDF, and Symantec. It's very difficult. I know that some competitors enable more NoSQL capability documentation for the objects. I know that erwin, for example, released a new version at the beginning of the year that extended the capability to document in a more efficient way a nonrational model.
For how long have I used the solution?
I started using the solution a year ago.
What do I think about the scalability of the solution?
The solution is very scalable. We have just under 100 users at this time. We are extending usage right now to 100 users.
How are customer service and support?
Technical support is very good. they provide excellent assistance when we need it. We are satisfied with the level of support we get.
How was the initial setup?
Initially, I joined the company a year ago and Sparx System was in place, however, we wrote Pro Cloud and Prolaborate and I was the one introducing Pro Cloud and Prolaborate.
The ramp-up in the tool is difficult to access. I'm talking about the Sparx System, not Prolaborate. It's not that user-friendly, and therefore there's a learning curve. It can be difficult for some of the people collaborating on the product.
What's my experience with pricing, setup cost, and licensing?
The pricing is quite good. When it comes to functionality vs cost, the product provides a good balance. It's a quality solution and provides good value for money spent. Other options are much more expensive.
What other advice do I have?
I'd rate the solution at an eight out of ten.
Which deployment model are you using for this solution?
On-premises