Key Point
| Why abstraction matters | Benefit |
|---|---|
| Simplification | Reduces complexity so problems are easier to understand and solve |
| Efficiency in design | Speeds development by focusing only on relevant system parts |
| Layered architecture | Lets each layer (e.g. TCP/IP) be designed/tested independently |
| Accessibility | Enables non-specialists to program without machine-level detail |
Worked Example
TCP/IP Layered Architecture (Abstraction Example)
Each layer abstracts the complexity below it. A browser uses HTTP without handling electrical signalling details.
| Layer | Example protocol/tech | Responsibility |
|---|---|---|
| Application | HTTP, FTP, SMTP | User-facing network services (e.g. sending email) |
| Transport | TCP | Reliable end-to-end delivery |
| Network | IP | Addressing and routing across networks |
| Data Link | Ethernet, Wi-Fi frames | Local network transmission |
| Physical | Cables, radio signals | Raw signal transmission |