Computing · Year 7

Active learning ideas

Input Devices

Active learning works well for input devices because students need to physically interact with hardware to grasp how data flows from the real world into computers. Hands-on testing and comparisons make abstract concepts like sensors and precision tangible, building lasting understanding beyond textbook definitions.

• National Curriculum Attainment Targets
• KS3: Computing - Computer Systems
• KS3: Computing - Hardware

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

Activity 01

• Stations Rotation
• 45 min · Small Groups

Stations Rotation: Device Testing Stations

Prepare stations for keyboard, mouse, touchscreen, and sensor (e.g., micro:bit light sensor). Groups test each for 7 minutes, noting input speed, accuracy, and errors in a shared table. Rotate and discuss findings as a class.

Analyze how sensors allow computers to interact with the physical world.

Facilitation Tip

During Device Testing Stations, circulate with a clipboard to listen for students naming both the device and the type of data it captures, such as 'the motion sensor detects movement direction'.

What to look for

Provide students with images of three different input devices (e.g., a webcam, a joystick, a barcode scanner). Ask them to write one sentence for each, explaining its primary function and one specific situation where it would be the best choice.

• Remember
• Understand
• Apply
• Analyze
• Self-Management
• Relationship Skills

Activity 02

• Decision Matrix
• 30 min · Pairs

Pairs: Comparison Matrix Challenge

Provide images or devices; pairs create a matrix comparing three input devices on criteria like cost, portability, and use cases. They justify choices with examples, then present to another pair for feedback.

Compare different input devices based on their functionality and typical use cases.

Facilitation Tip

In the Comparison Matrix Challenge, provide a printed blank matrix on A3 paper so pairs can annotate with sticky notes when they debate device suitability.

What to look for

Ask students to identify the input device used in a specific scenario, such as 'How does a smart thermostat know the room temperature?' or 'How does a video game character jump when you press a button?'. Students write down the input device and briefly explain its role.

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

Activity 03

• Decision Matrix
• 35 min · Whole Class

Whole Class: Sensor Response Demo

Use micro:bits or similar to demo sensors detecting light or tilt. Class predicts outcomes, tests in darkened room or by shaking, and logs data on shared board to identify patterns.

Design an input system for a specific user with accessibility needs.

Facilitation Tip

For the Sensor Response Demo, prepare a simple circuit with an LED that lights up when a light sensor detects darkness, so students see real-time input-to-output translation.

What to look for

Pose the question: 'Imagine you are designing a computer for someone who cannot use their hands. What input devices would you consider, and why are they suitable?' Facilitate a class discussion where students share and justify their design choices.

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

Activity 04

• Decision Matrix
• 25 min · Individual

Individual: Accessibility Design Brief

Students sketch an input system for a user scenario (e.g., visual impairment). They list devices, justify choices, and note adaptations like larger keys or voice input.

Analyze how sensors allow computers to interact with the physical world.

What to look for

Provide students with images of three different input devices (e.g., a webcam, a joystick, a barcode scanner). Ask them to write one sentence for each, explaining its primary function and one specific situation where it would be the best choice.

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

A few notes on teaching this unit

Teachers should emphasize the flow of information from the physical environment into the computer, using concrete examples like how a microphone converts sound waves to digital signals. Avoid overgeneralizing devices; instead, highlight their specialized roles, such as how touchscreens prioritize gesture recognition over typing precision. Research suggests students retain concepts better when they test physical limitations, like trying to use a touchscreen with gloves during accessibility prototyping.

Successful learning is evident when students can explain not just what input devices do, but why certain devices fit specific tasks. They should compare functionality, recognize the role of sensors in environmental data capture, and apply these ideas in design contexts like accessibility.

---

Watch Out for These Misconceptions

• During Device Testing Stations, watch for students labeling sensors as output devices because they light up or make sounds.

  During Device Testing Stations, hand students a printed data flow diagram with blanks for 'input' and 'output' and ask them to fill in examples from each station, such as 'light sensor → light level data → computer'.

• During Comparison Matrix Challenge, listen for pairs claiming keyboards and mice are the only 'real' input devices.

  During Comparison Matrix Challenge, provide a row in the matrix titled 'Unconventional Inputs' and require pairs to research and include at least two examples like eye-tracking or voice commands before finalizing.

• During Accessibility Design Brief, expect students to assume all input devices work the same for every user.

  During Accessibility Design Brief, give students a 'limitation card' with scenarios like 'user wears thick gloves' or 'user has limited vision' and require them to test their prototypes against these constraints.

---

Methods used in this brief

• Stations Rotation
• Decision Matrix