Algorithms can be represented in several ways before they are coded. The AQA 8525 specification requires you to understand and use flowcharts and pseudo-code. Both are ways of expressing the logic of an algorithm without tying it to a specific programming language.
A flowchart is a diagram that uses standard shapes connected by arrows to show the steps and decisions in an algorithm. Arrows show the flow of control — the order in which steps are executed.
| Shape | Name | Used for |
|---|---|---|
| Oval | Terminator | Start and End of the algorithm |
| Rectangle | Process | A calculation or action, e.g. x ← x + 1 |
| Parallelogram | Input / Output | Reading input from a user or displaying output |
| Diamond | Decision | A yes/no question — creates two branches |
| Rectangle+ | Subroutine | A call to a named subroutine (sub-program) |
START → Input number → Is number > 0? → Yes: Output "Positive" → END; No: Output "Not positive" → END
Pseudo-code is a structured way of writing algorithm steps using English-like statements and programming constructs (variables, loops, conditions) without the exact syntax of any real language. AQA provides its own pseudo-code notation that you must learn.
A trace table is a way of manually working through an algorithm step by step, recording how the values of variables change at each stage. They are used to:
| Step | i | total | OUTPUT |
|---|---|---|---|
| Start | – | 0 | – |
| i = 1 | 1 | 1 | – |
| i = 2 | 2 | 3 | – |
| i = 3 | 3 | 6 | – |
| End | – | – | 6 |
| Flowcharts | Pseudo-code |
|---|---|
| Visual — good for seeing flow of control | Textual — closer to real code |
| Easy to follow for non-programmers | Better for complex algorithms |
| Standard shapes everyone recognises | More compact for long algorithms |
| Harder to write loops with many iterations | Loops and conditions are easy to write |
8 AQA-style questions · 19 marks total · AI will mark your answers and give feedback
| Term | Definition |
|---|
Timed exam conditions. No feedback until you submit.