110 likes | 252 Views
Your name, date, 600.478:2009. Guidelines. The requirements/design presentation must present the problem, context, an outline of your solution (method(s) you are hoping to implement, extend), and a measure of success (accuracy, or performance metrics).Should contain block level/psuedo-algorithmic
E N D
1. Your name, date, 600.478:2009 Review Presentation Template 600.478:2009
2. Your name, date, 600.478:2009 Guidelines The requirements/design presentation must present the problem, context, an outline of your solution (method(s) you are hoping to implement, extend), and a measure of success (accuracy, or performance metrics).
Should contain
block level/psuedo-algorithmic sketches/diagrams of key components.
A timeline
Bottlenecks/data/methods/goals you will need to be successful
3. Your name, date, 600.478:2009 Outline
4. Your name, date, 600.478:2009 Project Goal
5. Your name, date, 600.478:2009 Need to be met/Impact
6. Your name, date, 600.478:2009 Review of prior art
7. Your name, date, 600.478:2009 Project Requirements
8. Your name, date, 600.478:2009 Your chosen method/design This is a high level design containing only block/method/module level information flow.
9. Your name, date, 600.478:2009 Scope of your project Include a timeline
10. Your name, date, 600.478:2009 Challenges What might keep you from being successful
11. Your name, date, 600.478:2009 Performance/Accuracy Measures Discuss how you will know you have succeeded.