Search (3 results, page 1 of 1)

0.026313884 = product of:
  0.05262777 = sum of:
    0.05262777 = sum of:
      0.027008435 = weight(_text_:p in 5135) [ClassicSimilarity], result of:
        0.027008435 = score(doc=5135,freq=2.0), product of:
          0.1359764 = queryWeight, product of:
            3.5955126 = idf(docFreq=3298, maxDocs=44218)
            0.037818365 = queryNorm
          0.19862589 = fieldWeight in 5135, product of:
            1.4142135 = tf(freq=2.0), with freq of:
              2.0 = termFreq=2.0
            3.5955126 = idf(docFreq=3298, maxDocs=44218)
            0.0390625 = fieldNorm(doc=5135)
      0.025619334 = weight(_text_:22 in 5135) [ClassicSimilarity], result of:
        0.025619334 = score(doc=5135,freq=2.0), product of:
          0.13243347 = queryWeight, product of:
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.037818365 = queryNorm
          0.19345059 = fieldWeight in 5135, product of:
            1.4142135 = tf(freq=2.0), with freq of:
              2.0 = termFreq=2.0
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.0390625 = fieldNorm(doc=5135)
  0.5 = coord(1/2)

Date

22. 3.2008 16:18:27

0.008957684 = product of:
  0.017915368 = sum of:
    0.017915368 = product of:
      0.035830736 = sum of:
        0.035830736 = weight(_text_:p in 340) [ClassicSimilarity], result of:
          0.035830736 = score(doc=340,freq=22.0), product of:
            0.1359764 = queryWeight, product of:
              3.5955126 = idf(docFreq=3298, maxDocs=44218)
              0.037818365 = queryNorm
            0.263507 = fieldWeight in 340, product of:
              4.690416 = tf(freq=22.0), with freq of:
                22.0 = termFreq=22.0
              3.5955126 = idf(docFreq=3298, maxDocs=44218)
              0.015625 = fieldNorm(doc=340)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Footnote

Rez. in: JASIST 58(2007) no.7, S.1066-1067 (X. Zhu u. J. Liao): "The user, without whom any product or service would be nothing, plays a very important role during the whole life cycle of products or services. The user's involvement should be from the very beginning, not just after products or services are ready to work. According to ISO 9241-11: 1998, Part 11, Usability refers to "the extent to which a product can be used by specified users to achieve specified goals with effectiveness, efficiency and satisfaction in a specified context of user." As an academic topic of human-computer interaction, Web usability has been studied widely for a long time. This classroom-oriented book, bridging academia and the educational community, talks about Web usability in a student-friendly fashion. It outlines not only the methodology of user-centered Web site design but also details the methods to implement at every stage of the methodology. That is, the book presents the user-centered Web-design approach from both macrocosm and microcosm points of view, which makes it both recapitulative and practical. The most important key word in Web Usability is "user-centered," which means Web developers should not substitute their own personal preferences for the users' needs. The book classifies Web sites into five types: E-commerce, informational, entertainment, community, and intranet. Since the methods used during Web development differ somewhat depending on the type of Web site, it is necessary to have a classification in advance. With Figure 1.3 on p. 17, the book explains the whole user-centered Webdevelopment life cycle (called "methodology" in this book review), which provides a clear path for Web development that is easy to understand, remember, and perform. Since all the following chapters are based on the methodology, a clear presentation of it is paramount. The table on p. 93 summarizes concisely all types of methods for requirements gathering and their advantages and disadvantages. According to this table, appropriate methods can be easily chosen for different Web site development projects. As the author remarked, "requirements gathering is central to the concept of user-centered design," (p. 98) and "one of the hallmarks of user-centered design is usability testing" (p. 205). Stage 2 (collect user requirements) and Stage 5 (perform usability testing) of the user-centered Web-development life cycle are the two stages with the most user involvement: however, this does not mean that all other stages are user unrelated. For example, in Stage 4 (create and modify physical design), frame is not suggested to be used just because most users are unfamiliar with the concept of frame (p. 201). Note that frequently there are several rounds of usability testing to be performed in the four case studies, and some of them are performed before the physical-design stage or even the conceptual-design stage, which embodies the idea of an iterative design process.
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.

0.0047264756 = product of:
  0.009452951 = sum of:
    0.009452951 = product of:
      0.018905902 = sum of:
        0.018905902 = weight(_text_:p in 493) [ClassicSimilarity], result of:
          0.018905902 = score(doc=493,freq=2.0), product of:
            0.1359764 = queryWeight, product of:
              3.5955126 = idf(docFreq=3298, maxDocs=44218)
              0.037818365 = queryNorm
            0.13903812 = fieldWeight in 493, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5955126 = idf(docFreq=3298, maxDocs=44218)
              0.02734375 = fieldNorm(doc=493)
      0.5 = coord(1/2)
  0.5 = coord(1/2)