1. 1 Interface Design Easy to use? Easy to understand? Easy to learn?

2. 2 Interface Design lack of consistency too much memorization no guidance / help no context sensitivity poor response Arcane/unfriendly Any others? Rank? Typical Design Errors

3. 3 12.1 Golden Rules Place the user in control Place the user in control Reduce the user’s memory load Reduce the user’s memory load Make the interface consistent Make the interface consistent

4. Reasonable? Quote pg. 357 “a system that reads my mind…knows what I want to do before I need to do it and makes it very easy for me to get it done…”

5. 5 Place the User in Control Define interaction modes in a way that does not force a user into unnecessary or undesired actions. Provide for flexible interaction. Allow user interaction to be interruptible and undoable. Streamline interaction as skill levels advance and allow the interaction to be customized. Hide technical internals from the casual user. Design for direct interaction with objects that appear on the screen. What are some additional design principles that “place the user in control”? Why on the second point? Why just the casual user?

6. 6 Reduce the User’s Memory Load Reduce demand on short-term memory. Establish meaningful defaults. Define shortcuts that are intuitive. The visual layout of the interface should be based on a real world metaphor. Disclose information in a progressive fashion. Why? What does the last point mean? What are some additional design principles that “reduce the user’s memory load”?

7. 7 Make the Interface Consistent Allow the user to put the current task into a meaningful context. Maintain consistency across a family of applications. If past interactive models have created user expectations, do not make changes unless there is a compelling reason to do so. What are some additional design principles that “make the interface consistent”?

8. Usability Page 361 “What do users want anyway?” Easy to learn and helpful “…interface fits the needs of the people who will be using it.” How to determine? – assessment/testing Measurable benefits increased sales and customer satisfaction competitive advantage – examples? reduced cost – examples?

9. 9 12.2 User Interface Analysis and Design User model — a profile of all end users of the system User model — a profile of all end users of the system Design model — a design realization of the user model Design model — a design realization of the user model Mental model (system perception) — the user’s mental image of what the interface is Mental model (system perception) — the user’s mental image of what the interface is Implementation model — the interface “look and feel” coupled with supporting information that describe interface syntax and semantics Implementation model — the interface “look and feel” coupled with supporting information that describe interface syntax and semantics What is the role of designer/engineer? One/some of the above more important?

10. 10 UI Analysis and Design Process

11. 11 12.3 Interface Analysis Interface analysis means understanding Interface analysis means understanding (1) the people (end-users) who will interact with the system through the interface; (1) the people (end-users) who will interact with the system through the interface; (2) the tasks that end-users must perform to do their work, (2) the tasks that end-users must perform to do their work, (3) the content that is presented as part of the interface (3) the content that is presented as part of the interface (4) the environment in which these tasks will be conducted (4) the environment in which these tasks will be conducted.

12. 12 User Analysis Are users trained professionals, technician, clerical, or manufacturing workers? Are users trained professionals, technician, clerical, or manufacturing workers? What level of formal education does the average user have? What level of formal education does the average user have? Are the users capable of learning from written materials or have they expressed a desire for classroom training? Are the users capable of learning from written materials or have they expressed a desire for classroom training? Are users expert typists or keyboard phobic? Are users expert typists or keyboard phobic? What is the age range of the user community? What is the age range of the user community? Will the users be represented predominately by one gender? Will the users be represented predominately by one gender? How are users compensated for the work they perform? (Or how are “you” compensated?) How are users compensated for the work they perform? (Or how are “you” compensated?) Do users work normal office hours or do they work until the job is done? Do users work normal office hours or do they work until the job is done? Is the software to be an integral part of the work users do or will it be used only occasionally? Is the software to be an integral part of the work users do or will it be used only occasionally? What is the primary spoken language among users? What is the primary spoken language among users? What are the consequences if a user makes a mistake using the system? What are the consequences if a user makes a mistake using the system? Are users experts in the subject matter that is addressed by the system? Are users experts in the subject matter that is addressed by the system? Do users want to know about the technology the sits behind the interface? Do users want to know about the technology the sits behind the interface? How do we gather the above information? Issues? Is there a best way?

13. 13 Task Analysis and Modeling Use-cases define basic interaction Use-cases define basic interaction Task elaboration refines interactive tasks Task elaboration refines interactive tasks Object elaboration identifies interface objects (classes) Object elaboration identifies interface objects (classes) Workflow analysis defines how a work process is completed when several people (and roles) are involved Workflow analysis defines how a work process is completed when several people (and roles) are involved Hierarchical representation defines a task hierarchy for each user type Hierarchical representation defines a task hierarchy for each user type

14. 14 Swimlane Diagram

15. 15 Analysis of Display Content Are different types of data assigned to consistent geographic locations on the screen (e.g., photos always appear in the upper right hand corner)? Are different types of data assigned to consistent geographic locations on the screen (e.g., photos always appear in the upper right hand corner)? Can the user customize the screen location for content? Can the user customize the screen location for content? Is proper on-screen identification assigned to all content? Is proper on-screen identification assigned to all content? If a large report is to be presented, how should it be partitioned for ease of understanding? If a large report is to be presented, how should it be partitioned for ease of understanding? Will mechanisms be available for moving directly to summary information for large collections of data. Will mechanisms be available for moving directly to summary information for large collections of data. Will graphical output be scaled to fit within the bounds of the display device that is used? Will graphical output be scaled to fit within the bounds of the display device that is used? How will color to be used to enhance understanding? How will color to be used to enhance understanding? How will error messages and warning be presented to the user? How will error messages and warning be presented to the user? Where will content come from? Where will content come from? Opportunities to customize? Issues with customization? If yes, how do we fix?

16. 16 Analysis of the Work Environment What are some of the physical characteristics of a workplace that can affect user interface design? What are some of the physical characteristics of a workplace that can affect user interface design? Are there other characteristics to examine? Are there other characteristics to examine?

17. 17 12.4 Interface Design Steps  Using information developed during interface analysis (SEPA, Section 12.3), define interface objects and actions (operations).  Define events (user actions) that will cause the state of the user interface to change. Model this behavior.  Depict each interface state as it will actually look to the end-user.  Indicate how the user interprets the state of the system from information provided through the interface.

18. 18 Interface Design Patterns Patterns are available for Patterns are available for The complete UI The complete UI Page layout Page layout Forms and input Forms and input Tables Tables Direct data manipulation Direct data manipulation Navigation Navigation Searching Searching Page elements Page elements e-Commerce e-Commerce Are these used? Why or why not?

19. 19 Design Issues Response time (length and variability) Response time (length and variability) One more important? One more important? Help facilities (old way was a colleague or a big paper manual) Help facilities (old way was a colleague or a big paper manual) What ways do/should we use today? What ways do/should we use today? Error handling Error handling Best practices? Best practices? Menu and command labeling Menu and command labeling 1-to-1?; Customizable?; Form? (Alt-something, Function keys, command line) 1-to-1?; Customizable?; Form? (Alt-something, Function keys, command line) Application accessibility Application accessibility What do we mean? What do we mean? Internationalization Internationalization Is this desirable? Is this desirable? Possible? Possible?

20. 20 Design Evaluation Cycle