The big idea: A flow diagram models what a programmable system DOES, using a small set of fixed symbols: a rounded box for start and stop, a parallelogram for input and output, a rectangle for a process, and a diamond for a decision.
A monitoring program must loop back, or it reads its sensor once and stops for ever.
The four symbols, then a complete automatic-light program drawn with them.
Interactive diagram
Explore the labelled diagram, charts and maps for this topic in full study mode.
Free preview
This is the free notes preview
You're reading the free notes. Aimnova Pro unlocks the full study experience — and you can try it with your first topic free to keep:
- FlashcardsLock in vocabulary and key terms with spaced repetition.
- Practice questionsAnswer exam-style questions and get instant AI marking.
- Mock exams & past-paper vaultSit full mocks and see exactly how examiners award marks.
- Personalised study planA daily plan built around your exam date and weak areas.
| Symbol | Shape | Rule |
|---|---|---|
| Terminal | A rounded box | START at the top; a STOP only if the program actually ends. A control program that runs for ever has no stop symbol |
| Input / output | A parallelogram | Reading a sensor or sending a value to an output device. Name the device, not the quantity |
| Process | A rectangle | Something the program does: set a variable, wait, switch something on |
| Decision | A diamond | A question with exactly TWO outputs, both labelled — YES and NO. Three lines out of a diamond is always wrong |
| Flow line | An arrow | Every path must lead somewhere, and the loop back is what makes it a control program |
The three mistakes examiners see: No loop back, so the program runs once. An unlabelled decision, so a reader cannot tell which path is which. And a path that goes nowhere, leaving the program with no defined behaviour on one branch.
Get feedback like a real examiner
Submit your answers and get instant feedback — what you did well, what's missing, and exactly what to write to score full marks.
From a requirement to a diagram
Write the requirement as a sentence
"Switch the lamp on when it is dark, off when it is light, and do not flicker at dusk." Everything in the diagram comes from that sentence.
Find the decision
Usually one question with two answers. If there are two questions, there are two diamonds — not one with three outputs.
Add what stops it misbehaving
A dead band so the lamp does not flicker at the threshold, and a delay so a passing headlight does not trigger it. Both are extra boxes, not extra components.
Close the loop
Every branch returns to the read step, so the system keeps monitoring for as long as it has power.
How this is tested — constructing flow diagrams to model a programmable system. It comes up two ways:
Paper 1 — multiple choice
- Identify the symbol used for a stated step.
- Find the error in a given flow diagram.
Paper 2 — analysing a product
- Construct a flow diagram for a described control system.
- Explain what a given flow diagram does.
The trap: Leaving out the loop back. A monitoring program that does not return to the read step has checked once and stopped.
Construct a flow diagram for a greenhouse vent that opens when the temperature rises above 25 °C and closes below 22 °C.
Model answer plan
See the mark-by-mark plan — for / against / judgement, with marking guidance — in study mode.