🧽

Operating Systems – Unit I

BCA – AI / ML | Course Presentation 2026

Slide 01 / 20
Academic Presentation • Bikini Bottom Edition

OPERATING SYSTEMS

Unit I: Introduction, Architecture & Strategies

PRESENTED BY

Eyad Khatab

Course: BCA – AI / ML

2026-09-28

What We Will Learn:

  • System Software & Hierarchy
  • Hardware vs Application OS
  • Resource Abstraction
  • 4 Key Execution Strategies
  • CPU Scheduling Algorithms
  • Process Lifecycle & States
SpongeBob OS Command Center

SpongeBob's OS Command Center

SpongeBob acts as the master OS coordinator, balancing CPU, Memory, and Storage for Bikini Bottom!

Patrick (User) Sandy (Tech) Mr. Krabs (Resource)
BCA – AI/ML • Operating Systems Unit I Press → or Click Next to Dive In! 01 / 20
Course Roadmap

Agenda – Our Dive Route (9 Stops Ahead)

Unit I Outline
01 What is an Operating System?
02 Computer Software Hierarchy
03 System Software vs Application Software
04 Components of System Software
05 Resource Abstraction
06 OS Strategies (Batch, Multiprogramming, Multitasking, Time-Sharing)
07 CPU Scheduling & Round Robin
08 Process vs Program & Process States
09 Summary & Wrap-up
Bikini Bottom Route Map

The Bikini Bottom Route Map

SpongeBob drives the boatmobile across 7 circular stops along the Bikini Bottom OS highway, with Patrick holding the map and Sandy ensuring technical accuracy!

Goal: Master Unit I concepts with 100% academic rigor and visual clarity!
BCA – AI/ML • Operating Systems Unit I 02 / 20
Slide 03 • Fundamental Concept

What is an Operating System?

The boss fish of the whole computer reef

Formal Definition:

System software that manages computer hardware and provides an environment for application programs. It acts as an intermediary between users/applications and physical hardware.

Major OS Responsibilities:

CPU Management
Memory Management
Storage & File System
I/O Management
Process Management
Protection & Security
Popular Examples: Linux, Windows, macOS, Android, Unix.
Visualizing Intermediary Role

Visualizing the Intermediary Role

