Search (3 results, page 1 of 1)

0.009059294 = product of:
  0.027177881 = sum of:
    0.0074585797 = product of:
      0.014917159 = sum of:
        0.014917159 = weight(_text_:theory in 340) [ClassicSimilarity], result of:
          0.014917159 = score(doc=340,freq=2.0), product of:
            0.16234003 = queryWeight, product of:
              4.1583924 = idf(docFreq=1878, maxDocs=44218)
              0.03903913 = queryNorm
            0.09188836 = fieldWeight in 340, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              4.1583924 = idf(docFreq=1878, maxDocs=44218)
              0.015625 = fieldNorm(doc=340)
      0.5 = coord(1/2)
    0.019719303 = product of:
      0.039438605 = sum of:
        0.039438605 = weight(_text_:methods in 340) [ClassicSimilarity], result of:
          0.039438605 = score(doc=340,freq=16.0), product of:
            0.15695344 = queryWeight, product of:
              4.0204134 = idf(docFreq=2156, maxDocs=44218)
              0.03903913 = queryNorm
            0.25127584 = fieldWeight in 340, product of:
              4.0 = tf(freq=16.0), with freq of:
                16.0 = termFreq=16.0
              4.0204134 = idf(docFreq=2156, maxDocs=44218)
              0.015625 = fieldNorm(doc=340)
      0.5 = coord(1/2)
  0.33333334 = coord(2/6)

Content

Introduction to Web usability -- Defining the mission and target user population -- Requirements gathering: what information is needed? -- Methods for requirements gathering -- Information architecture and site navigation -- Page design -- Designing for universal usability -- Physical design -- Usability testing -- Implementation and marketing -- Maintaining and evaluating Web sites

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.
The many hands-on examples throughout the book and the four case studies at the end of the book are obvious strong points linking theory with practice. The four case studies are very useful, and it is hard to find such cases in the literature since few companies want to publicize such information. The four case studies are not just simple repeats; they are very different from each other and provide readers specific examples to analyze and follow. Web Usability is an excellent textbook, with a wrap-up (including discussion questions, design exercises, and suggested reading) at the end of each chapter. Each wrap-up first outlines where the focus should be placed, corresponding to what was presented at the very beginning of each chapter. Discussion questions help recall in an active way the main points in each chapter. The design exercises make readers apply to a design project what they have just obtained from the chapter, leading to a deeper understanding of knowledge. Suggested reading provides additional information sources for people who want to further study the research topic, which bridges the educational community back to academia. The book is enhanced by two universal resource locators (URLs) linking to the Addison-Wesley instructor resource center (http://www. aw.com/irc) and the Web-Star survey and project deliverables (http:// www. aw.com/cssupport), respectively. There are valuable resources in these two URLs, which can be used together with Web Usability. Like the Web, books are required to possess good information architecture to facilitate understanding. Fortunately, Web Usability has very clear information architecture. Chap. 1 introduces the user-centered Web-development life cycle, which is composed of seven stages. Chap. 2 discusses Stage l, chaps. 3 and 4 detail Stage 2, chaps. 5 through 7 outline Stage 3, and chaps. 8 through I1 present Stages 4 through 7, respectively. In chaps. 2 through 11, details (called "methods" in this review) are given for every stage of the methodology. The main clue of the book is how to design a new Web site; however, this does not mean that Web redesign is trivial and ignored. The author mentions Web redesign issues from time to time, and a dedicated section is presented to discuss redesign in chaps. 2, 3, 10, and 11.
Web Usability is undoubtedly a success. After reading this book, Web designers will pay attention to both the content and the usability; otherwise, the majority might overlook the usability. Although this book mainly focuses on students and instructors, it also is appropriate for those who want to develop a user-centered Web site but do not know how. We would suggest that an initial reading is necessary to know what is included under each section title; from then on, when the methodology and methods are applied to guide a real-world project, only the table of contents and the chapter wrap-ups need to be reread, and other parts only when important details are forgotten. With the help of so many examples and strongly viable methods, Web Usability explains almost everything necessary during user-centered Web development and provides tips to help avoid some common mistakes. All of these characteristics facilitate effective and efficient Web-development processes. Similarly, the book reaches its content goal and usability goal as well. In short, Web Usability is an excellent case for book usability: a user-centered edit approach!"

0.003113411 = product of:
  0.018680464 = sum of:
    0.018680464 = product of:
      0.03736093 = sum of:
        0.03736093 = weight(_text_:29 in 1550) [ClassicSimilarity], result of:
          0.03736093 = score(doc=1550,freq=2.0), product of:
            0.13732746 = queryWeight, product of:
              3.5176873 = idf(docFreq=3565, maxDocs=44218)
              0.03903913 = queryNorm
            0.27205724 = fieldWeight in 1550, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5176873 = idf(docFreq=3565, maxDocs=44218)
              0.0546875 = fieldNorm(doc=1550)
      0.5 = coord(1/2)
  0.16666667 = coord(1/6)

Date

26. 8.2005 13:29:50

0.0022038599 = product of:
  0.013223159 = sum of:
    0.013223159 = product of:
      0.026446318 = sum of:
        0.026446318 = weight(_text_:22 in 5135) [ClassicSimilarity], result of:
          0.026446318 = score(doc=5135,freq=2.0), product of:
            0.1367084 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.03903913 = 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)
  0.16666667 = coord(1/6)

Date

22. 3.2008 16:18:27