©2001 Southern Illinois University, Edwardsville All rights reserved. Today Putting it in Practice: CD Ch. 20 Monday Fun with Icons CS 321 Human-Computer.

Slides:



Advertisements
Similar presentations
Design, prototyping and construction
Advertisements

Affinity Diagrams.
Chapter 9 User-centered approaches to interaction design By: Sarah Obenhaus Ray Evans Nate Lynch.
Methods: Deciding What to Design In-Young Ko iko.AT. icu.ac.kr Information and Communications University (ICU) iko.AT. icu.ac.kr Fall 2005 ICE0575 Lecture.
©2001 Southern Illinois University, Edwardsville All rights reserved. Today Tuesday Consolidation Reading: CD Ch.s 8, 9, & 10 Modeling & Interpretation.
Requirements Engineering n Elicit requirements from customer  Information and control needs, product function and behavior, overall product performance,
Council International Study Programs Internet Site Design March 12, 2001.
IS 214 Needs Assessment and Evaluation of Information Systems Managing Usability © Copyright 2001 Kevin McBride.
Chapter 6 The Process of Interaction Design Presented by: Kinnis Gosha, Michael McGill, Jamey White, and Chiao Huang.
Usability Inspection n Usability inspection is a generic name for a set of methods based on having evaluators inspect or examine usability-related issues.
Heuristics  Basis  Evaluators –Qualifications –Training  Preparation –Scenario  Results –List of problems –Severity –Group synthesis.
Project Sharing  Team discussions –Share results of heuristic evaluations –Discuss your choice of methods and results  Class-level discussion –Each spokesperson.
Requirements Analysis Concepts & Principles
Heuristic Evaluation Evaluating with experts. Discount Evaluation Techniques  Basis: Observing users can be time- consuming and expensive Try to predict.
Evaluating with experts
Course Wrap-Up IS 485, Professor Matt Thatcher. 2 C.J. Minard ( )
Overview of Software Requirements
Usability 2004 J T Burns1 Usability & Usability Engineering.
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.
1 Contextual Interview Shahnewaz A. Jolly CPSC 681: Research Methods in Human Computer Interaction Instructor: Dr. Saul Greenberg Date: November 4, 2009.
1 Requirements Elicitation Slinger Jansen. 2  1. Motivation  2. Requirements  3. Continuous RE  4. The RE Framework  7. Fundamentals of Goal Orientation.
Customer Focus Module Preview
Database System Development Lifecycle © Pearson Education Limited 1995, 2005.
Overview of the Database Development Process
Z556 Systems Analysis & Design Session 9 ILS Z556 1.
William H. Bowers – Modeling Users: Personas and Goals Cooper 5.
Requirements Analysis
Presentation: Techniques for user involvement ITAPC1.
Visioning ITM 734 Fall 2006 Corritore. 2 Visioning Goal – to create a vision of how your system will support your users’ work. * says what the new work.
ITEC224 Database Programming
Computer –the machine the program runs on –often split between clients & servers Human-Computer Interaction (HCI) Human –the end-user of a program –the.
5. IxD - fördjupning av tekniker Interaktionsdesign i digitala medier - HT09 Daniel Nylén, Institutionen för Informatik.
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.
5/20/ Conducting and Analyzing a Contextual Interview ICS 205 Spring 2002 Tom Herring Ratiya Komalarachun.
Interaction Design CMU. Today’s objectives Continue Design approaches (UCD, ACD)  User-Centered Design  Activity-Centered Design.
©2001 Southern Illinois University, Edwardsville All rights reserved. Today Fun with Icons Thursday Presentation Lottery Q & A on Final Exam Course Evaluations.
©2001 Southern Illinois University, Edwardsville All rights reserved. Today Interview Techniques (Hand-in partner preferences) Thursday In-class Interviewing.
©2001 Southern Illinois University, Edwardsville All rights reserved. Today System Design & Putting it Together Reading: ABF: Ch. 9 CD Ch.s 14, 15, 16,
® IBM Software Group © 2006 IBM Corporation Writing Good Use Cases Module 1: Introduction to Use-Case Modeling.
Kendall & KendallCopyright © 2014 Pearson Education, Inc. Publishing as Prentice Hall4-1 Interactive Methods to collect Information Requirements Interviewing.
Usability 1 Usability evaluation Without users - analytical techniques With users - survey and observational techniques.
©2001 Southern Illinois University, Edwardsville All rights reserved. Today Tuesday Running A Paper Prototyping Session CS 321 Human-Computer Interaction.
©2001 Southern Illinois University, Edwardsville All rights reserved. CS 321 Human-Computer Interaction Today Consolidation Reading: CD Ch.s 8, 9, & 10.

