**Midterm** CT 137 Hacking and Building Assignment or the Week of March 15 and March 22
For the week of March 15 and March 22:
This is a midterm project period.
Your midterm assignment is posted below and on the Maker Commons site. READ CAREFULLY AND THOROUGHLY!!!
For your midterm, you will create a toy, instrument, game, art, furniture, or wearable (clothing or accessory) that uses at least one digital or analog input and at least one digital or analog output. You will demonstrate your work in a 7-minute lightning talk. You must:
- Build a complete, working circuit (nicely and appropriately housed) that uses the Arduino Uno as your microcontroller.
- Use components and tools available in your Arduino kit. You may replace components that are missing or clearly damaged.
- Write your own code with comments that clearly explain each line of code. You may not copy and paste code. All code must be typed out.
- Include detailed documentation of your work, along with links, text, images, video (where appropriate), tags and categories. You must submit the link to your post in the comments section of the Maker Commons page for this assignment.
You may work in teams or individually, HOWEVER, everyone must post their own documentation and code on their individual blogs, in their own words. Copy and Paste excerpts from team or other resources will not be considered.
If you choose to work in a team, your team must consist of no more than three (3) people and you must form by Thursday, March 12, 3:50 pm. **No changes will be permitted after this time.** Anyone who does not form a group by that time will present an individual project.
Re-purpose code and circuits from the Arduino Starter Kit. Projects 2, 3, 4, 5 and 9 may be useful. It is not recommended that you use the other projects at this time.
Use old objects around the house for housing or as inspiration.
Make your project as interesting and pretty as possible. House it! No bare guts.
See this post for inspiration.
Use your imagination. You need not make your code complicated– in fact, it is not recommended.
Consider how users will interact with your project. Are selected components appropriate?
Tell a story in your documentation. What inspired your project idea? How did you gain resources? What was fun? What proved troublesome and how did you resolve problems?
Use proper terms and simple explanations for the beginner. “Thingy” is not an appropriate component name.
Proofread your documentation (spellcheck does NOT count). Tons of typos, poor spelling and poor grammar will impact the clarity of your communication.
Do not assume your reader or user has experience with your tools, code or project.
Consider including instructions with your project, so users understand its purpose and how to interact with it.
Get feedback others and ask others to test your project.
Lend a hand to someone else. You may discover a solution, remember a fix or come across a great idea.
Raise your hand early. You may ask staff and faculty for assistance, but they are NOT to write code or build any part of the project for you.
Use the “Resources” page on the course blog for help and resources.
99 Cent stores, Walmart, Michaels, Home Depot, Target and your home (and sometimes the street curb) are good places to source cheap items. You will not need anything in terms of electronics (since you are working with components in your kit). However, a list of resources for online and offline tools, components and other physical computing items is included on the class blog.
Allocate time outside of the regular class meet to get your project done.
Write down your project idea with sketches (stick figures are fine) and pseudo code so you can have a blueprint to guide you.
Your complete, working project and documentation are due Thursday, March 19, 7:00 pm. **Work after this point is fine, those revisions will not be considered in terms of the project build evaluation.**
You must be ready to give a strong lightning talk on Tuesday, March 24, between 2:00 pm and 3:30 pm. Everyone participates individually, even if their project was completed as a team.
Use your web documentation to drive your talk. Show the working piece and demonstrate its function.
Your time slot will be assigned Tuesday, March 24, 2:00 pm at the start of the class. Be prepared.
Include setup and breakdown in your time slot. We will keep strict time for each talk, so practice. A lot.
Questions? Email your professor, talk to an assistant, talk to your peers, etc.