| Category | Excellent | Good | Needs work |
|---|---|---|---|
| Organization & Formatting | 5 All formatting guidelines are followed; YAML is correct with all team members listed. |
4 Most formatting guidelines are followed; YAML is correct with all team members listed. |
3 / 2 Several or all formatting guidelines not followed; YAML contains elements that aren't updated from the template. |
| Research Question | 5 Research question is clear, focused, concise, complex, and arguable. |
4 Research question is reasonably clear and focused, but may be too simple, too complex, or too verbose. |
3 / 2 Research question is unclear and lacks focus; question is far too simple or overly complex. |
| Data Sources | 5 Data sources are clearly described with valid urls or citations used; validity of and concerns about data are discussed; data dictionaries included in appendix. |
4 Some data sources are not clearly described or urls / citations are missnig; validity of and concerns about data are minimally discussed; data dictionaries are in appendix. |
3 / 2 Data sources are poorly described or missing; description of validity of and concerns about data are poor or missing; no data dictionaries provided. |
| Overall Analysis | 18 - 20 Analysis and exploration of data conducted to address research questions; narrative text effectively used to describe analysis and results; overall analysis tells a coherent story addressing research question. |
15 - 17 Analysis and exploration of data conducted mostly addresses research questions; text used to describe analysis and results, but writing quality is poor or not in a narrative format; overall analysis not fully coherent in addressing research question. |
10 - 14 Analysis and exploration of data conducted does not address research questions; text poorly used or missing to describe analysis and results; overall analysis not coherent in addressing research question. |
| Visualizations | 27 - 30 Charts expertly demonstrate best practices of visual design; charts are functionally accurate and address research questions; appropriate chart types used for conveying key messages; annotations are appropriate; minimum of 3 charts met. |
22 - 26 Charts generally demonstrate best practices of visual design; some elements are distracting or confusing; some annotations missing, incomplete, or inaccurate; minimum of 3 charts not met. |
15 - 21 Charts generally lack best practices of visual design; multiple confusing or unclear / distracting elements; unrelated to research question; minimum of 3 charts notmet. |
| Technical Things | 5 All code runs without errors; all files included in the submitted .zip file; report is published on RPubs. |
4 Code has only one or two error, otherwise runs; all files included in the submitted .zip file; or report is not published on RPubs |
3 / 2 Code has multiple errors; submitted .zip file is missing components necessary to reproduce analysis; report not published on RPubs. |
Final Report
Due: June 25 by 11:59pm
Weight: The final report is part of the 40% final project grade.
Purpose: Communicate your data visualization project as a complete, reproducible analysis that tells a clear story using at least three visualizations.
Assessment: Your submission will be assessed using the rubric at the bottom of this page.
Instructions
Use the project template as the starting point for your report. Your final report must be rendered as a self-contained HTML file.
Required Sections
Your report should include all of the following:
1. Introduction
Briefly introduce your topic and state your research question(s). Motivate why this topic is interesting and important. Describe the format option you chose (same question / different audiences; same data / different questions; interactive dashboard) and explain why it fits your project.
2. Data
Describe your data source(s):
- Where did the data come from? Include a URL or citation.
- What are the key variables?
- What pre-processing steps did you take (cleaning, filtering, joining)?
3. Visualizations
Include at least three visualizations that work together to address your research question. For each visualization:
- Give it a descriptive title
- Describe what the chart shows and why you chose this chart type
- Explain how it connects to your research question and the other charts in your project
If you chose the interactive dashboard option, embed your app (via <iframe> or a link) and describe the three visual components.
4. Interpretation
Summarize your key findings. What insights do your visualizations reveal? What patterns, trends, or comparisons stand out?
5. Limitations
Discuss any limitations of your data or your visualizations. What can’t you conclude? What would you do differently with more time or data?
6. Conclusion
Provide a takeaway message. What should a reader remember after viewing your project?
7. References
Cite your data sources, R packages used, and any visualizations or publications that inspired your work.
Formatting Requirements
- Use the YAML header from the project template; update title, author, and date.
- Set
self-contained: trueso the HTML file includes all images and styles. - Set
code-fold: trueso code is accessible but not distracting. - All figures must have descriptive alt text or captions.
- File naming:
5-final.htmland5-final.qmd.
Submission
Submit your project as a link to your rendered HTML report. Your GitHub repository should include:
5-final.qmd— your source file5-final.html— your rendered reportdata/— your data files (if small enough to include in the repo)
Post your link in the designated Blackboard assignment by June 25 at 11:59pm.
Grading Rubric
Your final report is worth 70 points, assessed on the following criteria: