In the current situation, the software package is often leading, rather than the wishes of the end users
Over the past 30 years, companies have acquired complex software systems to tackle business challenges. These systems are used throughout the organization, such as purchasing, sales, human resources and finance. With these one-size-fits-all packages, companies are forced to adapt to the process, as prescribed in the supplied software system. An alternative to this is customizing these packages. However, this is very expensive and complex, since (external) consultants have to be hired for this and the translation of customer wishes into software code is difficult to validate and therefore realize.
Most companies therefore choose to adapt to a software package. But not every company has the same working method as prescribed by the software. This creates gaps between the software supplied and the desired working method of the company. This results in activities that are performed outside the system, for example using Excel sheets or even paperwork. This makes processes invisible and uncontrollable. It also increases error sensitivity and complexity. Just think of the consequences it can have for the process if an employee loses his Excel sheet or becomes ill. The consequences of this are often incalculable.
A model-driven approach to software development
A model-driven approach aims to close the gaps where legacy software does not match the desired process of a company. Our model-driven approach is close to a so-called low- or no-code solution. With this we refer to a way of software development that is aimed at building advanced software with less (or no) programming work. Instead of entering many program lines, the emphasis in this method is on merging building blocks to obtain the desired functionality. An advantage of a model-driven approach is that a model can lend itself very well as a blueprint, which is easy to understand by the end users and on which further improvements can be made, such as eliminating or automating redundant or non-value-adding activities such as mail traffic and handover.
The difference with other low- or no-code solutions
Where most low- or no-code solutions get stuck on being able to develop front-end applications, we focus on the development of a fully functioning workflow system. Complete in the sense of an attractive interface for every user, plus a working back-end for (automatic) retrieval, storage and storage of information. Translating models directly into software with the help of a compiler results in us being able to build validable and lightning-fast software that fits the desired working method of a company instead of manually writing and testing ( de-bugging) millions of lines of code. In this way, software becomes a facilitator of process improvement and innovation, rather than a hindrance.