levo

Data Structures: Arrays, Records and Hash Tables

Choosing and justifying a data structure

  • 3 things to know
  • Component 1

Overview

The questions that settle it — how the data is reached, whether the size is known, what order items must leave in — worked through for stacks, queues, arrays, linked lists and hash tables.

What you need to know

Answer each one before you reveal it.

Your recallNot started
Key term

What questions decide which data structure suits a problem?

Process

Which structure suits data that must be processed last in, first out?

Process

Which structure suits data that must be processed in order of arrival?

Questions from this subtopic

Each one with the model answer underneath.

  1. 1

    What questions decide which data structure suits a problem?

    Model answer

    The choice depends on the operations needed, the order the data must keep and whether the size changes. Speed of access and memory use are then compared.

  2. 2

    Which structure suits data that must be processed last in, first out?

    Model answer

    A stack suits last in, first out processing. An undo facility and the return addresses of subroutines both use one.

  3. 3

    Which structure suits data that must be processed in order of arrival?

    Model answer

    A queue suits first in, first out processing. A printer spooler holds waiting jobs in a queue.

  4. 4

    Justify a linked list for a list whose contents change constantly.

    Model answer

    A linked list inserts and deletes by changing pointers rather than shifting data. The list also grows and shrinks as memory allows.

  5. 5

    Justify an array for a fixed table of twelve monthly totals.

    Model answer

    An array of twelve elements holds all the totals under one identifier. The month number gives direct access to any total.

  6. 6

    Which structure suits hierarchical data such as a family tree?

    Model answer

    A tree suits hierarchical data because each node may have child nodes. The relationships are held by the structure itself.

Other ways to work this

The same content, four other ways.

What is inside Levo

Six ways to work the same material.

1Closed book
2Open book
3Closed book

The 3-step method, run for you

Answer cold, learn it, then prove it stuck. Levo tracks the jump between your first attempt and your last.

Data Structures: Arrays, Records and Hash Tables
Stacks, Queues, Linked Lists and Trees
Boolean Logic and Simplification
Algorithms, Pseudo-Code and Programming Constructs

Cram a whole paper in one sitting

Sort every topic into what you know and what you do not, then drill only the weak ones.

KDW to HAT.
decryptsencryptscompresses

Blank Blitz makes facts automatic

Rapid timed gap-fills on the terms and numbers you need to recall without thinking.

AThe two are not the same.
BOpen source refers to the availability of the code.
CMuch open source software is free of charge.

Build It gets the exam shape right

Assemble a full-mark answer from its marking points, in the order an examiner wants them.

Backup means the copy of the data.
TrueFalse

Test It catches misconceptions

Spot the fault in a statement. The traps are the mistakes students actually make.

721941163128510

Brain Breaks between sessions

Short focus games to reset attention, so the next set lands better than the last.

Every question in Data Structures: Arrays, Records and Hash Tables, on a schedule.

Attempt a question from memory, write the correct version, then attempt it again. Levo records the jump between your first attempt and your last, and brings each question back on the day you are due to forget it.

Or £46 a year, about £3.83 a month. Cancel anytime.