William H. Bowers – Making Software Considerate Cooper 14.

Slides:



Advertisements
Similar presentations
DEVELOPING A METHODOLOGY FOR MS3305 CW2 Some guidance.
Advertisements

Computer Architecture
Guiding the Behavior of Young Children. Establishing mutual respect Positive interaction Focusing on the child Encouragement of Self-control Effective.
© De Montfort University, Characteristics of Good Dialogues Howell Istance Department of Computer Science De Montfort University.
Lesson 5 Computer-Related Issues
William H. Bowers – Understanding Users: Qualitative Research Cooper 4.
11 HCI - Lesson 5.1 Heuristic Inspection (Nielsen’s Heuristics) Prof. Garzotto.
Tour of About Face Section 2: Designing Behavior and Form Cooper & Reimann AJ Brush Richard Anderson.
Part 4: Evaluation Days 25, 27, 29, 31 Chapter 20: Why evaluate? Chapter 21: Deciding on what to evaluate: the strategy Chapter 22: Planning who, what,
1 SWE Introduction to Software Engineering Lecture 26 – User Interface Design (Chapter 16)
Procedures Software for People. Agenda Procedure: Definition Software for People Designing Procedures Procedures as Problem Solving Software: Procedures.
Heuristic Evaluation of Usability Teppo Räisänen
10th Workshop "Software Engineering Education and Reverse Engineering" Ivanjica, Serbia, 5-12 September 2010 First experience in teaching HCI course Dusanka.
1 User Interface Design CIS 375 Bruce R. Maxim UM-Dearborn.
Lecture Set 3 Introduction to Visual Basic Concepts Part A – User Interfaces and Windows Forms – The Toolbox.
Chapter 11: Interaction Styles. Interaction Styles Introduction: Interaction styles are primarily different ways in which a user and computer system can.
William H. Bowers – Modeling Users: Personas and Goals Cooper 5.
CS 4720 Usability and Accessibility CS 4720 – Web & Mobile Systems.
Know the Workplace Chapter 11. At the workplace Consider what’s going on What is the expected conformity? How do you anticipate things? How do you become.
SWE205 Review Spring Why is software unusable? Users are no longer trained. Why? Feature creep Inherently hard: a problem of communication Designed.
Software Evaluation Catherine McKeveney Medical Informatics 1st March 2000.
Usability Evaluation/LP Usability: how to judge it.
10 Usability Heuristics for User Interface Design.
Multimedia Specification Design and Production 2012 / Semester 1 / week 5 Lecturer: Dr. Nikos Gazepidis
Usability Evaluation June 8, Why do we need to do usability evaluation?
Heuristic evaluation Functionality: Visual Design: Efficiency:
Global Communication Skills Tosspon UNO IPD Meeting 6 Agenda Conflict Management Active Listening.
William H. Bowers – High Level Design Torres 16.
William H. Bowers – Users, Their Work Environment and Tasks Torres 10.
William H. Bowers – Rethinking Files and Save Cooper 13.
BA Team: Product Ownership, Analysis, and Solution Design BA Bi-Weekly Mini-meeting May 19, Acceptance Criteria Defining Success one Story.
432 Invitation System (Instructions …..) Event name: Date: Time: Location: Description: Attend Not Attend Submit Cancel.
Usability 1 Usability evaluation Without users - analytical techniques With users - survey and observational techniques.
Developed by Tim Bell Department of Computer Science and Software Engineering University of Canterbury Human Computer Interaction.
William H. Bowers – Other Communication with Users Cooper 35.
William H. Bowers – Orchestration & Flow Cooper 9.
William H. Bowers – Designing for the Web Cooper 37.
William H. Bowers – Using Controls Cooper 26.
William H. Bowers – Improving Data Entry Cooper 17.
Heuristic Evaluation Short tutorial to heuristic evaluation
William H. Bowers – Understanding People Torres 3.
William H. Bowers – Eliminating Excise Cooper 10.
William H. Bowers – Requirements Torres 9.
William H. Bowers – Specification Techniques Torres 17.
William H. Bowers – Participatory Methods Torres 6.
Imran Hussain University of Management and Technology (UMT)
William H. Bowers – Conceptual Design and Architecture Torres 11.
1 Major Printer Administration Tasks Managing printers Managing documents Troubleshooting printers Performing tasks requiring the Manage Printers permission.
Ten Usability Heuristics These are ten general principles for user interface design. They are called "heuristics" because they are more in the nature of.
Human Computer Interaction Lecture 21 User Support
User Interface Design SCMP Special Topic: Software Development
Human Computer Interaction Lecture 21,22 User Support
THIS IS TO EVIDENCE YOUR WORK AND GET THE BEST GRADE POSSIBLE
Imran Hussain University of Management and Technology (UMT)
Krug Chapter 5 B: Software Should be Considerate
User Interface Design and Development
Krug 8 Dialog Boxes Toolbars
Web User Interface (WUI) Behavior
User Interface Design and Development
Krug Chapter 2 How We Really Use the Web and Web Site Design
Lesson 5 Computer-Related Issues
Cooper Part II Making Well-Behaved Products Data Entry
Cooper Part II Making Well-Behaved Products Flow
Norman 7 B: Improving Data Entry
Usability Heuristics Prof
Nilesen 10 hueristics.
SDLC Phases Systems Design.
User-Centered Design Data Entry CS 4640 Programming Languages for Web Applications [The Design of Everyday Things, Don Norman, Ch 7]
Software Should be Considerate
User-Centered Design Data Entry CS 4640 Programming Languages for Web Applications [The Design of Everyday Things, Don Norman, Ch 7]
Presentation transcript:

