Mendix Model-driven Development Platform

Guiding principles

At Mendix, we believe we’ve found the optimal balance in using the best capabilities of domain specific modeling (DSL), generic-purpose modeling (UML) and generic-purpose programming (Java, .NET). All three approaches are fully integrated in the Mendix Model-driven framework and co-exist in full harmony. We believe this is one of the core advantages and distinctive features of the Mendix solution. Importantly, when building the Mendix product, we consistently applied the following principles:

• Improving collaboration between Business & IT
  In essence, each model provides a common communication language between business analysts and IT engineers. Therefore each DSL should be supplied with a graphical and business-oriented interface that should be comprehensible for both business analysts and IT engineers. The business analyst can either model himself or otherwise easily pinpoint where the model does not fully match business needs. The IT engineer can check whether the model copes with any relevant technical details.

• Each DSL is executable by a run-time environment
  The model should be executable as a working application, without the additional step of code generation, preventing many of the maintenance and testing issues related to code generation

• Each DSL should be easily extendable with 3^rd generation programming languages
  This leaves the developer with “a way out” to cope with any unusual specific cases

• The need for using 3^rd generation programming languages should be minimised
  With the emphasis on DSL’s and the use of open standards, very little additional manual code (in Mendix “Java actions”) is required for an average project implementation, generally between 0-5%. Of course, developers remain able to manually intervene or add any existing libraries to the framework.

• Open systems architecture
  We are not tomorrow’s legacy. As we are a company of developers ourselves, we understand the value and importance of an open, extensible technology platform. As such, we provide an extensive API that gives low level access to the core of the framework. Even though our claim is to empower business analysts, real developers will not be disappointed.

• Open standards
  Mendix strives to adhere to relevant open and industry standards. Each model should be based on an existing industry standard if such exists. See the last chapter of this paper for a list of supported standards.

• Reusable
  Enable and provide incentives for the easy re-use of models, services, components, knowledge, existing technology and skills as much as possible.