---
# System prepended metadata

title: Design Check Instructions - Project 1 Spring-2022
tags: [Projects-S22, ' Project 1']

---

---
title: Design Check Instructions - Project 1 Spring-2022
tags: Projects-S22, Project 1
---

**Conducting design checks** 

TAs have the option to hold these over Zoom or in CIT. If you wanna hold in-person, please find a table in CIT (either lobby or upstairs table or empty classroom). Design checks should be no longer than 30 minutes, and it's totally okay if they finish early.

I don't really recommend doing the rubric while they're talking. Instead, just have this document open, and anytime there's a requirement, make sure that the group has addressed it. **If the student's submission does not include a requirement, ask them about it, and if they give a good answer, they still get points.** 

Tell the group that you'll be grading their submission.

1. Before the meeting, read through the group's submission and **read through the solution code for the dataset that the group chose**. Even though the design check doesn't include code, it's hard to be helpful if you aren't familiar with the solution.
2. Introduce yourself and say that design checks are meant to be a **casual** discussion about the group's ideas for the project. **Say that the group should switch whoever's speaking after each question.** 
3. If the group submitted their design check really late and you didn't get a chance to read it thoroughly, take a few minutes to read it individually at the beginning of the meeting.
4. **Requirement: Reference Sheets.** The group should have a document that describes the dataset tables. This document should have 1) column names for the global dataset tables and input/output tables for `summary-generator`, 2) an example row for each of these tables and 3) some kind of indicator (this could be color-coding, arrows, anything) of where tables will be joined (i.e. `region` for CO2).
5. **Requirement: Cleaning.** The group should have general steps for how they plan to clean the data. The group should mention 1) one Pyret table function they plan to use and 2) one Pyret strings function they plan to use.
6. **Requirement: Analysis Questions.** For each analysis question for the group's dataset, the group should have 1) a visualization and 2) a table necessary for that visualization. Not required for points, but ask groups if they have a plan to use `filter-with`, `transform-column` and `build-column` to build these tables. A lot of the times, students think that `filter-with` should be used when `transform-column` and `build-column` are necessary. Try to explain when to use each.
7. **Requirement: Check Block for `summary-generator`.** The group should have two examples for `summary-generator`. If the group did not use two different summary functions, explain using functions as inputs and the purpose of the summary function.
8. After the group has finished talking about their submission, ask if they have any questions. Say it's due **March 15**.