CSCI 507 / EENG 507 - Final Projects
Final projects will be done in teams of two students. The goal is to
provide deeper understanding and hands-on experience with a specific topic
related to our course material. Another goal is to help improve project skills:
project proposal, independent learning, project execution, and presentation
(both oral and written).
Each team will choose a final project from one of the topics to be described
in class. The course provides a good background to do these projects, but
if you really want to do something else, contact me for approval. I will
ask for project proposals sometime around the middle of the semester. I
just want a short (one page) description of what you will do, your intended
approach, data to be used, and a timeline.
Deliverables
Presentation. The team should give a short
presentation to the class at the end of the semester. Everyone on the team
should participate. A schedule will be provided. Class may run
longer on these days.
Report. Submit (via Blackboard) a final report on the first
Monday of finals week. Reports should be about 15-20 pages, not including appendices. Scoring
factors include: quantity, quality, and degree of difficulty of the work;
analytical or experimental results; clarity of presentation; and depth of
understanding displayed. Reports should be written in such a manner that a
person who is familiar with the class material, but not your specific topic
(i.e., other students taking this class),
could learn the topic from your report. Reports should contain the following material, organized logically
into sections:
- Introduction explaining the topic, and motivation. Specific aims of
your project. Be sure to state clearly any assumptions about images,
environment, lighting, etc.
- Discussion of previous work. You must cite some relevant sources from
the the literature. Describe that work briefly and give some explanation of
how that work fits your topic, is relevant, or is deficient, etc. Don’t just
list it without any comment.
- Description of the techniques you used to solve the problem and/or
perform experiments. Describe the algorithms you used and testing
procedures. Describe programming implementation and the use of existing
software tools. This description (together with your source code) should be
detailed enough for a reader to understand, use, and revise your code.
- Experiments and results, showing images and data. Describe results on
images and/or on your test data sets. Put quantitative results in tables or
graphs. Use statistics (e.g., mean, standard deviation) wherever possible to
describe a collection of measurements.
- Discussion. Achievements, limitations, and possible future work. Where
does it work well, and where does it fail? What would be needed to improve
the results?
- References. List of papers cited in the text. Use a consistent
citation style - see examples of styles in published journal or conference
papers.
- Appendix with any code you developed.
Project Grading
- 20% Presentation. Clarity and completeness of the presentation, use of
overheads and slides.
- 20% Soundness. Technical soundness and accuracy of project.
- 20% Organization and completeness of the report, adherence to guidelines
above.
- 20% Clarity of the report. Includes grammar and spelling.
- 20% Depth and sophistication of project. How difficult or involved was
the algorithm analysis or implementation.
Projects from previous semesters
