User System Interface CSC 8570-001 Fall 2010 Instructor: Robert E. Beck.

Slides:



Advertisements
Similar presentations
Graphical input techniques
Advertisements

By: Rachel Hall and Amy Austin.  Grade: All levels  Price  Host App: $24.99  Student App: free (allows up to 32 students)  Location: App Store 
Human Computer Interaction CSC User System Interface CSC Fall 2012 Instructor: Robert E. Beck.
Welcome to the seminar course
Human Computer Interaction CSC User System Interface CSC Meeting 2 September 4, 2012.
Project Proposal.
CS305: HCI in SW Development Evaluation (Return to…)
Copyright © 2006 by The McGraw-Hill Companies, Inc. All rights reserved. McGraw-Hill Technology Education Copyright © 2006 by The McGraw-Hill Companies,
Department of Computer Science
XP Exploring the Basics of Microsoft Windows XP1 Exploring the Basics of Windows XP.
What is Interaction Design?. What is interaction design? Designing interactive products to support people in their everyday and working lives –Sharp,
213: User Interface Design & Development Professor: Tapan Parikh TA: Eun Kyoung Choe
Ch 7 & 8 Interaction Styles page 1 CS 368 Designing the Interaction Interaction Design The look and feel (appearance and behavior) of interaction objects.
James Tam CPSC 481 Foundations and Principles of Human Computer Interaction James Tam.
10th Workshop "Software Engineering Education and Reverse Engineering" Ivanjica, Serbia, 5-12 September 2010 First experience in teaching HCI course Dusanka.
Irwin/McGraw-Hill Copyright © 2000 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS5th Edition.
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.
INTRODUCTION. Concepts HCI, CHI Usability User-centered Design (UCD) An approach to design (software, Web, other) that involves the user Interaction Design.
Software Engineer Report What should contains the report?!
TECHNOLOGY FOR TEACHING AND LEARNING Dr. Fedro ZazuetaDr. Fedro Zazueta.
Chapter 12 Designing Interfaces and Dialogues
 At the end of this class, students are able to  Describe definition of input devices clearly  List out the examples of input devices  Describe.
Operating Systems Chapter 4.
1. Learning Outcomes At the end of this lecture, you should be able to: –Define the term “Usability Engineering” –Describe the various steps involved.
CS110/CS119 Introduction to Computing (Java)
Human Computer Interaction Semester 1, 2013/2013.
Systems Analysis and Design in a Changing World, 6th Edition
HCI Research Project. Research Paradigms Theoretical (in the style of mathematics) –Mathematical deduction –Simulation –Analysis of algorithms The researcher:
CS378 - Mobile Computing App Project Overview. App Project Teams of 2 or 3 students Develop an Android application of your choosing subject to instructor.
CS 580 chapter 4 paradigms.
HCI Research Project. Research Paradigms Theoretical (in the style of mathematics) –Mathematical deduction –Simulation –Analysis of algorithms Experimental.
User System Interface CSC Spring 2009 Instructor: Robert E. Beck.
Output and User Interface Design
Explain the purpose of an operating system
1 CSCI E-170: L01 February 2, Lecture Plan Introduction to this class Introduction to usability GUI usability: Design Process, Principles & Bloopers.
CS CS 5150 Software Engineering Lecture 11 Usability 1.
User System Interface CSC Fall 2007 Instructor: Robert E. Beck.
Proposal for Term Project J. H. Wang Mar. 2, 2015.
Chapter 1 Historical Perspective. Significant Event Timeline 2.
Output Design. Output design  Output can be: Displayed on a screen/VDU/monitor. Printed on paper as hard copy. Sound.
Human Computer Interaction CSC User System Interface CSC Class Meeting 7 October 9, 2012.
Man and Machine: Introduction to HCI (MMI). Contents HCI: Introduction Design Rules: – Guidelines – Principles – Theories 2.
CS2003 Usability Engineering Usability Evaluation Dr Steve Love.
COLLECTING Software. Why use Software with Hardware? Software used for collecting includes the software that interfaces with hardware collection device.
COMPSCI 705 / SOFTENG 702 Exam Review Lecture Jim Warren Professor of Health Informatics Course coordinator CS705/SE702.
CSC USI Class Meeting 3 January 23, 2009.
C OMPUTING E SSENTIALS Timothy J. O’Leary Linda I. O’Leary Presentations by: Fred Bounds.
SD1230 Unit 6 Desktop Applications. Course Objectives During this unit, we will cover the following course objectives: – Identify the characteristics.
COMPUTER SOFTWARE FORM 1. Learning Area Introduction to computer software Operating System (OS) Application Software Word Processing Software Presentation.
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.
HCI Meeting 1 Thursday, August 26. Class Activities [1] Student questionnaire Answer the following questions: 1.When and where was the computer mouse.
MICROSOFT OFFICE APPLICATIONS Computer Basics 1.6.
Computer Operating Systems And Software applications.
Introduction to Human Factors in Information Systems Dr. Cindy Corritore Creighton University ITM 734 Fall 2005.
PartII. Key M&E requirements:  Specification of information requirements  What exactly do the decision makers want to know about the project?  For.
© 2011 DigitalDay | MOBILE WEB INFORMATION ARCHITECTURE Best Practices Workshop 1.
Chapter 1 Historical Perspective
CIS 375Competitive Success/tutorialrank.com
CIS 375 Education for Service-- tutorialrank.com.
Chapter 1 Historical Perspective
Chapter 1 Historical Perspective
CSC USI Class Meeting 2 August 30, 2006.
User System Interface CSC
HUMAN COMPUTER INTERACTION. The main aims of the chapter are to: Explain the difference between good and poor interaction design. Describe what interaction.
User/System Interface CSC
User/System Interface CSC
Presentation transcript:

