- 15% participation: asking questions and speaking during discussions and lecture
Rubric: Percentage of days in which you participate in discussion or ask questions in class
- 10% leading discussion
Rubric: A: Excellent questions that are engaging and generate vigorous discussion B: mediocre questions and discussion C: Weak questions D: Not prepared
- 25% weekly assignments and project descriptions
(Creativity, experimentation, critical thinking – the goal here is to try things out and not be afraid of failing.
Rubric: A: Project and description are excellent B: Project or description are mediocre D: Project or description are inadequate
- Practice, Midterm, and Final projects
In addition to the midterm and final, I will give you grades but no feedback on two projects so that they know what I will expect on the midterm and final. Anyone wanting feedback should make an appointment with me.
- 0% musical instrument (due week 5)
- 0% game
- 25% midterm
- 25% final
- Requirements for two Practice projects, Midterm, and Final projects:
- Meets all of the requirements of the assignment
- Unlike the weekly assignments, these must work correctly
- Schematic
- Either hand drawn or not
- Clear
- Correct
- All inputs on left, all outputs on right, all 5V on top, all GND on the bottom
- Resistor values labeled
- For any components for which there are no schematic symbols, use a box, a label, and include all pin names
- Program
- Filename must end with
.ino (or other for Processing)
- Filename must be meaningful (e.g. name of assignment or project), not e.g. sketch_029.ino
- Indentation must be correct (use <CMD> t or <CTRL> t)
- Meaningful variable names
- All numbers that will not change (e.g. pin numbers, array sizes) must be stored in
const int variables
- There may be some exceptions for this
- Useful comments
- No commented out code without an explanation
- No unused variables or code, unless there is a good reason and that reason is well documented in the code
- Meaningful text in an
Serial.print() or Serial.println()
- No unnecessary delays (i.e. every delay must have a documented reason) and no duplicates
- Break long lines
- Description
- Filename must be README.md
- Properly formatted
- Overall project concept
- Description of how the circuit and the code accomplish the concept
- Circuit schematic
- A photograph of the overall project
- A photograph of the electronics
- A link to a short video
- Problems, if any, and solutions, if any
- If the project did not operate as you intended, describe clearly how it does operate, and why you think it differs from what you intended
- Rubric:
- A: Project exceeds requirements. Excellent description, program, schematic. Project functions flawlessly, or any problems are analyzed and described clearly and correctly
- B: Project meets requirements. Adequate description, program, schematic. Minor problems, good analysis and description of desired and observed behavior
- C: Project meets some requirements but not all. Weak description, program, schematic. Erratic behavior, poor analysis
- D: Project does not meet any requirements
