Lazar, J.: Web usability : a user-centered design approach (2006)
0.00
0.0044732857 = product of:
0.013419856 = sum of:
0.013419856 = weight(_text_:search in 340) [ClassicSimilarity], result of:
0.013419856 = score(doc=340,freq=2.0), product of:
0.1747324 = queryWeight, product of:
3.475677 = idf(docFreq=3718, maxDocs=44218)
0.05027291 = queryNorm
0.076802336 = fieldWeight in 340, product of:
1.4142135 = tf(freq=2.0), with freq of:
2.0 = termFreq=2.0
3.475677 = idf(docFreq=3718, maxDocs=44218)
0.015625 = fieldNorm(doc=340)
0.33333334 = coord(1/3)
- Footnote
- Besides the major well-known software applications such as FrontPage and Dreamweaver (pp. 191-194), many useful software tools can be adopted to assist and accelerate the Web-development process, resulting in improvement of the productivity of the Web industry. Web Usability mentions such tools as the "code validator" (p. 189) to identify problematic areas of the handwritten code against spelling and usage, the tool available at a given URL address to convert portable document format (PDF) files into hypertext markup language (HTML) files (p. 201), WEBXACT, WebSAT, A-Prompt, Dottie, InFocus, and RAMP (pp. 226-227) to automate usability testing, and ClickTracks, NetTracker, WebTrends, and Spotfire (p. 263) to summarize Web-usage data and analyze the trends. Thus, Web developers are able to find these tools and benefit from them. Other strengths of the book include the layout of each page, which has a wide margin in which readers may easily place notes, and the fact that the book is easy to read and understand. Although there are many strengths in this book, a few weaknesses are evident. All chapter wrap-ups should have an identical layout. Without numbering for sections and subsections, it is very likely that readers will lose sense of where they are in the overall information architecture of the book. At present, the only solution is to frequently refer to the table of contents to confirm the location. The hands-on example on p. 39 would be better placed in chap. 4 because it focuses on a requirements gathering method, the interview. There are two similar phrases, namely "user population" and "user group," that are used widely in this book. User population is composed of user groups; however, they are not strictly used in this book. The section title "Using a Search Engine" (p. 244) should be on the same level as that of the section "Linking to a URL," and not as that of the section entitled "Marketing: Bringing Users to Your Web Site," according to what the author argued at the top of p. 236.
