Drowsiness Alert System

Transcription

1 Drowsiness Alert System 1 P a g e Brandi Thompson, Amelia Bauer, Devin Ross, Krystal Flowers, Becky Morrissey & Ben Degedeh

2 Between 2005 and 2009, there was an average of 83,000 crashes each year related to drowsy driving. The National Highway Traffic Administration 2 P a g e

3 Concept Prevent drivers from falling asleep at the wheel We began our project with this one simple idea. We knew that drowsy driving is problem that can lead to fatalities, but we did additional research to validate the need for a solution. We found the following statistics: The National Highway Traffic Administration found that between 2005 and 2009 there was an average of 83,000 crashes each year related to drowsy driving. This annual average includes almost 886 fatal crashes (2.5% of all fatal crashes), an estimated 37,000 injury crashes, and an estimated 45,000 property damage only crashes. AAA estimates that one out of every six deadly traffic accidents, and one out of eight crashes requiring hospitalization of car drivers or passengers is due to drowsy driving Clearly a solution would be more than helpful. 3 P a g e

4 Sketches After we agreed on a concept, each group member sketched potential solutions. We discussed the sketches and then consolidated them into a single sketch. Frame 1: Overview Sketches of how the app could potentially work. It could monitor steering behavior, eye movements and how often the vehicle drifts out of the proper lane to determine if a driver is sleepy. To help the driver wake up, the system could use GPS to direct them to a helpful location like a coffee shop or a rest stop. We also created a name for the app: WakeUP. 4 P a g e

5 Frame 2: Eye Tracking Frame 3: Monitoring Driving Behavior Frame 4: Tracking & Solving Drowsiness 5 P a g e

6 Personas After developing our sketches, we created two personas for WakeUp: Deborah Dormir and Kathy Greyheart. Deborah was created to represent the most typical WakeUp user: someone who downloaded WakeUp for their own personal use. Kathy Greyheart was created to represent a secondary type of WakeUp user: someone who downloads the app for a loved one to use. 6 P a g e

7 7 P a g e Deborah Dormir

8 8 P a g e Kathy Greyheart

9 Mood Board & Style Guide Next we began to brainstorm WakeUp s visual design by creating a mood board and drafting a style guide. We decided that we wanted the overall tone of the app to be friendly, dependable and trustworthy. To achieve this feel, we focused on blue tones and sans serif fonts. Lato Roboto 9 P a g e

10 10 P a g e

11 Scenario & Narrative Prototype Next, we used our Deborah Dormir persona to create a scenario and a narrative prototype. Deborah Dormir has just spent the past 12 hours meeting with a new client in Honolulu. She is driving to her hotel. It is only 8pm--but that s 11pm in her time zone. 11 P a g e

12 12 P a g e

13 13 P a g e WakeUp s proprietary system analyzes the data from the camera.

14 14 P a g e Deborah is displaying too many signs of drowsiness. WakeUp plays a sound to wake her up.

15 15 P a g e

16 Mid-Fi Prototypes After completing the narrative prototype, we began to dive deeper in to how WakeUp would work. Is it a phone app? If so, how could someone who was driving safely operate it? Should it be built in to a car instead? When/ how does a user sign up and or log in to WakeUp? Where are WakeUp s monitors located? And what s the best way to wake a sleepy driver up? We discussed these issues and decided to build two Mid-Fi prototypes to test with users: a phone app that could be placed on a driver s dashboard and an app that could be used in a driver s built-in dash display system. Initial Mobile Prototype Initial In-Car Display Prototype 16 P a g e

17 Evaluation: Phone App Background This prototype of WakeUp is fully controlled by the user s mobile device. The user places their phone in a dashboard cradle. The phone s camera monitors for signs of falling asleep at the wheel. The purpose of this evaluation was to: 1. Determine if users can understand system navigation and prompts. 2. Determine how users respond to the sound of our alarm. 3. Determine if users were distracted by shaking their device (thereby taking their eyes off the road). Test Setup There were two people involved, a facilitator and a user. The test was captured by video recording software. The facilitator directed the user to sit in front of a laptop with the phone app demo loaded. The facilitator dimmed the lights in an attempt to create an environment that would simulate a quiet night time drive. 17 P a g e

18 Evaluation: Phone App Script Moderator: Let s imagine that you re getting ready to go for a drive at night. You worry that you may get sleepy and want to prevent yourself from falling asleep at the wheel. You decide to use the WakeUp app to keep yourself awake and alert. The application is installed on your phone and activated. How would you get started? Expected Response: User clicks on the WakeUp Login button. The application presents the Welcome screen. User would then click on Activate Alarm System. Moderator: Let s now pretend that you have gotten sleepy. Action: Moderator clicks the red Click for Demo button. Moderator, please encourage user to yawn or nod their head until the alert screen appears. Action: Moderator counts to 5. Action: Moderator plays alert sound and app changes to Shake Device screen. Expected Response: Tester is surprised and alert. Tester shakes phone, thus stopping the alarm. Moderator: Please reset the system and continue your drive. Expected Response: User clicks on Reset. User is taken back to the Active and Monitoring screen. Moderator: Now please end your drive. Expected Response: User clicks on Exit and user is taken to the Welcome screen. Moderator: Thank you for walking through the application. 18 P a g e

