You will map the paper into four outputs: a references explanation, exact dry-run tables and output, a records-versus-ADT comparison, and a full procedural program.

You will spend about 35–45 minutes producing a brief plan or partial answer for each question type without opening model answers or receiving teaching.

You will classify each question type as ready, nearly ready, or repair needed and name the precise failure, such as missing concepts, weak example use, dry-run formatting, control-flow semantics, program logic, decomposition, validation, or ADT use.

You will be recommended the explanation, dry-run, program-design, or full-program repair sessions that match your gaps, with the double-mark programming question prioritised when several areas are weak.

You will begin two double-sided A4 pages containing only high-value answer structures, dry-run rules, program patterns, and personal error traps exposed by the diagnostic.