Technical writing for engineers

Technical writing for engineers

 · Technical writing: a practical guide for engineers and scientists by Phillip A. Laplante Call Number: TL27 The Naval Institute guide to naval writing by Robert ShenkAuthor: Manuel Jusino • Technical writers want to communicate as efficiently as possible, and active voice is more straightforward and is stronger than passive voice Ex 1: The feedthrough was composed of a sapphire optical fiber, which was pressed against the pyrotechnic that was used to confine the charge. Ex 2: The feedthrough contained a sapphireFile Size: KB Engineer's Guide to Technical Writing. × Close Log In. Log In with Facebook Log In with Google. Sign Up with Apple. or. Email: Password: Remember me on this computer. or reset password. Enter the email address you signed up with and we'll email you a reset link. Need an account? Click here Estimated Reading Time: 24 mins

Writing an Engineering technical report - Research & Learning Online

edu uses cookies to personalize content, tailor ads and improve the user experience. By using our site, you agree to our collection of information through the use of cookies. To learn more, view our Privacy Technical writing for engineers. edu no longer supports Internet Explorer. To browse Academia. edu and the wider internet faster and more securely, please take a few seconds to upgrade your browser.

Log In with Facebook Log In with Google Sign Up with Apple. Remember me on this computer. Enter the email address you signed up with and we'll email you a reset link. Need an account? Click here to sign up. Download Free PDF. Engineer's Guide to Technical Writing.

Josh H. Download PDF Download Full PDF Package This paper, technical writing for engineers. A short summary of this paper. Download PDF. Download Full PDF Package. Translate PDF. All Rights Reserved. Budinski Materials Park, OH www. Although this information technical writing for engineers believed to be accurate by ASM, ASM cannot guarantee that favorable results will be obtained from the use of this publication alone.

This publication is intended for use by per- sons having technical skill, at their sole discretion and risk. No claim of any kind, whether as to products or information in this publication, and whether or not based on negli- gence, shall be greater in amount than the purchase price of this product or publication in respect of which dam- ages are claimed. As technical writing for engineers any material, evaluation of the material under end-use conditions prior to specifica- tion is essential.

Therefore, specific testing under actual conditions is recommended. Nothing contained in this book shall be construed as a grant of any right of manufacture, sale, use, or reproduction, in connection with any method, process, apparatus, product, composition, or system, technical writing for engineers, whether or not covered by letters patent, copyright, or trademark, and nothing contained in this book shall be construed as a defense against technical writing for engineers alleged infringement of letters patent, technical writing for engineers, copyright, or trademark, or as a defense against liability for such in- fringement.

Comments, criticisms, and suggestions are invited, and should be forwarded to ASM International. ASM International staff who worked on this project included Steven Lampman, Acquisitions Editor, technical writing for engineers, Bonnie Sanders, Manager of Production, Nancy Hrivnak, Copy Editor, Kathy Dragolich, Production Editor, and Scott Henry, Assistant Director, technical writing for engineers, Reference Publications.

Library of Congress Cataloging-in-Publication Data Budinski, Kenneth G. Budinski p. Technical writing. Title T Tuttle of General Motors Institute. ix CHAPTER 1: Technical writing for engineers Is Technical Writing. It was not a company-training course.

Cowork- ers who attended my tutorial sessions went on to become effective techni- cal writers. In my opinion, our department is the model for the corporation. Everybody finishes his or her projects with a report. There is a format for each type of document and a system for archiving these documents. For- mal reports go to the corporate library, and they are available to all on-line. It is quite an effective system. That is the purpose of this book.

The overall objective of the book is frequent, effective, written documentation and the cost savings produced by effective communication. The first iteration of this book was directed toward college students in the sciences and engineering.

The eight or so reviewers, selected technical writing for engineers the publisher, were all English professors, and they thought that the text ma- terial was somewhat overwhelming for twenty-year-olds who never had full-time jobs.

Some were engineers with twenty years of experience. Young minds can handle anything. In my opinion, this book can help students as well as working technical people. The first four chapters are intended to bring the reader on board—to con- vince him or her that it is worth the effort to become a reasonably good technical writer.

There is also a chapter on how to conduct technical stud- ies. I have encountered many experienced technical people who did not know the basics of conducting a scientific investigation. There is a chap- technical writing for engineers on how to make effective illustrations and one on how to make oral presentations. The book ends with another philosophical chapter. This one is on how to discipline yourself to get writing tasks done in a timely manner. Grammar, punctuation, and report mechanics is relegated to the appendix.

