Projects
Projects
Your report must have the following structure, using these section headings:
1. Introduction: A general description of the area of your project and why you're
doing it.
2. Problem Specification: A clear and succinct technical description of the
problem you're addressing. Formulating a general problem (e.g., transcribing
music) into a well-defined technical goal (e.g., reporting a list of estimated
fundamental periods at each time frame) is often the most important part of a
project.
3. Data: What are the real-world and/or synthetic signals you are going to use to
develop and evaluate your work?
4. Approach: A description of how you went about trying to solve the problem.
Sometimes you can make a nice project by contrasting two or more different
approaches.
5. Results and Analysis: What happened when you evaluated your system using
the data and criteria introduced above? What were the principal shortfalls? (This
may require you to choose or synthesize data that will reveal these
shortcomings.) Your analysis of what happened is one of the most important
opportunities to display your command of signal processing concepts.
6. Development: If possible, you will come up with ideas about how to improve
the shortcomings identified in the previous section, and then implement and
evaluate them. Did they, in fact, help? Were there unexpected side-effects?
7. Conclusions: What did you learn from doing the project? What did you
demonstrate about how to solve your problem?
8. References: Complete list of sources you used in completing your project, with
explanations of what you got from each.