The stored-program idea is the strength of the von Neumann design and also the cause of its main limit. Students draw the von Neumann block diagram in Unit 2, and this one idea joins that diagram to Unit 5 and Unit 13.
The idea is that the program sits in the same memory as its data. The Teachers' Guide says it in one line: "The program is stored in the memory" (Teachers' Guide 2.3, page 67) (ගුරු අත්පොත 2.3, පිටුව 73). The Sinhala Guide writes "පරිගණක වැඩසටහන තැන්පත් වන්නේ පරිගණක මතකයෙහි ය", and the Sinhala syllabus calls the idea "ආචිත ක්රමලේඛ සංකල්පය" (විෂය නිර්දේශය 2.3, පිටුව 9). Before this idea, ENIAC needed new cables for each new program.
The strength shows in the OS lesson. The OS loads a program into memory, and the program in execution is a process. The Process Control Block (PCB) keeps the program counter of each process, so the OS can stop a process and start it again (Teachers' Guide 5.3, page 136) (ගුරු අත්පොත 5.3, පිටුව 147). The Sinhala Guide calls the PCB "ක්රියායන පාලන ඛණ්ඩය" and the program counter "වැඩසටහන් ගණකය".
The limit comes from the same shared memory. Instructions and data use one path to the CPU, the buses, and that path carries one word at a time. In 1977, John Backus called this path the "von Neumann bottleneck" (Backus, 1978). Caches, pipelines and multi-core chips hide the bottleneck, but they do not remove it.
This limit is the reason that Unit 13 asks students to predict "the technologies beyond von-Neumann computers" (Syllabus 13.3, page 49) (විෂය නිර්දේශය 13.3, පිටුව 47). The Sinhala syllabus says "වොන් නියුමාන් පරිගණකයෙන් ඔබ්බට". Quantum computing and nature-inspired computing make sense only after students see the limit.
Learn the three units as one idea: the stored program gives the OS its processes and gives Unit 13 its reason. The history, the OS links and the newer research are in an Explained post. Read it, then try the Unit 2 card.
