Sparx Systems Enterprise Architect Reviews

• Standards development for OMG - IEPPV, EFFRA, SOPES, IEPPS
• Product development - ASMG implementation of the IEF framework
• Client EA activities - for multiple federal and provincial agencies

Simplified our task at maintaining architecture information and traceability with requirements.

Large variety of profiles and frameworks available out-of-the-box without the need for customization, and not locked into one way of doing architecture. Huge advantage as one works the architecture between business and technical communities.

• Document
• Report generation
• More challenging than other tools to maintain documents and document versions for an architecture board review.

Using Sparx Enterprise Architect allowed my customer to detail and make the company's IT strategy visible and accessible to all. The system provided clear roadmaps for IT development and helped to keep up-to-date documentation of systems and processes.

I like to use this system, it is a handy tool for visual modeling that provides opportunities for analysis, design, and support of models using ArchiMate, UML. 

The system provides powerful tools for obtaining reports and documentation. 

There is a good community of users of this system, providing the opportunity to learn and share knowledge.

I would like the system to more "intellectually" build a scheme, place icons, and connect lines on the schemes.

No issues with stability.

No issues with scalability.

Good.

ARIS Business Architect, ARIS Business Designer. 

Sparx EA is better suited for small and medium-sized companies, cheaper and easier in terms of training. It is better suited to modeling on ArchiMate 3.0 notation.

Easy.

Pricing and licensing are suitable even for small companies.

I recommend connecting to the Sparx EA community.

Solution architecture and design, however the database management area really was not usable. I could not even send in a DDL to reverse engineer it. Also, adding referential integrity to existing fields from a reverse engineered database resulted in duplication of keys. 

Not really.

Unfortunately, only one of our solution architects was using this in the end, as the others resorted to Vision because it was more user-friendly. I ended up buying an Idera licence for ER/Studio and using that instead.

I struggled with most of the features for this tool, as did the rest of our architecture team.

The database part needs to be more like ERwin or ER/Studio. 

It really did not work for logical modeling. The look is very old-fashioned. You can't make the diagrams easy on the eye, so we ended up drawing them again in Visio anyhow.