Functional Blocks of a Computer (CPU, Memory, I/O) — Explanation + Diagram

Functional Blocks of a Computer (CPU, Memory, I/O) — Explanation + Diagram

Verified Sources
Oct 13, 2026

A general-purpose computer can be understood as a set of functional blocks that cooperate to execute programs: CPU (does computation), Memory (holds programs/data), and I/O subsystem (moves data in/out of the system). This organization is commonly taught using the stored-program concept as a basis for the CPU–memory–I/O relationships. 2

At a conceptual level (e.g., von Neumann-style organization), instructions and data reside in the same main memory, while the CPU fetches instructions and operates on data, and I/O devices interact with the outside world. 2

Key learning terms (block view): CPU, Main memory, Registers, System bus.

Footnotes

  1. Von Neumann architecture - Wikipedia - Describes stored-program idea and the conceptual elements including CPU, memory, and input/output. ↩ ↩2

  2. The Von Neumann stored program concept - BBC Bitesize (Edexcel GCSE Computer Science Revision) - Explains stored-program concept and fetch–decode–execute cycle with CPU internal units. ↩

  3. Von Neumann and the Stored-Program Computer That Enabled Software - Koder.ai - Provides a practical teaching model: CPU + memory + I/O. ↩

Block Diagram of Computer System Explained (Input, CPU, Memory & Output)

1) CPU (Central Processing Unit)

The CPU is the component that executes program instructions. In stored-program operation, the CPU typically performs a repeated cycle: it fetches an instruction from memory, decodes it, and then executes it using internal units such as an ALU and a Control Unit while using registers for immediate operands and intermediate results. 2

Functional responsibilities inside/around the CPU:

  • Fetch-decode-execute control: Coordinated by the control logic; supports correct sequencing of instructions.
  • Computation: Performed by the ALU for arithmetic and logic operations.
  • Temporary working storage: Registers hold addresses/operands and intermediate values to reduce latency compared with main memory.

Pro Tip (diagram interpretation): In your block diagram, imagine data moving to the CPU for processing and results moving back to memory or out to I/O. The CPU is not where data is permanently stored—main memory and storage do that. 2

Footnotes

  1. The Von Neumann stored program concept - BBC Bitesize (Edexcel GCSE Computer Science Revision) - Explains stored-program concept and fetch–decode–execute cycle with CPU internal units. ↩ ↩2 ↩3 ↩4

  2. Computer Organization : CPU, Memory and I/O organization | PPTX (slides) - Outlines CPU components (ALU and control) and block-diagram organization. ↩ ↩2

  3. Von Neumann architecture - Wikipedia - Describes stored-program idea and the conceptual elements including CPU, memory, and input/output. ↩

2) Memory (Primary/Main Storage)

The memory block stores both program instructions and data used by those instructions. In a stored-program model, both are kept in main memory, enabling the machine to change behavior by changing what is stored (i.e., software as data). 2

Common conceptual split:

  • Main memory (primary): Fast, directly accessible storage for currently executing programs and active data (often described as RAM/ROM in introductory texts).
  • Secondary/external storage (not always drawn in a minimal CPU–memory–I/O diagram): Persistent storage such as disks/SSDs for long-term files; accessed through I/O. (Your neat diagram can keep it optional, but it belongs under I/O/storage interactions.)

Why memory is a “functional block”:

  • The CPU must read instructions and operands from memory to execute.
  • Results are often written back to memory so subsequent instructions can use them.

Key learning terms (memory): Main memory, Cache, RAM, ROM.

Footnotes

  1. Von Neumann architecture - Wikipedia - Describes stored-program idea and the conceptual elements including CPU, memory, and input/output. ↩

  2. Von Neumann and the Stored-Program Computer That Enabled Software - Koder.ai - Provides a practical teaching model: CPU + memory + I/O. ↩

  3. Organization & Structure of a Computer System. | NUEL (eLearning book) - Explains memory types (primary/secondary; RAM/ROM) and role of registers/cache. ↩

3) I/O (Input/Output Subsystem)

The I/O subsystem provides the interface between the computer and external devices (the “outside world”). Input devices send data/commands into the computer; output devices present processed results back to users or other systems. 2

Typical examples:

  • Input: keyboard, mouse, sensors, network interface
  • Output: monitor, printer, speakers, actuators

