7735_ix.qxp 4/3/2007 11:47 AM Page 275

Index

A assumptions in software design, 138 attentive interfaces, 44 accessibility,51 audience for usability test reports, 243-244 accessibility myths (Web sites),203-205 audio information cues, 187 operating systems, 54-55 auxiliary applications, 175, 205, 213 Section 508, 52 Web Content Accessibility Guidelines, 52-54 Active Server Pages (ASP), 10 B ,27 Back , 27 advanced users, needs of, 143 back-end programming (Web sites),213 Aero interface, 6, 38 background sound,Web design myths, 202 affordances, 127 backward compatibility,Web accessibility myths, AJAX, 13, 25 204 ALT tags, 204-205 Bash (Bourne Again ) shell, 30 Alto, 2-3 batch files, 29 America Online (AOL), 9 batch interface, 28 Americans with Disabilities Act, 52 batch programming, 29 analyzing usability test data, 241-243 Bates, Marilyn, 117 animals associated with personality types, 118 beginners, needs of, 141 animation,Web design myths, 202 behavior. See user behavior AOL (America Online), 9 behavioral design patterns, 173 Apple II series, 3 behaviors in GUIs, 177 Apple Lisa, 3 mouse pointers, 178-180 Apple Macintosh, 3-4 windows, 181-185 application service providers (ASPs), 44 bell curve. See experience bell curve applications Berners-Lee,Tim, 9 application sites, 206-210 beta testing, 49, 92, 102, 136 Internet-based applications, 200 Bias, Randolph, 71. See also Vienna (Windows Web-based applications,44 code name) Aqua interface, 3-4, 39-40 blaming oneself (reasons for failure), 114 interface, 45-46 blaming wrong cause (reasons for failure), 115 ARPANET,8 blogs, 104 The Art of Usability (Raymond), 27 brain-computer interface, 46 artifact walkthrough, discourse-based interviews brain, knowledge in, 122-124 with, 237 brainstorming sessions, 165 ASP (Active Server Pages), 10 bread crumbs,Web site design,217 ASPs (application service providers), 44 breaking Web site design rules, 219-220 assistants, 190-191 Briggs, Katherine, 115 assistive technologies, 51 browsers. See Web browsers

275 7735_ix.qxp 4/3/2007 11:47 AM Page 276

276 Index

Bush,Vannevar,1 observation skills needed, 234-236 business case for usability ongoing relationships, establishing, 238-239 benefits of good design, 64-67 pilot tests, 233-234, 248-251 framework for,63-64 rapport with participants, establishing, 239 Mike’s Bikes case study,76-82 resolving problems during, 239-241 profitability,67-69 conscious behavior,subconscious behavior versus, ROI (return on investment) analysis, 69-71 125 stakeholder expectations, 60-63 consistency in Web site design,215, 218 Usability Engineering Life Cycle (UEL), 71-72 constraints design, testing, and development phase, 73-75 defined, 127 installation and feedback phase, 75-76 on designers, 88-89 requirements analysis phase, 72-73 on users, 88 business case for usability,60 Web site design versus GUI design, 198-200 business goals, 150 consumer-oriented Web portals, 210 business requirements, 166 context scenarios, 165 buttons, 20 contextual needs, 165 contextual text analysis, 73 C controlled usability evaluations, 227 cookies, 208 calculating dollar amount of benefit (ROI), 70-71 Cooper,Alan, 49, 86, 139-140, 143, 164, 171, 173, case study. See Mike’s Bikes case study 209 CERN, 9 critical incident interviews, 237 checklists for documentation design, 98-102 cued recall interviews, 236 CLI (command-line interface), history of, 28-30 cues. See information cues clicking cultural constraints, 88 clicking and dragging, 179 current information in Web site design,219 left mouse button, 178-179 cursors, 178 right mouse button, 180 customer partnering, 237 closing windows, 185 customer personas, 155 colors customer requirements, 166 in Web site design,215-216 customer retention, 67 Web-safe colors, 42, 199 customer segments, factors affecting interface command-line interface (CLI), history of, 28-30 usage, 93-94 communication with users customer support costs, 66 assistants and wizards, 190-191 customers’ goals, 150 online help systems, 190 customizability of GUIs, 31 paper prototyping advantages in, 94 standards, 189-190 competitive temperament, 120-121 D conceptual-level principles, 172 daemonic applications, 175, 205 conceptual models data elements, 167 creating, 127-129 data needs, 165 design, 74 databases,Web site interaction with, 215 Mike’s Bikes case study,129-131 deep and narrow task structures, 124 mockups, 74 defining usability tests, 228-229 concurrent, contextual interviews, 236 goals, creating, 229 conducting usability tests, 233 measures, determining, 231-232 interviewing skills needed, 236-238 participants, selecting, 229-230 7735_ix.qxp 4/3/2007 11:47 AM Page 277

