The Project Proposal is a written document listing the team members, overviewing the topic (for example, speech recognition) to be addressed by the project, with a literature or research review relevant to the proposed project, complete with citations and references in standard (e.g., IEEE journal) format, and a proposal as to the specific project and goals to be performed. That is, the Project Proposal should be a description of the intended final "product", (e.g., DSP-based program for recognition of the digits 0-9), and a description of the specific algorithms or approach that will be taken for the implementation, based on the results of the literature/background review. Typically, this would consist of a detailed block diagram of the proposed system along with which algorithm or method will be used to implement each block. The Proposal should summarize two milestones to be achieved during the course of project development, along a description of the final deliverable and mock-up of the application. The minimum viable product (MVP) and stretch goals should be clearly delineated. The Project Proposal can generally be expected to serve as a basis for the Introduction, Background Research, and parts of the system design portions of the Final Report, should the proposed approaches prove successful.
It is expected that a group of 3 team members will have a project of larger scope than a team with 2 members.
The followings summarize the required key components of the final proposal.
Introduction
Literature or Research Review including a brief description of the reference, other approaches that existing apps/papers use to tackle the same topic, your unique upgrades or secret sauce
Results from the prototype
Deliverable illustrating the final product to be delivered to the customers
MinimumViableProduct(MVP): committed “minimum” deliverable
StretchGoals: time permitting extra features
Milestones
Testing and Validation Plan for Android
There is not a strict page requirement, but 5-10 pages is a reasonable range to consider.
During the project, students will have to demonstrate 2 milestones toward the completion of their projects. The Project Plan must clearly state what are deliverables at each of these project milestones as "contract" between the student and the ECE 420 teaching staff. These project milestones (5% each) will be evaluated based on this contract.
The final project demonstration will be a scheduled but relatively formal review by the ECE 420 teaching staff of the (hopefully) completed project in action. The project team will deliver a presentation describing the final project deliverable and the algorithms/approach taken in implementing that deliverable. The project team will then demonstrate their system, or all working components if incomplete, perform verification experiments or show test results confirming to the satisfaction of the course staff that it works as designed, and answer any questions.
The lab tablets can be connected to the project via HDMI for better visual during the final demonstration, however the HDMI changes the behavior of the tablets slightly and can be overrided.
Each project team will submit a final report. This written report should include at least:
Introduction
Literature or Research Review
Technical Description of the project including equations, block diagrams, and possibly pseudocode
Screenshots illustrating the application "in action" and highlighting salient features of your app
Final results section including descriptions of the testing done on the project and problems encountered
Suggestions for Extensions and/or Modifications
Software/Hardware Documentation including an overview of the program structure (e.g. responsibilities for each file/function), logic diagrams, etc., as applicable
There is not a strict page requirement, but 10-15 pages is a reasonable range to consider. The documentation should be concise, but sufficient to convey the application's purpose and underlying algorithm structure and implementation. Another student should easily be able take up where the project left off or to use the results in a future project.