SISnet Zero Code. New parameterization paradigm

In the 1980s, the management systems were programmed in assembler, a language very close to the machine.

In the 1990s, the continous growth of management needs makes it necessary to evolve towards more modern languages, such as Cobol. These languages will bring programmatic systems closer to technicians, but will remain far from the business user.

At the end of the 1990s, high-level languages began to proliferate, bringing together techniques of scripting to valuable functions to business area, such as Visual Basic. These scripting languages began to be used not only by programmers but also by the user elites.

Since the year 2000, the languages that have appeared in scripting-type applications mixed with parameterization systems are considered low code. Low code is presented as an extension system of pre-built concepts and, by its very format, is still technology-oriented and not business-oriented.

However, despite the step forward in low code, it is still far from most business users. It is still complicated and needs certified personnel, since it is exclusively oriented to a control language and not to functionality, and it forces to have many technological concepts.

It was necessary to go one step further, and move towards a fully business-oriented, "no-code" technology system.

In Zero Code, logic is parameterized. Its construction units are based on functional elements, rather than technological instructions. Business variables exist implicitly based on context, rather than explicitly controlled through language.

For example, how would the actuarial age of an insured be modified in a policy?

1. Using low code, the user should know how to get to the policy, select the insurer and calculate his actuarial age
2. Using Zero Code, the variable "actuarial age of the insured" already exists, and takes the value corresponding to its execution context.

Therefore, Zero Code allows to describe in business terms, the logic of the processes; this way, processes become transparent to the organization and are preserved against knowledge leakage.