These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, User Interface Design based on Chapter 12 - Software Engineering: A Practitioner’s Approach, 6/e User Interface Design based on Chapter 12 - Software Engineering: A Practitioner’s Approach, 6/e copyright © 1996, 2001, 2005 R.S. Pressman & Associates, Inc. For University Use Only May be reproduced ONLY for student use at the university level when used in conjunction with Software Engineering: A Practitioner's Approach. Any other reproduction or use is expressly prohibited. The Psychology of Everyday Things by Donald A. Norman Donald A. NormanDonald A. Norman

These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, Interface Design Easy to use? Easy to understand? Easy to learn?  lack of consistency  too much memorization  no guidance / help  no context sensitivity  poor response  Arcane/un friendly Typical Design Errors Any examples? How about your remote controls? How about fighter airplanes? How are Windows OS and MS applications? How about UTD web sites? Vending machines?

These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, Golden Rules Place the user in control instead of ? Place the user in control instead of ? Reduce the user’s memory load dos vs. windows? Reduce the user’s memory load dos vs. windows? Make the interface consistent for the user Make the interface consistent for the user …btw, who’s the user? Should the user work with the designer, then, during UI design?

These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, Place the User in Control  Define interaction modes in a way that does not force a user into unnecessary or undesired actions.  Allow user interaction to be interruptible and undoable.  Streamline interaction as skill levels advance and allow the interaction to be customized. linear text vs. pie chart?  Design for direct interaction with objects that appear on the screen. how? any examples? Can you think of counter examples? Can the user be treated like the computer? How do we know the user will indeed be in control? UI Hall of Fame or Shame

These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, Reduce the User’s Memory Load  Reduce demand on short-term memory. how many?  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. Can you think of counter examples?

These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, 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. Can you think of any good examples? Any counter examples?

These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, User Interface Design Process What is this process called? How many cycles should there be for your own UI design?

These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, Interface Analysis Interface analysis means understanding Interface analysis means understanding (1) the users who will interact with the system through the interface; (1) the 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. What does this analysis lead to? How do we describe each of these, and relationships, precisely, …and where?

These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, User Analysis Are users trained professionals, technician, clerical, or manufacturing workers? Are users trained professionals, technician, clerical, or manufacturing workers? 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, gender, primary spoken language of the user community? What is the age range, gender, primary spoken language of the user community? 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? 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? What does this analysis lead to? How do we describe each of these, and relationships, precisely, and where?

These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, Task Analysis and Modeling Answers the following questions … Answers the following questions … What work will the user perform in specific circumstances? What work will the user perform in specific circumstances? What tasks and subtasks will be performed as the user does the work? What tasks and subtasks will be performed as the user does the work? What specific problem domain objects will the user manipulate as work is performed? What specific problem domain objects will the user manipulate as work is performed? What is the sequence of work tasks—the workflow? What is the sequence of work tasks—the workflow? 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 What does this analysis lead to? How do we describe each of these, and relationships, precisely, …and where? What would modeling result in?

These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, Swimlane Diagram What kind of diagram is this? What does this have to do with UI design?

These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, 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? 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? What does this analysis lead to? How do we describe each of these, and relationships, precisely…and where?