Design Proposal
The purpose of the design proposal is to:
  • clearly state the objectives of the project;
  • outline the methods of obtaining these objectives (including schematics);
  • communicate a project schedule that
    • provides evidence the project will be completed on time;
    • defines the roles and responsibilities of the group members; and
    • defines a development sequence to obtain the objectives.
    This schedule is likely presented by way of a Gantt chart;
  • outline experiments that will be used to evaluate the performance of each subsystem and the project as a whole. These experiments need to successfully address any hazards that the project presents; and
  • provides an estimated project budget.
It is from this document that a decision will be made as to whether or not further project development will occur. This review and approval process is part of a Critical Design Review (CDR).

It is suggested that you create this proposal prior to creating the CDR presentation and the materials associated with it. The CDR presentations are typically derived from this report.

The design proposal is the most critical part of the project. Good planning at this stage will make the remainder of the project go smoothly. Poor planning can lead to nightmares.

As a document length benchmark, prior years have required a submission no longer than 10 pages.

Please include the following items, using an organization method that you deem appropriate:
  • the project title, your group number, and member names;
  • a description of the project and its goals (with specifications of the final product). The target audience of the general description is the layman. The technical component should be aimed toward electrical engineers (your peers);
  • a brief discussion of background information relevant to the project. This will cite references;
  • a block diagram showing the overall design;
  • schematics drawn using Eagle schematic capture. This is the complete circuit including all interface requirements. Provide a textual description such that functionality is understandable by anyone in electrical engineering. Please cite your sources;
  • a testing section describing the experiments you will perform to test each subsystem in the design and the overall system. These experiments will often be firmware-oriented. For instance, to verify the connection of a 2x20 char LCD, firmware can be written to display information on the device. If a project presents hazards, ensure that these are addressed within this section. Please present this section in the order that development will occur;
  • a section presenting the project development schedule and sequence, including a description of the roles of the individuals within your design group. Division of labour is often subsystem-oriented; and
  • a cost estimate of the final "product". You may also outline labour costs, if you feel it appropriate.

Submission: Draft and Final Versions

Two versions of the Design Proposal are to be submitted: a draft version for the purpose of peer-evaluation, and a final version. Additionally, a peer-reviewed draft is submitted by individuals. The draft proposal, your peer review of another group's submission, and the final version of your group's proposal are submitted on different dates noted in the syllabus. The following sections outline the requested submission methods, and the grading associated with the submissions.

Draft Version Grading

Your draft submission is evaluated in a bid to ensure that it is relatively complete. A relatively simple grading scheme is used by your instructor and is available here: Draft Proposal Submission Rubric.

Draft Version Submission

Please submit as many individual paper copies of the draft version of the report as there are individuals in your design group. Please make submission to the course submission box outside the ECE General Office by 4PM on the date noted in the syllabus. Please do not staple all copies together, rather, staple the copies individually and use a paper clip to hold them together.

Proposal Draft Peer Review Grading

Shortly after submssion of the draft proposals, you will be provided with another group's report to review. To assist you in providing the feedback to the author group, you will be provided with a Proposal Review Sheet that you are asked to complete. In turn, your review is evaluated by course instruction personnel according to this Proposal Review Rubric.

Proposal Draft Peer Review Submission

Please return the marked-up copy of the paper you reviewed (complete with the review sheet) to the course submission box outside the ECE General Office by 4PM on the date noted in the syllabus.

Final Version Grading

In respect to evaluation of the final version of the design proposal, a relative grading scheme (one with respect to all submissions by all groups) will be used. A marking scheme is available here: Design Proposal Marking Scheme. Please note that the final version of the report is expected to satisfactorily address the feedback provided by your peers.

Final Version Submission and Return of Peer-Reviewed Copies

Please submit an electronic copy of a PDF version of this item by using the EE Capstone Submission Facility by 4PM on the date noted in the syllabus. (Any member of a group may submit on behalf of their entire group.)

Also by 4PM on the date noted in the syllabus, please return all the peer-reviewed copies of your draft final report and Engineering Drawings (System Block Diagram) to the course submission box outside the ECE General Office: since these reviews contain both the author group's work, and work by the reviewer, they will be kept by your instructor and destroyed according to FOIPP regulations.