Downloads: Assignment (doc) Evaluation Criteria (doc)
Project Resources
For this project you must identify a technical process related to sustainability and create a description that explains that process for an expert, technician or manager reader in your field.. Your description must incorporate one (or more, as needed) definitions. This assignment is based primarily on the principles in Chapters 9 of Technical Communication by Mike Markel, as well as on our class discussions of these genres. To do well on this project, you’ll also need to demonstrate mastery of the skills and strategies described in Chapters 5, 6, and 7 of the textbook. Your finished product should be appropriate for publication in a technical report, proposal, white paper, or training/education program for people in your field. Your target reader is technicians, or students with some expertise in your field, not lay people. This project helps you attain the following goals for this course:
- Write to multiple audiences, for various purposes (e.g., to persuade, to inform, to earn or maintain good will)
- Plan and manage short- and long-term writing projects
- Draft, design, revise, and edit documents
- Design and implement appropriate research strategies
- Follow and adjust to business and technical writing conventions
- Develop effective style and tone
- Design documents (e.g., using page design principles to format documents, incorporating graphics/visuals into documents)
Possible topics for the technical description project
- How are glass products (or a particular glass product) recycled?
- How are plastic products (or a particular plastic product) recycled?
- How is paper recycled?
- How are organic crops (or a particular crop e.g. raspberries) cultivated?
- How are alternative fabrics (or a particular fabric e.g. hemp) cultivated?
- How are alternative fuels (or a particular fuel e.g. solar, biodiesel, wind) generated?
- How does composting work?
- A topic of your choosing as long as it’s sufficiently technical, a process (as opposed to an object or mechanism) and meets the instructor’s approval
Deliverables for the technical description project
For this project you will create the following deliverables:
- Technical description
- Project Assessment Memo that describes the rhetorical choices you made
Caution!
Here are some areas where this assignment might go astray:
- The main focus of this project is a description of a technical process (i.e. how something happens). Your description may also entail descriptions of objects or mechanisms, but these descriptions must in some way support your process description. You will fail the assignment if you submit only an object or mechanism description.
- Technical descriptions are NOT the same as instructions. Instructions include numbered steps and are intended to guide a specific user through a particular task. Technical descriptions give readers an overview of a process (i.e. How does composting work? NOT “How, do you, Jim Bob, compost?).
- Avoid circular definitions, synonyms in definitions, and definitions that are not user-oriented (see TC Chapter 9).
- It’s easy to cross the line into plagiarism on this type of assignment. Borrowing content for this assignment – from any source without proper attribution – results in instantaneous failure of the course and referral of your case to the Dean’s office. Be meticulous about your research, citation, and summarizing/paraphrasing/quoting practices. We’ll use APA format for our citations. Find out everything you need to know about APA here: http://owl.english.purdue.edu/owl/resource/560/01/
- Using a pre-formatted template of any kind is a no-no for all of our deliverables (except for memos, use our course memo template for those). One of the purposes of this assignment is to get you comfortable using MS Word to format documents from scratch. You will fail the assignment if you build your document on a pre-existing template.
Evaluation criteria for the technical description project
1. Product
Your description must:
- Include appropriate components—an introduction, background, parts, and characteristics, visuals, conclusion—divided by headings and subheadings
- Provide descriptive detail at a level for the target audience
- Use appropriate document architecture and a consistent organizational strategy—general to specific, spatial, or chronological—dictated by audience and purpose
- Make effective use of at least two of the following types of definitions: definitions that describe, definitions that compare and contrast, definitions that classify, definitions that provide examples, and definitions that illustrate with visuals
- Integrate definition(s) at appropriate location(s) within the description
- Successfully integrate text and visuals to meet readers’ needs
2. Process
Your document must show evidence of:
- Careful analysis of your audience and purpose (i.e. your document connects with a specific audience for a specific reason)
- Meticulous research and use of source material. This includes appropriate list of citations, in-text citations, proper summarizing, paraphrasing, quoting, and generally giving credit where credit is due
- Careful editing and proofreading
3. Production
Your document must show evidence of an effective production process, including:
- Competent use of word processing features including styles, columns, and other appropriate formatting features
- Submission on time and in accordance with the submission requirements posted in our class web space
- Completion of a Project Assessment Memo and submitted at the same time as the project
Project Assessment Memo
You’ll submit a Project Assessment Memo (PAM) with each major assignment. In the PAM, you are expected to reflect (think about and analyze critically), how the work you did for the assignment helped you understand/achieve the learning objectives for this course. Your PAM should make explicit connections between course goals, readings/class discussions, and your finished product. (See relevant course goals at the top of this page.)
The Project Assessment Memo gives you an opportunity to tell the instructor precisely how and why you applied specific principles and strategies you picked up from our readings and discussions. The only way you can cut yourself short is by not thinking about or adequately explaining your process. You can use the following prompts as a starting point fore a 1-2 page memo (in correct memo format) describing the rhetorical choices you made when you were creating your description.
- How did your audience influence your deliverable? Which types of definitions did you include? Why were they necessary? Which organizational strategy did you use (e.g chronological)? Why?
- What kind of background research did you do to help you understand the process (or any objects or mechanisms involved in the process) so that you could explain it?
- What challenges did you encounter in trying to design a document that was attractive and helped your reader understand/process the information?
Comments (2)
julie.staggers@unlv.edu said
at 3:18 pm on Feb 1, 2009
On Sat, Jan 31, 2009 at 4:15 PM, <julie.staggers@unlv.edu> wrote:
Hi Cameron,
The Technical Description Project and the Wiki Project that follows it, will be on the same topic. The text you generate for the Technical Description Project will give you the content you'll use as the starting point for the Wiki Project; so those two are directly related. For these two projects, you'll write explanations (first to an expert, then to an average Joe) to help them understand how a process works. So, How Las Vegas Recycles Wastewater, or How the Wastewater Recycling Process Works is a GREAT topic for the Technical Description project. There's not a close connection between your wastewater topic and informatics, so you have a couple of options for tackling the "audience" issue: 1) you could assume that you are in wastewater and write as an imaginary expert to another expert reader; or 2) we could brainstorm a scenario in which someone in informatics had a work-related reason for needing to understand this information. We can discuss further on Tuesday if you like.
The Sustainability Project (team project) can be -- and probably will be -- completely different. For this project, you start by identifying a problem and then do research so that you can discover possible solutions to the problem. Eventually, you'll make a recommendation about what the best possible solution to the problem is. So, for this project you'll basically start with a question: What should the university do with its obsolete computer equipment? How can the university sustainability initiative get students more involved? How can the university encourage faculty to go "paperless" for their classes?
I'm hoping this answer helps clear things up. If not, let me know and we'll go for round two. Also, this was a great question. I'd like to share question and answer with everyone else over on the wiki; do you have any objections to that?
Dr. S.
Melissa said
at 9:27 pm on Feb 2, 2009
Hey everyone,
I was wondering if anyone else was having trouble getting to the preliminary proposals page. When I click on the link this is what it says:
I'm sorry, but we couldn't find what you were looking for.
Page names can't have a slash in them.
While normally you can create a new page just by linking to it, there may have been something about the page name that our system didn't like, such as an unexpected period or slash. Try going back to the referring page and removing these odd characters and then trying again.
If you're convinced you shouldn't be seeing this message, please contact support and let us know how you got here.
Please let me know if I am doing something wrong.
Thanks!
Melissa
You don't have permission to comment on this page.