Understand the concept of data structures. It may be helpful to set the…

The idea

A data structure is an organised way of storing related data so that it can be found, changed and processed efficiently. The concept matters because the same values can be arranged in different structures, and the arrangement affects how easily you can search, insert or remove items. Familiar contexts help: a queue of people at a till behaves first-in-first-out, a stack of plates behaves last-in-first-out, and a record can group a student's name, age and score together. In a practical setting, choosing a structure shapes the algorithm you write: an array suits a fixed list of scores you index by position, whereas a queue suits print jobs arriving in order. Understanding the concept means recognising what a structure stores, how items are added and accessed, and why one structure suits a task better than another.

What earns the marks

• Defines a data structure as an organised way of storing and relating data so it can be accessed and processed.
• Explains that the arrangement of data affects how easily items can be searched, inserted or removed.
• Recognises a familiar example, such as a queue (first-in-first-out) or a stack (last-in-first-out), and describes its behaviour.
• Explains how a chosen structure suits a practical task, for example an array for a fixed list of scores accessed by index.
• Distinguishes between structures by how items are added and retrieved rather than by the values they hold.

Common mistakes and how to put them right

• Treating a data structure as just any collection of variables.

  Put it right by stressing that a structure organises related data and defines how it is accessed.

• Assuming all structures behave the same way.

  Put it right by contrasting a queue's first-in-first-out order with a stack's last-in-first-out order.

• Thinking the concept is only abstract theory.

  Put it right by linking each structure to a practical task such as storing scores or managing print jobs.

Exam tips

• Read the question to identify whether it asks what a structure is, how it behaves, or why it suits a task, and answer that specific point.
• Use a concrete familiar example to anchor your reasoning rather than a vague description.
• When comparing structures, state the access or ordering rule that differs, not just the name of each structure.