Understanding instead of memorization
Students repeatedly connect formal concepts to observable behaviour.
Abstraction–Realization Cycle
From abstraction to working systems — and back again.
Technical understanding becomes powerful when ideas can move freely between equations, models, simulations, experiments, and real systems. The Abstraction–Realization Cycle structures learning around this movement.
Abstract → Realize → Observe → Reflect → Refine
01 · The cycle
Each stage produces something the next one can act on: a structure, an executable artefact, a measurement, a judgement, a revision.
02 · Why ARC
Students repeatedly connect formal concepts to observable behaviour.
Equations, algorithms, simulation, hardware, and experiments become different representations of the same problem.
Unexpected behaviour becomes evidence that helps refine the abstraction rather than merely producing a wrong answer.
03 · One tiny example
The point is not merely to obtain the correct controller. The point is to understand why it works.
04 · In a course
| Traditional element | ARC interpretation |
|---|---|
| Lecture | Abstraction |
| Exercise | Formal realization |
| Simulation | Executable realization |
| Laboratory | Physical realization |
| Measurement | Observation |
| Discussion | Reflection |
| Project iteration | Refinement |
ARC treats theory and practice as parts of the same loop. Each realization tests an abstraction. Each observation improves the next one.
See ARC-based coursesUnigaku · Abstraction–Realization Cycle