SubjectNest resource library

Development draft · local review needed

Day 12 · A nested key can still have a bugYear 7 Inquiry · T1 W3–4 · Day 12 lesson

Prepare this lesson

Year 7 / Integrated / Term 1 / Weeks 03 04

Part of the full two-week lesson sequence. Check the pack guide and taught point before teaching.

Open for this lesson: Pack guide · Daily routes · Worked swaps · Fresh learner checks · Aids and text routes.

Download full sequence

Teacher copy: This page may include teaching prompts or answer keys. Answer keys in this public library can be viewed by anyone. Give learners a clean prompt, use checks as formative evidence, and change a case locally when prior access matters.

Learner prompts

Codes: AC9TDI8P05, AC9TDI8P06, AC9S7I06. Goal: represent Version 1 as nested flowchart/pseudocode and trace one input to an error. Prepare: blank key/trace mat and Version 1.

  1. Open · 3 min. Ask what an IF choice needs: testable condition, two branches and an output or next test.
  2. Model · 5 min. Put Version 1's outer edge choice in a flowchart diamond, then nested tip/stem choices; read corresponding pseudocode aloud. Trace T1 to S2.
  3. Investigate · 8 min. Pairs trace T3 step by step: smooth → pointed → S3, then compare all three traits and find the long/short mismatch. Mark bug: missing final check.
  4. Choice · 10 min. D12-A/B/C: draw flowchart plus pseudocode, act with rule cards, or trace an erroneous branch table. Require a state-by-state trace, not a guessed output.
  5. Check · 6 min. Ask whether T4 should be J1 just because one edge has jagged section. No: mixed edge and short stem conflict with J1. Suggest “unmatched” branch and full-profile verification.
  6. Note · 3 min. Record whether learner linked a specific condition to the wrong output; next use a fresh fictional input.

Later/home: An optional extra can rewrite one nested condition in plain words. Paper algorithm only; no programming account needed.