Technical writing

From HandWiki
Revision as of 19:05, 6 February 2024 by John Stpola (talk | contribs) (linkage)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Short description: Type of written communication

Technical writing is the writing of technical content, particularly relating to industrial and other applied sciences, with an emphasis on occupational contexts.[1] The range of audiences for technical writing varies widely. In some cases, it is directed to people with specialized knowledge, such as experts or technicians.[2] In other situations, technical writers help convey complex scientific or niche subjects to end users who need a basic understanding of a concept rather than a full explanation of a subject.[3] Technical writing is the largest part of technical communication.[4]

Examples of fields requiring technical writing include computer hardware and software, architecture, engineering, chemistry, aeronautics, robotics, finance, medical, consumer electronics, biotechnology, and forestry.

Overview

Further information: Technical writer

Technical writing is performed by a technical writer (or technical author) and is the process of writing and sharing technical information in a professional setting.[5]:{{{1}}} A technical writer's primary task is to communicate technical information to another person or party in the clearest and most effective manner possible.[5]:{{{1}}} The information that technical writers communicate is often complex, so strong writing and communication skills are essential. Technical writers not only convey information through text, but they must be proficient with computers as well. Technical writers use a wide range of programs to create and edit illustrations, diagramming programs to create visual aids, and document processors to design, create, and format documents.[6]

While technical writing is commonly associated with instructions and user manuals, the terms technical writing and technical documentation can cover a wider range of genres and formats. memos, reports, business proposals, datasheets, product descriptions and specifications, and white papers are but a few examples of writing that can be considered technical documentation.[7] And for highly technical jobs (e.g., engineering and other applied sciences), aspects of résumés and job applications can also be considered technical writing.

Technical writing is not always handled by dedicated technical writers. For example, engineers often need to write directly about their own work. On the business side, marketing materials or press releases are usually written by people in those fields, although a technical writer or other technical person may need to have input on any technical subject matter involved.

History

While technical writing has only been recognized as a profession since World War II,[8]:{{{1}}}[9] its roots can be traced to classical antiquity.[10]:{{{1}}} Critics cite the works of writers like Aristotle as the earliest forms of technical writing.[10]:{{{1}}} Geoffrey Chaucer's work, A Treatise on the Astrolabe, is an early example of a technical document.[11] The earliest examples of technical writing date back to the Old English period.[12]

With the invention of the mechanical printing press, the onset of the Renaissance and the rise of the Age of Reason, documenting findings became a necessity. Inventors and scientists like Isaac Newton and Leonardo da Vinci prepared documents that chronicled their inventions and findings.[8]:{{{1}}} While never called technical documents during their period of publication, these documents played a crucial role in developing modern forms of technical communication and writing.[8]

The field of technical communication grew during the Industrial Revolution.[13]:{{{1}}} There was a growing need to provide people with instructions for using the increasingly complex machines that were being invented.[13]:{{{1}}} However, unlike the past, where skills were handed down through oral traditions, no one besides the inventors knew how to use these new devices. Writing thus became the fastest and most effective way to disseminate information, and writers who could document these devices were desired.[13]

During the 20th century, the need for technical writing skyrocketed, and the profession became officially recognized. The events of World War I and World War II led to advances in medicine, military hardware, computer technology, and aerospace technologies.[8]:{{{1}}} This rapid growth, coupled with the urgency of war, created an immediate need for well-designed documentation to support the use of these technologies. Technical writing was in high demand during this time, and "technical writer" became an official job title during World War II.[8]:{{{1}}}

Following World War II, technological advances led to an increase in consumer goods and standards of living.[8]:{{{1}}} During the post-war boom, public services like libraries and universities, as well as transport systems like buses and highways, saw substantial growth. The need for writers to chronicle these processes increased.[8]:{{{1}}} It was also during this period that large business and universities started using computers. Notably, in 1949, Joseph D. Chapline authored the first computational technical document, an instruction manual for the BINAC computer.[14]

