Search (4 results, page 1 of 1)

0.017288294 = product of:
  0.069153175 = sum of:
    0.069153175 = weight(_text_:services in 1550) [ClassicSimilarity], result of:
      0.069153175 = score(doc=1550,freq=4.0), product of:
        0.17221296 = queryWeight, product of:
          3.6713707 = idf(docFreq=3057, maxDocs=44218)
          0.046906993 = queryNorm
        0.40155616 = fieldWeight in 1550, product of:
          2.0 = tf(freq=4.0), with freq of:
            4.0 = termFreq=4.0
          3.6713707 = idf(docFreq=3057, maxDocs=44218)
          0.0546875 = fieldNorm(doc=1550)
  0.25 = coord(1/4)

Footnote

Rez. in: Library resources and technical services 44(2000) no.2, S.105-106 (J. Gelfand)

0.004939513 = product of:
  0.019758051 = sum of:
    0.019758051 = weight(_text_:services in 340) [ClassicSimilarity], result of:
      0.019758051 = score(doc=340,freq=4.0), product of:
        0.17221296 = queryWeight, product of:
          3.6713707 = idf(docFreq=3057, maxDocs=44218)
          0.046906993 = queryNorm
        0.114730336 = fieldWeight in 340, product of:
          2.0 = tf(freq=4.0), with freq of:
            4.0 = termFreq=4.0
          3.6713707 = idf(docFreq=3057, maxDocs=44218)
          0.015625 = fieldNorm(doc=340)
  0.25 = coord(1/4)

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.

0.003972031 = product of:
  0.015888125 = sum of:
    0.015888125 = product of:
      0.03177625 = sum of:
        0.03177625 = weight(_text_:22 in 5135) [ClassicSimilarity], result of:
          0.03177625 = score(doc=5135,freq=2.0), product of:
            0.1642603 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.046906993 = 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.25 = coord(1/4)

Date

22. 3.2008 16:18:27

0.002575955 = product of:
  0.01030382 = sum of:
    0.01030382 = product of:
      0.02060764 = sum of:
        0.02060764 = weight(_text_:management in 493) [ClassicSimilarity], result of:
          0.02060764 = score(doc=493,freq=2.0), product of:
            0.15810528 = queryWeight, product of:
              3.3706124 = idf(docFreq=4130, maxDocs=44218)
              0.046906993 = queryNorm
            0.13034125 = fieldWeight in 493, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.3706124 = idf(docFreq=4130, maxDocs=44218)
              0.02734375 = fieldNorm(doc=493)
      0.5 = coord(1/2)
  0.25 = coord(1/4)

Abstract

Some web sites "work" and some don't. Good web site consultants know that you can't just jump in and start writing HTML, the same way you can't build a house by just pouring a foundation and putting up some walls. You need to know who will be using the site, and what they'll be using it for. You need some idea of what you'd like to draw their attention to during their visit. Overall, you need a strong, cohesive vision for the site that makes it both distinctive and usable. Information Architecture for the World Wide Web is about applying the principles of architecture and library science to web site design. Each web site is like a public building, available for tourists and regulars alike to breeze through at their leisure. The job of the architect is to set up the framework for the site to make it comfortable and inviting for people to visit, relax in, and perhaps even return to someday. Most books on web development concentrate either on the aesthetics or the mechanics of the site. This book is about the framework that holds the two together. With this book, you learn how to design web sites and intranets that support growth, management, and ease of use. Special attention is given to: * The process behind architecting a large, complex site * Web site hierarchy design and organization Information Architecture for the World Wide Web is for webmasters, designers, and anyone else involved in building a web site. It's for novice web designers who, from the start, want to avoid the traps that result in poorly designed sites. It's for experienced web designers who have already created sites but realize that something "is missing" from their sites and want to improve them. It's for programmers and administrators who are comfortable with HTML, CGI, and Java but want to understand how to organize their web pages into a cohesive site. The authors are two of the principals of Argus Associates, a web consulting firm. At Argus, they have created information architectures for web sites and intranets of some of the largest companies in the United States, including Chrysler Corporation, Barron's, and Dow Chemical.