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

Slides:



Advertisements
Similar presentations
Design, prototyping and construction
Advertisements

Context-Aware User Interfaces. Gent, 21 maart 2005 Context-Aware User Interfaces Context-Aware User Interfaces is a requirement for all defined scenarios.
1 CS 501 Spring 2002 CS 501: Software Engineering Lecture 11 Designing for Usability I.
Youth worker competences The European context By Tsvetelina Ilieva, SCAS E-games: Empowering youth work.
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.
Chapter 1: The Context of SA&D Methods
From requirements to design
Part 2b: Requirements Chapter 2: How to Gather Requirements: Some Techniques to Use Chapter 3: Finding Out about the Users and the Domain Chapter 4: Finding.
Design Activities in Usability Engineering laura leventhal and julie barnes.
Human Computer Interface. HCI and Designing the User Interface The user interface is a critical part of an information system -- it is what the users.
Department of Information Science and Telecommunications Interactive Systems Michael B. Spring Department of Information Science and Telecommunications.
SIMS 213: User Interface Design & Development
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.
L Management Information Systems & The MIS Challenge l Factors Shaping Business Today l The Role of IT in the Information Age l Information as a New Business.
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.
Verbal (symbol) Based Interactions Dr.s Barnes and Leventhal.
New Library Catalogue Interface Proposal 3. Introduction This presentation will outline the design decisions for the new interface of the on-line library.
Understanding and Conceptualizing Interaction Chapter 2.
The Xerox “Star” A Retrospective By Bruno Nadeau & Luv Sharma.
Chapter 2: Understanding and conceptualizing interaction
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.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 16 Slide 1 User interface design.
How does the user think visually? That understanding can tell us about how to design visual images.
Exploring the Basics of Windows XP
The chapter will address the following questions:
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 18 Slide 1 Software Reuse 2.
1 ISE 412 Human-Computer Interaction Design process Task and User Characteristics Guidelines Evaluation.
Chapter 2: Understanding and conceptualizing interaction Question 1.
Chapter 11: Interaction Styles. Interaction Styles Introduction: Interaction styles are primarily different ways in which a user and computer system can.
Office Management A Look from the Inside-Out Mohammad Najjar, PhD Management Science 1.
1 BTEC HNC Systems Support Castle College 2007/8 Systems Analysis Lecture 9 Introduction to Design.
1 Human-Computer Interaction  Design process  Task and User Characteristics  Guidelines  Evaluation.
CSC 480 Software Engineering Lecture 19 Nov 11, 2002.
The ID process Identifying needs and establishing requirements Developing alternative designs that meet those requirements Building interactive versions.
Luigina Ciolfi, Interaction Design Centre CS4826, Human-Computer Interaction 09/04/2002
Great Idea – Computer “Desktop What’s on your Computer Desktop? Browser and reader Office tools Microsoft Office or some other product Adobe Reader.
Understand the Business Function
Operating Systems. Without an operating system your computer would be useless! A computer contains an Operating System on its Hard Drive. This is loaded.
CS CS 5150 Software Engineering Lecture 11 Usability 1.
Chapter 4 paradigms. why study paradigms Concerns –how can an interactive system be developed to ensure its usability? –how can the usability of an interactive.
1 Object-Oriented Systems Development Bahrami © Irwin/ McGraw-Hill Chapter 2: Object Basics Object-Oriented Systems Development Using the Unified Modeling.
AVI/Psych 358/IE 340: Human Factors Interfaces and Interaction September 22, 2008.
Content The system development life cycle
Understanding and conceptualizing interaction
Metaphors in Computing  Metaphors are the fundamental concepts, terms, and images by which and through which information is easily recognized, understood,
Agents that Reduce Work and Information Overload and Beyond Intelligent Interfaces Presented by Maulik Oza Department of Information and Computer Science.
Computer in Everyday Life
Slide 1 Tomorrow’s Technology and You Chapter 11 Computers in Society © 2006 Prentice-Hall, Inc.
Foundations of Information Systems in Business. System ® System  A system is an interrelated set of business procedures used within one business unit.
U i Modleing SGOMS in ACT-R: Linking Macro- and Microcognition Lee Yong Ho.
CMPF124 Personal Productivity With Information Technology Chapter 1 – Part 2 Introduction to Windows Operating Systems Manipulating Windows GUI CMPF 124.
Human-Computer Interaction Design process Task and User Characteristics Guidelines Evaluation ISE
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.
1 CS 501 Spring 2003 CS 501: Software Engineering Lecture 13 Usability 1.
Conceptual Model Design Informing the user what to do Lecture # 10 (b) Gabriel Spitz.
Planning Instruction A Review of the Cognitive Domain and Performance Objectives.
Introduction to Human Factors in Information Systems Dr. Cindy Corritore Creighton University ITM 734 Fall 2005.
DOCUMENTATION REF: Essentials of IT (Hamilton et al) Chapter 1.
What are Paradigms Predominant theoretical frameworks or scientific world views –e.g., Aristotelian, Newtonian, Einsteinian (relativistic) paradigms in.
Operating System Basics. Outline The User Interface Running Programs Managing Files Managing Hardware Utility Software.
CEN3722 Human Computer Interaction Interface Metaphors and Conceptual Models Dr. Ron Eaglin.
ICS 463, Intro to Human Computer Interaction Design: 6 (Theory): Interface Metaphors (Chapter 7)
INTERACTION PARADIGMS
The User Lecture 2 DeSiaMore
Chapter 6: Interfaces and interactions
Tracey Boswell Kate Wise LI842 Indexing and Abstracting April 2008
Professor John Canny Fall 2001 Sept 25, 2001
Professor John Canny Spring 2003 Feb 26
Presentation transcript:

