The Relational Catalog

An incorrect design of the relational (and not) database is a source of great problems in the life of an information system; not only the initial development suffers but also its evolution.
There is a widespread misunderstanding that it is enough to have once used a spreadsheet to be an computer scientist and to create an information system … “what does it take?”; the manager with the Excel spreadsheet is always lurking and is one of the greatest dangers that must be faced by insiders.
The most used models are tools to visually represent data and relationships in an orderly and complete manner but are not able to tell us how to organize thought upstream.
And the question arises: if we know that it is so, do we have to settle for these tools or is it time to take another step forward?
If computers can quickly run the algorithms, whatever they are, why move the processing in the design phase and not let it run on the computer at run time?
The Relational Catalog is a proposal to address the problem in a different way; a new way of thinking about a database that does not destroy the past but, indeed, makes it evolve by integrating it and allowing coexistence between old and new.
An optimal model to allow you to concentrate, at a higher level, especially on the semantics adopted more than on the tedious and repetitive relational algebra that so constantly changes because the initial requirements are not precise or because the needs evolve.