IB COMPUTER SCIENCE | A1.3.1 Role of Operating Systems

Lesson objective

Describe how operating systems manage hardware resources, provide services for applications, support user interaction and control access to resources.

Learn

A1.3.1 | ROLE OF OPERATING SYSTEMS

01 | YOUR APPS SHARE ONE COMPUTER

Imagine listening to music while writing an essay and downloading a file. The applications appear to work independently, yet they use the same processor cores, RAM, storage and network connection. Something must coordinate access to those resources.

An operating system (OS) is system software that manages a computer’s hardware resources and provides common services for applications. It also provides ways for users to interact with the system.

Without shared management, every application would need much more responsibility for controlling devices and avoiding conflicts with other programs. The OS provides a coordinated environment in which applications can run.

The key idea is not simply “the OS makes the computer work”. Its role is to make hardware usable by software, manage competing demands and provide controlled access to resources.

02 | THREE THINGS TO KEEP SEPARATE

Hardware is the physical equipment: the CPU executes instructions, RAM holds working data, and an SSD stores files. Hardware performs the physical operations.

Application software performs a user’s task, such as editing a photograph, writing a document or displaying a webpage. It decides much of what the user wants to do with the data.

The operating system supplies a managed environment and shared services that support those tasks. A photo editor chooses an image effect; the OS helps provide processor time, memory and access to the saved image.

A file manager supplied with an OS is a useful interface to file operations, but its visible window is only one part of the overall system. Much of the OS’s work happens without a window appearing.

PartExample responsibility
ApplicationApply a blur effect to a photograph
Operating systemManage memory and file access for the editor
HardwareExecute instructions and store the resulting bits

03 | THE OS AS AN INTERMEDIARY

An intermediary sits between other parts and helps them work together. Applications request services rather than each implementing all the low-level details of every storage device, printer and network adapter.

For example, a text editor can request that data be written to a named file. OS services manage access to the file system and coordinate the operation through appropriate device software. The application does not need to know the physical storage location of each byte.

The model below is a conceptual view of responsibilities. It is not a claim that every CPU instruction takes a trip through each box: ordinary application calculations run on the CPU, while managed operations such as file access use OS services.

USER AND APPLICATIONS

A person edits a document; the editor requests services.

OPERATING SYSTEM

Interfaces, shared services, resource management and protection.

HARDWARE

Processor, memory, storage and input/output devices.

Applications use OS services for managed resources. Hardware carries out the physical work.

04 | HIDING DETAIL WITH ABSTRACTION

When you save a document, you choose a folder and filename. You do not normally specify an SSD controller command or the storage blocks that should contain the data. The system presents a simpler way to work with a complicated device.

This is an abstraction: a useful representation that hides details the user or application does not need for the task. Files and folders are examples of OS-supported abstractions.

Abstraction does not mean the detail disappears. The system still has to carry out the underlying operation. It means an application can use a common file service while the OS and related components handle lower-level work.

This reduces duplicated development effort. Several applications can use the same file services instead of each containing a complete storage-management system.

05 | PROVIDING AN ENVIRONMENT FOR APPLICATIONS

An installed program is stored software. When it runs, the OS creates and manages a running instance, called a process. The process needs resources such as memory and opportunities for its instructions to execute.

Applications use application programming interfaces (APIs): defined ways for software components to request services. An API may be supplied by the OS, a library or another service. APIs are not all direct calls to the OS kernel.

A system call is a controlled request to the kernel for an OS service, such as certain file or process operations. Libraries often provide easier functions that make these requests on an application’s behalf.

You do not need to memorise system-call names here. Understand the purpose: applications have an organised way to request managed services rather than unrestricted control of every resource.

06 | COORDINATING LIMITED RESOURCES

A resource is something a program needs to do its work, such as CPU time, RAM, storage space or a device. These resources have limits, and several programs can need them at once.

The OS coordinates allocation and access. For instance, it can schedule runnable work on processor cores, manage memory allocations and organise queued device operations. Different resources need different management techniques.

On one CPU core, instructions from different runnable tasks can be interleaved over time. Multiple cores can also execute work in parallel. The appearance of several active applications does not mean every task runs continuously or at exactly the same instant.

