CS 522 HumanComputer Interaction HCI Design Establishing User
CS 522: Human-Computer Interaction HCI Design Establishing User Requirements Dr. Debaleena Chattopadhyay Department of Computer Science debchatt@uic. edu debaleena. com
Course Information: CS 522
Overview of HCI Design Chapter Topics 1. Introduction 2. Organizational Support for Design 3. The Design Process 4. Design Frameworks 5. Design Methods 6. Design Tools, Practices, and Patterns 7. Social Impact Analysis 8. Legal Issues
Approach toward Design • Design is inherently creative and unpredictable. Interactive system designers must blend knowledge of technical feasibility with a mystical esthetic sense of what attracts users. • Form follows function. • Put user needs first, not technological functionalities. • Usability engineering has evolved into a recognized discipline with maturing practices and a growing set of standards
UX – User Experience • Usability engineers and user-interface architects, sometimes called the user experience (UX) team are gaining experience in organizational change • The Usability Experience Professionals Association (UXPA) holds annual meetings called the “World Usability Day”
Design Process An iterative design process would consist of four distinct phases
Design Process (continued) • Envision an idea – conceptualize • Establish user requirements • High-level design – a preliminary stage, where the high-level design or architecture of the interactive system is derived. Use sketching, paper mockups, and high-fidelity prototypes • Detailed design –a detailed stage, where the specifics of each interaction is planned out. • Build prototype. • Evaluate.
Conceptualize An example of personalized health summary delivered to hospitalized patients via smartphones. Reference: Acharya, S. , Di Eugenio, B. , Boyd, A. D. , Lopez, K. D. , Cameron, R. , & Keenan, G. M. (2016, September). Generating summaries of hospitalizations: A new metric to assess the complexity of medical terms and their definitions. In The 9 th International Natural Language Generation conference (p. 26).
Conceptualize (continued) An example of data-driven ecological research for three types of users. Reference: Li, J. , Brugere, I. , Ziebart, B. , Berger-Wolf, T. , Crofoot, M. , & Farine, D. (2015, April). Social information improves location prediction in the wild. In AAAI Workshop.
Conceptualize Exercise (5 minutes) • Think of a very technical project you have done in the past. • Now think of a relevant HCC system you want to build using that tech. Describe the concept briefly.
Notes on Establishing Requirements • Requirements engineering is founded on the awareness of a variety of stakeholders relevant to the design process • Stakeholders represent all those who are affected by or have an interest in the product in all its ramifications.
Requirement Elicitation • Problem-driven inquiry, conceptualization at hand • Interviews to users to qualitatively explore issues of relevant activity, emerging problems and expectations • Surveys (for large sample) to gather quantitative results on detailed items • Ethnographic approach (Observation) • Exploratory workshops and use of technology probes. • Scenario development and storyboarding/ personas
Persona Creation • Who are your typical users? • What are the representative aspects of each type of users? • Example: Imagine you will be redesigning the AT&T website. Who are your typical users?
Persona Professional User: Steve Spellman Age: 34 Professional: senior HR manager Service Subscription: wireless (one i. Phone, one blackberry) User Goal: Constantly informed or recommended about AT&T’s new features and services that are customizable to his own profile Make efficient AT&T service upgrades/change and can easily get started on these newly added
Persona (continued) Family User: Jennifer Minnelli Age: 41 Professional: Reference librarian, mom to two children Service Subscription : Home phone, digital TV, internet User Goal: Easily manage various AT&T bills, including those of the family members’ Comprehensible and effective troubleshooting
Persona (continued) Student User: Jennifer Minnelli Age: 23 Professional: Graduate student of Art History Service Subscription: U-Verse Internet (shared with roommates), wireless User Goal: Easily compare different service plans and learn about their features through personalized suggestions related to her situation(budget, constraints) Get special offer information to save
User Interview – for requirement elicitation Do’s and Don’ts.
• General attitude of interviewer: – YES: Learning, understanding, identifying, discovering, unveiling, clarifying (= open to change) – NO: confirming, demonstrating, re-assuring, achieving consensus, discussing opinions (= closed to change) • Key test of a good requirements interview: – What are the 3 -4 key things that you have learned (that you did not know before)? • Focus your questions on the experience – Not projection, prediction, extrapolation, “thoughts” – NO: Is this a useful application? – YES: Is this application valuable to the work you do right now? How? Why?
• Focus on immediate experience – Capture current behavior – NO: Is this product <interesting> for you? – YES: If it were available right now, would you use it? Why? How? • Non-judgmental attitude – Do not convey in any way that you are expecting a certain answer… – NO: Don’t you think this feature would be better if available also as a i. Pad application? – YES: Is there any other way you’d like to use a feature like this in your current work? How? Why?
• Keep each question focused on a single topic – Avoid using AND / OR in your questions (linking more statements together) – NO: How would you use this app at school or at work, for example? – YES: • How would you use this app at school? • How would you use this app at work? • Provide a way out from your options • Even in close-ended questions, give the possibility of expressing things outside the available options – NO: which of the following feature is most important to you? [what if no one is important? ] – YES: Rate from 1 to 5 how important each feature is for you, where 1 is least important, 5 is most important. Put 0 if a feature is irrelevant for you.
• Avoid binary questions – – Do not force black/white commitments on the “whole” Elicit “analytical” feedback on specific elements NO: Is this product useful? YES: What, if anything, do you find useful about this product? Why?
Requirements Specification - Abstraction • Purpose: The requirements analysis must produce a readable and clear, documented SET of requirements that informs the design activity • Focus: Requirements should be expressed at a level of detail which is appropriate for leaving room for alternative design exploration (within the frame established by the requirements) • NO: user sees a pop-up asking to register, he enters user name and password, click on submit and the pop-up close, showing a page with the top navigation bar and in the center a dashboard with all the personalized information displayed in a grid metaphor…. • YES: – User access the personal app upon authentication – A personalized dashboard displays high-priority tasks – Dashboard layout follow common patterns of…
Design Frameworks • User-centered design (UCD) – Takes the needs, wants, and limitations of the actual end users into account during each phase of the design process • Participatory design (PD) – Direct involvement of people in the collaborative design of the things and technologies they use • Agile interaction design – Development methods for self-organizing, dynamic teams and that facilitate flexible, adaptive, and rapid development that is robust to changing requirements and needs
Design Methods • • Illustration of how the solutions considered during a design process will grow (diverge) and shrink (converge) iteratively until it eventually fixates on a single point, the finished product This particular design process involves three iterations, but real processes may have more or fewer iterations. 4 -24
Project proposal • ~10 minute presentation – one/two group members may present • Sign-up using the Google Doc • Deliverable – ~2 -page document
Project proposal (continued) • What to present and write up? – – Conceptualization of the idea – a vision diagram. Primary and secondary users Initial user requirements Some literature review on the HCI topic (may not be exhaustive). – Next steps, i. e. a plan of the design process, how do you plan to gather user requirements, what kind of design framework you foresee using, and what evaluation methods? (This is all tentative and may change in future, but you need to have a plan and a rationale. )
To do: • CITI IRB training – DUE Sep 5, 11: 59 pm CST • Readings: Proctor & Zandt, 2008. Human Factors in Simple and Complex Systems. Chapters 3 (Reliability and Human Error in Systems) and 4 (Human Information Processing). pp. 53— 107. • Start working on your project proposals – DUE week 4
Further References • M. Kuniavski, Observing the User Experience, Morgan Kauffmann 2002, (Chapter 6). • Cockburn, A. , Writing Effective Use Cases, Addison-Wesley, 2000. • Carroll, J. M. , Making Use. Scenario-based Design of Human. Computer Interactions, MIT Press, 2000. • Bolchini, D. , Paolini, P. , Goal-Driven Requirements Analysis for Hypermedia-intensive Web Applications, Requirements Engineering Journal, Springer, RE 03 Special Issue (9) 2004, 85 -103. • Hackos, Jo. Ann T. and Redish, Janice C. (1998). User and Task Analysis for Interface Design. Wiley.
- Slides: 28