Index 277

test materials, preparing, 232-233 error messages, poor design of, 138 test scenarios, creating, 230-231 ethical, good design as, 86, 171 demographics in personas, 147 ethnographic interviews, 237 descriptive statistics, 241 ethnography,144 design myths (Web sites),202-203 evaluating personas, 154 design team, 228 expectations design, testing, and development phase (UEL), of personas, 165 73-75 of stakeholders, 60-63 design. See Goal-Directed Design ; user experience bell curve, 140-141 interface design advanced users, needs of, 143 designers beginners, needs of, 141 constraints on, 88-89 intermediate users, needs of, 142-143 expectations of, 61 experience goals, 150 detailed design, 75 Extensible Markup Language (XML), 41 DHTML (Dynamic HTML), 25 extreme usability,152 dialog boxes, 181 extroversion/introversion dichotomy,116 difficult tasks, transforming into simple tasks, 126-127 F disabled users. See accessibility failures, reasons for,114-115 discourse-based interviews with artifact walk- feedback, 225. See also usability tests through, 237 in conceptual models, 129 distributions (), 7 on documentation design, 102 Dock in Mac OS GUI, 11-12, 39 feedback phase (UEL), 75-76 documentation, feeling/thinking dichotomy,116 defined, 48 fingerprint scanning, 35 good design for,96-97 Firefox, 10 planning process, 97-103 Flash, 13, 25 dollar amount of benefit (ROI), calculating, 70-71 focus groups, 227, 237 Donoghue, Karen, 68 fonts in Web site design,199, 215-216 DOS, history of CLI (command-line interface), 29 Fore, David, 86 double-clicking, 179 form factor,166 drop-down menus, 20 form processing (Web sites),214-215 Dubberly,Hugh, 86 formative usability testing, 49 Dumas, Joseph, 47, 228, 242 formatting conventions for documentation, 102 Dynamic HTML (DHTML), 25 Forward button, 27 framework, 166-169 E framework phase (Goal-Directed Design Process), edge cases, 149, 192 144 Eisenberg, Bryan and Jeffrey,117, 147-148 Free Software Foundation, 7 elastic users, 149 front end (Web sites),213 elegant, good design as, 87, 171 functional elements, 167 embedded links, 26 functional groups, 168 end goals, 150 functional needs, 165 end user design, 149 future of , 44-46 Engelbart, Douglas, 1 Mac OS, 43 engineers, expectations of, 61 Web browsers, 43-44 enterprise Web portals, 210 Windows Vienna, 43 environmental Web portals, 211 7735_ix.qxp 4/3/2007 11:47 AM Page 278

278 Index