The invention of the transistor in 1947 allowed computers to be produced more cheaply and within the purchasing range of individuals and small businesses.[8]:{{{1}}} As the market for these "personal computers" grew, so did the need for writers who could explain and provide user documentation for these devices.[8]:{{{1}}} The profession of technical writing saw further expansion during the 1970s and 1980s as consumer electronics found their way into the homes of more and more people.[8]

In recent years, the prominence of computers in society has led to many advances in the field of digital communications, leading to changes in the tools technical writers use.[8]:{{{1}}} Hypertext, word processors, graphics editing programs, and page laying software have made the creation of technical documents faster and easier, and technical writers of today must be proficient in these programs.[5]:{{{1}}}

Technical documents

Technical writing covers many genres and writing styles, depending on the information and audience.[5]:{{{1}}} Technical documents are not solely produced by technical writers. Almost anyone who works in a professional setting produces technical documents of some variety. Some examples of technical documentation include:

  • API guides are written for the developer community and are used to explain the application programming interfaces.
  • Case study is a published report about a person, group, or situation that has been studied over time; also : a situation in real life that can be looked at or studied to learn about something.[15] For example, an individual's challenging situation at his or her workplace and how he or she resolved it is a case study.
  • Datasheets are the documents that summarize the features, key specifications, technical characteristics, application circuits, and some other important information about the product, machine, equipment, software, application, or system in brief.
  • Descriptions are shorter explanations of procedures and processes that help readers understand how something works.[5]:{{{1}}} For example, a technical writer might author a document that shows the effects of greenhouse gases or demonstrates how the braking system on a bike functions.
  • Emails, letters, and memoranda are some of the most frequently written documents in a business.[16]:{{{1}}} Letters and emails can be constructed with a variety of goals—some are usually aimed at simply communicating information while others are designed to persuade the recipient to accomplish a certain task. While letters are usually written to people outside of a company, memoranda (memos) are documents written to other employees within the business.[16]:{{{1}}}
  • Help systems are online help centers that provide users with technical information about products and services. They provide content as web pages that are viewed in a browser. The content may be created in help center software, such as Zendesk, or in help authoring tools or component content management systems that can create a help center as an HTML output.
  • Instructions and procedures are documents that help either developers or end-users operate or configure a device or program.[16]:{{{1}}} Examples of instructional documents include user manuals and troubleshooting guides for computer programs, computer hardware, household products, medical equipment, mechanical products, and automobiles.
  • Press releases. When a company wants to publicly reveal a new product or service, they will have a writer author a press release. This is a document that describes the product's functions and value to the public.[17]
  • Proposals. Most projects begin with a proposal—a document that describes the purpose, tasks required by, methods to be used, and cost of the project.[16]:{{{1}}} Proposals cover a wide range of subjects. For example, a technical writer may author a proposal that outlines how much it will cost to install a new computer system, a marketing professional may write a proposal with the product offerings, and a teacher may write a proposal that outlines how a new biology class will be structured.
  • Résumés and job applications are another example of technical documents.[16]:{{{1}}} They are documents that are used in a professional setting to inform readers of the author's credentials.
  • Specifications are design outlines that describe the structure, parts, packaging, and delivery of an object or process in enough detail that another party can reconstruct it.[18] For example, a technical writer might diagram and write the specifications for a smartphone or bicycle so that a manufacturer can produce the object.
  • Technical reports are written to provide readers with information, instructions, and analysis for tasks.[16]:{{{1}}} Reports come in many forms. For example, a technical writer might evaluate a building that is for sale and produce a trip report that highlights his or her findings and whether he or she believes the building should be purchased. Another writer who works for a non-profit company may publish an evaluation report that shows the findings of the company's research into air pollution.
  • Websites. The advent of hypertext has changed the way documents are read, organized, and accessed. Technical writers of today are often responsible for authoring pages on websites like "About Us" pages or product pages. They are often expected to be proficient in web development tools.[19]:{{{1}}}
  • White papers are documents that are written for experts in a field and typically describe a solution to a technological or business challenge or problem.[16]:{{{1}}} Examples of white papers include a piece that details how to make a business stand out in the market or a piece explaining how to prevent cyber-attacks on businesses.