Readers who need help can use them. The appendix also con- tains examples of just about every kind of technical document that one would encounter including a complete technical paper and a patent. In summary, this book contains the writing suggestions of a typical en- gineer with five years experience in the auto industry and thirty-six years in the chemical process industry. I have written over forty papers for archival journals, a teaching textbook, and a reference text, and I review papers for four technical journals.

I became heavily involved in writing as part of a career in research and development. This book reflects what is needed in industry, and I believe these needs are common in business and government as well. Effective communications is a prerequisite for a suc- cessful technical career, and this book presents a system that has proven to be successful in making effective communicators.

I thank all reviewers for their honest and helpful sug- gestions, in particular, Steve Helba and Nancy Kesterson for their work in getting knowledgeable reviewers and to J. for ideas. I acknowledge the talent of Judy Soprano for the chapter and cover art and the hard work of Angela Leisner at Home-Office Connection in converting my handwritten text and illustrations into an orderly electronic file. I could not have done this book without her.

Kenneth G. ASM International, Materials Park, Ohio, USA www. org This publication is copyright © ASM International®. All rights reserved. org American Technical Publishers Ltd. uk Neutrino Inc. In Japan Takahashi Bldg. This publication is being made available in PDF format as a benefit to members and customers of ASM International.

You may download and print a copy of this publication for your personal use only. Other use and distribution is prohibited without the express written permission of ASM International. No warranties, express or implied, including, without limitation, warranties of merchantability or fitness for a particular purpose, are given in connection with this publication.

This publication is intended for use by persons having technical skill, at their sole discretion and risk. Since the conditions of product or material use are outside of Technical writing for engineers control, ASM assumes no liability or obligation in connection with any use of this information.

As with any material, evaluation of the material under end-use conditions prior to specification is essential. Nothing contained in this publication shall be construed as a grant of any right of manufacture, sale, use, or reproduction, in connection with any method, process, apparatus, product, composition, or system, whether or not covered by letters patent, copyright, or trademark, and nothing contained in this publication shall be construed as a defense against any alleged infringement of letters patent, copyright, or trademark, or as a defense technical writing for engineers liability for such infringement.

Engineers' Guide to Technical Writing Copyright © ASM International® Kenneth G. Budinski, p All rights reserved. org CHAPTER 1 What Is Technical Writing? CHAPTER GOALS 1. Show where technical writing fits into the spectrum of interpersonal communications 2. Illustrate how technical writing differs from other forms of writing TECHNICAL WRITING is a broad term that encompasses a wide vari- ety of documents in science, engineering, technical writing for engineers, and the skilled trades.

The ma- jor types of documents in technical writing can be grouped into four major categories Fig. Writing reports is common for many techni- cal people because reports are a major part of the development and appli- cation of technology.

Very few companies pay technical professionals a salary without written words to implement and evaluate technical writing for engineers has been worked on or developed.

For example, if an engineer spends a year de- veloping a new transmission for a car, several types of reports are needed for the design, evaluation, and implementation of the new component. This usually requires a written document and related engineering drawings—a report.

A second category of technical writing includes documents for teaching and education Fig. Scripts for videos, movies, magazine articles, or multimedia presentations are most often written and edited by profession- als in these fields.

Books on technical topics are most often written by academicians, al- though technical professionals occasionally may write an entire book in their area of experience and knowledge.

Writing a book obviously requires much more discipline than the writing of reports, but it still requires the clarity of presentation and purpose as in the reports and papers of day-to- day business. The key difference is that books are intended for a larger audience and should have unique and compelling features for the readers. Papers and theses are more common forms of educational or informa- tional documents written by technical professionals.

Technical Writing for Scientists and Engineers

, time: 20:53

Technical Writing For Engineers (and others) | Vista Projects

 · Technical writing: a practical guide for engineers and scientists by Phillip A. Laplante Call Number: TL27 The Naval Institute guide to naval writing by Robert ShenkAuthor: Manuel Jusino Engineer's Guide to Technical Writing. × Close Log In. Log In with Facebook Log In with Google. Sign Up with Apple. or. Email: Password: Remember me on this computer. or reset password. Enter the email address you signed up with and we'll email you a reset link. Need an account? Click here Estimated Reading Time: 24 mins • Technical writers want to communicate as efficiently as possible, and active voice is more straightforward and is stronger than passive voice Ex 1: The feedthrough was composed of a sapphire optical fiber, which was pressed against the pyrotechnic that was used to confine the charge. Ex 2: The feedthrough contained a sapphireFile Size: KB