# Technical Writing Seminar¶

#### ECE 4920, V. Hunter Adams (vha3@cornell.edu)¶

Note: I've adopted many of Bruce Land's policies for this course.

## The Objective¶

This course fulfills the College of Engineering Technical Communication requirement, and may also be used as an advisor-approved elective.

## Prerequisites¶

You must have taken ECE 4760 or ECE 5760 in a previous semester to enroll in this course. You may not take this course and ECE 4760/ECE 5760 simultaneously.

## Procedure¶

#### Before our first meeting¶

• Read articles from a variety of publications to decide which is most appropriate for your project. I will help you with this, of course, but it's best if you've done some preliminary reading. Some publications that you might consider include (but are not limited to):
• Depending on your project, you might also consider an academic journal (in rare cases) or a publication devoted to the particular topic for your project (music, biology, etc.).
• Email me to setup a first meeting.

#### At our first meeting (first or second week of classes)¶

• We will decide upon a target publication, based on your research.
• We will obtain a style guide for your target publication.
• We will establish a meeting schedule.

#### Before our second meeting¶

• Resolve IP considerations with your lab partners.
• All partners that are participating in this class will be co-authors.
• Partners that are not participating in this class have two options. Each partner must send me an email specifying their chosen option.
• They will be a co-author, and therefore participate in approving the writing, but not do the writing.
• They will not be a co-author, and therefore will be acknowledged but not participate in the writing or approval.
• Rewrite you final project report. Take this first draft very seriously.
• Reorganize your report for a top-down explanation of the project. Remember that your audience may be non-specialist. If so, have a nonn-engineering friend read your draft for clarity.
• Remove all references to our particular class (e.g. "We used Hunter's board."), replace these with more general statements.
• Where appropriate, remove highly specific references to our architecture. For example, replace "We configured Timer 2 to overflow every 909 CPU cycles." with "We configured a 16-bit timer, incrementing at 40MHz, to overflow every 909 cycles." Someone that knows about microcontrollers should understand what you're saying, even if they've never worked with our specific microcontroller. These sorts of errors are most common in first drafts.
• Eliminate ABET-specific sections from your report, and convert to a design narrative suitable for the publication's target audience. In most cases, you don't need the ethics, safety, or work distribution sections.
• All images should be included.
• Research background material and related projects. Assemble a reference list to include in the manuscript.
• Reorganize and (if necessary) extend the results section of the original report.
• Do not use any code in the text of the manuscript. Explain it in words. There are occasional exceptions to this, but never for PLIB function calls.
• Follow the style guide for the target publication.
• Submit your first draft through Canvas one week before our next meeting. I need time to read through the draft.

#### At our second meeting (fourth or fifth week of classes)¶

• We will discuss necessary revisions to your first draft.

#### At every subsequent meeting (we'll meet every two weeks)¶

• We will discuss necessary revisions to your most recent draft.

Usually, it takes 3-4 revisions to get the manuscript ready for submission. Sometimes more, sometimes less. Once we all agree that it is ready, submit it to the magazine/journal and cc me!

• Timely submission of writing drafts during the semester. Your final grade will drop one grade-step (A$\rightarrow$A-, B+$\rightarrow$B) for every week that a deliverable is late.