19 Evaluation: Dash Display Background This prototype is an app installed on the user s car dashboard display. The purpose of this evaluation was to: 1. Determine if users can understand system status. 2. Determine how users respond to the voice alarm. 3. Determine if users look too long at the display to operate WakeUp (thereby taking their eyes off the road) Test Setup There were two people involved in this test, a facilitator and a user. The test was captured by video recording software. The facilitator directed the user to sit in front of a laptop running the dash display interactive demo. 19 P a g e

20 Evaluation: Dash Display Script Moderator: Let s imagine that you re driving late at night. You worry that you may get sleepy and want to check to make sure your WakeUp system is working. Please check the status of your WakeUp system. Expected Response: User clicks on the WakeUp app from Home Screen and hears a voice stating that it s active and/or reads the system status. Action: After the user navigates to the System Status Screen, the moderator would imitate the system voice and say The system is active. Monitoring eyes, facial movements and driving behavior. Moderator: Let s now pretend that you have gotten sleepy. Action: Moderator clicks the red Click for Demo button. Moderator, please encourage user to yawn or nod their head until the alert screen appears. Action: Moderator, imitate the system voice and say, (User s Name), you are (whatever action the user was doing). Are you drowsy? Expected Response: Yes. Action: Moderator, imitate the system voice and say, I will help you get to your destination safely. Would you like to find a place to take a quick nap? Moderator: Pretend that you are fully awake now and don t want the voice alert s help. Turn off the voice alert. Expected Response: User says Deactivate or presses the Deactivate button. Action: Moderator, imitate system voice and say, Voice alert deactivated. 20 P a g e

21 Evaluation Results Mobile App 1. The user did not understand when to activate the monitoring system. They logged in and even though they saw the button labeled Activate Alarm System they didn t think to start the system until they were feeling drowsy. 2. The user did not understand that they were expected to start the system at the beginning of her drive. 3. The user did not understand that they were supposed to shake the device to stop the sound. The alarm effectively woke them up but they did not read the prompts instructing them to shake their phone to confirm that they had been woken up. 4. The user did not understand why they needed a login. 5. User seemed startled by the alarm. When asked about it later they said that they were expecting something else. User said this alarm sounded like a hurricane warning system. 6. The user stated that they liked that the alarm was immediately followed by a person speaking directly to them. 21 P a g e

22 22 P a g e

23 23 P a g e

24 Evaluation Results In-Car Display 1. The user understood the system status, but was unclear if they had to do anything before the system was activated--such as input desired settings. 2. User appreciated the fact that they could be directed to a nearby coffee shop or hotel to take a breather. They thought this was helpful because they wouldn t have to stop and enter in a location manually. 3. The user thought having a button to disable the in-car system wasn t the best option because of the driver being distracted from the road. Should just have the voice confirmation. 4. The user liked the sound of the alert system, appreciated the voice and believed it was efficient at waking them up. 24 P a g e

25 Prototype Revisions Mobile App For the updated mobile application, we implemented many of the recommendations we found from the testing session. We simplified the home screen and removed the sign in option. Now, the user just has to select the WakeUp icon located on the bottom of the screen in order to activate the monitoring system. For the alarm itself, we got rid of the alarm sound and replaced it with a voice that states the user s name and tells them to wake up. The removal of the alarm will ensure that the user does not get startled by the sound upon waking, for this could be a potential safety hazard. Initial Mobile Prototype Updated Prototype 25 P a g e

26 Prototype Revisions In-Car Display For the updated in car display version, we took the recommendation of stripping down the status screen. We removed any clutter and had a green button which contained the word enabled. This button will signify that the WakeUp app is monitoring the user. We also removed the deactivation option and, like the mobile version, we replaced the loud alarm sound with a voice prompt that will alert up the user. Initial In-Car Display Prototype Updated Prototype 26 P a g e

27 Hi-Fi Storyboard & Prototypes After completing our revisions based on our tests, we edited the visual design of our mid-fi prototypes to produce our final hi-fi prototypes. Since the prototypes can be difficult to understand without narration, we also created a storyboard to describe how WakeUp functions. 27 P a g e

28 Storyboard 28 P a g e

29 29 P a g e

30 30 P a g e

31 31 P a g e

32 32 P a g e

33 Phone App Imagine that you are traveling. You just stepped into your rental car. You re jetlagged and are worried you may get sleepy before you reach your destination. You place your phone in a dashboard cradle and access the WakeUp app. Click Here to Access a Demo of the Phone App 33 P a g e

34 Dash Display Imagine that you just stepped into your car to drive home. It s late at night and you re worried you may get sleepy before you get there. You access the WakeUp app from your car s dashboard. Click Here to Access a Demo of the Dash Display App 34 P a g e

35 Marketing Materials Finally we developed a brochure to market WakeUp. 35 P a g e

36 36 P a g e

37 37 P a g e

38 38 P a g e Click here to follow the online portfolio for WakeUp.