Learn

Architecture & pattern guides

Read the idea, build it on a Grid, prove it in a challenge. Short, practical guides — illustrated with RodGrid's own nodes — on system design, design patterns, flow modeling, and how to get the most out of the app.

All articles

Flowchart basics: start, process, end

What a flowchart says that a paragraph can leave out, the four shapes of a straight run of steps, and why a path that finishes needs an explicit End.

What a paragraph lets you leave out

A flowchart answers two questions that a paragraph can leave open: after this step, what happens next, and where does this path finish? Take a museum's ticket kiosk, described the way it would be in a meeting: "The kiosk takes the visitor's choice, charges the card and prints the ticket." Everyone nods. Nobody has said what happens when the card is declined, because the sentence reads just as well without it. A flowchart models the same procedure as connected steps, and there a gap has a shape: a step with no line leaving it, a path that stops halfway down the page.

Four shapes are enough to begin. Start is where the flow begins, and the flows in these articles have a single one. Process is a step that does work. Input/Output is data crossing the flow's boundary, in either direction. End is where a path finishes. The connections between them carry one meaning, order: an edge from one step to another says the second happens after the first.

The kiosk, straight through

A tap starts the flow. The choice comes in and the ticket goes out, so both are Input/Output, and charging the card is Process. Data, documents & manual input covers the narrower shapes for a person typing and for a generated document.

How big is one box?

The whole kiosk could be a single Process called Sell ticket. That is true, and it stops being useful the day a visitor says they paid and got nothing, because one box cannot show that the charge comes before the print. With separate steps you can point at the problem, a printer that jams after a successful charge, and Error handling & error boundaries covers drawing what the kiosk does then. Split a box when a reader needs to see the order of what it does or tell its outcomes apart: Sell ticket hides both, and Charge card and Print ticket show them.

A path that just stops

A declined card opens a second path, through a question that Decisions & branching teaches, and that path has to reach an End as much as the first one does. Leave it off because the flow "obviously" finishes, and a box with an unused output could mean the flow is over or that the author stopped drawing. In a procedure that finishes, every path has to reach an explicit End, including the error paths, though several paths can share one.

One way into a step

A plain step takes one incoming connection, so you cannot wire two edges into it to mean "either path continues here": the Grid refuses the second. That single-input rule is why loops and converging paths need a Merge or a junction in front of the shared step. Merge & path convergence explains it, and Loops & retries draws the loop. The limits are fixed per node:

NoteIn RodGrid each logical node accepts at most one incoming connection, except End (many), the junctions Merge / Or / Summing Junction (up to four) and the Parallel Gateway (up to three, the AND-join); Start takes none.

Your first flow: a login

The User Login Flow challenge is the kiosk's shape with one fork in it: read a username and password, check them, then grant access or show an error, in at most eight nodes. Spend your attention on one thing: every path, success and failure, reaches an explicit End, and no node is left dangling with an unused output. The new part is the one Decision it needs, which the next article teaches. If you try the Challenge first, treat that Decision as a box with two exits, yes and no.

Practice this