User Stories
- Joy He (Deactivated)
- Cheryl Li
General viewing data
In general: As a team member, I need to be able to access all of the data. Doing so doesn’t necessarily have to be effortless; I just need to be able to access and view it.
**Finding/searching for data/filtering: – @Riishi Jeevakumar
As a team member, I need to be able to find the data set I want as quickly as possible so that a) I can find data in real time during testing (firmware) or debugging components (hardware) and b) I can do my work efficiently in general (even during EOD/checkpoint data lookovers)
Some sort of search box for specific sets of data, filtering system, tab organization…?
Stats Canada
**Displaying values vs **booleans vs enums: ** – @Catherine Burns
**Comparing data: As a team member, I need to be able to view and compare multiple graphs so I can see and compare how each graph changes relative to each other. This will allow me to pinpoint if a change in one set of data corresponds with a change in another (i.e. changes occur at the same time, or one changes after the other) and aid in issue triangulation.
I will often compare data sets that are closely related to each other, such as front battery voltage and rear battery voltage
I could also theoretically want to compare stuff like altitude and motor controller temperature (how does going up a hill affect the MCl temp?)
**Ability to pin data/customize the dashboard – need to ask about laptop usage
Specific values: As a team member, I need to be able to view the specific value of each data point on the graphs - (it can just be a hover)
Connection errors: As a team member, I need to know if and when the telemetry dashboard went offline, so that I know a) that the connection needs to be fixed and b) what time the data that is currently on the dashboard is from
Faults – @Cheryl Li
All faults: As a team member, I need to be able to see/access all faults easily and know exactly when they are happening as soon as possible, so I am able to address or debug them.
access historical data → search/filter
immediate data
**Urgent faults: As a team member, I need to know which faults are urgent/critical, so I can stop and start investigating the solar car immediately.
different type of warning → perhaps banner
Non-urgent faults: As a team member, I need to be able to see less-urgent faults from earlier in the day, so I am able to address or debug them at checkpoints or at the end of the day. **
data log that marks errors?
Fault information: As a hardware team member, I need to have an idea of where the fault is originating from (which part of the car/which board/etc) so that I can quickly diagnose the problem, locate the fault physically in the car, and start working with the part.
show error data → origin, time, error type if we can do that, part
man would it be cool to be able to show relevant data from that error time? we could do super common ones like temperature and voltage. will wireframe because this seems cool
https://www.figma.com/file/epkdq7ZBL5ZzVPCEdN2pLG/Error-Display?node-id=0%3A1
Notes: In the context of the telemetry dashboard, does it make sense to have popups? from a “oh no there is an error here’s a popup that tells me something has gone terribly wrong” perspective, it makes total sense because it pays to have the error displayed immediately and grab your attention. But from a data analysis perspective it doesn’t.
Error Figma Flow: https://www.figma.com/file/3aK1Tv5WAr8r7XyXOpstWI/Untitled?node-id=2%3A2
**Historical data – @Joy He (Deactivated)
Fault investigation: As a team member, I need to be able to find and see all the data at the time that a fault occurred, so I can figure out what went wrong.
When fault occurs, dashboard at that time is automatically saved/bookmarked and is accessible somewhere, so it can quickly be pulled up/jumped to
Navigating historical data: As a team member, I need to be able to find and view all the data at a specific time (ie from hours earlier). For example, we may have gone up a hill at 4:35PM, and I am curious about how that affected x, y, and z.
Ability to save/bookmark dashboard when special event is occuring
Different UI view/styling when in historical mode vs real-time
Start/end time picker? – 24 hours; and a different component if we decide to do beyond 24 hours
Race time
Rapid context changes: As a team member that frequently rotates in and out of looking at the dashboard, I need to be able to decipher the dashboard and the state of the system quickly with limited context so that these rotations can happen efficiently.
Don’t overwhelm them with information
Fewer and larger graphs/pieces of information at the forefront
Logically grouped graphs/information
Better graph labelling where the information can be read and processed by non-firmware users (or anyone who may not be so familiar with the content).