Flowchart
Also known as: flow diagram, process diagram
A visual diagram that represents the steps of an algorithm using standard shapes (ovals for start/end, rectangles for processes, diamonds for decisions, arrows for flow). Flowcharts help plan programs, document processes, and communicate algorithms to non-programmers.
💡 Intuition
A flowchart is a map of your algorithm — you can trace the path from start to finish and see every decision point along the way.
Core Idea
Flowcharts make control flow visible. They're especially useful for understanding loops and branching logic.
🔬 Example
🎯 Why It Matters
Flowcharts help plan programs, document processes, and communicate algorithms to non-programmers.
⚠️ Common Confusion
Diamonds are for decisions (yes/no questions) only. Rectangles are for actions/processes.
Related Concepts
Prerequisites
Next Steps
How Flowchart Connects to Other Ideas
To understand flowchart, you should first be comfortable with pseudocode and algorithm. Once you have a solid grasp of flowchart, you can move on to design specification.
Go Deeper
Frequently Asked Questions
What is Flowchart in CS Thinking?
A visual diagram that represents the steps of an algorithm using standard shapes (ovals for start/end, rectangles for processes, diamonds for decisions, arrows for flow).
Why is Flowchart important?
Flowcharts help plan programs, document processes, and communicate algorithms to non-programmers.
What do students usually get wrong about Flowchart?
Diamonds are for decisions (yes/no questions) only. Rectangles are for actions/processes.
What should I learn before Flowchart?
Before studying Flowchart, you should understand: pseudocode, algorithm.