Data Engineering at the University of Florida
Use this rubric when reviewing project proposals (Week 4).
Total Points: 100
| Score | Points (per criterion) | Description |
|---|---|---|
| 5 | 100% of weight | Excellent |
| 4 | 80% of weight | Good |
| 3 | 60% of weight | Satisfactory |
| 2 | 40% of weight | Needs Work |
| 1 | 20% of weight | Incomplete |
| Score | Meaning |
|---|---|
| 5 | Excellent - Publication-ready quality |
| 4 | Good - Strong with minor improvements needed |
| 3 | Satisfactory - Acceptable but needs refinement |
| 2 | Needs Work - Significant gaps or issues |
| 1 | Incomplete - Major revision required |
Is the research problem clearly defined and well-motivated?
| Score | Description |
|---|---|
| 5 | Crystal clear problem; compelling motivation; significance well-argued |
| 4 | Clear problem statement; good motivation |
| 3 | Problem understandable but motivation could be stronger |
| 2 | Problem vague or poorly motivated |
| 1 | No clear problem statement |
Guiding Questions:
Does the proposal demonstrate knowledge of prior work?
| Score | Description |
|---|---|
| 5 | Comprehensive survey; clear positioning relative to prior work |
| 4 | Good coverage of relevant work; identifies gaps |
| 3 | Some relevant work cited; positioning could be clearer |
| 2 | Limited related work; missing key references |
| 1 | No related work or completely irrelevant citations |
Guiding Questions:
Is the methodology feasible and technically sound?
| Score | Description |
|---|---|
| 5 | Innovative approach; clearly feasible; well-justified choices |
| 4 | Sound methodology; reasonable approach |
| 3 | Approach understandable but some details unclear |
| 2 | Methodology vague or potentially infeasible |
| 1 | No clear approach or fundamentally flawed |
Guiding Questions:
Are the proposed metrics and baselines appropriate?
| Score | Description |
|---|---|
| 5 | Comprehensive evaluation; appropriate metrics; strong baselines |
| 4 | Good evaluation plan; reasonable metrics and baselines |
| 3 | Basic evaluation outlined; some gaps |
| 2 | Evaluation unclear or inappropriate metrics |
| 1 | No evaluation plan |
Guiding Questions:
Is the proposal well-written and organized?
| Score | Description |
|---|---|
| 5 | Exceptionally clear; well-organized; no errors |
| 4 | Clear writing; good organization; minor errors |
| 3 | Understandable but could be clearer; some disorganization |
| 2 | Hard to follow; significant writing issues |
| 1 | Incomprehensible or severely disorganized |
Guiding Questions:
## Proposal Review: [Team Name]
**Reviewer:** [Your Name]
**Overall Recommendation:** [Strong Accept / Accept / Weak Accept / Weak Reject / Reject]
### Scores
| Criterion | Score (1-5) | Weight | Points |
|-----------|-------------|--------|--------|
| Problem Statement | | 20% | /20 |
| Related Work | | 20% | /20 |
| Proposed Approach | | 25% | /25 |
| Evaluation Plan | | 20% | /20 |
| Writing Quality | | 15% | /15 |
| **Total** | | 100% | **/100** |
### Summary
[2-3 sentence summary of the proposed work]
### Strengths
1.
2.
3.
### Weaknesses
1.
2.
3.
### Questions for Authors
1.
2.
### Minor Comments
-
### Recommendation
[Explain your overall assessment and what would strengthen the proposal]
When calibrating your reviews: