Ganesh: Courseware for Technical Report Writing in Delft
DOI:
https://doi.org/10.1558/cj.v11i2.65-85Keywords:
technical report writing, courseware, GaneshAbstract
Technical engineers consider communication and writing skills to be among the most difficult aspects of their profession. Communication courses, however, are expensive, because teaching takes place in tutorials in which students are given feedback regularly. Therefore a computer assisted practicum has been designed. The practicum aims to diminish the amount of lecturer effort while increasing student participation through the interactive and user-friendly courseware Ganesh. The program (in Dutch) consists of two modules: 1) a report module, which offers examples of and criteria for the standard components of technical reports; 2) a style module, which discusses subjects such as sentence complexity, use of examples, use of connectives, spelling, etc. In both modules the student can opt for additional examples or exercises via buttons, menus and hypertext paths. In this paper we would like to discuss some of the characteristics of the program and the results of a test we performed last spring.References
Anderson, P. V. (1 991). Technical Writing, A Reader-centered Approach. 2nd Ed. HarcourtBrace Jovanovic, New York.
Andeweg, B. A., E. R. Hoekstra, J. C. de Jong and S. Kunst (1991). "Computer AssistedTeaching of Technical Writing in Delft." Proceedings of the Fourth Annual Conferenceon Computers and the Writing Process, 76-85. University of Sussex, Brighton.
Andeweg, B. A., E. R. Hoekstra, J. C. de Jong and S. Kunst (1992). "HypertextAdventures, Computer Assisted Teaching of Technical Report Writing in Delft."Computers and Writing: Issues and Implementations, M. Sharples (Ed.), Kluwer.
Elling, M. G. M., B. A. Andeweg, J. C. de Jong, P. C. Post, C. E. Swankhuisen (1992). DeTechniek van Het Schriftelijk Rapporteren. 6e Geheel Herziene Druk. InternePublikatie Vakgroep Communicatie en Kennisoverdacht, TU Delft. ["TheTechnique of Technical Writing"]
Effective Writing (1986). Quay Software Limited, Lymington.
Glushko, R. J. (1992). "Seven Ways to Make a Hypertext Project Fail." TechnicalCommunication 2, 226-230.
Hoekstra, E. (1990). "Driemaal Courseware Over Schrijven: Hoe u uw Schrijftalenten viaComputergestuurde Lessen Kunt Ontwikkelen." InterCommunicatief 3, 5, 8-11.["Three Courseware Programs on Writing: Developing your Talents by ComputerAssisted Training"]
Hoogland, W. (1992). Rapport Over Rapporteren; Rapporteren in Theorie en Praktijk.Groningen: Wolters Noordhoff. Met Diskette. ["Report on reporting" with diskette]
Heusinkveld, H. W. (1988). "De Computer en (Bedrijfs) Correspondentie in de ModerneTalen." Levende Talen 436, 670-675.
Huckin, T. N. and L. A. Olsen (1991). Technical Writing and Professional Communication.2nd Ed. New York, McGraw-Hill Inc.
Mathes, J. C. and D. W. Stevenson (1976). Designing Technical Reports. Indianapolis.
Nickels, Shirk, H. (1 992). “Online Documentatie, Vraagstukken Rond het Creëren vanOnline Documentatie." Communicatief 4 [Also published as "Guidelines forSelecting Hypertext as a Medium for Technical Communication." Proceedings of the38th International Technical Communication Conference. New York April 14-17, 1991.
Vonderen-van Staveren, M. L. van and D. W. Vaags (1985). "Ingenieurs Hikken aanTegen Niet-technische Taken." De Ingenieur 11. ["Engineers Boggle at Non-technical Tasks']
Watt, Susan(1987). Writing for Business: a Computer-based Program, Version 1. ' SheridanCollege, Canada.
Wresch, William (1 989). Writer's Helper Stage II. Published by CONDUIT, Iowa City,Iowa.
