Understanding and conceptualizing interaction. Understanding the problem space –What do you want to create? –What are your assumptions? –Will it achieve.

Slides:



Advertisements
Similar presentations
Conceptualizing interaction
Advertisements

Understanding and conceptualizing interaction. Recap HCI has moved beyond designing interfaces for desktop machines About extending and supporting all.
Design, prototyping and construction
Last time… Conceptual models –To what is it similar? What metaphors do they bring to bear? –What actions can one perform on or with a web page?
Activity Design Goal: work from problems and opportunities of problem domain to envision new activities.
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.
Interface metaphors & analogies pp pp
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.
Recap HCI has moved beyond designing interfaces for desktop machines
The Psychopathology of Everyday Things
From requirements to design
SIMS 213: User Interface Design & Development
Usability goals Effective to use (Man kan göra det man vill göra.)
ID Conceptual Models (Mental Models) Summary
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.
Design Process …and the project.
Chapter 2: Understanding and conceptualizing interaction
Administrivia Turn in ranking sheets, we’ll have group assignments to you as soon as possible Homeworks Programming Assignment 1 due next Tuesday Group.
User-Centered Design and Development
Conceptual Model Mr. John Kelleher. 1 Conceptual Model A description of the proposed system in terms of a set of integrated ideas and concepts about what.
Conceptual Models & Interface Metaphors Working as a Team*
What is a prototype? A prototype is a small scale model of your larger product. Can be a physical object, or a simple software program. Many physical.
1 FJK User-Centered Design and Development Instructor: Franz J. Kurfess Computer Science Dept. Cal Poly San Luis Obispo.
Review an existing website Usability in Design. to begin with.. Meeting Organization’s objectives and your Usability goals Meeting User’s Needs Complying.
CS305: Fall2008 Mental and Conceptual Models Readings: Chapter 2 of ID-Book.
CS 235: User Interface Design August 27 Class Meeting Department of Computer Science San Jose State University Spring 2015 Instructor: Ron Mak
CS 235: User Interface Design August 27 Class Meeting Department of Computer Science San Jose State University Fall 2014 Instructor: Ron Mak
Chapter 2: Understanding and conceptualizing interaction Question 1.
Conceptual Models & Interface Metaphors. Objectives By the end of this class, you will be able to… Define conceptual model Identify instances where the.
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.
Usability Evaluation/LP Usability: how to judge it.
Prof. James A. Landay University of Washington Autumn 2004 Conceptual Models & Interface Metaphors October 7, 2004.
Heuristic evaluation Functionality: Visual Design: Efficiency:
INTERACTION DESIGN. Today’s objectives Understanding & conceptualizing interaction Control Design Challenge.
AVI/Psych 358/IE 340: Human Factors Interfaces and Interaction September 22, 2008.
Designing & Testing Information Systems Notes Information Systems Design & Development: Purpose, features functionality, users & Testing.
Understanding and conceptualizing interaction
1 Introduction to Software Engineering Lecture 1.
Chapter 2: Understanding and conceptualizing interaction.
Problem Statement Overview of tasks Requirements for selection test.
The Design of Everyday Things Darn these hooves! I hit the wrong switch again! Who designs these instrument panels, raccoons?
Human Centric Computing (COMP106) Assignment 2 PROPOSAL 23.
Yonglei Tao School of Computing & Info Systems GVSU Ch 7 Design Guidelines.
Chapter 5:User Interface Design Concepts Of UI Interface Model Internal an External Design Evaluation Interaction Information Display Software.
Barbara white : interaction design Understanding users cognitive social affective.
Metaphors Informing the user what to do Lecture 10 Gabriel Spitz 1.
 Creative  Abstract  Algorithm  Programming  Data  Internet  Impact.
Conceptual Model Design Informing the user what to do Lecture # 10 (b) Gabriel Spitz.
Of 24 lecture 11: ontology – mediation, merging & aligning.
Activity Design Goal: work from problems and opportunities of problem domain to envision new activities.
William H. Bowers – Conceptual Design and Architecture Torres 11.
The Project. A little video inspiration IDEO – an industrial design company.
Chapter 2 Understanding and conceptualizing interaction
How to think about interaction
CEN3722 Human Computer Interaction Interface Metaphors and Conceptual Models Dr. Ron Eaglin.
Conceptual Models & Interface Metaphors
Automatic cLasification d
Chapter 3 Understanding users
Activity Flow Design - or - Organizing the users’ Work
Agents & Agency What do we mean by agents? Are agents just a metaphor?
© James D. Skrentny from notes by C. Dyer, et. al.
The Design of Everyday Things
Models, Metaphor, Paradigms
MIS 385/MBA 664 Systems Implementation with DBMS/ Database Management
Presentation transcript:

Understanding and conceptualizing interaction

Understanding the problem space –What do you want to create? –What are your assumptions? –Will it achieve what you hope it will?

An example What were the assumptions made by cell phone companies when developing WAP services? Was it a solution looking for a problem?

Assumptions: realistic or wish-list? People want to be kept informed of up-to-date news wherever they are - reasonable People want to interact with information on the move - reasonable People are happy using a very small display and using an extremely restricted interface - not reasonable People will be happy doing things on a cell phone that they normally do on their PCs (e.g. surf the web, read , shop, bet, play video games) - reasonable only for a very select bunch of users

From problem space to design space Having a good understanding of the problem space can help inform the design space –e.g. what kind of interface, behavior, functionality to provide But before deciding upon these it is important to develop a conceptual model

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: –“the proposed system in terms of a set of integrated ideas and concepts about what it should do, behave and look like, that will be understandable by the users in the manner intended”

First steps in formulating a conceptual model What will the users be doing when carrying out their tasks? How will the system support these? What kind of interface metaphor, if any, will be appropriate? What kinds of interaction modes and styles to use? Always keep in mind when making design decisions how the user will understand the underlying conceptual model

Andre modeller Mental modell –Kunnskap om et system inne I brukerens hode Bruker modell vs. design modell –Designere har andre modeller enn brukere

Refrigerator Problem: freezer too cold, but fresh food just right freezer fresh food

Refrigerator Controls What is your conceptual model? Normal SettingsC and 5 Colder Fresh FoodC and 6-7 Coldest Fresh FoodB and 8-9 Colder FreezerD and 7-8 Warmer Fresh FoodC and 4-1 OFF (both)0 A B C D E

A B C D E A Common Conceptual Model independent controls cooling unit cooling unit

Actual Conceptual Model Now can you fix the problem? Possible solutions: 1) make controls map to user’s model 2) make controls map to actual system A B C D E cooling unit

Design Model & User Model Users get model from experience & usage –through system image What if the two models don’t match? Design Model User Model System Image

Interface metaphors Interface designed to be similar to a physical entity but also has own properties –e.g. desktop metaphor, web portals Can be based on activity, object or a combination of both 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

Benefits of interface metaphors Makes learning new systems easier Helps users understand the underlying conceptual model Can be very 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 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