The next lesson examines individual OS functions in more detail. At this stage, connect resource management to its overall purpose: supporting useful, responsive work while preventing programs from simply taking whatever they want.

07 | PROVIDING WAYS FOR PEOPLE TO INTERACT

A user interface lets a person give instructions and receive feedback. A graphical user interface (GUI) uses visual controls such as windows, icons and menus. A command-line interface (CLI) accepts text commands.

A graphical file manager can let you open a folder by clicking it. A command-line shell can request related file operations using commands. The interfaces differ, but they can rely on services from the same underlying OS.

A GUI is therefore not the entire operating system, and an OS does not have to display a desktop. Servers and embedded devices may run without a local graphical interface.

Applications also have their own interfaces. The buttons inside a photo editor do not all belong to the OS simply because they appear on the screen.

08 | PROTECTION AND CONTROLLED ACCESS

On a shared computer, one user should not automatically be able to read another user’s private files. Likewise, an ordinary application should not freely overwrite another application’s memory.

The OS helps enforce access control: rules governing which users and processes may use particular resources. Authentication establishes an identity; authorisation determines what that identity is allowed to do.

In many general-purpose systems, ordinary application code runs with restricted privileges. The kernel, the central part of the OS, runs with privileges needed for core management. This separation supports protection and stability.

Protection is not a guarantee that a system can never fail or be compromised. A faulty application may be contained, but faults in privileged components can have wider effects. Configuration, updates and other security measures still matter.

09 | DEVICE DRIVERS CONNECT THE DETAILS

A printer, keyboard and storage controller do not all accept the same low-level instructions. A device driver is software that helps the OS communicate with a particular device or device class.

An application can request printing through a supported interface while printing services and suitable drivers help prepare and deliver the job. The printer’s hardware then produces the physical page.

The driver is software, not the cable or the physical device. Some drivers are supplied with an OS; others come from device manufacturers. Driver organisation varies, so do not assume every driver always runs in the same privilege mode.

A common interface makes device access more manageable, but it does not guarantee that every device or application will work with every OS. Suitable hardware support and compatible software are still required.

10 | FOLLOW A REQUEST THROUGH THE SYSTEM

Choose a task and step through a simplified example. Notice how responsibility changes: the application decides what the task means, the OS provides managed services, and hardware performs the physical operation.

The exact implementation varies by OS and application. These examples describe responsibilities rather than a complete sequence of every internal operation.

11 | WHO IS RESPONSIBLE FOR THIS PART?

A single task can involve all three layers. Classify the specific responsibility described in each case, rather than assigning the entire task to just one layer. For example, the editor chooses the document format, OS services manage file access, and a storage device retains the bits.

Each first answer counts towards your score. Feedback explains the distinction before you move on.

12 | THE OS IS NOT THE SAME AS FIRMWARE

When a computer starts, firmware helps initialise the platform and begin the startup process. A bootloader then loads the OS kernel, sometimes through several stages. The OS takes on the ongoing management role once it is running.

Firmware is software closely associated with hardware, such as motherboard startup firmware. It is not the same as the desktop OS, even though both are system-level software. The exact boundary and startup sequence depend on the device.

A typical computer stores its installed OS on non-volatile storage and loads the code and data it needs into memory during operation. Do not describe a normal desktop OS as simply being “stored in ROM”.

Not every computer-based device requires a general-purpose OS. A small microcontroller can run a dedicated program directly on its hardware, often called bare-metal software. More complex embedded systems may use an OS, including a real-time OS.

13 | DIFFERENT SYSTEMS, THE SAME CENTRAL ROLE

Windows, macOS, Linux-based systems, Android and iOS are familiar OS examples. They differ in interface, design, supported hardware and available applications, yet they all provide managed environments for software.

A laptop emphasises interactive work. A server may provide services remotely with no local graphical desktop. A phone manages apps alongside touch input, sensors, network connections and battery constraints.

The presence of a browser does not make the browser an OS. A browser is application software, even when it is the user’s main workspace. Similarly, cloud software still runs on computers with underlying system software.

