Turning a structure diagram into a main flowchart and sub-flowcharts
A flowchart that calls each sub-problem from the structure diagram with a subroutine symbol. Each sub-problem then gets its own separate flowchart.
Understanding Turning a structure diagram into a main flowchart and sub-flowcharts in IGCSE Computer Science Paper 2
What it does: Each bottom-level box is a sub-problem, so each one is drawn as a separate flowchart with the same name as its box. The main flowchart uses a subroutine symbol for each call. A diamond is only for decisions. Using the same names links the flowcharts to the structure diagram, so nothing gets lost.
Common mistakes: In the main flowchart every bottom-level box from the structure diagram is called with the subroutine symbol (a rectangle with double side lines). A plain process rectangle is wrong, so line 3 should be [| MarkAnswers |]. The sub-flowchart for the GetMarks box must finish with an end terminator. Line 4 should be ( END ), not a second start.
Free printable worksheet with full answer key — or add this module to a class and your students practise it interactively.
This module's key terms are also in a printable crossword (Modules 123–134) and word search (Modules 123–145).
Take this worksheet further — free with Cloodit
Each concept is reinforced from every angle — learned, then applied, then tested.
Cloodit turns curriculum-aligned coding content into journeys students work through one biome at a time.
Over 100 of them, across seven natural biomes.
Turns their work into revision material ready for Flash Cards and Exam study.
Live, competitive practice for the start of the lesson or a teacher-led lesson finisher.
Honour your top performers, or encourage a student who's trying hard — ready to print in seconds.
Quick Questions
Match the Pairs
Key Term
main flowchartFill in the Blanks
Spot the Error
Student with a class code? Join your class →