-
Notifications
You must be signed in to change notification settings - Fork 16
/
scenario1_document.htm
352 lines (322 loc) · 14.7 KB
/
scenario1_document.htm
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en" id="mysite-com">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>COM104: Introduction to Technical Communication Syllabus</title>
<link rel="stylesheet" type="text/css" media="screen, print" href="css/reset.css" />
<link rel="stylesheet" type="text/css" media="screen" href="css/syllabi.css" />
<!--[if lte IE 7>
<link rel="stylesheet" type="text/css" media="screen" href="css/screen-ie.css" />
<![endif]-->
<link rel="stylesheet" type="text/css" media="print" href="css/print.css" />
<!--REMOVE COMMENT TAGS TO USE FACEBOOK SHARE METADATA:-->
<!--
<meta name="title" content="Match this with the content of the title tag above." />
<meta name="description" content="A short description of this page." />
<link rel="image_src" href="http://example.com/media/share/thumbnail.jpg" />
-->
<!--REMOVE COMMENT TAGS TO USE FAVICON LINKS:-->
<!--
<link rel="icon" href="" type="image/png" />
<link rel="shortcut icon" href="" type="image/png" />
-->
<script type="text/javascript" src="js/mootools/mootools-core.js"></script>
<script type="text/javascript" src="js/site.js"></script>
</head>
<body>
<div id="page">
<div id="header">
<h1 style="text-align:center">COM104 Course Syllabus</h1>
<ul class="accessibility">
<li><a href="#navigation">Jump to Navigation</a></li>
<li><a href="#content">Jump to Content</a></li>
</ul>
</div>
<div id="content">
<div id="main">
<h2 style="text-align:center">COM 104: Introduction to Technical Communication</h2>
<h2 style="text-align:center">Fall 2010, TuTh 1:30-3:10 p.m.</h2>
<h2 style="text-align:center">Siegel Hall, Rm 001</h2>
<h3>Course overview</h3>
<p>This course explores the...</p>
<p>There are no required textbooks for this course. All readings listed on the course calendar can be found on course reserve under <em>Smith (COM104)</em>. All other announcements and resources can be found on the <a href="">course website</a></p>
<p>Contact Instructor Jane Smith by e-mail or in person:</p>
<ul>
<li>[email protected]</li>
<li>Office: Siegel Hall, Rm 327</li>
<li>Office hours: TuTh 10-11:30 a.m. or by appointment</li>
</ul>
<h3>Objectives</h3>
<p>After completing this course, students will be able to:
<ul>
<li>Understand key technical communication genres and the stylistic and content-related considerations of each</li>
<li>Conduct audience analyses for various document genres</li>
<li>Write and edit technical documents of professional quality</li>
<li>Work collaboratively to write and edit business reports and manage collaborative projects</li>
</ul>
</p>
<h3>Course calendar</h3>
<table id="calendar" width="100%">
<tr id="calendar">
<th colspan="2" align="center" id="calendar">Date</th>
<th id="calendar">Readings for next class</th>
<th id="calendar">Assignments and exercises</th>
</tr>
<tr id="calendar">
<td id="calendar">Sept. 7</td>
<td id="calendar">Tues.</td>
<td id="calendar">Konrath, K. (2003). "Writing in the workplace."</td>
<td id="calendar">Course overview</td>
</tr>
<tr class="alt" id="calendar">
<td id="calendar">Sept. 9</td>
<td id="calendar">Thur.</td>
<td id="calendar">Schroeder, K. (2005). "Document structure and organization."</td>
<td id="calendar">Genre exercise</td>
</tr>
<tr id="calendar">
<td id="calendar">Sept. 14</td>
<td id="calendar">Tues.</td>
<td id="calendar">Gutbrod, N. (2006). "Style and word choice for business writing."</td>
<td id="calendar">E-mail exercise</td>
</tr>
<tr class="alt">
<td id="calendar">Sept. 16</td>
<td id="calendar">Thur.</td>
<td id="calendar">Stern, J.M. (2001). "Strategies for writing reports and technical documentation."</td>
<td id="calendar">Read your choice of white paper from epa.gov for discussion</td>
</tr>
<tr id="calendar">
<td id="calendar">Sept. 21</td>
<td id="calendar">Tues.</td>
<td id="calendar">Kirsch, A.J. (2007). "Procedural knowledge and information age."</td>
<td id="calendar">Introduction to Project 1</td>
</tr>
<tr class="alt" id="calendar">
<td id="calendar">Sept. 23</td>
<td id="calendar">Thur.</td>
<td id="calendar">Hultman, J. (2009). "Procedural documentation in gaming communities." </td>
<td id="calendar">Lab: Group analysis of user-generated content</td>
</tr>
<tr id="calendar">
<td id="calendar">Sept. 28</td>
<td id="calendar">Tues.</td>
<td id="calendar">Find user-generated gaming procedure and bring to class</td>
<td id="calendar">Instructions for the Web exercise</td>
</tr>
<tr class="alt" id="calendar">
<td id="calendar">Sept. 30</td>
<td id="calendar">Thur.</td>
<td id="calendar">Jahn, A. (2003). "An interview-based approach to peer editing."</td>
<td id="calendar">Workshop Project 1 in class</td>
</tr>
<tr id="calendar">
<td id="calendar">Oct. 5</td>
<td id="calendar">Tues.</td>
<td id="calendar"></td>
<td id="calendar"><strong>Project 1 Due</strong></td>
</tr>
<tr class="alt" id="calendar">
<td id="calendar">Oct. 7</td>
<td id="calendar">Thur.</td>
<td id="calendar" colspan="2" align="center">NO CLASS: FALL BREAK</td>
</tr>
<tr id="calendar">
<td id="calendar">Oct. 12</td>
<td id="calendar">Tues.</td>
<td id="calendar">Kuhopt, S. (2010). "Principles and methods of audience analysis." </td>
<td id="calendar">Introduction to Audience Analysis assignment</td>
</tr>
<tr class="alt" id="calendar">
<td id="calendar">Oct. 14</td>
<td id="calendar">Thur.</td>
<td id="calendar"></td>
<td id="calendar"></td>
</tr>
<tr id="calendar">
<td id="calendar">Oct. 19</td>
<td id="calendar">Tues.</td>
<td id="calendar"></td>
<td id="calendar"></td>
</tr>
<tr class="alt" id="calendar">
<td id="calendar">Oct. 21</td>
<td id="calendar">Thur.</td>
<td id="calendar"></td>
<td id="calendar"></td>
</tr>
<tr id="calendar">
<td id="calendar">Oct. 26</td>
<td id="calendar">Tues.</td>
<td id="calendar"></td>
<td id="calendar"></td>
</tr>
<tr class="alt" id="calendar">
<td id="calendar">Oct. 28</td>
<td id="calendar">Thur.</td>
<td id="calendar"></td>
<td id="calendar"></td>
</tr>
<tr id="calendar">
<td id="calendar">Nov. 2</td>
<td id="calendar">Tues.</td>
<td id="calendar"></td>
<td id="calendar"></td>
</tr>
<tr class="alt" id="calendar">
<td id="calendar">Nov. 4</td>
<td id="calendar">Thur.</td>
<td id="calendar"></td>
<td id="calendar"><strong>Project 2 Due</strong></td>
</tr>
<tr id="calendar">
<td id="calendar">Nov. 9</td>
<td id="calendar">Tues.</td>
<td id="calendar"></td>
<td id="calendar"></td>
</tr>
<tr class="alt" id="calendar">
<td id="calendar">Nov. 11</td>
<td id="calendar">Thur.</td>
<td id="calendar"></td>
<td></td>
</tr>
<tr>
<td id="calendar">Nov. 16</td>
<td id="calendar">Tues.</td>
<td id="calendar"></td>
<td id="calendar"></td>
</tr>
<tr class="alt" id="calendar">
<td id="calendar">Nov. 18</td>
<td id="calendar">Thur.</td>
<td id="calendar"></td>
<td id="calendar"></td>
</tr>
<tr id="calendar">
<td id="calendar">Nov. 23</td>
<td id="calendar">Tues.</td>
<td>Morissy, M. (2006). "Emerging skills in technical communication."</td>
<td>Speaker: Joyce Rasmussen</td>
</tr>
<tr class="alt" id="calendar">
<td id="calendar">Nov. 25</td>
<td id="calendar">Thur.</td>
<td colspan="2" align="center" id="calendar">NO CLASS: Happy Thanksgiving!</td>
</tr>
<tr id="calendar">
<td id="calendar">Nov. 30</td>
<td id="calendar">Tues.</td>
<td id="calendar">Haber, P. (2009). "Communicating across cultures: Considerations..."</td>
<td id="calendar">Lab/discussion reviewing international communication</td>
</tr>
<tr class="alt" id="calendar">
<td id="calendar">Dec. 2</td>
<td id="calendar">Thur.</td>
<td id="calendar">Mirel, B. (1998). "Applied Constructivism for User Documentation."</td>
<td id="calendar">Documentation exercise</td>
</tr>
<tr id="calendar">
<td id="calendar">Dec. 7</td>
<td id="calendar">Tues.</td>
<td id="calendar">Nielsen, J. (2000). "Ten good deeds in Web design."</td>
<td id="calendar">Usability exercise</td>
</tr>
<tr class="alt" id="calendar">
<td id="calendar">Dec. 9</td>
<td id="calendar">Thur.</td>
<td id="calendar">Reviw editing and assessment techniques</td>
<td id="calendar">Workshop papers in class</td>
</tr>
<tr id="calendar">
<td id="calendar">Dec. 14</td>
<td id="calendar">Tues.</td>
<td colspan="2" align="center" id="calendar"><strong>Paper Due: Siegel Hall, Rm 001, 1:30-3:10 p.m.</strong></td>
</tr>
</table> <h3>Grading & project requirements</h3>
<table id="grading">
<tr id="grading">
<th id="grading">Coursework</th>
<th id="grading">Items</th>
<th id="grading">Grading</th>
</tr>
<tr id="grading">
<td rowspan="2" id="grading">Projects</td>
<td id="grading">Project 1</td>
<td id="grading">15%</td>
</tr>
<tr id="grading">
<td id="grading">Project 2</td>
<td id="grading">20%</td>
</tr>
<tr id="grading">
<td id="grading" rowspan="2">Papers</td>
<td id="grading">Audience Analysis</td>
<td id="grading">25%</td>
</tr>
<tr id="grading">
<td id="grading">White Paper</td>
<td id="grading">25%</td>
</tr>
<tr id="grading">
<td rowspan="2" id="grading">Participation</td>
<td id="grading">In-class discussion</td>
<td id="grading">5%</td>
</tr>
<tr id="grading">
<td id="grading">Labs and group work</td>
<td id="grading">10%</td>
</tr>
</table>
<ul>
<li><strong>Project 1:</strong> Write a 400-word procedural writing deliverable that instructs the audience on how to accomplish a given task. Deliverables will be judged on how effectively they make use of illustrations and how thoroghly they address audience needs given stated assumptions regarding knowledge and skill-level.</li>
<li><strong>Project 2:</strong> Select a published article and edit/rewrite it for an online magazine. Deliverables will be judged on how well the address stated audience needs, the constraints of the online medium, and the style of the website.</li>
<li><strong>Audience Analysis:</strong> In 1,000 words, analyze the manner and success with which the author(s) of an article tailor the writing to the intended audience. Papers will be judged by how well they make an argument and thoroughly address content, organization, layout and visuals.
</li>
<li><strong>White Paper:</strong> A 800-1,000 word white paper on submitting walkthroughs/gaming tips to a wiki or community website. Papers will be judged on mechanics, style, formatting, and how well they address the audience needs per the audience analysis.</li>
</ul>
<h3>University policies</h3>
<h4>Grading Criteria</h4>
<p>A - Student has turned in all required components of a project, the work is exceptional in quality, and reflects the student's dedication to adjusting the project to his or her own interests.</p>
<p>B - Student has turned in all required components of a project and submitted work that is acceptable as graduate level.</p>
<p>C - Student has turned in all required components of a project, but the work is below graduate level.</p>
<p>E - Student has not turned in all required components of a project.</p>
<h4>Attendance and Participation</h4>
<p>Your attendance and active participation are required both for your own success in the class, and for the success of the class as a whole. However, if you absolutely must miss, you must contact the instructor ahead of time via email.</p>
<h4>Academic Honesty</h4>
<p>As with any course at IIT, you are expected to uphold the Code of Academic Honesty in the <a href="">Undergraduate Student Handbook</a>. All work for this course should be your own original effort, including print and digital page design and computer code. Summarizations and quotations of text, as well as any use of open source code libraries and images not of your own making, should be clearly cited as legally and ethically warranted and rhetorically appropriate.</p>
<p>If you are at all uncertain as to whether you are submitting work that in whole or in part may violate the Code of Academic Honesty, please contact me immediately and before the work is due. The consequences of academic dishonesty are severe. Any student who violates the Code of Academic Honesty will be subject to expulsion from this course with a failing grade, and I will report the student to the Chair of the Department of Humanities and the Associate Dean of Graduate Academic Affairs, who may take additional disciplinary action.</p>
<h4>Special Needs Statement</h4>
<p>Students who have any difficulty (either permanent or temporary) that might affect their ability to perform in class should contact me privately, either in person or via email, at the start of the semester. Methods, materials, or deadlines will be adapted as required to ensure equitable participation.</p>
</div>
<div id="supporting">
</div>
</div>
<ul id="navigation">
<li><a href="index.htm">Home</a></li>
<li><a href="resources.htm">Resources</a></li>
<li><a href="about.htm">About</a></li>
</ul>
<div id="footer">
<p class="copyright">
© 2010 by Gewgaws Lab. Some rights reserved. Content licensed under a
<a rel="license" href="http://creativecommons.org/licenses/by-sa/3.0/us/">
Creative Commons Attribution-Share Alike 3.0 United States License
</a>.
<a class="cc-badge" rel="license" href="http://creativecommons.org/licenses/by-sa/3.0/us/">
<img alt="Creative Commons License" src="http://i.creativecommons.org/l/by-sa/3.0/us/88x31.png" />
</a>
</p>
<p class="project-information">
<a href="http://github.com/gewgaws/git-for-writers">Git for Writers repository</a>
hosted at <a href="http://github.com">GitHub</a>. Learn <a href="participate.htm">how to
contribute</a> to Git for Writers.
</p>
<ul class="validators">
<li><a href="http://validator.w3.org/check?uri=referer" title="Validate this page's XHTML">XHTML</a></li>
<li><a href="http://jigsaw.w3.org/css-validator/check/referer" title="Validate this page's CSS">CSS</a></li>
</ul>
</div>
</div>
</body>
</html>