Computing · Year 3

Active learning ideas

Constructing a Digital Branching Database

Active learning works for constructing digital branching databases because students experience firsthand how decisions about attributes and question order shape the efficiency of real-world data systems. Hands-on creation with tangible items and peer testing makes abstract ideas about logical flow and minimisation concrete and memorable.

• National Curriculum Attainment Targets
• KS2: Computing - Data and Information
• KS2: Computing - Information Technology

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

Activity 01

• Plan-Do-Review
• 35 min · Pairs

Pairs: Class Toy Database

Students work in pairs to photograph 10 classroom toys and create a branching database with yes/no questions like 'Is it soft?' or 'Does it have wheels?'. They test the database on each other, timing searches, then swap and improve based on feedback. End with a paired demo to the class.

Analyze how the order of questions affects the speed of finding an answer in a database.

Facilitation Tip

During Pairs: Class Toy Database, circulate and ask each pair to explain their first two questions and why they placed them at the top of the tree.

What to look for

Provide students with a simple list of 5 animals. Ask them to write down the first two yes/no questions they would use to start building a branching database to identify them. Then, ask them to explain why they chose those questions first.

• Remember
• Apply
• Analyze
• Self-Management
• Decision-Making
• Self-Awareness

Activity 02

• Plan-Do-Review
• 45 min · Small Groups

Small Groups: Question Order Race

Groups build two versions of a food database: one with random questions, one optimised. Classmates search both while groups time results. Discuss which order works best, then rebuild the slower one. Record efficiency gains in group logs.

Construct a digital branching database for a specific topic.

Facilitation Tip

In Small Groups: Question Order Race, time each group’s optimised tree against their original version and post the results for comparison.

What to look for

Students exchange their completed branching databases. Each student tests their partner's database by trying to identify 3 different items. They then provide feedback on one thing they liked and one suggestion for improvement, focusing on whether the paths were clear and easy to follow.

• Remember
• Apply
• Analyze
• Self-Management
• Decision-Making
• Self-Awareness

Activity 03

• Plan-Do-Review
• 40 min · Whole Class

Whole Class: Database Testing Gallery

Students upload finished databases to shared software. The class walks around devices, testing each one and noting search times and confusions on sticky notes. Creators review feedback in plenary and vote on the most user-friendly.

Evaluate the user-friendliness of a branching database.

Facilitation Tip

In the Database Testing Gallery, give each group three test objects they did not use when building their database to ensure genuine peer evaluation.

What to look for

During database construction, circulate and ask students: 'What attribute are you using for this question?' and 'What happens if the answer is 'no'?' This checks their understanding of attributes and logical flow.

• Remember
• Apply
• Analyze
• Self-Management
• Decision-Making
• Self-Awareness

Activity 04

• Plan-Do-Review
• 25 min · Individual

Individual: Personal Reflection Trail

Each student sketches their question tree before digitising, then journals changes after testing. Compare initial and final paths to note efficiency improvements. Share one key learning in a class circle.

Analyze how the order of questions affects the speed of finding an answer in a database.

What to look for

Provide students with a simple list of 5 animals. Ask them to write down the first two yes/no questions they would use to start building a branching database to identify them. Then, ask them to explain why they chose those questions first.

• Remember
• Apply
• Analyze
• Self-Management
• Decision-Making
• Self-Awareness

A few notes on teaching this unit

Teachers approach this topic by framing databases as decision tools rather than static lists. Use live timings to show how broad-first questioning halves the search space at each step. Avoid letting students add questions for quantity; insist on precision. Research suggests students grasp logical flow better when they test others’ work than when they only build their own.

Successful learning looks like students designing databases where broad attributes split items quickly, clear yes/no questions lead users logically to each item, and peers can identify objects within five steps. Reflection shows students adjusting their trees based on feedback and timing results.

---

Watch Out for These Misconceptions

• During Pairs: Class Toy Database, watch for students arranging questions by whim or listing every attribute instead of choosing broad splits.

  Ask pairs to explain their first question’s breadth: Does it split the full set roughly in half? If not, prompt them to swap for a higher-level attribute like size before material.

• During Small Groups: Question Order Race, watch for groups adding more questions to improve speed rather than reordering existing ones.

  Provide a printed list of their current questions and have them mark which ones can be moved upward to broaden splits; time both versions to show gains from sequencing alone.

• During Whole Class: Database Testing Gallery, watch for students assuming their tree will work for any theme once it’s built.

  Ask each group to test three items outside their original theme; when dead ends appear, have them revise one question to include cross-theme attributes like weight or colour.

---

Methods used in this brief

• Plan-Do-Review