SpongeBob stands at a central control board directing traffic between user app requests (Squidward's music app) and raw hardware gears (CPU, RAM, Disks).

Security Guard:

Plankton tries to sneak past without permission, but the OS security barrier locks him out!

BCA – AI/ML • Operating Systems Unit I 03 / 20
Slide 04 • System Architecture

Computer Software Hierarchy

From the user at the surface... down to the hardware at the seabed

1. USERS People running tasks (SpongeBob, Patrick, Sandy)
2. APPLICATION SOFTWARE User-specific tasks — Word, Chrome, Games
3. SYSTEM SOFTWARE Manages computer & provides platform — OS, Drivers
4. HARDWARE CPU, Memory, Disk, I/O Devices
4-Story Underwater Glass Tower

4-Story Underwater Glass Tower

Squidward rides a glass elevator through four levels. SpongeBob coordinates in the System Software level, ensuring applications never crash directly into raw hardware circuitry!

Key Insight: User applications communicate strictly downwards through the OS abstraction layers!
BCA – AI/ML • Operating Systems Unit I 04 / 20
Slide 05 • Comparison

System Software vs Application Software

Aspect System Software Application Software
Purpose Resource management & machine operation User-specific tasks & productivity
Necessity Essential (Computer cannot run without it) Optional (Installed based on user needs)
Examples Windows, Linux, Device Drivers, Firmware MS Word, Google Chrome, Media Players
Orientation Hardware-oriented User-oriented
💡 "System software builds the platform — application software plays on it!"
BCA – AI/ML • Operating Systems Unit I 05 / 20
Slide 06 • Module Breakdown

Components of System Software

Five crew members that keep the submarine running smoothly

1. Operating System (OS):

Core manager of CPU, memory, storage, files, I/O devices, and security.

2. Device Drivers:

Translators that allow the OS to talk to hardware peripherals.

3. Language Translators:

Assembler, Compiler, and Interpreter to translate high-level code to machine code.

4. Utility Software:

Tools for system maintenance, backup, disk management, antivirus, and diagnostics.

5. Firmware:

Low-level control software stored permanently in non-volatile memory (BIOS / UEFI).

Operations Center with 5 Stations

Operations Center with 5 Stations

SpongeBob coordinates the central OS hub, Sandy operates language translators, Mr. Krabs manages backup utilities, Squidward controls output devices, and Patrick carries a giant wrench for hardware utilities!

All 5 components work together seamlessly.
BCA – AI/ML • Operating Systems Unit I 06 / 20
Slide 07 • Peripheral Interface

Device Drivers

The translators between the OS and every hardware gadget

Communication Pipeline:

Application OS Device Driver Hardware

Common Driver Examples:

  • • Printer Driver
  • • Graphics Card Driver
  • • Network Adapter Driver
  • • Audio / Sound Driver
📌 EXAM POINT: A driver hides device-specific hardware details from applications!
The Repair Shop & Drivers Scene

The Repair Shop Scene

SpongeBob uses translating cables to connect the OS to giant printers and audio speakers. Patrick tries to bypass the driver and plug hardware straight into the OS—resulting in a funny shock!

Driver = Hardware-Specific Translator
BCA – AI/ML • Operating Systems Unit I 07 / 20
Slide 08 • Execution Engine

Language Translators

Computers execute only machine instructions — somebody must translate!

1. Assembler

Translates low-level Assembly language directly into binary machine code.

2. Compiler (e.g., GCC, Clang)

Translates the entire source code program into machine code before execution.

3. Interpreter (e.g., Python, Ruby)

Translates and executes source code line-by-line dynamically during execution.

⚡ Compiler translates ALL before run — Interpreter translates WHILE running!
The Code Translation Factory

The Code Translation Factory

Sandy operates a massive Compiler machine that converts an entire batch of blueprint code into a finished machine binary, while Patrick feeds line-by-line tape into an Interpreter machine!

Source Code → [Translator] → Machine Code (1s & 0s)
BCA – AI/ML • Operating Systems Unit I 08 / 20
Slide 09 • Maintenance & Control

Utility Software & Firmware

The maintenance toolbox and the built-in brain of hardware

Utility Software

Software designed to analyze, configure, optimize, or maintain a computer system.

  • ✔ Backup & Recovery Tools
  • ✔ Disk Defragmentation & Management
  • ✔ File Compression (Zip/Rar)
  • ✔ Antivirus & Security Scanners
  • ✔ System Diagnostics
Firmware

Low-level software embedded permanently into non-volatile memory (ROM/Flash) for hardware initialization and control.

  • ✔ Motherboard BIOS / UEFI
  • ✔ Router Control Firmware
  • ✔ Embedded IoT Device Firmware
Key Distinction: Utilities run on top of the OS for routine maintenance; Firmware resides inside hardware chips to boot the system!
BCA – AI/ML • Operating Systems Unit I 09 / 20
Slide 10 • Core OS Concept

Resource Abstraction – Meaning

Hide the scary machinery, show a friendly button

Definition:

Abstraction is the technique where the OS hides the complex physical details of hardware and presents simple, logical high-level interfaces to application programs.

Example Code Abstraction:

file = open("data.txt")
read(file) → write(file) → close(file)

Applications request simple operations without needing to know physical magnetic tracks, arm movements, or controller interrupts!

Glass Abstraction Barrier

Glass Abstraction Barrier

SpongeBob stands in front of a clean control box with one glowing "OPEN" button. Sandy pulls back a curtain revealing a chaotic mess of cables, gears, and spinning disks behind the smooth interface!

Hide Complexity → Provide Simple Interface
BCA – AI/ML • Operating Systems Unit I 10 / 20
Slide 11 • Architectural Rationale

Why is Abstraction Needed?

Because nobody wants to talk to a disk controller at breakfast

What Apps Do NOT Need to Know:

  • ❌ Which physical disk sector holds data
  • ❌ Hardware-specific controller protocols
  • ❌ Complex interrupt signal timing

Key Benefits of Abstraction:

  • ✔ Simplicity: Easy high-level programming
  • ✔ Portability: Code runs on different machines
  • ✔ Security: Protected direct hardware access
  • ✔ Resource Sharing: Concurrent safe access
  • ✔ Hardware Independence: Upgrades don't break apps
Smooth Golden Bridge vs Terrifying Maze

Smooth Golden Bridge vs Terrifying Maze

SpongeBob happily walks across a golden abstraction bridge above a dark, tangled maze of physical sectors. Mr. Krabs guards five glowing gates representing Simplicity, Portability, Security, Sharing, and Independence!

Abstraction transforms low-level chaos into high-level order.
BCA – AI/ML • Operating Systems Unit I 11 / 20
Slide 12 • Taxonomy

The Four Key Abstractions

Every heavy physical machine gets a friendly logical mask

Physical Resource OS Abstraction Key Purpose
Physical CPU Process / Thread Virtual dedicated execution thread
Physical RAM Memory Virtual Memory Isolated, uniform memory space
Storage Disk File / Directory Structured persistent byte stream
Network Card Socket Interface Standard communication endpoint
CPU → Process  |  Memory → Virtual Space  |  Disk → File  |  Network → Socket
Four Key Abstractions Illustration

Hardware to Logical Abstraction

BCA – AI/ML • Operating Systems Unit I 12 / 20
Slide 13 • Execution Models

OS Strategies – Overview

Four ways the OS organizes swimming lanes for processes

01

Batch Processing

Jobs grouped, run with zero user interaction.

Goal: Throughput
02

Multiprogramming

Multiple programs in RAM; switch CPU on I/O wait.

Goal: CPU Utilization
03

Multitasking

Rapid CPU context switching across concurrent tasks.

Goal: Progress
04

Time-Sharing

Fixed time quantum rotated among interactive users.

Goal: Response Time
⭐ "Each strategy optimizes a different superpower to keep system performance high!"
BCA – AI/ML • Operating Systems Unit I 13 / 20
Slide 14 • Strategy 01

01 Batch Processing

Collect the jobs, run them all, no interruptions

Core Concept & Flow:

Jobs collected and executed in batches without user interaction during execution.

Jobs → Job Queue → OS → CPU → Output Results
Advantages:

Highly efficient for large, repetitive non-interactive tasks.

Disadvantages:

Poor response time; errors discovered late at batch end.

Practical Examples: Payroll processing, student grade processing, bill printing.

Industrial Conveyor Batch Scene

Industrial Conveyor Batch Scene

Patrick stands outside a locked fence waiting for a long queue of papers to finish processing inside a heavy CPU machine. A giant slow-moving clock on the wall highlights the long wait time!

High Batch Throughput | Low User Interaction
BCA – AI/ML • Operating Systems Unit I 14 / 20
Slide 15 • Strategy 02

02 Multiprogramming

While one fish waits, another one swims!

Mechanism:

Multiple programs reside in memory simultaneously. When the currently running program (P1) pauses to wait for an I/O operation (e.g., disk read), the OS context-switches the CPU to run another ready program (P2).

P1 waits for Disk/IO ➔ CPU instantly switches to execute P2!
Primary Goal:

Maximize CPU utilization & eliminate idle CPU waiting time.

Requirements:

Memory management, scheduling, and program protection.

Memory Booth CPU Sprint

Memory Booth CPU Sprint

Inside a giant Memory Room with glass booths, P1 shows a red "Waiting for I/O" light. SpongeBob as the CPU manager instantly sprints over to booth P2 with a green "Running" light!

Zero Idle CPU Time!
BCA – AI/ML • Operating Systems Unit I 15 / 20
Slide 16 • Strategy 03

03 Multitasking

Many tasks, one CPU, super-fast costume changes

Concurrent Progress Experience:

Logical extension of multiprogramming. The OS rapidly switches the single CPU core among multiple runnable processes/threads so quickly that users feel all applications are running simultaneously.

User Experience Sequence:
Browser ➔ Music Player ➔ IDE ➔ Browser ➔ Music

High-speed time slices create seamless user concurrency.

SpongeBob Multitasking

SpongeBob Motion Blur Scene

SpongeBob moves so fast he appears as a blur operating three screens at once (Squidward's browser, Patrick's music player, Sandy's IDE). Mr. Krabs holds a stopwatch showing lightning switches!

One Physical CPU • Perceived Concurrency
BCA – AI/ML • Operating Systems Unit I 16 / 20
Slide 17 • Strategy 04

04 Time-Sharing

Everyone gets a slice of CPU cake — one quantum at a time

Interactive Multi-User Computing:

Designed specifically for interactive multi-user/multi-tasking systems. Each active user or process receives a small fixed CPU time slice called a Time Quantum.

Goal & User Perception:

Rapid rotation ensures fast response times. Every connected user feels as if they have exclusive access to the CPU!

Rotation: User 1 (Quantum) ➔ User 2 (Quantum) ➔ User 3 (Quantum) ➔ Repeat
The Equal Spotlight Stage

The Equal Spotlight Stage

SpongeBob, Patrick, Sandy, and Squidward sit on equal pedestals under a giant pie-chart clock. A single CPU spotlight shines on SpongeBob; as his tiny quantum slice finishes, the spotlight passes smoothly to Patrick!

Fair Time Slice = Excellent Interactive Response
BCA – AI/ML • Operating Systems Unit I 18 / 20
Slide 18 • Algorithmic Control

CPU Scheduling & Round Robin

Who gets the CPU next? Take a ticket and wait your turn!

The CPU Scheduler:

Selects which ready process in memory gets the CPU next.

Common algorithms: FCFS, SJF, Priority, and Round Robin.

Round Robin (RR) Algorithm:

Preemptive scheduling algorithm where processes take circular turns with a fixed time quantum. Fair and optimal for interactive time-sharing systems.

Small Quantum: High switching overhead.
Large Quantum: Poor interactive response.
Circular Race Track Scene

Circular Race Track Scene

Three karts (P1, P2, P3) move in a circular track around a glowing CPU core trophy. SpongeBob acts as race referee blowing the whistle when a kart's quantum timer runs out!

Circular Queue • Equal CPU Share
BCA – AI/ML • Operating Systems Unit I 18 / 20
Slide 19 • Process Lifecycle

Process vs Program & Process States

Program:

Passive entity stored on disk (instructions, executable file).

Process:

Program in execution — active entity with CPU counter, registers, memory state, and allocated resources.

Five Process States:

  • 1. New: Being created
  • 2. Ready: Waiting for CPU
  • 3. Running: Executing on CPU
  • 4. Waiting: Blocked for I/O
  • 5. Terminated: Finished
Train Station State Machine

Train Station State Machine

SpongeBob brings a dusty static book (Program) to life with a hard hat (Process). He navigates 5 train platforms: New turnstile → Ready queue → Running inside CPU locomotive → Waiting bench at printer → Terminated exit gate!

New ➔ Ready ➔ Running ➔ Waiting ➔ Terminated
BCA – AI/ML • Operating Systems Unit I 19 / 20
Unit I Finale

Summary – We Survived Unit I! 🎉

Bikini Bottom Operating System Mastered!

Key Takeaways:

The Operating System acts as the core hardware manager and software execution platform.
Resource abstraction hides complex hardware mechanics behind simple logical interfaces.
Four OS Strategies: Batch, Multiprogramming, Multitasking, and Time-Sharing each optimize distinct execution goals.
A process is a program in execution, moving dynamically across five lifecycle states.
CPU Scheduling and Round Robin enable fair, efficient time-sliced execution.
Grand Celebration Finale

Grand Celebration Finale!

SpongeBob proudly holds the glowing OS emblem while Patrick, Sandy, Squidward, Mr. Krabs, Plankton, and Gary celebrate against the Bikini Bottom sunset sky!

Thank You! Questions?

PRESENTED BY Eyad Khatab • BCA – AI / ML

BCA – AI/ML • Operating Systems Unit I End of Unit I Presentation 20 / 20