1. Graphing Calculator Final Project Barbara Eikov Kris Lee

2. Overview Problem Space Problem Space Usability Goals Usability Goals User Experience Goals User Experience Goals Persona Persona User Needs/Expectations User Needs/Expectations Possible Designs/Evaluation of Designs Possible Designs/Evaluation of Designs Final Prototype/Final Evaluation Final Prototype/Final Evaluation

3. Problem Space We wanted to create a calculator the performs basic and advanced mathematics We wanted to create a calculator the performs basic and advanced mathematics Some people cannot afford a calculator that can perform advanced mathematics Some people cannot afford a calculator that can perform advanced mathematics The Windows Calculator is not good enough The Windows Calculator is not good enough

4. Usability Goals/User Experience Goals Usability:  Efficient to use  Easy to Learn  Easy to remember how to use User Experience:  Helpful  Engaging  Fun

5. Primary Persona Name: Pablo Vasquez Name: Pablo Vasquez Age: 19 Age: 19 Occupation: Student at Clarkson Occupation: Student at Clarkson Salary: Not enough to afford to go to Clarkson Salary: Not enough to afford to go to Clarkson Likes: Playing video games, watching movies, music, ramen noodles Likes: Playing video games, watching movies, music, ramen noodles Dislikes: Homework, rainy days, when his girlfriend left him for his sister Dislikes: Homework, rainy days, when his girlfriend left him for his sister

6. Secondary Persona Name: Kevin Dempsey Name: Kevin Dempsey Age: N/A Age: N/A Occupation: Math Professor at Clarkson Occupation: Math Professor at Clarkson Likes: Complex Analysis, ERC dates with his twin brother Likes: Complex Analysis, ERC dates with his twin brother Dislikes: Lazy students, bad math Dislikes: Lazy students, bad math

7. User Needs/Expectations User needs: Perform basic math operations Perform basic math operations Graph equations Graph equations Customizable Customizable User expectations: Perform higher math: derivatives, limits, and statistics Perform higher math: derivatives, limits, and statistics Does not crash Does not crash Easy to use Easy to use

8. Design 1 User Likes: Familiar design Familiar design Naming scheme corresponds to a typical calculator Naming scheme corresponds to a typical calculator Not cluttered Not cluttered User Dislikes: Need to press a lot of buttons for the most basic needs. Need to press a lot of buttons for the most basic needs. Menus might be confusing as to where to find functions. Menus might be confusing as to where to find functions. No customizability. No customizability. A lot of button pushing A lot of button pushing

9. Design 2 User Likes: No clutter No clutter Buttons on the left are customizable Buttons on the left are customizable Can type in expressions with keyboard Can type in expressions with keyboard User Dislikes: Not a conventional calculator style Not a conventional calculator style A lot of menus-might be hard to find what you need A lot of menus-might be hard to find what you need

10. Design 3 User Dislikes: Initial setup of wanted design may be difficult Initial setup of wanted design may be difficult Only three customizable options at a time Only three customizable options at a time A lot of button pushing when the keyboard could be used to type regular expressions A lot of button pushing when the keyboard could be used to type regular expressions Cluttered when user wants a lot of functionality Cluttered when user wants a lot of functionality User Likes: Very simple structure for the most basic users Customizable Eliminates the need to trace through a lot of menus

11. User Data  We conducted an interview and asked the user three questions:  What do you like about this design?  What do you not like about this design?  Do you have any suggestions?  A total of 21 people were interviewed, 14 in class and 7 out of class

12. User Data  Resulting metric:

13. User Data  From the users feedback and our metric we have decided to implement Design 2  We’ve modified our design to include a drop down menu with possible functions  We will be using Visual Basic to make our prototype

14. Prototype

15. Final Evaluation Surveyed/Interviewed 12 students at Clarkson of different majors Surveyed/Interviewed 12 students at Clarkson of different majors Results: Results: Students felt the categories for the functions were goodStudents felt the categories for the functions were good Students completed a task faster the second time they asked to complete itStudents completed a task faster the second time they asked to complete it Students were able to stay focused on all the required tasksStudents were able to stay focused on all the required tasks

16. Conclusion Problem Space Problem Space Usability Goals Usability Goals User Experience Goals User Experience Goals Persona Persona User Needs/Expectations User Needs/Expectations Possible Designs/Evaluation of Designs Possible Designs/Evaluation of Designs Final Prototype/Final Evaluation Final Prototype/Final Evaluation

17. Questions?