Human Computer Interaction
Today Next time  Interaction Reading: ID – Ch 2 Interaction  Introduction to HCI & Interaction Design Reading: ID – Ch. 1 CS 321 Human-Computer Interaction.
Requirements Validation
EVALUATION PROfessional network of Master’s degrees in Informatics as a Second Competence – PROMIS ( TEMPUS FR-TEMPUS-JPCR)
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.
District Leadership Module Preview This PowerPoint provides a sample of the District Leadership Module PowerPoint. The actual Overview PowerPoint is 73.
TIG Ensuring Vertical Articulation in the Science Curriculum.
©2001 Southern Illinois University, Edwardsville All rights reserved. Today Wednesday Running A Paper Prototyping Session Paper Prototyping Video: Paper.
Understanding User's Work Ethnography The systematic study and documentation of human activity without imposing a prior interpretation on it via immersion.
Administrivia  Feedback from the mid-term evaluation  Insights from project proposal.
©2001 Southern Illinois University, Edwardsville All rights reserved. CS 321 Human-Computer Interaction Today Design from Data Reading: CD Ch. 11, 12,
UTA/ARRI. Enterprise Engineering for The Agile Enterprise Don Liles The University of Texas at Arlington.
©2001 Southern Illinois University, Edwardsville All rights reserved. Today Tuesday Contextual Inquiry & Intro to Ethnography Introduction to HCI & Contextual.
©2001 Southern Illinois University, Edwardsville All rights reserved. Today System Design: Reading: CD Ch.s 14, 15, &16 Monday Midterm CS 321 Human-Computer.
©2001 Southern Illinois University, Edwardsville All rights reserved. Today Tuesday CS 321 Human-Computer Interaction Paper Prototyping Video: Paper Prototyping.
Prof. James A. Landay University of Washington Winter 2007 Video Prototyping January 22, 2007.
1 Usability Analysis n Why Analyze n Types of Usability Analysis n Human Subjects Research n Project 3: Heuristic Evaluation.
SE 431 Human Computer Interactions Jamal Nasir. How to design & build good UIs UI Development process Usability goals User-centered design Design discovery.
©2001 Southern Illinois University, Edwardsville All rights reserved. Today Thursday Consolidation Reading: CD Ch.s 8, 9, & 10 In-class modeling exercise.
User-centered approaches to interaction design By Haiying Deng Yan Zhu.
User-centred system design process
Informatics 121 Software Design I
Robertson & Robertson: Chapter 2 Software Specification Lecture 10
Presentation transcript:

©2001 Southern Illinois University, Edwardsville All rights reserved. Today Putting it in Practice: CD Ch. 20 Monday Fun with Icons CS 321 Human-Computer Interaction

©2001 Southern Illinois University, Edwardsville All rights reserved. Practicing Participatory Design Design the Process No single process works for every problem Know the intent of each step and choose which ones fit the project  What point are you coming into the project? –At the beginning, somewhere in the middle, at the end?  Is this a new system or a re-design of an existing one?  What access do you have to the users?  How much time is devoted to design?

©2001 Southern Illinois University, Edwardsville All rights reserved. The Techniques Contextual Inquiry Interpretation Sessions Work Models Consolidated Models Affinity Diagram Visioning Story Boards UED/UI Paper Prototypes

©2001 Southern Illinois University, Edwardsville All rights reserved. Design Principles: Principle of Data Ground all design action in explicit understanding of the users and how they work Use concrete data to derive the understanding  Contextual Inquiry  Work Models  Affinity Diagram Use concrete data to justify design  Vision (Work Redesign)  Story Board  Paper prototyping More than just “User Friendly”

