Today Next time  Interaction Reading: ID – Ch 2 Interaction  Introduction to HCI & Interaction Design Reading: ID – Ch. 1 CS 321 Human-Computer Interaction.

Slides:



Advertisements
Similar presentations
Chapter 5 Development and Evolution of User Interface
Advertisements

Chapter 9 User-centered approaches to interaction design By: Sarah Obenhaus Ray Evans Nate Lynch.
Ch.6: Requirements Gathering, Storyboarding and Prototyping
©2001 Southern Illinois University, Edwardsville All rights reserved. Today Tuesday Consolidation Reading: CD Ch.s 8, 9, & 10 Modeling & Interpretation.
AN OVERVIEW BY JAMIE STARKE The Role of Prototyping.
User Interface Design Notes p7 T120B pavasario sem.
COMP 6620 Chapter Presentation Karthik Vemula. Agenda:-  User Centered Approach  Basic Activities of Interaction Design.  In Class Assignment.
IS214: Needs Assessment and Evaluation Introduction to Usability Assessment.
Information & Interaction Design Fall 2005 Bill Hart-Davidson Session 7: teams present research plan + a sequence diagram from phase 2 homework; Affinity.
1 User Centered Design and Evaluation. 2 Overview Why involve users at all? What is a user-centered approach? Evaluation strategies Examples from “Snap-Together.
Information & Interaction Design Fall 2005 Bill Hart-Davidson Session 6: analyzing work practices – rationale and challenges; the 5 Contextual Design work.
Identifying needs and establishing requirements Chapter 7b.
Course Wrap-Up IS 485, Professor Matt Thatcher. 2 C.J. Minard ( )
Team Project IS 485, Professor Matt Thatcher. 2 Agenda l Review l Team project –project overview –team feedback –milestones l Questions?
Contextual Design. Purpose for us An example A term often used, with varying levels of precision.
User-centered approaches to interaction design. Overview Why involve users at all? What is a user-centered approach? Understanding users’ work —Coherence.
DESIGNING FOR USABILITY – USER CENTERED DESIGN Presentation by Carlos Jensen, Phd.
1 User Centered Design and Evaluation. 2 Overview My evaluation experience Why involve users at all? What is a user-centered approach? Evaluation strategies.
INTRODUCTION. Concepts HCI, CHI Usability User-centered Design (UCD) An approach to design (software, Web, other) that involves the user Interaction Design.
CS 3724: Introduction to Human Computer Interaction Chris North Jason Lee Szu-Chia Lu.
Joy Hamerman Matsumoto.  St Jude Medical Cardiac Rhythm Management Division manufactures implantable cardiac devices ◦ Pacemakers ◦ Implanted defibrillators.
Human Interface Engineering1 Main Title, 60 pt., U/L case LS=.8 lines Introduction to Human Interface Engineering NTU Seminar Amy Ma HIE Global Director.
Requirements Elicitation. Requirement: a feature or constraint that the system must satisfy Requirements Elicitation: specification of the system that.
Can Programmers do Course Design?. The Programmer.
SBD: Activity Design Chris North CS 3724: HCI. Problem scenarios summative evaluation Information scenarios claims about current practice analysis of.
Ibrahim A. Atoum Portable-02, Room-03 University of Hail, KSA
Introduction to SDLC: System Development Life Cycle Dr. Dania Bilal IS 582 Spring 2009.
ACTIVITY. THE BRIEF You need to provide solid proof to your stakeholders that your mobile website meets the needs of your audience. You have two websites.
1 REQUIREMENT ENGINEERING Chapter 7. 2 REQUIREMENT ENGINEERING Definition Establishing what the customer requires from a software system. OR It helps.
Computer –the machine the program runs on –often split between clients & servers Human-Computer Interaction (HCI) Human –the end-user of a program –the.
Teaching Human-Computer Interaction Using Participatory Design Methods Dr. Jerry Weinberg, SIUE Dr. Mary Stephen, SLU Ms. Kristin Caufield Supported by.
S556 SYSTEMS ANALYSIS & DESIGN Week 11. Creating a Vision (Solution) SLIS S556 2  Visioning:  Encourages you to think more systemically about your redesign.
Today Thursday Introduction to HCI and Contextual Design Course Introduction CS 321 Human-Computer Interaction Jerry B. Weinberg Reading: CD: Chapter.
Integrating Usability Engineering and Agile Software Development: A Literature Review 陳振炎教授 楊哲豪
Usability testing. Goals & questions focus on how well users perform tasks with the product. – typical users – doing typical tasks. Comparison of products.
HCI in Software Process Material from Authors of Human Computer Interaction Alan Dix, et al.
SBD: Activity Design CS HCI Chris North Usability Engineering - Chapter 3.
Lecture 7: Requirements Engineering
©2001 Southern Illinois University, Edwardsville All rights reserved. Today Interview Techniques (Hand-in partner preferences) Thursday In-class Interviewing.
1 Introduction to Software Engineering Lecture 1.
©2001 Southern Illinois University, Edwardsville All rights reserved. Today System Design & Putting it Together Reading: ABF: Ch. 9 CD Ch.s 14, 15, 16,
Mario Čagalj University of Split 2014/15. Human-Computer Interaction (HCI)
SBD: Analyzing Requirements Chris North CS 3724: HCI.
SBD: Activity Design CS HCI Chris North Usability Engineering - Chapter 3.
©2001 Southern Illinois University, Edwardsville All rights reserved. CS 321 Human-Computer Interaction Today Consolidation Reading: CD Ch.s 8, 9, & 10.
Z556 Systems Analysis & Design Session 10 ILS Z556 1.
©2001 Southern Illinois University, Edwardsville All rights reserved. CS 321 Human-Computer Interaction Today Course Introduction Wednesday Introduction.
SBD: Activity Design Chris North cs3724: HCI. Problem scenarios summative evaluation Information scenarios claims about current practice analysis of stakeholders,
©2001 Southern Illinois University, Edwardsville All rights reserved. Today Wednesday Running A Paper Prototyping Session Paper Prototyping Video: Paper.
©2001 Southern Illinois University, Edwardsville All rights reserved. Today Putting it in Practice: CD Ch. 20 Monday Fun with Icons CS 321 Human-Computer.
©2001 Southern Illinois University, Edwardsville All rights reserved. CS 321 Human-Computer Interaction Today Design from Data Reading: CD Ch. 11, 12,
User Interface Evaluation Introduction Lecture #15.
Today Discussion Follow-Up Interview Techniques Next time Interview Techniques: Examples Work Modeling CD Ch.s 5, 6, & 7 CS 321 Human-Computer Interaction.
©2001 Southern Illinois University, Edwardsville All rights reserved. Today Tuesday Contextual Inquiry & Intro to Ethnography Introduction to HCI & Contextual.
SBD: Analyzing Requirements Chris North cs3724: HCI.
©2001 Southern Illinois University, Edwardsville All rights reserved. Today System Design: Reading: CD Ch.s 14, 15, &16 Monday Midterm CS 321 Human-Computer.
William H. Bowers – Requirements Torres 9.
Supporting the design of interactive systems a perspective on supporting people’s work Hans de Graaff 27 april 2000.
©2001 Southern Illinois University, Edwardsville All rights reserved. Today Tuesday CS 321 Human-Computer Interaction Paper Prototyping Video: Paper Prototyping.
6.S196 / PPAT: Principles and Practice of Assistive Technology Wed, 19 Sept Prof. Rob Miller Today: User-Centered Design [C&H Ch. 4]
CS 3724: Introduction to Human Computer Interaction Chris North Regis Kopper.
©2001 Southern Illinois University, Edwardsville All rights reserved. Today Thursday Consolidation Reading: CD Ch.s 8, 9, & 10 In-class modeling exercise.
Introduction to System Evaluation IS 588 Dania Bilal & Lorraine Normore Spring 2007.
User-centered approaches to interaction design By Haiying Deng Yan Zhu.
Stanford hci group / cs October 2007 An Overview of Design Process Scott Klemmer tas: Marcello Bastea-Forte, Joel Brandt,
CS 321: Human-Computer Interaction Design
SBD: Analyzing Requirements
SBD: Analyzing Requirements
CS 321 Human-Computer Interaction
User-centered approaches to interaction design
Presentation transcript:

