Permalink
Browse files

Added final project files

  • Loading branch information...
1 parent e9a7345 commit 917a2b5f0fb9f960f60479d5719d4fcdde60069f @tarynsauer tarynsauer committed Apr 6, 2010
View
@@ -57,7 +57,7 @@ <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 can be found on the course calendar. All other announcements and resources can be found on the <a href="">course website</a></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>jsmith@iit.edu</li>
@@ -67,72 +67,72 @@ <h3>Course overview</h3>
<h3>Objectives</h3>
<p>After completing this course, students will be able to:
<ul>
- <li>Understand genres</li>
- <li>Conduct audience analysis</li>
- <li>Write and edit</li>
- <li>Work collaboratively to</li>
+ <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 discussion</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">Introductory reading</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">Discuss genres</td>
- <td id="calendar">Class exercise</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"></td>
- <td id="calendar"></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"></td>
- <td id="calendar"></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"></td>
- <td id="calendar"></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"></td>
- <td id="calendar"></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"></td>
- <td id="calendar"></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"></td>
- <td id="calendar"><strong>Project 1 Due</strong></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"></td>
+ <td id="calendar"><strong>Project 1 Due</strong></td>
</tr>
<tr class="alt" id="calendar">
<td id="calendar">Oct. 7</td>
@@ -142,8 +142,8 @@ <h3>Course calendar</h3>
<tr id="calendar">
<td id="calendar">Oct. 12</td>
<td id="calendar">Tues.</td>
- <td id="calendar"></td>
- <td id="calendar"></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>
@@ -214,8 +214,8 @@ <h3>Course calendar</h3>
<tr id="calendar">
<td id="calendar">Nov. 23</td>
<td id="calendar">Tues.</td>
- <td></td>
- <td></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>
@@ -225,31 +225,31 @@ <h3>Course calendar</h3>
<tr id="calendar">
<td id="calendar">Nov. 30</td>
<td id="calendar">Tues.</td>
- <td id="calendar"></td>
- <td id="calendar"></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"></td>
- <td id="calendar"></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"></td>
- <td id="calendar"></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"></td>
- <td id="calendar"><strong>Paper Due</strong></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>Final exam: Siegel Hall, Rm 001, 1:30-3:10 p.m.</strong></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">
@@ -273,7 +273,7 @@ <h3>Course calendar</h3>
<td id="grading">25%</td>
</tr>
<tr id="grading">
- <td id="grading">Research Paper</td>
+ <td id="grading">White Paper</td>
<td id="grading">25%</td>
</tr>
<tr id="grading">
@@ -285,14 +285,31 @@ <h3>Course calendar</h3>
<td id="grading">Labs and group work</td>
<td id="grading">10%</td>
</tr>
- </table> <ul>
- <li>Project 1</li>
- <li>Project 2</li>
- <li>Audience Analysis</li>
- <li>Research Paper</li>
+ </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>
- <p>Insert updated (7/2010) university policies here.</p>
+<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">
View
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
View
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
View
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
View
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
View
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
View
@@ -68,11 +68,8 @@ <h3>Scenario description</h3>
</ul>
</p>
<h4>Week one</h4>
- <div class="img">
- <img src="/media/img/scenario1_figure1.png" width="350" height="593" /></a>
- <div class="desc">Figure 1</div>
- </div>
<h3>Create new document & syllabus outline</h3>
+ <img alt="figure 1" width="320px" align="right" src="scenario1_figure1.png"/>
<ol>
<li>Creating an HTML document for the syllabus
<ol>
@@ -90,11 +87,8 @@ <h3>Create new document & syllabus outline</h3>
</ol>
</ol>
<h4>Week two</h4>
- <div class="img">
- <img src="/media/img/scenario1_figure2.png"/>
- <div class="desc">Figure 2</div>
- </div>
<h3>Add course calendar outline & grading scale</h3>
+ <img alt="figure 2" width="320px" align="right" src="scenario1_figure2.png"/>
<ol>
<li>Updating existing documents
<ol>
@@ -110,47 +104,50 @@ <h3>Add course calendar outline & grading scale</h3>
</ol>
<h4>Week three</h4>
<h3>Flesh out calendar & add course objectives</h3>
+ <img alt="figure 3" width="320px" align="right" src="scenario1_figure3.png"/>
<ol>
<li>Updating existing documents
<ol>
<li>You add some of the assigned readings and in-class exercises to the calendar table and finish the course objectives. The syllabus now looks like <strong>Figure 3</strong>.</li>
<li>You <a href="">Make a Commit</a> to match your project's working copy of COM104_syllabus.htm to the <em>com104</em> repository copy.</li>
</ol>
</li>
- <li>Reviewing document history
- <ol>
- <li>Before moving on to other work, you want to review all of the changes you made to the document today.</li>
- <li>You...</li>
+ <li>Reviewing document history: Before moving on to other work, you <a href="">Track Changes</a> to review all of the changes you made to the document today.
</ol>
</li>
</ol>
<h4>Week four</h4>
<h3>Update university policies & make consistent with course objectives</h3>
+ <img alt="figure 4" width="320px" align="right" src="scenario1_figure4.png"/>
<ol>
<li>Updating existing documents
<ol>
- <li></li>
- <li></li>
+ <li>The University has just released their updated academic policies. You copy, paste, and format the policies in the syllabus document.</li>
+ <li>You change the course objectives to make them consistent with the University policies' grading and participation criteria.</li>
+ <li>You <a href="">Make a Commit</a> to match your project's working copy of COM104_syllabus.htm to the <em>com104</em> repository copy.</li>
</ol>
</li>
<li>Adding select update to other branch
<ol>
- <li>You want to add the updated university policies to the syllabus document in the <em>courses</em> branch.</li>
+ <li>You also want to add the updated university policies to the syllabus document in the <em>courses</em> branch, so you <a href="">Switch Branches</a>.</li>
+ <li>You then use <a href="">Cherry-Picking</a> to commit only the university policies update to the syllabus.htm document in the <em>courses</em> branch.</li>
</ol>
</li>
</ol>
<h4>Week five</h4>
<h3>Finish calendar & project requirements</h3>
+ <img alt="figure 5" width="320px" align="right" src="scenario1_figure5.png"/>
<ol>
<li>Updating existing documents
<ol>
- <li></li>
- <li></li>
+ <li>You finish adding the assignments and readings to the course calendar table and add requirement descriptions for each major project assignment.</li>
+ <li>You <a href="">Make a Commit</a> to match your project's working copy of COM104_syllabus.htm to the <em>com104</em> repository copy.</li>
</ol>
</li>
<li>Rolling back last week's changes to course objectives
<ol>
<li>You realize that course objectives should be more consistent with the course calendar and not the university policies, so you want to restore the previous version of the text.</li>
+ <li>You use a <a href="">New Commit to Revert</a> the unwanted changes to course objectives.</li>
</ol>
</li>
</ol>
@@ -159,13 +156,13 @@ <h3>Finish course description & make final edits</h3>
<ol>
<li>Updating existing documents
<ol>
- <li></li>
- <li></li>
+ <li>You make some final edits to the text of the syllabus document.</li>
+ <li>You then experiment with format by making several changes to the syllabus.css document.</li>
</ol>
</li>
- <li>Accepting only some of the textual and formatting changes
+ <li>Accepting only some of the changes
<ol>
- <li>Cherry pick to accept some textual and formatting changes, but reject others.</li>
+ <li>You decide to only accept the textual changes, so you use <a href="">Git Checkout</a> to restore the <em>project</em> repository's version of syllabus.css and restore COM104_syllabus.htm to the revised version.</li>
</ol>
</li>
</ol>

0 comments on commit 917a2b5

Please sign in to comment.