1. Welcome! 1.Project Description 2.Scope and Approach 3.Prototype 4.Final Evaluation 5.Summary 6.Closing Comments Overview Team Cree Vilia Ingriany Alvin Lau Christopher Hanno Karen Chyn Gerri Benrizani

2. Translink Website Project Trip planning and scheduling for metro Vancouver area residents Goal What the website does Improving Translink website with regards to other transit scheduling system Why Translink? - Too many steps BUT + Has complete resources of the local transit systems Hence Need a more usable interface Problems Hence - Poor error checking - Hidden Controls

3. Scope & Approach Feature Scope  Trip Planner  Next Bus Schedule  Real-Time Schedule Most important functions Parts that users mainly use. Trip Planner & Next-Bus (Improvements on existing features) Real-Time Bus (New Feature) Focus on regular local commuters User-centered design process Approach Reduced steps More visible controls Integrate Google Map On the run planning Accurate schedule Why these?

4. Medium-Fidelity Prototype Compare to other systems Nextbus.com Transitdb.com Google Map Transit Focus on regular users Assumption : Real-time bus location Use Translink exclusive information Fare information Bike and wheelchair access How did we get here? Proposal Support 3 types of users Focus entirely on Translink Analysis Can only focus on 1 type of user Consider other systems Key Focus

6. Old VS New

7. OLD NEW Detailed Walking direction Bike/Disability access icons Fare information More accessible map Route Alerts Trip Planner Result IMPROVEMENTS STEP 1 STEP 2 STEP 3

8. Real-Time Bus Next Bus Get bus schedule Same function as the current website Real Time Bus (New Feature !) Real-Time Result Page actual time for the next three bus inspired by nextbus.com Result Page

9. Prototype Evaluation Result Think-Aloud Observation Semi-Structured Interview Prototype more useful than old interface Better usability, better performance More effective approach to get information Evaluation Method What did the users think?

10. In 13 Weeks … Goal Improving Translink website with regards to other transit scheduling system Problems to address - Poor error preventions - Too many steps - Hidden Controls Interview & Observation Medium-Fidelity Prototype

11. Closing Comments Future Design Recommendations Implement Google API for search and map Consider other existing scheduling systems to be integrated Use more understandable language Last words… Learning about methods employed in interface design process Proud of our prototype See you in CS444!

12. THANK YOU