Today Next time  Interaction Reading: ID – Ch 2 Interaction  Introduction to HCI & Interaction Design Reading: ID – Ch. 1 CS 321 Human-Computer Interaction

 Why is it so difficult to create a schedule on Student Information System (SIS)? SMITH, JOHN E

The System’s Work Model does not fit the User’s Work Model  Any system forces a specific way for tasks to be done  System’s Work Model  Every user has an understanding of how a task should be done  Conceptual Model, Mental Model  For applications like the SIS the system’s model is hard to understand and work with because it makes no sense in terms of the work being done.  Causes errors, non-use

What is Design?  Design is a creative activity of making artifacts that are usable for a specific purpose.  Software Engineer  Software is reliable, robust, and maintainable  Software Designer  Software fits the user’s overall activities, enhances productivity, and produces a satisfying experience (Enjoyable!)

User’s Task Model vs. Engineer’s Model  User’s task model A representation of the user’s conceptual model  Main Goal: Make the Engineer’s model invisible to the user.  Engineer’s model Underlying implementation Linkages

From the Interface Hall of Shame The program, Woodworkers Estimate Helper provides a classical example of geekspeak. The program is “designed for woodworkers and cabinet makers”, and purports to assist in the process of calculating price quotes for their projects. Unfortunately the program uses such programming terminology as “Databases”, “Records”, and, if the user attempts to enter a duplicate part name, presents the message “Key Validation Error”. While we do not mean to disparage any woodworkers, we can quite confidently state that the typical woodworker has essentially no practical understanding of such terms, nor should they be required to. Is it any wonder that many new users are intimidated by computers?

System Centered vs. Customer Centered Design  System Centered Design  Focuses on organizing the functionality of the system  Customer Centered Design  Focuses on the customer’s conceptual model  Participatory Design, User-Centered Design, Human-Centered Design

Customer Centered Design Interject the designer in the user’s world and the user in the designer’s world to develop a shared conceptual model

Contextual Design (CD)  Gather data from multiple users  Design depends on seeing the implications of the data  Design begins with a creative leap from customer data to implications for design and from implications to ideas for specific features  Abstract data into a common model

Steps in Contextual Design  Contextual Inquiry  Work Modeling  Consolidation  User Environment Design  Interface Design and Prototyping  Work Redesign

Step 1 - Contextual Inquiry  Gather Data  Observation  Interview  Participation  “Shadowing”  Learn User’s Vocabulary  Gather Artifacts  Gain an understanding of the user

Step 2 – Work Modeling  Concrete Representations  User’s activities  Context of the work  Team Interpretation Sessions  Shared understanding

Step 3 - Consolidation  Look across multiple users  Common practices  Divergent practices  Inductive Process  Going from a few to a large population

Step 4 – Work Redesign  Don’t just automate  Look for places to improve  Visioning  Brainstorming sessions  Creative process

Step 5 – User Environment Design  Explicit representation of the system work model  “Blue Print” for the User Interface Design

Step 6 – Interface Design & Prototyping  Paper Prototyping  Lo-fidelity prototype  Communicate design with the user