DRI | |
|---|---|
Participants | |
Start Date |
|
Status | DEVELOPMENT |
Tools | Figma, Confluence |
On this page |
📔 Introduction
The driver display shows information about the car that is most relevant the driver while the car is in motion. Generally, it will contain gauges, indicators, and warning symbols. This content may change depending on the car's equipment, settings, and which functions are active at that time.
What’s special about our display?
MS XIV will have a 7” x 5” touchscreen integrated into the dashboard behind the steering wheel.
Our goal is to minimize the amount of information to reduce the cognitive load on the driver, who will be driving for long periods ranging from a couple to a few hours.
The driver display will receive data from the Telemetry Pi, which will allow us to display unique information such as the ‘recommended speed’ that Strategy will be modeling.
💼 Problem
The task of HMI designers is to ensure high usability, low distraction, and high user acceptance. And the HMI design principles listed below can help achieve the perfect balance of these criteria.
How might we minimize the potential for distractions and cognitive overload for the driver?
🏁 Goals
To create an interface that will cater and will be intuitive to both the typical everyday driver and driver for MS XIV.
To design a reliable system, which in turn will reduce the required level of attention so the driver may focus on the road ahead of them while driving for long periods
🗓 Timeline
The driver display was tackled during 3 separate terms, the first two of which will be referred to as ‘early iterations.’ This timeline focuses on the latest iteration.
Phase | Description | Deadline |
|---|---|---|
Research | Learn about the current architecture of the Driver Display from the Firmware team!
| 2 weeks |
Planning | Create a clear plan of action before starting any designing!
| 1 week |
Design I | Design the best driver display!
| 3 weeks |
Test I | Collect feedback and opinions about the design
| 1 week |
Design II | Apply the feedback received during Test I and improve our designs!
| 3 weeks |
Handoff | Pull all assets and documentation together for easy access for developers.
| 1 week |