Usability and Human Factors Approaches to Design Lecture

Usability and Human Factors Approaches to Design Lecture b This material (Comp 15 Unit 8) was developed by Columbia University, funded by the Department of Health and Human Services, Office of the National Coordinator for Health Information Technology under Award Number 1 U 24 OC 000003. This material was updated by The University of Texas Health Science Center at Houston under Award Number 90 WT 0006. This work is licensed under the Creative Commons Attribution-Non. Commercial-Share. Alike 4. 0 International License. To view a copy of this license, visit http: //creativecommons. org/licenses/by-nc-sa/4. 0/.

Approaches to Design Lecture b – Learning Objectives • Describe requirements analysis and cognitive task analysis (Lecture b) • Characterize the role of prototypes in design (Lecture b) • Describe the principles of participatory design (Lecture b) • Explain the difference between low fidelity and high fidelity prototypes (Lecture b) • When it would be appropriate to use one versus the other (Lecture b) 2

Needs and Requirements • Definition of requirements: – An explanation of what the system should “be” or should “do” – Documentation of “needs” in order to communicate between everyone involved in system development – A set of goals that define objectives for design • What are we trying to achieve? – Identifying needs so that the system can support the user’s goals. – Produce a set of stable requirements that can be moved forward into the design activity 3

Why Do We Need Requirements? • To make communication clear, unambiguous and specific on system “needs” • To identify potential mismatch between user needs and designers’ understanding • To reduce the time and costs involved in developing a system • To evaluate the functions of a system during testing 4

Task Descriptions • Scenarios – “Stories” • Use Cases – Focus on user-system interactions • Essential Use Cases – Abstractions from scenarios – User intention vs. System responsibility Usability. gov 5

Cognitive Task Analysis • Tools and techniques for describing knowledge and strategies required for task performance – Hierarchical decomposition of goals and component tasks • Objective: Yield information about the knowledge, thought processes, and goal structures that underlie observable task performance – Models of competent performance 6

Task Analysis: ATM Machines • • Goal: Obtain Cash from machine IF ATM is available THEN insert card in appropriate slot IF Card is accepted by Machine THEN enter PIN code IF you cannot remember PIN THEN Retrieve slip of paper with number • IF Machine prompts you for an action THEN Indicate that you wish to withdraw cash • IF “Withdraw Cash” button/icon is visible THEN press button/icon • IF “Withdraw Cash” button/icon is not visible THEN locate button/icon 7

A Partial Walkthrough: ATM Goal: Obtain $80 Cash from Checking Account 1. Action: Enter Card (Screen 1) System response: Enter PIN > (Screen 2) 2. Sub-goal: Interpret prompt and provide input 3 & 4. Actions: Enter “Pin” on Numeric keypad and Hit Enter (press lower white button next to screen) System response: “Do you want a printed transaction record”. Binary Option: Yes or No (Screen 3) 5. Sub-goal: Decide whether a printed record is necessary 8

A Partial Walkthrough: ATM (Cont’d – 1) Goal: Obtain $80 Cash from Checking Account, continued 6. Action: Press Button Next to No Response System response: Select Transaction-8 Choices (Screen 4) 7. Sub-goal: Choose Between Quick Cash and Cash Withdrawal 8. Action: Press Button Next to Cash Withdrawal System response: Select Account (Screen 5) 9. Action: Press Button Next to Checking System response: Enter Dollar Amounts in Multiples of 20 (Screen 6) 10 & 11. Action(s): Enter $80 on Numeric Key Pad and Select Correct 9

Prototypes • Artifact used to facilitate team communication • Test novel ideas • Central to all design disciplines • Answer questions and support designers in choosing between alternatives – Clarify requirements 10

Low Fidelity Prototyping • • • Storyboards, Sketching Fast and cheap User participation Throw away Hard to convey flow Harder to convert to code and specifications 11

IDEATel Launchpad Starren, J. , Hripcsak, G. , Sengupta, S. , Abbruscato, C. R. , Knudson, P. E. , et. Al. (2002) 12

IDEATel Launchpad Mockup Starren, J. , Hripcsak, G. , Sengupta, S. , Abbruscato, C. R. , Knudson, P. E. , et. Al. (2002) 13

High Fidelity Mockup Kaufman, D. R. , Cronin, P. , Rozenblit, L. , Voccola, D. , Horton, A. , et. Al. (2011). 14

Measure Selector Mockup • Selector is tool designed for scientists involved in autism research • High fidelity mockup assembled with a diagramming/visualization tool • Interface approximates final design – Functionally partitions the screen – Anticipates structure of user interaction/dialogue • Based on prior usability testing and requirements analysis (Affairs, 2016) 15

PICTIVE Output Kaufman, D. (2012). 16

High Fidelity Prototyping • • Functional, Interactive “Living specification” Expensive and slow Throw-away vs. Evolutionary 17

Low versus High Fidelity Type Advantages Low Fidelity • • • High Fidelity • • Disadvantages Low cost Evaluate multiple design costs Communication Screen layout issues Proof-of-Concept • More complete functionality Fully interactive Clearly defined navigational schemes Look and feel of final product • 1. 1 Table: Preece, et al. (2007). • • • Poor detailed specs Limited utility beyond requirements Navigational and flow limitations Expensive Time-consuming Inefficient for proof of design Not effective for requirements gathering 18

Participatory Design • Approach to design actively involve and continuously engage all stakeholders – Not just end-users • Focuses on processes and procedures • Embraces a philosophy of empowerment and democratization – Core set of principles 19