User System Interface CSC Fall 2010 Instructor: Robert E. Beck

Introductions (1)  Information sheet Information sheet Information sheet  Questionnaire: student information  Questions 1.Who invented the computer mouse? When? Where? 2.What battery operated devices do you have with you tonight? 3.What (computer-based) POS systems do you typically encounter as a customer in a standard week? 4.What process would you use to find the latitude and longitude of the statue of Gregor Mendel on the plaza in front of the Mendel Science Center?

Introductions (2)  Name  If working –For what company? –In what capacity?  If a full-time student –Plans after graduation  Describe the user interface of the first computer you used.

Battery Operated Devices  Cell phone  Watch  Calculator  Laptop  iPod  Remote car key  Bluetooth headset  iPhone, droid, Blackberry, windows mobile  Remote house security  Flashlight  Laser pointer  Pedometer

Goals  Developing design principles  Investigating models and theories  Creating evaluation processes –Experimentation –Opinion  Outlining an effective design process—interface engineering  Proposing interface designs

Themes (1)  Hierarchy of design principles  Models  Theories (or theory)  Awareness –Mental models –Common interactions –Microsoft vs. Apple vs. others –General knowledge

Themes (2)  Multidisciplinary approach  Frontiers of HCI  Definitions, use of words  Examples

Strategies (Ways of Knowing)  Create concept maps for reading assignments –Combine individual maps  Slip-of-paper (SOP) questions and surveys –Summarize results  Lectures, sometimes  Discussion, always  Argumentation, when appropriate

Strategies (2)  Examples  Careful reading of research and survey articles  PowerPoint as a guide –Edited during class –Posted after class on course web site

Activities  Research project –Report –Presentation –Poster  Article presentation  Web-based project  Exercises  Experiments  Exam – in two parts –Second part: December 14

Responsibilities  Attendance  Reading  Team support  Dialog with classmates and instructor

Hot Topics Burning Questions Time for your thoughts  Pair up by twos  For the next few minutes, write down as many issues or problems in user- system interaction as you can.

Issue Summary  How do we do this?

Hot Areas; Burning Issues The List  Errors made through inadvertent gestures, e.g. iPad, Wii  Bad default choices; not checking device properties, e.g. zoom setting  Discrepancies between presentation and function, e.g. bad choice of icons  Error cost of wrongly pressed, chosen widgets.  Non-intuitive interfaces to systems, e.g. synching iPod and iTunes  System time-outs  Discoverability of functionality, especially advanced features  Foreshadowing completion of tasks

Hot Topics: Others’ Ideas  CHI 20XX topics CHI 20XX topics CHI 20XX topics  HCIL presentations HCIL presentations HCIL presentations  Interactions Interactions

