<?xml version="1.0" encoding="UTF-8"?>
<books>
  <book number="1">
    <metadata>
      <title shortTitle="Improving Web Site Usability">Improving
      the Usability of a Web Site Through Expert Reviews and
      Usability Testing</title>
      <authors>
        <author>Millicent Marigold</author>
        <author>Montana Marigold</author>
      </authors>
      <publicationInfo>
        <place>New York</place>
        <publisher>Ersatz Publications</publisher>
        <dateIssued>2001</dateIssued>
        <dateRevised>2002</dateRevised>
      </publicationInfo>
      <price>25.99</price>
      <subjects xml:lang="en">
        <subject>Usability testing</subject>
        <subject>Web site development</subject>
        <subject>Heuristic evaluation</subject>
        <subject>Cognitive walk-through</subject>
        <subject>Web site usability</subject>
      </subjects>
      <subjects xml:lang="it">
        <subject>Test di usabilit&#224;</subject>
        <subject>Sviluppo di siti web</subject>
        <subject>Euristiche di valutazione</subject>
        <subject>Percorsi cognitivi</subject>
        <subject>Usabilit&#224; di siti web</subject>
      </subjects>
    </metadata>
    <content>
      <introduction>
        <author>Elina Rose</author>
        <p>The usability of a Web site is how well the site
        supports the user in achieving specified goals. A Web
        site should facilitate learning, and enable efficient and
        effective task completion, while propagating few errors.
        Satisfaction with the site is also important. The user
        must not only be well-served, but must feel
        well-served.</p>
        <p>Expert reviews and usability testing are methods of
        identifying problems in layout, terminology, and
        navigation before they frustrate users and drive them
        away from your site.</p>
        <p>The most successful projects employ multiple methods
        in multiple iterations. As Millicent Marigold remarked
        during a recent conference, "Don't stop. Iterate,
        iterate, then iterate again."</p>
        <p>This book has been approved by the Web Site Users
        Association.</p>
      </introduction>
      <part number="1">
        <title>Expert Reviews</title>
        <introduction>
          <p>Expert reviewers identify problems and recommend
          changes to web sites based on research in human
          computer interaction and their experience in the
          field.</p>
          <p>Two expert review methods are discussed here. They
          are heuristic evaluation and cognitive
          walk-through.</p>
          <p>Expert review methods should be initiated early in
          the development process, as soon as paper 
          <b>p</b>
          rototypes (hand-drawn pictures of Web pages) or 
          <b>w</b>
          ireframes (electronic mockups) are available. They
          should be conducted using the hardware and software
          similar to that employed by users.</p>
        </introduction>
        <chapter>
          <title>Heuristic Evaluation</title>
          <p>Expert reviewers critique an interface to determine
          conformance with recognized usability principles. 
          <footnote>One of the best known lists of heuristics is 
          <citation
          url="http://www.useit.com/papers/heuristic/heuristic_list.html">
          Ten Usability Heuristics by Jacob Nielson</citation>
          . Another is 
          <citation
          url="http://usability.gov/guidelines/index.html">
          Research-Based Web Design and Usability
          Guidelines</citation>
          </footnote>
          </p>
        </chapter>
        <chapter>
          <title>Cognitive Walk-Through</title>
          <p>Expert reviewers evaluate Web site understandability
          and ease of learning while performing specified tasks.
          They walk through the site answering questions such as
          "Would a user know by looking at the screen how to
          complete the first step of the task?" and "If the user
          completed the first step, would the user know what to
          do next?," with the goal of identifying any obstacles
          to completing the task and assessing whether the user
          would cognitively be aware that he was successful in
          completing a step in the process.</p>
        </chapter>
      </part>
      <part number="2">
        <chapter>
          <title>Usability Testing</title>
          <p>Once the problems identified by expert reviews have
          been corrected, it is time to conduct some tests of the
          site with your unique audience or audiences by
          conducting usability testing.</p>
          <p>Users are asked to complete tasks which measure the
          success of the information architecture and
          navigational elements of the site.</p>
          <p>Then changes are made to improve service to
          users.</p>
        </chapter>
      </part>
    </content>
  </book>
  <book number="2">
    <metadata>
      <title shortTitle="Usability Basics">Usability Basics: How
      to Plan for and Conduct Usability Tests on Web Site Thereby
      Improving the Usability of Your Web Site</title>
      <publicationInfo>
        <place>New York</place>
        <publisher>Ersatz Publications</publisher>
        <publisher>Electronic BookWorks</publisher>
        <dateIssued>2000</dateIssued>
        <dateRevised>2001</dateRevised>
      </publicationInfo>
      <price>174.00</price>
      <subjects xml:lang="en">
        <subject>Usability testing</subject>
        <subject>Web site development</subject>
        <subject>Guides and finding aids</subject>
      </subjects>
      <subjects xml:lang="it">
        <subject>Test di usabilit&#224;</subject>
        <subject>Sviluppo di siti web</subject>
        <subject>Guide e aiuti di ricerca</subject>
      </subjects>
    </metadata>
    <content>
      <introduction>
        <p>This is a basic handbook for planning and conducting
        usability tests on Web sites. Usability testing should be
        used in conjunction with other expert review methods.</p>
        <p>This book has not been approved by the Web Site Users
        Association.</p>
      </introduction>
      <part number="1">
        <chapter>
          <title>Planning then Conducting Usability Tests</title>
          <p>Take the following steps to plan usability testing. 
          <step number="1">Clarify and articulate the goal of the
          usability testing.</step>
          <step number="2">Identify tasks which are critical for
          users to be able to complete successfully.</step>
          <step number="3">Compile a script of questions or
          instructions which will prompt the user to attempt
          those tasks.</step>
          <step number="4">Identify your users and begin
          recruiting them.</step>
          <step number="5">Conduct a pretest on a few
          users.</step>
          <step number="6">Edit the script based on insights
          gleaned from the pretest.</step>
          <step number="7">Resume testing.</step>
          </p>
        </chapter>
      </part>
      <part number="2">
        <chapter>
          <title>Conducting Usability Tests</title>
          <p>Users can be tested at any computer workstation 
          <footnote>They may be most comfortable at their own
          workstation.</footnote>
          or in a lab.</p>
          <p>Give the user the script, then assure them that you
          are testing the Web site, not them. Users are asked to
          verbalize their thoughts as they complete the tasks.
          The event is recorded or someone takes notes. It is
          often preferable to have two testers, 
          <footnote>Usability testing can be done at great
          expense or on a shoe string, using 
          <testingProcedure>in-house expertise</testingProcedure>
          or 
          <testingProcedure>contracting with human computer
          interaction professionals</testingProcedure>
          .</footnote>
          one to ask the questions, another to take notes.
          Testers should offer no guidance or comments to the
          user. Mouse movements, typing, expressions, and the
          user's words should be recorded.</p>
        </chapter>
        <chapter>
          <title>Evaluating and Implementing Results</title>
          <p>Compile the results and review collectively. Make
          changes to the site to alleviate the problems found in
          Web site components which were propagating the largest
          number of or the most devastating errors. Begin new
          iterations of testing and changes, until users are
          successful in the accomplishing the tasks.</p>
        </chapter>
      </part>
    </content>
  </book>
  <book number="3">
    <metadata>
      <title shortTitle="Usabilityguy Manuscript Guide">John
      Wesley Usabilityguy: A Register of His Papers</title>
      <authors>
        <author>Millicent Marigold</author>
        <author>Morty Marigold</author>
      </authors>
      <publicationInfo>
        <publisher>Ersatz Manuscript Library</publisher>
        <dateIssued>1998</dateIssued>
        <dateRevised>2002</dateRevised>
      </publicationInfo>
      <price>21.49</price>
      <subjects xml:lang="en">
        <subject>Computers</subject>
        <subject>Software evaluation</subject>
        <subject>Usability testing</subject>
        <subject>Manuscript collections</subject>
      </subjects>
      <subjects xml:lang="it">
        <subject>Calcolatori</subject>
        <subject>Valutazione di software</subject>
        <subject>Test di usabilit&#224;</subject>
        <subject>Collezioni di manoscritti</subject>
      </subjects>
    </metadata>
    <content>
      <introduction>
        <p>The papers of John Wesley Usabilityguy span the years
        1946-2001, with the bulk of the items concentrated in the
        period from 1985 to 2001. The papers feature his career
        as a developer of software applications and usability
        specialist. The collection consists of correspondence,
        memoranda, journals, speeches, article drafts, book
        drafts, notes, charts, graphs, family papers, clippings,
        printed matter, photographs, r&#233;sum&#233;s and other
        materials.</p>
      </introduction>
      <part number="1">
        <container type="box">1-12</container>
        <title>Subject File, 
        <date normalize="1930/1974">1930-1974</date>
        </title>
        <introduction>
          <p>Correspondence, telegrams, memoranda, journals,
          logs, testimony, approved travel orders, invitations,
          charts, graphs, forms, biographical data, photographs,
          book drafts, clippings and other printed matter,
          r&#233;sum&#233;s and miscellaneous material. Organized
          by name of person or organization, topic, or type of
          material.</p>
        </introduction>
        <component>
          <container type="box">1</container>
          <componentTitle>Computers</componentTitle>
          <subComponent>
            <componentTitle>Software, 
            <componentDate normalize="1946/1947">
            1946-1947</componentDate>
            </componentTitle>
          </subComponent>
          <subComponent>
            <componentTitle>Human Computer Interaction research, 
            <componentDate normalize="1945/1952">
            1945-1952</componentDate>
            </componentTitle>
            <subsubComponent>
              <componentTitle>Flow diagram, 
              <componentDate normalize="1950">
              1950</componentDate>
              </componentTitle>
            </subsubComponent>
            <subsubComponent>
              <componentTitle>General, 
              <componentDate normalize="1947/1951">
              1947-1951</componentDate>
              </componentTitle>
            </subsubComponent>
            <subsubComponent>
              <container type="box">2</container>
              <componentTitle>Eye Movement research, 
              <componentDate normalize="1949/1950">
              1949-1950</componentDate>
              </componentTitle>
            </subsubComponent>
            <subsubComponent>
              <componentTitle>User profiling, 
              <componentDate normalize="1950/1959">
              1950s</componentDate>
              </componentTitle>
            </subsubComponent>
          </subComponent>
        </component>
        <component>
          <componentTitle>Web User Appreciation Award, 
          <componentDate normalize="1956">1956</componentDate>
          </componentTitle>
        </component>
      </part>
      <part number="2">
        <container type="box">3-5</container>
        <title>Writings File, 
        <date normalize="1985/1999">1985-1999</date>
        </title>
        <introduction>
          <p>Correspondence, articles, book drafts, notes,
          contracts, clippings, and printed matter. Arranged
          alphabetically by type (articles, books, reports, and
          miscellaneous) and therein alphabetically by type of
          material, subject, or title.</p>
        </introduction>
        <component>
          <componentTitle>Writings by
          Usabilityguy</componentTitle>
          <subComponent>
            <componentTitle>
              <componentDate normalize="1996">
              1996</componentDate>
            </componentTitle>
            <subsubComponent>
              <componentTitle>"How Many Users Are Enough for User
              Testing?"</componentTitle>
            </subsubComponent>
            <subsubComponent>
              <componentTitle>"How to Evaluate Results from User
              Tests."</componentTitle>
            </subsubComponent>
            <subsubComponent>
              <container type="box">5</container>
              <componentTitle>"When Are You Done
              Testing?"</componentTitle>
            </subsubComponent>
            <subsubComponent>
              <componentTitle>"Do-It-Yourself User
              Testing"</componentTitle>
            </subsubComponent>
          </subComponent>
        </component>
        <component>
          <componentTitle>Charitable
          Contributions</componentTitle>
          <subComponent>
            <componentTitle>Diseases: AIDS, Hepatitis,
            Tuberculosis 
            <componentDate normalize="1990/1999">
            1990-1999</componentDate>
            </componentTitle>
          </subComponent>
          <subComponent>
            <componentTitle>Environmental Conservation: Rivers 
            <componentDate normalize="1995">1995</componentDate>
            </componentTitle>
          </subComponent>
        </component>
      </part>
    </content>
  </book>
</books>


