Development lifecycle with Dashboards

EN | ES

1 Single Role
2 Role splitting

There are two typical ways of working with platform dashboards, In the first one, a single user is in charge of all the tasks, while in the second one, there are different profiles.

Single Role

In this case, one user will do all the tasks. This is a non-expert role, typically a user who knows the business, but does not need to have great technical skills.

Quick generation of reports/dashboards.
Use of gadgets or pre-built templates.
Creation of all the elements from the dashboard engine.
Simple management of data sources: The collaboration of a data expert or queries may be required.
Direct presentation through the url of the dashboard or access to the control panel.
It will be a role that uses, and only uses, the pre-built templates or gadgets.

Role splitting

In this case, we will address much more complex dashboards, focused on client customizations, and we will want to have a division of the work to be performed. A user can monopolize all the roles or just one and, depending on the complexity of the case, all the stages of development may be necessary or not.

By having stages in the process, we will be able to divide the work and iterate easily. All the layers are decoupled and, therefore, allow the work of one team not to affect another’s and, in addition, they make it possible for the integration cost to be completely null, by having reference to the lowest level components.

Starting from clear requirements, we can have a data scientist uploading data to the platform and modeling the different data sources. We can have a front developer who is only in charge of building gadget templates (will always develop outside the dashboards), while a designer will link these templates to her dashboard and, simply by refreshing it, she will be able to see the changes that have been included. In the integration part, we will have the same case and we can have a profile in charge of integrating the engine in other applications, also in a decoupled way, through URL or the VueJS Wrapper.