Computing · Year 5

Active learning ideas

Operating Systems and Software

Active learning helps students move beyond passive listening to build mental models of how operating systems function. By sorting, simulating, and testing ideas, they connect abstract concepts like resource management to concrete experiences they can discuss and remember.

• National Curriculum Attainment Targets
• KS2: Computing - Computer Systems

• 20–40 min
• Pairs → Whole Class
• 4 activities

Activity 01

• Think-Pair-Share
• 30 min · Small Groups

Card Sort: Classifying Software

Prepare cards listing software like Windows, Microsoft Word, antivirus tools, and games with brief descriptions. In groups, students sort cards into 'system software' or 'application software' piles and justify choices with evidence from descriptions. Conclude with a whole-class share-out to refine classifications.

Explain the purpose of an operating system for a computer to function.

Facilitation Tip

During Card Sort: Classifying Software, circulate as pairs debate examples, noting where students struggle to separate system software from applications.

What to look for

Present students with a list of 5-7 software items (e.g., Microsoft Word, Windows 11, Google Chrome, macOS, a drawing app, printer driver, a video game). Ask them to sort these into two columns: 'Operating System/System Software' and 'Application Software'. Review their sorting to identify misconceptions.

• Understand
• Apply
• Analyze
• Self-Awareness
• Relationship Skills

Activity 02

• Think-Pair-Share
• 40 min · Small Groups

Role-Play: OS Resource Manager

Assign roles in small groups: one student as the operating system, others as hardware (CPU, memory) and applications requesting resources. Simulate scenarios where apps compete for memory; the OS allocates and resolves conflicts. Debrief on why coordination matters.

Differentiate between system software and application software.

Facilitation Tip

For Role-Play: OS Resource Manager, assign roles before starting so students focus on simulating tasks rather than managing group dynamics.

What to look for

On a small card, have students write one sentence explaining what would happen if a computer booted up with no operating system. Then, ask them to list one example of application software and one example of system software they used today.

• Understand
• Apply
• Analyze
• Self-Awareness
• Relationship Skills

Activity 03

• Think-Pair-Share
• 25 min · Pairs

Prediction Demo: Life Without OS

Show a short video or simulated boot sequence of a computer without an operating system. In pairs, students predict issues beforehand, like no desktop or program crashes, then compare predictions to the demo and note real-world examples from devices.

Predict what would happen if a computer did not have an operating system.

Facilitation Tip

In Prediction Demo: Life Without OS, pause after each prediction to ask pairs to explain their reasoning before revealing the next scenario.

What to look for

Pose the question: 'Imagine you have a brand new computer, but it has no operating system installed. What is the very first thing you would need to do before you could even open a web browser or play a game?' Facilitate a class discussion focusing on the OS as the foundational software.

• Understand
• Apply
• Analyze
• Self-Awareness
• Relationship Skills

Activity 04

• Think-Pair-Share
• 20 min · Individual

Device Audit: Software Inventory

Students examine a school device or their own, listing installed software. Individually classify each as system or application, then pair up to verify and discuss borderline cases like web browsers. Share findings in a class tally.

Explain the purpose of an operating system for a computer to function.

Facilitation Tip

During Device Audit: Software Inventory, model how to check multiple locations (Settings, Start Menu) to ensure thoroughness before students begin.

What to look for

Present students with a list of 5-7 software items (e.g., Microsoft Word, Windows 11, Google Chrome, macOS, a drawing app, printer driver, a video game). Ask them to sort these into two columns: 'Operating System/System Software' and 'Application Software'. Review their sorting to identify misconceptions.

• Understand
• Apply
• Analyze
• Self-Awareness
• Relationship Skills

A few notes on teaching this unit

Teachers should emphasize layered thinking: the OS sits below applications, handling invisible but critical tasks. Avoid letting discussions focus only on visual elements like icons or wallpapers. Use analogies students know, like a librarian managing books (OS) versus specific books (applications) they want to read. Research shows hands-on sorting and role-play reduce misconceptions about software layers more effectively than lectures.

Students will confidently differentiate operating systems from applications, explain core functions like memory management, and justify why a computer cannot run without an operating system. Clear explanations and accurate categorization during activities show understanding.

---

Watch Out for These Misconceptions

• During Card Sort: Classifying Software, watch for students who place operating systems like Windows or macOS into the application category, treating them as software you open like a game or word processor.

  Guide students to consider what happens when they turn on the computer: the OS loads first, allowing apps to run. Ask them to think about whether the desktop background or login screen is the OS or just a feature the OS provides to users.

• During Role-Play: OS Resource Manager, listen for students who describe the OS only as a tool for changing wallpapers or adjusting volume, reducing its role to aesthetics and sound.

  Use the simulation to highlight the OS managing CPU time and memory for multiple apps. Ask role-players to explain how they decide which app gets more resources when two run at once, tying their actions to real system functions.

• During Prediction Demo: Life Without OS, listen for students who claim that a computer might still work if you install apps carefully without an OS, suggesting they believe the OS is optional.

  Demonstrate that without an OS, hardware cannot interpret app instructions. Ask students to predict what error messages might appear and why, using their knowledge of boot processes to justify their claims.

---

Methods used in this brief

• Think-Pair-Share