TITLE

Documentation: Literacy, artistry and finger painting

AUTHOR(S)
Gibbs, Mark
PUB. DATE
August 1997
SOURCE
Network World;08/04/97, Vol. 14 Issue 31, p70
SOURCE TYPE
Trade Publication
DOC. TYPE
Article
ABSTRACT
Presents predictions concerning software documentation. Drawback of blending documentation with source code; Comments on WebSite Profession from O'Reilly and Associates; Emergence of online documentation and gradual disappearance of paper documentation.
ACCESSION #
9708106027

 

Related Articles

  • Keep HRIS documentation.  // Personnel Journal;Nov94, Vol. 73 Issue 11, New Product News... p13 

    Presents an excerpt from an article featured in the October 1987 issue of `Personnel Journal' entitled `HRIS Training: Keep Documentation on Track,' by Maureen MacAdam. Cases where documentation is training; Contents of a computer systems documentation; Features; Target user audiences.

  • Shred your manuals! Holtzman, Jeff // Popular Electronics;Jan94, Vol. 11 Issue 1, p70 

    Comments on the fact that software companies find it difficult to document their products in a satisfactory manner. Complexity of computer software; Proposed hypothetical field of endeavor called a documentation engineer; Need for a documentation engineer to be have a two-year Master of Science...

  • Say good-bye to the paper documentation. Coffee, Peter // PC Week;3/7/94, Vol. 11 Issue 9, p41 

    Opinion. Commends the use of CD ROMs for documentation by Symantec, Microsoft and Borland. Instances when paper documentation lies; Advantages of using CD ROM for documentation.

  • Documentation: The next frontier for vendors. Van Name, Mark L.; Catchings, Bill // PC Week;7/18/94, Vol. 11 Issue 28, pN/10 

    Discusses various aspects of software documentation. Excel; Absence of DOS and Windows manuals; On-line help; Suggestions for vendors.

  • INCLUDING PURPOSE IN SOFTWARE DOCUMENTATION. Block, Barbara // Intercom;Apr2001, Vol. 48 Issue 4, p24 

    Focuses on the need for technical writers to include purpose and overview information in software documentation. Guidelines in document construction; Benefits of software documentation; Importance of saving a document.

  • When does more documentation mean less work?  // IEEE Software;Oct84, Vol. 1 Issue 4, p98 

    Focuses on the development of software documentation in software engineering. Attempts to reduce software development costs; Guidelines for the determination of a good documentation; Establishment of documentation standards.

  • Readers create manifesto for paid support. Coffee, Peter // PC Week;10/11/93, Vol. 10 Issue 40, p34 

    Presents one of several reactions from readers familiar with deficient software design and documentation on a previous column dealing with the demise of `free' software support. Availability of bug lists; Cost of full disclosure.

  • Omission is no sin, as long as you admit it. Surkan, Michael // PC Week;08/10/98, Vol. 15 Issue 32, p75 

    Comments on problems which occur in computer software. How easy it is to miss a problem in the complicated computer software of the late 1990s; Software in which necessary features have been omitted, without any documentation to that effect; The history of software developers and their...

  • Documentation: How much is enough? Tice, George // IEEE Software;May88, Vol. 5 Issue 3, p95 

    Focuses on the software documentation for software-engineering standards in the United States. Comparison of three major public software engineering standards; Recommendation range of standard organization from minimum of six required documents; Expansion of documentation set needed for...

Share

Read the Article

Courtesy of VIRGINIA BEACH PUBLIC LIBRARY AND SYSTEM

Sorry, but this item is not currently available from your library.

Try another library?
Sign out of this library

Other Topics