Design Discourse - Composing and Revising Programs in Professional and Technical Writing, 2010a
Design Discourse - Composing and Revising Programs in Professional and Technical Writing, 2010a Design Discourse - Composing and Revising Programs in Professional and Technical Writing, 2010a
Parker So, all in all, the effort to introduce technical communication into the engineering undergraduate curriculum has been a worthwhile one. Furthermore, developing the technical communication course so that it accomplishes what both the profession and the faculty expect of it, while daunting at times and certainly time-consuming, has been an exciting challenge over the years. Now, the effort to integrate communication skills into the more senior level courses, including the graduation project, exemplifies the kind of synergy that is possible between communication specialists and engineering faculty (and, incidentally, the students, the end-users). the professional context: technical communication and the problem-solving model We can define engineering as the application of highly specialized, and technical, knowledge to a practical end that either remedies a problem or represents the “best” solution to a problem, usually within a set of defined constraints. We can then argue that engineers are essentially problem solvers. Following the Mathes and Stevenson model, enunciated in their book Designing Technical Reports, we can also say that most communication in the professional context of engineering comes about because of an engineering problem, a problem that someone has determined needs to be addressed (31). Thus, learning a problemsolving strategy – particularly one that helps to illustrate the connection between engineering design and the communication that must accompany it – will help students prepare for their professional lives in a way that a less practical approach might not achieve. While providing students with clear-cut steps to follow to accomplish their tasks, such a strategy must nonetheless be flexible enough to allow students to move freely between the steps, to pause and reflect, to test and explore, but without the kind of “lock-step” procedure that may stifle creativity and lead to a less satisfying conclusion (Winkler 119). Some years ago, I began to develop such a problem-solving strategy after I realized that the processes used to describe both the writing practice, on the one hand, and the scientific and engineering practice, on the other, were remarkably similar, so much so that, in using the old scientific formula of “observe, test and solve,” I could effectively talk to my engineering students about how they could proceed with their writing tasks. Indeed, these basic steps mirror those described by many other scholars who talked about the link between communication and problem solving (such as Barton and Barton; Dunkle and Pahnos; Flower; Maki and Schilling; Moran; Robinson; Souder; Tryzna and Batschelet; 206
Introducing a Technical Writing Communication Course and Winkler); those who discussed engineering design (such as Krick and Beakley et al); and those who studied engineering problem solving (such as Woods et al). These steps include: define the problem; brainstorm possible solutions to the problem; define the criteria to be used to assess any options offered as solutions to the problem; develop the prototype of a possible solution; test the prototype; and, finally, create the final product or document. Eventually, I developed this connection into a more formal model that my students abbreviated to “C.A.T.S.,” the acronym for Classify, Analyze, Test and Solve, as illustrated below (“Two Hats”; “Problem Solving”; “Implementing Collaborative Projects”; Handbook). This problem-solving model, stressing as it does both the methodology and the process, as Plants et al suggest, guides students as they work so that they are able to proceed fairly quickly and effectively. At the same time, the model is flexible, giving students the option to go back and forth between the steps or skip steps altogether. All in all, this model highlights the importance of problem solving to the entire engineering activity , and it is in this professional context that the model is so useful (Parker “Case Study Workshop” 40, Halstead & Martin 245). Procedure/Activity Engineering Design Communication Design C – Classify • Problem Definition • Gathering Data • Brainstorming Audience Analysis Purpose Formulation A - Analyze • Developing Ideas/Possible Solutions • Examining Technical Alternatives • Developing Working Solutions Communication Alternatives (patterns, outlines) figure 1: problem solving in engineering and communication design (more) 207
- Page 174 and 175: Nugent and it simultaneously—not
- Page 176 and 177: Nugent For each of the sixty-two ce
- Page 178 and 179: Nugent nally, over a third of progr
- Page 180 and 181: Nugent Management Project Managemen
- Page 182 and 183: Nugent • 38% of respondents (10)
- Page 184 and 185: Nugent theory addresses this concer
- Page 186 and 187: Nugent invaluable theoretical model
- Page 188 and 189: Nugent Savage, Gerald J. “The Pro
- Page 190 and 191: Kungl and Hathaway edge, judgment,
- Page 192 and 193: Kungl and Hathaway ideas. That facu
- Page 194 and 195: Kungl and Hathaway minor. To insure
- Page 196 and 197: Kungl and Hathaway we found both we
- Page 198 and 199: Kungl and Hathaway amount of math a
- Page 200 and 201: Kungl and Hathaway We outlined four
- Page 202 and 203: Kungl and Hathaway classes. The uni
- Page 204 and 205: Kungl and Hathaway • starting fif
- Page 207 and 208: 10 Reinventing Audience through Dis
- Page 209 and 210: Reinventing Audience through Distan
- Page 211 and 212: Reinventing Audience through Distan
- Page 213 and 214: Reinventing Audience through Distan
- Page 215 and 216: Reinventing Audience through Distan
- Page 217 and 218: Reinventing Audience through Distan
- Page 219: Reinventing Audience through Distan
- Page 222 and 223: Parker accreditation board. And thi
- Page 226 and 227: Parker T- Test • Evaluating the W
- Page 228 and 229: Parker figure 2: the collaborative
- Page 230 and 231: Parker place. It nonetheless provid
- Page 232 and 233: Parker Canadian scholars focus on a
- Page 234 and 235: Parker Duin, A.H. “Computer-Suppo
- Page 236 and 237: Parker Trzyna, T. & Batschelet, M.W
- Page 238 and 239: Ballentine engineering schools and
- Page 240 and 241: Ballentine engineers outside of the
- Page 242 and 243: Ballentine However, as student grou
- Page 244 and 245: Ballentine want to know more about
- Page 246 and 247: Ballentine Client Letter The letter
- Page 248 and 249: Ballentine and implementation. Natu
- Page 250 and 251: Ballentine Most English departments
- Page 252 and 253: Ballentine Regardless of these indu
- Page 254 and 255: Ballentine unique attributes. Regar
- Page 256 and 257: Ballentine 25 Florman, Samel C. The
- Page 259: futures
- Page 262 and 263: Di Renzo Greater Expectations: A Ne
- Page 264 and 265: Di Renzo for that site, decisions w
- Page 266 and 267: Di Renzo ultimately is impossible (
- Page 268 and 269: Di Renzo Great Society. In the resu
- Page 270 and 271: Di Renzo and screaming, from the cl
- Page 273 and 274: 14 The Write Brain: Professional Wr
Introduc<strong>in</strong>g a <strong>Technical</strong> Writ<strong>in</strong>g Communication Course<br />
<strong>and</strong> W<strong>in</strong>kler); those who discussed eng<strong>in</strong>eer<strong>in</strong>g design (such as Krick <strong>and</strong> Beakley<br />
et al); <strong>and</strong> those who studied eng<strong>in</strong>eer<strong>in</strong>g problem solv<strong>in</strong>g (such as Woods et<br />
al). These steps <strong>in</strong>clude: def<strong>in</strong>e the problem; bra<strong>in</strong>storm possible solutions to the<br />
problem; def<strong>in</strong>e the criteria to be used to assess any options offered as solutions<br />
to the problem; develop the prototype of a possible solution; test the prototype;<br />
<strong>and</strong>, f<strong>in</strong>ally, create the f<strong>in</strong>al product or document.<br />
Eventually, I developed this connection <strong>in</strong>to a more formal model that<br />
my students abbreviated to “C.A.T.S.,” the acronym for Classify, Analyze, Test<br />
<strong>and</strong> Solve, as illustrated below (“Two Hats”; “Problem Solv<strong>in</strong>g”; “Implement<strong>in</strong>g<br />
Collaborative Projects”; H<strong>and</strong>book). This problem-solv<strong>in</strong>g model, stress<strong>in</strong>g<br />
as it does both the methodology <strong>and</strong> the process, as Plants et al suggest, guides<br />
students as they work so that they are able to proceed fairly quickly <strong>and</strong> effectively.<br />
At the same time, the model is flexible, giv<strong>in</strong>g students the option to go<br />
back <strong>and</strong> forth between the steps or skip steps altogether. All <strong>in</strong> all, this model<br />
highlights the importance of problem solv<strong>in</strong>g to the entire eng<strong>in</strong>eer<strong>in</strong>g activity<br />
, <strong>and</strong> it is <strong>in</strong> this professional context that the model is so useful (Parker “Case<br />
Study Workshop” 40, Halstead & Mart<strong>in</strong> 245).<br />
Procedure/Activity Eng<strong>in</strong>eer<strong>in</strong>g <strong>Design</strong> Communication <strong>Design</strong><br />
C – Classify<br />
• Problem Def<strong>in</strong>ition<br />
• Gather<strong>in</strong>g Data<br />
• Bra<strong>in</strong>storm<strong>in</strong>g<br />
Audience Analysis<br />
Purpose Formulation<br />
A - Analyze<br />
• Develop<strong>in</strong>g Ideas/Possible Solutions<br />
• Exam<strong>in</strong><strong>in</strong>g <strong>Technical</strong> Alternatives<br />
• Develop<strong>in</strong>g Work<strong>in</strong>g Solutions<br />
Communication<br />
Alternatives (patterns,<br />
outl<strong>in</strong>es)<br />
figure 1: problem solv<strong>in</strong>g <strong>in</strong> eng<strong>in</strong>eer<strong>in</strong>g <strong>and</strong> communication<br />
design<br />
(more)<br />
207