[F26] Rubric Meeting

[Sir-NoChill]

Review and discussion points from August 17 Rubric Meeting

• Running both the compilers and the generated code through valgrind - Coherence?
• We need to look inside people's code to see what they understand
• Should we drop the code points in favour of peer-review points?
  • @novo52 the lab exams work as a verification step, so that they serve as a 'gate' to ensure that the students know
  • Can we set a minimum passing grade on the lab exams while keeping them at a small weighting?
• For each assignment we need a portion of the total weight
  • for each assignment we then assign a non-negligible portion to the lab exams
  • Generator - lab exam = 60%
  • LOLCode - lab exam = 50%
  • VCalc - lab exam = 33-40%
  • Gazprea - lab exam = 25-33%, @jnamaral has a different weighting perspective
• We need to budget TA time, but could we followup with the groups? The students need to know what they get assessed on. Should we talk with the english department?
• Get automatic class hierarchy diagrams from doxygen or jetbrains tooling
• remember 'cairo, no buildings are finished because the tax goes up when it is finished' - if you ask for a metric, you get the metric
• How do we tie in the project management tooling to this term
• Non-negligible amount of points for signing in questions
• Marking budget for the subjective portion

Action Items

• Writing up the deliverables for the oral exam - how does it affect the other marking? What happens if it's not one? @rcunrau
• Writing up the deiverables for the interviewers @novo52
• Take a look at how to build rubrics for the software engineering portions
• We should look at hours estimates for interviews with implementation teams
• Closing issues on the spec, namely [SPEC]: Vector Semantics? #106 and vector related issues @Sir-NoChill
• LOLCode spec tests currently take input, segment into multiple tests @rcunrau
• Get it into the syllabus @rcunrau
• Development Log Rules with a peer-evaluation within teams @Sir-NoChill
• Make us teachers @rcunrau
• How are the implementation details ( Add architecture properties to implementation guidelines #103 ), should we merge them into the rubric?
  • Two new sections under grading for interviews and lab exams @novo52

[novo52]

Suggestion for an alternative to interviews with teams: we could create channels in discord for each team to use for communication, which the TAs have access to. Then, we can see if they are going off the rails and if they are doing design work with each other. IDK if they should be enforced as the primary method of communication or if this is a good idea, LMK what you think.

[Sir-NoChill]

I do like that idea, it at least gives them all a central place to ping us for group-related questions, it almost replaces the question forum.

We could pre-populate the teams in the discord server and permission gate by role access then when the students choose their groups they can obtain a role. Do we know our enrollment numbers yet?