Test 2 Lectures

Source

Lessons 2.7 through 2.10

Design principles in general give us some great rules of thumb to use when creating our initial prototypes and designs.

• 2.7 - Task Analysis

  • Task analysis allows us to describe those needs,
    • those tasks in formal ways to equip the interface design process, and cognitive load lets us keep in mind how much users are asked to do at a time.
  • 2.7.7 - 5 Tips: Developing GOMS Models
  • 2.7.5 - Strengths and Weaknesses of GOMS
  • 2.7.8 - GOMS to Cognitive Task Analysis
  • 2.7.13 - Cognitive Task Analysis Strengths and Weaknesses
• Mental models provide us an understanding of how the design alternatives might mesh with the user’s understanding of the task.
• 2.8 - Distributed Cognition
  • Distributed cognition gives us a view on interface design that lends itself to design at a larger level of granularity.
  • Week 8 Readings
  • models or theories, of the context surrounding ACI
    • 2.8.2 - Distributed Cognition
      • 2.8.4 - How a Cockpit Remembers Its Speeds
      • 2.8.7 - Distributed Cognition as a Lens
  • Other Theories
    • 2.8.10 - Social Cognition
      • how social connections create systems that can, together, accomplish tasks
    • 2.8.12 - Situated Action
      • humans as improvisers
      • like distributed cognition, but
        • not interested in the long-term and enduring permanent interactions
      • Memory: recognition is easier than recall
    • 2.8.15 - Activity Theory
      • interaction between various pieces of an activity
      • very complex, predates HCI (HCI comes from it)
      • Three main contributions of Activity Theory
        1. Zooms out to activity (general) instead of task (specific). More abstract.
        2. Zooms out from low level operators to general user needs
        3. user actions can go higher or lower level on the hierarchy
• 2.9 Interfaces and Politics
  • 2.9.9 - Value-Sensitive Design
    • Stakeholders (direct/indirect)
  • 2.9.13 - Exploring HCI: Interfaces and Politics
    • Social Effects
• 2.10 Conclusion to Principles
  • Human as:
    • Processor, Predictor, and Participant

Lessons 3.5 through 3.8

• 3.5 - 3.5 Prototyping
  • Verbal, Paper, Wizard of Oz, Wireframing, Physical, Multi-Level

• 3.6 - Evaluation

  • 3.6.2 - Three Types of Evaluation
    1. 3.6.7 - Qualitative Evaluation
    2. 3.6.11 - Empirical Evaluation
       • 3.6.13 - Hypothesis Testing
    3. 3.6.18 - Predictive Evaluation
       • 3.6.20 - Cognitive Walkthroughs
  • 3.6.22 - Exercise: Evaluation Pros and Cons Solution

• 3.7 - HCI and Agile Development

  • 3.7.3 - Exercise: When to Go Agile Solution
    • Good candidates for Agile: use existing devices and don’t have high stakes associated with them.
  • 3.7.4 - When to Go Agile
    • Boehm and Turner
      • environment with low criticality
      • frequently changing requirements
  • 3.7.5 - Paper Spotlight: Towards a Framework for Integrating Agile Development and User-Centred Design
    • Stephanie Chamberlain, Helen Sharp, and Neil Maiden
      • User-centered design:
        • At a minimum, user-centered design advocates involving users throughout the process through surveys, and interviews, and evaluations, and more things that we’ve already talked about.
        • high user involvement and close team collab
        • How feasible would it be to actually execute,
        • what would you need?
        • What users do you need?
          • How many?
          • When do you need them?
      • 3.8.8 - Approaches to User-Centered Design
        • Participatory design
          • all stakeholders are involved in design (not just source of data)
          • can be too focused on design team perspective
        • Action Research
          • done by the actual users
          • focuses more on others than participatory design
        • design-based research
          • can be done by outside practitioners (unlike action research)
  • Testing:
    • Live prototyping,
    • AB
  • 3.7.9 - 5 Tips: Mitigating Risk in HCI and Agile Development
• 3.8 - Conclusion to Methods
  • Designing audiobooks for exercisers 1,2,3,4
  • Design cycle
    • iterative process
      • need-finding
      • brainstorming design alts
      • prototyping
      • evaluation with real users
  • Design principles just streamline the design process, not replace it