1. William H. Bowers – whb108@psu.edu Rethinking Files and Save Cooper 13

2. William H. Bowers – whb108@psu.edu Topics Difficulties With Files Difficulties With Files Problems With the Implementation Model Problems With the Implementation Model Save As Dialog Save As Dialog Archiving Archiving

3. William H. Bowers – whb108@psu.edu Topics Implementation vs. Mental Model Implementation vs. Mental Model Unified Document Management Unified Document Management Reasons for Disk Storage Reasons for Disk Storage

4. William H. Bowers – whb108@psu.edu Difficulties With Files Files exist in two places Files exist in two places –Disk –Working memory (while open) File system is confusing to users File system is confusing to users Use undo to abandon changes Use undo to abandon changes UI mimics implementation model UI mimics implementation model

5. William H. Bowers – whb108@psu.edu Problems With the Implementation Model Influence of file system on UI is pervasive Influence of file system on UI is pervasive –Menus –Dialogs –Treated as OS treats it Resistance to improving it Resistance to improving it

6. William H. Bowers – whb108@psu.edu Save As Dialog Confusing to end users Confusing to end users Allows both file naming and directory selection Allows both file naming and directory selection Requires user knowledge of both Requires user knowledge of both Usually put files in default directory Usually put files in default directory Can’t be used to change name or directory Can’t be used to change name or directory

7. William H. Bowers – whb108@psu.edu Archiving No explicit application function for archiving No explicit application function for archiving Copy / Paste can be confusing Copy / Paste can be confusing Save as not the best tool for the job Save as not the best tool for the job

8. William H. Bowers – whb108@psu.edu Implementation vs. Mental Model Users think of files as paper documents Users think of files as paper documents Only one copy exists at a time Only one copy exists at a time Implementation uses two copies Implementation uses two copies Implementation should be hidden from end user Implementation should be hidden from end user Rethink file commands to support goals Rethink file commands to support goals

9. William H. Bowers – whb108@psu.edu Unified Document Management Automatic saving Automatic saving –On close –Not time based –During inactivity Create a copy Create a copy Create a milestone copy Create a milestone copy Name/rename Name/rename

10. William H. Bowers – whb108@psu.edu Unified Document Management Placing and repositioning Placing and repositioning Specifying stored format Specifying stored format Reversing some changes Reversing some changes Abandoning all changes Abandoning all changes

11. William H. Bowers – whb108@psu.edu Unified Document Management Currently applications adapt to file system Currently applications adapt to file system Archiving not inherent in current system Archiving not inherent in current system Executing programs exist on disk and in memory Executing programs exist on disk and in memory Start menu should indicate that program is already running Start menu should indicate that program is already running

12. William H. Bowers – whb108@psu.edu Reasons for Disk Storage Price Price Data persistence Data persistence Portability Portability Software is already designed for it Software is already designed for it Users are used to it Users are used to it

13. William H. Bowers – whb108@psu.edu Questions & Discussion