Technical writing is pragmatic. The purpose is to get people to do something, this includes making a decision. It is an act of communication, rather than an act of self-expression. The focus is on the subject (topic) and the reader; the writer is secondary [17]. Typically, technical writing is communication between a specialist and a non-specialist (lay person), or between a specialist and an expert in the same or different discipline.
The discussion of writing from the previous subsection applies to technical writing as well. The definition of technical writing indicates how it differs from writing in general. Pattow and Wresch [20] defines the processes technical writing as: evaluating the writing situation, conducting research, writing the document, and reviewing and revising. These processes correspond to the general writing models. In terms of the Hayes and Flower model, the first two technical writing processes relate to planning. The third step correlates with translating. The final stage of the technical writing is the same as for writing in general--reviewing.
The first technical writing process is evaluating the writing situation. This process involves: defining the purpose or goal of the document, identifying the audience, determining the type of document that will satisfy the goal, noting the available resources, and identifying time constraints. Also, determining whether or not the task will be completed by a group or an individual is part of this process. This factor has a definite influence on the writing process. As with writing in general, more than one author adds to the complexity of the task because collaboration and group issues are introduced. (This is discussed further in the next subsection.) Conducting research entails collecting, analyzing, and organizing information. Reviewing and revising the document necessitates ensuring that the document meets the needs of the reader and the overall purpose, as well as correcting syntactical errors.