English 421, "Technical Writing"
Catherine A Shuler
Section: 001 & 002
Office Hrs: 9:30 am-10:30 am MWF
Office: Heavilon 220
Ph: 765.494.9681
Fax: 765.494.3780
E-Mail: cshuler@purdue.edu
English 421 helps students become better technical communicators, whose work is characterized by the presentation of technical material in written and visual formats that are user centered and aware of audience and context. The course and its principles are grounded in rhetorical theory and informed by current research in technical communication.
Communication across multiple audiences and for multiple purposes continues to be a desired skill set in technical and professional fields. Beyond field-specific knowledge and experience, successful and ethical communication drives the professional world. This class, in content and form, models these successful communication practices. Working individually and in groups, students learn effective strategies for communicating about and with technology, particularly in networked workplaces and through usability testing. To achieve success in this course, students must display the ability to succeed in their future workplaces by developing a variety of informative and visually effective print and electronic documents.
You will have one required text for this class: Technical Communication Handbook, by Laura J. Gurak and Mary E. Hocks; Instead of additional textbooks, the other readings for English 421 will be drawn from a variety of sources, including academic journals, popular-press magazines and books, blogs and websites, and narratives from technical writing. Course readings cover rhetorical principles, technical writing, ethics, and usability. Furthermore, students are encouraged and sometimes required to find additional readings to supplement their learning. This includes your weekly article assignment for the Documentation Project.
These are general course goals outlined by the Professional Writing Program. Instructors will articulate how each specific project incorporates the course goals.
Writing in Context
Project Management
Document Design
Make rhetorical design decisions about technical documents including
Teamwork
Learn and apply strategies for successful teamwork, such as
Research
Understand and use the research methods and strategies necessary to the production of professional documents, including
Technology
Use and evaluate the writing technologies frequently used in the workplace, such as emailing, instant messaging, image editing, video editing, presentation design and delivery, HTML editing, Web browsing, content management, and desktop publishing technologies.
The focus of Project One is a rhetorical analysis of online discussion sites. This project will prepare you for the other two major projects: the white paper and user documentation in multimedia. Your assignment is to locate a discussion site that discusses an open source software that can be used as a writing tool. You will analyze aspects of the rhetorical situation that have been discussed in class. Particular attention should focus on an analysis of the audience, contributors to the discussion site. Your analysis will be used to create a report on both the function of the software and its effectiveness as a writing tool. At the end of this project, your reports will be used to select the software that will be the subject of your collaborative projects. During this project you will learn about
(Individual; 20% of course grade.)
The focus of Project 2 is the white paper, a common report genre in the professional world. White papers are used in business, industrial, and governmental contexts to sum up the gist of what’s known about a subject. During this project you will learn about
All group members will keep a project log and submit Collaborative Project Evaluation forms.
(Collaborative: 25% of course grade.)
For Project 3, you will work collaboratively in project teams on a client-based service-learning project that teaches you to manage complex writing challenges in real contexts that matter. You will learnn principles of project management, collaboration, document cycling, usability testing and study, and client-based research. Because you will work with real clients--either in the community or online, you will also learn important principles of professional and ethical communication. The goal will be to start with the White Paper Projects produced already this semester and then, after user-testing and usability study, produce a user-guide that teaches a critical and (perhaps) complex application of the technology to an interested client. You will begin the project by thinking of and contacting clients who may benefit from having such your report, which will consist of several components, including a short multmedia, web-based presentation. (Collaborative; 25% of course grade.)
Much of your writing for this class will be posted publicly on the Internet to your individual weblog or our community weblog home page. Weblog posting assignments will include drafts, project logs, and research notes, among other types of content. The calendar specifies what you should post to your weblog and by when, so let that be your guide.
Although we will have many readings each week, you are responsible for writing one, 300-word blog post as a reading response. The reading responses will synthesize the readings and your reactions to them, much like class discussion.
All comments and replies to another's blog post should follow effective rhetorical strategies for networking with others on the Web. (Readings from the course text provide guidelines to follow.)
|
Rhetorical Analysis Project (memo) |
20% |
|
Project 2 |
25% |
|
Project 3 |
25% |
|
Weblogs, Reading Responses, Comments, etc. |
20% |
| Project Logs, Peer Review, Research Posts |
10% |
The three major projects in the course will be comprised of several components, each of which will be worth a percentage of your final grade. For the two collaborative projects, students will complete the required Collaborative Evaluation Form.
All major assignments will be graded on the standard plus-minus letter-grade scale: A=100-94, A-=93-90, B+==89-87, B=86-84, B-=83-80, C+=79-77, C=76-74, C-=73-70, D+=69-67, D=66-64, D-=63-60, F=59 or below.
Students must participate in all of the three major projects and complete a majority of the required weblog posting assignments in order to pass this class. Students with questions about final grades should review university policies regarding grade appeals, which are outlined by the Dean of Students here: "http://www.purdue.edu/ODOS/services/gradeappeals.htm.
This portion of your grade will be based on
In order to participate fully in the course, you should already be able to use the technology platform and applications listed below.
Familiarity with certain technologies is crucial for participation and success in the course. If you need any assistance now or at any point during the semester, please do not hesitate to ask.
During the semester, you'll need regular access to the Internet and email. Because the course home page is the main locus of the class community, you are responsible for reading and keeping current with all content posted there, including what has been submitted by both the instructor and your fellow students. You'll be responsible for configuring your system to access course materials, to read course email and participate in online discussions, and to submit your work. Very early in the semester, you will be asked to demonstrate that you can meet these responsibilities:
If at any time you have problems accessing the Internet from home, you'll need to find a public lab or connection point. Problems with computers will not be an excuse for falling behind or failing to complete required assignments. If your Internet service goes down, find another connection point. If your computer breaks, use another one. In other words, find a way to complete the assignments on time. Because computer problems are a fact of life, always work to complete your assignments early and make frequent backups to multiple media.
Teamwork is a required component of the course. You and your project team members are responsible for updating one another and me about assignment development and progress. In addition, you also are responsible for negotiating together all aspects of your work, including planning, drafting, revising, file managing, and scheduling of assignments. When a collaborative project is assigned, you will receive explicit guidelines for successful collaboration. Individual group members will complete Collaborative Evaluation Forms. For more information about good principles of collaboration, see the brochure, Group Work and Collaborative Writing <http://dhc.ucdavis.edu/vohs/>.
Attendance is required at all scheduled electronic and face-to-face (F2F) meetings. Since you will be working in project teams much of the semester, you also will be required to attend any scheduled out-of-class meetings with your team to complete course assignments. Three absences may result in your final grade being lowered by as much as a letter grade. More than three absences can result in a failing grade for the course. Excused absences may be granted for religious holidays or university-sponsored events, provided you make a written request to me no less than two weeks in advance and that you complete any required work before the due date. Being excessively or regularly late for class or team meetings, both electronic and F2F, can also be counted as an absence.
Cell phones, iPods, iPhones, Blackberrys, and any other personal technologies should not be used inside a college classroom. Thus, in English 421, they are not allowed. Turn them off upon entering the classroom. If you are found to be using any such devices, you will immediately be asked to leave the class and will receive no credit for the day, as per the policies and consequences explicated herein.
Further, any non-class-related use of the computers is considered disruptive to the classroom environment (e.g. checking or using e-mail, Facebook, IM, Sports Illustrated.com, etc.). Because all classes are held in internet-capable computer labs, the temptation to use the machines in such a way is great. Doing so is not only disruptive, it is rude. Thus, if you are found to be using them in such a manner, you will be asked to leave class and receive no credit for the day, as per the policies and consequences explicated herein.
Late work, for the most part (see the ‘Extension Procedure’ below), will receive no credit in this class. That is to say that, when it comes to late work, there is no such thing; the vast majority of missed class assignments cannot be made up and will result in a zero if not completed on time. If you miss a quiz, test, in-class writing, blog-posting, or other assignment or activity for any reason (including absence), you cannot make them up, and will receive a zero on those course components. Also, you must be IN CLASS to hand in any work that is due, unless directed otherwise: If you are absent on the day an assignment or project is to be turned in, you will receive no credit, regardless of your reasons for not turning in the work.
Should a serious and unavoidable problem arise, you will need to obtain an extension from me, your instructor, in order to receive any credit for your work PRIOR to not turning it in on time. The policy for extension is as follows and requires that you:
Purdue students and their instructors are expected to adhere to guidelines set forth by the Dean of Students in "Academic Integrity: A Guide for Students," which students are encouraged to read here:
http://www.purdue.edu/ODOS/osrr/integrity.htm
The preamble of this guide states the following: "Purdue University values intellectual integrity and the highest standards of academic conduct. To be prepared to meet societal needs as leaders and role models, students must be educated in an ethical learning environment that promotes a high standard of honor in scholastic work. Academic dishonesty undermines institutional integrity and threatens the academic fabric of Purdue University. Dishonesty is not an acceptable avenue to success. It diminishes the quality of a Purdue education, which is valued because of Purdue's high academic standards."
Academic dishonesty is defined as follows: "Purdue prohibits "dishonesty in connection with any University activity. Cheating, plagiarism, or knowingly furnishing false information to the University are examples of dishonesty." [University Regulations, Part V, Section III, B, 2, a] Furthermore, the University Senate has stipulated that "the commitment of acts of cheating, lying, and deceit in any of their diverse forms (such as the use of substitutes for taking examinations, the use of illegal cribs, plagiarism, and copying during examinations) is dishonest and must not be tolerated. Moreover, knowingly to aid and abet, directly or indirectly, other parties in committing dishonest acts is in itself dishonest." [University Senate Document 72-18, December 15, 1972]"
If you have any questions about this policy, please ask.
In the event of a major campus emergency, course requirements, deadlines and grading percentages are subject to changes that may be necessitated by a revised semester calendar or other circumstances. You can acquire updated information from the course website, by emailing me, or by contacting me through the English Department at 765-494-3740.
The link below provides access to the final draft of the Protagonize user documentation video.
During week 16 we met and made some minor corrections to our draft. We discussed the comments and usability test results from the previous weeks had given us. We drastically shortened the presentation and combined all four scripts to produce one copy for Michael to read. The first draft that was made up of four videos had significant overlap in the material that was covered. By combining our thoughts a little bit better, we able to condense the material of the documentation. The final draft is much more reader friendly as it addresses only the most relevant topics.
This week we finished our multimedia project. We used the peer evaluations from other people in our class and used their feedback to revise our rough draft. Mike took the corrections that everyone made to their parts and updated them on the website. Then we presented our website in class on wednesday. The final draft of the website is submitted on the class website and the group work is complete. Our group worked well together to complete the project on time.
For the final week we made some minor changes to the multimedia documentation that we presented in class. We felt adding audio as on optional component to our presentation would be beneficial so that was done using a text to speech program and is optional on each slide of the presentation. After that was completed the final project was submitted.
The final draft of The Googlers' user documentation PowerPoint on iGoogle can be found here.
We created a web based tutorial for our documentation. The website also allows the user to download their own copy of each tutorial. This is our complete and final version.
In week 16 we finished up our final version of the multimedia documentation. Audio was added to each slide that could be played if desired. The audio was done using a text-to-speech program and is accessed much like the 'next' and 'back' buttons. We also submitted the final project.
The Multimedia Documentation project is in its final stages. This week, we created the final draft of the document, which in our case is a video with voiceover. The team met on Tuesday evening to create the final draft, which was only slightly modified from the previous draft. Demi and Matt each did the voiceover for one part of the video, while Kyle and I used the other laptops to show how to conduct an online meeting with webcams. Demi then posted the video on YouTube. The final version of the document is due Wednesday, Dec. 16th.