G refining, 191-194 windows, 181-185 gesture interfaces, 45 behaviors, 177 GNOME, 7, 12-13, 40 defined, 18 GNU , 7 differences among Goal-Directed Design Process, 49, 143-146 Linux GUI, 12-13 framework, defining, 166-169 Mac OS GUI, 11-12 refinement stage, 191-194 Web pages, 13-14 requirements, obtaining, 164-166 Web programs, 14 user and task analysis Windows GUI, 11 observing users, 152-154 differences among, 10 personas, constructing, 147-159 GUI design,Web site design versus, 198-200 personas, evaluating, 154 history of personas, prioritizing, 154-156 Apple Macintosh, 3-4 qualitative research, 146-147 Linux, 7-8 goals , 5-6 constructing personas, 149-150 Xerox Alto, 2-3 creating for usability tests, 229 history of, 1-2 of good design, 85-87, 171 operating systems, 18-19 good design parts of, 19-23 designers and users, constraints of, 87-90 rules for interaction with, 198 for documentation, 96-103 goals of, 85-87, 171 importance of, 104-105 H paper prototyping Hackos, JoAnn, 153 advantages of, 93-95 haptic feedback, 36 disadvantages of, 95-96 hardware, security interfaces, 34-36 Mike’s Bikes case study,105-110 help. See information cues; online help systems overview of, 91 helplessness (reasons for failure), 115 product mockups versus, 91 hierarchy of functional groups, defining, 168 skepticism toward, overcoming, 92-93 High-Performance Computing Act of 1991, 9 storyboarding versus, 91 highlight presentations of usability test results, wireframes versus, 91 246-247 paper prototyping, 90 Hippocrates, 116 patterns of, 172-173 history principles of, 172 of CLI (command-line interface), 28-30 Goodwin, Kim, 86 of GUIs, 1-2 Google Spreadsheet, 44 Apple Macintosh, 3-4 Gore,Al, 9 Linux, 7-8 graphical user interfaces. See GUIs Microsoft Windows, 5-6 graphics Xerox Alto, 2-3 in Web site design,216-217 of Web design, 8 Web accessibility myths, 204-205 Internet Explorer,9-10 Web design myths, 202 Internet, beginning of, 8 group interviews, 237 Mosaic, 9 GUIs (graphical user interfaces), 30-32 Netscape Navigator,9 behaviors HTML (Hypertext Markup Language), 24 mouse pointers, 178-180 human characteristics of user interface design, 171 7735_ix.qxp 4/3/2007 11:47 AM Page 279

Index 279

humanistic temperament, 120 J , 25-26 Java, 14, 24 Hypertext Markup Language (HTML), 24 JavaScript, 25 judging/perceiving dichotomy,117 I Jung, Carl, 116 I-shaped bar as mouse pointer,178 de Icaza, Miguel, 7 K images. See graphics KDE, 7, 12-13, 40 immediate recall interviews, 236 Keirsey,David, 117 implementation model, 139 key path scenarios, constructing, 169 individuality constraints, 89 key path variants, 192 inferential statistics, 241 kiosks, Section 508 accessibility,52 information cues knowledge in brain versus in world, 122-124 audio cues, 187 Korman, Jonathan, 86 pop-up messages, 187 search engines, 188 visual cues, 186-187 L informational sites, 205, 208 left mouse button, clicking, 178-179 input methods, defining, 166 legal documents, preparing for usability tests, 232 installation and feedback phase (UEL), 75-76 Leopard (Mac OS X), 40 Intel 80386 chips, 5 Level 1 design (UEL), 74 interaction design, 171 Level 2 design (UEL), 74-75 goals of good design, 171 Level 3 design (UEL), 75 patterns of good design, 172-173 life goals, 149 principles of good design, 172 links. See hyperlinks interaction framework, sketching, 168 Linux, 7-8 interaction-level principles, 172 as GUI operating system, 19 interfaces, 1. See also GUIs interface design issues and improvements, 40 interface design, 49 unique GUI features, 12-13 interface-level principles, 172 Lisa, 3 intermediate users logical constraints, 88 needs of, 142-143 long-term production costs, 65 perpetual intermediates, 140 Internet M defined, 23 Mac OS, 3-4 history of, 8 future of user interface design, 43 Internet-based applications, 200 as GUI operating system, 19 Internet Explorer,9-10 OS X, 3-4 interviewing users when constructing personas, interface design issues and improvements, 151-152 39-40 interviewing skills for conducting usability tests, unique GUI features, 11-12 236-238 managers, expectations of, 62-63 introversion/extroversion dichotomy,116 mapping process in conceptual models, 129 intuition/sensing dichotomy,116, 122-124 Marble Answering Machine, 45 iterative conceptual model evaluation, 74 marketing people, expectations of, 62 iterative design standards evaluation, 75 maximizing windows, 19, 184 iterative detailed user interface design evaluation,75 Mayhew,Deborah, 71 7735_ix.qxp 4/3/2007 11:47 AM Page 280

280 Index

