Model-driven architecture can be highly theoretical, but also very practical.

 

At Genus, we try combine the theory and the practice into a good workmanship.

 

For us, model-driven architecture is all about finding the right building blocks, like our logic concepts illustrated to the right.

The right building blocks need to be enriched with the right properties and functions, to give our modeling users what they need to make applications.

 

The figure to the right shows some details of our task, action and effect concepts, as they are used in Genus Studio.

Our modeling users (or modelers as we call them) combine our concepts to workable applications, like this detailed form.

 

Our modelers do not have to do any programming whatsoever (and our modeling tool Genus Studio does not allow it either).

Our applications are used by our customers to handle real-life and complex business processes.

 

Genus Apps is used in a competitive market - the technology is beyond the point of initial research and development.

Our technology is based on a software architecture made to handle large data volumes and many concurrent users.

Genus Apps itself is made by programming using development tools and components from well-known and recognized vendors.

But most importantly, this paradigm shift had not been possible without great programmers that get the work done by carefully designing and writing the code.