User/System Interface

Slides:



Advertisements
Similar presentations
Chapter 12 cognitive models.
Advertisements

Human Computer Interaction CSC User System Interface CSC Class Meeting 6 October 2, 2012.
Group Project CVEN Mixing and Transport in the Environment. A River Dye Study.
Chapter 2: Understanding and conceptualizing interaction
Chapter 1 Program Design
CSC USI Class Meeting 2 August 31, Beginnings SOP 1: 1. When you use a (physical) key-based entry device, what do you do to the keys? A.
CSC USI Class Meeting 4 September 14, 2010.
1 CGS1060 Mobile UIs Copyright 2012 by Janson Industries.
Architectural Design.
Human Computer Interaction CSC User System Interface CSC Class Meeting 4 September 18, 2012.
©2011 1www.id-book.com Analytical evaluation Chapter 15.
Chapter 2: Understanding and conceptualizing interaction Question 1.
HCI Research Project. Research Paradigms Theoretical (in the style of mathematics) –Mathematical deduction –Simulation –Analysis of algorithms The researcher:
Your personal Display Section Presence notes Display Picture & ‘Indicator’ Contacts Activity Feeds Conversations Phone Options Your Location Your Presence.
HCI Research Project. Research Paradigms Theoretical (in the style of mathematics) –Mathematical deduction –Simulation –Analysis of algorithms Experimental.
The ID process Identifying needs and establishing requirements Developing alternative designs that meet those requirements Building interactive versions.
Ch 14. Testing & modeling users
Human Computer Interaction CSC User System Interface CSC Class Meeting 5 September 25, 2012.
HCI Meeting 3 Thursday, September 2. Class Poll What does the word interface mean in the context of HCI and user-system interface design? What verb should.
Human Computer Interaction CSC User System Interface CSC Class Meeting 7 October 9, 2012.
© 2012 xtUML.org Bill Chown – Mentor Graphics Model Driven Engineering.
Chapter 2.2 Game Design. CS Overview This introduction covers: –Terms –Concepts –Approach All from a workaday viewpoint.
CSC USI Class Meeting 3 January 23, 2009.
Prezi is a flash-based presentation software and storytelling tool for exploring and sharing ideas upon a virtual canvas.presentation software storytelling.
CSC USI Class Meeting 5 September 21, 2010.
Understanding and using patterns in software development EEL 6883 Software Engineering Vol. 1 Chapter 4 pp Presenter: Sorosh Olamaei.
Task Analysis CSCI 4800/6800 Feb 27, Goals of task analysis Elicit descriptions of what people do Represent those descriptions Predict difficulties,
Cognitive Dimensions  Developed by Thomas Green, Univ. of Leeds  Used to analyze the usability of information artifacts  Applied to discover useful.
CSC USI Class Meeting 10 November 9, 2010.
CSC USI Class Meeting 6 October 5, Outline for Evening One-minute assessment Research project issues Table creation revisited Augmenting.
CSC USI Meeting 8 October 26, Designing the Perfect Phone™ Meet as design teams this evening Interim design report due by 9:00 p.m. EDT.
CSC USI Class Meeting 9 October 31, 2007.
Administrivia  Feedback from the mid-term evaluation  Insights from project proposal.
CSC USI Class Meeting 4 September 13, 2006.
HCI Meeting 1 Thursday, August 26. Class Activities [1] Student questionnaire Answer the following questions: 1.When and where was the computer mouse.
Introduction to the course Aug 30, Day 1 Object-oriented Programming thru Video Games TIDE 1840 Harry Howard Tulane University.
Cognitive Dimensions  Developed by Thomas Green and Alan Blackwell  Enhanced by Marian Petre Marian PetreMarian Petre  Descriptions of aspects, attributes,
Class Meeting 3 September 7, 2010
General System Navigation
How to think about interaction
Human Computer Interaction Lecture 23 Cognitive Models
Human Computer Interaction
Task Analysis CSCI 4800/6800 Feb 27, 2003.
Sharing lessons through effective modelling
INF385G: Topic Discussion Huang, S. C.
CIS 376 Bruce R. Maxim UM-Dearborn
FOP: Buttons and Events
Business in a Connected World
Writing for Academic Journals
Program and Graphical User Interface Design
Computer Programming.
The Design of Everyday Things
Class Meeting 5 February 10, 2009
CSC USI Class Meeting 2 August 30, 2006.
Chapter Four Engineering Communication
CS305, HW1, Spring 2008 Evaluation Assignment
Class Meeting 8 November 1, 2005
Chapter Four Engineering Communication
Chapter Four Engineering Communication
Cognitive models linguistic physical and device architectural
Testing & modeling users
Chapter 12 cognitive models.
Meeting 10 Tues, September 28
CSC USI Class Meeting 6 October 3, 2007.
Chapter 12 cognitive models.
User System Interface CSC
Chapter 8: Actor-System Interaction Modeling
User/System Interface CSC
User/System Interface
User/System Interface CSC
Presentation transcript:

User/System Interface Meeting 5 September 24, 2019

Deep Breath

