Computing · Year 10

Active learning ideas

Operating Systems: Resource Management

Active learning turns abstract resource management concepts into tangible experiences that students can test and discuss. By simulating CPU scheduling, comparing interfaces, and role-playing memory allocation, students see how operating systems balance competing demands in real time.

• National Curriculum Attainment Targets
• GCSE: Computing - Operating Systems

• 30–45 min
• Pairs → Whole Class
• 4 activities

Activity 01

• Simulation Game
• 45 min · Small Groups

Simulation Game: CPU Scheduling Relay

Divide class into processes holding task cards. Students line up as CPU queues and pass a baton representing CPU time based on round-robin rules. Groups time runs with different algorithms, then discuss efficiency. Debrief with charts of wait times.

Explain how an operating system manages memory and CPU resources.

Facilitation Tip

In the CPU Scheduling Relay, set a strict 30-second timer per process to force students to experience the impact of scheduling decisions immediately.

What to look for

Present students with a scenario: 'Two applications, a web browser and a video editor, are running simultaneously. The video editor is performing a complex rendering task.' Ask students to explain how the OS might manage CPU time between these two processes, referencing one scheduling concept (e.g., priority).

• Apply
• Analyze
• Evaluate
• Create
• Social Awareness
• Decision-Making

Activity 02

• Simulation Game
• 35 min · Pairs

Comparison: GUI vs CLI Challenge

Provide identical tasks like file organization on Windows GUI and Linux CLI emulators. Pairs complete both, timing themselves and noting pros, cons. Class shares findings in a Venn diagram on the board.

Compare the user interfaces of different operating systems (e.g., GUI vs. CLI).

Facilitation Tip

For the GUI vs CLI Challenge, provide identical tasks for both interfaces so students measure usability differences with concrete data.

What to look for

Pose the question: 'Imagine you are designing a new operating system. What are the key trade-offs you would consider when choosing between a GUI and a CLI as the primary interface for your OS? Discuss usability versus resource consumption.'

• Apply
• Analyze
• Evaluate
• Create
• Social Awareness
• Decision-Making

Activity 03

• Simulation Game
• 40 min · Small Groups

Role-Play: Memory Manager

Assign roles: processes requesting memory blocks, OS allocator using first-fit strategy on a shared grid. Groups simulate allocation failures and swaps. Rotate roles and record fragmentation patterns for analysis.

Predict the challenges of developing software without an underlying operating system.

Facilitation Tip

During the Memory Manager role-play, give each student a limited set of index cards to represent physical RAM, forcing them to negotiate solutions when demand exceeds supply.

What to look for

Students write down one specific challenge they anticipate when trying to manage computer memory without an operating system, and one way an OS overcomes this challenge.

• Apply
• Analyze
• Evaluate
• Create
• Social Awareness
• Decision-Making

Activity 04

• Simulation Game
• 30 min · Pairs

Prediction: No-OS Scenarios

In pairs, students list software tasks then brainstorm hardware conflicts without an OS. Use provided prompts to script simple pseudocode solutions. Whole class votes on most critical challenges and proposes OS fixes.

Explain how an operating system manages memory and CPU resources.

What to look for

Present students with a scenario: 'Two applications, a web browser and a video editor, are running simultaneously. The video editor is performing a complex rendering task.' Ask students to explain how the OS might manage CPU time between these two processes, referencing one scheduling concept (e.g., priority).

• Apply
• Analyze
• Evaluate
• Create
• Social Awareness
• Decision-Making

A few notes on teaching this unit

Teach this topic through iterative cycles of simulation, reflection, and comparison. Research shows students grasp invisible processes best when they first act them out, then analyze their own experiences. Avoid front-loading theory—instead, let simulations reveal patterns before formalizing them. Connect each activity to real-world examples students already know, like their school’s computer lab or their own devices.

Students will articulate trade-offs in CPU scheduling and memory management, justify interface choices with evidence, and explain how OS techniques prevent conflicts. They should connect simulations and role-plays to concrete examples of resource allocation in familiar systems.

---

Watch Out for These Misconceptions

• During CPU Scheduling Relay, watch for students assuming faster processes complete first. Redirect by asking them to track which process is waiting longest and why the current queue order matters.

  During the Memory Manager role-play, watch for students believing adding RAM always solves memory issues. Redirect by having them simulate swapping to disk and observe performance trade-offs.

• During GUI vs CLI Challenge, watch for students equating ease of use with power. Redirect by asking them to compare the number of steps required to complete identical complex tasks in each interface.

  During GUI vs CLI Challenge, watch for students assuming CLI is only for experts. Redirect by having them time a peer using both interfaces to complete a file-search task, then analyze efficiency.

• During No-OS Scenarios prediction activity, watch for students thinking hardware manages resources independently. Redirect by asking them to list all the resources a single application would need without an OS and how conflicts would arise.

  During the Memory Manager role-play, watch for students believing virtual memory eliminates all limits. Redirect by giving them a scenario where disk space is also limited and asking how the OS would prioritize swapping.

---

Methods used in this brief

• Simulation Game