Conceptual Models. Conceptual model A conceptual model is: “a high-level description of how a system is organized and operates.” (Johnson and Henderson,

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

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.
The Psychopathology of Everyday Things
A brief overview What is program evaluation? How is an evaluation conducted? When should it be used? When can it be used? Used with Permission of: John.
From requirements to design
David Liddle’s ideas: the Conceptual Model Information Systems Development 3 UQI107S3.
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.
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.
Chapter 6 The Process of Interaction Design Presented by: Kinnis Gosha, Michael McGill, Jamey White, and Chiao Huang.
Software Engineering General Project Management Software Requirements
Understanding and Conceptualizing Interaction Chapter 2.
Chapter 2: Understanding and conceptualizing interaction
What is a good length of string? –Depends on its use How do you design a good length of string? –Can be determined by a process What is a good user interface?
Using SuperVISE for Software Design Validation III Peter Henderson and Bob Walters.
Design of the Conceptual Model Winograd, Chapter 2.
1 FJK User-Centered Design and Development Instructor: Franz J. Kurfess Computer Science Dept. Cal Poly San Luis Obispo.
Foundations This chapter lays down the fundamental ideas and choices on which our approach is based. First, it identifies the needs of architects in the.
CASE Tools And Their Effect On Software Quality Peter Geddis – pxg07u.
Lecture 7: Objects and Interaction 1  Principles of Interactive Graphics  CMSCD2012  Dr David England, Room 718,  ex 2271 
Chapter 2: Understanding and conceptualizing interaction Question 1.
PROGRAMMING LANGUAGES The Study of Programming Languages.
Understand the sequence of oral presentation assignment components Learn how to develop explanations for assigned material –Listen to lecture on Rowan.
Results-Based Management
Brandon Graham Putting The Practices Into Action March 20th.
Copyright © 2013 Curt Hill The Zachman Framework What is it all about?
Team Skill 6: Building the Right System From Use Cases to Implementation (25)
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.
Design, prototyping and construction CSSE371 Steve Chenoweth and Chandan Rupakheti (Chapter 11- Interaction Design Text)
Software Requirements Presented By Dr. Shazzad Hosain.
Protocols for Mathematics Performance Tasks PD Protocol: Preparing for the Performance Task Classroom Protocol: Scaffolding Performance Tasks PD Protocol:
Secure Systems Research Group - FAU Classifying security patterns E.B.Fernandez, H. Washizaki, N. Yoshioka, A. Kubo.
Using Commtap Communication Targets and Activities Project.
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.
Oct 14, 2001OOPSLA’01- DSVL1 Experiences with Visual Programming Languages for End-Users and Specific Domains Philip T. Cox Trevor J. Smedley Dalhousie.
Decision Support Systems MGMT Summer 2012 Night #7, Part 2 somewhat based on Chapter 12.
AVI/Psych 358/IE 340: Human Factors Interfaces and Interaction September 22, 2008.
1 Systems Analysis and Design in a Changing World, Thursday, January 18, 2007.
Assignment Paired Prototyping Some content based on GDC 2006, Gingold and Hecker Brent M. Dingle 2014 Game Design and Development Program Mathematics,
Understanding and conceptualizing interaction
1 5 Nov 2002 Risto Pohjonen, Juha-Pekka Tolvanen MetaCase Consulting AUTOMATED PRODUCTION OF FAMILY MEMBERS: LESSONS LEARNED.
Chapter 2: Understanding and conceptualizing interaction.
Towards a Pattern Language for User Interface Design
Software Engineering Design & UML.
Understanding Users Cognition & Cognitive Frameworks
ECE450 - Software Engineering II1 ECE450 – Software Engineering II Today: Introduction to Software Architecture.
Differentiation PLC.
Chapter 6 – Architectural Design Lecture 1 1Chapter 6 Architectural design.
Conceptual Model Design Informing the user what to do Lecture 10 Gabriel Spitz 1.
Architecture View Models A model is a complete, simplified description of a system from a particular perspective or viewpoint. There is no single view.
CSE 303 – Software Design and Architecture
ANU comp2110 Software Design lecture 8 COMP2110 Software Design in 2004 lecture 8 Software Architecture 1 of 2 (design, lecture 3 of 6) Goal of this small.
Learning Objectives Understand the concepts of Information systems.
CMC Conceptualization Spring General The term computer-mediated communication refers to both task-related and interpersonal communication conducted.
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.
RUBRICS AND SCALES 1. Rate yourself on what you already know about scales. Use the scale below to guide your reflection. 2.
William H. Bowers – Conceptual Design and Architecture Torres 11.
Conceptual Model Design Informing the user what to do Lecture 10a Gabriel Spitz 1.
Process 4 Hours.
Chapter 2 Understanding and conceptualizing interaction
How to think about interaction
Imran Hussain University of Management and Technology (UMT)
Spreadsheet Engineering
Good and Bad Interfaces
CS 321: Human-Computer Interaction Design
Models, Metaphor, Paradigms
Comp 15 - Usability & Human Factors
Presentation transcript:

Conceptual Models

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

From David Liddle The most important thing to design is the conceptual model. Everything else should be subordinated to making that model clear, obvious and substantial. That s almost the opposite of how most software is designed (Liddle, 1996, p.17)

What is a conceptual model? It is NOT a description of the user interface It is an abstraction (structure) that outline what people can do with a product and what concepts are needed to understand how to interact with it.

Why a conceptual model is needed? Why not start with the nuts and bolts of design? –Architects and interior designers would not think about which colour 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

Conceptual models help 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 of a conceptual model 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

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

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

Compare the conceptual models for Visicalc and the star interface 1.What similarities do they share in their use of analogy and core concepts? 2. How do they differ? Activity Text p 53

Summary points A conceptual model is a high-level description of a product – what users can do with it and the concepts they need to understand how to interact with it Decisions about conceptual design should be made before commencing any physical design Interface metaphors are commonly used as part of a conceptual model