Architectural spike on Taranta 2.0

Benefits include:

• We understand what requirements are relevant and how some of the most critical ones could be supported by a certain architecture.
• the design lets us estimate the effort needed to redesign the entire Taranta
• the specification lets us identify slices to be added as feature in future PIs
• after implementing everything in the specification we end up with Taranta 2.0 that:
  • does what is deemed necessary, and
  • is webpack 5 compatible, and
  • there is no library that is out of date.

• a google document is produced with a list of relevant requirements, with associated quality attributes and quality scenarios (a paragraph per requirement should be enough):
  • a bullet list of requirements that apply to current Taranta and that we want for Taranta 2.0
  • a bullet list of new requirements and their expected benefits for Taranta 2.0 (eg web responsive dashboards, eg performance reqs, eg. extendability reqs, eg, deployability reqs).
• code for the prototypes is produced
• a section of the document is included that discusses the findings and to what extent each of the considered quality scenarios support the requirements.

Quality scenarios that have to be considered are (other scenarios are welcome):

• Performance: here we should consider the performance requirements that were analyzed 2 yeasr ago (https://docs.google.com/document/d/1_mfRBUlzVwrsfUN4tVUzOUZaUetAIPGxbcUBUxBBdgk/edit#heading=h.dx716liqcsn2)
• Extendability: 
  • where a module contains a new type of widget
  • where a module contains a configured widget
  • where a module contains a dashboard
  • where a module contains a new data source (alternative to TangoGQL)
  • where a module contains a new view (ag the synoptic view, alternative to Dashboards and Devices)
• Deployability: 
  • where a user wants to configure a certain instalce of Taranta with a subset of existing modules

Two Google documents shall be produced: a list of requirements for Taranta 2.0 and a specification of Taranta 2.0.

The requirements document should include:

• a bullet list of requirements that apply to current Taranta and that we want for Taranta 2.0
• a bullet list of new requirements and their expected benefits for Taranta 2.0 (eg web responsive dashboards).

The specification document should contain:

• a description of components (ie. deployable artefacts) that make up the physical architecture of Taranta
• each component should be associated to a definition of its responsibility and an interaction protocol and API
• each component should be described in terms of underlying modules and/or classes (ie. parts of the source code), each associated to its responsibility and interaction protocol with other modules
• in particular, the front end in React should be specified in terms of React components, state management (actions and reducers), and possibly other interaction mechanisms (eg events)
• appropriate object-oriented patterns are employed
• appropriate UML diagrams should be added for clarification
• TangoGQL should be retained.

These two documents should be sufficiently rich to let a developer understand if the specification provided suffices to support the requested requirements. Detail should be enough also to accurately estimate the total implementation effort needed (in terms of min and max story points needed for each part).

In order to support the first need ("suffices") a number of quality scenarios should be defined and hand simulated to make sure that the design fulfills that quality attribute (see my comment below https://jira.skatelescope.org/browse/SP-2712?focusedCommentId=160817&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-160817). The list of quality attributes and their scenarios will be defined while working on this feature, after the list of requirements has been understood.

The specification should be such that appropriate unit, intergration and component tests can be easily written.

Original estimation was 8 FP.

Taranta 2.0 code can be found at:

https://gitlab.com/tarantapoc/

Taranta 2.0 documenation containing requirement, archetecture design and performance comparison:

https://docs.google.com/document/d/1lY3FNwkSQ8kLT54XxaOLUFodAAPvn-xAclcniHBoK3I/edit