Big picture
A computer system turns input into useful output by executing instructions stored in memory. When a student opens a recorded lesson, the processor, memory, storage, display, operating system and application cooperate; no single component explains the entire experience.
Understanding this cooperation helps you choose suitable equipment, diagnose delays and answer comparison questions precisely. A large storage drive cannot substitute for working memory, just as a fast processor cannot recover an unsaved document after a power failure. This chapter follows information through the system and connects each component to its purpose.
Learning goals
Explain the input–process–output model with storage.
Distinguish CPU components and their roles.
Compare volatile memory and persistent storage.
Calculate storage using explicit bit and byte units.
Classify software and explain operating-system services.
Core ideas
1. Hardware, software and the stored-program idea
Hardware is the physical equipment; software is the set of programs that tells it what to do. A keyboard is hardware, while a text editor is software. Data are representations such as attendance entries; processing can turn them into information such as a monthly attendance summary. The distinction depends on use: that summary may itself become input to another calculation.
In a stored-program computer, instructions and data are held in memory. A block diagram can be described as input devices feeding main memory, with the CPU exchanging instructions and data with memory, output devices presenting results, and secondary storage retaining files. Arrows indicate transfers rather than a compulsory one-way journey: an edited document may move repeatedly between memory and storage.
2. CPU organisation and instruction execution
The central processing unit contains an arithmetic and logic unit, control unit and registers. The ALU performs arithmetic and comparisons. The control unit coordinates operations; it does not itself perform every addition. Registers hold small amounts of immediately needed information inside the processor.
During a simplified fetch–decode–execute cycle, the processor fetches an instruction from memory, decodes its meaning, executes it and stores the result as needed. For an addition, operands reach registers, the ALU adds them, and the result can be written back. The clock coordinates operations, but clock frequency alone does not determine performance: architecture, number of cores, memory access and workload also matter. Do not claim that every instruction necessarily takes exactly one clock tick.
3. Memory hierarchy and volatility
A memory hierarchy balances speed, capacity and cost. Registers are closest to execution, followed broadly by cache, main memory and secondary storage. Cache keeps frequently or recently used instructions and data near the processor, reducing slower memory accesses. A larger cache can help some workloads, but no capacity guarantees that every requested item is present.
RAM provides working space and is normally volatile: its contents disappear when power is lost. ROM is non-volatile and holds firmware; modern firmware may use electrically rewritable memory. Secondary storage such as an SSD retains files without continuous power. Saving a document copies its useful state to persistent storage; merely seeing it on the screen does not prove that it has been saved.
4. Units and a worked storage calculation
A bit represents one binary digit. A byte contains eight bits. Distinguish a quantity in bits from a quantity in bytes before calculating. Binary prefixes use powers of two, while decimal prefixes use powers of ten; textbooks sometimes use KB loosely, so state the convention in an answer.
Unit | Exact size | Example use |
|---|---|---|
B | 8 bits | A byte count |
KiB | 1,024 bytes | Binary memory measurement |
MiB | 1,024 KiB | Binary capacity |
kB | 1,000 bytes | Decimal size |
MB | 1,000,000 bytes | Decimal drive capacity |
Worked example: a lab stores 48 uncompressed monochrome images, each 128 × 64 pixels with one bit per pixel. One image needs 128 × 64 = 8,192 bits, then 8,192 ÷ 8 = 1,024 bytes. All images need 48 × 1,024 = 49,152 bytes. Dividing by 1,024 gives 48 KiB, excluding headers and metadata. Compression or colour depth would change this calculation.
5. Input and output devices
Input devices capture data or instructions. A scanner digitises a page, a microphone captures sound, and a camera captures images. OCR recognises text within a scanned image; scanning alone does not guarantee editable text. A barcode reader reads an encoded identifier, which an application can use to retrieve product details.
Output devices present results: a monitor provides visual output, speakers provide audio, and a printer produces hard copy. A touchscreen combines display output and touch input. Choose devices by purpose: a visually impaired learner may benefit from screen-reader audio, while a diagram-heavy practical may require a sufficiently clear display. A sensor can feed observations automatically, whereas a keyboard relies on deliberate human entry. Input and output are roles, so one physical device may support both.
6. Storage technologies and selection
Magnetic storage, such as a hard disk, stores data magnetically. Optical storage uses a laser to read discs. Solid-state storage, including SSDs and flash drives, uses electronic memory without the moving read mechanism of a hard disk. Compare access speed, portability, capacity, durability and cost per unit of storage.
A school may use an SSD for responsive application access and a separate backup destination for recovery. A portable flash drive is convenient for transfer but can be misplaced; convenience does not make it a complete backup policy. Non-volatile does not mean indestructible. Drives can fail, files can be deleted, and malware can damage accessible copies. Keep backups separate enough that a single incident cannot destroy every copy.
7. Software categories and translators
System software supports the computer's operation. It includes the operating system, device drivers and language translators. Application software performs user tasks, such as preparing slides, managing accounts or browsing learning resources. Utilities perform maintenance or support tasks, such as backup, compression and malware scanning.
A compiler translates source code into another form, often a complete target program, while an interpreter executes program instructions through an interpreting environment. An assembler translates assembly language. These are conceptual roles; real language implementations can combine compilation and interpretation. Python implementations commonly compile source into bytecode before executing it, so saying Python never involves compilation is misleading. A driver allows the operating system to communicate with a particular device rather than replacing the application.
8. Operating systems and a complete scenario
An operating system manages processes, memory, files, devices and user access. Process scheduling shares processor time; memory management allocates working space; the file system organises persistent data. A graphical interface uses visual controls, while a command-line interface accepts commands. The interface style is not the whole operating system.
Suppose a student prints an essay. The application requests printing, the operating system manages the job, a suitable driver communicates device-specific instructions, and the printer produces output. Meanwhile, the essay is in RAM while being edited and on storage after saving. If the printer is disconnected, adding RAM does not repair the connection. Explain a fault by locating its role in this chain rather than recommending the fastest or largest component automatically.
A reliable approach to questions
Read the command word before choosing an answer. A definition needs the distinguishing feature; a comparison needs matching criteria on both sides; an application needs a reason linked to the situation.
Extract the supplied evidence and assumptions. Keep a small working table rather than relying on memory. If information is absent, state the limit instead of inventing a value or claiming certainty.
Work through the relevant rule one step at a time. For a program, record the changing state; for a scenario, connect the requirement to the feature that meets it. Explain why the closest alternative fails.
Check the result against the original question, including boundary cases, units and wording. Present a concise final answer followed by enough reasoning for another student to reproduce your conclusion.
Connections that matter
Number systems explain why memory is measured in bits and bytes.
Python programs rely on CPU execution, memory and operating-system services.
Responsible computing connects storage choices to backups and safe disposal.
Common mistakes
Confusing RAM with permanent storage: saving requires a persistent copy.
Calling the control unit an arithmetic device: arithmetic belongs to the ALU.
Treating MB and MiB as identical: state decimal or binary units.
Assuming one device has only one role: a touchscreen accepts input and displays output.
Revision checklist
I can explain the input–process–output model with storage.
I can distinguish CPU components and their roles.
I can compare volatile memory and persistent storage.
I can calculate storage using explicit bit and byte units.
I can classify software and explain operating-system services.