Knowledge Organiser: Pseudocode and Flowcharts
Part of Pseudocode & Flowcharts · GCSE GCSE Computer Science revision
This topic summary covers Knowledge Organiser: Pseudocode and Flowcharts within Pseudocode & Flowcharts for GCSE Computer Science. Revise Pseudocode & Flowcharts in Algorithms for GCSE Computer Science with 15 exam-style questions and 8 flashcards. This is a high-frequency topic, so it is worth revising until the explanation feels precise and repeatable. It is section 9 of 9 in this topic. Use this topic summary to connect the idea to the wider topic before moving on to questions and flashcards.
Topic position
Section 9 of 9
Practice
15 questions
Recall
8 flashcards
Knowledge Organiser: Pseudocode and Flowcharts
Key Terms
- Pseudocode: An informal, language-independent way of describing an algorithm using plain English-like statements
- Flowchart: A diagram using standard symbols to represent the steps and flow of an algorithm
- Oval/Terminator: Start or End of the flowchart
- Parallelogram: Input or Output operation
- Rectangle: Process or calculation step
- Diamond: Decision point with Yes/No branches
Must-Know Facts
- Flowchart symbol mnemonic — OPRD: Oval (start/end), Parallelogram (I/O), Rectangle (process), Diamond (decision)
- Decision diamonds MUST have Yes and No labels on their outgoing arrows
- Loops in flowcharts show an arrow pointing back to an earlier step
- Pseudocode uses: if…then…elseif…else…endif; for…next; while…endwhile
- Every opening keyword needs a closing keyword (IF→ENDIF, FOR→NEXT, WHILE→ENDWHILE)
- Pseudocode is not run on a computer — it communicates logic to any programmer
Key Concepts
- Flowchart: always start at START oval, follow arrows, evaluate diamonds (Yes/No), end at END oval
- Pseudocode structure keywords: IF/THEN/ELSEIF/ELSE/ENDIF — FOR/NEXT — WHILE/ENDWHILE
- Assignment: variable = value; Input: variable = input("prompt"); Output: print(value)
- Indentation inside loops and conditions makes pseudocode clearer
Common Mistakes
- Using the wrong flowchart symbol: Rectangles = process/calculation; Parallelograms = input/output; Diamonds = decisions; Ovals = start/end — mixing these up loses marks
- Not labelling decision diamond branches: Both outgoing arrows from a diamond MUST be labelled Yes and No (or True/False) — unlabelled branches make the logic ambiguous
- Writing pseudocode without closing keywords: Every IF needs ENDIF, every FOR needs NEXT, every WHILE needs ENDWHILE — missing closing keywords is penalised
- Not indenting pseudocode inside loops and conditions: Indentation is required to show the structure — unindented pseudocode is harder to read and loses presentation marks
- Confusing pseudocode with actual Python/Java syntax: Pseudocode is language-independent — using language-specific syntax (e.g. Python's
print()ordef) in a pseudocode answer may not be credited
Revise this topic interactively on PrepWise — self-test mode, tap-to-reveal definitions, and Common Mistakes from examiners.
Try the interactive Knowledge Organiser — free →