©2001 Southern Illinois University, Edwardsville All rights reserved. Design Principles: Principle of Team Develop a shared understanding and a common team focus Use external representations to develop a common vision  Interpretation sessions, affinity diagram, work models, UED  “Working-on-the-Wall” Bring different perspectives together  X-func team: cross functional team Effective team work depends on being able to manage team meetings  Define roles  Define the process  Maintain focus  Maintain team memory

©2001 Southern Illinois University, Edwardsville All rights reserved. Design Principles: Principle of Design Thinking Alternate between working and reflecting Reflecting provides a check of coherent structure, consistency, and completeness Reflecting reminds the team about what each step reveals. Each transformation acts like a walkthrough of the design  From raw data to the interpretation  From the interpretation to a vision  From a vision to a design  From a design to a usability test

©2001 Southern Illinois University, Edwardsville All rights reserved. INTENT STEPCUSTOMER DATADESIGN THINKINGTEAM AND ORGANIZATION Contextual Inquiry  Gather detailed data needed for design  Discover implicit aspects of work that would normally be invisible  Put technical experts in the customer data  Stimulate the recognition of implications for design  Build the team through shared experiences  Collect concrete data to resolve conflicts Interpretation Sessions  Use the while team’s perspective to see what matters in the work  Capture all aspects of one customer’s work efficiently  Manage the good of insight from all team members  Capture design ideas as they come  Share preliminary design ideas to start cross-pollination  Bring multiple perspectives to bear on the data  Teach team members the perspectives of other organizations  Keep everyone engaged in processing the data Work models  Create a coherent representation of work practice  Record actual user data to check the system  Distinguish between opinions and real data  Reveal aspects of work that matter for design  Capture elements of work in a tangible form  Feed market stories, scenarios, and planning  Create a culture in which concrete data is the basis for making decisions Affinity diagram  Organize data across all customers to reveal scope of issues  Provide a review of the data prior to consolidating and visioning  Identify holes in the data  Push from point fixes to systemic solutions  Introduce inductive thinking  Allow individuals to develop their responses to the data  Share design ideas without evaluation  Drive consensus about what the data means  Make data easy to share  Make key customer issues stand out Create the first step toward corporate knowledge of their customer Work model consolidation  Create one statement of the customer population  Show common structure without losing variation across customers  Reveal implications for design through dialog with each model  Create a map of customer population for planning, sharing, and reuse  Make it possible to validate understandings with customers

©2001 Southern Illinois University, Edwardsville All rights reserved. INTENT STEPCUSTOMER DATADESIGN THINKINGTEAM AND ORGANIZATION Vision  Respond to the data with new work practice designs  Shift the team's focus from tools to work practice  Create a coherent response by reacting to the data rapidly  Generate divergent options before deciding on one  Separate evaluation from generation of ideas  Develop design ideas together as a team  Defuse ownership in ideas Storyboards  Redesign work practice, not technology  Ground redesign in consolidated data  Ensure redesigned work  practice hangs together  Work out details of vision sequentially  Let designers think in the U1 without committing to it  Create a public representation of a task for sharing and checking  Enable parallel design work in small teams User Environment Design  Design the user's experience of the system to be coherent  Allow different user scenarios to be checked in the system  Make the system work model explicit  Show relationships between parts of the system  Find errors in system structure before coding  Drive later object modeling  Separate out the UI conversation  Make the system structure explicit and sharable  Show the relationship between systems  Provide a tool for planning and coordinating multiple systems and teams  Provide a high-level specification Paper prototyping  Check system structure and user interface with customer  Let the customer communicate in their own language  Get an additional layer of detailed data about actions within the system  Check sales point of potential  Provide a fast way to check design alternatives  Learn to separate UI from structural implications  Create and test ideas quickly to prevent over-attachments  Ensure a shared understanding of what customers find valuable  Share ideas in terms that customers and management can understand

©2001 Southern Illinois University, Edwardsville All rights reserved. Senior Project Please remember what you learn here for Senior Project HCI Lab is available for Senior Project Check out Senior Projects at: