Details
-
Enabler
-
Must have
-
None
-
Obs Mgt & Controls
-
-
4
-
4
-
40
-
10
-
Team_CREAM
-
Sprint 3
-
-
-
-
14.6
-
Satisfies Acceptance Criteria, Accepted by FO
-
-
Taranta Team_CREAM
Description
We need to run a UX spike (a spike aimed at understanding WHO will use something, under WHICH circumstances, to drive WHAT decisions or actions, and WHY those are needed) to better understand usefulness of these widgets:
- active dashboards: given N dashboards, each of them is associated to some condition (like an event being signalled) that would automatically make that dashboard the visibile one.
- active widgets: in a dashboard, a widget could be normally hidden or collapsed. When an event occurs then the state of the widget changes.
- cyclic dashboards: given N dashboards, the user can link them in a loop so that when run, taranta shows each dashboard for a given time and then switches to the next. Or the switch is manually triggered.
- a barchart widget, where different variables can be plot and compared. Similar to the barchart of R.
- widget for presenting tabular info (eg each rows represent an antenna, a subarray, a beam, ...; with associated attributes and even buttons + LEDs)
- tabbed dashboards: see the description in SP-1871
- starburst diagram: see the description in SP-1870
NOTE
I suggest that this work is tackled in a Lean UX approach: the build-measure-learn loop.
- build mockups based on current ideas
- measure: collect feedback with interviews and user testing sessions
- learn: what might work, what might be useful, what might be challenging from a usability viewpoint
This loop should be executed at least twice for each widget.
Attachments
Issue Links
- informs
-
SP-2508 Taranta widgets can be collapsed/expanded
- Funnel
-
SP-2507 Taranta has a barchart widget
- Funnel
-
SP-2506 Taranta has a tabular view
- Done
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...