Addressing Confusions Models, theories, frameworks of HCI : See summary at end of Meeting 4 slides More discussion this evening and in subsequent weeks Research project ideas Consider systems that frustrate you Scan the topics in one or more of the most recent conference proceedings Focus on small everyday systems: maybe those from the Internet of Things (IoT), maybe laptop and tablet apps that should be the same but aren’t, maybe tasks that take many actions and probably shouldn’t Research project logistics Waiting for clarification about Cayuse Use team members to help, post questions and doubts on piazza.com

Phrase Exercise Only 4 from the grammar had no meaning to anyone drag and drag move and drag drag twice move twice Conversely, you (as experts) agreed Tap is described by one phrase commonly chosen from the grammar Double tap is described by 8 phrases from the grammar Press and hold is described by 5 phrases from the grammar Press and drag is described by 1 phrase from the grammar

Phrase Exercise (2) The two-finger interactions: The only phrase that most everyone attached to an action, and that action was Pull together/Pull apart, was double press Conclusion: Describing actions in common terms is difficulty and should proceed from the interface view to the user view, rather than the other direction.

Research Project Short presentation One spokesperson At most five minutes long Research area, hypotheses, variables, initial experimental design Questions and comments from the audience Designed to help the teams improve their project plan

Research Teams Aspen: Jessica, Josh C Bailey: Anusha, Harsha, Jos, Taylor Conifer: Chaitanya, Josh B, Moulika Durango: Greeshma, Mounika, Vamsi Estes Park: Bhavan, Jarred, Sheshank Fairplay: Kowmundi, Nitin, Usha

Research Project Issues Add to bibliography – goal is at least 15 references Design experiment Create experimental tools Draft consent form using template from Office of Research Protections Complete IRB application on Cayuse by October 3 Are access issues resolved? Start writing Introduction and Background sections Note: Progress Report 1 due 10/22

Summary of Some Ideas User goals Mental models GUEPs Cognitive dimensions

User Goals Based on last week’s discussion and other sources, here’s a list of user goals (from the user’s viewpoint) Users want systems that: Are powerful, meaning fast and efficient Have proper functionality Minimize the possibility for (tragic) errors Allow easy recovery from misdirected actions Are easily learned and easily relearned

User Goals (2) Fit a cognitive model based on past experience Are easy to maintain, including setup Are flexible Stimulate creative problem solving Are personally satisfying

GUEPs and CDs GUEPs (Generative User Engineering Principles) CDs (Cognitive Dimensions)

Understanding Cognitive Dimensions What are they? Meaning from name Meaning from examples Meaning from their definitions Some are negative in that interfaces should not exhibit the property How can they be applied? To notation in an interface (text, icons) To representations of the interface components (widgets) To understanding of functionality

Relating GUEPs and CDs Match the 14 cognitive dimensions to the 9 GUEPs, looking for overlapping and orthogonal ideas. Summarize the results by creating a 14 by 9 array whose cell entries describe the relationship between the ith CD and the jth GUEP

Mental Models Viewed as theories: Constructed by humans Based on their world experience Derived from language, perception, or imagination What humans believe to be true about particular domains, devices, or systems

Mental Models (2) Viewed as problem spaces Mental structures (ideas, concepts, virtual worlds) Contain possible states Searchable, so that users can plan their behaviors (paths from one state to the next, converging on a solution)

A Lengthy Example: An MP Music players (MP) at the ready (iPod, Zune, app on a smart phone, …) What is your mental model of an MP? What do you believe to be true about an MP? How would you describe the problem space associated with an MP?

MP(2) What tasks do you want to accomplish with an MP? Described in high level terms For example, from a completely different context I want fresh tomatoes from my garden on my salad.

MP(3) What operators are available? Physical keys or widgets Virtual widgets on the interface What actions are required to interact with these widgets?

MP(4) What notation do we use for widget interaction? Do we need to expand the keystroke notations of Card & Moran K, H, P, M, Do we use Raskin & Beck expanded to include swipe? Or more?

MP(5) Preparing for task analysis Tasks vs. goals Hierarchical task analysis vs. GOMS ConcurTaskTrees http://hiis.isti.cnr.it/lab/research/CTTE/home From the Human Interfaces in Information Systems laboratory Example

ConcurTaskTrees Task Types Type Action Example User No system interaction Read a message Abstraction Complex User session Application No user interaction Perform a database query Interaction User and system together Click a button

ConcurTaskTrees Operators Unary Operators Icon Description Syntax * Iterative T1 * [ ] Optional [ T1 ] ⃖⃗ Connection T1 Temporal Operators Icon Description Syntax [ ] Choice T1 [ ] T2 |=| Order Independency T1 |=| T2 ||| Concurrent T1 ||| T2 |[ ]| Concurrent with information exchange T1 |[ ]| [> Disabling T1 [> T2 |> Suspend/Resume T1 |> T2 >> Enabling T1 >> T2 [ ]>> Enabling with information exchange T1 [ ]>>T2

Synthesizing Edge and Blackwell Referring to your concept map: What is its top-level concept? What is its structure? What is its shape?

Leave Behind Concept map of the Edge and Blackwell paper

For Next Time Next Time is Tuesday, October 8 For Tuesday, October 1, meet as research teams for an intensive writing session. One person writes; one dictates and checks; one works in parallel exploring the literature Or for an intensive programming session in which you develop your experimental materials. Also, catch up on your reading, including Shneiderman, et al, Chapter 5.