MBTI (Myers-Briggs Type Indicator), N 115-117, 130 narratives for personas, 154 MDI (multiple-document interface), 19, 181-182 National Center for Supercomputing Applications measures, determining for usability tests, 231-232 (NCSA), 9 mechanical-age design, result of, 138-139 navigation in Web site design,217-222 memex, 1 navigation buttons, 27 Mena, Federico, 7 NCSA (National Center for Supercomputing mental model. See users’ mental model Applications), 9 bar in Mac OS GUI, 11 necessary use scenarios, 192 menus, 20-21 needs of personas, identifying, 165 methodical temperament, 119 negative personas, 156 Microsoft Internet Explorer,9-10 net present value (NPV) amount, calculating, 70 Microsoft Windows, 5-6 Netscape Navigator,9 Mike’s Bikes case study NLS (oN-Line System), 2 business case for usability,76-82 Norman, Donald, 121, 128 conceptual models, creating, 129-131 notes, writing during usability tests, 235-236 paper prototyping, 105-110 NPV (net present value) amount, calculating, 70 personas, constructing, 156 personas, constructing, 157-159 pilot usability tests, conducting, 248-251 O refining paper prototype test, 192-194 obscurity in software design, 138 Web site navigation features, 220-222 observation skills while conducting usability tests, minimizing windows, 19, 184 152-154, 226-227, 234-236 Minority Report (film), 45 ongoing relationships, establishing, 238-239 Mirsky,Steve, 98 online help systems, 100, 190 misconceptions, adhering to (reasons for failure), open-source software, 7 115 opening windows, 181-183 misunderstandings in seven stages of human Opera, 10 action, 121-122 operating systems mockups, paper prototyping versus, 91 accessibility features, 54-55 modal windows, 184 GUI operating systems, list of, 18-19 modeling phase (Goal-Directed Design Process), outlines for documentation, creating, 102 144 personas, constructing, 147-152, 156-159 P personas, evaluating, 154 Palo Alto Research Center (PARC), 2 personas, prioritizing, 154-156 paper documentation, 98 Mosaic, 9 paper prototyping, 90 mouse pointers, 178-180 advantages of, 93-95 moving conducting pilot tests, 248-251 mouse pointers, 178 constructing key path scenarios, 169 windows, 184-185 defined, 85 MSN.com Maps, 45 disadvantages of, 95-96 multimedia products, Section 508 accessibility,52 Mike’s Bikes case study,105-110 multiple-document interface (MDI), 19, 181-182 overview of, 91 multitasking, 5 product mockups versus, 91 Myers, Isabelle, 115 refining, 192-194 Myers-Briggs Type Indicator (MBTI), 115-117, 130 skepticism toward, overcoming, 92-93 myths about Web site design,200-205 7735_ix.qxp 4/3/2007 11:47 AM Page 281

Index 281

storyboarding versus, 91 Portable Document Format (PDF) documentation, wireframes versus, 91 99 Paper Prototyping (Snyder), 90 portal sites, 206, 210-213 PARC (Palo Alto Research Center), 2 postural design patterns, 173 participants in usability tests postures. See software postures; Web postures establishing rapport with, 239 PowerShell, 30 selecting, 229-230 pragmatic, good design as, 87, 171 partner requirements, 166 presenting usability test results, 245-247 path scenarios, constructing, 169 primary personas, 155-159 patterns of good design, 172-173 primary temperaments, 117-118 PDF (Portable Document Format) competitive temperament, 120-121 documentation, 99 humanistic temperament, 120 perceiving/judging dichotomy,117 methodical temperament, 119 performance measures, 231-232 spontaneous temperament, 119-120 perpetual intermediate users, 140 principles of good design, 172 perpetual intermediates, 189 prioritizing personas, 154-156 personality types problem statements, 164 animals associated with, 118 problems during usability tests, resolving, 239-241 MBTI (Myers-Briggs Type Indicator), 115-117, process interviews, 237 130 product engineers/designers, expectations of, 61 primary temperaments, 117-118 product mockups, 91 competitive temperament, 120-121 production costs, 65-66 humanistic temperament, 120 professionalism of paper prototyping, 92 methodical temperament, 119 profitability of usability design, 67-69 spontaneous temperament, 119-120 programming languages for Web pages, 24-25 personas project teams, 97-98 advantages of, 148-149 prototyping design standards, 75. See also paper constructing, 147-152, 156-159 prototyping evaluating, 154 psychographics in personas, 148 expectations of, 165 psychology of user behavior identifying needs of, 165 MBTI (Myers-Briggs Type Indicator), 115-117 prioritizing, 154-156 primary temperaments requirements, obtaining, 164-166 competitive temperament, 120-121 persuasion process in sales, 148 humanistic temperament, 120 photographs for personas, 154 methodical temperament, 119 PHP,25 spontaneous temperament, 119-120 physical constraints, 88 primary temperaments, 117-118 pilot usability tests, conducting, 233-234, 248-251 reasons for failure, 114-115 planning process seven stages of human action, 121-122 for good documentation design, 97-103 purposeful, good design as, 87, 171 paper prototyping advantages in, 93-94 platform capabilities/constraints in requirements Q analysis, 73 qualitative research, 146-147 platform-independent, 24 quantitative research, 146 pointing devices in GUIs, 31. See also mouse questionnaires, preparing for usability tests, 233 pointers quick and dirty usability testing, 49 pop-up menus, 20 pop-up messages, 187 7735_ix.qxp 4/3/2007 11:47 AM Page 282

