Entry Winograd:1999:DIC from jcd.bib

Last update: Tue Mar 5 02:04:11 MST 2019                Valid HTML 4.0!

Index sections

Top | Symbols | A | B | C | D | E | F | G | H | I | J | K | L | M | N | O | P | Q | R | S | T | U | V | W | X | Y | Z

BibTeX entry

@Article{Winograd:1999:DIC,
  author =       "Terry Winograd",
  title =        "Documentation, Interaction, and Conversation",
  journal =      j-ASTERISK,
  volume =       "23",
  number =       "4",
  pages =        "3--7",
  month =        nov,
  year =         "1999",
  CODEN =        "ASTRF7",
  ISSN =         "0731-1001",
  bibdate =      "Wed Dec 06 08:46:56 2000",
  bibsource =    "http://web.mit.edu/tps/www/NL/SIGDOC_WWW/jcdtoc/sigtoc.html;
                 http://www.math.utah.edu/pub/tex/bib/jcd.bib",
  abstract =     "From the perspective of an artificial intelligence
                 researcher now acquainted with digital libraries,
                 Winograd argues that documentation, however well
                 executed, is never an end in itself but always just a
                 means to user performance, ``a part of getting
                 something done that they care about.'' He compares
                 documentation use with other user ``conversations''
                 (with software and other people) to contend that
                 ``there is no boundary at which the interface stops and
                 the documentation begins'' (5). Hence an awareness of
                 ``how people actually work in living situations'' (7)
                 is crucial for good documentation design. Two open
                 commentaries immediately follow Winograd's paper. In
                 the first, Whitney Quesenbery (8-11) elaborates on the
                 holistic, integrative role of documentation (which
                 Winograd admits near the end of his paper). Writers are
                 often the only staff members who see a whole product
                 from the user's perspective, and their insight into
                 user mental models should have influence earlier in the
                 design process. In the second commentary, Dennis Wixon
                 (12-14) examines Winograd's examples again and finds
                 that in designing both documentation and product
                 interfaces the best goal is to match user needs in
                 diversity as well as in grain size.",
  acknowledgement = ack-nhfb,
}

Related entries