HookYour laptop runs 200 programs at once on a chip that can only do one thing at a time
Open Task Manager on a Windows laptop right now and you will typically see well over 150 processes listed as "running". Your browser, a music app, the antivirus, a dozen background services — all apparently going at once. But a single CPU core can only execute one instruction at any given instant. The sense of everything happening simultaneously is an illusion, and the software that stages that illusion is the operating system. It slices the processor's time into tiny fragments and switches between programs thousands of times a second — fast enough that a video keeps playing while you type, even though, at the level of the silicon, the CPU is only ever doing one thing.
That juggling act is one of five jobs the operating system does, and section 1.5 is essentially a list of those jobs plus the smaller helper programs — utility software — that keep the system healthy. The operating system manages the interface you interact with, the memory your programs live in, the peripherals plugged in around it, the users who log in, and the files stored on disk. The utilities handle the maintenance the OS does not do every second: encrypting data, defragmenting a hard drive, compressing files to save space. OCR wants you to explain each job in terms of what problem it solves — not just to recite "manages memory", but to say what goes wrong without it.
ModelThe operating system's first two jobs: the interface and memory
The user interface is the layer that lets a human drive the machine. Most people use a graphical user interface (GUI) — windows, icons, menus and a pointer — which is easy for beginners but uses more memory and processing power. Power users and servers often prefer a command-line interface (CLI), typing text commands: harder to learn, but faster, more precise and far lighter on resources, which is why data centres are administered by typed commands rather than by clicking.
Memory management is the OS deciding which program's data sits where in RAM, and it is the mechanism behind the multitasking illusion from the introduction. When several programs run, the OS allocates each a region of memory and, crucially, stops one program reading or corrupting another's — without that isolation, one crashing app would take the whole machine down. When RAM fills up, the OS uses virtual memory: it moves the least-recently-used data out to a reserved area of the much slower hard drive (the "page file" or "swap"), freeing RAM for what you are using now. That is why a machine with too little RAM slows to a crawl when you open many tabs — it is constantly shuffling data between fast RAM and slow disk, an effect called thrashing.
Trace what happens when RAM runs out. A laptop has 8 GB of RAM. The user has a browser using 5 GB, a photo editor using 2 GB, and then opens a game needing 3 GB — a total demand of 10 GB against 8 GB of physical memory. The operating system cannot fit all three, so its memory manager identifies the browser tabs the user has not touched for a while, writes that data out to virtual memory on the SSD, and hands the freed RAM to the game. When the user clicks back to those tabs, the OS swaps them back in and pages something else out. Everything keeps working, but each swap involves the slow drive — so the more the machine over-commits memory, the more it stutters. The fix a real user feels is simply adding more RAM, which removes the need to page at all.
MechanismManaging peripherals, users and files
A modern PC has to talk to a huge range of hardware — printers, keyboards, webcams, graphics cards — made by hundreds of manufacturers. The OS cannot possibly know the details of every device, so it relies on device drivers: small programs, supplied by the hardware maker, that translate the OS's generic instructions ("print this page") into the exact signals a particular model understands. This is peripheral management, and it is why plugging in a brand-new printer sometimes triggers a "installing driver" message — the OS is loading the translator it needs.
User management lets multiple people share one computer or network with separate accounts, each with its own files, settings and access rights. A school network administrator has full control; a pupil account cannot install software or see other pupils' work. This is the same least-privilege idea that appears in network security. Finally, file management organises data into a hierarchy of folders (directories), and handles naming, moving, copying, deleting and setting permissions on files. It hides the physical reality — that a single file may be scattered across many separate blocks on the disk — behind the tidy fiction of "a document in a folder".
Follow a file's address. When file management stores a report, it does not just dump it somewhere — it records a path that pins down exactly where it lives in the folder hierarchy, for example C:\Users\Aryan\Documents\report.docx. Reading that left to right: the C: drive, then the Users folder, then that user's folder, then Documents, then the file itself with its .docx extension telling the OS which program opens it. User management then layers permissions on top: Aryan's account can edit that file, a guest account may be allowed only to read it, and another pupil's account cannot see it at all — three different rights on one physical file, all enforced by the operating system.
DataUtility software: defragmentation
Utility software is the category of small system programs that maintain, configure and optimise the computer — they are not applications you "use" so much as tools that keep the machine working well. OCR names three you must be able to explain: defragmentation, encryption and compression.
Defragmentation tackles a problem specific to magnetic hard disk drives (HDDs). As files are saved, deleted and resized over time, the free space becomes scattered, and the OS is forced to store new files in whatever gaps it can find — so a single file ends up split, or fragmented, across non-adjacent blocks all over the platter. Reading it then means the read/write head physically jumping back and forth, which is slow. A defragmentation utility physically reorganises the blocks so each file's pieces sit together (contiguously) and the free space is gathered into one region, so the head can read a file in one sweep. Crucially, solid-state drives (SSDs) should not be defragmented — they have no moving head, so fragmentation costs them no time, and the extra writes only wear the drive out faster.
Watch a disk before and after. Picture a hard disk as eight numbered blocks. A file report.doc was saved into blocks 1, 3 and 6, because blocks 2, 4 and 5 were occupied at the time; a file photo.jpg sits in blocks 2 and 5; blocks 4, 7 and 8 are free. To read report.doc, the head must travel 1 → 3 → 6, skipping over other data twice. After defragmentation, the utility rewrites the layout so report.doc occupies blocks 1, 2, 3 together and photo.jpg occupies 4, 5, with 6, 7, 8 left as one free region. Now report.doc reads in a single continuous pass — same data, far fewer head movements, faster access. Run the same routine on an SSD and you gain nothing while shortening the drive's life.
MechanismUtility software: encryption and compression
Encryption software scrambles the contents of files or an entire drive using a key, so that anyone who copies or steals the data without the key sees only meaningless ciphertext. This is why an encrypted, stolen laptop is a lost piece of hardware rather than a reportable data breach — the thief cannot read a byte of it. Whole-disk encryption tools (such as BitLocker on Windows) do this transparently in the background every time a file is written or read.
Compression software reduces the size of files so they take up less storage and transfer faster over a network. Lossless compression (used for text, program files and formats like ZIP and PNG) shrinks the data in a fully reversible way — the original is restored exactly. Lossy compression (used for photos, music and video, as in JPEG and MP3) achieves much bigger savings by permanently discarding detail the human eye or ear is unlikely to miss — which is fine for a holiday photo but unacceptable for a spreadsheet, where every value must survive. Choosing the right kind is the judgement OCR tests.
Compress a string by hand. One simple lossless method is run-length encoding (RLE), which replaces runs of the same value with a count and the value. Take the 12-character string AAAAAABBBWWW. Instead of storing twelve characters, RLE records the runs: six A's, three B's, three W's, written as 6A3B3W — just 6 characters. That is a saving of 50%, and it is completely reversible: 6A3B3W expands back to the exact original with no loss. Notice the catch that makes RLE a poor general tool: a string with no repeats, such as ABCDEF, would become 1A1B1C1D1E1F — twice the size. Compression only wins when there is redundancy to exploit, which is why the method must match the data.
VocabularyKey terms the mark scheme pays for
TrapsMisconceptions that cost marks
ExamWhat examiners want
In OCR J277 Component 01, systems software is examined across all three assessment objectives. AO1 marks come from stating the OS's jobs precisely — examiners want the function and the problem it solves, so "memory management allocates RAM to programs and keeps them isolated so one crashing program does not bring down the others" scores where a bare "it manages memory" does not. Learn the five OS roles (interface, memory, peripheral, user, file management) and the three named utilities (encryption, defragmentation, compression) as checklists, because "state two functions of an operating system" is a near-guaranteed question.
AO2 asks you to apply the idea to a scenario: if the stem says a computer with a hard disk drive has become slow to open files, the answer is defragmentation — and you should say why (scattered blocks force the read/write head to jump), not just name the tool. Watch for the SSD trap, where the correct application is that defragmentation would not help. The AO3 extended-response questions typically ask you to compare or justify — a GUI versus a command-line interface for a given user, or lossy versus lossless compression for given data. Structure these as a genuine two-sided argument ending in a decision tied to the scenario: "for a data-centre administrator a command-line interface is better because it is faster and uses fewer resources, even though it is harder to learn." The mark you must not drop is the justification — a comparison without a reasoned recommendation caps you below the top level.