Year 6 Computing

Chapters to explore

An algorithm should work for ordinary inputs and important edge cases. Boundary values sit at the edge of a rule, such as the minimum age in a fictional game. Trace the exact comparison and predict its result. A clear test table records input, expected output and actual output.

Try it: Write an input rule, then make a table with ordinary, boundary and outside values.

Networked systems send information through connected devices using agreed rules. Large messages may be divided into packets and reassembled. A delay or lost connection can affect delivery. The internet supports different services; understanding a simplified route helps explain why a local device is only one part of the system.

Try it: Model a message as numbered paper pieces and explain why the receiver must reconstruct it.

Data analysis looks for patterns while checking quality and limits. Missing values, inconsistent units or a biased sample can mislead. A pattern does not by itself prove that one thing causes another. Use clear labels and explain what the data can and cannot support.

Try it: Analyse a small fictional dataset and write one supported conclusion and one limitation.

Digital images, audio and text can be edited or generated. A realistic appearance does not prove that an event happened. AI systems can produce plausible mistakes. Check important claims using reliable evidence, protect private information, and explain when generated material is being used.

Try it: With an adult, compare a labelled fictional image and a documented real image. Discuss what supports each description.

Responsible publishing considers permission, privacy and accuracy. Credit acknowledges a creator, while permission determines whether a use is allowed. Check the terms attached to a resource with an adult. Do not assume something can be copied simply because it is online. Correct mistakes openly and respectfully.

Try it: Make a source list for a project using your own work and clearly permitted resources.

A programming project begins with a goal and success criteria. Decompose the task, plan the algorithm, build a version and test it with varied inputs. Record problems and improvements. Explain the program so another person can understand its behaviour and limitations.

Try it: Design a small paper or block-code program with three criteria, a test table and a short explanation.

Digital systems commonly represent information using bits with two states, written 0 and 1. Groups of bits can encode different kinds of data using agreed conventions. The same pattern needs a context to interpret it. This lesson models representation without claiming a bit is literally a written digit inside every device.

Try it: Invent a four-symbol code using two-bit patterns.

A display should suit the question and data. Check labels, units, missing values and scale. A truncated axis can exaggerate visual differences. Explain sample limits and avoid identifying people through unnecessary personal data.

Try it: Redraw a fictional chart with clear labels and an explained scale.

Documentation explains purpose, controls, data and known limitations. Another person should be able to try the project without guessing. Include test results and credit resources. A handover can reveal unclear instructions even when the program itself works.

Try it: Write a short guide for a paper or digital project.

Learning together

Each chapter brings together teaching, an example, practice and a practical discovery. Use the material with discussion and suitable offline activities. Choose a comfortable starting point and revisit explanations as needed.