Operating and Distributed Systems Quiz

Definition: Software that manages hardware and software resources on a computer.
Functions:
- Process management: Handles the creation, scheduling, and termination of processes.
- Memory management: Allocates and deallocates memory space as needed.
- File system management: Provides a way to store and retrieve files on storage devices.
- Device management: Manages device communication via drivers.
- User interface: Facilitates interaction between the user and the system (CLI or GUI).

Definition: A model where components located on networked computers communicate and coordinate their actions.
Characteristics:
- No shared clock: Each component operates independently.
- Asynchronous communication: Components communicate through messages over a network.
- Scalability: Can grow by adding more nodes.
- Fault tolerance: Can continue operation even if some components fail.
Examples: Cloud computing, peer-to-peer networks, and microservices architecture.

Definition: The conceptual model that defines the structure, behavior, and more views of a system.
Key Aspects:
- Components: Individual parts of the system (e.g., processors, memory, I/O devices).
- Interconnections: How components communicate (e.g., buses, networks).
- Data flow: Path of data within the system.
- Layering: Organizes system into layers for abstraction and separation of concerns.
Types:
- Von Neumann architecture: Single memory for data and instructions.
- Harvard architecture: Separate storage for data and instructions.

Definition: Process of defining the architecture, components, modules, interfaces, and data for a system.
Key Principles:
- Modularity: Dividing a system into smaller, manageable parts.
- Abstraction: Simplifying complex systems by hiding details.
- Scalability: Designing systems to handle growth.
- Maintainability: Ensuring the system can be updated and repaired easily.
Stages:
- Requirements analysis: Understanding user needs.
- System specification: Defining what the system should do.
- Architectural design: High-level structure of the system.
- Detailed design: Specifics of components and interactions.

Definition: Systems that involve multiple computers and devices communicating over a network.
Components:
- Nodes: Individual devices (computers, servers, routers).
- Links: Connections between nodes (wired or wireless).
- Protocols: Rules governing communication (e.g., TCP/IP, HTTP).
Types of Networks:
- Local Area Network (LAN): Limited geographic area, high speed.
- Wide Area Network (WAN): Covers large geographic areas, lower speed.
- Peer-to-Peer: Direct connection between nodes without a central server.
Functions:
- Data transmission: Transfer of data between devices.
- Resource sharing: Allows multiple users to access shared resources.
- Communication: Facilitates interaction through various services (emails, messaging).

A model where components on networked computers communicate and coordinate actions.
Characteristics:
- No shared clock: Each component operates independently without synchronized timing.
- Asynchronous communication: Components communicate via messages sent over a network.
- Scalability: Capable of expanding by adding more nodes.
- Fault tolerance: Remains operational despite the failure of some components.
Examples: Cloud computing, peer-to-peer networks, microservices architecture.

Conceptual model defining the structure and behavior of a system.
Key Aspects:
- Components: Parts of the system such as processors, memory, and I/O devices.
- Interconnections: Communication methods among components (e.g., buses, networks).
- Data flow: The path and management of data transitioning within the system.
- Layering: Organizes the system into layers for improved abstraction and separation of concerns.
Types:
- Von Neumann architecture: Utilizes a single memory space for both data and instructions.
- Harvard architecture: Employs separate storage for data and program instructions.

Process that defines the architecture, components, modules, interfaces, and data for a system.
Key Principles:
- Modularity: Breaks down a system into manageable, smaller parts.
- Abstraction: Simplifies complex systems by concealing intricate details.
- Scalability: Design must accommodate growth and increased demand.
- Maintainability: Ensures ease of updating and repair.
Stages include:
- Requirements analysis: Gathers and defines user needs.
- System specification: Outlines the functionalities the system must provide.
- Architectural design: Defines high-level structure and components.
- Detailed design: Focuses on specific components and their interactions.

Systems involving multiple computers and devices that communicate over a network.
Components:
- Nodes: Individual devices such as computers, servers, and routers.
- Links: Connections between nodes that can be wired or wireless.
- Protocols: Sets of rules regulating communication (e.g., TCP/IP, HTTP).
Types of Networks:
- Local Area Network (LAN): Operates within a limited geographic area, typically high-speed.
- Wide Area Network (WAN): Spans large geographic areas with generally lower speeds.
- Peer-to-Peer: Direct connections between nodes without a centralized server.
Functions:
- Data transmission: Enables data transfer between devices.
- Resource sharing: Allows multiple users to access shared resources efficiently.
- Communication: Facilitates interactions through services such as email and messaging.