1 / 64

Imran Hussain University of Management and Technology (UMT)

Virtual University Human-Computer Interaction. Lecture 36 Behavior & Form – Part IV. Imran Hussain University of Management and Technology (UMT). In Last Lecture …. Evaluation Conceptual framework for developing an interactive product

blossom-benjamin
Download Presentation

Imran Hussain University of Management and Technology (UMT)

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Virtual University Human-Computer Interaction Lecture 36Behavior & Form – Part IV Imran Hussain University of Management and Technology (UMT)

  2. In Last Lecture … • Evaluation • Conceptual framework for developing an interactive product • How we can use this framework to identify certain usability problems • Tactical vs. strategic usability

  3. Usability can be tactical as well as strategic

  4. In Today’s Lecture … • Undo functionality • Files and Save functionality

  5. Understanding Undo

  6. Users and Undo • Reverses previous action

  7. User Mental Models of Mistakes • Humans make mistakes • Programmers should not think of human mistakes as errors • Programmers follow implementation model • Human being do not like to be told that they have make an error so the software should not contradict users

  8. Undo Enables Exploration • Users are like explorers using a tool • They like experiment to see what they can achieve with computer • Undo reassures user if they are in trouble then this function helps them to reverse any action

  9. Designing an Undo Facility • Undo not directly related to goal of user • Users have different models of undo • Novice: help • Intermediate: deleted data • Expert: stack of procedures that can be undone • Undo should be designed to support exploration and not for reversing errors • Undo should be global-wide function

  10. Types of Undo • Incremental and Procedural Actions • Blind and Explanatory Undo • Single and Multiple Undo • Redo

  11. Incremental and Procedural Actions • Procedural component • What the user did? • Data component • What information was affected? • Incremental actions there is both procedural component and data component • Procedural actions do not have data component • These operations act on data but do not add or delete the data

  12. Blind and Explanatory Undo • Blind Undo • There is no indication what the operation is • Explanatory Undo • There is some textual and visual information of the particular operation

  13. Single Undo • Most common form of undo • It reverses the effects of the most recent user’s action

  14. Other Models for Undo-like Behavior • Comparison • Category-specific undo • Deleted data buffers • Milestoning and reversion • Freezing

  15. Other Models for Undo-like Behavior • Comparison • Category-specific undo • Deleted data buffers • Saves the user having to remember exact undo operations and their sequence • Milestoning and reversion • For significant changes make a milestone copy, use revert option to access it • Freezing • Lock the document so certain aspects cannot be changed

  16. What’s wrong with saving changes to files …

  17. Saving Changes to Files • Programs and data files exist in 2 places at the same time • Data and program managed by file system • Explorer (Windows) • Finder (Mac) • The file system and the disk storage facility it manages is the primary cause of disaffection in computer users

  18. Let’s consider the ‘save as’ dialog box …

  19. what’s the point in having a redundant dialog box that users always click yes?…

  20. what’s the point in a function that will confuse new users and they might click ‘no’?

  21. .. confuses possibility with probability (poor assumption)

  22. … why would someone close the document if they didn’t want the changes

  23. … why does it ask for saving changes when you are done and not when making them?

  24. saving changes -------- closing doc(compare with writing in a notebook)when user closes doc, this is the time the differences between the memory and disk need to be reconciledno obvious connection, e.g.- erasing notes when closing book- discarding changes when we leave room

  25. Reason? implementation model is rendered as interface for users

  26. Problems with implementation model …

  27. What happens when I try to rename a file …

  28. Q: What’s the function of the ‘save as’ window?Ans: placing and naming a file

  29. I close the ‘save as’ dialog box, go to ‘explorer’, and try renaming again …

  30. Another example:What happens when I then open the document make some changes that don’t make difference to the contents of the file …

  31. So why do we have these problems …

  32. The Computer’s File System • Data and program managed by file system • Explorer (Windows) • Finder (Mac) • File system is an internal facility and shouldn’t affect the user • Software applications (you) treat file system (a car) just like the OS (a mechanic) does

  33. Let’s say you want to create a copy for archive …[no explicit function for creating copy have to use ‘save as’]

More Related