Access the full text.
Sign up today, get DeepDyve free for 14 days.
References for this paper are not available at this time. We will be adding them shortly, thank you for your patience.
Must a technical report be a pyrotechnic display of intricate facts, figures, and tables? Far too many engineering personnel submit logically complete, technically correct reports--which efficiently put the reader to sleep. Analysis of the technical report shows that its functional parts are designed for different classes of readership, each having different needs and technical skill levels. Writing your material while focussing on its intended audience instead of a piece of equipment, will vastly increase reader comprehension and minimize the stereotyped image of the dull report. Also, the resultant time saved for the reader represents a cost saving which justifies the slight extra attention given by the writer.
ABCA Bulletin – SAGE
Published: Dec 1, 1972
Read and print from thousands of top scholarly journals.
Already have an account? Log in
Bookmark this article. You can see your Bookmarks on your DeepDyve Library.
To save an article, log in first, or sign up for a DeepDyve account if you don’t already have one.
Copy and paste the desired citation format or use the link below to download a file formatted for EndNote
Access the full text.
Sign up today, get DeepDyve free for 14 days.
All DeepDyve websites use cookies to improve your online experience. They were placed on your computer when you launched this website. You can change your cookie settings through your browser.