How to use this sheet
Take one sheet per team. You are marking only your own course's dimension of the shared file — the row against your course code below. The five criteria are the same in every course and every block, so a 14 means the same thing across the university. The team mark of 15, with the viva of 5 you hold in the Presentations & Viva week and your own quizzes and assignments 10, makes the sessional 30 of the hundred. Where your course falls outside a team's eight, you mark that student's lens note on this same sheet instead.
The window. The file goes in between Sat 12 and Wed 16 December, and the whole window is on time; nothing is accepted after Wednesday 16 December. Individual adjustment. You may move one member up to two marks above or below the team mark on the evidence of the viva and the team charter, with a one-line reason in the comment box. Moderation. The convener samples three files per block and will ask you to re-mark, with them present, if your marks sit three or more (out of 15) away from the other courses on the same file. One or two enrolled members. Where your course marks a Folio for one or two enrolled members of the team, mark their named sections; integration (2) asks whether the section belongs to the Folio, not whether the Folio holds together; no ±2 on a one-member marking.
The 15 marks
| Criterion | Max | What you are looking for | Awarded |
|---|---|---|---|
| Substance in this course's dimension | 6 | Does the part this course marks actually work? Is it right, complete and at the level expected of this year? | |
| Evidence and method | 3 | Is the claim supported? Was the method appropriate, followed, and reported honestly? | |
| Integration with the team's file | 2 | Does this part fit the rest of the work, or does it sit beside it? Is the file one document or five stapled together? | |
| Presentation and professionalism | 2 | Is it legible, cited, complete and handed in on time, in the form asked for? | |
| Revision and response to feedback | 2 | Did the draft change after the session-10 review, and can the team say why? | |
| Total | 15 |
Bands
| Band | Description |
|---|---|
| 13–15 | Professional. Could be handed to the client, the customer or the community as it stands. Reasoning is explicit and the evidence supports every claim. |
| 10–12 | Sound. Complete, correct and defensible, with gaps that are visible but not damaging. |
| 8–9 | Adequate. The work exists and meets the brief, but is thin in evidence, craft or integration. |
| 5–7 | Weak. Incomplete, or complete but not supported. Would need substantial rework to be usable. |
| 0–4 | Not submitted, or so far short of the brief that it cannot be assessed. |
The dimensions in this block
Each course marks only its own row. The wording below is the same as the one printed in that course's outline, so a student reading their outline and a teacher reading this sheet are looking at the same sentence.
| Code | Course | Dimension marked — 15 marks | Teacher |
|---|---|---|---|
| GCCC554 | Compiler Construction | This course marks the language layer of the product: the grammar or input specification the team defined, the scanner and parser that implement it, the checks that catch bad input before it reaches a user, and the test evidence that the layer is correct. 15 marks, team. | Haris Yaseen |
| GCCG562 | HCI & Computer Graphics | This course marks the interface: the user research behind it, the prototype and how it changed after testing, the usability test run with real participants and reported properly, the accessibility check, and the quality of anything the product renders. 15 marks, team. | Haris Yaseen |
| GCCS691 | Advanced Programming – Visual Prog | This course marks the application itself: the architecture, the quality of the code, the interface a stranger has to use without help, the tests and the version-control history, and whether the deployed product actually works when it is opened cold. 15 marks, team. | Haris Yaseen |
| GCDS552 | Database Systems | This course marks the data layer: the conceptual model, the normalised schema and its justification, the quality and performance of the queries the product actually runs, the transaction and backup arrangements, and the handling of any personal data collected. 15 marks, team. | Dr Nasreen |
