Computing · Secondary 4

Active learning ideas

Introduction to Data Persistence: Saving and Loading

Active learning works well for this topic because students need to see firsthand how data disappears when programs end and how lists or dictionaries can temporarily hold that data within a single run. Each activity forces learners to handle data directly, making the abstract concept of persistence concrete through immediate feedback.

• MOE Syllabus Outcomes
• MOE: Programming - S4
• MOE: Data Management - S4

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

Activity 01

• Problem-Based Learning
• 35 min · Pairs

Pair Programming: Quiz Score Saver

Pairs create a 5-question quiz program. Prompt answers, save correct ones in a list using append(). Write a load function to sum scores and display results. Test with different inputs and debug resets.

Explain why data persistence is important for many applications.

Facilitation Tip

During Pair Programming: Quiz Score Saver, encourage partners to swap roles every five minutes so both see the data flow from input to storage.

What to look for

Ask students to write down one reason why data is lost when a program closes. Then, have them describe one way they could make a program 'remember' a user's favorite color during a single run.

• Analyze
• Evaluate
• Create
• Decision-Making
• Self-Management
• Relationship Skills

Activity 02

• Problem-Based Learning
• 45 min · Small Groups

Small Groups: Inventory Tracker

Groups build an inventory system with a dictionary for items and quantities. Add functions to save new stock via user input and load to display totals. Simulate sales by updating and retrieving values.

Analyze how data can be temporarily stored and retrieved within a running program.

Facilitation Tip

For Small Groups: Inventory Tracker, provide physical sticky notes labeled with item names so students can simulate the inventory before coding.

What to look for

Present students with a short Python code snippet that uses a list to store user inputs. Ask them to predict what will be printed if the program is run twice, and explain why the output changes or stays the same.

• Analyze
• Evaluate
• Create
• Decision-Making
• Self-Management
• Relationship Skills

Activity 03

• Problem-Based Learning
• 25 min · Individual

Individual Challenge: User Profile Loader

Individuals code a profile saver: input name, age, hobbies into a list or dict. Save to a global structure, then load in a separate function to print a summary. Restart sections to verify persistence.

Design a simple program that can 'remember' user input during its execution.

Facilitation Tip

In Individual Challenge: User Profile Loader, circulate and ask students to verbalize what happens if they forget to initialize their dictionary before loading data.

What to look for

Facilitate a class discussion using the prompt: 'Imagine you are building a simple calculator app. What kind of data would you want it to remember *during* its execution, and how would you store it using the methods we've learned?'

• Analyze
• Evaluate
• Create
• Decision-Making
• Self-Management
• Relationship Skills

Activity 04

• Problem-Based Learning
• 40 min · Whole Class

Whole Class: Persistence Relay

Class divides into teams; each adds one feature (save, load, edit) to a shared program skeleton projected live. Run tests after each addition, discuss failures as a group.

Explain why data persistence is important for many applications.

Facilitation Tip

For Whole Class: Persistence Relay, assign each team a specific step in the save-load process to ensure full participation.

What to look for

Ask students to write down one reason why data is lost when a program closes. Then, have them describe one way they could make a program 'remember' a user's favorite color during a single run.

• Analyze
• Evaluate
• Create
• Decision-Making
• Self-Management
• Relationship Skills

A few notes on teaching this unit

Teach this topic by starting with a live demo: create a list, add items, then close and reopen the program to show data loss. Use this shock moment to introduce in-memory persistence as a temporary fix. Avoid rushing into files until students fully grasp why memory-only solutions are limited. Research shows students grasp persistence better when they experience the problem before learning the solution, so let the confusion drive the need for the tool.

By the end of these activities, students will confidently explain why simple variables do not persist across a program's parts and how lists or dictionaries can store multiple inputs for retrieval. Successful learners will also design small programs that save and load data intentionally, not accidentally.

---

Watch Out for These Misconceptions

• During Pair Programming: Quiz Score Saver, watch for students who assume the quiz scores stay saved after they close the program.

  Have partners stop and rerun the code to observe the empty list, then guide them to add a print statement after each score is added to confirm storage within the run.

• During Small Groups: Inventory Tracker, watch for students who think the inventory list will remember items between program executions.

  Ask each group to restart the program and observe the empty list, then discuss why apps like this need external storage for true persistence.

• During Individual Challenge: User Profile Loader, watch for students who confuse print statements with actual data storage.

  Require students to add a test line that tries to load the profile immediately after saving, then debug any failures by checking if the dictionary was properly updated.

---

Methods used in this brief

• Problem-Based Learning