282 Index

R Section 508 accessibility,52 security Radio Frequency Identification (RFID) tags, 35 Web engineering, 214 rapport with test participants, establishing, 239 Windows Vista, 38 Raskin, Jef, 45 security interfaces, 34-36 Raymond, Eric, 27 selecting real-world requirements, 166 participants for usability tests, 229-230 Red Hat, 7 usability test techniques, 226-228 Redish, Ginny,153 self-referential design, 149 Redish, Janice, 47, 228, 242 semantic constraints, 88 refinement phase (Goal-Directed Design Process), sensing/intuition dichotomy,116, 122-124 145, 191-194 served personas, 155 reflexive interfaces, 45 seven stages of human action, 121-122 Rehabilitation Act of 1973, 52 severity of usability test data, 243 Reimann, Robert, 49, 86, 139, 140, 143, 164, 171, SGML (Standard Generalized Markup Language), 173, 209 41 Reimer,Jeremy,1 shallow task structures, 124 relationships, establishing ongoing relationships, short-term production costs, 65 238-239 simple tasks, transforming difficult tasks into, reports, writing on usability tests, 243-245 126-127 requirements analysis phase (UEL), 72-73 simplicity requirements-gathering sessions, 228 in conceptual models, 128 requirements phase (Goal-Directed Design in users’ mental models, 139 Process), 144, 164-166 in Web site design,218 research phase (Goal-Directed Design Process), single document interfaces (SDIs), 19 144-147 site visits for observing users, 226-227 resizing windows, 184 smart cards, 34 resolution of Web pages, 33 Snyder,Carolyn, 90 resolving problems during usability tests, 239-241 social constraints, 88 results of usability tests, presenting, 245-247 software development retina scanning, 35 bad behaviors of, 138-139 return on investment (ROI), 69-71, 92 phases of, 136-137 review process for documentation, 103 Section 508 accessibility,52 RFID (Radio Frequency Identification) tags, 35 software postures, 173-177, 205 RIAS (Rich Internet Application System), 13, 44 sound,Web design myths, 202 right mouse button, clicking, 180 sovereign applications, 173, 205, 208 ROI (return on investment) analysis, 69-71, 92 spontaneous temperament, 119-120 rules for Web site design,breaking, 218-220 Sputnik, 8 stakeholder expectations, 60-63 S Stallman, Richard, 7 sales, persuasion process, 148 Standard Generalized Markup Language (SGML), sales people, expectations of, 62 41 scenarios, creating for usability tests, 230-231 standards scope of usability test data, 242 in level 2 design, 74-75 , 22 in user interface design, 189-190 SDIs (single document interfaces), 19 in Web site design search engines, 188 colors and text, 215-216 secondary personas, 155 consistency,215 7735_ix.qxp 4/3/2007 11:47 AM Page 283

Index 283