William H. Bowers – Making Software Considerate Cooper 14

William H. Bowers – Agenda Designing Considerate Software Designing Considerate Software Characteristics Characteristics –Takes an Interest –Is Deferential –Is Forthcoming –Uses Common Sense –Anticipates Needs

William H. Bowers – Agenda Characteristics Characteristics –Is Conscientious –Doesn’t Burden You with its Personal Problems –Keeps Us Informed –Is Perceptive

William H. Bowers – Agenda Characteristics Characteristics –Is Self-Confident –Doesn’t Ask a Lot of Questions –Fails Gracefully –Knows When to Bend the Rules –Takes Responsibility

William H. Bowers – Designing Considerate Software Put needs of user first Put needs of user first Respectful Respectful Generous Generous Helpful Helpful Independent of UI Independent of UI

William H. Bowers – Characteristics Takes an interest Takes an interest Is deferential Is deferential Is forthcoming Is forthcoming Uses common sense Uses common sense Anticipates needs Anticipates needs

William H. Bowers – Characteristics Is conscientious Is conscientious Doesn’t burden you with its personal problems Doesn’t burden you with its personal problems Keeps you informed Keeps you informed Is perceptive Is perceptive

William H. Bowers – Characteristics Is self-confident Is self-confident Doesn’t ask a lot of questions Doesn’t ask a lot of questions Fails gracefully Fails gracefully Knows when to bend the rules Knows when to bend the rules Takes responsibility Takes responsibility

William H. Bowers – Takes an Interest Remembers our work habits Remembers our work habits Does not demand then discard information Does not demand then discard information

William H. Bowers – Is Deferential Inconsiderate software passes judgment on user actions Inconsiderate software passes judgment on user actions Considerate expresses an opinion Considerate expresses an opinion Makes suggestions Makes suggestions Explains consequences Explains consequences Submits to the user Submits to the user

William H. Bowers – Is Forthcoming Volunteers related information Volunteers related information Provides hardware feedback Provides hardware feedback –Printer status –Printer needs (low paper)

William H. Bowers – Uses Common Sense Puts appropriate functions in appropriate places Puts appropriate functions in appropriate places Doesn’t put dangerous, irreversible actions near routine ones Doesn’t put dangerous, irreversible actions near routine ones

William H. Bowers – Anticipates Needs Pre-loading web pages linked to the current one Pre-loading web pages linked to the current one Read ahead buffers Read ahead buffers

William H. Bowers – Is Conscientious Focuses on goals, not tasks Focuses on goals, not tasks Automatically backs up documents before writing new one without asking Automatically backs up documents before writing new one without asking

William H. Bowers – Doesn’t Burden You with its Personal Problems “Whines at us with error messages” “Whines at us with error messages” Interrupts with confirmation dialogs Interrupts with confirmation dialogs Notifies us of success unnecessarily Notifies us of success unnecessarily

William H. Bowers – Keeps Us Informed Rich feedback Rich feedback Modeless feedback Modeless feedback

William H. Bowers – Is Perceptive Observes usage Observes usage Recognizes patterns of use Recognizes patterns of use Offers relevant information Offers relevant information Remembers and predicts preferences Remembers and predicts preferences

William H. Bowers – Is Self-Confident Does not use unnecessary confirmation dialogs Does not use unnecessary confirmation dialogs Performs actions appropriately as requested Performs actions appropriately as requested

William H. Bowers – Doesn’t Ask a Lot of Questions Too many choices are an ordeal Too many choices are an ordeal Should not interrogate Should not interrogate Presents only valid choices Presents only valid choices

William H. Bowers – Fails Gracefully Crashes usually discard existing data Crashes usually discard existing data Error messages are generally useless Error messages are generally useless Failures are not isolated Failures are not isolated

William H. Bowers – Knows When to Bend the Rules Two states – compliance, non- compliance Two states – compliance, non- compliance No in between allowed No in between allowed “Fudgeability” “Fudgeability” Rigidity is the result of the implementation model Rigidity is the result of the implementation model Humans require fudge factors Humans require fudge factors

William H. Bowers – Knows When to Bend the Rules Flexibility reduces mistakes Flexibility reduces mistakes Inflexibility casts users and software as adversaries Inflexibility casts users and software as adversaries Prevents users from reaching goals Prevents users from reaching goals

William H. Bowers – Takes Responsibility Typical print operation Typical print operation –Spools print –Cancel stops printing –Cancel does not purge printer memory –Reports cancellation –Prints unnecessary pages

William H. Bowers – Questions & Discussion