Search (3 results, page 1 of 1)

0.009253663 = product of:
  0.046268314 = sum of:
    0.046268314 = weight(_text_:books in 493) [ClassicSimilarity], result of:
      0.046268314 = score(doc=493,freq=2.0), product of:
        0.24756333 = queryWeight, product of:
          4.8330836 = idf(docFreq=956, maxDocs=44218)
          0.051222645 = queryNorm
        0.18689486 = fieldWeight in 493, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          4.8330836 = idf(docFreq=956, maxDocs=44218)
          0.02734375 = fieldNorm(doc=493)
  0.2 = coord(1/5)

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.

0.006939962 = product of:
  0.03469981 = sum of:
    0.03469981 = weight(_text_:22 in 5135) [ClassicSimilarity], result of:
      0.03469981 = score(doc=5135,freq=2.0), product of:
        0.17937298 = queryWeight, product of:
          3.5018296 = idf(docFreq=3622, maxDocs=44218)
          0.051222645 = 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.2 = coord(1/5)

Date

22. 3.2008 16:18:27

0.005287808 = product of:
  0.026439039 = sum of:
    0.026439039 = weight(_text_:books in 340) [ClassicSimilarity], result of:
      0.026439039 = score(doc=340,freq=2.0), product of:
        0.24756333 = queryWeight, product of:
          4.8330836 = idf(docFreq=956, maxDocs=44218)
          0.051222645 = queryNorm
        0.10679707 = fieldWeight in 340, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          4.8330836 = idf(docFreq=956, maxDocs=44218)
          0.015625 = fieldNorm(doc=340)
  0.2 = coord(1/5)

Footnote

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.