Basic Computer Organisation

Introduction

Every computer, no matter how complex, boils down to the same basic cycle: it takes something in, does something with it, and gives something back. This chapter starts with that cycle.

Concept

A computer system's most fundamental sequence of operations is: Input → Process → Output.

• Input Unit — accepts raw data from the outside world and converts it into binary instructions the computer can actually work with. A keyboard is the standard example: every key you press gets translated into binary before the computer does anything with it.
• Processing — the CPU (and its parts, including the ALU) actually performs operations on that data.
• Output Unit — presents the processed result back in a human-readable form (a monitor, a printer).
• Storage Unit — holds data and instructions, both temporarily (RAM) and permanently (a hard disk).

Explanation

The Input → Process → Output sequence is worth memorizing in that exact order — it's the single most repeated structural idea in this chapter, and exam questions frequently test it directly by asking you to identify which stage a given device belongs to.

Note: A keyboard is an Input device specifically because its job is translating human characters into binary — not because it's simply "used to type."

Summary

Every computer system follows the same Input → Process → Output sequence: an Input Unit converts raw data to binary, the CPU processes it, an Output Unit presents the result, and a Storage Unit holds data both temporarily and permanently.

Core Functional Units

Introduction

Hardware alone can't do anything useful — software is what actually tells it what to do. Not all software plays the same role, though; this topic sorts software into its standard categories.

Concept

Software Categories

• System Software — acts as the interface between the hardware and the user (and other software). The Operating System is the primary example.
• System Utilities — support/maintenance programs, like Antivirus software or a Disk Defragmenter, that keep the system running smoothly.
• Application Software — general-purpose programs for a specific everyday task (a word processor, a browser).
• Customized Software — built specifically for one particular organization's needs (software written specifically for one hospital's or one bank's internal processes).

Language Translators

Language Translators convert human-written code into a form the machine can execute:

• Compilers — translate the whole program at once.
• Interpreters — translate and execute line by line.
• Assemblers — translate assembly language specifically.

Explanation

A Device Driver is worth noting explicitly as not a language translator — it's a different kind of system software entirely, one that lets the OS communicate with a specific piece of hardware. It's easy to lump it in with Compilers/Interpreters/Assemblers since all four sound like "system-level" software, but only the latter three actually translate code.

Note: Software built for ONE specific organization (a particular hospital, a particular bank) is Customized Software — general-purpose software anyone could buy off the shelf is not.

Summary

System Software interfaces hardware with users; System Utilities maintain the system; Application Software handles general tasks; Customized Software is built for one specific organization; Language Translators (Compiler, Interpreter, Assembler) convert code into machine-executable form — a Device Driver is system software but not a translator.

The Software Hierarchy

Types of System Software

Introduction

The Operating System is the single most important piece of system software — every other program on a computer runs through it, and it's constantly managing resources behind the scenes without you noticing.

Concept

Core OS Functions

• Processor Management — decides which process gets CPU time and when.
• Memory Management — allocates RAM to running applications.
• Device Management — handles communication between the OS and connected hardware, like a printer.
• File Management — organizes and controls access to files on storage.

User Interface Types

• GUI (Graphical User Interface) — icon and window based, following the WIMP model: Windows, Icons, Menus, Pointers.
• CLI (Command Line Interface) — the user interacts entirely by typing text-based commands.

Explanation

GUI and CLI represent a real tradeoff, not just "old vs. new": CLI is faster to use once you know the exact commands and uses fewer system resources, while GUI is far more intuitive for a new user and needs no commands memorized — which is exactly why both interface types still exist side by side today.

Note: WIMP is specifically the four building blocks of a GUI: Windows, Icons, Menus, Pointers — a common exam expansion question.

Summary

The OS manages the processor, memory, devices, and files — the core resources every running program depends on. Users interact with it either through a GUI (WIMP: Windows, Icons, Menus, Pointers) or a CLI (text-based commands).

Core Responsibilities