Architecture and OS for Computer Sciences
Computer architecture and operating systems explain how software meets hardware. Architecture covers the CPU, registers, instruction execution, memory hierarchy and caches. The operating system manages processes, threads, scheduling, virtual memory, file systems and synchronisation, so many programs can safely share one machine. Together they describe what actually happens when code runs.
Stage: Computer Systems · Part of the Computer Science roadmap · Last reviewed 19 November 2026
What to learn in Architecture and OS
- Describe the fetch, decode and execute cycle of a simple CPU
- Explain why caches speed up programs that access nearby memory
- Distinguish a process from a thread and what each one shares
- Compare round robin and priority scheduling on a small set of jobs
- Explain how virtual memory and paging give each process its own address space
Architecture and OS interview questions
What is the difference between a process and a thread?
A process is a running program with its own address space and resources. Threads are units of execution inside a process that share its memory and open files but have separate stacks and registers. Threads are cheaper to create but need synchronisation to avoid data races.
What causes a deadlock and how can it be prevented?
Deadlock needs four conditions at once: mutual exclusion, hold and wait, no preemption, and circular wait. Breaking any one prevents it. A common method is to acquire locks in a fixed global order, which removes the circular wait.
Where Architecture and OS fits in the Computer Science roadmap
Architecture and OS belongs to the Computer Systems stage (beginner level), which takes about 40 hours. Under the hood.
Other units in this stage
Back to the full Computer Science roadmap