Tools

The following tools are used by technical writers to author and present documents:

  • Desktop publishing tools or word processors. Technical writers use word processors such as Scrivener, Microsoft Word, Apple Pages, and LibreOffice Writer to author, edit, design, and print documents. Since technical writing is as much about page layout as it is the written language, enhanced desktop publishing tools such as Adobe InDesign and LyX are also used.[20] These programs function similarly to word processors but provide users with more options and features for the document's design and automate much of the formatting.[21]
  • Help authoring tools. These are used by technical writers to create the help systems that are packaged with software products, delivered through web browsers or provided as files users can view on their computers. When writing instructional procedures to describe mechanical, electrical, or software programs, technical writers use these tools to assist them in simplifying assembly, operation, or installation processes.
  • Component content management systems. These are also used by technical writers to create help systems and documents. Component Content Management Systems (CCMS) allow writers to create similar outputs as help authoring tools, but they also provide content management features such as version management and built-in workflows.
  • Image editing software. Often, images and other visual elements can communicate information better than paragraphs of text.[5]:{{{1}}} In these instances, image editing software like Adobe Photoshop and GIMP are used by technical writers to create and edit the visual aspects of documents like photos, icons and diagrams.
  • Collaborative software programs. Because technical writing often involves communication between multiple individuals who work for different companies, it can be a collaborative affair.[5]:{{{1}}} Technical writers use Wiki Systems and shared document work-spaces to work with other writers and parties to construct technical documents.[5]:{{{1}}}
  • Web development tools. Technical writer jobs are no longer limited to just producing documents. They sometimes also produce content for a company's corporate and other professional web sites.[19]:{{{1}}} Technical writers might therefore be expected to be proficient in Web development tools like Adobe Dreamweaver.
  • Text editors. Programs such as Microsoft Notepad, TextEdit, or Wordstar allow technical writers to edit plain text. Text editors can be used to change content such as configuration files, documentation files, and programming language source code. Text editors are widely used by technical writers working with online content.
  • Graphing software. To communicate statistical information such as the number of visits to a restaurant or the amount of money a university spends on its sporting programs, technical writers use graphs and flowcharts.[5]:{{{1}}} While programs like Microsoft Excel and Word can create basic graphs and charts, sometimes technical writers must produce more complex and detailed graphs that require functions not available in these programs and may need to turn to graphing and diagramming tools (e.g., Microsoft Visio).[22]
  • Screen capture tools. Technical writers frequently use screen-capture tools like Camtasia and Snagit.[23][24] When creating instructions for computer software, it may be easier for a technical writer to simply record a short video of their desktops as they complete a task than it would be to write a lengthy series of instructions that describe how the task must be performed. Screen capture tools are also used to take screenshots of programs and software running on user's computers and then to create accompanying diagrams.

List of associations

