EN | ES
Single Role
In this case, the user do all the tasks. This role isn’t an expert, tipically it’s a business knowledge user but don’t have high tecnical skills:
Quick generation of reposrts/dashboards.
Use of builtin gadgets or prebuilt template.
All elements are created in the dashboard engine.
Simple use of datasources. Can be necessary an expert user for this tasks.
Presentation through URL of the dashboard or controlpanel access.
It will be a role that will use, and only use, pre-built gadgets or templates.
Role splitting
With the role splitting, we’re going to paralelize and assigns the task an iterate between them easily. All the development layers are independent so this can prevent from blocking developer from each other. This have a zero cost of integration because all layers are linked by a pointer
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 to not interfere with another, and they also facilitate that the cost of integration is completely null by having reference to the lowest level components.
Beginning with clear requirements, we can have some datscientics uploading data to the platform and writting the diferent datasources. Front developer could only have tasks of building gadget templates outside of the dashboard, while one layout designer can focus on dashboard design and interactions and can have the new upgrades of gadget templates only refreshing the dashboard. In the integration layer, we have the same thing, we can have some developer dealing with the task of integrate the dashboard engine in the front aplication with use URL way of VueJS wrapper
