230 likes | 415 Views
Evaluating and Suggesting Improvements to PEBL User Interface. Yin Yin Tan . Outlines. Motivation PEBL Introduction Heuristic Principles PEBL UI Survey Data Analysis Suggestions & Conclusion. Motivation.
E N D
Evaluating and Suggesting Improvements to PEBL User Interface Yin Yin Tan
Outlines • Motivation • PEBL Introduction • Heuristic Principles • PEBL UI Survey • Data Analysis • Suggestions & Conclusion
Motivation • Evaluating User Interface (UI) can be potentially beneficial to both designers and users as it centers on the problems UI designers might not be aware of. • Experimental psychology is one of the leading trends in the study of psychology. • Among all the free experimental, psychological software, PEBL has the most predesigned experiments for people to use. • There is no app for Android as a platform for psychological experimenting (Strasburger, 2014).
Psychology Experiment Building Language (PEBL) PEBL (Mueller, 2013) is open-source free psychological software. Users can program and design their won experiments. Users can use already built-in tests to conduct experiments. Wide range of experiments in the area of neuropsychology, cognition, and clinical psychology.
PEBL Predesigned Cognitive Decathlon Object Judgment Test Visual Search Test Trail-Making Test Traveling Salesman Problem Bechara’sGambling Task Compensator Tracking Aimed Movement Test Device MinicryTask
Heuristic Usability Principles for PEBL UI • Easy Functionality • Information Availability • User Control & Freedom • Visibility of System Status • Consistency & Standards • Error Recovery • Minimalist Design • Aesthetic Design • Pleasurable Interaction • Help & Documentation • Potential Expansion
Questionnaire for PEBL Usability Test • Demographic data: gender, age race, & major • What kind of user are you? 1) a designer of a PEBL experiment, 2) an experimenter of a PEBL experiment, 3) a participant of a PEBL experiment, 4) all above, 5) both experimenter and participant • The links of PEBL User Interface should take users where they want to go. Menu choices, Icon labels should be readable, logical, and mutually exclusive. Regarding "Easy Functionality", how do you think of PEBL Interface? 1) very difficult to function, 2) difficult to function, 3) neutral, 4) easy to function, 5) very easy to function • The User Interface should be designed to convey 'just enough' meaningful information to facilitate the data collection. Regarding "Information Availability", How do you think of PEBL?“ 1) minimal information, 2) not enough information, 3) neutral, 4) enough information, 5) too much information • Regarding "User Control & Freedom", how do you think of PEBL? 1) minimal, 2) not enough, 3) neutral, 4) enough, 5) too much information • The system should always keep users informed about what is going on and what to expect next in a reasonable time. Regarding "Visibility of System Status", How do you think of PEBL? 1) not at all visible, 2) not so visible, 3) neutral, 4) visible, 5) very visible • The content and terminology should be standardized and consistent on PEBL. The transition from one view to another should be easily perceptible. Regarding "Consistency & Standards", How do you think of PEBL? • If an error occurs, the app should recover from it very quickly and give users correct direction information. Regarding "Error Recovery", How do you think of PEBL? 1) not at all helpful, 2) not so helpful, 3) neutral, 4) helpful, 5) very helpful • The user interface design should be succinct and simple. Regarding "Minimalist Design", How do you think of PEBL? 1) very bad, 2) bad, 3) neutral, 4) good, 5) very good • They user interface should be artistic and beautiful. Regarding "Aesthetic Design", How do you think of PEBL? 1) very bad, 2) bad, 3) neutral, 4) good, 5) very good • Regarding "Pleasurable Interaction", How do you think of PEBL? 1) very bad, 2) bad, 3) neutral, 4) good, 5) very good • The documentation should be goal-oriented and the help document should link users to the exactly right place to solve problems. Regarding "Help & Documentation", How do you think of PEBL? 1) very bad, 2) bad, 3) neutral, 4) good, 5) very good • Regarding "Security of Use", How secure do you feel when using PEBL? 1) not at all secure, 2) not so secure, 3) neutral, 4) secure, 5) very secure • Regarding "Potential Expansion", Do you like to see PEBL as an app? 1) no, 2) maybe not, 3) I don't care, 4) maybe), 5) of course yes • Would you use PEBL outside of the class/experiment in the future? 1) not at all, 2) maybe not, 3) I don't know, 4) maybe, 5) of course yes • Do you think using PEBL to learn these paired countries is better than traditional textbook? 1) no, 2) maybe not, 3) I don’t care, 4) maybe, 5) of course yes • Comments or feedback on your experience of PEBL User Interface.
Experimental Researchers Experimenters Programmers Participants The Public Designers PEBL Users Analysis Data Analysis Potential App Users PEBL & PEBL UI Inexperienced Users Novices Experienced Users Experts
Survey Results • Positive results: • easy functionality • information availability • visibility of system status • consistency & standards • minimalist design • pleasurable interaction • help & documentation • security of use • potential expansion • Improvement Needed: • user control & freedom • error recovery • aesthetic design
Gender Difference on PEBL Potential Experimenters Participants Experimenters Experimenters Participants Participants
Written Comments From Participants • The icon looks bad and plastic • The UI is old fashioned, not aesthetic • PEBL should work on web browsers • PEBL is not as friendly as commercial • Not sure whether we can control more variables in the task • Everything is on one screen • It is better than Python in terms of programming • Easy to use
Informal Interview with Dr. Mueller (PEBL Designer) 2 big improvements in the newly revised PEBL 0.13 Modify parameters in PEBL UI Randomize the sequence of experiments My impression he does care what users think about PEBL and wants to take actions to improve it. Modify Parameters Randomize Tasks
Suggestion 3: Information Availability ~ Just Enough InfoHarrison, Kurtenbach, & Vicente (1995)
Suggestions & Conclusions • Suggestions: • Provide customization of UI to caster users’ need (Burkolteret al, 2014). • Implement bubble coding to enhance error recovery(Bragdonet al, 2010). • Give users options on the design/modification of experiments, such as PsychoPy with both builder view and coder view (PsychoPy, 2014). • Further help analyze the data collected via programming some functions for simple graphs and tables in the codes of an experiment. • Conclusion: • PEBL can provide versatile and valid tests for researchers to measure participants’ performance. • Designing some interesting PEBL tests into an app is feasible.