Entry Wright:1998:DIS 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{Wright:1998:DIS,
  author =       "Patricia Wright",
  title =        "Designing Information-Supported Performance: The Scope
                 for Graphics",
  journal =      j-ASTERISK,
  volume =       "22",
  number =       "4",
  pages =        "3--10",
  month =        nov,
  year =         "1998",
  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 =     "Using three psychological studies of the role of
                 graphics in three different documentation projects to
                 illustrate her points, Wright argues against the
                 popular cliche of seeking a standard ``best practice''
                 to solve documentation problems. She suggests as more
                 beneficial the thoughtful balancing of design tradeoffs
                 by carefully exploiting the boundary conditions
                 specific to each project, using a ``map'' of past
                 research for guidance. Immediately following Wright's
                 paper, four commentators explore its implications.
                 Russell Borland (11-15) looks closely at just how
                 research ``maps'' of various structures and
                 granularities might actually support managing design
                 tradeoffs. Thomas Williams and Judith Ramey (16-20)
                 consider the difficulty of thoroughly representing the
                 documentation ``knowledge matrix'' in a way that both
                 researchers and practitioners will find helpful. And
                 Thyra Rauch (21-25) argues that long-term social
                 studies of users and their task domains may be
                 sufficient to guide documentation tradeoffs in
                 practice.",
  acknowledgement = ack-nhfb,
}

Related entries