References

  1. ↑ "What is Technical Writing? - Tech Writer Today". https://techwhirl.com/what-is-technical-writing. 
  2. ↑ Hamlin, Annemarie; Rubio, Chris; Desilva, Michele (2015). "Audience Analysis". https://pressbooks.pub/coccoer/chapter/audience-analysis/. 
  3. ↑ Marshall, Carrie (2018). Technical Writing For Business People (1st ed.). Swindon UK. pp. 1. 
  4. ↑ "Technical Communications - What is it? - Tech Writer Today". http://techwhirl.com/what-is-technical-communications. 
  5. ↑ 5.0 5.1 5.2 5.3 5.4 5.5 5.6 5.7 5.8 Mike Markel (2012). Technical Communication 10th Edition. Bedford/St. Martins. 
  6. ↑ Johnson, Tom (December 19, 2011). "What Tools Do Technical Writers Use". I'd Rather Be Writing. http://idratherbewriting.com/2011/12/19/what-tools-do-technical-writers-use/. 
  7. ↑ "Document Types". The Mayfield Handbook of Technical & Scientific Writing. http://web.mit.edu/course/21/21.guide/docutyp.htm. 
  8. ↑ 8.00 8.01 8.02 8.03 8.04 8.05 8.06 8.07 8.08 8.09 8.10 O'Hara, Fredrick M. Jr.. "A Brief History of Technical Communication". Montana State University Billings. http://www.msubillings.edu/cotfaculty/fullon/_notes/History%20of%20Technical%20Communication%20%282%29.pdf. 
  9. ↑ Alamargot, Denis; Terrier, Patrice; Cellier, Jean-Marie, eds (2007-10-01). Written Documents in the Workplace. doi:10.1163/9789004253254. ISBN 9780080474878. http://dx.doi.org/10.1163/9789004253254. 
  10. ↑ 10.0 10.1 Doody, Aude; Follinger, Sabine; Taub, Liba (February 8, 2012). "Structures and Strategies in Ancient Greek and Roman Technical Writing: An Introduction". Studies in History and Philosophy of Science (University Of Cambridge) 43 (2): 233–236. doi:10.1016/j.shpsa.2011.12.021. Bibcode: 2012SHPSA..43..233D. http://www.hps.cam.ac.uk/people/taub/structures_and_strategies.pdf. Retrieved April 22, 2014. 
  11. ↑ "The Way to the Stars: Build Your Own Astrolabe". Saint John's College. http://www.joh.cam.ac.uk/library/library_exhibitions/schoolresources/astrolabe/chaucer. 
  12. ↑ Hagge, John (July 1990). "The First Technical Writer in English: A Challenge to the Hegemony of Chaucer". Journal of Technical Writing and Communication 20 (3): 269–289. doi:10.2190/vwcw-xkmv-949f-vlf7. ISSN 0047-2816. http://dx.doi.org/10.2190/vwcw-xkmv-949f-vlf7. 
  13. ↑ 13.0 13.1 13.2 Crabbe, Stephen (2012). "Constructing a Contextual History of English Language Technical Writing". University of Portsmouth. http://eprints.port.ac.uk/9695/1/trans-kom_05_01_03_Crabbe_Technical_Writing.20120614.pdf. 
  14. ↑ "History of Technical Writing". Proedit. 14 September 2012. http://www.proedit.com/history-of-technical-writing/. 
  15. ↑ "Dictionary and Thesaurus". https://www.merriam-webster.com/dictionary/case%20study. 
  16. ↑ 16.0 16.1 16.2 16.3 16.4 16.5 16.6 Tebeaux, Elizabeth; Dragga, Sam (2010). The Essentials of Technical Communication. Oxford University Press. 
  17. ↑ Perelman, Leslie C., Barrett, Edward, and Paradis James. "Press jaylan peregrino". The Mayfield grave naba Handbook of Technical & Scientific Writing. Retrieved May 4, 2014.
  18. ↑ Perelman, Leslie C., Barrett, Edward, and Paradis James. "Specifications." The Mayfield Handbook of Technical & Scientific Writing. Retrieved May 4, 2014.
  19. ↑ 19.0 19.1 Anderson, Paul V. (2007). Technical Communication [A Reader-Centered Approach] 6th Edition. Thompson Wadsworth. 
  20. ↑ Johnson, Tom "What Tools Do Technical Writers Use". I'd Rather Be Writing. December 19, 2011. Retrieved May 4, 2014.
  21. ↑ "What is LyX". LyX. Retrieved May 9, 2014.
  22. ↑ Hewitt, John (January 18, 2005). "How Technical Writers use Microsoft Visio". Poe War. http://www.poewar.com/document-hack-a-technical-writers-journal-visio-meets-framemaker/. 
  23. ↑ Brierley, Sean (2002). "Screen Captures 102". STC Carolina: 5–8. http://www.stc-carolina.org/wiki_attachments/Screen_Captures_102.pdf. Retrieved May 9, 2014. 
  24. ↑ Johnson, Tom (December 19, 2011). "What Tools Do Technical Writers Use". I'd Rather Be Writing. http://idratherbewriting.com/2011/12/19/what-tools-do-technical-writers-use/. 

External links



Retrieved from "https://handwiki.org/wiki/index.php?title=Technical_writing&oldid=3374226"