Wilteq WILTEQArduino Self-Study
Week 4 · Timing & Evidence

Session 20: Code-correction assessment

Assessment120 minNo new lesson

Learning outcomes

  • Diagnose and repair a faulty sketch by method
  • Record a fault inventory and a debug journal
  • Explain the five fault classes in your own words

Kit and components

  • Uno, USB cable, breadboard, push button, jumpers; optional LED and 330 Ω resistor
  • Printed brief and criteria grid for each learner
  • The door-bell faulty sketch as a file on each lab PC

Pre-reading about 15 min

Students read these on their phones before class. They are listed on the student Before class page.

  1. the Practical Assessments: Competent or not yet competent
  2. the Practical Assessments: Code-correction exercise

Session plan

  1. 0:0010 min
    Discuss

    Briefing and conditions

    Read the brief and conditions aloud and confirm everyone has the faulty sketch file.

  2. 0:1080 min
    Assess

    Independent assessment

    Learners write the inventory first - initial and time each one when you see it - then repair, build and demonstrate. Observe each demonstration and ask the questions from the assessor guidance.

  3. 1:3020 min
    Assess

    Explanations and marking

    Learners write their explanations while you finish the demonstrations. Mark each criterion C or NYC with a short comment.

  4. 1:5010 min
    Wrap-up

    Results and next steps

    Give results privately. NYC learners receive the criteria to work on and the reassessment date (S35).

Checkpoint: ready to move on?

Every learner has a signed grid with each criterion marked and, where Not Yet Competent, written feedback and a reassessment date.

Extension for fast finishers

Learners who finish early start Task A's success criteria from its brief.

Catch-up path

Learners marked NYC redo Code Along chapter 9 and the practice sketch before the S35 reassessment.

Homework and practice

Pre-reading for S21.

Facilitator notes

  • Assessor copy - the door-bell sketch faults: PinMode capitalisation and INPUT instead of INPUT_PULLUP (line 6); missing semicolon (line 7); buttonPin versus ButtonPin capitalisation (line 12); pressed = true assignment (line 13); missing } before else (line 15).
  • Keep the inventories - they are the evidence for criterion 1.
← Session 19Session 21 →