top of page
Escribiendo en una computadora

Language and Methodology

En el trabajo

When a custom development is delivered, we find differences between what the client initially thought and the idea that was finally transmitted to the development team. Normally converting an idea into programming code can take a long time, due to the large number of lines of programming code required.

Based on our experiences developing in our factory and managing code from multiple developers and multiple projects, we created our own methodology where we minimize this risk.

We minimize the amount of programming code required to turn a complex idea into a system component.

We identified that many application performance issues were based on how complex it is to properly separate the persistence layer and the business layer.

Our language and methodology largely mitigate this problem.

We identified that much of the development time of the applications was consumed by the development of the visual interfaces.

Our language and methodology greatly reduced the time required for the development of interfaces.

Our language is based on flow charts, and a very small number of programming commands, where the use of SQL sentences complements the capacity of the language.

Average performance values
using

Flujvision

tablafluj_ing.png
bottom of page