Hardware Basics

Overview

Students explore the main hardware components of a computer, with a focus on the CPU and RAM. They connect hardware specifications to performance and usability, laying groundwork for later lessons on computer systems and security.

Learning intentions

Students will:

• identify key hardware components in a computer system, focusing on CPU and RAM
• explain, in everyday terms, how CPU and RAM specifications affect how quickly tasks can be completed
• make recommendations for suitable hardware choices based on different user needs (light vs heavy workloads)
• use digital tools responsibly to organise and present evidence of learning

Success criteria

Students can:

• describe what a CPU does and what RAM does in a computer
• explain how more capable CPU and sufficient RAM can improve performance for specific tasks
• match a given workload scenario to appropriate hardware needs using simple reasoning
• communicate their explanation clearly using the class template or shared slide

Curriculum links

• Technologies — AC9TDI8K01: explain how hardware specifications affect performance and select appropriate hardware for particular tasks and workloads
• Technologies — AC9TDI8P11: select and use digital tools efficiently to create and communicate content using common conventions
• General capability focus: critical and creative thinking by making evidence-based hardware recommendations

Lesson structure (60 minutes)

1. 0–6 min · Hook (Think–Pair–Share). Teacher shows two short “device experience” scenarios (e.g., slow loading during a game; video editing stalling during playback) and asks what might be inside the device that causes the differences. Students think-pair-share and record one guess on their worksheet.

2. 6–15 min · Guided introduction: CPU vs RAM. Teacher uses a simple labelled diagram of a computer to explain roles: CPU as the “doer” that carries out instructions; RAM as temporary fast workspace that holds data/programs while tasks are running. Students annotate their diagram with brief definitions and one “real-world analogy” for each.

3. 15–25 min · Spec-to-performance mini model. Teacher demonstrates with a short class discussion and board prompts:

• If a CPU is faster/more capable, tasks can be processed with less delay.
• If RAM is too small, the computer may slow down because it cannot hold enough active data/workspace. Students complete a “cause → effect” chart for four statements, e.g., “Many tabs open” and “RAM needs are higher.”

4. 25–45 min · Investigation: Match hardware to workloads (Groups of 3). Teacher hands out four workload cards and a recommendation template. Each group chooses two cards and fills the template:

• workload type (e.g., school research with many tabs; multiplayer gaming; photo editing; basic video editing)
• which hardware matters most (CPU and/or RAM)
• what specification change would help (described in general terms, not brand-specific)
• one justification sentence using “because…”. Students justify choices and share within their group, then submit one group response to the teacher for quick checking.

5. 45–55 min · Whole-class debrief: best-fit reasoning. Teacher selects 2–3 groups to present their reasoning using the template structure. Students give “glow and grow” feedback: one thing that is clear and one question that would strengthen the explanation.

6. 55–60 min · Exit ticket (formative check). Students answer two prompts independently:

• “Explain how RAM affects performance when you run heavy apps.”
• “Choose either CPU or RAM to improve for a given scenario and explain why in one sentence.”

Resources

• Teacher slides with labelled CPU/RAM diagram and scenario cards
• Student worksheet: diagram + cause→effect chart + group recommendation template
• Workload cards (4 scenarios) and a classwork checklist
• Coloured pens/pencils for annotating diagrams
• Device for teacher demo (optional) showing task lag when many apps are open
• Digital tool access for later lessons (optional for today): shared folder location and a simple slide/doc template

Assessment

• Observation during group investigation: check students’ ability to link specifications to performance outcomes
• Quality of group justification sentences (evidence of cause→effect reasoning)
• Exit ticket responses: identify misconceptions (e.g., confusing CPU with RAM, or unclear reasoning)

Differentiation

• Support: provide sentence starters for justifications (e.g., “RAM helps because…”, “I would choose more RAM for…”); offer a partially completed cause→effect chart
• Support: allow students to use a simple “needs more / needs less” scale for CPU and RAM rather than technical terms
• Extension: ask students to rank the importance of CPU vs RAM for each workload and defend the ranking with two reasons
• EAL/SEN considerations: include visual supports (icons for CPU/RAM), reduce writing load by allowing a short bullet response, and ensure clear, consistent terminology across the lesson