The establishment of a system revolves around two core concepts:
- the data model
- the view of it that is manipulated by users
To achieve an interactive front-end system, it pays to have a backend that is very clear, a testable data model that acts predictably.
You can of course link in unlimited data to the core of predictable modules, using their individual or a combination of key fields together and attaching unformatted data to that, providing unlimited expansion.
- The developer has to look at the data model from an inside first perspective.
- The user wants to explain the view and how it is manipulated by users, often in an abstract or fictional manner.
The trick is to understand the interactions between entities in an abstract way but to not try an explain implementation detail in any way but to explore how the primary elements of the system interact. By defining these interactions, it is possible to make a machine that treats data in the same fashion, although implicit rules are no longer a complication in the process.
It is probably best to define the data elements to increase understanding of the form of the system. Then the front-end (the content of the dash-boards) has some logic behind it. The very basic thing is data.
Or is it better to define data in the abstract pattern afforded by NOSQL style database records. The central part of the database should be expressed in language without difficulty. It is important to enable interactivity to be written without it being stuck in conceptualisation phase.
