Engineers and scientists of all types are often required to write reports, summaries, manuals, guides, and so forth. While these individuals certainly have had some sort of English or writing course, it is less likely that they have had any instruction in the special requirements of technical writing.
Filling this void, Technical Writing: A Practical Guide for Engineers and Scientists enables readers to write, edit, and publish materials of a technical nature, including books, articles, reports, and electronic media. Written by a renowned engineer and widely published technical author, this guide complements the traditional writer’s reference manuals and other books on technical writing. It helps readers understand the practical considerations in writing technical content.
Drawing on his own work, the author presents many first-hand examples of writing, editing, and publishing technical materials. These examples illustrate how a publication originated as well as various challenges and solutions.
The Nature of Technical Writing
Who Writes Technical Documentation?
Taxonomy of Technical Writing
Technical Writing Basics
Structuring Your Writing
Positioning Your Writing
Choosing the Right Words
Making Your Technical Writing More Interesting
The 5 Cs of Technical Writing
The Writing Process
The Traditional Writing Process
Dealing with Writer’s Block
Permissions and Plagiarism
Reviews of Books, Papers, and Reports
Writing Letters of Reference
Meetings, Agendas, and Minutes
Customer Relations Writing
Strategic Plans and Planning
Using Graphical Elements
Breaking up the Monotony
Modeling Ideas with Graphics
Selecting the Best Model for a Schedule
Dealing with Figures
Dealing with Tables
Dealing with Equations
Dealing with Dynamic Content
Publishing Your Work
Making a Living as a Writer
The Review Process
Open Access Publishing
Writing for E-Media
E-Mail Can Be Dangerous
Writing with Collaborators
Writing in Different Voices
Very Large Collaborative Writing Projects
Behavior of Groups
Other Paradigms for Team Building
Antipatterns in Organizations
Exercises and References appear at the end of each chapter.
Phillip A. Laplante is a professor of software engineering at Pennsylvania State University’s Great Valley School of Graduate Professional Studies. Dr. Laplante is an IEEE and SPIE fellow and a licensed professional engineer in Pennsylvania. His applied research encompasses software project management, software testing, and requirements engineering.
"Concisely written, fastpaced, comprehensive, and written with workplace expectations in mind, Laplante hits the mark when he says his book is intended to complement reference books or other technical communication books. … The language is easy for students to understand; the design, graphics, and examples keep readers engaged; and it can be a great supplement or primary text depending on how much original material of your own you would like to provide to your students."
—Diane Martinez, Technical Communication, May 2012