Introduction to Usability Engineering CS 352 Winter 2015 1.

Slides:



Advertisements
Similar presentations
Observing Users CS352. Announcements See syllabus for upcoming due dates. 2.
Advertisements

Introduction to Usability Engineering CS 352 Winter
Human Capabilities: Mental Models CS352. Announcements Notice upcoming due dates (web page). Where we are in PRICPE: –Predispositions: Did this in Project.
AN OVERVIEW BY JAMIE STARKE The Role of Prototyping.
From requirements to design
Concepts and Prototypes
Evaluation (cont.): Heuristic Evaluation Cognitive Walkthrough CS352.
Before usability CS 147: Intro to HCI Dan Maynes-Aminzade After 1 st Usability Review.
Design Analysis of Everyday Objects IS 485, Professor Matt Thatcher.
Designing CS 352 Usability Engineering Summer 2010.
User-Centered Design (UCD) CS 352 Usability Engineering Summer 2010.
Midterm Exam Review IS 485, Professor Matt Thatcher.
Review of last lecture 1.Norman’s 2 Gulfs are… – Gulf of Execution and Gulf of Evaluation 2.Goals of usability engineering include… – Effectiveness, safety,
CS147 - Terry Winograd - 1 Lecture 9 – Prototyping Terry Winograd CS147 - Introduction to Human-Computer Interaction Design Computer Science Department.
Usability 2004 J T Burns1 Usability & Usability Engineering.
From Controlled to Natural Settings
INTRODUCTION. Concepts HCI, CHI Usability User-centered Design (UCD) An approach to design (software, Web, other) that involves the user Interaction Design.
Usability 2009 J T Burns1 Usability & Usability Engineering.
Improving the customer experience on a council website The journey from 1 star to 4 star.
Introduction to Usability Engineering CS 352 Winter
PROJECT #4 Design Heejoon Jung Kyu Hou Eunyoung Cho Minho Jeung.
Design Chris North cs3724: HCI. Quiz What are the 3 steps in producing a UI?
CSCD 487/587 Human Computer Interface Winter 2013 Lecture 3 HCI and Interactive Design.
Formative Evaluation cs3724: HCI. Problem scenarios summative evaluation Information scenarios claims about current practice analysis of stakeholders,
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 7: Focusing on Users and Their Tasks.
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.
Software Design Experiences 2009, adapted from d.school.bootcamp.2008 DP 0 The Wallet Project.
Reflection-in-action CS 352 Summer Why reflection-in-action? PRICPE is great! …but how do I carry out each step of it, e.g., Prototyping? Reflection-in-action.
Interaction Design John Kelleher. Interaction Design “Designing interactive products to support people in their everyday and working lives” Software.
Chapter 1: What is interaction design?. Bad designs From:
Interaction Design: Overview
Observing Users CS352 Usability Engineering Summer 2010.
The Emotion Quiz Cecelia Redding Erika Zimmermann Jeff Crowe Torben Eisler.
Concepts and Prototypes CS352. Announcements Notice upcoming due dates (web page). Where we are in PRICPE: –Predispositions: Did this in Project Proposal.
Evaluation (cont.): Heuristic Evaluation Cognitive Walkthrough CS352.
Interacting with consumer Software Engineering. So far… What is Software Engineering? Different software process models waterfall, incremental, spiral.
Before usability CS 147: Intro to HCI After 1 st Usability Review.
Choreography Assistant Human Computer Interaction - April 6, 2004 Choreography Assistant.
Use the cards to control the lecture… Usability Design.
“Problem Solving Process” 6 th grade Written by Sony Gala.
Learning about your users (cont.).: The field interview CS 352 Usability Engineering Summer 2010.
Technological Design VS Engineering Design. Technological design and Engineering design are very similar and sometimes the terms are often confused with.
Concepts and Prototypes
Introduction to Usability Engineering
Digital media & interaction design
Technological Design VS Engineering Design
SysML V2: User-Centered Design Approach
Analytical Evaluation with GOMS and KLM
Design, prototyping and construction
A Design Process.
Evaluation (cont.): Cognitive Walkthrough and Heuristic Evaluation
Introduction to HCI CS 565.
Introduction to Usability Engineering
Evaluation - Analytical Cognitive Walkthrough and Heuristic Evaluation
Problem Travel in urban environments requires real-time, reliable, and situation-specific transit information Solution Take Me There uses activity-sensing.
Introduction to Usability Engineering
DP The Wallet Project d.school.bootcamp.2008.
Engineering Innovation
Human Capabilities: Mental Models
Evaluation Types CS352.
Computer Science Department
Introduction to Usability Engineering
After 1st Usability Review
Formative Evaluation cs3724: HCI.
Introduction to Usability Engineering
Evaluation - Analytical Cognitive Walkthrough and Heuristic Evaluation
Evaluation - Analytical Cognitive Walkthrough and Heuristic Evaluation
Evaluation (cont.): Empirical Studies: The Thinkaloud
Design, prototyping and construction
Presentation transcript:

Introduction to Usability Engineering CS 352 Winter

HW #1 and Design Principles Visibility of user’s options/actions. Feedback Constrain –(making certain errors impossible) –eg: menus vs typing to prevent syntax errors. (Internal) consistency Affordance –makes clear HOW I can do things with an object 2

Design Activities: Mapped to PRICPE Process Process activities (See ch. 1) –Identify needs/requirements of the user experience. –Develop alternative design ideas that meet the requirements. –Build prototypes of the designs to communicate/assess. –Evaluate iteratively throughout the process. 3 Pre-dispositions Research Insights Concept Prototype Evaluate

In-Class Design Activity Split up into groups of 4-5. You have until 11:30 to design: –An on-line “virtual” grocery. Order from home, food arrives. How: Use PRICPE process. –Write all your names on the top of the PAPER. –Write any lists/notes (1 st P) on PAPER. In this activity, we’ll skip R, but you might get a few Insights from group discussion. –Pick a population & device(s). –When you’re ready, SKETCH Concepts/Prototypes on PAPER. –Be ready to argue for why your solution would work for that device/population –Aim for creative, interesting, useful solutions –Goal: hands-on practice with the design process. We’ll look at a few with the doc scanner. 4