mod6 - Module Six: Technical Writing the Report PLEASE...

Info iconThis preview shows pages 1–2. Sign up to view the full content.

View Full Document Right Arrow Icon
Module 6 - 21 Module Six: Technical Writing – the Report PLEASE NOTE: BECAUSE OF ITS COMPLEXITY AND LENGTH THIS MODULE HAS A VALUE OF 40% Module 6 Due Date: 4 November 2010 Value: 40% Objectives: 1. Learn to write effective feasibility, progress, and activity reports. 2. Understand the importance of writing for the audience when creating a formal report. Readings: READER: Charles T. Brusaw, Gerald J. Alred, and Walter E. Oliu. Handbook of Technical Writing (5 th edition) New York: St. Martin’s Press, 1997, pp. 8-11; 208-213; 453-456; 599-601. READER: Ron S. Blicq, Guidelines for Report Writing Scarborough: Prentice-Hall Canada Inc., 1982, pp. 39-54; 112-151. Stewart and Allen Forms of Writing Toronto: Prentice Hall, 2009, pp. 324-328. Commentary: As in business writing, a good piece of technical writing communicates information concisely, yet thoroughly. Technical reports should not be written to demonstrate your mastery of literary allusion. Avoid all flowery language. Besides clarity and conciseness, desirable qualities in a technical report include an easy- to-read format. By this I do not mean monosyllabic words. Instead, your report should include
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Image of page 2
This is the end of the preview. Sign up to access the rest of the document.

Page1 / 2

mod6 - Module Six: Technical Writing the Report PLEASE...

This preview shows document pages 1 - 2. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online