Participatory Design Principles • Every stakeholder has a voice regardless of status • Workers are a prime source of innovation • Systems are networks of people, practices, and technology embedded in particular organizational contexts • Find concrete ways to improve the working lives of co-participants – reducing tedium associated with work tasks – designing new opportunities for exercising creativity – increasing worker control over work content 20

A Case Study in Participatory Design: Children’s Contributions in Designing a Communication Tool for Children with Cancer • Ruland CM, Starren J, Vatne TM. Participatory design with children in the development of a support system for patient-centered care in pediatric oncology. J Biomed Inform. 2007 Nov 13; – Center for Shared Decision Making and Nursing Research, Rikshospitalet Medical Center Oslo, Norway – Department of Biomedical Informatics, Columbia University, NY • Funding: Norwegian Research Council 21

SISOM • A communication tool to: • Help children with cancer communicate their symptoms and problems – give them a “voice” • Improve communication between the child, parents and health care providers • Assist health care providers in individually tailored patient care 22

Design Challenges • • • Developmental factors Valid data capturing Seriously ill children as primary users Limited verbal skills Adjustment to clinical context and different users 23

Children’s Contributions • • Graphical user interface Understandable child-friendly terms Iconic and graphical representations Usability 24

Design Techniques • • • Scenarios Brainstorming, drawing, building feedback Low – tech prototyping Observation Evaluation of ideas Videotaping 25

Design Session Ruland , C. M. , Starren, J. , Vatne T. M. (2008). 26

How to Decide Which Ideas To Use • • • Evaluation of ideas based on: System requirements Usability criteria (Nielsen) Usability heuristics Interface guidelines 27

Island Ruland, C. M. , Starren, J. , Vatne, T. M. (2008). 28

My Body Ruland, C. M. , Starren, J. , Vatne, T. M. (2008). 29

Pain and Discomfort Ruland, C. M. , Starren, J. , Vatne, T. M. (2008). 30

Conclusions from Design Study • Many creative suggestions that the design team would not have thought of • Difficulty to stick to specifications – play mode • Importance of role play • Mixture between children’s ideas and experts knowledge 31

Approaches to Design Summary – Lecture b • • Characterized requirements analysis Demonstrated a cognitive task analysis Characterize the role of prototypes in design Explain the difference between low fidelity and high fidelity prototypes – When it would be appropriate to use one versus the other • Provided a detailed case study of participatory design • Up next: design principles to support usability and a focus on Nielsen’s heuristics and their role in design 32

Approaches to Design References – Lecture b References 1. Kaufman, D. R. , Pevzner, J, Hilliman, C. , Weinstock, R. S. , Teresi, J. Shea, S. & Starren, J. (2006). Re-designing a telehealth diabetes management program for a digital divide seniors population. Home, Healthcare, Management & Practice. 18: 223 -234. 2. Preece, J. , Rogers, Y. , & Sharp, H. (2007). Interaction Design: Beyond Human-Computer Interaction (2 nd ed. ). West Sussex, England: Wiley. 3. Starren J, Hripcsak G, Sengupta S, Abbruscato CR, Knudson PE, Weinstock RS, Shea S. Columbia University's Informatics for Diabetes and Telemedicine (IDEATel) Project: technical implementation. JAMIA 2002; 9: 25 -36. 4. Kaufman D. R. , Cronin P. , Rozenblit L. , Voccola D. , Horton A. , Shine A. , Johnson S. B. (2011). Facilitating the iterative design of informatics tools to advance the science of autism. Studies in Health Technology and Informatics, 69, 955 -9. 5. Affairs, A. (2016). Use Cases. Usability. gov. Retrieved 14 September 2016, from https: //www. usability. gov/how-to-and-tools/methods/use-cases. html Images Slides 12 &13: Starren, J. , Hripcsak, G. , Sengupta, S. , Abbruscato, C. R. , Knudson, P. E. , Weinstock, R. S. , Shea, S. (2002). Columbia University's Informatics for Diabetes and Telemedicine (IDEATel) Project: technical implementation. JAMIA 2002; 9: 25 -36. Slide 14: Kaufman, D. R. , Cronin, P. , Rozenblit, L. , Voccola, D. , Horton, A. , Shine, A. , Johnson, S. B. (2011). Facilitating the iterative design of informatics tools to advance the science of autism. Studies in Health Technology and Informatics, 69, 955 -9. 33

Approaches to Design References – Lecture b (Cont’d – 1) Images Slide 16: Kaufman, D. (2012). Plastic Interface for Collaborative Technology Initiative through Video Exploration. Department of Biomedical Informatics, Columbia University Medical Center, New York, NY. Slide 26: Ruland, C. M. , Starren, J. , Vatne, T. M. (2008). Participatory design with children in the development of a support system for patient-centered care in pediatric oncology. JBI. 2008; 41(4): 624– 635. Slide 28 -30: Ruland, C. M. , Starren, J. , Vatne, T. M. (2008). Participatory design with children in the development of a support system for patient-centered care in pediatric oncology. JBI. 2008; 41(4): 624– 635 Charts, Table, & Figures 1. 1 Table: Preece, J. , Rogers, Y. , & Sharp, H. (2007). Interaction Design: Beyond Human-Computer Interaction (2 nd ed. ). West Sussex, England: Wiley. 34

Usability and Human Factors Approaches to Design Lecture b This material was developed by Columbia University, funded by the Department of Health and Human Services, Office of the National Coordinator for Health Information Technology under Award Number 1 U 24 OC 000003. This material was updated by The University of Texas Health Science Center at Houston under Award Number 90 WT 0006. 35