1 / 17

Today

CS 321 Human-Computer Interaction. Today. Introduction to HCI & Contextual Design. Reading: CD – Ch. 1 BDS – Intro & Ch. 1. Monday. Contextual Inquiry & Intro to Ethnography. Reading: CD – Ch.s 2, 3, 4 “Using Ethnography in Contextual Design”. SMITH, JOHN E. 555326543.

elsie
Télécharger la présentation

Today

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. CS 321 Human-Computer Interaction Today Introduction to HCI & Contextual Design Reading: CD – Ch. 1 BDS – Intro & Ch. 1 Monday • Contextual Inquiry & Intro to Ethnography Reading: CD – Ch.s 2, 3, 4 “Using Ethnography in Contextual Design”

  2. SMITH, JOHN E. 555326543 Why is it so difficult to create a schedule on Student Information System (SIS)?

  3. The System’s Work Model does not fit the User’s Work Model • Any system forces a specific way for tasks to be done • System’s Work Model • Every user has an understanding of how a task should be done • Conceptual Model, Mental Model • For applications like the SIS the system’s model is hard to understand and work with because it makes no sense in terms of the work being done. • Causes errors, non-use

  4. Example: How do people research a topic?

  5. What is Design? • Design is a creative activity of making artifacts that are usable for a specific purpose. • Software Engineer • Software is reliable, robust, and maintainable • Software Designer • Software fits the user’s overall activities, enhances productivity, and produces a satisfying experience (Enjoyable!)

  6. Linkages User’s Task Model vs. Engineer’s Model • User’s task model A representation of the user’s conceptual model • Engineer’s model Underlying implementation Main Goal: Make the Engineer’s model invisible to the user.

  7. From the Interface Hall of Shame The program, Woodworkers Estimate Helper provides a classical example of geekspeak. The program is “designed for woodworkers and cabinet makers”, and purports to assist in the process of calculating price quotes for their projects. Unfortunately the program uses such programming terminology as “Databases”, “Records”, and, if the user attempts to enter a duplicate part name, presents the message “Key Validation Error”. While we do not mean to disparage any woodworkers, we can quite confidently state that the typical woodworker has essentially no practical understanding of such terms, nor should they be required to. Is it any wonder that many new users are intimidated by computers?

  8. System Centered vs.Customer Centered Design • System Centered Design • Focuses on organizing the functionality of the system • Customer Centered Design • Focuses on the customer’s conceptual model • Participatory Design, User-Centered Design, Human-Centered Design

  9. Customer Centered Design Interject the designer in the user’s world and the user in the designer’s world to develop a shared conceptual model

  10. Contextual Design (CD) • Gather data from multiple users Abstract data into a common model Design depends on seeing the implications of the data Design begins with a creative leap from customer data to implications for design and from implications to ideas for specific features

  11. Steps in Contextual Design • Contextual Inquiry • Work Modeling • Consolidation • Work Redesign • User Environment Design • Interface Design and Prototyping

  12. Step 1 - Contextual Inquiry Click movie to play • Gather Data • Observation • Interview • Participation • “Shadowing” • Learn User’s Vocabulary • Gather Artifacts • Gain an understanding of the user

  13. Step 2 – Work Modeling • Concrete Representations • User’s activities • Context of the work • Team Interpretation Sessions • Shared understanding

  14. Step 3 - Consolidation • Look across multiple users • Common practices • Divergent practices • Inductive Process • Going from a few to a large population

  15. Step 4 – Work Redesign • Don’t just automate • Look for places to improve • Visioning • Brainstorming sessions • Creative process

  16. Step 5 – User Environment Design • Explicit representation of the system work model • “Blue Print” for the User Interface Design

  17. Step 6 – Interface Design & Prototyping • Paper Prototyping • Lo-fidelity prototype • Communicate design with the user

More Related