graphics, 216-217 test scenarios, creating for usability tests, 230-231 navigation, 217-222 testing methods. See usability testing Star,3 testing scripts, preparing for usability tests, 232 Start button, 11 tests. See usability tests statistics, types of, 241 text in Web site design,215-216 storyboarding, 90. See also paper prototyping text user interface (TUI), 30-31 constructing key path scenarios, 169 thinking/feeling dichotomy,116 paper prototyping versus, 91 three-click rule, 128, 219 structural design patterns, 173 time constraints, 89 structuring tasks, 124-125 , 11, 21-22, 26 style guide development, 75 , 187 style sheets, defining for documentation, 102 topology in personas, 148 stylus, 37 Torvalds, Linus, 7 subconscious behavior,125 touch interfaces, 36 subjective measures, 231 trade shows, meeting users at, 228 summative usability testing, 50 training costs, 66 supplemental personas, 155 transforming difficult tasks into simple tasks, 126-127 T transient applications, 174, 205 application Web sites as,209-210 table of contents for documentation, 103 informational Web sites as,208 tabs in MDI (multiple-document interface), portal sites as, 213 181-182 triangulating data, 242 tactile interfaces, 36 trough (of ), 22 tangible interfaces, 45 TUI (text user interface), 30-31 task structures, 124-125 taskbars, 11, 23 tasks U conceptual models UEL (Usability Engineering Life Cycle), 71-72 creating, 127-129 design, testing, and development phase, 73-75 Mike’s Bikes case study,129-131 installation and feedback phase, 75-76 scenarios, creating for usability tests, 230-231 requirements analysis phase, 72-73 transforming from difficult to simple, 126-127 UNIX-based CLIs, 30 user and task analysis URL (Uniform Resource Locator), 24 observing users, 152-154 usability design personas, constructing, 147-159 business case for,60 personas, evaluating, 154 benefits of good design, 64-67 personas, prioritizing, 154-156 framework for,63-64 qualitative research, 146-147 Mike’s Bikes case study,76-82 TCP/IP,8 profitability,67-69 teams for documentation design, 97-98 ROI (return on investment) analysis, 69-71 technical goals, 150 stakeholder expectations, 60-63 technical requirements, 166 Usability Engineering Life Cycle (UEL), 71-76 telecommunications products, Section 508 connection with user interface design and accessibility,52 usability testing, 60 temperaments. See primary temperaments defined, 47 test materials, preparing for usability tests, importance of, 59 232-233 types of, 48-49 7735_ix.qxp 4/3/2007 11:47 AM Page 284

284 Index

Usability Engineering Life Cycle (UEL), 71-72 user behavior design, testing, and development phase, 73-75 conceptual models installation and feedback phase, 75-76 creating, 127-129 requirements analysis phase, 72-73 Mike’s Bikes case study,129-131 usability engineers, 48 conscious versus subconscious usability goal settings in requirements analysis, 73 behavior,125 usability roundtables, 227, 237 knowledge in brain versus knowledge in world, usability scientists, 48 122-124 usability services, 48 psychology of usability tests, 49-50 MBTI (Myers-Briggs Type Indicator), 115-117 analyzing data, 241-243 primary temperaments, 117-121 changes based on, 247 reasons for failure, 114-115 conducting seven stages of human action, 121-122 interviewing skills needed, 236-238 task structures, 124-125 observation skills needed, 234-236 transforming difficult tasks into simple tasks, ongoing relationships, establishing, 238-239 126-127 pilot tests, 233-234, 248-251 user goals, Goal-Directed Design Process, 143-146 rapport with participants, establishing, 239 framework, defining, 166-169 resolving problems during, 239-241 refinement stage, 191-194 conducting, 233 requirements, obtaining, 164-166 connection with user interface design and user and task analysis, 146-159 usability design, 60 user interface design. See also GUIs; user interface defining models goals, creating, 229 accessibility issues measures, determining, 231-232 operating systems, 54-55 participants, selecting, 229 Section 508, 52 participants, selecting, 230 Web Content Accessibility Guidelines, 52-54 test materials, preparing, 232-233 accessibility issues, 51 test scenarios, creating, 230-231 communication with users defining, 228-229 assistants and wizards, 190-191 paper prototyping. See paper prototyping online help systems, 190 presenting results of, 245-247 standards, 189-190 techniques for,226-228 connection with usability design and testing, 60 types of data from, 241 framework, defining, 166-169 writing report on, 243-245 future of, 44-46 usage myths (Web sites),201-202 Mac OS, 43 usage patterns, discovering, 144 Web browsers, 43-44 user and task analysis Windows Vienna, 43 defined, 50 good design. See good design Goal-Directed Design Process, 49 GUI behaviors, 177 observing users, 152-154 mouse pointers, 178-180 personas, constructing, 147-159 refining, 191-194 personas, evaluating, 154 windows, 181-185 personas, prioritizing, 154-156 human characteristics of, 171 qualitative research, 146-147 information cues trends in, 50-51 audio cues, 187 usability testing, 49-50 pop-up messages, 187 7735_ix.qxp 4/3/2007 11:47 AM Page 285