Chapter 2, part 3 Human Aspects: Interface Metaphors and Conceptual Models... What is a metaphor? Traditionally, metaphors were used in speech where things were described with other things that shared some common elements, e.g. calling a ferocious person a tiger.

Metaphors continued Verbal metaphors are often applied to make an abstract concept more understandable. Verbal metaphors = Analogies based on familiar knowledge. Virtual metaphors = combining the system plus familiar domains into one entity. This usually enables to form a concrete system image.

Metaphors continued Where the interface metaphor became important in User Interface Design......when physical objects that can typically be found in offices were implemented as interface metaphors (e.g. paper, folders, filling cabinets, rubbish bins etc.). Examples: Xerox Star User Interface, Mac, Windows etc.

Metaphors continued This analogy to a typical office desk helped a lot of people to better understand how to deal with computers = Desktop metaphor. The mouse (itself a metaphor) also helped people to further control their actions through selecting, dragging etc.

Metaphors continued Advantage: Users were able to develop mental models of the system. These mental models were more like the metaphor world rather than how the system really worked (which is indeed harder to understand), i.e. people developed functional models and were typically unaware of the underlying structural aspects.

Metaphors continued Composite Metaphors......make applications even more powerful by combining the desktop metaphor with other metaphors and possible actions (Menus, windows, scroll bars etc.).

Metaphors continued What does Ubiquitous Computing aim for? To enable the user to naturally, effortlessly and unconsciously interact with the system to accomplish everyday tasks (i.e. that the process gets automated much as bike riding or car driving is automated with experience).

Metaphors continued Ubiquitous Computing continued Many electronic systems are invisible in standard home environments and the control of these systems becomes natural after a while (microwave ovens, the laundry etc.)

Metaphors continued Ubiquitous Computing continued It would be best to have invisible interfaces for some applications (e.g. as soon as speech recognition and selective attention to separate speech from noise work perfectly, there might be many more invisible interfaces)

Metaphors continued Conceptual models...provide frameworks how to design appropriate interface metaphors. They describe various ways in which systems are understood by different people.

Metaphors continued Conceptual models continued 2 important questions: 1. How do users understand the system? 2. How do designers understand the system?

Metaphors continued Conceptual models continued Designers need to understand what concepts users have about how the system works, and designers should ideally help users to develop accurate mental models of the system.

Organisational Aspects Many users work in organisations and therefore it is not only important to consider the individual user, but also to consider the organisations users work in. For instance it is useful to consider what mental models users have about how the computer network works in the entire organisation.

Organisational Aspects continued Attention should be paid to the organisational structure, the working practices and the culture of the organisation. If no attention is paid to these aspects, a new computing system is unlikely to be used in the most effective way or might even be ignored or discarded.

Organisational Aspects continued The question arises how to design and implement computer systems into an organisation so that they are accepted and effectively used. Because organisations sometimes change very rapidly, it is important to constantly adapt to these changes and to evaluate the organisational structures over time.

Organisational Aspects continued How will organisational structures look like in the future. Several scenarios have partly become reality and might be more frequent in the future. The paperless office where information is handled electronically. The automated office where factories are operated by robots. The electronic cottage where people work from home.

Organisational Aspects continued The global village where computing, telecommunications and multimedia enables an interconnected society world-wide.

Organisational Aspects continued Influences of technology on society and organisations have had both positive and negative effects (e.g. tools for enriching and speeding up work, but also deskilling and increased control over workers). It is therefore necessary to also consider ethical aspects. End of Chapter 2 from the study guide