Specs and Performance

Overview

This lesson compares common hardware specifications and how they affect performance for different computing tasks. It builds directly from lesson 1 in the unit by moving from “what components are” to “how specifications change what you can do well.”

Learning intentions

• Students will explain how hardware specifications affect the speed and capability of a digital system.
• Students will identify which specifications matter most for specific tasks (e.g., gaming, multimedia, AI training).
• Students will justify a hardware choice using evidence from simple comparisons and test results.

Success criteria

• I can describe how at least three hardware specifications (e.g., clock speed, cores, RAM/storage size) can change performance.
• I can match a set of hardware specifications to a realistic task and explain why it fits.
• I can use data from a comparison task to support my hardware recommendation.

Curriculum links

• Digital Technologies: AC9TDI8K01 — explain how hardware specifications affect performance and select appropriate hardware for particular tasks and workloads.
• Digital Technologies: AC9TDI8K01_E1 — connect specifications to task performance (e.g., bandwidth/latency examples and RAM needs for multimedia authoring).
• Digital Technologies: AC9TDI8K01_E2 — select appropriate hardware for tasks (e.g., stronger graphics for gaming; more storage for video editing).
• Digital Technologies: AC9TDI8P11 — use digital tools efficiently to create and present comparisons with appropriate conventions.

Lesson structure (60 minutes)

1. 0–5 min · Hook (scenario). Teacher presents two short device stories: one has high clock speed but low RAM; the other has fewer cores but much more RAM. Students think-pair-share: “Which device is likely to feel faster for a school multimedia task and why?”

2. 5–15 min · Direct teach (specs → performance). Teacher models a “specification to performance” chain using three anchor ideas:

• Clock speed: affects how quickly a core can perform operations (use the phrase “helps, but isn’t the whole story”).
• Cores: parallel work capacity (more cores can help multitasking or workloads that split across cores).
• RAM size: how much data/programs can be held near the CPU for quick access (more RAM reduces slowdowns like stuttering or swapping). Students take guided notes in a table with columns: Specification, What it affects, Simple example.

3. 15–25 min · Micro-investigation (task cards). In small groups of 3, students receive task cards (e.g., “record and edit short video”, “run several apps while researching”, “play a graphic-heavy game”, “open many browser tabs and documents”). Each group chooses the 2–3 most relevant specifications from a class list (clock speed, cores, RAM, storage type/size, graphics capability if included) and writes a one-sentence justification. Teacher circulates, prompting groups to connect their reasons to “performance during the task,” not brand preference.

4. 25–40 min · Data comparison (guided example). Teacher runs a quick, age-appropriate demo using classroom devices or a projector: open a heavy resource scenario (for example, launching an editing project or switching between resource-heavy apps) and record observable differences (load time, responsiveness, ability to multitask). If full hardware comparison isn’t possible, use teacher-prepared result cards that show realistic patterns (e.g., Device A loads quickly but crashes during switching; Device B loads slower but remains responsive due to more RAM). Students complete a “claim–evidence–reasoning” sheet:

• Claim: which specification likely explains the result
• Evidence: what was observed
• Reasoning: link to how the specification affects performance

5. 40–55 min · Hardware recommendation (apply and justify). Individually, students choose a hardware profile for a given “real life” need (teacher assigns two or three options to reduce copying). Profiles include different combinations of specifications (e.g., higher cores + moderate RAM vs moderate clock speed + high RAM). Students write a short recommendation (6–8 sentences) that must include:

• The task/workload
• The top 2–3 specifications that matter most
• A justification tied to performance outcomes
• One limitation or trade-off (e.g., “fewer cores may reduce performance in parallel workloads”)

6. 55–60 min · Exit ticket (check understanding). Students answer: “Name one specification that improves performance for your chosen task and explain why.” Teacher collects for quick review.

Resources

• Task cards (printed), group question prompts
• Guided notes table (print or digital)
• “Claim–evidence–reasoning” worksheet
• Hardware profile cards with specification combinations
• Device demo setup (or teacher-prepared result cards if needed)
• Exit ticket slips
• Laptops/tablets only if available for quick recording or writing

Assessment

• Formative: teacher listens to group justifications during the task-card discussion (check for “specification → performance” links).
• Formative: review the claim–evidence–reasoning sheets for correct use of evidence and explanations.
• Summative for this lesson (lightweight): exit ticket showing a clear specification-to-task performance explanation.

Differentiation

• Support: sentence starters for justification (e.g., “This specification matters because…”, “The result likely happened due to…”).
• Support: provide a word bank (clock speed, cores, RAM, storage, responsiveness, load time, multitasking).
• Extension: challenge students to add a trade-off (e.g., “Why might a higher clock speed not solve RAM-related lag?”) or to rank the specifications by importance and explain their ranking.
• EAL/SEN: allow oral rehearsal of the recommendation with a partner before writing; reduce writing length while maintaining the required elements (task, key specs, justification, trade-off).