ACM Home Page
Please provide us with feedback. Feedback
A future for professional communicators in software engineering
Full text PdfPdf (1.37 MB)
Source ACM Special Interest Group for Design of Communication archive
Proceedings of the 12th annual international conference on Systems documentation: technical communications at the great divide table of contents
Banff, Alberta, Canada
Pages: 76 - 87  
Year of Publication: 1994
ISBN:0-89791-681-6
Author
John K. Horberg  Rensselaer Polytechnic Institute
Sponsor
SIGDOC: ACM Special Interest Group for Design of Communications
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 0,   Downloads (12 Months): 9,   Citation Count: 0
Additional Information:

references   index terms  

Tools and Actions: Request Permissions Request Permissions    Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/192506.192547
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
 
2
Balzer, T. Cheatham, and Green. (1983). "Software technology in the 1990% using a new paradigm,'' Computer. vol. 16, 39-45.
 
3
 
4
 
5
 
6
Bresko, L. (1991). "The need for technical communicators on the software development team," Technical Communication. vol. 38, 214-220.
 
7
 
8
 
9
10
 
11
Doheny-Farina, S. (1992). Rhetoric, renovation, technology: case studies of technical communication in technology transfers. Cambridge: The MIT Press.
 
12
 
13
Farkas, D.K. (1991). Collaborative Writing, Software Development, and the Universe of Collaborative Activity. In M.L. Lay & W.M. Karlis (Eds.), Collaborative writing in industry: investigations in theory and practice (pp. 13-30). Amity~He, New York: Baywood Publishing.
 
14
Geisler, C. (1991). "Writing about the material world: communication tasks in engineering design," IPCC91 Proceedings: The Engineered Communication, vol. 1, 128-133.
 
15
16
 
17
Graham, Clancy and DeVaney. (1982). A Software Design and Evaluation System. In Edward Yourdon (Ed.) Writings of the revolution: selected readings on software engineering, (pp. 112-122). Yourdon Press.
 
18
 
19
 
20
Horberg, J.K. (1993). Engineer/customercommunication practices: a study of software engineering. Masters Thesis. University of Minnesota.
 
21
 
22
Kostur, P. and Hall. (1991). Avoiding Miscommunication: How to Analyze and Edit for Meaning. IPCC91 proceedings: the engineered communication, vol. 1, 18-25.
 
23
Krauss, R. and Fussell. (1991). Mutual knowledge and communicative effectiveness. In M. Lay and W. Karlis, (Eds.) Collaborative writing in industry: investigations in theory and practice, (pp. 111-145). New York: Baywood Publishing.
 
24
 
25
Mcewen-Beeman. (1991). Communication Engineered as Process. IPCC91 Proceedings: The Engineered Communication. vol. 1, (pp. 57- 59).
 
26
Norman, D.A. (1988). The psychology of everyday things. New York: Basic Books, Inc.
 
27
Olson, G.M. and Olson. (1991). User-Centered Design of Collaboration Technology. Journal of Organizational Computing, vol. 1 (1), 61-83.
 
28
 
29
 
30
Ramey, J. (1991). Communication: Usability Engineering. IPCC91 Proceedings: The Engineered Communication, vol. 1, (pp. 60-64).
 
31
Redish, J. and Ramey. (1993). Measuring the value added by professional technical communicators. IEEE Transactions on Professional Communication, vol. 36, pp. 158-161.
 
32
 
33
 
34