Index 285

search engines, 188 requirements, obtaining, 164-166 visual cues, 186-187 user and task analysis, 146-159 interaction design interviewing when constructing personas, goals of good design, 171 151-152 patterns of good design, 172-173 observing, 152-154, 226-227 principles of good design, 172 users’ mental model interaction design, 171 bad software development behaviors, 138-139 issues and improvements implementation model versus, 139 Linux, 40 phases of software development, 136-137 Mac OS X, 39-40 Web interfaces, 41-42 V Windows Vista, 38-39 validation scenarios, 192 issues and improvements, 42 validity of paper prototyping, 92 requirements, obtaining, 164-166 videos, Section 508 accessibility,52 software postures, 173-177 Vienna (Windows code name), 43 user interface models views, defining, 167 batch interface, 28 visibility in conceptual models, 129 button interfaces, 37 vision statements, 164 CLI (command-line interface), history of, 28-30 VisiOn, 5 GUI (), 30-32 visual information cues, 186-187 security interfaces, 34-36 voice mail hell, 37 tactile interfaces, 36 telephone user interfaces, 37 touch interfaces, 36 W TUI (text user interface), 30-31 W3C (World Wide Web Consortium),Web Content types of, 27-28 Accessibility Guidelines, 52-54 Web interfaces, 32-35 Web,9, 23 user profile in requirements analysis, 73 Web-based applications,44 user surveys, 228 Web browsers users. See also user interface design Address bar,27 behavior defined, 23-24 conceptual models, 127-131 Firefox, 10 conscious versus subconscious behavior,125 future of user interface design, 43-44 knowledge in brain versus knowledge in Internet Explorer,9-10 world, 122-124 Mosaic, 9 psychology of, 114-122 navigation buttons, 27 task structures, 124-125 Netscape Navigator,9 transforming difficult tasks into simple tasks, Opera, 10 126-127 toolbars, 26 constraints on, 88 Web accessibility myths, 204 expectations of, 61 Web Content Accessibility Guidelines, 52-54 experience bell curve, 140-141 Web engineering, 213-215 advanced users, needs of, 143 Web interfaces, 32-35, 41-42 beginners, needs of, 141 Web postures, 205-207 intermediate users, needs of, 142-143 application sites, 208-210 goals, Goal-Directed Design Process, 143-146 informational sites, 208 framework, defining, 166-169 portal sites, 210-213 refinement stage, 191-194 Web programs, unique GUI features, 14 7735_ix.qxp 4/3/2007 11:47 AM Page 286

286 Index

Web site design windows defined, 49 behaviors of, 181-185 GUI design versus, 198-200 closing, 185 history of, 8 defined, 19-20 Internet Explorer,9-10 moving, 184-185 Internet, beginning of, 8 opening, 181-183 Mosaic, 9 resizing, 184 Netscape Navigator,9 wireframes, paper prototyping versus, 91 hyperlinks, 25 wizards, 190-191 interaction with Web sites,199 work re-engineering, 74 myths about, 200-205 World Wide Web,9, 23 programming languages for,24-25 World Wide Web Consortium (W3C),Web Content resolution of, 33 Accessibility Guidelines, 52-54 rules for,breaking, 218-220 world, knowledge in, 122-124 Section 508 accessibility,52 writing standards notes during usability tests, 235-236 colors and text, 215-216 reports on usability tests, 243-245 consistency,215 WWW (World Wide Web),9, 23 graphics, 216-217 navigation, 217-222 X-Y-Z three-click rule, 128 X system, 9 unique GUI features, 13-14 Xerox Web engineering, 213-215 Alto, 2-3 Web postures, 205-207 PARC (Palo Alto Research Center), 2 application sites, 208-210 Star,3 information sites, 208 XGA resolution, 33 portal sites, 210-213 XHTML, 41 Web-safe colors/fonts, 42, 199, 215 XML (Extensible Markup Language), 41 Web sites as documentation,101 wide and deep task structures, 124 zooming interfaces, 45 widgets, 19 ZUI (), 45 Wilson, Chauncy,47, 50 Windows, 5-6 as GUI operating system, 18 history of CLI (command-line interface), 29 unique GUI features, 11 Windows Vienna, 43 Windows Vista, 38-39