The proposal outlines your project's motivation, design, requirements, ethics, and safety. The project proposal is an expansion on the information provided in the RFA. Use the following format:
- Objective: One to two paragraphs detailing the problem statement and proposed solution.
- Background: One to two paragraphs explaining the context of the problem to be solved by your project, including any relevent references to justify the existence and/or importance of the problem (i.e., the need or want for a solution).
- Physical Design: A pictorial representation of your project that puts your solution in context. Not necessarily restricted to your design. Include other external systems relevant to your project (e.g. if your solution connects to a phone via Bluetooth, draw a dotted line between your device and the phone). Note that this is not a block diagram and should explain how the solution is used, not a breakdown of inner components.
- High-level requirements list: A list of three quantitative characteristics that this project must exhibit in order to solve the problem. Each high-level requirement must be stated in complete sentences and displayed as a bulleted list. Avoid mentioning "cost" as a high level requirement.
- Block Diagram: A general block diagram of the design of your solution. Each block should be as modular as possible and represent a subsystem of your design. In other words, they can be implemented independently and re-assembled later. The block diagram should be accompanied by a brief (1 paragraph) description of the high level design justifying that the design will satisfy the high-level requirements.
- Functional Overview: A brief description of the function of each block in the block diagram and explain how each block contributes to the overall design and feature list above. Include a discussion of the interface with other blocks. Every block in the block diagram must have its own description and each description should be 1-2 paragraphs in length.
- Block Requirements: For each subsystem in your block diagram, you should include a highly detailed block description. Each description must include a statement indicating how the block contributes to the overall design dictated by the high-level requirements. Any interfaces with other blocks must be defined clearly and quantitatively. Include a list of requirements where if any of these requirements were removed, the subsystem would fail to function. Good example: Power Subsystem must be able to supply at least 500mA to the rest of the system continuously at 5V +/- 0.1V.
- Risk Analysis: Identify the block or interface that poses the greatest risk to successful completion of the project. Justify your choice.
- Ethics and Safety
Assess the ethical and safety issues relevant to your project. Consider both issues arising during the development of your project and those which could arise from the accidental or intentional misuse of your project. Specific ethical issues should be discussed in the context of the IEEE and/or ACM Code of Ethics. Cite, but do not copy the Codes. Explain how you will avoid ethical breaches. Cite and discuss relevant safety and regulatory standards as they apply to your project. Review state and federal regulations, industry standards, and campus policy. Identify potential safety concerns in your project.
Requirements and Grading
Please see the Proposal Grading Rubric for grading details. Please see Example Proposal as a guideline for document detail and length. (However, be aware that this proposal uses a rubric from previous years)