Skip to content
Computer Science · 6th Year

Active learning ideas

Sequences and Instructions

Sequences and instructions are the first step into formal programming for 6th Year pupils. This topic focuses on the precision required to make a computer perform a task. Unlike humans, computers cannot 'guess' what we mean, so the order of commands is absolute. This aligns with the NCCA Primary Mathematics Curriculum's focus on computational thinking and the Digital Learning Framework's emphasis on learner outcomes.

NCCA Curriculum SpecificationsPrimary Mathematics Curriculum (2023) - Computational ThinkingDigital Learning Framework - Domain 1: Learner Outcomes
15–30 minPairs → Whole Class3 activities

Activity 01

Simulation Game30 min · Pairs

Simulation Game: Live Coding

One student is the 'Programmer' and another is the 'Sprite.' The programmer uses physical command blocks (Move, Turn, Jump) to navigate the sprite through an obstacle course in the classroom. If the sprite hits an object, the programmer must 'debug' the sequence.

What happens if code is in the wrong order?
ApplyAnalyzeEvaluateCreateSocial AwarenessDecision-Making
Generate Complete Lesson

Activity 02

Think-Pair-Share15 min · Pairs

Think-Pair-Share: Bug Hunt

The teacher displays a short block-based program with a deliberate sequencing error. Students work in pairs to identify the mistake, predict what will happen when it runs, and suggest a fix before testing it on a screen.

How do we debug a sequence?
UnderstandApplyAnalyzeSelf-AwarenessRelationship Skills
Generate Complete Lesson

Activity 03

Inquiry Circle30 min · Small Groups

Inquiry Circle: Dance Algorithms

Groups create a 4-step dance sequence and write it down as code. They swap their 'code' with another group who must perform it exactly as written. They then discuss how small changes in order change the whole dance.

What is a bug?
AnalyzeEvaluateCreateSelf-ManagementSelf-Awareness
Generate Complete Lesson

A few notes on teaching this unit


Watch Out for These Misconceptions

  • Computers are 'smart' and will know what I mean.

    Students often leave out obvious steps. Use a role-play activity where the 'computer' follows instructions literally (e.g., 'put on shoes' before 'put on socks') to demonstrate the need for absolute precision.

  • A bug means I am bad at coding.

    Normalize debugging as a standard part of work. Use peer teaching to share 'favourite bugs' and how they were solved, reframing errors as puzzles to be cracked rather than failures.


Methods used in this brief