SS 3 Third Term

Lesson objectives

By the end of the lesson sequence, learners should be able to:

1. Define the central concepts and use precise technical vocabulary.
2. Explain the relevant components, models, processes or principles.
3. Analyse, compare, calculate, design or justify solutions using appropriate criteria.
4. Apply the concepts in a practical task and produce inspectable evidence.
5. Test or review their work, identify limitations and explain safe, ethical or secure practice where relevant.

Key vocabulary

• Hardware: the physical components of a computer system.
• Software: the programs and data that run on hardware.
• Data representation: how numbers, text and other data are encoded for processing.
• Binary coded decimal (BCD): a binary code for decimal digits.
• Overflow: when a calculation exceeds the storage capacity.
• Underflow: when a calculation produces a value below the minimum representable.

Common misconceptions

• "More bits always mean faster processing." Additional bits increase range or precision, not speed.
• "Overflow cannot happen in modern systems." It can, if bounds are not checked.
• "Software has no impact on hardware performance." Inefficient code can bottleneck even powerful hardware.

Teacher activities

1. Open with a diagnostic/retrieval task linked to prerequisite knowledge.
2. Present objectives, technical vocabulary and the problem or use case.
3. Teach through concise explanation, annotated diagrams, worked examples and live demonstrations.
4. Model the expected reasoning or technical workflow, including common failure cases.
5. Set guided practice and then an independent or team task; monitor progress and provide targeted feedback.
6. Facilitate peer review, question learners on design decisions and consolidate the lesson.

Student activities

1. Complete the starter and identify gaps in prerequisite knowledge.
2. Annotate notes, diagrams, code, tables or process models.
3. Explain a concept or predict the outcome of a worked example.
4. Complete the practical/problem-solving task and document the steps taken.
5. Test results with more than one example where appropriate; debug or revise errors.
6. Present or submit the output and reflect on quality, limitations and responsible use.

Practical / learning evidence

Produce a topic-appropriate artefact such as a labelled architecture/network diagram, algorithm, flowchart, pseudocode, tested program, database schema/query, web page, spreadsheet, graphics design, security policy, project document or structured written analysis. The teacher must define the precise task, constraints and success criteria.

Resources and preparation

Computers/devices, required software or development environment, projector, sample datasets, notes and reliable power. Prepare test data and an offline route where possible. Use fictional or anonymised data; do not expose personal learner information in demonstrations.

Assessment for learning

Assess conceptual precision, reasoning, technical correctness, test coverage, safe/ethical practice, documentation and ability to justify decisions. Use questioning, code/output inspection, practical demonstration, short written analysis and peer review. Record misconceptions and reteaching needs.

Inclusion and extension

Provide scaffolded examples, reference sheets, accessible formats and structured roles for group tasks. Extend advanced learners with edge cases, larger datasets, performance/security considerations or alternative solution designs. Avoid assuming equal access to devices or connectivity outside school.