Project Proposal

The project proposal should provide a basic description of what your project is, why it is interesting, and why you have chosen to implement it in a particular way. Below is a basic outline for the proposal to be used as a guideline. Please cover all the points listed.

• Project abstract
  A one paragraph description of the project and why it is should be useful to someone.
• Project scenario
  A scenario that highlights how the product will actually be used by and end-user.  Approximately 0.5 pages.
  
• Design strategy
  Provide a description of the overall design, it's major components, and their purpose. Describe any special constraints (e.g., cost, speed, size, storage, power) your design needs to satisfy. State clearly the tradeoffs that will need to be evaluated. Approximately 2 pages.
• Design unknowns
  Describe the features of your design that your group is least familiar with and with which there is no prior experience. For example, an input sensor for which you may have to deal with sensitivity and signal noise issues or a development environment with unfamiliar APIs. Approximately 1 page.
• Implementation plan and schedule
  Outline a plan for implementing your project describing the pieces to be implemented and tested and how they will be integrated. Try to come up with a rough timeline for your work and a rough division of labor between group members. Approximately 1 page.
• Resource requirements
  Specify the resources you'll require for your project. These should focus on the needs you expect to have that are not met by the standard equipment available in the lab. For example, any special programming environments, components, evaluation boards, computing platforms, signals sources (e.g., video or audio), etc.  Think of this as a parts and software list.  Approximately 1 page.