Use this guide as a working review for Programming Assignment Checklist. Begin with “Confirm required language and version”, then move through “List inputs, outputs and edge cases” and the remaining stages against your own brief. The aim is to leave a clear trail from the requirement to the technical evidence and final explanation, rather than relying on a generic submission checklist.
Confirm required language and version
Treat “Confirm required language and version” as a decision point rather than a box to tick. Write down what could go wrong, what another student or marker would need to reproduce, and which assumption should be tested. That makes the transition to “List inputs, outputs and edge cases” much easier to justify.
Before leaving this stage, reproduce the important result from a clean starting point where possible. Check filenames, versions, commands and references, and make a short note of limitations. Those notes are useful later when you write evaluation or prepare for a demonstration or viva.
List inputs, outputs and edge cases
A practical way to handle “List inputs, outputs and edge cases” is to create a small, inspectable output first. Compare it with the rubric, record any dependency or source you relied on, and only then expand the work. This prevents the final report from becoming disconnected from the actual technical process.
Before leaving this stage, reproduce the important result from a clean starting point where possible. Check filenames, versions, commands and references, and make a short note of limitations. Those notes are useful later when you write evaluation or prepare for a demonstration or viva.
Build small testable components
For “Build small testable components”, work directly from the wording of your own assessment. Note the exact action verbs, required files and marking signals that relate to this stage. Then decide what concrete evidence will demonstrate completion before moving on to “Capture meaningful evidence”.
Before leaving this stage, reproduce the important result from a clean starting point where possible. Check filenames, versions, commands and references, and make a short note of limitations. Those notes are useful later when you write evaluation or prepare for a demonstration or viva.
Capture meaningful evidence
A practical way to handle “Capture meaningful evidence” is to create a small, inspectable output first. Compare it with the rubric, record any dependency or source you relied on, and only then expand the work. This prevents the final report from becoming disconnected from the actual technical process.
Before leaving this stage, reproduce the important result from a clean starting point where possible. Check filenames, versions, commands and references, and make a short note of limitations. Those notes are useful later when you write evaluation or prepare for a demonstration or viva.
Clean the repository before submission
Treat “Clean the repository before submission” as a decision point rather than a box to tick. Write down what could go wrong, what another student or marker would need to reproduce, and which assumption should be tested. That makes the transition to “Confirm required language and version” much easier to justify.
Before leaving this stage, reproduce the important result from a clean starting point where possible. Check filenames, versions, commands and references, and make a short note of limitations. Those notes are useful later when you write evaluation or prepare for a demonstration or viva.
Final check for Programming Assignment Checklist
Return to the first section, compare the finished work with each rubric row and verify that every important claim is supported by code, a test, a result, a source or a clearly reasoned explanation. Remove evidence that does not help the reader understand or assess the work.