LILULI

Team Members

  • Lili Shi, 2010
  • Lulu Hu, 2011
  • Liz Peirce, 2009

car

Problem Statement

Our goal is to provide business women and men with an entertainment system that features the capabilities of a personal digital assistant and allows the user to interact with the system without compromising driving abilities to ensure safety among all passengers.

P1 P2 P3 P4

P5: Implementation

Our final prototype is high-fidelity. It implements all screens and buttons necessary for our three scenarios. Windshield alerts are displayed sparingly to show how they work. Radio functionality as well as presets are not implemented as they are not important to our tasks, however they would be necessary and important in a well developed entertainment system so we have included them in our prototype as non-functional buttons.

Click here to view a how-to demonstration of our prototype.

Click here to view our final computer prototype.

Our prototype was implemented in Adobe Flash, and requires Flash Player to run properly. The prototype presents our phone, music, and traffic functions as described and used in our scenarios. The riskiest part of our system is the keypad menu interaction with the display. This part of the system is the focus of our design alongside the windshield alerts.

In this high-fidelity prototype, the user can see the entire console and dashboard at all times. This allows the user to see exactly what would happen at the click of each button. We implemented each button that was necessary for our user scenarios. We also showed windshield alerts randomly in order to show the user how that part of the system would interact with the user while driving.

*Important Note: Given the use of Flash, we were unable to create dual functionality of buttons that would normally be implemented in a car system, as well as the scrollable buttons. We realized it would not be worth trying to create buttons where you could click the top and bottom rather than scroll as this would not be realistic of what our system actually seeked to do. Therefore, while we kept singular functionality of all buttons, it is important to note that in an actual system, these would be able to do more than one option. For example, one button like this is the Volume/Power button which currently turns the system on or off. In a real system, this button would be able to turn back and forth, changing the volume.