Mental Models Sonia Chiasson and Robert Biddle Human Oriented Technology Lab Carleton University, Ottawa.

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
User Interfaces Interface IS the system UI an important determinant of success of MSS –Execution time –System versatility –Learning time for users, end.
The City of Ember Literary Devices.
Design Concepts and Principles
Usable Security (Part 1 – Oct. 30/07) Dr. Kirstie Hawkey Content primarily from Teaching Usable Privacy and Security: A guide for instructors (
Ch 11 Cognitive Walkthroughs and Heuristic Evaluation Yonglei Tao School of Computing and Info Systems GVSU.
Good Design Visibility is key to interaction design Take advantage of affordances/constraints Provide a good conceptual model for the user.
Design Activities in Usability Engineering laura leventhal and julie barnes.
Independent Research End User Design Cortney Germain Matthew Hung Mark Lewis Prazen.
Week 8 Implementation Design Alex Baker. Implementation Design System Design – Describes what the system should do Implementation Design – Describes what.
Software Requirements
Specialized Business Information Systems Chapter 11.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
Overview of Long-Term Memory laura leventhal. Reference Chapter 14 Chapter 14.
MONITORING PROJECTS: QUALITY AND RESULTS. DAY ONE ASSESSMENT DAY TWO DESIGN DAY THREE MONITORING MORNING Intro. Training Intro. Assessment Intro. DesignIntro.
Performing User Interface Design
Understanding Task Orientation Guidelines for a Successful Manual & Help System.
Computational Thinking Related Efforts. CS Principles – Big Ideas  Computing is a creative human activity that engenders innovation and promotes exploration.
Design, goal of design, design process in SE context, Process of design – Quality guidelines and attributes Evolution of software design process – Procedural,
Visual 3. 1 Lesson 3 Risk Assessment and Risk Mitigation.
Conceptual Models & Interface Metaphors. Objectives By the end of this class, you will be able to… Define conceptual model Identify instances where the.
Spring /6.831 User Interface Design and Implementation1 Lecture 3: Visibility.
Data Flow Diagram A method used to analyze a system in a structured way Used during: Analysis stage: to describe the current system Design stage: to describe.
11 C H A P T E R Artificial Intelligence and Expert Systems.
Explanation Facility دكترمحسن كاهاني
1 Science as a Process Chapter 1 Section 2. 2 Objectives  Explain how science is different from other forms of human endeavor.  Identify the steps that.
Chapter 17. Initial Object Design Inputs: requirements meetings various Use Cases – 10% complete Key risks addressed with preliminary programming System.
COMPSCI 345 S1 C and SoftEng 350 S1 C Interaction Styles Lecture 4 Chapter 2.3 (Heim)
Modeling - Simulation and AI Software ©Ideler2002.
16 October Reminder Types of Testing: Purpose  Functional testing  Usability testing  Conformance testing  Performance testing  Acceptance.
A-Level Computing#BristolMet Session Objectives#15 MUST define the term user interface SHOULD describe the characteristics of different UIs and suggest.
Understanding Users Cognition & Cognitive Frameworks
1 COSC 4406 Software Engineering COSC 4406 Software Engineering Haibin Zhu, Ph.D. Dept. of Computer Science and mathematics, Nipissing University, 100.
Decision Making in U.S. History Introduction Lesson Created by Mrs. Janiak using Decision Making in U.S. History text.
PICTURE your design. Purpose : Functions & Content Functions the facilities that make the content of the ICT useful for relevant users and other ICT’s.
1 The Good, the Bad, and the Ugly: Collecting and Reporting Quality Performance Data.
Human Abilities 2 How do people think? 1. Agenda Memory Cognitive Processes – Implications Recap 2.
Yonglei Tao School of Computing & Info Systems GVSU Ch 7 Design Guidelines.
Yan Zhang University of North Carolina, Chapel Hill Introduction Research goals  Help build systems that are able to provide.
Capabilities of Humans. Gestalt More than the sum of its parts.
The Digital Crime Scene: A Software Perspective Written By: David Aucsmith Presented By: Maria Baron.
Chapter 5:User Interface Design Concepts Of UI Interface Model Internal an External Design Evaluation Interaction Information Display Software.
Capabilities of Humans. Gestalt More than the sum of its parts.
Ergonomics/Human Integrated Systems (Project 02)
Supporting the design of interactive systems a perspective on supporting people’s work Hans de Graaff 27 april 2000.
Basic Organization of UI Software. 2 The User Interface n Typically want to think of “UI” as only one component of an overall system – The part that “deals.
Design, prototyping and construction(Chapter 11).
Analysis and Critical Thinking in Assessment 1. What is the problem? Gathering information Using information to inform decisions/ judgment Synthesising.
Interaction Frameworks COMPSCI 345 S1 C and SoftEng 350 S1 C Lecture 3 Chapter (Heim)
Dr. Mark Gaynor, Dr. Feliciano Yu, Bryan Duepner.
The Marketing Plan. Executive Summary  This is at the beginning of the marketing plan and is an overview of the entire marketing plan  It briefly addresses.
Ecological Interface Design Overview Park Young Ho Dept. of Nuclear & Quantum Engineering Korea Advanced Institute of Science and Technology May
Copyright 2006 John Wiley & Sons, Inc Chapter 5 – Cognitive Engineering HCI: Developing Effective Organizational Information Systems Dov Te’eni Jane Carey.
A CPU Schedule Algorithm Simulator By: Renwei Yu.
Knowledge Representation. A knowledge base can be organised in several different configurations to facilitate fast inferencing Knowledge Representation.
DSS & Warehousing Systems
The systems approach Churchman, C.W. (1968) The Systems Approach, Dell Publishing Co., New York. Ackoff, R.L. (1971) Towards a system of system concepts.
The User Lecture 2 DeSiaMore
Object-Oriented Programming (OOP) Lecture No. 2
Design, prototyping and construction
DESIGN, PROTOTYPING and CONSTRUCTION
Human Computer Interaction
Model, View, Controller design pattern
A Usability Study and Critique of Two Password Managers
Workshop III Mental representations and discrete choice behaviour
Expert Knowledge Based Systems
Chapter 1 Key Security Terms.
Expert Knowledge Based Systems
Design, prototyping and construction
Presentation transcript:

Mental Models Sonia Chiasson and Robert Biddle Human Oriented Technology Lab Carleton University, Ottawa

Mental models 1943 Craik  humans translate external events into internal models used for reasoning

Mental models 1943 Young  mental model is users’ mental representation of their interaction with complex devices 1981

Mental models 1943 Norman  designer – system – user

Mental models 1943 Bayman & Mayer  user conception of the “invisible” info processing between input and output

Mental models 1943 Johnson-Laird  mental models are a method of representing knowledge and the manipulation of models is a form of reasoning

user’s mental model system image the actual system researcher’s conceptualization designer’s conceptual model Mental models according to Norman

What kinds of mental models can we encourage?

Metaphors shield users from tech details more accessible to novice users –framed as something relevant and meaningful –draws upon existing knowledge may have unintended consequences –users may draw unexpected/undesirable conclusions

EID approach Ecological Interface Design foster mental model that reflects actual system hierarchy of detail helps users diagnose/troubleshoot unexpected situations, understand impact of actions assumes knowledgeable user Overview... progressively more detail... Physical components and sensors

Current security interfaces Novices: –very limited models of computer security threats –magical computer *stuff* happens –UI does not foster useful mental models –invisibility/transparency is bad but common approach –“more education” = unrealistic burden on users –dangerous errors = personally at risk Experts: –domain knowledge –UI re-purposed/adopted for security purposes –multiple alarm, indicators, & visualizations –> must assimilate to make decision = often overwhelming –dangerous errors = system- wide vulnerabilities

As researchers/designers... we must consider... at least 3 topics

1. How to foster security mental models UI must convey info needed to accurately/easily predict and understand consequences of actions and system behaviour should we go with metaphor or EID approach? –what are the risks of each? –if we go with metaphors, is there an overarching “security” metaphor that could work? what is computer security like that would be relevant to non-technical users? –is it dependent target users?

2. Attacks on mental models how can attackers manipulate user mental models to their advantage? how can we defend against it? –can we ever provide cues that can’t be spoofed? does fostering a legitimate user’s mental model reveal info to attackers? how do we tell legit people what’s really happening without compromising security?

3. How to identify mental models how do we identify mental models? how can we tell if the appropriate model is being conveyed?

Wrap up different approaches to fostering mental models –metaphor vs EID current systems do poor job of conveying mental model for both novice and expert users must consider: –how to foster security mental models –how attackers take advantage of mental models –how to accurately identify user mental models