| Criteria | Exemplary | Satisfactory | Needs Improvement | Score |
| 4-5 | 2-3 | 0-1 | |
|
| Algorithm |
|
A definite problem is stated and all aspects of the algorithm/technique
to be implemented are clearly described.
|
| | |
The problem to be solved is mentioned, and some aspects of the proposed
algorithm are described, but vague issues remain.
|
| |
| | |
The algorithm to be implemented is not described, and the problem
to be solved is not clear.
|
| |
| |
| Background Knowledge |
|
Includes a complete description of what needs to be learned, how it
connects to course content, and why it is reasonable.
|
| | |
Some necessary background knowledge is alluded to, but incompletely
presented; lacks connections to course content or reasonableness.
|
| |
| | |
No reference to independent background knowledge that must be acquired.
|
| |
| |
| References |
|
References to materials explaining relevant algorithm details are
included and appropriately cited.
|
| | |
References to relevant materials are made, but without complete citations.
|
| |
| | |
Vague or no references to relevant source materials.
|
| |
| |
| Milestones |
|
Four milestones of appropriate difficulty are clearly described.
|
| | |
Some milestones given or some with insufficient detail or inappropriate
difficulty.
|
| |
| | |
Only an overarching goal is stated with no milestones.
|
| |
| |
| Effort |
|
First milestone has been passed and excellent progress is demonstrated.
|
| | |
Some progress has been made, but the first milestone remains incomplete.
|
| |
| | |
Little progress is demonstrated.
|
| |
| |
| Data |
|
Evaluation data and acquisition method are clearly described. Data
difficulty is scaffolded for incremental milestones.
|
| | |
Data sources are vague or acquisition methods are unrealistic. Data
scaffolding is vague or incorrect.
|
| |
| | |
Data sources are not mentioned or scaffolding of data difficulty is
ignored.
|
| |
| |
| Evaluation |
|
A clear evaluation methodology is given for each milestone and the
project as a whole.
|
| | |
Evaluation method given for whole project but not milestones. Metrics
are not clear or comparable.
|
| |
| | |
No metrics for evaluation are given.
|
| |
| |
| Feasibility |
|
Initial work described clearly with tests/results reported. Reflections
on the results clearly integrated with milestones.
|
| | |
Some work performed, but incompletely described and/or unintegrated
with other milestones or data.
|
| |
| | |
No initial evaluations reported or other integration.
|
| |
| |
| Risks |
|
Potential difficulties of each developmental stage are clearly catalogued.
|
| | |
Some risks are mentioned, but potential caveats are missed.
|
| |
| | |
Little to no consideration of risk or difficulty is conveyed.
|
| |
| |
| Professionalism |
|
Proposal contains a coherent, well-organized narrative with no spelling
or grammar errors.
|
| | |
Occasional spelling/grammar errors and/or discontinuous logical structure
in proposal.
|
| |
| | |
Rampant spelling/grammar errors in proposal and/or little to no obvious
organization.
|
| |
| |
|
| | | | | |
| Total | | | | |
| | | | | /50 |