![Designing for Humans What is a User Interface? â The place at which independent systems meet and act on or communicate with each otherâ ,[object Object],[object Object],[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Usability principles 1
Similar to Usability principles 1 (20)
More from Sameer Chavan
More from Sameer Chavan (15)
Recently uploaded
Recently uploaded (20)
Usability principles 1
- 1. Usability Engineering - 1 Sameer Chavan
- 10. Design Problem
- 12. UI Design Owner Engineer Architect Building a Custom - made house
- 13. UI Design User Programmer U.I.Designer Building a Software Product
- 15. What if the Engine Designers make bike?
- 16. What if the Engine Designers make bike?
- 17. What if the Engine Designers make bike?
- 18. Actual Required Bike Design
- 24. Market Maturity Model Technology Focus User Focus Market Maturity Over Time
- 25. Users donât like Unexpectations Access denied O.k., and now youâll do exactly what Iâm telling you !
- 27. Usability & Software Development life cycle Understand the User & .. Do user Task Analysis Define User Requirements Develop Interactions Concept Develop Prototypes Test Test Software Development Test Release Test Requirements Capture Design Development Usability Evaluation / Usability Testing
- 28. What suits one customer might not suit the next
Editor's Notes
- Jane It is easy to want to focus on the first part of this âequationâ because buttons, lists, browsers, and widgets in general are familiar to us. We can talk more concretely about those things we can see rather than about how someone might perceive information or react to a prompt. However, the widgets that appear in an interface are a collection of touchpoints with the user. These touchpoints are the results of a great deal of anlaysis of human behavior, work habits, environmental anlaysis, and user feedback. UI design is not graphic design. The graphic element of UI design is only the presentation level of all user interaction with the system. You also have a very good article in your resources section called â Usability is Not Graphic Design .â This article discusses the common misconception that what a usability engineer does is makes things pretty.
- Jane If you remember only four things from this class, I hope it is these four principles. If you can remember them, they will be your guide to dealing with every UI decision or problem that arises.
- Jane Letâs talk about human limits. Not in the sense that human beings are dumb or that they canât do anything right. Weâre talking here about basic human-computer interaction points from a human point of view. There is a very interesting book called Things that Make us Smart by Don Norman. In that book, Norman points out that itâs OK to have human strengths and weaknesses because computers also have strengths and weaknesses. Usability problems arise when there is a situation that reveals the weaknesses of the user or the weaknesses of the computer. Another possibility is some mismatch of how the two work together. Example: sorting a list of alphanumeric strings for 8 hours visual inspection
- Jane Lotâs of eye movement causes visual fatigue--the more people have to search a screen for information or scrutinize a screen to figure out what to do, the more taxing it is on their eyes. Over the course of a day, people who have to struggle with visual clutter or mayhem will become very visually fatigued. Color and highlighting indicate meaning. People give meaning to color. This has strong implications for cultural or international designs--different colors mean different things in different cultures. 9% of men and 2% of women have some form of color blindness or color confusion. Donât rely on color alone to provide cues. Consistent format goes back to the first point. If every screen presents a new layout or inconsistent placement of buttons, the effort to use the application increases. People scan--This has particular significance in dialog boxes. There needs to be a visual indicator in danger situations so that people slow down and read at least some of the info in the dialog. Scan - conclusion âitâs not there.â
- Erin Attention Spans: Between individuals and Across Individuals Our software is just one piece of their tasks to get their job done. Fatigue: Leads to increased probability of errors Senses: Shop Floor - noisy environment Key Combinations - where they keys are Keyboard/mouse on Web: Tab and Enter are supported on Web, and sometimes Esc; otherwise you canât count on keyboard shortcuts. More mouse clicks needed to do the same thing on the web as in a GUI. After last bullet: Quote from Thornton May presentation to AIIM on 9/28/98: â2/3 of all the people who have ever lived to age 65 are alive todayâ People are staying in the workforce longer - new challenges for design.
- Erin--slide & short term memory activity Limit a personâs memory load. Note: example of limiting memory load is to show a file name rather than expecting the user to remember the file name as they move between windows. Provide Context! Example of breaking down decision-making into chunks: group boxes around a group of widgets that are related. Sorting options so that they can look at the data in different ways to make different decisions. Exaggerated sense of time when in a hurry - e.g., stoplights. Need for Visual Indicators - feedback. (OMF example of opening worklist 5 times) ACTIVITY: short term memory activity goes here. Should take no more than 10 minutes. See notes on next page.
- Jane People expect the interface to communicate WITH them, and believe that computers will follow the same rules of communication that exist for human to human interaction. They expect the interface to be flexible and give them feedback. Emotions: Users may have had a negative or positive experience with a previous system and they tend to generalize those emotions to your new system. People âlikeâ a system or âtrustâ the system. People want computers to be predictable. As they work, they want to be able to predict the computer will respond, or even to eliminate thinking about the possibility of any unpredictable response. Context provides specific meaning and interpretation options. Out-of-context information takes longer to understand and is often misunderstood. Context on a software screen is developed through title bar names, labels, and grouping of information. Mental models are picture of how something should work or act. People develop mental models based on their own experiences, and these models may not always be correct. (Example--lights and windshield wipers in a car--where are they located?) (Example--Frau and the defroster in the new car) Book âThe Media Equationâ by Reeves and Nass, 1996.
- Jane To summarize what weâve been talking about, this is a list of the basics. These are design constraints that must always be at the forefront of your mind as you design an interface or as you evaluate an interface or as you write about an interface.
- As we discuss these stages, we will point out 3 things at each stage: 1. What the âmarket at largeâ is doing during the stage. 2. What development teams generally tend to do during each stage, based on market behavior. 3. Usability issues and user perceptions during each stage. (Instructor - would a blank table with the 3 headings be easier for people here?)
- Jared Spool refers to the first stage of a product in the market as Raw Iron. After 1st bullet: NOVELTY (Show four bullet points) (After last bullet point): As users get more and more sophisticated, and as products get more âplentifulâ this stage gets shorter and shorter. Technology has really changed the length of this stage. There are some factors that are critical to this stage and also at all of the future stages we will discuss--we are not going to focus these in detail. However, a companyâs market position is a key factor here and in all of the future stages. That means that based on whether a company is a market leader, a contender, a niche player, or a startup, the companyâs exact behavior during a stage may be influenced by their market position. That is a whole other class, so weâre not going to go there--but keep that thought in the back of your mind as we get into discussions about the stages and what they mean.
- The transparency stage is somewhat difficult to explain without giving examples of products that have become transparent. One example of a product that is on its way to becoming transparent (and some would say already is transparent) is the PC. Price has become a differentiator. There are still a few features that are valued as must-haves, but most PCâs are alike in feature and function.
- These section headings (e.g. ANALYSIS, DESIGN, TESTING) are not methodology phase names. They are simply labels to group the type of duties we perform. The ANALYSIS duties are started during the Concept phase and finished during the System phase Conceptual Design is started during the Concept phase and finished during the System phase Collaborative Design and Image Creation occur during the System and Implementation phases The TESTING duties can be performed during any phase