Intro

This feature replaces 280, 281, 284.

It is also quite articulated, on purpose, in order to start practicing UX in agile terms. Giorgio will help splitting this feature and organising the work during sprints.

It has 2 outputs, both produced incrementally sprint by sprint:

• potentially shippable Webjive increments, as usual
• a google document describing the Webjive roadmap

In the following I will refer to these roles with respect to Webjive:

• UI designer, this is the individual who uses Webjive to develop a specific UI to be connected to some Tango devices. This person can also be the UI user, but these two roles are conceptually different.
• UI user,  this is the individual who is going to use the UI constructed through Webjive; s/he will be an engineer or a commissioner.

Plots:

A UI designer can add/change/remove any basic plot from the dashboards of the UI that is working on.

Plots MIGHT include bar plots, histograms, pie charts, scatter plots, time series, spectrograms, dials, and others.

The UI designer can edit SOME of the properties of each plot, such as font, color, size, labels for axes and for points, ticks for axes, symbols to be plotted, variants such as stacked bars, scales for axes, data sources, units, precision of data.

Widgets:

A UI designer can add/change/remove any basic widget from the dashboards of the UI that is working on.

Basic widgets MIGHT include combobox, button, link, icon, label, text field, formatted text viewer, formatted text editor, radio button, checkbox, slider, pull-down menu.

Images and colors:

A UI designer can add/change/remove icons (any of GIFs, PNGs or other might be ok) from the dashboards of the UI that is working on, and configure them so that they appear conditionally, depending on states or attribute values of Tango devices.

A UI designer can configure SOME widgets so that their foreground/background colors can change depending on states or attribute values of Tango devices.

The UI designer and the UI users can view a trace log of the interactions between Webjive and the underlying Tango devices. This is a built-in widget to display the trace data; it is a widget that represents a "console" that can be placed and sized in any region of a screen, just like any other widget.

Roadmap document

A live document is needed to allow Giorgio and Nick to present to other organizations (such as MaxIV and Tango Collaboration) what are the intentions of SKA regarding Webjive, on a rolling horizon of 6-12 months.

This document is to be producted incrementally, based on the findings discovered during individual sprints. Giorgio and Valentina will lead this activity and will be among the editors of this document.

Scope to consider for this feature

We don't expect that every widget and plot will be implemented in this feature. However we do expect that the "console", that what is described under "images and colors" and that a handful of other widgets/plots ARE delivered. These are all the widgets that are used in the TMC prototype (as of 31 May), and a few other ones suggested in the roadmap document.

Note on how to carry out analysis

Analysis of user needs should be carried out as timeboxed spikes of 2 individuals that interview for 1h or less 1-2 prospective users (i.e. members of other SKA teams), collect examples and opinions, organize them, and revise the roadmap document. We expect this to happen 1-2 times during each sprint so that a relatively large number of potential users are interviewed.

Giorgio or Valentina will be one of the interviewers in each interview.

Acceptance criteria

• increments of the roadmap should be cohesive chunks of examples of widgets/plots that are suggested along with text describing how the team discovered that some users might find those things useful.
• each section of the roadmap should enable the reader to understand what new enhancements we are thinking for Webjive, and why we believe it is important to implement them ASAP.
• the roadmap should be based on findings coming from selected SKA teams (i.e. NCRA and CIPA) that develop tango devices. It could include other information that Giorgio will provide (eg. possible similar analysis performed in MaxIV).
• each new widget/plot implemented in increments should be used in 1 or more demos that are informally organized by the team with potential users of those UIs. User feedback should be collected, possibly acted on by changing things in Webjive, and documented in the roadmap.