P 5 - Files for production, Work Plan

From CS294-84: Interactive Device Design
Jump to: navigation, search

Overview

  • Submit, through SVN, CAD Files and Circuit Board files you would like us to fabricate.
  • Submit, on the wiki, a detailed work plan: What you have achieved since last week, what you have left to do, who will do what, when you will do it, and what your contingency plans are in case not all design choices work out.


Grading Guidelines

You will be evaluated on whether you've made concrete progress since last week, whether your designs are ready for fabrication, and whether you know how to finish by the end of the semester.

  • Electronics: (5pt) Do you have a concrete plan and prototype for integrating the various components you need into a single system? Do you have either PCB files if you need a custom board or a hand-soldered protoboard? Have you thought about/described how you will power the device?
  • CAD: (5pt) Do you have a complete model of your device? Your current files should be able to hold your current electronics - with mounting bosses, screws for the enclosure, etc.
  • Plan: (5pt) Have you made a detailed plan for the remaining weeks that clearly assigns responsibilities, sets target dates, and lists contingency plans?

Writeup

We suggest the following organization:

Progress since last week

Describe briefly what happened since the last deliverable.

Final PCB and CAD design

Include screenshots and describe any design issues or open questions you still have. The more concrete these questions are, the faster we'll be able to answer them.


Work Plan

A list of major steps you still need to take. Estimate the time it will take you for each step and make deadlines to track your progress. Assign responsibilities to individual team members. Plan time for ordering components and for shipping. At this point, if we don't have a part in the store in 141, you're better off ordering it yourself. Make a Gantt Chart if you feel this is helpful, or a spreadsheet. Also, list the biggest risks to successful completion and think about contingency plans.

How to submit

You know the drill by now:

  • create a wiki page called P5-TeamName.
  • commit your code to SVN:

Turn in your code using the Class Revision Control System

Create a directory for your group for P5:

svn mkdir
http://berkeleyhci.unfuddle.com/svn/
berkeleyhci_devicedesign/assignments/p5/<teamname> -m "creating p5 group directory"

(all on one line)

Where <teamname> is a concatentation of your firstnames or usernames, e.g. bjoern-paul, or your teamname, e.g., ilabgroup. Just make sure we know how to map from the directory name to you.

Then checkout the directory you just created:

svn checkout
http://berkeleyhci.unfuddle.com/svn/
berkeleyhci_devicedesign/assignments/p5/<teamname> p5

Then add your files with svn add and commit them with svn commit.

Only check in your source files - don't check in any binaries. Feel free to check in images, but keep them <2mb each. Don't check in videos.

Submissions