Vocabulary of Design Visibility - –how easily a user can see what can be done and how to do it Mappings - –how a control and object are related –suffers.

Slides:



Advertisements
Similar presentations
Chapter 2, part 3 Human Aspects: Interface Metaphors and Conceptual Models... What is a metaphor? Traditionally, metaphors were used in speech where things.
Advertisements

Chapter 11 Designing the User Interface
Design Project (Last updated: Nov. 22/2010) Change since August 31: added the notes to the presentation in the next slide.
Understanding and conceptualizing interaction. Understanding the problem space –What do you want to create? –What are your assumptions? –Will it achieve.
SECOND MIDTERM REVIEW CS 580 Human Computer Interaction.
May 2, May 2, 2015May 2, 2015May 2, 2015 Azusa, CA Sheldon X. Liang Ph. D. Software Engineering in CS at APU Azusa Pacific University, Azusa, CA.
Interface metaphors & analogies pp pp
The Psychopathology of Everyday Things
Annoy Your Users Less Session 202 Philip Wolfe, Lead Developer Farm Credit Services of America.
From requirements to design
What is Design? Professor: Tapan Parikh TA: Eun Kyoung Choe
Spatial Hypermedia and Augmented Reality
SIMS 213: User Interface Design & Development
ID Conceptual Models (Mental Models) Summary
Chapter 6 The Process of Interaction Design Presented by: Kinnis Gosha, Michael McGill, Jamey White, and Chiao Huang.
Knowledge Acquisitioning. Definition The transfer and transformation of potential problem solving expertise from some knowledge source to a program.
Understanding and Conceptualizing Interaction Chapter 2.
Software Requirements
Chapter 2: Understanding and conceptualizing interaction
Chapter 4 Cognitive Engineering HCI: Designing Effective Organizational Information Systems Dov Te’eni Jane M. Carey.
1 FJK User-Centered Design and Development Instructor: Franz J. Kurfess Computer Science Dept. Cal Poly San Luis Obispo.
Chapter 13: Designing the User Interface
User Centered Design Lecture # 5 Gabriel Spitz.
User Characteristics & Design Principles Gabriel Spitz 1 Lecture # 11.
Sofia Carlander Kinoshita Laboratory 2004/2005
Chapter 2: Understanding and conceptualizing interaction Question 1.
PROGRAMMING LANGUAGES The Study of Programming Languages.
Conceptual Models & Interface Metaphors. Objectives By the end of this class, you will be able to… Define conceptual model Identify instances where the.
Teamwork and Problem Solving
Principles of User Centred Design Howell Istance.
The ID process Identifying needs and establishing requirements Developing alternative designs that meet those requirements Building interactive versions.
Understanding and conceptualizing interaction. Recap HCI has moved beyond designing interfaces for desktop machines About extending and supporting all.
What is an interface? How many different types of interfaces can you think of?
Mestrado em Informática Médica SIntS 13/14 – T5 Design Concepts Miguel Tavares Coimbra.
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 7: Focusing on Users and Their Tasks.
1 Chapter 5 Software Engineering Practice. 2 What is “Practice”? Practice is a broad array of concepts, principles, methods, and tools that you must consider.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
Coming up: Software Engineering: A Practitioner’s Approach, 6/e Chapter 5 Practice: A Generic View copyright © 1996, 2001, 2005 R.S. Pressman & Associates,
Comp 15 - Usability & Human Factors Unit 8a - Approaches to Design This material was developed by Columbia University, funded by the Department of Health.
INTERACTION DESIGN. Today’s objectives Understanding & conceptualizing interaction Control Design Challenge.
AVI/Psych 358/IE 340: Human Factors Interfaces and Interaction September 22, 2008.
Understanding and conceptualizing interaction
Conceptual Models. Conceptual model A conceptual model is: “a high-level description of how a system is organized and operates.” (Johnson and Henderson,
Chapter 2: Understanding and conceptualizing interaction.
Towards a Pattern Language for User Interface Design
Chapter 1: What is interaction design?. Bad designs From:
Interaction design Xiangming Mu.
Understanding Users Cognition & Cognitive Frameworks
ECE450 - Software Engineering II1 ECE450 – Software Engineering II Today: Introduction to Software Architecture.
Spreadsheet Engineering Builders use blueprints or plans – Without plans structures will fail to be effective Advanced planning in any sort of design can.
Conceptual Model Design Informing the user what to do Lecture 10 Gabriel Spitz 1.
Interaction Design Chapter 1. Good design? Bad design?
Gabriel Spitz 1. Light Switch Issues  Consistency – The switch design is inconsistent with common light switches  Visibility – No visible cue regarding.
Conceptual Model Design Informing the user what to do Lecture # 10 (a) Gabriel Spitz.
After testing users Compile Data Compile Data Summarize Summarize Analyze Analyze Develop recommendations Develop recommendations Produce final report.
Barbara white : interaction design Understanding users cognitive social affective.
TRAINING PACKAGE The User Action Framework Reliability Study July 1999.
1 CS 501 Spring 2003 CS 501: Software Engineering Lecture 13 Usability 1.
Metaphors Informing the user what to do Lecture 10 Gabriel Spitz 1.
Conceptual Model Design Informing the user what to do Lecture # 10 (b) Gabriel Spitz.
Interaction Frameworks COMPSCI 345 S1 C and SoftEng 350 S1 C Lecture 3 Chapter (Heim)
Conceptual Model Design Informing the user what to do Gabriel Spitz 1.
Conceptual Model Design Informing the user what to do Lecture 10a Gabriel Spitz 1.
William H. Bowers – Conceptual Design and Architecture Torres 11.
Conceptual Model Design Informing the user what to do Lecture 10a Gabriel Spitz 1.
Chapter 2 Understanding and conceptualizing interaction
How to think about interaction
Digital media & interaction design
Software Engineering Practice: A Generic View
Presentation transcript:

Vocabulary of Design Visibility - –how easily a user can see what can be done and how to do it Mappings - –how a control and object are related –suffers when more functions than controls Feedback – -shows what has been done -suffers when delayed or not meaningful Cues and affordances learned expectations about visual forms

Core characteristics of interaction design Users should be involved through the development of the project Specific usability and user experience goals need to be identified, clearly documented and agreed at the beginning of the project Iteration is needed through the core activities

Today’s theme: –It’s all in the head.

Conceptual model Need to first think about how the system will appear to users (i.e. how they will understand it) A conceptual model is: “a high-level description of how a system is organized and operates.” (Johnson and Henderson, 2002, p. 26)

Web Definitions A mental model captures ideas in a problem domain, while a conceptual model represents 'concepts' (entities) and relationships between them.... en.wikipedia.org/wiki/Conceptual_model_(computer_science) en.wikipedia.org/wiki/Conceptual_model_(computer_science) A mental image of an object, system, or process. a high-level conceptual representation of important assumptions, inter-component flows, states, parameters, and uncertainties; may be used as a defines concepts of a universe of discourse. Conceptual model provides the abstract description of the selected real-world features. costg9.plan.aau.dk/Bremen2001/Rados/RadosGlossary.htm costg9.plan.aau.dk/Bremen2001/Rados/RadosGlossary.htm written description and visual representation of how a system or process works and interacts chments/Glossary.html chments/Glossary.html

What is and why need a conceptual model? Not a description of the user interface but a structure outlining the concepts and the relationships between them Why not start with the nuts and bolts of design? –Architects and interior designers would not think about which color curtains to have before deciding where the windows will be placed in a new building –Enables “designers to straighten out their thinking before they start laying out their widgets” (p. 28) –Provides a working strategy and a framework of general concepts and their interrelations

Helps the design team Orient themselves towards asking questions about how the conceptual model will be understood by users Not to become narrowly focused early on Establish a set of common terms they all understand and agree upon Reduce the chance of misunderstandings and confusion arising later on

Main components Major metaphors and analogies that are used to convey how to understand what a product is for and how to use it for an activity. Concepts that users are exposed to through the product The relationships between the concepts –e.g., one object contains another The mappings between the concepts and the user experience the product is designed to support

Class Conceptual model

A classic conceptual model: the spreadsheet Analogous to ledger sheet Interactive and computational Easy to understand Greatly extending what accountants and others could do

Why was it so good? It was simple, clear, and obvious to the users how to use the application and what it could do “it is just a tool to allow others to work out their ideas and reduce the tedium of repeating the same calculations.” capitalized on user’s familiarity with ledger sheets Got the computer to perform a range of different calculations and recalculations in response to user input

Don Norman Design of Everyday Things. Buy at amazon

Conceptual Model Mental Model

Watson task You are shown a set of four cards placed on a table each of which has a number on one side and a colored patch on the other side. The visible faces of the cards show 3, 8, red and brown. Which card(s) should you turn over in order to test the truth of the proposition that if a card shows an even number on one face, then its opposite face is red?

Watson task You are a bartender and need to make sure you are not serving minors. Who do you check? Coke Beer

The Conceptual Model is what the designer produces and tries to communicate to the user. The Mental Model is what the user develops and understands about the system.

Vocabulary of Design The burden of interpretation –how much “thinking” is required on the users part? Input gaps –how easy it is to figure out how to do it Output gaps –how easy it is to figure out system state

Impementation Model Represented Model User Mental Model

User Models? Mental Models –The expectation a user has about a computer’s behavior. –Inside the head… can be trained User Models –The expectation a computer has of a user –Inside the computer… can be changed directly.

Another classic 8010 Star office system targeted at workers not interested in computing per se Spent several person-years at beginning working out the conceptual model Simplified the electronic world, making it seem more familiar, less alien, and easier to learn Johnson et al (1989)

The Star interface

Interface metaphors Designed to be similar to a physical entity but also has own properties –e.g. desktop metaphor, search engine Exploit user’s familiar knowledge, helping them to understand ‘the unfamiliar’ Conjures up the essence of the unfamiliar activity, enabling users to leverage of this to understand more aspects of the unfamiliar functionality People find it easier to learn and talk about what they are doing at the computer interface in terms familiar to them

Benefits of interface metaphors Makes learning new systems easier Helps users understand the underlying conceptual model Can be innovative and enable the realm of computers and their applications to be made more accessible to a greater diversity of users

Problems with interface metaphors (Nelson, 1990) Break conventional and cultural rules –e.g., recycle bin placed on desktop Can constrain designers in the way they conceptualize a problem space Conflict with design principles Forces users to only understand the system in terms of the metaphor Designers can inadvertently use bad existing designs and transfer the bad parts over Limits designers’ imagination in coming up with new conceptual models

Vocabulary of Design The burden of interpretation –how much “thinking” is required on the users part? Input gaps –how easy it is to figure out how to do it Output gaps –how easy it is to figure out system state

Bathtub control User’s goals: –Warm bath –Right amount of water Psychological variables –Temperature & water depth Physical variables –Cold water flow rate –Warm water flow rate

Simple design Hot Water Cold Water valve Bath Tub

But how do you turn on the shower? Pushing the control (arrow) is only PART of the solution (see next slide) How does this map temperature and speed?

The problem: another control Both controls have to be on!

Design exercise Design the perfect bathtub control. 1. Assume you have unlimited budget 2. Bath control only… no shower. 3. Think about mapping controls to the users goals (physical variables).