Imran Hussain

1
Virtual University Human-Computer Interaction
Lecture 36Behavior Form Part V

• Imran Hussain
• University of Management and Technology (UMT)

2
In Last Lecture

• Undo
• files save changes in the file

3
In Todays Lecture

• How we can resolve the problem of mental model
  vs. implementation model?
• How we can cope with better strategy to implement
  and develop interfaces?
• How to make software considerate
• How to make software smart

4
Unified Document Management
5
This is a new way of managing documents and files
6
Unified Document Management

• Automatically saving the document
• Creating a copy of the document
• Naming and renaming the document
• Placing and repositioning the document
• Specifying the stored format of the document
• Reversing some changes
• Abandoning all changes
• Creating a milestone copy of the document

7
Automatically saving the document
8
No longer require the Save As function
9
Save changes in idle time
10
Keyboard accelerators should be maintained
11
Creating a copy of the document
12
Creating a copy of the document

• Have function called snapshot copy
• It should be intelligent so that to give files
  similar filenames

13
Naming and renaming the document
14
Naming and renaming the document

• Show name on title bar
• This should be editable

15
Placing and repositioning the document
16
Place files automatically
17
Specifying the stored format of the document
18
Reversing some changes
19
Reversing some changes

• Should be done from program
• Using undo
• Should not have to call file system

20
Abandoning all changes
21
Abandoning all changes

• This option can also be provided

22
Creating a milestone copy of the document
23
A New File Menu
24
Making Software Considerate
25
What makes software considerate?

• Considerate software takes an interest
• Considerate software is deferential
• Considerate software is forthcoming
• Considerate software uses common sense
• Considerate software anticipates needs
• Considerate software is conscientious
• Considerate software doesnt burden you with its
  personal problems

26
What makes software considerate?

• Considerate software keeps you informed
• Considerate software is perceptive
• Considerate software is self-confident
• Considerate software doesnt ask a lot of
  questions
• Considerate software fails gracefully
• Considerate software knows when to bend rules
• Considerate software takes responsibility

27
Considerate software takes an interest

• Todays personal computers do not have this
  personal touch
• They do not remember what user likes or dislikes

28
Considerate software is deferential
29
Considerate software is deferential

• Restaurant host suggests table
• We desire some other table
• Software can express opinion, but should not pass
  judgment on human actions (e.g., that we have
  made a mistake)
• Example
• SUBMIT

30
Considerate software is forthcoming
31
Considerate software is forthcoming

• Example
• When we print, printer does not tell us
• Paper is low
• No of documents in queue
• Nearby printer is free

32
Considerate software uses common sense
33
Considerate software uses common sense

• Software should not place constantly-used
  function near irreversible functions

34
Considerate software anticipates needs
35
Considerate software is conscientious
36
Considerate software is conscientious

• Software saves new file which has similar name to
  an existing one
• Why not ask to rename old file?

37
Considerate software doesnt burden you with its
personal problems
38
Considerate software doesnt burden you with its
personal problems

• Computers burden us with
• Confirmation dialog boxes
• Notifiers
• Error messages

39
Considerate software keeps you informed
40
Considerate software is perceptive
41
Considerate software is perceptive

• Software should remember our behavior and
  identify patterns of behavior

42
Considerate software is self-confident
43
Considerate software is self-confident

• If user want to delete a file
• Provide undo

44
Considerate software fails gracefully
45
Making Software Smart
46
Giving software memory

• Software should try to remember what the user
  does?
• Smart software will remember information that is
  relevant to user

47
Task coherence

• Remembering choices and defaults
• Remembering patterns

48
Task coherence

• Predicting what users will do based on what they
  did last
• Example
• Salman uses 12-point Times
• Kamran uses 10-point Arial

49
Remembering patterns

• By remembering patterns we can reduce excise
• Example You are writing a report. You want white
  text on black background

50
Actions to remember

• File locations
• File-open facilities should remember where user
  gets his files
• Deduced information
• Software should remember information that can be
  deduced from facts
• Multi-session undo
• Most programs discard stack of undo options when
  they close a file
• Past data entries
• If program remembers past data entries that user
  has made then less mistakes will be made by user