Single-source manuals

G. Bist IBM (Canada)

Abstract

Because corporations today face fierce international competition, they must produce and maintain high-quality documentation-but at minimal cost. Optimizing a writer's time and effort will no doubt become a key study area as we try to do more with less, without sacrificing quality. One way to increase a technical writer's productivity is to design documentation so that it covers a broader product area. This approach gets more use (or reuse) of the text. The paper describes the productivity and cost benefits of creating single-source manuals, that is, two or more manuals output from the same set of source files created and updated by one writer. It also describes how to create single-source manuals based on an actual case.< <ETX xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink">></ETX>

Journal
IEEE Transactions on Professional Communication
Published
1994-06-01
DOI
10.1109/47.291573
CompPile
Open Access
Closed
Export

Citation Context

Cited by in this index (2)

  1. IEEE Transactions on Professional Communication
  2. IEEE Transactions on Professional Communication

References (8)

  1. Preparedness training
    CIO
  2. In search of elegance
    Comput Lang
  3. SGML by evolution
    Tech Commun
  4. Configurable user documentation?or how I came to write a language with a future conditional
    Proceedings of the USENIX/SAGE Large Installation System Administration conference
  5. The new society of organizations
    Harvard Business Review
Show all 8 →
  1. Customer intimacy and other value disciplines
    Harvard Business Review
  2. The Goal The Process of Ongoing Improvement
  3. America and the New Economy