1. Project 4: User interface for logging food intake and activities Thanh Le Christine Liang Warren Trinh Muhammad Zaman

2. Project Recap The project focuses on an application that will allow health conscious users to record their daily dietary routines and physical activities into a calendar log, called the diary. The diary will allow users to track their progress and create notes to improve it Our task is to perform usability tests and to find ways to improve the system

3. Project Recap Cont'd Identified Initial Heuristic Issues o Presented to our client and resolved Usability Research Methods: o Two Iterations of Testing  8 Users for First Iteration, 4 Users for Second Iteration o Target Users: Type 2 Diabetics, Health Enthusiasts o 30-40 minutes o Background Questionnaire o Pre-Test Interview o "Think Aloud" Testing o Post-Test Interview

4. Project Recap Cont'd Pre-Test Interview: First impressions of interface "Think Aloud" Testing: o Laptop o Screen capture software o Microphone o Webcam to capture facial expressions o Test Case Scenarios: 1.4 Scenarios, 9 Tasks 2.Always the same set of scenarios for each user Post-Test Interview: System Usability Scale and Follow-Up Questions

5. What We've Done So Far Usability Testing Protocol Submitted To and Approved By Client 5 Usability Tests Performed o 2 Older (>30 years old) Users o 3 Younger (<30 years old) User 3 Usability Tests Scheduled for this Week o 3 Younger Users 4 Users Scheduled for the 2nd Iteration of Testing

6. Insights So Far The terminology is not as easy to understand as we first thought Users use "notes" more often than "add items" when they add meals with items Some users ignore menus in the third column on the right Users cannot see the glucose menu at the bottom Users feel that they need more instruction and guidance before using the website Users prefer more feedback after they perform a task o Pop-up window closes/ cascading window collapses after they enter an entry o Diary refreshes automatically after they enter an entry Navigation is cumbersome o Reviewing past activities or meals for multiple dates requires you to view each day individually

7. Problems The website had a few bugs that hindered some of the testing tasks o Bugs reported to and fixed by our client One of our older users had trouble with the touch pad on the laptop that we did our testing on o Brought a mouse for our other users Problem with the prepaid campus parking pass o User had to buy a parking pass and we reimbursed him Hard to get some of the younger users to look past the fact that the website was still a prototype

8. Decisions to be Made After analyzing the results from the testing: o What we want to change o How we want to design the GUI for the diary CSS schemes. Based on the test results and feedback, more CSS schemes will be designed for the app.

9. Updated Timeline Week 7: Interim Presentation (5/9) Finish First Iteration of Testing (team) Analyze Testing Results (team) Create a GUI prototype (team) Present Results to Client (team) Week 8: Update Website (Client) CSS Schemes (Warren) Week 9: Second Iteration of testing (team) Analyze Testing Results (team) Present Results to Client (team) Week 10: Final Presentation (5/30)