Each student's final score out of 100 combines the capstone with the assignments and quizzes from the course. Change the weights to see how the ranking would shift. This changes only your own view of the page.
Each bar is a student's final score, split into what the capstone, assignments and quizzes contributed. Hover a bar for the breakdown; click it to open the student's full report.
Click a column to sort. Click a student to open their full report.
Each line is one student's marks in the order they happened: three Python assignments and the Python quiz, the FastAPI work, the capstone and the final score. The dashed line is the class average. Pick up to three students to compare. Hover a column for everyone's marks on that piece of work, and hover a dot for the marker's note.
Each piece of work had a different difficulty, so growth is measured against the class, the way the quiz reports did it. For every student, the hollow dot is where they stood in the Python phase (A4–A6 and the Python quiz), the small dot the FastAPI phase (A7, six-API, A8 and the FastAPI quiz) and the solid dot the capstone (team mark and viva). Zero is the class average. Growth is the move from the first dot to the last; work that was missed or excused is left out of these averages. Click a student to open their report.
Every quiz topic, assignment criterion and capstone criterion is filed under one of nine skill areas, so each area can be followed through the course. In the Python and FastAPI weeks a level combines that phase's quiz topics with the assignment criteria in the same area; the capstone column is the team's mark on that area's criteria. Hover a cell to see exactly what it is built from.
| Skill area | Python weeks 24–28 Aug | FastAPI weeks 2–7 Sep | Capstone (team) 25 Sep |
|---|
Each cell is a student's level in one skill area, coloured by how far it sits above (blue) or below (red) the class average for that area. Switch phases to follow an area through the course, or choose "Change" to see who moved up or down against the class in each area from its first appearance to its last. Click a name to open the student's report.
The team mark out of 80. The darker part (63 marks) was marked from the repository: shared requirements, the hard problem's code and tests, process and clean code. The lighter part (17 marks) is the demo: explaining the hard problem (5), the live change (10) and the paper design (2). Chips show each member's viva out of 20; click one to open that student's report.
The team mark line by line: what was found in the repository (63 marks) and at the demo (17 marks). Open a team to see each criterion, the evidence and the mark. Marks where a team lost half or more are in red. No team wrote its hard-problem tests before the code, so that line is 0/3 everywhere.
Quiz average (across) against viva mark (up). Students in the top right both know the material and can explain what they built. Those in the bottom right know the theory but struggled to explain their own code. Those in the top left explained their code better than their quizzes suggest.
Rows are students in order of final rank; columns are the course in date order. Darker means a higher mark. Click a column heading to sort by it, hover a cell for the marker's note, and click a name to open the student's report.
| Student | Assignment | Own-work confidence | Mark (blended → halved) | Why it was tagged |
|---|