An application built for one OS may depend on interfaces and executable formats that another does not provide. Shared OS services reduce the details each application must handle, but they do not make all applications universally portable.

14 | DESCRIBE THE ROLE WITH A LINKED EXAMPLE

For describe the role of operating systems, identify the OS as system software, state that it manages hardware resources and provides common services, and connect those roles to an example. Mention interaction and protection where relevant.

A strong response might be: “An operating system provides a managed environment for applications. It coordinates processor time and memory so several applications can make progress, and supplies file services so an editor can save a named document without directly controlling the storage device. It also enforces permissions on access to resources.”

Avoid saying that the OS does the application’s whole job, is just the desktop, or guarantees security. Describe who does what and why the shared management layer is useful.

Next, you will examine the individual functions of an OS, including how it manages processes, memory, files and devices.

Further reading: application and kernel protection in Windows

MATCH THE SYSTEM TERM TO ITS ROLE

Terminology

Terminology

Operating system

System software managing hardware resources and providing common services for applications.

System software

Software supporting the operation and management of a computer system.

Application software

Software performing tasks for users, such as editing documents.

Hardware

The physical components of a computer.

Resource

A capacity or component needed for work, such as CPU time, memory or a device.

Resource management

Coordinating the allocation and use of system resources.

Intermediary

A layer that helps other parts of a system interact.

Abstraction

A useful representation that hides unnecessary underlying detail.

OS service

A facility offered by the OS, such as managed file access.

Process

A running instance of a program with associated execution state and resources.

Kernel

The central OS component responsible for core system management.

API

A defined interface through which software requests functionality from another component.

System call

A controlled request to the kernel for an OS service.

User interface

A means for users to give instructions and receive feedback.

GUI

A graphical user interface using visual controls.

CLI

A command-line interface accepting text commands.

Shell

An interface program through which a user interacts with OS services.

Device driver

Software helping an OS communicate with a device or device class.

Access control

Rules and mechanisms restricting use of resources.

Authentication

Establishing the identity of a user or other entity.

Authorisation

Determining which actions or resources an identity is permitted to use.

Privilege

Permission to perform particular operations in a system.

Multitasking

Managing progress of multiple tasks, including by interleaving execution.

Firmware

Software closely associated with hardware operation and control.

Bootloader

Software that loads the OS kernel as part of startup.

Bare-metal software

Software running directly on hardware without an underlying OS.

Questions

Questions

CHECK YOUR UNDERSTANDING

Select all correct choices. Each exact set earns one point.

1. Which describe the overall role of an OS?
2. Which is an application-specific responsibility?
3. Why are files and folders useful abstractions?
4. Which statements about interfaces are correct?
5. What is a process?
6. Which statements about drivers are correct?
7. What is the difference between authentication and authorisation?
8. Which statements about applications and hardware are accurate?
9. Which statements about startup and embedded devices are correct?
10. Which are reasons for shared OS services?

EXPLAIN AND COMPARE

Write your answers before revealing each sample.

1. Describe the role of an operating system.

2. Describe how an OS helps several applications use one computer.

3. Describe the difference between an OS and an application using a text editor.

4. Describe an OS abstraction and its benefit.

5. Describe how a user can interact with an OS without a GUI.

6. Describe the role of a device driver.

7. Describe how an OS helps protect a user’s files.

8. Describe a process and why the OS manages it.

9. Describe the relationship between firmware, a bootloader and the OS.

10. Describe why an OS is more than the visible desktop.

DESCRIBE IT | A SHARED SCHOOL COMPUTER

A student edits a report while music plays and a download continues. Describe the OS’s role in supporting these activities. Separate the work of applications, OS services and hardware. Then describe what should happen if an application requests a file the student is not permitted to read. Use linked examples rather than simply listing management functions.

Flashcards

Flashcards

Click to flip. Select the ideas you need to revisit.

0 cards selected for revision.

    Selections are kept while this page is open.

    Workbook

    Workbook

    COMING SOON

    The workbook for A1.3.1 Role of Operating Systems is coming soon. Complete the matching task and written questions in your exercise book.