Computer Science · 6th Year · Programming Fundamentals · 2.º Período

Sequences and Instructions

Pupils write their first block-based programs, ensuring commands are executed in the correct order to achieve a goal.

TL;DR: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 Specifications
• Primary Mathematics Curriculum (2023) - Computational Thinking
• Digital Learning Framework - Domain 1: Learner Outcomes

About This Topic

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.

In this unit, students move from 'unplugged' logic to block-based coding environments. They learn that a 'bug' is simply a mistake in the sequence and that debugging is a positive, iterative part of the creative process. This mindset shift is crucial for building resilience and problem-solving skills that apply across all areas of the Irish curriculum.

This topic comes alive when students can physically model the sequences and see the immediate impact of changing a single instruction.

Key Questions

1. What happens if code is in the wrong order?
2. How do we debug a sequence?
3. What is a bug?

Watch Out for These Misconceptions

Common Misconception

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

What to Teach Instead

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.

Common Misconception

A bug means I am bad at coding.

What to Teach Instead

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.

Active Learning Ideas

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.

30 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.

15 min·Pairs

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.

30 min·Small Groups

Frequently Asked Questions

Which block-based language is best for 6th Year?

Scratch is the most common in Irish schools due to its versatility and community support. However, VEXcode VR or Microsoft MakeCode are also excellent for showing how sequences control virtual robots or hardware.

How does sequencing link to literacy?

Sequencing in code is very similar to procedural writing in the Primary Language Curriculum. Both require a clear beginning, middle, and end, and both rely on transition words or logical steps to ensure the reader (or computer) can follow along.

What are the best hands-on strategies for teaching sequences?

Unplugged activities are essential. Using physical blocks or cards to build a program before touching a computer helps students focus on the logic. Collaborative debugging, where students help each other find errors, also builds a supportive classroom culture.

How do I assess a student's ability to sequence code?

Look at their 'debugging' process. A student who can identify why a sequence failed and systematically test a solution is demonstrating a higher level of understanding than one who simply gets it right by accident.