Available:*
Library | Item Barcode | Call Number | Material Type | Item Category 1 | Status |
---|---|---|---|---|---|
Searching... | 30000004720276 | TK5105.888 L394 2006 | Open Access Book | Book | Searching... |
On Order
Summary
Summary
User Interface Design/Human Computer Interaction Web Usability: A User-Centered Design Approach Jonathan Lazar, Towson University ISBN 0-321-32135-9 DESIGN WITH THE USER IN MIND A Web site design that does not consider its user is a Web site that is destined to be a disappointing experience for the user. This new book by Jonathan Lazar provides readers with the concepts and tools needed to develop Web sites that maximize the user experience. It takes readers through the entire User-Centered Development Life Cycle, demonstrating practical skills and techniques that will help them for years to come. THE USER-CENTERED DEVELOPMENT LIFE CYCLE The User-Centered Development Life Cycle ensures that the needs of a Web site's users are the focus of the Web site's design, from its inception through its implementation and management. Keeping this focus--while collecting requirements, designing pages, and performing usability testing--results in a more effective design and more satisfied users. Real-world applications are highlighted in four Case Studies, which demonstrate how both commercial and noncommercial organizations designed user-centered Web sites: / kodak.com (Eastman Kodak) / PlayFoo Cancer Institute) / asha.org (American Speech-Language Hearing Association) Jonathan Lazar's unique combination of expertise--teaching, research, and practice of HCI, informatics, IT, and accessibility--is what really sets him apart from the other 'Web experts' publishing today. His text reflects the diversity that successful Web design requires by balancing user-centeredness with a solid understanding of technical and business issues. --ARNIE LUND, Director of Design and Usability, Microsoft Corporation This text is magic; it packs experience between the covers of a book. Lazar's energetic style is filled with examples, focused lists, and Case Studies that walk readers through the Web design process and give them the confidence to do it themselves. He makes user-centered design seem easy by making sure that people matter. If every designer trained from this book, the World Wide Web would be a better place. --BEN SHNEIDERMAN, Professor of Computer Science, University of Maryland For more information about Addison-Wesley Computing books visit aw.com/computin
Table of Contents
Chapter 1 Introduction to Web Usability | p. 1 |
Introduction | p. 1 |
Why Focus on the User? | p. 3 |
Greater Profits | p. 3 |
Reduce User Frustration | p. 4 |
How Is the Web Different from Traditional Information Systems? | p. 5 |
No User Training | p. 6 |
Predictability Means Easy Use | p. 7 |
Traditional Development of Information Systems | p. 8 |
New Challenges in Web Development Projects | p. 8 |
The Role of Users | p. 9 |
Types of Web Sites | p. 10 |
Defining the User Population | p. 12 |
Defining the User Tasks | p. 13 |
The User-Centered Web Development Life Cycle | p. 16 |
Stage 1 Define the Mission of Your Web Site and Its Target User Population | p. 17 |
Stage 2 Collect the User Requirements for Your Web Site | p. 18 |
Stage 3 Create and Modify the Conceptual Design of Your Web Site | p. 19 |
Stage 4 Create and Modify the Physical Design | p. 19 |
Stage 5 Perform Web Site Usability Testing | p. 19 |
Stage 6 Implement and Market Your Web Site | p. 19 |
Stage 7 Evaluate and Improve Your Web Site | p. 20 |
Cost Justifying User Involvement in Development | p. 20 |
Project Management Techniques | p. 22 |
Clear Objectives | p. 23 |
Specific Responsibilities | p. 23 |
Documentation | p. 23 |
Progress Reports | p. 23 |
Chapter Wrap-Up | p. 24 |
Discussion Questions | p. 24 |
Design Exercise | p. 24 |
Suggested Reading | p. 25 |
Chapter 2 Defining the Mission and Target User Population | p. 29 |
Introduction | p. 29 |
Mission of the Web Site | p. 30 |
Typical Organizational Goals of Different Web Sites | p. 30 |
Process of Determining the Site Mission | p. 31 |
Writing a Mission Statement | p. 33 |
What If There Isn't a Mission? | p. 34 |
Targeted User Population | p. 36 |
Advantages of Knowing a Targeted Population | p. 37 |
Targeting Different User Groups | p. 38 |
Developing User Profiles and Audience Splitting: Implications for the Development Process | p. 38 |
Diverse User Populations | p. 41 |
Additional Considerations for Web Site Redesign | p. 43 |
Web Site Logs: Tracking Where Users Have Been | p. 44 |
Research Prior Relationships | p. 45 |
Chapter Wrap-Up | p. 46 |
Discussion Questions | p. 46 |
Design Exercise | p. 47 |
Suggested Reading | p. 47 |
Chapter 3 Requirements Gathering-What Information Is Needed? | p. 51 |
Introduction | p. 51 |
General User Demographic Information | p. 52 |
Domain Knowledge | p. 53 |
User Computing Experience | p. 56 |
Using Interface Metaphors | p. 59 |
Adapting to Past Experiences | p. 59 |
User Computing Environment | p. 61 |
Task Analysis and Content | p. 63 |
Determining Content Preferences | p. 64 |
Assessing Existing Content | p. 66 |
Responsibility for Developing Content | p. 66 |
Benchmarking | p. 67 |
Additional Considerations for Web Site Redesign | p. 69 |
Chapter Wrap-Up | p. 70 |
Design Exercise | p. 70 |
Discussion Questions | p. 70 |
Suggested Reading | p. 71 |
Chapter 4 Methods for Requirements Gathering | p. 75 |
Introduction | p. 75 |
Determining Access to Users | p. 76 |
Guidelines for Choosing Access Techniques | p. 77 |
Introducing Surveys | p. 78 |
Paper Surveys | p. 80 |
Electronic Surveys | p. 81 |
E-Mail Surveys | p. 82 |
Web-Based Surveys | p. 83 |
Informing Users about the Electronic Survey | p. 85 |
Interviews | p. 87 |
Phone Interviews | p. 88 |
Focus Groups | p. 88 |
The Moderator's Role | p. 90 |
Challenges of Working with Focus Groups | p. 90 |
Electronic Focus Groups | p. 91 |
Participatory Design | p. 92 |
Other User Involvement Activities for Structuring Information | p. 93 |
Card Sorting | p. 94 |
Scenarios | p. 95 |
Paper Prototyping | p. 95 |
Final Thoughts | p. 96 |
Chapter Wrap-Up | p. 98 |
Discussion Questions | p. 98 |
Design Exercise | p. 99 |
Suggested Reading | p. 99 |
Chapter 5 Information Architecture and Site Navigation | p. 103 |
Introduction | p. 103 |
Web Site Content Objects | p. 104 |
Determining the Web Content Objects | p. 105 |
Organizing Web Content Objects | p. 106 |
Information Architecture | p. 107 |
Theoretical Foundations/Relationship to Menu Design | p. 108 |
Web Navigation | p. 112 |
Knowing Where Users Have Been | p. 112 |
Knowing Where Users Are | p. 113 |
Knowing Where Users Can Go | p. 113 |
Organizing and Labeling Navigation Choices | p. 120 |
Client Feedback | p. 122 |
Breadcrumbs Navigation | p. 123 |
Search Engines for Navigation | p. 124 |
Location of Navigation | p. 127 |
Technical Requirements for Navigation | p. 128 |
Chapter Wrap-Up | p. 131 |
Design Exercise | p. 131 |
Discussion Questions | p. 131 |
Suggested Reading | p. 132 |
Chapter 6 Page Design | p. 135 |
Introduction | p. 135 |
Technical Considerations | p. 136 |
Download Speed | p. 136 |
Plug-Ins | p. 139 |
Animation | p. 140 |
Screen Resolution | p. 142 |
Layout Considerations | p. 142 |
Cluttered Design | p. 142 |
Background Patterns | p. 144 |
Grids and Layouts | p. 145 |
Font Color | p. 146 |
Font Size and Face | p. 148 |
Text Spacing | p. 149 |
Content Considerations | p. 150 |
Identification | p. 150 |
Credibility | p. 151 |
Chapter Wrap-Up | p. 154 |
Design Exercise | p. 154 |
Discussion Questions | p. 154 |
Suggested Readings | p. 155 |
Chapter 7 Designing for Universal Usability | p. 159 |
Introduction | p. 159 |
User Diversity | p. 160 |
Older Users | p. 160 |
Younger Users | p. 162 |
Users with Disabilities | p. 164 |
Browser Diversity | p. 170 |
Browser Usage Data | p. 173 |
Common Browser Incompatibility Problems | p. 173 |
Solutions for Multiple-Browser Design | p. 180 |
Chapter Wrap-Up | p. 182 |
Design Exercise | p. 182 |
Discussion Questions | p. 182 |
Suggested Reading | p. 183 |
Chapter 8 Physical Design | p. 187 |
Introduction | p. 187 |
Coding by Hand Using a Text Editor | p. 188 |
Web Development Applications | p. 191 |
Macromedia Dreamweaver | p. 191 |
Microsoft FrontPage | p. 192 |
How to Code Navigation | p. 194 |
Table-Based Navigation | p. 194 |
Frame-Based Navigation | p. 197 |
Gathering Content for Web Pages | p. 201 |
Functionality Testing: Does the Code Work? | p. 202 |
Chapter Wrap-Up | p. 203 |
Design Exercise | p. 203 |
Discussion Questions | p. 203 |
Suggested Reading | p. 204 |
Chapter 9 Usability Testing | p. 205 |
Introduction | p. 205 |
Expert-Based Reviews | p. 207 |
Heuristic Review | p. 209 |
Guidelines Review | p. 210 |
Consistency Inspection | p. 212 |
User-Based Testing | p. 213 |
1 Select Representative Users | p. 214 |
2 Select the Setting | p. 215 |
3 Decide What Tasks Users Should Perform | p. 219 |
4 Decide What Type of Data to Collect | p. 220 |
5 Before the Test Session | p. 224 |
6 During the Test Session | p. 225 |
7 Debriefing After the Session | p. 225 |
Automated Usability Testing | p. 225 |
Incorporating Testing Feedback | p. 229 |
Chapter Wrap-Up | p. 231 |
Design Exercise | p. 231 |
Discussion Questions | p. 231 |
Suggested Reading | p. 232 |
Chapter 10 Implementation and Marketing | p. 235 |
Introduction | p. 235 |
Housing the Web Site | p. 236 |
Domain Name | p. 236 |
The Contract for Web Hosting | p. 237 |
Final Acceptance Tests on the Web Server | p. 238 |
Marketing: Bringing Users to Your Web Site | p. 238 |
Guessing a URL | p. 239 |
Being Given the URL | p. 240 |
Linking to a URL | p. 242 |
Using a Search Engine | p. 244 |
Considerations for Site Redesign | p. 247 |
Chapter Wrap-Up | p. 249 |
Design Exercise | p. 249 |
Discussion Questions | p. 249 |
Suggested Reading | p. 250 |
Chapter 11 Maintaining and Evaluating Web Sites | p. 251 |
Introduction | p. 251 |
Maintenance of Web Sites | p. 252 |
Evaluation of Web Sites | p. 252 |
Using Surveys for Evaluation | p. 254 |
Reaching Nonusers: Interviews and Focus Groups | p. 260 |
Web Usage Data | p. 260 |
When to Redesign a Web Site | p. 265 |
Chapter Wrap-Up | p. 267 |
Design Exercise | p. 267 |
Discussion Questions | p. 267 |
Suggested Reading | p. 268 |
Case Study A kodak.com | p. 271 |
Background | p. 271 |
Mission of the Web Site | p. 272 |
Target User Population | p. 275 |
Plan for Requirements Gathering | p. 276 |
Web Server Logs | p. 276 |
Search Logs | p. 278 |
Interviews with Kodak Business Units | p. 280 |
Focus Groups | p. 280 |
Usability Testing | p. 283 |
Guest Book Messages from Visitors | p. 287 |
User Surveys | p. 287 |
Requirements Collection and Site Design | p. 288 |
Business Unit Interviews | p. 288 |
Consumer Focus Groups | p. 288 |
Dealer Focus Groups | p. 289 |
Synthesizing Requirements | p. 290 |
Conceptual Design | p. 291 |
Information Architecture | p. 292 |
Iterative Design with Usability Testing | p. 293 |
Usability Testing, Round One | p. 293 |
Page Layout | p. 297 |
Introduction | p. 297 |
Focus on Text | p. 298 |
The Look of the New Pages | p. 298 |
Physical Design | p. 299 |
Developing Web Pages | p. 299 |
Usability Testing | p. 300 |
Introduction | p. 300 |
Computer-Based Usability Testing (Usability Testing, Round Two) | p. 301 |
Implementation and Marketing | p. 301 |
Previewing the New Design with Users | p. 301 |
A Sampling of the Best | p. 305 |
A Sampling of the Worst | p. 306 |
Marketing | p. 307 |
After the Launch | p. 307 |
Ongoing Maintenance | p. 308 |
Case Study B asha.org | p. 309 |
Defining the Mission and Target User Population | p. 309 |
The ASHA Web Site When the Usability Engineering Process Started | p. 310 |
Usability Presentation | p. 312 |
Requirements Gathering with Users | p. 312 |
Interviews at National Headquarters | p. 313 |
Ethnography in the Action Center | p. 314 |
Users' Feedback | p. 314 |
Analysis of Web Logs | p. 315 |
Review of Other Professional Studies | p. 315 |
Web Survey | p. 316 |
User Groups | p. 316 |
Outcomes | p. 319 |
Usability Testing: Expert Review | p. 319 |
Expert Review Findings | p. 320 |
The ASHA Community: Building and Connecting | p. 321 |
Site Information Architecture | p. 321 |
Site Navigation | p. 322 |
Graphics | p. 323 |
Special Needs | p. 324 |
Outcomes | p. 325 |
Requirements Gathering with Users: Focus Groups | p. 325 |
Focus Groups Findings | p. 326 |
Outcomes | p. 329 |
Prototype Design and Building | p. 329 |
Usability Testing: User Observations | p. 330 |
Finding Information on Stuttering for a Parent | p. 331 |
Observing Users' Working with the Prototype | p. 332 |
User Survey | p. 332 |
Interviews | p. 333 |
User Success | p. 334 |
User Satisfaction | p. 335 |
Outcomes | p. 336 |
Conclusions | p. 338 |
Case Study C CancerNet | p. 339 |
Overview | p. 340 |
The Communication Technologies Branch-Why Is a Cancer Organization Involved in Usability Engineering? | p. 340 |
Defining the Mission and the Target User Population | p. 343 |
Requirements Gathering with Users: Learning What Users Want | p. 343 |
Information Architecture and Site Navigation | p. 346 |
Usability Testing | p. 346 |
Launching the Site | p. 350 |
Lessons Learned Overall | p. 350 |
Case Study D PlayFootball.com | p. 359 |
Introduction | p. 359 |
Defining the Mission and Target User Population | p. 360 |
Requirements Gathering | p. 360 |
Findings from the Observational Play Groups | p. 361 |
Toward a Homepage: Site Navigation | p. 364 |
Focus Group Findings | p. 366 |
Comments on the Homepage Design | p. 367 |
Finalizing the Homepage | p. 369 |
Page Design | p. 370 |
Usability Testing | p. 371 |
Summary and Conclusions | p. 372 |
Index | p. 375 |
Credits | p. 393 |