If writers can't program and programmers can't write, who's writing user documentation?

Subscribe (Full Service)


	Search: The ACM Digital Library The Guide

	Feedback

If writers can't program and programmers can't write, who's writing user documentation?

Full text

Pdf (626 KB)

Source

ACM Special Interest Group for Design of Communication archive
Proceedings of the 4th annual international conference on Systems documentation table of contents

Ithaca, New York, United States

Pages: 62 - 70

Year of Publication: 1986

ISBN:0-89791-186-5

Author

Gregory R McArthur

National Center for Atmospheric Research, Boulder, Colorado

Sponsor

SIGDOC: ACM Special Interest Group for Design of Communications

Publisher

ACM New York, NY, USA

Bibliometrics

Downloads (6 Weeks): 1, Downloads (12 Months): 10, Citation Count: 0

Additional Information:

references index terms collaborative colleagues peer to peer

Tools and Actions:	Request Permissions Review this Article Save this Article to a Binder Display Formats: BibTeX EndNote ACM Ref

DOI Bookmark:	Use this link to bookmark this Article: http://doi.acm.org/10.1145/10563.10574 What is a DOI?

REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

	1	Anon., 1984. How Does This ~$%@ Thing Work? TIME Magazine Vol. 123, No. 18. pg. 64
	2	Knauer, Gene., 1984. The Rise of the Technical Writer Ccmpute~rld January 9, 1984
	3	G. M. Weinberg, The psychology of computer programming, Van Nostrand Reinhold Co., New York, NY, 1988
	4	McClelland, L., 1984. 1984 National Test Scores Office of Research and Testing University of Colorado Boulder, Colorado Statistics C~iled frcm Educational Testing Service Princeton, New Jersey
	5	Stephens, J.G., 1984. "10 Tips for Improving Your Documentation" In: PC Tech Journal Vol. 1, No. 5 February 1984 pg. 83
	6	Brian W. Kernighan , P. J. Plauger, The Elements of Programming Style, McGraw-Hill, Inc., New York, NY, 1982
	7	Brooks, R.E., 1980. Studying Progr~r Behavior Experimentally: Th__ee Problems of Pro~ Methodoloqy. In: Human Factors in Software Development IEEE ~SACS1 1981 pp. 591-597
	8	Parikh, Girish., 1981. How to Measure Pr~rammer Productivity Shetal Enterprises Chicago, Ill 95 pp.
	9	Bly, Robert. W. and Gary Blake., 1982. Technical Writing: Stucture, Standards, and S~ McGraw Hill New York, New York 114 pp.
	10	Tracz, William J., 1981. ~uter Proqramming and the Human Thou hnq~ Process In: Human Factors in Software Development IEEE ~SACM 1 1981 pg. 25

INDEX TERMS

Classification:
D. Software
D.2 SOFTWARE ENGINEERING
D.2.7 Distribution, Maintenance, and Enhancement
Subjects: Documentation

General Terms:
Documentation

Collaborative Colleagues:

Gregory R McArthur: colleagues

Peer to Peer - Readers of this Article have also read:

Constructing reality Proceedings of the 11th annual international conference on Systems documentation
Douglas A. Powell , Norman R. Ball , Mansel W. Griffiths
Data structures for quadtree approximation and compression Communications of the ACM 28, 9
Hanan Samet
A hierarchical single-key-lock access control using the Chinese remainder theorem Proceedings of the 1992 ACM/SIGAPP Symposium on Applied computing
Kim S. Lee , Huizhu Lu , D. D. Fisher
An intelligent component database for behavioral synthesis Proceedings of the 27th ACM/IEEE Design Automation Conference on
Gwo-Dong Chen , Daniel D. Gajski
The GemStone object database management system Communications of the ACM 34, 10
Paul Butterworth , Allen Otis , Jacob Stein

Adobe Acrobat

QuickTime

Windows Media Player

Real Player