ARIS vs. erwin Data Modeler

Well suited for enterprise architecture modeling where the intent to document elements beyond processes as well, such as risks and controls, KPIs, systems, org charts, etc. It also has the excellent capability of creating custom reports, hence if looking for various views right from summary to detailed, this is a great tool. It is less appropriate for implementing the processes as it is not very strong in BPMN.

I have had a chance to use few other data modeling tools from Quest and Oracle, but I am most comfortable using erwin Data Modeler. They understand your data modeling needs and have designed the software to give you a feeling of completeness when you are designing a data model.

Incentivized

• Query feature is excellent to extract information in a specific manner.
• Ability to create custom reports.
• Collaboration feature is very good.
• Semantic checks to check validation errors.
• cloud based central repository.

Incentivized

• Reverse Engineering: I love the way we can import an SQL file containing schema meta data and generate ER diagram out of it. This is specifically useful if you are implementing erwin Data Modeler for an existing database.
• Forward Engineering: We use this feature very frequently. Where we do database changes in our physical and logical data models and then generate deployment scripts for the changes made.
• Physical vs Logical Models: I like to have my database model split into physical and logical models and at the same time still linked to each other. Any changes you make to logical model or physical model shows up in the other.

Incentivized

• Defining databases, use of entities and relationship diagrams, define data, like data models, there is still a part they could improve.
• Providing more standard reports and improving on access rights and privileges functionality

Incentivized

• Cost is the single largest barrier to entry with this tool.
• Would like to see a greater variety of export options available for use outside of the tool, for example as a vector graphic.
• Support has been uneven at times.

Incentivized

I am a BPM and Enterprise Architect Consultant and hence have been using different BPM and EA tools for consulting practice. Until now I have used Opentext Provision EA,Sparx EA, MS Visio and IBM Blueworks. All of the tools used are good and have their own unique features and capabilities. ARIS BPA is widely used by my current organization for different projects.

Incentivized

I had a lot of experience using erwin Data Modeler for designing data models. I think it's pretty intuitive and easy to use. It has enough features to represent your database requirements in form of a model.

Incentivized

It has good, even complex functionality that is provided by its library and ability to create relations between items, yet it is not hard to use. Anyone can use it in a short time. It provides reporting abilities and good documentation with the availability of exporting options. The only drawback I have seen was user management/login issues.

Incentivized

CA customer support and our account manager have been able to support us with any issues that we have had, from managing our serial keys to issues we logged tickets to resolve. There are aspects of key management that have made it difficult over the years but support usually has worked with us.

Incentivized

The Service area, they have been very useful. ARIS suite is covering number of applications. ARIS engine is very powerful and robust. The tool can be configured in many ways which can be beneficial but can be a curse at the same time. As a user, you need to apply this flexibility with care.

Incentivized

Not listed, but I've only used alternatives built into something like the Squirrel SQL editor. That one is semi-functional but lacking many features and, in some instances, just plain wrong. The only pro there is that it's freely available and works over ODBC. I've tried some of the other free ones like Creately but didn't have much success.

Incentivized

• Documentation of processes made it possible for anyone to see who does what, how and using what systems.
• Dependency on specific people is eliminated.

Incentivized

• It is difficult to assign a monetary value to it. The initial learning curve was fairly long.
• It allows us to have better support documentation.
• It allows ease of communications between functional units.

Incentivized