ARIS vs. Mendix

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.

Mendix excels in scenarios involving Business Process Automation, making it a strong choice for applications requiring workflow automation, including processes like request approvals, document management, and other business workflows.Conversely, Mendix may be less suitable for projects that demand highly customized solutions with extensive custom coding. Its primary focus on low-code development may not align well with the requirements of projects that heavily rely on intricate and specialized coding.

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

• We're able to really easily develop different views that are very specific to a customer's needs or customer's different types of user needs. So for example, the production managers can have a certain view that's relevant to them and then certain line managers can have views that are specific to them that allow them to run different scenarios which they define. So it allows us to easily build customized apps for each different type of user.

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

• Earlier versions lacked in UI/Ux. This is still improving.
• Since everyone and anyone can create custom add ons (widgets), Mendix could improve their quality checks (but not as rigid as eg Apple).
• Upgradeability used to be somewhat of an issue. Version 7 looks to be handling this better than previous versions.

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

A 10 would say I have nothing to wish for. A 9 means I haven't seen anything better.This tool really helps you in the whole creation and maintenace cycle, so from requirements to building/modeling to testing to deploying to capturing feedback.

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

Response times are quick and you will get updates regularly about the status of your request. Even with very technical questions they have specialists that can help you with your problems it will give you an answer or help you with a work around.

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

Mendix would be my preferred system all the way. The system is designed for these kinds of works. I've worked with WP and DNN but they should be used just for websites. To create an app for a business value, I would suggest Mendix. Also, the offline capabilities of Mendix have greatly improved since the deployment of Mendix 7.13.

• 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 helps to speed up application development because of its low code by the fact that it's low code. It allows professional developers to focus more on specialized application development rather than the more routine application development that business IT and super users can do for themselves with some coaching from the IT department. So it's just allowing the more specialist professional developers.net, for example, Java in our organization to focus on more complex engineering application developments.

Incentivized