Landscape of the Field  Taxonomy  Ontology

Sources  ACM Digital Library  Conference proceedings (MSC 159)  The Web—but be careful  The course web site course web sitecourse web site  University HCI labs, e.g. –U of Maryland  Popular press –Information Week –Financial Times  Falvey Library reference desk

Sources (2)  Steve Krug, Don’t Make Me Think: A Common Sense Approach to Web Usability, 2 nd Edition  Jeff Johnson, GUI Bloopers 2.0: Common User Interface Design Don'ts and Dos  Jakob Nielsen, Designing Web Usability

Contacts  PhillyCHI – Philadelphia region chapter of SIGCHI PhillyCHI  SIGCHI – ACM Special Interest Group on Computer Human Interaction SIGCHI

Conferences  ACE – Computer Entertainment Technology  AVI – Advanced Visual Interfaces  CHI – Computer Human Interaction  CSCW – Computer Supported Cooperative Work  DSV-IS  HCI International  HCIL Symposium (U Maryland) HCIL Symposium (U Maryland) HCIL Symposium (U Maryland)  HICS  Hypertext

Conferences (2)  IDC  Interact  IUI – Intelligent User Interfaces  IVA  SG – Smart Graphics  SIGIR – Information Retrieval  UIST – User Interface Software Technology  User Modeling  World Wide Web

Tools  Concept maps: –  EndNote  Task models: –ConcurTaskTrees Environment ConcurTaskTrees EnvironmentConcurTaskTrees Environment  Help compiler  Treemap: – history/ history/ history/

Tools (2)  UISK: User Interface Sketching Tool UISK: User Interface Sketching Tool UISK: User Interface Sketching Tool  NodeXL NodeXL

What Do We Mean when we write  USI  HCI  GUI  DMI  IUI  SUSI

What Do We Mean By  User  System  Interface  Human  Computer  Interaction  Graphical  Direct  Manipulation

Eras of HCI  Holes  Command lines  Menus and characters  Widget objects and bit maps  Small devices

iPad  A new small device  Issues of design and user interaction? –Discoverability of functionality –Easy to learn elementary functionality –Lack of multitasking, only single window –Keyboard design –Accidental gesture interpretation –Inconsistent interfaces across apps (extends to all software)

iPad(5) –Displaying non-mobile web sites –Pinch zoom –Scroll to end? –Is it trying to be a computer?

What to Study: Potential Topics  Tiny interfaces: Cell phones, smartphones, PDAs, ultramobile PCs, house systems, POS systems  Gesture-based input; pen interfaces  Intelligent interfaces (cf. IUI)  Task analysis (e.g. buying a ticket)  Collaboration tools/systems (cf. CSCW)  Personalization; recommender systems  Friendly forms  Creating digital libraries  Mashup tools  Web-based interfaces to systems, to information, for task completion

Reading a Research Paper  Expect to find –Abstract –Introduction –Description of experiment –Discussion of results –Conclusion –Proposals for future work –References

Reading (2)  Try the abstract—though it may be too abstract, too condensed.  Read the introduction until you get confused.  Read the conclusion.  Look at the reference list—hoping to find papers you already know about.  Check the headings and first few lines of the middle sections for ease of understanding.

Reading (3)  Examples: –Mackenzie: Unipad text entry Mackenzie: Unipad text entryMackenzie: Unipad text entry –Soukoreff and Mackenzie: Metrics for text entry errors Soukoreff and Mackenzie: Metrics for text entry errorsSoukoreff and Mackenzie: Metrics for text entry errors

Next Time  Read Wigdor & Balakrishnan, Tilt Text: using tilt for text input to mobile phones. (You can get a copy of the paper from the ACM Digital Library.)  Evaluate its structure and content as a research paper.  Identify design principles for user interfaces based on the paper.  Hand in your solution to the table exercise. table exercise.table exercise.

Next Time (2)  Install EndNote on your computer and record the references from the Wigdor paper in it. –EndNote has been available for loan from the library. Check with the Reference Desk  Install the CMAP software on your computer and capture the principal ideas of today’s lecture in it.

Next Time (3)  What is the difference between taxonomy and ontology?  How is the field of HCI divided?