The I/O subsystem transfers information between:

  • external devices
  • memory (where CPU processing happens)
  • CPU (indirectly via memory and control paths)

Because I/O devices can be slower than the CPU, common data transfer modes exist, including:

  • Programmed I/O (CPU explicitly checks/controls transfers)
  • Interrupt-driven I/O (CPU is notified when ready)
  • DMA (Direct Memory Access), where a controller transfers blocks directly between I/O and memory, reducing CPU involvement.

Warning (common misconception): I/O devices do not “compute” like the CPU. They move data—computation is performed by the CPU/ALU over data stored in memory. Transfer methods (interrupts/DMA) exist to manage speed mismatches and CPU overhead.

Footnotes

  1. Von Neumann architecture - Wikipedia - Describes stored-program idea and the conceptual elements including CPU, memory, and input/output. ↩

  2. The Von Neumann stored program concept - BBC Bitesize (Edexcel GCSE Computer Science Revision) - Explains stored-program concept and fetch–decode–execute cycle with CPU internal units. ↩

  3. I/O Interface (Interrupt and DMA Mode) - GeeksforGeeks - Describes programmed I/O, interrupt-initiated I/O, and DMA and their purpose. ↩ ↩2

How blocks work together (fetch–process–communicate)

  1. 1
    Step 1

    Instructions and required data reside in main memory, ready for the CPU to access.

  2. 2
    Step 2

    The CPU reads the next instruction from memory (via control logic and internal registers).

  3. 3
    Step 3

    Control Unit directs the operation; ALU performs arithmetic/logic; results are prepared for storage or further steps.

  4. 4
    Step 4

    Operands are obtained from memory and results are written back so later instructions can use them.

  5. 5
    Step 5

    Input devices send data through the I/O subsystem into memory; output devices receive processed results from memory.

Functional-block roles (what each block primarily does)

Relative emphasis in a minimal block-diagram model: CPU computes, Memory stores, I/O communicates with external devices.

Lifecycle of an instruction in the CPU–Memory–I/O model

Data & instructions in Memory

1. Ready state

Main memory holds the program and active data."

CPU fetch

2. Instruction begins

CPU retrieves the next instruction from memory."

CPU decode

3. Instruction interpretation

Control unit interprets what action the instruction requests."

CPU execute + write-back

4. Computation & storage

ALU computes; results are written to memory or prepared for output."

I/O transfers

5. External interaction (as needed)

Input updates memory; output sends results from memory."

Common exam-style questions

Input → I/O → Memory ↔ CPU → Memory → I/O → Output

Knowledge Check

Question 1 of 4
Q1Single choice

In a functional block model (CPU, Memory, I/O), what does the CPU primarily do?

Explore Related Topics

1

Virtual Memory, Its Implementation, and the Role of the TLB

Virtual memory abstracts physical RAM by giving each process a large contiguous logical address space, implemented with paging, page tables, and a Translation Lookaside Buffer (TLB) that caches recent translations.

  • Provides protection, simplifies programming, enables demand paging and sharing of code/pages.
  • Virtual address = (VPN, offset); physical address = (PFN, offset) with VPN → PFN via TLB or page‑table walk.
  • Effective access time: EAT=α(m+ϵ)+(1−α)(2m+ϵ)EAT = \alpha (m+\epsilon) + (1-\alpha)(2m+\epsilon), so high TLB hit rate α\alpha is critical.
  • Multi‑level page tables reduce memory use for sparse address spaces.
  • TLB reach = (entries) × (page size); exceeding it causes TLB thrashing and performance loss.
2

Which Component Is the Brain of a Microcomputer System?

The microprocessor is the brain of a microcomputer because it executes instructions, controls operations, and incorporates the ALU, control unit, and registers.

  • It combines all CPU functions on one chip, unlike RAM (volatile workspace) or ROM (permanent storage).
  • The ALU only performs arithmetic/logic and cannot direct the whole system.
  • Formula: Microcomputer Brain=Instruction Control+Execution+Coordination\text{Microcomputer Brain} = \text{Instruction Control} + \text{Execution} + \text{Coordination}
  • Exam strategy: discard memory components and sub‑units, leaving the microprocessor as the correct choice.
3

Organization of a Natural Language Understanding (NLU) System: Diagrammed Architecture