SIMS 213: User Interface Design & Development Marti Hearst Tues, Jan 27, 2004.

Slides:



Advertisements
Similar presentations
Structured Design The Structured Design Approach (also called Layered Approach) focuses on the conceptual and physical level. As discussed earlier: Conceptual.
Advertisements

Design, prototyping and construction
Conceptual Models & Interface Metaphors. 2 Interface Hall of Fame or Shame? Tabbed dialog for setting options in MS Web Studio –more tabs than space to.
HCI 특론 (2007 Fall) Conceptual Models & Interface Metaphors.
I213: User Interface Design & Development Marti Hearst Thurs, Jan 25, 2007.
SIMS 213: User Interface Design & Development Marti Hearst Thurs, Jan 30, 2003.
Part 1: Introducing User Interface Design Chapter 1: Introduction –Why the User Interface Matters –Computers are Ubiquitous –The Importance of Good User.
SIMS 213: User Interface Design & Development Marti Hearst Tues, Feb 25, 2003.
Introduction to the Course Marti Hearst (UCB SIMS) SIMS 213, UI Design & Development 19, 1999.
UQI120S2 Human Computer Interaction Designing and building GUIs We made the point that the final product should fit the cognitive makeup of the user. We.
Requirements Analysis 8. 1 Storyboarding b508.ppt © Copyright De Montfort University 2000 All Rights Reserved INFO2005 Requirements Analysis Human.
SIMS 213: User Interface Design & Development Marti Hearst Thurs, Jan 18, 2001.
Part 3: Design Days 15, 19, 21, 23 Chapter 8: Work Reengineering and Conceptual Design Chapter 9: Design Guidance and Design Rationale Chapter 10: Interaction.
SIMS 213: User Interface Design & Development Marti Hearst Tues, Jan 25, 2005.
SIMS 213: User Interface Design & Development Marti Hearst Tues, Feb 14, 2006.
Understanding and Conceptualizing Interaction Chapter 2.
SIMS 213: User Interface Design & Development Marti Hearst Tues, Feb 15, 2005.
The Xerox “Star” A Retrospective By Bruno Nadeau & Luv Sharma.
SIMS 202 Information Organization and Retrieval Prof. Marti Hearst and Prof. Ray Larson UC Berkeley SIMS Tues/Thurs 9:30-11:00am Fall 2000.
Chapter 2: Understanding and conceptualizing interaction
SIMS 213: User Interface Design & Development Marti Hearst Tues, Feb 10, 2004.
SIMS 213: User Interface Design & Development Marti Hearst Tues Feb 13, 2001.
I213: User Interface Design & Development Marti Hearst Tues, Feb 13, 2007.
Usability 2004 J T Burns1 Usability & Usability Engineering.
SIMS 213: User Interface Design & Development Marti Hearst Thurs, Jan 20, 2005.
SIMS 213: User Interface Design & Development Marti Hearst Thurs, Jan 22, 2004.
SIMS 213: User Interface Design & Development Marti Hearst Thurs, Jan 18, 2007.
Rapid Prototyping Marti Hearst (UCB SIMS) SIMS 213, UI Design & Development February 25, 1999.
SIMS 213: User Interface Design & Development Marti Hearst Tues, Feb 12, 2002.
SIMS 213: User Interface Design & Development Marti Hearst Thurs, Jan 26, 2006.
Introduction to HCI Marti Hearst (UCB SIMS) SIMS 213, UI Design & Development January 21, 1999.
MCT260-Operating Systems I Operating Systems I Interfaces to Operating Systems.
SIMS 213: User Interface Design & Development Marti Hearst Thurs, Jan 29, 2004.
SIMS 213: User Interface Design & Development Marti Hearst Thurs, Jan 23, 2003.
Discount Usability Engineering Marti Hearst (UCB SIMS) SIMS 213, UI Design & Development March 2, 1999.
INTRODUCTION. Concepts HCI, CHI Usability User-centered Design (UCD) An approach to design (software, Web, other) that involves the user Interaction Design.
Copyright 1999 all rights reserved Overview of HCI n What is Human-Computer Interaction? n Why should an Information Scientist be concerned with Human-Computer.
Agile Process: Overview n Agile software engineering represents a reasonable compromise to conventional software engineering for certain classes of software.
Chapter 2: Understanding and conceptualizing interaction Question 1.
SIMS 213: User Interface Design & Development Marti Hearst Thurs, Jan 24, 2002.
The ID process Identifying needs and establishing requirements Developing alternative designs that meet those requirements Building interactive versions.
1 Computer Graphics Assistant Professor Dr. Sana’a Wafa Al-Sayegh 2 nd Semester ITGD3107 University of Palestine.
Visual BASIC 1 Introduction
Search and Navigation Based on the paper, “Improved Search Engines and Navigation Preference in Personal Information Management” Ofer Bergman, Ruth Beyth-Marom,
Paradigms Material from Authors of Human Computer Interaction Alan Dix, et al.
AVI/Psych 358/IE 340: Human Factors Interfaces and Interaction September 22, 2008.
Final Presentation Red Team. Introduction The Project We are building an application that can potentially assist Service Writers at the Gene Harvey Chevrolet.
CS2003 Usability Engineering Human-Centred Design Dr Steve Love.
Conceptual Models. Conceptual model A conceptual model is: “a high-level description of how a system is organized and operates.” (Johnson and Henderson,
Chapter 7 Interactive Design and Prototyping Human Performance Engineering Robert W. Bailey, Ph.D. Third Edition.
A Semiotic Model of User-Interface Metaphor
Fall 2015CISC/CMPE320 - Prof. McLeod1 CISC/CMPE320 Assignment 1 due tomorrow, 7pm. RAD due next Friday in your Wiki. Presentations week 6. Tomorrow’s lecture.
Proposal 12: Contents Metaphor –Briefly explains the metaphor that I have chose, and why I think it is a good one to use. Interface Design –Lists the objects.
Metaphors Informing the user what to do Lecture 10 Gabriel Spitz 1.
Operating Systems Overview Basic Computer Concepts Operating System What does an operating system do  A computer’s software acts similarly with.
Conceptual Model Design Informing the user what to do Lecture # 10 (b) Gabriel Spitz.
Prototyping Creation of concrete but partial implementations of a system design to explore usability issues.
Toolkits and Languages CSE 490JL Section Dec 1 st & 3 rd 2004 Richard C. Davis & Kate Everitt.
Prof. James A. Landay University of Washington Winter 2007 Video Prototyping January 22, 2007.
Software Design and Development Development Methodoligies Computing Science.
GUI Evolution (Fruit vs Squares)
Conceptual Models & Interface Metaphors
Getting Started with Windows 10
Design.
ICS 463, Intro to Human Computer Interaction Design: 6 (Theory): Interface Metaphors (Chapter 7)
Cooper Part III Interaction Details Designing for the Desktop
Agile Process: Overview
Cooper Part III Interaction Details Designing for the Desktop
Software - Operating Systems
Presentation transcript:

SIMS 213: User Interface Design & Development Marti Hearst Tues, Jan 27, 2004

Metaphor in User Interfaces

Metaphor and Analogy Metaphor –L. metaphora, fr. to carry over, transfer; meta: beyond, over –The transference of the relation between one set of objects to another set for the purpose of brief explanation (Webster’s revised) Analogy –A resemblance of relations; an agreement or likeness between things in some circumstances or effects, when the things are otherwise entirely different. (Webster’s revised) –1. Similarity in some respect between things that are otherwise dissimilar: "the operation of a computer presents an interesting analogy to the working of the brain“ (WordNet) – 2: (logic) inference that if things agree in some respects they probably agree in others (WordNet)

Slide adapted from James Landay Metaphor Lakoff & Johnson –“...the way we think, what we experience, and what we do every day is very much a matter of metaphor.'' –in our language & thinking - “argument is war” …he attacked every weak point... criticisms right on target... if you use that strategy We can use metaphor to highlight certain features & suppress others –There is some systematicity to the transference

What are some example interface metaphors?

Direct Manipulation uses a Metaphor Metaphor –Computer objects as visible, moveable objects Consequences –Items represented as icons –Items can be “picked up” and “moved” on a surface –Items can be “thrown out” –Items can be “copied” Do we really want to have to drag them to a photocopier? How much is too much?

The Desktop Metaphor Started at Xerox PARC –Xerox Star (see video) –Bitmapped screens made it possible Not meant to be a real desktop –Idea is to organize information in a way to allow people to use it in the way they user information on their desktops –Allow windows to overlap – make the screen act as if there were objects on it Apple took it farther –Waste basket, etc Microsoft took it to extremes –Microsoft Bob – a recognized failure

Macintosh Desktop

Caldera’s Desktop

Microsoft Bob’s Desktop Metaphor

Microsoft Bob’s Livingroom – Almost not a metaphor anymore!

Beyond the Desktop Robertson, George et al. " The Task Gallery: A 3D Window Manager." In Proceedings of CHI 2000

Beyond the Desktop Jun Rekimoto, Multiple-Computer User Interfaces: "Beyond the Desktop" Direct Manipulation Environments, ACM CHI2000 Video Proceedings, 2000.

Identify the mis-matched metaphors (from the Interface Hall of Shame) The classic (from the mac desktop) –To eject a disk you drag it to the trashcan

Identify the mis-matched metaphors (from the Interface Hall of Shame) VCR buttons to control a printer??

Identify the mis-matched metaphors (from the Interface Hall of Shame) Using tabs to make arbitrary groups

Direct Manipulation Metaphor DLITE makes heavy use of direct manipulation metaphors But it isn’t supposed to be just like in the real world Retain what works, omit the rest

Discussion Kent Sullivan, The Windows 95 User Interface: A Case Study in Usability Engineering, CHI A case study of the iterative design process.

Sullivan Case Study –12 people on the Windows 95 team!! –Waterfall design method (compartmentalized; UI done at the end during quality assurance stage) would produce an unusable product. –Method: Find most common tasks, and test on those Compare to a baseline (Windows 3.1) Rapid prototyping tools Importance of usability testing!! –Stepping back Found big problems Held a retreat to radically re-think things

Sullivan Case Study –Decided to: Focus on scaffolding (beginner -> intermediate-expert) Give up on too much backwards-compatibility with 3.1 Dump the huge design spec (!) Encouraged social interaction. Continually informed outsiders as well as team members about the design –Fine tuning with usablity tests Holistic interface test in the lab – Many participants! Longitudinal field study –About Windows 3.1 … a good demonstration of what happens when usability is not taken into account